Related
Pardon my boldness but I have been on this forum now for awhile and been reading and getting alot of very good information on ROOTING.
I have yet to ROOT my Hero and I am really in a struggle to do so because it seems to me that those of you, for the most part, who have ROOTED your phones are the same people who are having all the problems with this and that appearently because of the ROOT. I mean that folks with stock Hero's very rarely say that something isn't working as it should. App's withstanding. I refer to stock features only.
Reading the problems is the Who's Who of why I think it not a wise choice for me to ROOT at this time.
Anyway, I had my say and my stock Hero works just fine with its 1800 from Mugen. Remember, its a phone, not a pc even tho it share's some pc features.
Thanks for listening...and for a great place to learn.
The key piece of information to remember is that rooting does't cause the issues we experience. It's the custom ROMs and hacks we install that cause problems
I think most everyone here remembers that we're doing these things at our own risk.
As for the OP, if you don't feel a desire for the features available after rooting or flashing a custom ROM, that's cool. It's not for everyone.
Rooting, flashing, hacking... it's for tinkerers. People who like to find out why something does or doesn't work and then find a fix for it.
I would place a bet on this:
The people who don't have root or don't want to root, and they rarely post their issues in comparision with those who have rooted.
Yes, Most of the issues you see here are self inflicted, but it's what we do. We like a challenge/problem, it gives us something to do. Another reason to stay up till 3 in the morning to find out WHY it's jacked up.
If your issues are so bad, RUU and stick with stock (A whole new set of issues).
We mention our problems so that developers can try and fix them for the next release. In all honesty, Ive had one 1 problem, that was when I installed AOSP 1.6, which btw is/will not supported by our phone officially, I got the dreaded SMS issue that SOME people are experiencing.
Well yea many people post about issues who are rooted, but it is caused by other things they are doing that require it. Simply rooting your device shouldn't cause anything to go wrong.
Roms and other things that require root access tend to be beta, and even if they are not beta they are created by people, and not everything will be perfect.
It is pretty hard to permakill your hero compared to other devices. The only way I know of using the software is through flashing the radio, or messing with ESID and stuff like that.
Which you aren't supposed to do .
Yo Is_907
Not quite the 1st reply I was expecting but a very nice understanding instead. You SIR are a gentlemen and I thank you.
Yes, at the ripe old age of 62 I do believe ROOTing and all that goes with it are for you younger folks who have grown up with computers and like devices. I do tinker somewhat and in fact, my wife and I host a private FREE World of Warcraft ( WOW )server. Been hosting online game servers for about 9 years now and we love it.
Once again, thanks and as you said, I probably need alot more schooling before I would attempt a ROOT. My only problem is AWAKE time, its really high even tho I have removed those apps I can remove to help that situation. Hopefully, 2.1 will help us Non Roots somewhat but if not, then I will strongly consider ROOTing. As long as I know there are people like yourself to help us old dudes.
Thanks again Is_907, and to the rest of you who voiced your opinions, Thanks. All good points and even more reason to consider ROOTing.
rdisanza said:
Pardon my boldness but I have been on this forum now for awhile and been reading and getting alot of very good information on ROOTING.
I have yet to ROOT my Hero and I am really in a struggle to do so because it seems to me that those of you, for the most part, who have ROOTED your phones are the same people who are having all the problems with this and that appearently because of the ROOT. I mean that folks with stock Hero's very rarely say that something isn't working as it should. App's withstanding. I refer to stock features only.
Reading the problems is the Who's Who of why I think it not a wise choice for me to ROOT at this time.
Anyway, I had my say and my stock Hero works just fine with its 1800 from Mugen. Remember, its a phone, not a pc even tho it share's some pc features.
Thanks for listening...and for a great place to learn.
Click to expand...
Click to collapse
There's not an issue with rooting in and of itself. Take me for instance. I've had some problems with my phone:
1. Apps2SD didn't work...but that was part of a ROM that was being beta tested.
2. Kernel locked up...that was due to an invalid setting I put into the kernel I was building.
3. Lost CPU kernel control...this is something I'm doing wrong in the kernel I am building. I simply restore a control file from a previous build and recompile.
These are things that were expected in testing and needed to be fixed or that I inflicted on my own.
I have a friend who has rooted his Hero, but hasn't applied any of the custom ROMs to his phone (although he has installed applications that require root). He's never had an issue with the phone.
It really depends on what you use it for.
rdisanza said:
Yo Is_907
Not quite the 1st reply I was expecting but a very nice understanding instead. You SIR are a gentlemen and I thank you.
Yes, at the ripe old age of 62 I do believe ROOTing and all that goes with it are for you younger folks who have grown up with computers and like devices. I do tinker somewhat and in fact, my wife and I host a private FREE World of Warcraft ( WOW )server. Been hosting online game servers for about 9 years now and we love it.
Once again, thanks and as you said, I probably need alot more schooling before I would attempt a ROOT. My only problem is AWAKE time, its really high even tho I have removed those apps I can remove to help that situation. Hopefully, 2.1 will help us Non Roots somewhat but if not, then I will strongly consider ROOTing. As long as I know there are people like yourself to help us old dudes.
Thanks again Is_907, and to the rest of you who voiced your opinions, Thanks. All good points and even more reason to consider ROOTing.
Click to expand...
Click to collapse
Rooting really isn't too difficult. Just look at the intelligence level of some of the people who have managed to root (before anyone flames me, I'm mainly talking about myself)!
I believe it's entirely possible to root your phone, install a custom ROM that is close to stock, and then live a happy life without ever messing with it again.... Sorry, I couldn't keep a straight face!
Kidding aside, did you update your phone with the Sprint Maintenance Release? You mentioned "awake time" which this patch will fix without the need to root.
Honestly, I mess around with my Hero so much that I am often startled when it rings and I'm reminded that it's a phone.
watzone69 said:
Rooting really isn't too difficult. Just look at the intelligence level of some of the people who have managed to root (before anyone flames me, I'm mainly talking about myself)!
I believe it's entirely possible to root your phone, install a custom ROM that is close to stock, and then live a happy life without ever messing with it again.... Sorry, I couldn't keep a straight face!
Kidding aside, did you update your phone with the Sprint Maintenance Release? You mentioned "awake time" which this patch will fix without the need to root.
Honestly, I mess around with my Hero so much that I am often startled when it rings and I'm reminded that it's a phone.
Click to expand...
Click to collapse
lol I second this my wife hates the fact the I have tis really nice phone and when ever I am at home she can never get ahold of because I am always doing something to it.
to the OP rooting really is not hard I mean if you are hosting a MMORPG server you could surely do it, but if your happy with your phone as is then that is really awesome. I myself when I first got my phone knew ABSOLUTLY NOTHING about android or linux or what in the work a kernel or apk was but with the help of the great community here I have learned so much. Dont get me wrong I am no where near where a lot of the guys on here are but I am learning and helping as much as I can just as those that helped me (i mean I am just happy that I think I could go through and make a theme now lol). if you are happy with the phone as is the only benifit of rooting I would bring up is being able to make backups of everything that way if anything does happen to the phone then you dont have to go trough and redownload apps and set everyhting back up again.
if you do decide to make the leap there are many people here more than willing to help.
Its not the Intelligence thing, I know I can ROOT if I wish either with PreKitchen or the cmd prompt. And YES, I do host a game server and can write script so its not that I don't have the know-how. Its just me, I really don't need to be ROOT'd but the thought of having full control is the thing. Guess you could say I am a Control Freak. If you have ever played online and been part of the game Administration, you know what I mean.
Thanks, I haven't said NO, still just wondering is all.
Regards,
rdisanza said:
Its not the Intelligence thing, I know I can ROOT if I wish either with PreKitchen or the cmd prompt. And YES, I do host a game server and can write script so its not that I don't have the know-how. Its just me, I really don't need to be ROOT'd but the thought of having full control is the thing. Guess you could say I am a Control Freak. If you have ever played online and been part of the game Administration, you know what I mean.
Thanks, I haven't said NO, still just wondering is all.
Regards,
Click to expand...
Click to collapse
oh please understand I wasnt trying to insult you at all, and yes I understand the control thing. thats why I rooted originally but then I flashed my first rom and got addicted. Now if im not changing my phone in some way on a pretty much daily basis I start to get the DT's lol.
No insult taken my friend. The DT's, lol WORD!
Rooting is actually deceptively easy. All you have to do is download fresh pre-kitchen and hit root. Even from the command prompt (which i used because i don't have access to a windows machine) is still easy. This is literally ALL you have to do: (These are instructions for macs, basically same on windows)
Step 1. Download Android SDK from android.com
Step 2. Download Amon Ra's Sprint Hero Recovery Image
Step 3. Copy the recovery image to root of phone's SD card (name it recovery.img)
Step 4. Open command prompt and navigate to tools folder of the SDK \AndroidSDK\Tools
Step 5. Type the following code with phone plugged in via USB:
Code:
adb shell
#cd /sdcard
#flash_image recovery recovery.img
#reboot recovery
Your phone should then boot into a screen with green text on a black background. Success! You have rooted. (Note: you will need to get the version of Stock ROM with SU for root access.)
Before you reboot the phone go into Backup/Restore>Nandroid Backup Then hit Home to confirm. This will say Performing backup...... and then say Backup complete! You may now hit Reboot System Now and it will start up like normal. Then, mount the SD card, and copy the Nandroid folder to your computer. This is your stock ROM, if anything goes wrong copy this back to the phone and restore it. You may boot into recovery by starting up the phone while holding the home button. Hope this helped.
HeroMeng said:
Rooting is actually deceptively easy. All you have to do is download fresh pre-kitchen and hit root. Even from the command prompt (which i used because i don't have access to a windows machine) is still easy. This is literally ALL you have to do: (These are instructions for macs, basically same on windows)
Step 1. Download Android SDK from android.com
Step 2. Download Amon Ra's Sprint Hero Recovery Image
Step 3. Copy the recovery image to root of phone's SD card (name it recovery.img)
Step 4. Open command prompt and navigate to tools folder of the SDK \AndroidSDK\Tools
Step 5. Type the following code with phone plugged in via USB:
Code:
adb shell
#cd /sdcard
#flash_image recovery recovery.img
#reboot recovery
Your phone should then boot into a screen with green text on a black background. Success! You have rooted. (Note: you will need to get the version of Stock ROM with SU for root access.)
Before you reboot the phone go into Backup/Restore>Nandroid Backup Then hit Home to confirm. This will say Performing backup...... and then say Backup complete! You may now hit Reboot System Now and it will start up like normal. Then, mount the SD card, and copy the Nandroid folder to your computer. This is your stock ROM, if anything goes wrong copy this back to the phone and restore it. You may boot into recovery by starting up the phone while holding the home button. Hope this helped.
Click to expand...
Click to collapse
You don't have to push the asroot2 exploit!?!?!!?
Kcarpenter said:
You don't have to push the asroot2 exploit!?!?!!?
Click to expand...
Click to collapse
Not if you're flashing a custom rom that already has it.
You have to have root access to initially install the custom recovery image. So you DO need to push the asroot2 exploit & run it on the phone.
gu1dry said:
You have to have root access to initially install the custom recovery image. So you DO need to push the asroot2 exploit & run it on the phone.
Click to expand...
Click to collapse
I never had to do that when I rooted. Flashed MCR right after I rooted using above method and it worked fine.
Yes the asroot2 exploit is was allows to root the phone, so therefore you had run the exploit initially.
I guess I missed this over the weekend and I am looking for the original install that I dont need to have root for. I have been reading over the threads here and in the Dev forum and I am not seeing any links to the download for Non-Root users.
I am to much of a ***** to root my phone. i spent way to much cash on it and i am too worried something will go wrong.
So here is want I am asing for
A. The original non root install with instructions on how to do it
or
B. Someone to help walk me through the process of rooting and getting FroYo 2.2 set up on my phone.
Please shoot me a PM if your willing to help out. I am just way to worried if I do this without someone who knows what they are doing I am going to screw up my phone, and my wife would never let me buy another one ...lol
Can somsone help out a fellow Dev, thanks
Sorry I can't post links but here you go
androidandme.com/2010/05/news/how-to-manually-install-android-2-2-on-your-nexus-one/
Ya just found it buried in a thread
Thanks
See if I would have spent another 10 minutes searching I would have found it without having to ask ...lol
Got to remember to scan threads for 30 minutes not 20 before asking ...lol
Or use this: http://forum.xda-developers.com/showthread.php?p=6043779#post6043779
(Or the Root/2.2 links in my sig.)
Okay, I'll give you the general idea, as I understand it:
The FRF50 ROM that was leaked from Google is exclusively for ERE27 Builds only. Unless that is the native build on your phone, you will not be able to apply that as is.
Paul O'Brien, over at Modaco, repacked it so that it can be flashed with any current ROMs. Though he's said that there are no conditions, there in fact are a few stipulations to be aware of.
-If you have never unlocked your bootloader, you won't be able to flash anything at all. Something to think about. There's a few threads here dedicated to this topic alone. It voids your warranty so that is why some people are holding off and waiting for the official OTA update to be released.
-Though it's true that you don't have to be rooted to flash Paul's repack, unless you have ERE27 stock, you need to flash using one of the custom recovery images. And in order to flash your recovery.img, you need to be rooted. So you need to have had rooted before.
So the steps, from stock, would be:
(1) Unlock your bootloader, via flashboot.
(2) Flash superuser to your boot.img (aka rooting)
(3) Flash a custom recovery to recovery.img (I use RA)
(4) Flash Paul's FRF50 repack using said recovery image.
I'm sorry I can't post the links to the relavant posts, but my status as a member doesn't allow me to. Hope this helped clear some things up for you.
Paul22000 said:
Or use this: http://forum.xda-developers.com/showthread.php?p=6043779#post6043779
(Or the Root/2.2 links in my sig.)
Click to expand...
Click to collapse
Paul, is that Avatar a picture of YOU?
OMG theres a search feature!!!
Really OMG I didnt know this!
I guess me saying I searched threads and the site for 20 minutes was something you missed.
But thanks to all who actually decided to help and not be another one of these "USE SEARCH" people.
I respect the work you do for us here Paul, but come on man. Read before making a post like that ....lol
attn1 said:
Paul, is that Avatar a picture of YOU?
Click to expand...
Click to collapse
All I wil say is:
λ
LOL ...........
you don't need to root to install froyo and you don't need to hook up your nexus to a pc. my method is pretty simple and it works.
edit: I shouldn't say it's my method. Its actully a backdoor to installing froyo.
theletterj said:
Okay, I'll give you the general idea, as I understand it:
The FRF50 ROM that was leaked from Google is exclusively for ERE27 Builds only. Unless that is the native build on your phone, you will not be able to apply that as is.
Paul O'Brien, over at Modaco, repacked it so that it can be flashed with any current ROMs. Though he's said that there are no conditions, there in fact are a few stipulations to be aware of.
-If you have never unlocked your bootloader, you won't be able to flash anything at all. Something to think about. There's a few threads here dedicated to this topic alone. It voids your warranty so that is why some people are holding off and waiting for the official OTA update to be released.
-Though it's true that you don't have to be rooted to flash Paul's repack, unless you have ERE27 stock, you need to flash using one of the custom recovery images. And in order to flash your recovery.img, you need to be rooted. So you need to have had rooted before.
So the steps, from stock, would be:
(1) Unlock your bootloader, via flashboot.
(2) Flash superuser to your boot.img (aka rooting)
(3) Flash a custom recovery to recovery.img (I use RA)
(4) Flash Paul's FRF50 repack using said recovery image.
I'm sorry I can't post the links to the relavant posts, but my status as a member doesn't allow me to. Hope this helped clear some things up for you.
Click to expand...
Click to collapse
Okay, there's a lot of good info out there mixed in with a lot of mis-information.
Your steps will work BUT:
I prefer to do it this way:
Unlock the boot loader via fastboot
Flash Amon_RA 170 recovery for Nexus One
Do a nandroid Backup
Flash your ROM of choice (Modaco's FROYO in this case)
If you are running stock recovery, you CAN flash, but only Google's updates. If you have a T-mobile N1 this may work for you without unlocking the bootloader by flashing the Google Froyo Release with the stock recovery:
Google Froyo Release
You must be on release ERE27 for this to work.
Here's a link to some instructions on how to use the stock recovery program:
jp_macaroni's thread
I suspect that since most people have already rooted or cannot get to ERE27, Paul's guide is the best way to go for them.
If you are running a custom recovery, you can flash custom updates, but NOT Google's updates intended for any stock phone/firmware level.
You don't need to root (root access) to the current ROM before flashing a custom ROM. You only need to unlock the bootloader and install a custom recovery image.
jcohenlv said:
OMG theres a search feature!!!
Really OMG I didnt know this!
I guess me saying I searched threads and the site for 20 minutes was something you missed.
But thanks to all who actually decided to help and not be another one of these "USE SEARCH" people.
I respect the work you do for us here Paul, but come on man. Read before making a post like that ....lol
Click to expand...
Click to collapse
Yeah you know, everyone is new once. It's easy to sort out the tripe from the real deal when you've been around the block once or twice. Paul is doing his best to be helpful and not cause more confusion.
The problem isn't that people can't search so much as it is that searches yield too much conflicting information, so lets not jump down people's throats when they ask for a point of clarification. Instead, lets start asking moderators to sticky good info and pulling redundant/bad info so that searches are more meaningful. The number of new threads in here because of the Froyo release is mind numbingly high. Let's all try to exercise some patience.
attn1 said:
Okay, there's a lot of good info out there mixed in with a lot of mis-information.
Your steps will work BUT:
I prefer to do it this way:
Unlock the boot loader via fastboot
Flash Amon_RA 170 recovery for Nexus One
Do a Nadroid Backup
Flash your ROM of choice (Modaco's FROYO in this case)
If you are running stock recovery, you CAN flash, but only Google's updates. If you have a T-mobile N1 this may work for you without unlocking the bootloader:
If you are running a custom recovery, you can flash custom updates, but NOT Google's updates intended for any stock phone/firmware level.
You don't need to root (root access) to the current ROM before flashing a custom ROM. You only need to unlock the bootloader and install a custom recovery image.
Click to expand...
Click to collapse
I'm not disagreeing with you, but as far as I know, yes, you do have to root in order to flash Amon_RA Recovery to your phone. If that's not correct, I apologize for spreading misinformation.
theletterj said:
I'm not disagreeing with you, but as far as I know, yes, you do have to root in order to flash Amon_RA Recovery to your phone. If that's not correct, I apologize for spreading misinformation.
Click to expand...
Click to collapse
You only need to unlock the bootloader. You do not need root.
Unlocking the boot loader allows installation of an alternate recovery, which allows you to install custom software to the existing ROM or to install a custom ROM. It's updating the ROM that allows you to gain root access, not unlocking the boot loader. It goes in this order:
> Unlock boot loader (void warranty - still not rooted)
> Install custom recovery
> nandroid backup (recommended/optional)
> Update ROM (for root access - or not)
The original instructions worked perfect
All that was needed was to change the name to update.zip load it on the root of the SD card then but the phone in bootloader and load recovery from SD.
Took about 5 minutes.
Once the phone came up it did a few things and took about another 5 minutes to chill on the processes then I was able to use the phone without any problems.
So for those interested here are the exact steps:
This is for NON Rooted T-Mobile Version!!!!
To manually install Android 2.2 on the Nexus One, perform the following steps:
1. Download the official Android 2.2 firmware for the Nexus One.
2. Copy the file to your microSD card and name it update.zip (newb warning: not update.zip.zip)
3. Power off your phone.
4. Hold down the VOLUME DOWN button and power it back on.
5. The phone will now search for files like PB00IMG.zip, etc. This is normal. Scroll down to recovery (using Volume Down Key) and press the POWER button.
6. When you see the “/!\” symbol, press the POWER button and the Volume Up button at the same time. You should be presented with a menu and one of the options should be “Apply sdcard:update.zip”.
7. Use the trackball to navigate to “apply sdcard:update.zip” and select it.
8. When you see “Install from sdcard complete”, select “reboot system now”.
Wait 5 minutes, phone will reboot once rebooted let the phone sit for about 5 minutes then you are good to go. It couldn't be any easier
Hi there,
I had been umming and arring about rooting and installing a new ROM one of my familys HTC Heroes for some time now and finally after reading lots of "How to's" on lots of different forums I decided to take the plunge and give it a go using the guide on here.
Both my wifes phone and my sons phone are sim unlocked Orange HTC Heros running 2.1-Update 1.
Rooting it was easy. One press of a button and I was there. Its pretty much worked OK and I have sucessfully made three backups of the wifes Hero.
My main query and this is the bit I have not really been able to find much info about despite spending a day trawling through the forums looking for similar queries is this:
Having flashed my recovery image file, the first time I reboot I can get into the recovery mode just fine. From here I can make a backup of the current ROM after which the Hero reboots and goes back into the OS as it should.
If I then shut it down and reboot using the HOME key + POWER option It does not go into the recovery mode. I get the screen with an image of the phone next to a red triangle with an exclamation mark in it.
Using the advice from various forums whilst searching for further advice / hints I have left the phone for up to half an hour but it stays on this screen. The only way to get it out of this screen it to pull the battery.
If I then boot up the phone and reflash the recovery image, I can then get into the recovery mode once again but for ONE BOOT ONLY.
I have tried AmonRA Revcovery v1.7.01. and also the Clockwork Recovery 2.5.0.7 images and both produce the same results. I have tried flashing the images via ROM Manager and also via Android Terminal Emulator
My question is this: Do I have to flash the recovery image EVERY time I want to open the recovery mode or is there something I have missed? At present I have held back from installing a new ROM in case I go past a point of no return where I brick the phone. Neither my wife or son would be too pleased despite my son wanting a better ROM on his.
Apologies for writing "War and Peace" but I wanted to make sure I had covered all I could and hope this is a) not a query already posted elswhere which I have missed b)posted in the right place. Apologies to any forum mods if its not.
Regards
Rhinestone.
hmm look on the unlokr.com or something like that. They use some simple passes and it's the way i did it. the on;y difference is that my phone wasn't blocked on a carrier...
1.there is a program that roots the hero's rom
2.after that i recommend installing clockwork recovery mode (it doesn't need signed zips)
3.if you don't feel safe doing this, i recommend to stop... I know that the 2.1 rom is boring but you can end up with a bricked phone after this...
The official 2.1 update has a script that reflashes the stock recovery every time the phone is shut down.
Hunt about for a modified 2.1 rom, all of them have had that script removed. I'm not a huge fan of sense now, but when I did use it, I found villainrom to be a good 2.1 sense rom.
TheReverend210 said:
The official 2.1 update has a script that reflashes the stock recovery every time the phone is shut down.
Hunt about for a modified 2.1 rom, all of them have had that script removed. I'm not a huge fan of sense now, but when I did use it, I found villainrom to be a good 2.1 sense rom.
Click to expand...
Click to collapse
This, just flash a custom ROM and it will stick.
Hello,
Problem might be with rooting, possible it has not been rooted completely or anything messed up. You can try this for rooting.
http://unrevoked.com/
If you are sure its rooted completely, then check out Superuser apps, if its there, and you are rooted, if not then download terminal emulator and type "su" command, if its doesnt display any error then its rooted.
Other then this,
problem might be with the recovery images you are flashing, download droid explorer its a window application, its has an option of flashing recovery with one click, simply choose recovery image & flash it, clockmod recovery or amonr any of this you can get in xda.
I've got a new A500 and I intend to root it soon, but I would like advice on whether to take the current update 7.014.1 being pushed before I go through the rooting process? It currently shows having 3.2 OS version.
Zoandroid said:
I've got a new A500 and I intend to root it soon, but I would like advice on whether to take the current update 7.014.1 being pushed before I go through the rooting process? It currently shows having 3.2 OS version.
Click to expand...
Click to collapse
Doesn't matter, the only way to root it is by flashing it which wipes it totally clean
timmyDean said:
Doesn't matter, the only way to root it is by flashing it which wipes it totally clean
Click to expand...
Click to collapse
My concern, being still in the middle of researching just how to root the A500, was whether the update would have a similar effect as, for example, the more major update from 3.0 to 3.2, which, as I understand it totally changes the procedure used to achieve root. But if it won't matter one way or the other, I might as well take the update in the interim. I keep hoping to see a more simple 'one-click' style of root made available before I tackle this task. So far I've found something like 3 different ways to root the tablet between this forum and another. But each is a rather involved process.
Thanks!
timmyDean said:
Doesn't matter, the only way to root it is by flashing it which wipes it totally clean
Click to expand...
Click to collapse
I downgraded, rooted, and then flashed the stock ROM without wiping. If going to any other rom, you might need to wipe.
There currently is no way to root a stock 3.2 or later tablet with a simple one click. In the past GingerBreak gave us that ability but since has been plugged. The other thing causing issues is ACER locked the boot loader making it difficult to flash in a new boot image to get to root.
=== 411 on rooting ===
So, if you have a tablet and want to root it then you have to start looking at security holes. This is what the GingerBreak exploit did along with others. But, ACER plugged those holes and as of today, nobody has found anymore.
So, you might look at exploiting an update.zip. These are OTA's that run but they are signed by ACER. So you can take it apart (unzip) and modify it, but you cannot resign it with an ACER Key. Therefore, you have to sign it with your key. Since it is NOT signed by ACER, the ACER recovery will not install it. So, you have to replace the ACER recovery with CWM which will install any update.zip regardless of who signed it. You just need to change the built in recovery by flashing in CWM recovery.
Lastly, you can just change the boot image and add root. This is easy and straight forward to do. This is just like making your own custom update.zip. Once you have your custom boot, you can then just use Nvflash to flash in your custom boot.
Now, fast forward. ACER (can someone please explain to me why?) decided to lock the bootloader thereby not allowing you to replace the recovery, boot, or any other area. Meaning, you cannot use Nvflash anymore without a key.
With the bootloader locked, you can only load new images if you know the key used to lock it. Of course, they use a public and private key combination, and they appear to use the serial number of the USB device as part of the public key making the keys on my tablet unique compared to yours.
With all this said, this ends all the easy simple rooting methods because first, they've plugged all the security holes (which they should do). Secondly, they locked the boot loader making it very difficult for people to just flash in a rooted boot image.
Armed with this, how do you root a 3.2? One way to do it is to get to a version prior to 3.2 loaded that has a security hole or does not have the bootloader locked. You now exploit it and get root. Now, with root access you make a 'backdoor' that only you know about which allows you to get into your tablet as root. With this done, now roll your tablet forward apply all updates. Since you have a 'backdoor' you can always gain root access.
Unfortunately, this gets to be messy or can be more difficult to do than just clicking on a GingerBreak application. However, if you follow the steps posted here in the forum, it's straight forward and easy enough to do. If not, you are going to have to wait for someone to find a hole and build a oneclick application. I wouldn't hold my breath on this, it probably will never happen because everyone is working on ICS.
Lastly, everyone should write to ACER, refuse to buy ACER (or any tablet) that doesn't allow you (AS THE OWNER) to change it. How would you like to buy a Ford to just have Ford lock the lug nuts on the rims so you could NOT put on your custom wheels.
I believe failure to allow owners to unlock these devices will be the downfall to Android. Windows 8 does NOT have such restrictions and businesses are not going to use devices that are locked and cannot be customized for business. Because developers write software they can sell, they'll move to Windows 8 and drop supporting Android and all these goofy flavors and restrictions. Android might be great and everyone hates Microsoft, but software vendors are going to NOT want to support all these devices.
my 2¢
timmyDean said:
There currently is no way to root a stock 3.2 or later tablet with a simple one click. In the past GingerBreak gave us that ability but since has been plugged. The other thing causing issues is ACER locked the boot loader making it difficult to flash in a new boot image to get to root.
=== 411 on rooting ===
So, if you have a tablet and want to root it then you have to start looking at security holes. This is what the GingerBreak exploit did along with others. But, ACER plugged those holes and as of today, nobody has found anymore.
So, you might look at exploiting an update.zip. These are OTA's that run but they are signed by ACER. So you can take it apart (unzip) and modify it, but you cannot resign it with an ACER Key. Therefore, you have to sign it with your key. Since it is NOT signed by ACER, the ACER recovery will not install it. So, you have to replace the ACER recovery with CWM which will install any update.zip regardless of who signed it. You just need to change the built in recovery by flashing in CWM recovery.
Lastly, you can just change the boot image and add root. This is easy and straight forward to do. This is just like making your own custom update.zip. Once you have your custom boot, you can then just use Nvflash to flash in your custom boot.
Now, fast forward. ACER (can someone please explain to me why?) decided to lock the bootloader thereby not allowing you to replace the recovery, boot, or any other area. Meaning, you cannot use Nvflash anymore without a key.
With the bootloader locked, you can only load new images if you know the key used to lock it. Of course, they use a public and private key combination, and they appear to use the serial number of the USB device as part of the public key making the keys on my tablet unique compared to yours.
With all this said, this ends all the easy simple rooting methods because first, they've plugged all the security holes (which they should do). Secondly, they locked the boot loader making it very difficult for people to just flash in a rooted boot image.
Armed with this, how do you root a 3.2? One way to do it is to get to a version prior to 3.2 loaded that has a security hole or does not have the bootloader locked. You now exploit it and get root. Now, with root access you make a 'backdoor' that only you know about which allows you to get into your tablet as root. With this done, now roll your tablet forward apply all updates. Since you have a 'backdoor' you can always gain root access.
Unfortunately, this gets to be messy or can be more difficult to do than just clicking on a GingerBreak application. However, if you follow the steps posted here in the forum, it's straight forward and easy enough to do. If not, you are going to have to wait for someone to find a hole and build a oneclick application. I wouldn't hold my breath on this, it probably will never happen because everyone is working on ICS.
Lastly, everyone should write to ACER, refuse to buy ACER (or any tablet) that doesn't allow you (AS THE OWNER) to change it. How would you like to buy a Ford to just have Ford lock the lug nuts on the rims so you could NOT put on your custom wheels.
I believe failure to allow owners to unlock these devices will be the downfall to Android. Windows 8 does NOT have such restrictions and businesses are not going to use devices that are locked and cannot be customized for business. Because developers write software they can sell, they'll move to Windows 8 and drop supporting Android and all these goofy flavors and restrictions. Android might be great and everyone hates Microsoft, but software vendors are going to NOT want to support all these devices.
my 2¢
Click to expand...
Click to collapse
Hi, and thank you VERY much for posting such a nice explanation, especially in addition to all the work you have done posting your thread rooting 3.2. I understand, and completely agree with your explanation, as well as your position on taking control of what we bought and paid for. I take even stronger offense with this tablet's bootloader being locked than I do on my phones. This is not a discounted phone with a service plan tied to a cell provider. It has WiFi, but " I " am the only one providing its data (it never leaves my home). There is no justification here that I am 'leasing' a provider's technology . It was a gift, so I can't speak to choosing the vendor. But I like your wheel lug analogy.
I've been reading the threads on rooting, and both my Android phones are rooted and ROMed, so I've been around the block a couple times from the rooting aspect. But thus far I have been rather confused as to which route to take with the tablet. I don't want to be limited to using terminal for su access, so I want to 'fully root' the tablet. My goal is to allow apps like Titanium Backup, Root Explorer, and others I use on the phones, as well as having Clockworkmod Recovery, or similar recovery capable of working with nandroid backups. But for now I don't have plans to use a custom ROM. So having rooted stock 3.2 would suffice.
Although I do fully understand the need to research these kinds of things before jumping in, I also know that often times information evolves, and lengthy threads which were once considered current info end up not getting updated during that evolution. This can lead to wasted time reading information which can no longer actually be used . So in the spirit of pursuing the most current info, could you recommend which thread I can use to get the best results while rooting this 3.2.1 OS Tablet with the above goals in mind?
Used Timmydean's method, it is pretty easy as long as you follow his instructions with in the zip file he has made with all the tools you need inside of hat zip file. You root, install super user and busybox then download Acer recover installer and that will install cwm...
http://forum.xda-developers.com/showpost.php?p=20654298&postcount=129
Good luck and thanks again timmydean for this method.
Sent from my A500 using xda premium
Thanks, that sounds like the way to go. I'll head over to the link you provided.
I've got a couple of questions about the zip file at that post. I want to download that to my PC, and will be using ADB from there, right? I have the choice of doing so from either Windows XP SP3, or Windows 7 Home Premium. I read in older threads that many of the problems people had were only when they used XP, but were avoided by using Windows 7 (which was exactly opposite of what people experienced rooting the LG Ally), so it seems that in this case it is desirable to use Win7?
I presume I'll need to install a driver so the PC can 'see' the tablet. Is one provided in the tools, or do I need to download that somewhere?
I used windows 7. Yes the driver is in the zip file. I unzipped the file to a folder on my desktop and went from there.
In the zip there is a folder called usbpcdriver. Run the set up from within the fooder to get your driver... please read the instructions that say read me..
Sent from my A500 using xda premium
Thanks. I intend to read everything I can get my hands on before I actually start this. I definitely don't want any trouble or, heaven forbid, to brick the tablet.
pretty easy i think... good luck and let us know when you get rooted
I'm not finding any actual instructions on the steps to take for this procedure. The readme file in version 3 zip file only talks about "changes" from whatever the original procedure was.
Where can I get the actual instructions for the entire procedure?
Edit: I just downloaded version 2 of the zip file. In that one there is an additional PDF called "Steps". It is a little more detailed, and says at step 20 that "you should now have 3.2 with a SU shell installed". Does the DotNetDetector step actually ROOT the device? That seems simple enough, but it still has no mention of things like installing ADB and the PC driver. I located the actual thread from which the single post was derived (the target of the URL above, where it is suggested I use TimmyDean's procedure). I am now looking through that entire thread to try to sort out where the instructions are.
AHA! Post 119 of that main thread says "Also the instructions and everything you need are in earlier posts.".
It appears this procedure needs an instruction manual written to consolidate all the gathered information. Having a link to only the download zip files isn't telling me the whole picture. I'll try gleaning the thread and see if I can put together all the steps needed from start to finish to make this work. Looks like ROOT ain't happening tonight.
http://www.multiupload.com/SLR6XSV841
---------- Post added at 05:14 AM ---------- Previous post was at 05:11 AM ----------
thats the link to read me file.. I about to jail break an Iphone 4... Wish me luck
I edited the above post while you were replying. I'll check out that link, thanks.
Good luck on jailbreaking the DemonSpawn 4.
http://forum.xda-developers.com/showpost.php?p=20680452&postcount=137
he has updated it again. looks like a few steps where taken out to make it more simpler
good luck man. Iphone is jail broken
OK, so it looks like the file you just sent me a link to is the same one as the "Steps.PDF" file that was released in Version 2. It appears to me that what I need to do is blend the changes (detailed in version 3's readme file) into that original Steps file, to make a single contiguous set of instructions, and then start at the top. I notice it does mention installing the PC driver and ADB.
Do I have this right so far?
rdnkchevy said:
http://forum.xda-developers.com/showpost.php?p=20680452&postcount=137
he has updated it again. looks like a few steps where taken out to make it more simpler
good luck man. Iphone is jail broken
Click to expand...
Click to collapse
That was fast! Wanna do my tablet?
The link you sent just now is to the version 3 zip file posted on 12/25, which is what I had initially downloaded. It does appear he streamlined the procedure, but it is that readme file which leaves out the part about installing the PC driver and ADB in the beginning, and also leaves out the part at the end telling you that you should now have 3.2 with a SU shell installed.
Please understand that I want to be "fully" rooted, not just have the ability to gain an SU prompt in terminal. Will this procedure "fully root" the tablet? I'm confused by what he means saying "SU shell installed".
Yes if you use his v3 file you will be.. you will need to down load acer recovery from the market after you are rooted and then flash clockworkmod.. this should all take you about 30 min if that...
rdnkchevy said:
Yes if you use his v3 file you will be.. you will need to down load acer recovery from the market after you are rooted and then flash clockworkmod.. this should all take you about 30 min if that...
Click to expand...
Click to collapse
OK, thanks!! Rooting went well without incident. I just installed Root Explorer and Titanium Backup, and made a backup to SD of my apps and data. Then installed Acer Recovery Installer, and let it install CWM Recovery. But what is considered the "home" button on the tablet?? Is it the reset button? The only buttons on this thing are the Volume rocker and the Power button. ( I got brave and found out it is the POWER button ).
Edit: To clarify, I meant to ask which button serves as the Home button while you are IN the CWM Recovery environment, not while in the Android OS home screen.
*Now Working for 4.3 Update* Will require an up-to-date install of 4.1.x first and then after re-boot, it will update to 4.3 (read post on next page).
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here https://www.dropbox.com/s/9wbux6a4kn0ndz9/StockRecovery-signed.zip
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
jay_ntwr said:
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here http://www.androidrevolution.nl/downloader/download.php?file=Flash_recovery_2.17.401.1.rar
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
Click to expand...
Click to collapse
I appreciate you writing this up. It seems like I've never been able to find a good solution to installing the OTA updates post-root. That being said, do you have any idea what happened in Step 7 that made it finally work? I just don't understand how doing the same thing over and over finally just worked. I want to try installing an update, but I'm a little nervous to do it. And I don't know how else to make the pesky update notification go away without installing it.
trickinit said:
I appreciate you writing this up. It seems like I've never been able to find a good solution to installing the OTA updates post-root. That being said, do you have any idea what happened in Step 7 that made it finally work? I just don't understand how doing the same thing over and over finally just worked. I want to try installing an update, but I'm a little nervous to do it. And I don't know how else to make the pesky update notification go away without installing it.
Click to expand...
Click to collapse
I really have no idea why Step 7 got so strange. The only thing that gave me a warm fuzzy whatsoever was that others were reporting that it was hanging and they just rebooted the phone over and over until it got all the way through the process. It could have something to do with the stock recovery for all I know--a bug perhaps. Again, it made me nervous and I won't do it again. I only did the write up so folks could see what happens and make a call whether or not they wanted to try it themselves and see the steps all on one page instead of getting stuck like I did and then finding the rest of the steps. That part sucked. At least you'll know what you're getting into though. Good luck one way or the other. Please post up if you do go through with it and what your results are.
Thank you for the info! Does sound like an awful lot of work though
jay_ntwr said:
I really have no idea why Step 7 got so strange. The only thing that gave me a warm fuzzy whatsoever was that others were reporting that it was hanging and they just rebooted the phone over and over until it got all the way through the process. It could have something to do with the stock recovery for all I know--a bug perhaps. Again, it made me nervous and I won't do it again. I only did the write up so folks could see what happens and make a call whether or not they wanted to try it themselves and see the steps all on one page instead of getting stuck like I did and then finding the rest of the steps. That part sucked. At least you'll know what you're getting into though. Good luck one way or the other. Please post up if you do go through with it and what your results are.
Click to expand...
Click to collapse
I'm thinking I'll give it a go. I'll do a nandroid backup and store it on my pc. Worst case scenario, I'll just start over from scratch, re-root, and restore my backup. I'll make sure to report my results.
I just makes me wonder why bother using the OTA update if you already went through rooting and flashing custom recovery? It's just one step more to flash the custom ROM and at least you will get constant updates with the developer who created the custom ROM. To me it seems like you either stay stock if you want OTA updates or go the whole hog and use custom ROMs. Just my 2 cents.
shadowboy23 said:
I just makes me wonder why bother using the OTA update if you already went through rooting and flashing custom recovery?
Click to expand...
Click to collapse
Well, in my case, I purchased the Dev edition straight from HTC so I automatically have a de-bloated OS from HTC instead of the ATT ROM that I would have gotten had I purchased the phone from the ATT Store. In that case, I'd no question have a custom ROM from the forum. I just didn't see the need this time around. I would have left the stock recovery, but I do like to make backups so ClockworkMod is something I can't live without. I suppose there are others in that same boat but they are probably few and far between. Really, I just hate to update my ROM since the phone is working how I want at the moment. It's hard to justify just blowing away a functioning OS, setting up everything again, etc. but I may do it again if the OTAs come frequently and/or the process is as strange as it was this past go around.
jay_ntwr said:
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here http://www.androidrevolution.nl/downloader/download.php?file=Flash_recovery_2.17.401.1.rar
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
Click to expand...
Click to collapse
hi,
one question. this recovery.img i also can use for my htc one 802w? i use the original rom (4.1.2) on my htc one. i make s-off over htcdev.com install cwm802w.img . i become the info the system update to 4.2.2 is available but the phone cant install the update.
any people like help me?
best regards,
ps: sorry for my bad english
Does sound like an awful lot of work though
greengoose_at said:
hi,
one question. this recovery.img i also can use for my htc one 802w? i use the original rom (4.1.2) on my htc one. i make s-off over htcdev.com install cwm802w.img . i become the info the system update to 4.2.2 is available but the phone cant install the update.
any people like help me?
best regards,
ps: sorry for my bad english
Click to expand...
Click to collapse
Just find a stock recovery for 802w, flash it to your phone and you should be fine to to OTA. The original post didn't mention if he's using 802w. If he's not, then the recovery.img can't be used for 802w.
How to get s_off , supercid 11111111
and return to s_on with supercid ?please tell me quickly
Thanks for all friends
Sent from my HTC One using xda premium
Sent from my HTC One using xda premium
I haven't been able to get this to work. I flashed back to the stock recovery, but when I attempt to install the update it gets about half way through before rebooting. It goes back into recovery, starts installing again, but then stops and just shows a red triangle with an exclamation mark. I can get the phone to reboot by holding the power button for 10 seconds, which boots it up normally. When it gets up and running, it's like nothing ever happened, but then the update notification reappears.
trickinit said:
I haven't been able to get this to work. I flashed back to the stock recovery, but when I attempt to install the update it gets about half way through before rebooting. It goes back into recovery, starts installing again, but then stops and just shows a red triangle with an exclamation mark. I can get the phone to reboot by holding the power button for 10 seconds, which boots it up normally. When it gets up and running, it's like nothing ever happened, but then the update notification reappears.
Click to expand...
Click to collapse
I'm experiencing the same thing, can't seem to find anything about it...
With the new 4.3 rolling out on the Dev editions, I decided it was time to try this again. What I found was I had to update to a something prior to the new 4.3. In other words, it was still one of the 1.29 streams that updated first and did just like the last time I did this. The thing stopped, locked up, had to hold the power button down, locked up again, reset again, then it was fine. As soon as the phone booted, the 4.3 update was available and I installed that without any issues. So, the method above still works and even with the weirdness I felt a little better this go around.
Good luck.
sunnyyen said:
Just find a stock recovery for 802w, flash it to your phone and you should be fine to to OTA. The original post didn't mention if he's using 802w. If he's not, then the recovery.img can't be used for 802w.
Click to expand...
Click to collapse
I haven't really checked this thread in weeks. I'm not sure what an 802w is. If you can clarify, I'll check and post.
Totally ran just fine
I had to as stated roll back to the attached recovery, did that with fastboot and no problems, then restarted the phone, then had it start the OTA update, then read around debating if I want CWM or TeamWin, but before I notice, the progress bar got up past half way. Looked away for what must've been less than 5 minutes until it vibrated and was restarting itself. It restarted again, and then it loaded and updated all the apps... Seemed like the smoothest rooted update I've ever done, no forced restarting or anything!
I just bought my HTC One last friday, and I think I screwed up things a little bit, because the first thing I did after I charged it, was updating everything to 4.3, before unlocking the bootloader, getting s-off and before rooting the phone. So I ended up with the latest 4.3 on my phone, but it was a pain in the ass to root it properly. I was able to unlock the bootloader, but something must be different with the way 4.3 treats the internal storage distribution, because I was only able to get root, using TWRP and the latest version of SuperSu, but I wasn´t able to install Busybox.
It's a little bit weird, because although I was able to use Titaniumbackup to install some apps, apps like OTA Rootkeeper don't work properly. I also lost the stock calculator, flashlight and voice recorder, but I was able to install older versions again.
I think the only thing I regret is not getting s-off first, but I think this will only mean that I will have to wait for a revone update, or I will have to flash the boot.img after flashing a custom rom as I always did with my One X.
jay_ntwr said:
I haven't really checked this thread in weeks. I'm not sure what an 802w is. If you can clarify, I'll check and post.
Click to expand...
Click to collapse
802w is Chinese dual sim version with different radio frequency
Sent from my HTC One dual sim using xda app-developers app
deepforest said:
802w is Chinese dual sim version with different radio frequency
Sent from my HTC One dual sim using xda app-developers app
Click to expand...
Click to collapse
That is not the one I have then.
I have a rooted HTC one with stock rom. I relock the bootloader and I also have stock recovery.
I am on 4.19.401.5 version.
So, will it be possible for me to have new OTA update including Sense 6?
Should I install the missing applications also, like calculator and flashlight?