Related
Just got prompted for a new update here is the link
https://android.clients.google.com/packages/incrediblec/OTA_IncredibleC_Verizon_WWE_1.22.605.2_1.22.605.0_release_sign.a33bc3bf.zip
Instructions?
if you want to install this you just downlaod it put it on the root of your sd card, than rename it to update.zip than rebbot to rcovery than select apply update.zip.
Im not saying its ok to install this, as for me i am going to wait for a bot till i can look into more.
Mirror Here
Anybody without a corp account try flashing this yet?
i flashed it today and I do NOT have the CorpEmail account. I really hope this doesn't stop me from getting root.
Gimpeh said:
Anybody without a corp account try flashing this yet?
Click to expand...
Click to collapse
i have, no differences at all. battery life will tell in a day or two
So are we safe letting update go thru? Or should we hold off if we want root?
I wouldn't flash it yet. It contains a recovery image and I don't know if anyone knows for certain what's different about the image.
Would this have the correct test keys?
I flashed. Not noticing anything unexpected. Im getting my incredible replaced anyway. Sounds like I'm listening to people talk underwater.
I doubt you'd notice anything different; I'm just afraid that they've closed a useful hole.
Now if this thing would just stop asking me every 20-30 minutes ... grrrr.
The update fixes the email client for business users.
The meat of the update they don't tell you about, however, is there is a new recovery image in the updater. So yeah, maybe a hole was closed.
I held down volume down button and hit power, booted into the prompt, selected "recovery mode," and all I got was a red triangle and exclamation point.
I downloaded the zip, renamed it update.zip, and put it on /sdcard using Astro.
Am I doing something wrong?
I have the exact same problem.
dont do it
Just checking to see if people successfully installed this OTA update from the mirror site link provided earlier in this thread. I think it's my only chance to go to FroYo without using RUU/wiping the phone.
I figure I can update from 1.22.605.0 with this update and then go to the FroYo thread and run that update. Does that sound like it will work?
This whole subject was coverd in another thread.
http://forum.xda-developers.com/showthread.php?t=770091
swindelljd said:
Just checking to see if people successfully installed this OTA update from the mirror site link provided earlier in this thread. I think it's my only chance to go to FroYo without using RUU/wiping the phone.
I figure I can update from 1.22.605.0 with this update and then go to the FroYo thread and run that update. Does that sound like it will work?
Click to expand...
Click to collapse
read the other thread, you need to update to 1.22.605.2 first, easy and does not lose date.
Root and OTA
I have rooted with unrevoked 3.1 but still have stock 2.1. Do I need to unroot to install the OTA or will the OTA still be pushed to my phone while I am still rooted?
Hi guys, i'm new here and a bit of a noob to the whole Android world.
I got my a500 about a month ago and loving it, Rooted it and got rid of all the bloat ware and is running like a dream.... love it....
A couple of days ago, i got an update: System Update 1.139,05, downloaded it and went to install, rebooted but nothing, Update failed!
I already have Android version 3.0.1 and Kernel version 2.6.36.3.
Is it me doing some thing wrong? Is it because its rooted? Do i need the update, please help, just want it to be up to date. Love the forum, thanks
chickin2000 said:
Hi guys, i'm new here and a bit of a noob to the whole Android world.
I got my a500 about a month ago and loving it, Rooted it and got rid of all the bloat ware and is running like a dream.... love it....
A couple of days ago, i got an update: System Update 1.139,05, downloaded it and went to install, rebooted but nothing, Update failed!
I already have Android version 3.0.1 and Kernel version 2.6.36.3.
Is it me doing some thing wrong? Is it because its rooted? Do i need the update, please help, just want it to be up to date. Love the forum, thanks
Click to expand...
Click to collapse
I've seen that some other users have had issues with the update if they removed the bloatware. Have you put it back before you attempted the update? If not, you'll have to put everything you've removed back and if you've edited any of the system files like build.prop, etc..you'll have to put it back to original also.
Thanks for the reply JackMetal! ERRRRRMMMM Q: is this a big update and if so then how would i put everything back, would it be factury settings? and if i do need to put everything back on why did i root it? lol sorry for being suck a noob! )
chickin2000 said:
Thanks for the reply JackMetal! ERRRRRMMMM Q: is this a big update and if so then how would i put everything back, would it be factury settings? and if i do need to put everything back on why did i root it? lol sorry for being suck a noob! )
Click to expand...
Click to collapse
LOL - yeah, I know..it's kind of a sucky move on Acer's part to force that. ;-) How did you remove them? Did you just delete them or freeze them within Titanium Backup? If deleted, did you happen to make a backup of them first so you could restore them now.
You can look at /cache/recovery/last_log and see exactly what it's complaining about. If you don't have the files you deleted, you can ask in the forum to see if another user can send them to you. I'd be glad to send mine, but I would imagine mine probably wouldn't help you since they are from 'after' the update and the checksum would still fail since they're changed. We could give it a shot though, and if it doesn't work you can see if someone that hasn't updated or happens to have the previous versions backed up, could send you the files.
---edit
Actually, I've got a few Titanium Backups from before the update, so I may just have the files you need!
Sweet dude, right will have to give it a look as i deleted them, noob thing to do i know lol still learning, thanks again for the super quick reply!
Same thing happened to me and this was after I restored my A500 to factory stock. I re-started the update download from the settings/info menu and this time it went without a hitch. I now have the updated A500, rooted it and am ready to go.
Advice for those people rooting their tablets. Don't just delete any .apks you don't want; move them to a folder on the internal sd card instead so whenever you need to restore them it's a simple matter of just moving them back).
Right, just an update.......
don't laugh, but i did try to put back all of the bloat ware!!!!! However, i replace some things and got rid of others, NOT GOOD! " HOME NOT WORKING ", yes thats what it said or words to that effect! Restarted as i thought that would help! OMG BOOT LOOP! Phone acer and sent it back for repair, UPS picked it up and acer received it this morning, and 30 mins again i got a text message with it done you douche bag, well they didn't say douche bag, but hay they should have done! Yes i'm a noob at all this, but i have learnt my lesson. Must say thanks for the help anyway from the forum!
P.S UPS SUCK BALLS, they are rude and v unprofessional! (had problems with them picking up the tablet).
P.P.S Back up everything and the back it up again! And DONT get rid of any system file or anything, to quote someone from the forum, " you have plenty of room! ", I have the 32Gb so yes i have the room lol!
O and just one more thing............ BACK THING UP NOOBS !!!!!!! )
Or Rename!
iCurmudgeon said:
Same thing happened to me and this was after I restored my A500 to factory stock. I re-started the update download from the settings/info menu and this time it went without a hitch. I now have the updated A500, rooted it and am ready to go.
Advice for those people rooting their tablets. Don't just delete any .apks you don't want; move them to a folder on the internal sd card instead so whenever you need to restore them it's a simple matter of just moving them back).
Click to expand...
Click to collapse
Also to make easy, just rename the .apk's to .bak or freeze them in Titanium backup!
Not to sound like a smartass but you know you could have done it yourself? Flash the device i mean.
What you do is you look for the boot.img and system.img and update.zip files in this forum or somewhere.
First the chinese one that you can just place in your External SD card and press Power+Vol- when device is turned of.
Then proceed to look for the American version, or whatever you wish if it's available.
Then you do this: place the boot.img and system.img in the root internal memory called Sdcard and place the update.zip in your EXTERNAL MicroSDcard.
Install Terminal emulator and push the boot and system img's 1st boot, 2ndSystem. Have superuser installed to.
After that when the images are pushed (usually the tablet would freeze after the system.img)
Then you force stop and power up the unit by holding Power button + Vol-
and that's it! No need to send to repair and pay money perhaps.
Today I DEcided To Root My Friends SGS Fascinate, All i wanted to do is replace the stock launcher with a newer one on root explorer, but messed it up, the TwLauncher kept FC and i could get out of it, i then came here and started flashing "Recoveries" but all it did was make it worse, right now im waiting for a download to finish with the DI01.bin to see if Odin3 can help, and on top of that the clockworkmod that is flashed on the device is damage somehow doesnt want to mount the sd card where i have the backup and the roms , since i cant flash anything aFTER 12 HOURS ON THE SITE AND TO NO SUCCESS i come to you guys.
I know you have your own business and problems but thats what were here for helping each other
i would appreciated much if anyone can help
treborbula
treborbula1 said:
Today I DEcided To Root My Friends SGS Fascinate, All i wanted to do is replace the stock launcher with a newer one on root explorer, but messed it up, the TwLauncher kept FC and i could get out of it, i then came here and started flashing "Recoveries" but all it did was make it worse, right now im waiting for a download to finish with the DI01.bin to see if Odin3 can help, and on top of that the clockworkmod that is flashed on the device is damage somehow doesnt want to mount the sd card where i have the backup and the roms , since i cant flash anything aFTER 12 HOURS ON THE SITE AND TO NO SUCCESS i come to you guys.
I know you have your own business and problems but thats what were here for helping each other
i would appreciated much if anyone can help
treborbula
Click to expand...
Click to collapse
Can you still get your phone into download mode? If you can, follow the instructions in the sticky post titled " how to recover your fascinate from any brick... " by Dalev.
PWGB,TKSGB10-14, adren shot xix, honeycomb2.03, ec09 radio.
No offense, but judging by your post you have no business flashing/rooting anything if you don't understand what your doing, let alone on someone else's phone.
Sent by way of the GB delivery truck..
You can install different launchers without being rooted...just an fyi
Swyped via Tapatalk
Okay so like I said I have the a200 and I am on ICS and I rooted and installed CWM using a batch program by someone on the acer fourms. I dont seem to be getting alot of responces over there though. I am looking to go back to stock. So I have to install a stock rom and stock recover.img and lock the bootloader. Now I just got a ota update notification but of corse I cant update with CWM so I downloaded it and copied it to my pc and then I unzipped it and went to the META-INF\com\google\android\updater-script then I erased the first line of the updater script then I renammed the whole thing update and rezipped it so now I have the ota with the edited updater script nammed update.zip If I install this through CWM will it return me to stock? Any help from you guys would be apriciated.
Thank you,
Charlie
PS I am not saying anything bad about anyone over at the other fourm I just havent gotten alot of responces from them is all they are probally busey or whatever so I just wanted to try over here.
mojorisin7178 said:
Okay so like I said I have the a200 and I am on ICS and I rooted and installed CWM using a batch program by someone on the acer fourms. I dont seem to be getting alot of responces over there though. I am looking to go back to stock. So I have to install a stock rom and stock recover.img and lock the bootloader. Now I just got a ota update notification but of corse I cant update with CWM so I downloaded it and copied it to my pc and then I unzipped it and went to the META-INF\com\google\android\updater-script then I erased the first line of the updater script then I renammed the whole thing update and rezipped it so now I have the ota with the edited updater script nammed update.zip If I install this through CWM will it return me to stock? Any help from you guys would be apriciated.
Thank you,
Charlie
PS I am not saying anything bad about anyone over at the other fourm I just havent gotten alot of responces from them is all they are probally busey or whatever so I just wanted to try over here.
Click to expand...
Click to collapse
You can't do OTA update with CWM. You need stock recovery.
Restart your tab, go get Acer Recovery Installer app in market. It will allow you to install official recovery. This is the easiest way but works only for rooted devices.
Cheers
mojorisin7178 said:
Okay so like I said I have the a200 and I am on ICS and I rooted and installed CWM using a batch program by someone on the acer fourms. I dont seem to be getting alot of responces over there though. I am looking to go back to stock. So I have to install a stock rom and stock recover.img and lock the bootloader. Now I just got a ota update notification but of corse I cant update with CWM so I downloaded it and copied it to my pc and then I unzipped it and went to the META-INF\com\google\android\updater-script then I erased the first line of the updater script then I renammed the whole thing update and rezipped it so now I have the ota with the edited updater script nammed update.zip If I install this through CWM will it return me to stock? Any help from you guys would be apriciated.
Thank you,
Charlie
PS I am not saying anything bad about anyone over at the other fourm I just havent gotten alot of responces from them is all they are probally busey or whatever so I just wanted to try over here.
Click to expand...
Click to collapse
Actually, you can install this through CWM, but you need to make some changes. Several in the install.script. Then in the rom itself, you need to remove a couple of things. Mainly bootloader.blob. and recovery folder. These are the things you have to compensate for in the install.script.
Also, may be a recovery file in there also that needs to be removed. Acer has been getting clever these days. Something like boot.p (civato has it named in his guide)
If you can post the update.zip you have, so some of us can look at it, we can put it in a CWM format.
Okay I will post the ota as it came in before I modified it. It was in my cache. So if I post this then you can turn it into something I can use to go back to 100% stock? That is what I am really looking to do with the boot loader locked and root gone and cwm? Also I did not know that there was an app that retires the stock recovery. That is pro ally the best way if it works because if I use that then I should be able to just use the update the w/ay it is I think. Anyway I will all try that and also post those files when I get home tonight after work. Thank you for your help wit this.
Charlie
Actually someone over at the acer fourm made a CWM flashable .zip for the update. But it is only the rom so mit dosnt help me I want to lock the bootloader. So I did try the market app and it does work so what I am thinking is restoring my first nandroid the one I made right after I installed cwm so it will get rid of the last update then restoring my bootloader from the market app then taking the ota the way it came over the air and renaming that update.zip and booting into recovery then it should do the ota update and when it is done everything should be back to stock I think. My only question is do I put it on my inyernal or external sd card? I guess I will try both. I will let you know how I make out.
Okay I am posting the official OTA the latest one for the a200 I am posting the one as it came over the air pulled right out of my cache. I have never done this before so bear with me. http://dl.dropbox.com/u/32696206/B2435D271BA1D0BC231D6BE66778A6AB.zip
Okay so I think that I did that right if It doesnt work let me know If anyone can make a flashable out of this that will lock the bootloader and get rid of CWM let me know. And thanks for all of your help
mojorisin7178 said:
Okay I am posting the official OTA the latest one for the a200 I am posting the one as it came over the air pulled right out of my cache. I have never done this before so bear with me. http://dl.dropbox.com/u/32696206/B2435D271BA1D0BC231D6BE66778A6AB.zip
Okay so I think that I did that right if It doesnt work let me know If anyone can make a flashable out of this that will lock the bootloader and get rid of CWM let me know. And thanks for all of your help
Click to expand...
Click to collapse
No problem. Downloading now. I will look at it in the morning, and see what's in it. It it is something worth flashing, I will certainly let you know. Regards... MD
*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?