Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

The new HTC ONE (M7)

Jumping from my Nexus 7 to my HTC One makes me loathe the lack of home center button on the One even more. After a long day of using the tablet, when I go to pick up my phone, I keep reaching for the center "HTC" logo to try to go home.

HTC will never live this one down. The home configuration is just all sorts of stupid.
 
onthecouchagain said:
Jumping from my Nexus 7 to my HTC One makes me loathe the lack of home center button on the One even more. After a long day of using the tablet, when I go to pick up my phone, I keep reaching for the center "HTC" logo to try to go home.

HTC will never live this one down. The home configuration is just all sorts of stupid.
Click to expand...

While I agree with you on that in my opinion its not that bad, just takes some getting used to. If you constantly use the HTC and no other android devices you can get used to it.
 
iPhonemaster5S said:
While I agree with you on that in my opinion its not that bad, just takes some getting used to. If you constantly use the HTC and no other android devices you can get used to it.
Click to expand...

Agreed, I don't find it that bad. But the One is my first Android device and I don't have any others.;)
 
onthecouchagain said:
If it didn't take a gazillion and ten steps to do it, and if it didn't look and sound confusing as hell, I would do it.

But it does.
Click to expand...

Fair enough. It is very confusing.

I find that the various YouTube videos out there are the best way to learn out to S-Off, etc for the first time.
 
onthecouchagain said:
If it didn't take a gazillion and ten steps to do it, and if it didn't look and sound confusing as hell, I would do it.

But it does.
Click to expand...

Now the hardest part is setting S-OFF :) But via HTCdev or revone (if still 4.1.2) is pretty easy overall.

Basically the steps have been refined somewhat after it was noted that the OTA update for 4.3 was going to phones with different MIDs, which was the hardest part to change and gave me the biggest heart attack.

The thread: http://forum.xda-developers.com/showpost.php?p=43459658&postcount=1 now has the steps outlined very easily for a FULL conversion to 4.3 via a RUU. It is easy enough to root the phone and then flash back the stock 4.3 recovery if you want to also, I can personally confirm that a rooted 4.2.2 with stock recovery still received the OTA to 4.3 without a problem (I lost root, but the update went through).

Use the stock non-rooted 4.3 RUU in the thread though :)

----------
onthecouchagain said:
I'd also be more confident if I had access to Windows. I'm all OSX.
Click to expand...

I'm on OS X and used the adb and fastboot commands from the latest SDK (they are under the adt-bundle-mac-x86_64-*/sdk/platform-tools folder / directory. Just make sure the RUU zip file (still zipped) is in the same folder / directory.
 
bwhinnen said:
Now the hardest part is setting S-OFF :) But via HTCdev or revone (if still 4.1.2) is pretty easy overall.

Basically the steps have been refined somewhat after it was noted that the OTA update for 4.3 was going to phones with different MIDs, which was the hardest part to change and gave me the biggest heart attack.

The thread: http://forum.xda-developers.com/showpost.php?p=43459658&postcount=1 now has the steps outlined very easily for a FULL conversion to 4.3 via a RUU. It is easy enough to root the phone and then flash back the stock 4.3 recovery if you want to also, I can personally confirm that a rooted 4.2.2 with stock recovery still received the OTA to 4.3 without a problem (I lost root, but the update went through).

Use the stock non-rooted 4.3 RUU in the thread though :)

----------



I'm on OS X and used the adb and fastboot commands from the latest SDK (they are under the adt-bundle-mac-x86_64-*/sdk/platform-tools folder / directory. Just make sure the RUU zip file (still zipped) is in the same folder / directory.
Click to expand...

That's the part that trips me up. What are they doing in the Terminal window with ADB and fastboot? The instructions always glaze over that part. They always just say "now run ADB in terminal" and I'm like wut?

I'll have a look at your thread, though. Thank you.
 
I found that xda thread very useful. Even better was the humorous line

"WE WILL NOT SPOON FEED YOU IN THIS THREAD"

Just like that caps and all.

I found it reasonably easy, just a bit laborious. A little time, patience and viola! Now we're running 4.3 Yipeeee !
 
onthecouchagain said:
That's the part that trips me up. What are they doing in the Terminal window with ADB and fastboot? The instructions always glaze over that part. They always just say "now run ADB in terminal" and I'm like wut?

I'll have a look at your thread, though. Thank you.
Click to expand...

:) It can be daunting, especially for someone new to this (I was just a couple of weeks ago). I also won't talk about S-OFF methods other than telling you to search :)

NOTE THAT THIS WILL COMPLETELY WIPE YOUR PHONE! Take a backup as appropriate :)

I downloaded the sdk from developer.android.com and it ended up in my Downloads folder, I'm lazy and left it there. I also downloaded the RUU from the thread above.

First thing you need to do is unzip the Android sdk which will give you a folder in Downloads in there is an sdk folder and in that a platform-tools, you can see this in Finder and then simply copy the RUU.zip from Downloads into that platform-tools folder.

Then open a terminal window and change to the following directory:

/Users/bmw/Downloads/adt-bundle-mac-x86_64-20130522/sdk/platform-tools

Note my username is bmw, yours will be different, also the adt-bundle may have a different date on it.

So you'll end up with a prompt called "YOUR-MACHINE:platform-tools username$". From there you will run the commands, remember on OS X you will need to preface each command with a "./" (no quotes). For example when they say adb you would type ./adb.

Let's look at the commands they have (your phone should be connected):

./adb reboot bootloader

That will reboot the phone into the boot loader. At this stage you should run the following and copy them to a notepad or similar for future reference:

./fastboot getvar all

Then you can change your CID to a new one (GOOGL001 in this case):

./fastboot oem writecid GOOGL001

The you put the phone into a ROM update mode in order to upload a full RUU:

./fastboot oem rebootRUU

Then simply flash the RUU, note the first time this will only really apply the hboot and give you an error "FAILED (remote: 90 hboot pre-update! please flush image again immediately)" simply flash the same zip again, this is expected to happen.

./fastboot flash zip RUU-HTC_One_GE-3.06.1700.10.zip

Then the second time:

./fastboot flash zip RUU-HTC_One_GE-3.06.1700.10.zip

Once that is complete (on the phone) you can then restart:

./fastboot reboot

When you reboot you will be in a NEW VANILLA Google Play Edition 4.3 ROM. You will need to install apps and all your details again.

*DISCLAIMER - All I have done above is reference the current commands in the thread as they stand at 13:11 on the 5th of August 2013 GMT+10 :) I also take no responsibility for the commands above as they are copied from the thread.

Always reference http://forum.xda-developers.com/showthread.php?t=2358781 in its entirety for the most up to date and relevant information.

In reality this is the method you would use to install any factory or carrier based RUU to the phone, the only difference being the CID used, remember your original one :)

I hope I've not overstepped what I am allowed to put here and I hope this helps you out.
 
Got a notification for a software update from AT&T today.....perhaps new Android version rollout finally hitting US carriers?

Will need to get to WiFi to confirm the update, but will let ya'll know!
 
jrswizzle said:
Got a notification for a software update from AT&T today.....perhaps new Android version rollout finally hitting US carriers?

Will need to get to WiFi to confirm the update, but will let ya'll know!
Click to expand...

Don't hold your breath. AT&T released a 'maintenance update' a couple days ago, doesn't have 4.2.2.

And if per chance you were lucky enough to get it, I'll personally be furious as my Developer Edition still doesn't have it. That would likely be the last straw for me with HTC.
 
tbayrgs said:
Don't hold your breath. AT&T released a 'maintenance update' a couple days ago, doesn't have 4.2.2.

And if per chance you were lucky enough to get it, I'll personally be furious as my Developer Edition still doesn't have it. That would likely be the last straw for me with HTC.
Click to expand...

Ahh ok - likely the maintenance update then. I haven't had anything updated in a while.

Oh well.
 
tbayrgs said:
Don't hold your breath. AT&T released a 'maintenance update' a couple days ago, doesn't have 4.2.2.

And if per chance you were lucky enough to get it, I'll personally be furious as my Developer Edition still doesn't have it. That would likely be the last straw for me with HTC.
Click to expand...

This is couch's cue.
 
AutoUnion39 said:
This is couch's cue.
Click to expand...

Well, can't disagree with him on this point. HTC is rolling out the update in phases--fine, not happy about it but it seems to be following when the device was originally available for sale. I still think it's taking far too long.

Now if ANY of the carrier branded phones in the USA get it before the Developer's Edition, HTC can add me to the 'former customer' list as this was one of the selling points of this version of the device--updates before everyone else.
 
The worst part for you guys is not waiting for 4.2, is 4.3 and KLP.

Will HTC release 4.3 at all? Will they release KLP a year later because they will unite efforts with their new One beginning next year?

Too many doubts.
 
Sensamic said:
The worst part for you guys is not waiting for 4.2, is 4.3 and KLP.

Will HTC release 4.3 at all? Will they release KLP a year later because they will unite efforts with their new One beginning next year?

Too many doubts.
Click to expand...

4.3 shouldn't be too much to worry about, given it was a relatively minor behind-the-scenes update. KLP will be the problem, especially if it's a major overhaul. If it is released around Oct/Nov, then the One will probably be upgraded by this time next year, if the update to Sense 5 for the One X is anything to go by. However from what I've seen of 4.2.2 the One is running as smooth as any phone I've seen, so that should hopefully tide me over until 5.0 appears.

And on that note I'm soon to be a proud owner of the One (price drop on Amazon made the decision for me) - It should be arriving tomorrow.

Can't wait :D
 
Sensamic said:
The worst part for you guys is not waiting for 4.2, is 4.3 and KLP.

Will HTC release 4.3 at all? Will they release KLP a year later because they will unite efforts with their new One beginning next year?

Too many doubts.
Click to expand...

Yeah, I wouldn't be too optimistic about seeing KLP until at least 6 months post release but personally, I don't honestly care because I know with my penchant for trying new phones that there's no chance I'll still be using the HTC One next year, much less six months from now.
 
PerfectDB said:
4.3 shouldn't be too much to worry about, given it was a relatively minor behind-the-scenes update. KLP will be the problem, especially if it's a major overhaul. If it is released around Oct/Nov, then the One will probably be upgraded by this time next year, if the update to Sense 5 for the One X is anything to go by. However from what I've seen of 4.2.2 the One is running as smooth as any phone I've seen, so that should hopefully tide me over until 5.0 appears.

And on that note I'm soon to be a proud owner of the One (price drop on Amazon made the decision for me) - It should be arriving tomorrow.

Can't wait :D
Click to expand...

4.2.2 was a minor update too, yet HTC seems to be taking their sweet time releasing it on their flagship phone in one of the most important markets in the world.
 
tbayrgs said:
Yeah, I wouldn't be too optimistic about seeing KLP until at least 6 months post release but personally, I don't honestly care because I know with my penchant for trying new phones that there's no chance I'll still be using the HTC One next year, much less six months from now.
Click to expand...

Me too. And HTC ain't doing much to keep me around, so...

I turn my sights towards this year's Nexus or next year's Moto X.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back