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?
First off, ive been searching and trying different roms for hours to no prevail. I will begin with what ive accomplished and attempted. BTW, im a complete noob to rooting.
I followed the 1.5 to 2.1 sticky "[Walkthrough] From stock (1.5) to rooted 2.1 (update - new link)". I successfully completed part 1 and part 2 but fail on part 4. I did not attempt the recovery install and regret it now.
So I was able to get the full install of PB00IMG.zip to work flawlessly. I don't believe it was actually necessary to install a special rom at this point but when i started i figured they were step by step instructions. Then i got the usb driver installed and my pc recognized my phone as the htc dream which i figure is normal. After that I attempted to install the ivan 1.0 rom and got exactly this:
E: Can't open /cache/recovery/command
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
I figure the only relevant part is the signature failure. I realize that all the zips are signed and therefore cannot be opened. I understand that they have to be renamed to "update.zip". No im not naming it "update.zip.zip". I am renaming it with windows xp. I saw somewhere that a guy had the same issue and renamed it with astro and it worked out fine so Im hoping this is the issue but that seem silly. Ive verified the md5 sums of the rom images as well.
Ive also tried the Eris_Official that is on the sticky and plane jane 1.0.
Ive seen some debate on whether or not the 2.1 ota eris's can be rooted but it seems quite apparent its the same as any other eris. my hboot is 1.46 and not 1.49 so all is well there.
I also applied wipe data/factory reset
At this point i am at a loss as to what to do because it seems as though ive tried everything. I will reinstall PB00IMG.zip (hopefully) but im not sure what that rom actually does, i have no idea at all. From what i saw upon booting it seems like a simple stock 2.1 rom that is rooted. I'd prefer not to use that but as long as i can install the overclock kernel then i dont mind too much. I prefer the ivan rom. I prefer to switch between roms at will like the experienced rooters on here.
i did not wipe cache partition because im not sure what that does and it was never mentioned.
From deductive reasoning, it HAS to be an issue with the signature verification and is probably a simple fix.
Any help would be greatly appreciated. Hopefully i have mentioned everything that has transpired.
You can't flash a rom without first flashing the recovery img, go back to step 4 and flash amon ra's recovery image.
i realized that and was in the process when you posted. thanks tho. I guess i got impatient and figured recovery meant like a back up if i screwed up. thats what happens when ya dont follow directions! i have like 3 roms saved and im dl'ing the ivan and will give it a shot. everything else is completed tho. just waiting on teh download. i think i lost a good amount of contacts tho because i didnt back them up. i have no clue how to get them back beyond trying to sync with google. does our google account save all contacts automatically?
illogical06 said:
i realized that and was in the process when you posted. thanks tho. I guess i got impatient and figured recovery meant like a back up if i screwed up. thats what happens when ya dont follow directions! i have like 3 roms saved and im dl'ing the ivan and will give it a shot. everything else is completed tho. just waiting on teh download. i think i lost a good amount of contacts tho because i didnt back them up. i have no clue how to get them back beyond trying to sync with google. does our google account save all contacts automatically?
Click to expand...
Click to collapse
it does if you have syncing enabled, when you log in with your email on the new rom, it will restore your contacts back from google. also the first time you open your market, if you hit menu and go to downloads, it remembers what you had previously downloaded.
ivans is nice as an like stock rom, but i think it is out dated, there was a newer one jcase's plain jane rom, or basically anything on the front page. tho i perfer cyanogen elb, or zenexp. eh try a few different ones
its weird because i never turned off sync my google email. the only sync options i had were google, facebook, and flickr (that applied to me). Most of my contacts are saved but not all.
I also did the market thing immediately but apps like handscent weren't in there which is odd to me.
My big thing about switching between roms is saving all the settings from the previous one. I presume there is a root app for that but i havent even begun to dive into it. I just wanted to overclock this thing because its pissing me off with how slow it is. Also, it being more slim as far as cluttered bs apps helps too.
btw, i got it fully up and running, just installing apps and adding contacts. I would say that contacts over a few months old or less are the only ones missing.
illogical06 said:
I guess i got impatient and figured recovery meant like a back up if i screwed up.
Click to expand...
Click to collapse
so why would you leave that to chance. . . im sure you noticed all the disclaimers, i understand its at your own risk but still. The recovery has saved my 4$$ several times now. . . trust me especially if your a new it isn't worth the risk. (unless your ballin but no offense to anyone if we were we'd all have incredibles or at least moto droids by now). . and don't use rom manager until its been tested on our device thoroughly . . . which means never use rom manager on an HTC Eris. lolz
You can use something like titanium to backup your apps and settings
Sent from my Eris using Tapatalk
Illogical when did you get your Eris? I ask this because I'm getting a replacement Eris next week an I'm just wondering if I have to prepare my self for the new 2.1 with the 1.49 h boot or if there a possibility that I would get something easier to root.
My phone asks me if I want to install, I hit yes, it powers off and goes to the screen with the droid and the status bar. Status bar fills up then it changes to the droid with the ! in the triangle and just stays there. If I pull the battery it asks me if I want to install again when the phone boots up.
Rooted 2.2 w/ unrevoked forever.
my update went to that page with the !....had 2 arrows kinda making a circle around it. Just wait it out...mine sat there a few but did its thing...
Mine doesn't have the arrows. It has been sitting there for 15+ minutes on two different occasions now.
i get "assert failed" then boots to previous rom
hmmm... Does it have any red on that page? I have seen that page with red on it...battery pull usually fixes it. Mine was same page but no red at all just the arrows. Maybe you should be on a stock 2.2 ROM?
There are several different ways to get it now here is one you can try:
http://forum.xda-developers.com/showpost.php?p=8279411&postcount=23
AnHero said:
My phone asks me if I want to install, I hit yes, it powers off and goes to the screen with the droid and the status bar. Status bar fills up then it changes to the droid with the ! in the triangle and just stays there. If I pull the battery it asks me if I want to install again when the phone boots up.
Rooted 2.2 w/ unrevoked forever.
Click to expand...
Click to collapse
Same configuration here with the same results.
It's just the little green guy and the !. No red. Battery pulled 3 times now, won't work. I'm on stock 2.2.. only rooted. I rooted it and haven't changed anything. Not even a custom kernel.
Hmm, something must be up with the OTA update. Just download the package from one of the other threads, save it to SD card and update from zip from recovery.I did that and it worked in less than 10 minutes
There are several different ways to get it now here is one you can try:
http://forum.xda-developers.com/showpost.php?p=8279411&postcount=23
Also I have the actually files that I got when I did the OTA if you want them. I am actually unrooted on one of my phones...for comparison stuff. So the files I recieved on the unrooted OTA are here:
These are the 2 files I recieved when I updated:
1: http://www.mediafire.com/?i2ypi9121snmpyo
2: http://www.mediafire.com/?cljyvv281l1b000
I have not tested to see if they break root but this is the official updates...2 seperate files/apk's.
Same problem here with unrevoked so I did it manually and it worked like a charm.
I can't post links but if you go to androidcentral it has the instruction there on the front page.
http://www.androidcentral.com/....
AnHero said:
My phone asks me if I want to install, I hit yes, it powers off and goes to the screen with the droid and the status bar. Status bar fills up then it changes to the droid with the ! in the triangle and just stays there. If I pull the battery it asks me if I want to install again when the phone boots up.
Rooted 2.2 w/ unrevoked forever.
Click to expand...
Click to collapse
had that exact same problem. i think the OTA doesn't bode well with being rooted, at least thats what it seems. i was unrevoked and tried it (then got your problem with the !). so i tried unrooting it and the update worked like a charm
BTW....You will need run unrevoked again if you applied the update manually!
yep i went all stock unrooted and it took it right away. it probably didnt like the fact i was on metropcs too lol
why are you guys doing ota? there is already a rooted version of this update in development that you can flash from recovery.
i just want pri,radio,etc and rom to be stock without any mods besides what i do.
poetictragdyx said:
had that exact same problem. i think the OTA doesn't bode well with being rooted, at least thats what it seems. i was unrevoked and tried it (then got your problem with the !). so i tried unrooting it and the update worked like a charm
Click to expand...
Click to collapse
I'm getting error 7.
Can you provide the link for unrooting?
Help with OTA
Hello everyone.Im sure your getting bombarded with a lot of questions.I have the OTA Downloaded on my computer.I changed the name to update.zip
Im not sure if im putting the file on the sdcard of if there is a specific file i cant find to put it in.
When i go through the process of shutting phone off and using the volume button i get are you sure you want to install and i click yes.
This is what i get.
Clockwork recovery v2.5.0.1
---Install from sdcard...
Finding update package....
Opening update package...
E: Cant open/sdcard/update.zip
(No such file or directory)
Installation aborted.
Thanks in advance...
So is the manual update working for everyone that rooted using unrevoked 3.2? I just want to make sure before I go through the process.
AnHero said:
My phone asks me if I want to install, I hit yes, it powers off and goes to the screen with the droid and the status bar. Status bar fills up then it changes to the droid with the ! in the triangle and just stays there. If I pull the battery it asks me if I want to install again when the phone boots up.
Rooted 2.2 w/ unrevoked forever.
Click to expand...
Click to collapse
Guide for this
http://forum.xda-developers.com/showthread.php?p=8285266#post8285266
Dear all,
I got a update notification today. I was so happy to see that.
I spent 20 mins on downloading this firm, but after the unzipping procedure,
it exit Andriod OS and reboot to a DOS-like system.
I saw a bee on the screen, there was a ProcessBar under this bee.
When the process went to around 20%, the process was failed and a "!" was shown up.
I installed Acer Recovery Installer on my tablet and I have Recovery on it as well.
Is it the reason why I cannot update my OS?
Help!!!!!
Easier way to get official OTA updates from acer is to be full stock :
- stock rom
- stock recovery / bootloader
Remember that updating to stock 3.2 will makes you lose root
franva said:
Dear all,
I got a update notification today. I was so happy to see that.
I spent 20 mins on downloading this firm, but after the unzipping procedure,
it exit Andriod OS and reboot to a DOS-like system.
I saw a bee on the screen, there was a ProcessBar under this bee.
When the process went to around 20%, the process was failed and a "!" was shown up.
I installed Acer Recovery Installer on my tablet and I have Recovery on it as well.
Is it the reason why I cannot update my OS?
Help!!!!!
Click to expand...
Click to collapse
Must remove root and all mods and reflash stock recovery. Maybe not all, but that should work.
shaun298 said:
Must remove root and all mods and reflash stock recovery. Maybe not all, but that should work.
Click to expand...
Click to collapse
Are there instructions on how to do this?
Update 3.2 failed
Hello, I have the same problem, I can install the stock with CWM? if so, where can I download? the ROM?
(sorry for my bad english)
My device is Acer Iconia Tab A501
I am having quite a bit of problem updating my A500. After the update downloaded the first time, it gave me an error saying update is invalid. After that it is constantly trying to download. As soon as 357 MB is downloaded, instead of asking me whether to install now or later, it just goes ahead and tries to re-download all over again. As you know it takes some 20 mins to get the whole 357MB over wifi, so I went ahead and unchecked the automatic update checkbox in system update. Does anyone know where the downloaded file ends up? I could just try to run it from that location.
My system was rooted, but once I got the last ROM update (3.1), the tablet was unrooted and none of the rooted apps work anymore. So I don't think I should be having root related issues unlike some of you who are having problems. Any help is appreciated.
Fix for "Invalid Update" problem .....
Samaruf,
I suggest that you have a look at Post #4 in the following thread......
http://forum.xda-developers.com/showthread.php?p=18132338#post18132338
This thread appears to be focused on a different problem. The resolution to your problem is at the above thread. Good luck....
*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?