Related
I did a PaSSIMG FRG33 version, but I can not root with universal androot also can not return to the version of PASSIMG FRF91, indicates that it is old version. Anyone know?
As it stands, if you want root you're back to having to unlock the bootloader.
You could try: http://forum.xda-developers.com/showthread.php?t=726258 and seeing if you can revert to FRF91 afterwards.
Try?
But someone made with good results?
You should have rooted FRF91, installed a custom recovery, and then used an update.zip format of FRG33 to update to update the system and boot.
kam187 said:
You should have rooted FRF91, installed a custom recovery, and then used an update.zip format of FRG33 to update to update the system and boot.
Click to expand...
Click to collapse
No work recovery with update.zip. Android exclamation!
Also, i can not install passimg frf91, indicat that is a old version
Androith said:
No work recovery with update.zip. Android exclamation!
Also, i can not install passimg frf91, indicat that is a old version
Click to expand...
Click to collapse
Android exclamation is STOCK recovery. Kam is saying "custom recovery" like Clockworks or RA.
Ok,
I got it, but unlocking fastboot to install the superboot. Now I have total control
Now we have to wait to close lock
Thanks!!
Which version of superboot should we be using to root this frg33?
The superboot FRF91
http://www.mediafire.com/?4nnez0uddqk519r
Thanks a lot. I opted not to wait for a new 1-click version. Unlocked the bootloader by cmd prompt. It was weird though. I thought when I was reading about superboot that all you had to do was dbl-click it from windows, but I ended up having to run it for cmd prompt, too. Either way, I'm rooted now. My only remaining question has to do with the custom recovery stuff. I flashed the "latest clockwork recovery" in ROM Manager. Then I flashed the modaco rooted/deodexed/busybox/etc. version of frg33. Is that all I need for my phone to be "safe" at this point? I guess ROM manager let's me flash just about any of the custom ROMS, but if one hangs on load, I just wanna make sure everything is restoreable.
BTW....Android clearly has the best and most helpful community of users that I have ever seen!!!
makelegs,
Glad you got it all worked out and are truely unlocked and rooted. As long as you nandroid, you are safe on what ever yoy wan to do. The dreaded, botched radio flash is probably the only way to get hurt. At least that is my understanding.
That's the funny thing.... I am completely confused about "nandroid." I can't figure out if nandroid is a general concept or something very specific. I have a couple of complete backups performed with clockwork, but nowhere in my "recovery" area have I seen the word NANDROID. So I'm pretty sure, at this point, that if the fit hits the shan I have a plan-b, but nobody ever says "be sure to 'some other kind of' backup." They always say "be sure to nandroid." Am I taking this too literally??? or have I overlooked a step in this process?
I even paid for the premium Rom Manager upgrade so that I could try out different ROM's, but I have this sneaky suspicion that I oughta get closure on the whole "nandroid" thing before I get too carried away.
You've been a lotta help.
makelegs said:
That's the funny thing.... I am completely confused about "nandroid." I can't figure out if nandroid is a general concept or something very specific. I have a couple of complete backups performed with clockwork, but nowhere in my "recovery" area have I seen the word NANDROID. So I'm pretty sure, at this point, that if the fit hits the shan I have a plan-b, but nobody ever says "be sure to 'some other kind of' backup." They always say "be sure to nandroid." Am I taking this too literally??? or have I overlooked a step in this process?
I even paid for the premium Rom Manager upgrade so that I could try out different ROM's, but I have this sneaky suspicion that I oughta get closure on the whole "nandroid" thing before I get too carried away.
You've been a lotta help.
Click to expand...
Click to collapse
Can't speak for Clockwork but on Anom the backup goes in /sdcard/nandroid/DEVICEID/dated-subdir
Each time you make a backup using nandroid, it's a new directory.
And you can NOT restore a nandroid made from a different recovery from what I've read. If you make it with Clockwork you gotta restore it with Clockwork.
makelegs,
It has become a general term with the advent of Rom Manager/ClockworkMod. If you look at the top of the Clockwork screen when in recovery, it say nandroid. The term generally means a full image backup of your phone as opposed to just backing up apps/data. In the nandroid the OS and all else is backed up. So, I wouldn't give it a second thought.
What khaytsus said is the only important thing. Restore thru whichever recovery you backed up with. Clockwork to Clockwork or Amon to Amon.
Amon is put into the nandroid file on your sd and Clockwork is put into Rom Manager under Backups. Although, you can get to them a couple different ways in Clockwork. Thru Install Rom From SD Card or Manage and Restore Backups. Also by booting into Clockwork Recovery. You probably already know that if you use Clockwork.
Ken
Is it actually probable that 1 click might be made to work for 33? It doesn't seem like there are many other users with stock/33 like myself. I feel like a horses ass for flashing it and screwing up my protected apps. All through the incremental updates that led us from 2.1 to froyo went thru easily with no paid apps issues so I didn't have my guard up for this one. (Unless they all had a modded fingerprint status which I starting to think I may remember them having, whatever, this is a bummer...)
Maybe it will be updated, but the folks on frg22 (i think) have been waiting even longer. I was just too busy and OCD to wait it out.
It was probably only ever a matter of time before I went the unlocked bootloader/root route. This was just the catalyst for me. I learned an awful lot in the process. Alas, my phone is back to "normal", but running modaco's rooted/deod/busy/frf91 finger/etc... version of FRG33. And I now realize that if I had just flashed the clockwork recovery to begin with, when I was 1-click rooted on frf91, then this whole thing would've been substantially less of a PITA for me.
Good luck!
FRG33
I got caught out i had 1 click root with cm6
But then installed FRG33 not realising i would lose root if i reverted to it after i had done a backup of cm6 .
I had a lot of things including adfree working on FRG33 prior to recovery .
I think the universal androot app uses the "exploid" method which indeed was patched in FRG versions. But I believe someone on the forum reported that FRG22 or FRG33 was still vulnerable to the "rageagainstthecage" root exploit.
Can someone here verify whether FRG83 is still rootable using "rageagainstthecage"?
You can try the instructions for rooting FRG33 in the Wiki on FRG83.
I have tried booting into recovery with clockworkmod and also stock recovery many times. I have disabled fastboot and each time I have tried I get the picture of the phone and the triangle.Once again I have fastboot turned off. I have searched the threads and tried what ever I found and nothing has worked. I am wanting to do a nanroid backup and I am getting more and more discouraged each time I try and it fails. I guess maybe its time to send it back as I have 4 more days left on buyers remorse. Thought I would try to solicit some help before making the decision to send it back. I have a Nexus One and a Vibrant and have never had this problem with either one of them. I have tried it with the Visionary temp root applied and with it off and does not make a difference. I have not applied the perma root yet. Any and all help is and will be greatly appreciated
I had a similar issue. I would do the full permroot, then flash clockwork recovery through fastboot.
Thanks so much for the swift reply. I am not sure if I am going to keep this phone so I am not wanting to permaroot at this time. Is there not a way to flash recovery without doing permaroot? i read where Paul Obrien states in his thread for permaroot that one should do nanroid backup before doing permaroot. This leaves me very confused. How in the world do you do that???lol It looks like the decison to send it back or keep it is being made for me. I have never called CS and asked for help to flash recovery as I feel that they would not respond favorably and want to know why I want to flash recovery, but that could be wrong also. Help!!!!!!!!!!!
Edit:Just got off the phone with tech support and they state that recovery cannot be accessed as a safety feature. Not sure I believe them as he did not know what fast boot was or what a nanroid backup is. He said the little phone and the triangle with the exclamation is the bootloader screen and no other screen can be accessed after selecting recovery. Any and all help and info is GREATLY appreciated.!!!
Help PLEASE
tenbeau said:
Help PLEASE
Click to expand...
Click to collapse
I'm not sure how far you'll be able to get, but I've been in your position before, so anything I can suggest to help-
http://forum.xda-developers.com/showthread.php?t=834225
If you follow it EXACTLY it should work out- you might have to try a few times- I did, he also includes the script to return it to S=on. The terminal emulator worked best for me
Once you get permroot you can get clockwork on there.
I don't understand what you're trying to do. Are you trying to boot into CWM recovery or the stock recovery? The way I understand it is that once you flash CWM, it overwrites the stock recovery. And furthermore, if you're trying to make a nandroid, you will need to boot into CWM. If you need the stock recovery back, someone posted a link to reflash it back onto the phone.
Follow the above instructions on how to turn s-on. Itz actually easy. Jes download the files, type in 2 commands in terminal emulator, you are now perm rooted with s-off. That easy. If you want to unroot, go to visionary and click on unroot, simple and works like a charm
Sent from my HTC Glacier using XDA App
I just tried flashing the Gingerbreadime.zip and followed the directions to the letter and I experienced my first soft brick. The phone went into a boot loop at the mytouch screen. Luckily I was able to go into Recovery and restored the backup I had made after rooting and turning s=off. It appears to have restored okay as I still have root etc. Does anyone have any idea how or why this happened ? This zip was posted in Droid-Life and was advertised as good for all android 2.2 devices. I have never used adb but have it set up on my phone so I guess I had better get more familiar with it. I have flashed my Vibrant numerous times using Odin and Rom manager but I don't believe that there is a similar program for the Mt4g (Odin that is) I guess I have been spoiled by my Vibrant as it seems to have more options to recover with and are easier to use from what I can tell. I do love this MT4g though It is probably the best all around phone I have ever owned. Any and all info and help is greatly appreciated.:
to my knowledge there has been no gingerbread port for our device yet. Your lucky you didn't brick your device.
tenbeau said:
I just tried flashing the Gingerbreadime.zip and followed the directions to the letter and I experienced my first soft brick. The phone went into a boot loop at the mytouch screen. Luckily I was able to go into Recovery and restored the backup I had made after rooting and turning s=off. It appears to have restored okay as I still have root etc. Does anyone have any idea how or why this happened ? This zip was posted in Droid-Life and was advertised as good for all android 2.2 devices. I have never used adb but have it set up on my phone so I guess I had better get more familiar with it. I have flashed my Vibrant numerous times using Odin and Rom manager but I don't believe that there is a similar program for the Mt4g (Odin that is) I guess I have been spoiled by my Vibrant as it seems to have more options to recover with and are easier to use from what I can tell. I do love this MT4g though It is probably the best all around phone I have ever owned. Any and all info and help is greatly appreciated.:
Click to expand...
Click to collapse
There are people experiencing the same thing in the Nexus forum. Personally I would stay away from anything that is not specifically built for this phone as its a completely different OS than Vanilla or Moto Droid or etc. etc.
bobsbbq said:
to my knowledge there has been no gingerbread port for our device yet. Your lucky you didn't brick your device.
Click to expand...
Click to collapse
yes I a sure am. I trusted the Dorid-Life site and should not have. Thanks for the swift response...
setzer715 said:
There are people experiencing the same thing in the Nexus forum. Personally I would stay away from anything that is not specifically built for this phone as its a completely different OS than Vanilla or Moto Droid or etc. etc.
Click to expand...
Click to collapse
I sure intend to and I should have got on this forum before I even attempted to flash it. Right now everything seems fine except I cannot get into recovery only clockworkimode recovery. I am holding down the volume down button and pressing the power button at the same time and the device just reboots. Any ideas and what could be causing that? I am embarassed to say that my ignorance that pushed me to flash that zip is probably at the root of it. Any steps that I can take to enable me to get into stock recovery to check and make sure S=off?
Edit: Just pulled battery and sim card and than put them back in and the device went into stock recovery and s=off so I hope that all is okay and I did not create some ghosts that will show up when I attempt to flash a rom later on.
Please post questions in Q&A section.
I did the same thing. I flashed the .zip file from droid life forum and got a success message when I installed it through recovery and mine never bootlooped. I didn't get the gingerbread keyboard but it didn't bootloop either
Sent from my HTC Glacier using XDA App
tenbeau said:
I sure intend to and I should have got on this forum before I even attempted to flash it. Right now everything seems fine except I cannot get into recovery only clockworkimode recovery. I am holding down the volume down button and pressing the power button at the same time and the device just reboots. Any ideas and what could be causing that? I am embarassed to say that my ignorance that pushed me to flash that zip is probably at the root of it. Any steps that I can take to enable me to get into stock recovery to check and make sure S=off?
Edit: Just pulled battery and sim card and than put them back in and the device went into stock recovery and s=off so I hope that all is okay and I did not create some ghosts that will show up when I attempt to flash a rom later on.
Click to expand...
Click to collapse
I think you mean bootloader? You only have 1 recovery. If you flashed clockwork you no longer have stock recovery. Vol Down + Pwr gets you to bootloader or SPL where it shows S=off.
I did not flash the zip (sounds like an overkill to flash a zip for new KB). I ADB pushed both files and got a FC on multi-touch KB... oh well, I like HTC_IME better anyway
tenbeau said:
I sure intend to and I should have got on this forum before I even attempted to flash it. Right now everything seems fine except I cannot get into recovery only clockworkimode recovery. I am holding down the volume down button and pressing the power button at the same time and the device just reboots. Any ideas and what could be causing that? I am embarassed to say that my ignorance that pushed me to flash that zip is probably at the root of it. Any steps that I can take to enable me to get into stock recovery to check and make sure S=off?
Edit: Just pulled battery and sim card and than put them back in and the device went into stock recovery and s=off so I hope that all is okay and I did not create some ghosts that will show up when I attempt to flash a rom later on.
Click to expand...
Click to collapse
make sure fastboot is checked off otherwise you cant get into the bootloader. to make sure it is off go to: menu, settings, applications and uncheck fastboot. you're good to go then. to get into recovery, you can do it thru bootloader or by opening up rom manager and clicking on the "reboot to recovery" option
setzer715 said:
There are people experiencing the same thing in the Nexus forum. Personally I would stay away from anything that is not specifically built for this phone as its a completely different OS than Vanilla or Moto Droid or etc. etc.
Click to expand...
Click to collapse
the website was not specific enough. the port at the current moment is for motorola droid devices. they should have been more specific instead of saying any rooted 2.2 android phone. even if you do get it on your phone, its only going to force close every time you try and type something. thats what happened to me, so after about 24 hours i said **** it and removed it. swype in my opinion is better anyway. im trying to port the g2 swype to our phone so we can have a swype with a mic on the keyboard. oddly, ours didnt come with one.
I posted this elsewhere but I would like a answer faster.
I like to think I am rather educated in regards to how to root and all that. I just got my replacement Evo today and of course it is updated to 2.3.3. So I can't use unrevoked, but I was hoping to flash over to a older backup I made on 2.2 on my old phone.
Except, when I do the whole hold the volume down + power button and eventually choose recover, all that happens is a image of a phone and a exclamation point appears and it never leaves here.
I know in order for me to be able to use ClockwordMod I need to root the phone, which can't happen on 2.3
So what are my options? How do I flash over my old rom???? Even if it doesnt let me get back to 2.2 its still better than redownloading all my apps.
Rapture Veteran said:
I posted this elsewhere but I would like a answer faster.
I like to think I am rather educated in regards to how to root and all that. I just got my replacement Evo today and of course it is updated to 2.3.3. So I can't use unrevoked, but I was hoping to flash over to a older backup I made on 2.2 on my old phone.
Except, when I do the whole hold the volume down + power button and eventually choose recover, all that happens is a image of a phone and a exclamation point appears and it never leaves here.
I know in order for me to be able to use ClockwordMod I need to root the phone, which can't happen on 2.3
So what are my options? How do I flash over my old rom???? Even if it doesnt let me get back to 2.2 its still better than redownloading all my apps.
Click to expand...
Click to collapse
Well, you have a couple problems here.....if I am not mistaken, your first problem seems to be that your recovery may either be corrupt or not installed. I saw this issue back in my TP2 days. Not with the evo though. If this is a replacement EVO and you cannot properly get to your recovery, then I would suggest contacting sprint on this issue. It should at least go into the stock recovery. As for your rooting issue...you can't do anything untill root is provided for the update.....best of luck to you!
His recovery is not corrupt. That's stock recovery
HipKat said:
His recovery is not corrupt. That's stock recovery
Click to expand...
Click to collapse
thats what i thought. so i have to just update the drivers by installing the provided unrevoked drivers/method? id like it but im new and it wont let me. well...
unrevoked dot com/rootwiki/doku.php/public/windows_hboot_driver_install
Well, as we've seen in the 10 million posts about this, there is no root for 2.3.3 yet.
No root, no recovery. No nothing, but stock and that's that.
Rapture Veteran said:
I posted this elsewhere but I would like a answer faster.
I like to think I am rather educated in regards to how to root and all that. I just got my replacement Evo today and of course it is updated to 2.3.3. So I can't use unrevoked, but I was hoping to flash over to a older backup I made on 2.2 on my old phone.
Except, when I do the whole hold the volume down + power button and eventually choose recover, all that happens is a image of a phone and a exclamation point appears and it never leaves here.
I know in order for me to be able to use ClockwordMod I need to root the phone, which can't happen on 2.3
So what are my options? How do I flash over my old rom???? Even if it doesnt let me get back to 2.2 its still better than redownloading all my apps.
Click to expand...
Click to collapse
Are you s-on or s-off ?
HipKat said:
His recovery is not corrupt. That's stock recovery
Click to expand...
Click to collapse
If I member right once in stock recovery you push vol up + power button to get the menu up.
sent from my locked EVO via tapatalk
*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?