it gets to writing signiture and says it cant update this rom. is there a newer ruu from sprint. it used to work till i got my replacement phone in.
I had same issue..
what I did was (and this only worked cuz I had this already done) Rooted the phone with RA 1.5.2 recovery and flashed Fresh 1.0
once I got it to successfully load into fresh.. then I ran the RUU 1.29 and it worked..
still cant get it to let me un root it. it says that it is the wrong rom to do it. is there a new ruu
Have you tried flashing while in quick boot?
sorry to be such a newb. but what is quick boot and how do i get to it
Power your phone off. Hold the volume down button and power it on. You will get a menu and one of the options is quick boot (I think it's volume up but I'm not positive).
With it hooked up to your computer, check device manager in windows and make sure you don't have any missing phone drivers. If you don't then run the RUU.
ok trying that now. and no errors with drivers
still doesnt work as soon as it gets to updating signature it stops. i dont get it. i have done it a million times with no problems. now it wont work
do you have "usb debugging" turn OFF?
I can confirm testing it with debugging off it still doesn't work. I've tried a million times as well, same problem. I'm not sure if we have to flash the stock rom image before doing so, but in flashrec it only gives me the option of backing up image before actually flashing one and I get an error "Backup Failed: Could not run command" not sure if that has anything to do with it
RUU 1.29 CDMA Sprint
Here's how I got it to work. I reflashed mine couple weeks ago with stock sprint rom (orginal factory state). You need to have HTC sync connected first. Once you establish connection than run RUU 1.29. The hero will drp connection than automatically re-install drivers than it will continue to load the original rom from sprint.
mulcahyd said:
Here's how I got it to work. I reflashed mine couple weeks ago with stock sprint rom (orginal factory state). You need to have HTC sync connected first. Once you establish connection than run RUU 1.29. The hero will drp connection than automatically re-install drivers than it will continue to load the original rom from sprint.
Click to expand...
Click to collapse
I was working with someone who was having an issue flashing the RUU (failing at checking license). I took him in to fastboot and we literally tried manually running the restore step by step. Basically what the RUU does but manually. And it would still fail at the license. It wasn't a driver issue.
But your fix will work for people whose RUU says it can't find the phone after it reboots it.
flipzmode said:
I was working with someone who was having an issue flashing the RUU (failing at checking license). I took him in to fastboot and we literally tried manually running the restore step by step. Basically what the RUU does but manually. And it would still fail at the license. It wasn't a driver issue.
But your fix will work for people whose RUU says it can't find the phone after it reboots it.
Click to expand...
Click to collapse
So how do we get it to work? I get the same error, unfortunately. I was thinking about trying your hero ruu update that you put out...
obannvi said:
So how do we get it to work? I get the same error, unfortunately. I was thinking about trying your hero ruu update that you put out...
Click to expand...
Click to collapse
The one on ppcgeeks? Heh I need to pull that. I used it earlier and found that after using it I had no access to the /data folder. Not huge deal if you are using it to take your phone back to Sprint or something, but no good if you are wanting to use it. I need to fix the script but am swamped right now.
What's your reason for wanting to RUU? Is your phone "with google" branded?
flipzmode said:
The one on ppcgeeks? Heh I need to pull that. I used it earlier and found that after using it I had no access to the /data folder. Not huge deal if you are using it to take your phone back to Sprint or something, but no good if you are wanting to use it. I need to fix the script but am swamped right now.
What's your reason for wanting to RUU? Is your phone "with google" branded?
Click to expand...
Click to collapse
I have the "With Google" branding. I wanted too revert back and get it swapped out. I also wanted to reflash Fresh to it...
obannvi said:
I have the "With Google" branding. I wanted too revert back and get it swapped out. I also wanted to reflash Fresh to it...
Click to expand...
Click to collapse
So of the people that have been having the issue where it fails at the licensing issue and gives you: Error[140]: Bootloader Version Error, all the ones I've talked to (only a couple of you) have had "with google" phones. Although all have said that they were able to RUU before and can't anymore.
If you strictly want to return to stock so that you can return the phone then I can help you. PM me.
flipzmode said:
So of the people that have been having the issue where it fails at the licensing issue and gives you: Error[140]: Bootloader Version Error, all the ones I've talked to (only a couple of you) have had "with google" phones. Although all have said that they were able to RUU before and can't anymore.
If you strictly want to return to stock so that you can return the phone then I can help you. PM me.
Click to expand...
Click to collapse
I just dont understand why its sluggish. It was never sluggish before. I figure by reverting back to stock and then re-freshing it, it should be ok.
You can try just clearing your cache (my app installer in my sig can help you do that) and then flashing fresh on top of itself to see if that helps the speed issue.
flipzmode said:
You can try just clearing your cache (my app installer in my sig can help you do that) and then flashing fresh on top of itself to see if that helps the speed issue.
Click to expand...
Click to collapse
I'll give it a shot. I do have a nand backup of my original install before I installed Fresh...I did that prior and then I installed Fresh again...
Didnt work, still sluggish. I did a wipe through the recovery menu so we'll see what happens.
Related
Hi, Sorry to start a new thread but I have a specific Android 2.1-invoked difficulty. (I think. Indeed, I hope.)
This is my phone. I can give the serial number if it helps anyone.
hero cvt ship s-on
hboot-1.76.007 (hero10000)
m1crop-010f
touch panel-syn0104
radio-6.35.06.18
Aug 4 2009, 19:43:30
My Hero is completely unmolested. Just a Hero supplied by my subcontracted Vodafone supplier. I have done nothing to it except load apps. It is not rooted. I think. Until yesterday, I did not know what "rooted" meant. Well, not in this context, and unless you are Australian you will not get that joke.
So I got the OTA ROM notice to upgrade - supposedly the prep part of Android 2.1. I accepted it and it all went fine. No problem - all done. Rebooted and running 2.73.405.5...
Nothing happened for a fortnight until Sunday evening when the second OTA part came through. I accepted. It downloaded, the 75% wait thing happened, it rebooted... It stopped at the famous triangle warning screen. I waited, waited, waited, went to bed and got up. "Hero" it said - it is hung at the Hero screen. I rebooted a few times. Nothing. Stuck. Took the battery out for a few hours, took the SDcard out, swapped SDcard, took out the SIMcard, put them back. Nothing. Hung at Hero screen. So I read a few websites = "Reflash the ROM, you fool". OK, how do I do that? And so I found the two boot methods...
Rebooting with VOL DOWN works - ie it is available but does nothing. FASTBOOT can be seen but does nothing. RESET DEVICE does nothing. HBOOT fails and says no image. USB connection is found by Windows - it appears as a device in Control Panel but reflashing the RUU.exe from the HTC website gets error 170. No connection. Hsync is loaded, says not connected. Obviously I cannor mount it. So I extracted the rom.zip from the official RUU and did the HOME+POWER Android System Recovery sdcard and update.zip malarkey. It found the zip but says "No signature". Now, this is the official HTC ROM from the website, matched to my serial number - extracted from the EXE because the EXE won't work because it won't connect - and it says no signature. I thought that that was impossible. Reading about, I think that that happens when trying to put strange ROMs onto unrooted phones. And I have no idea how to even begin doing stuff like that even if I had an interest in it.
And so I have stopped before I turn the bloody thing into a paperweight. If it is not already one such.
BTW it is under warranty. Should I just send the damn thing back to HTC?
One other message I do not understand is that when I load the system recovery, the first thing that comes up (in yellow, under the blue menu choices) is "E:can't open /cache/recovery/command". I have no idea what that means but it may mean something to somebody. There are no directories like that on the SDcard so I guess that it is referring to the internal memory.
I have tried to give as much info as I can but I am not an Android freak. I am though pretty IT savvy and at a loss to understand what has happened. I think that my phone may be branded to somewhere I do not understand but that does not explain why the official ROM has a signature issue. Or am I just a dim noobie?
Any and all help will be gratefully and humbly accepted. Thanks. Great phone BTW.
And another thing...
I did have a thought that maybe the signature part of the gig resided in a part of the RUU that isn't in the ROM.ZIP and that maybe that is why it is failing. Alas, I have no idea if that is the case or not. If it is the case, I will need advice as to how to make the phone connect to the USB so that I can use the RUU.EXE - which screen would be best etc.
Thanks again.
Are you on Windows 7? If so you may want to find an xp machine as I know people with Windows 7 including me have problems. I use a Windows XP virtual machine.
Good idea
Good idea, Andrew. Thanks. I'll report back.
menelaus said:
Good idea, Andrew. Thanks. I'll report back.
Click to expand...
Click to collapse
It will work, remember to install the HTC SYNC application and enable debugging on the phone. Good luck.
P.S I like your terminology "My Hero is completely unmolested. " lol...
Excellent!
Windows 7 it was, Andrew, thank-you. You are a Genioid. Although I have never had a problem before.
Now, shall I try updating to 2.1 again before restoring all my stuff.... Yes!
Thanks again. Much appreciated.
menelaus said:
Windows 7 it was, Andrew, thank-you. You are a Genioid. Although I have never had a problem before.
Now, shall I try updating to 2.1 again before restoring all my stuff.... Yes!
Thanks again. Much appreciated.
Click to expand...
Click to collapse
Good luck...
Or not.
andrewb84uk said:
Good luck...
Click to expand...
Click to collapse
Well, that was fun. Update failed again with...
can't chown/mod system/xbin
It seems that this is related to having an old SPL. That is all very boring and technical. I am back to my trusty RUU and will wait for a month or two before trying the update again. I have a living to earn.
Thanks for your help, Andrew.
Hey,
I'm a "noob" and not SUPER technically advanced when it comes to phones, but I have a decent idea how to do things with it.
I got an Incredible used from someone and it was already rooted by him. I was told the other night that you need to have the phone unrooted in order to get the official OTA 2.2 update. That night I attempted to unroot it, but turns out I was doing it wrong. I went to bed, and woke up with the OTA update on my phone asking if I wanted to install it, so I said Install Now, and it went to the Boot screen and I dont know if I did something wrong, or it just wouldnt work because my phone was rooted.
So now, 3 days later I've got it Unrooted finally, and I've tried several different update.zip files that I've downloaded from different forums, etc. None of them will work, and they all say Installation Aborted.
Also, when I am in the recovery screen, it says E: Can't open /cache/recovery/command
I've tried several different sd cards thinking that was the problem, and same failure everytime. I have a feeling it is my phone itself..
Any ideas, help, advice??
Greatly appreciated..
bbrown35 said:
Hey,
I'm a "noob" and not SUPER technically advanced when it comes to phones, but I have a decent idea how to do things with it.
I got an Incredible used from someone and it was already rooted by him. I was told the other night that you need to have the phone unrooted in order to get the official OTA 2.2 update. That night I attempted to unroot it, but turns out I was doing it wrong. I went to bed, and woke up with the OTA update on my phone asking if I wanted to install it, so I said Install Now, and it went to the Boot screen and I dont know if I did something wrong, or it just wouldnt work because my phone was rooted.
So now, 3 days later I've got it Unrooted finally, and I've tried several different update.zip files that I've downloaded from different forums, etc. None of them will work, and they all say Installation Aborted.
Also, when I am in the recovery screen, it says E: Can't open /cache/recovery/command
I've tried several different sd cards thinking that was the problem, and same failure everytime. I have a feeling it is my phone itself..
Any ideas, help, advice??
Greatly appreciated..
Click to expand...
Click to collapse
Just download the Verizon 2.2 Froyo update RUU. Run it on your computer with your phone connected and you'll get it. You didn't need to unroot either cause it will automatically zap that.
ejdavis72 said:
Just download the Verizon 2.2 Froyo update RUU. Run it on your computer with your phone connected and you'll get it. You didn't need to unroot either cause it will automatically zap that.
Click to expand...
Click to collapse
Hey, sorry but I don't know what an RUU is, and where/how I get it.. also, I have a macbook, is that a problem?
Thanks!
bbrown35 said:
Hey, sorry but I don't know what an RUU is, and where/how I get it.. also, I have a macbook, is that a problem?
Thanks!
Click to expand...
Click to collapse
I'm not sure if Mac is a problem but I'm sure you can find someone with a PC that will let you use it. I will private message you the link cause xda won't let me post a link here cause I'm too new to the forums. Check your inbox.
I've searched the forum, found some good information but I am still coming up short on getting my phone to normal.
My (Rooted) Hero was perfect until I installed a beta version of Opera Mini Browser and then it went all hinky.
Some of the touch screen keys stopped working and parts of the screen have become unresponsive.. The entire phone (software) is now unstable.
I have tried a Nandroid recovery to no avail.
I've tried the steps available at the below link but still come up short.
http : // developer. htc. com / adp. html
Are there any steps or instructions specifically for the Hero to flash with a new factory image/radio/system?
Also, I'm a little sketchy on fastboot.
Any help would be appreciated. I almost Hulk Smashed the phone but I remembered I got excellent information from this site when I installed my first ROM.
Thank you.
I apologize that my search for this information didn't keep me from making a thread about it.
fix it
just find the latest, or any, RUU.
run that. it'll take everything back to the way it came
try this one: ftp://hero:[email protected]/HTC Sprint Hero MR 2.27.651.6.exe
it's not the Newest, but almost the newest.
http://www.htc.com/us/support/hero-sprint/downloads/
if that doesnt work
rideascooter said:
just find the latest, or any, RUU.
run that. it'll take everything back to the way it came
try this one: ftp://hero:[email protected]/HTC Sprint Hero MR 2.27.651.6.exe
it's not the Newest, but almost the newest.
Click to expand...
Click to collapse
rideascooter said:
http://www.htc.com/us/support/hero-sprint/downloads/
if that doesnt work
Click to expand...
Click to collapse
Agreed, an RUU should fix it
I have tried to update the RUU.
The process starts, the screen on my Hero reads HTC and then nothing.
The installer then displays an ERROR 171 message regarding USB connection.
I guess I should have mentioned that in the first post.
Also I have tried to reflash the current ROM with the same results. The touch screen is dead in certain areas in portrait mode but not landscape mode. The same for the touch keyboard.
Any other suggestions?
RUU doesn't work. The update process starts and then the phone disconnects from the computer.
Easy10pins said:
Any other suggestions?
RUU doesn't work. The update process starts and then the phone disconnects from the computer.
Click to expand...
Click to collapse
have you tried running the RUU from fastboot?
Easy10pins said:
Any other suggestions?
RUU doesn't work. The update process starts and then the phone disconnects from the computer.
Click to expand...
Click to collapse
get a new usb cable... try, try again... patience, yoda...
riggsandroid said:
have you tried running the RUU from fastboot?
Click to expand...
Click to collapse
Can you explain fastboot and how to do it on the Hero?
Easy10pins said:
Can you explain fastboot and how to do it on the Hero?
Click to expand...
Click to collapse
I believe iy is a low level boot menu
I used it to run the ruu when it kept failing the usual way.
To access it poeer off your phone and turn it on while pressing vol up + home and you should see a white screen and it will say fastboot usb. then run the ruu.
It should complete.
hfelton said:
get a new usb cable... try, try again... patience, yoda...
Click to expand...
Click to collapse
I have several different USB cables and have tried them all including the one that came with the phone.
riggsandroid said:
I believe iy is a low level boot menu
I used it to run the ruu when it kept failing the usual way.
To access it poeer off your phone and turn it on while pressing vol up + home and you should see a white screen and it will say fastboot usb. then run the ruu.
It should complete.
Click to expand...
Click to collapse
AWESOME! I knew I could find the answers here. The phone is currently updating.
Now to find a decent ROM to reinstall.
Any suggestions?
Easy10pins said:
AWESOME! I knew I could find the answers here. The phone is currently updating.
Now to find a decent ROM to reinstall.
Any suggestions?
Click to expand...
Click to collapse
Let it finish before you claim victory.
CM6. 1 is good as well as AOSP.
Well did it work?
Froyo Powered HTC Hero
Gentlemen,
Thank you for your assistance. Although I was able to install the latest RUU, the touch screen is still unresponsive. I can't say the phone is bricked but it's pretty much useless at this point.
Everything was good until I installed the beta for Opera Mini mobile. Then things went screwy. Oh well.
Good thing I had all of my apps and data backed up to the SD card so when my Samsung Moment comes in, I can get back up to speed quick.
Thanks again for all of your assistance.
Today I installed my first rom, it was called dl09_supah_clean_04. That worked ok but I could not receive text messages. I thought maybe I'd try another rom. So I downloaded one called hamsters rom. Once I booted the phone up with that rom I got a bunch of errors. So I restarted and now get nothing but the samsung logo flashing. I go into recovery mode, click on update.zip to load clockwork recovery and get a message saying:
e:can't mount /dev/block/vold/179:9
(no such file or directory)
e:can't mount sdcard:update.zip
Installation aborted
I'm just wondering if I am screwed here. I'm about to plug the sdcard into my computer and copy update.zip again in hopes of getting clockwork recovery to work.... just wondering if anyone has any ideas in case this doesn't work.
You need to put it on the phones internal sd card plus sometimes you need to put text message setting yourself like message centres number .
Sent from my GT-I9000 using XDA App
Is this a troll?
mdisaac said:
Today I installed my first rom, it was called dl09_supah_clean_04. That worked ok but I could not receive text messages.
Click to expand...
Click to collapse
That's because you have to install a DL09 kernel and modem as well.
I thought maybe I'd try another rom. So I downloaded one called hamsters rom.
Click to expand...
Click to collapse
How clueless are you?
That's a i9000 ROM. Or Captivate port.
Every single flashing thread warns
DO NOT FLASH ANYTHING NOT SPECIFICALLY FOR THE VERIZON FASCINATE
You flashed a GSM ROM onto a CDMA phone. That's just asking for a brick.
Now download this (and since you can't figure obvious things out, flash it into *PDA* of Odin, NOT NOT NOT NOT NOT "phone"), and pray it works.
THANK YOU, THANK YOU, THANK YOU!!
My phone is back and working on the stock rom. I am definitely clueless when it comes to this but I am not giving up. I am going to get the dl09_supah_clean_04 rom working. I'll be more careful this time though.
Thanks again!
s44 said:
Is this a troll?
That's because you have to install a DL09 kernel and modem as well.
How clueless are you?
That's a i9000 ROM. Or Captivate port.
Every single flashing thread warns
DO NOT FLASH ANYTHING NOT SPECIFICALLY FOR THE VERIZON FASCINATE
You flashed a GSM ROM onto a CDMA phone. That's just asking for a brick.
Now download this (and since you can't figure obvious things out, flash it into *PDA* of Odin, NOT NOT NOT NOT NOT "phone"), and pray it works.
Click to expand...
Click to collapse
not trying to be a d!ck but, you really need to stop before you do brick your phone. read, read, and read some more. its clear you dont understand what your doing and are going to end up screwing up even worse. read EVERYTHING dealing with ONLY the VZN fascinate. if it says anything other that VZN fascinate DO NOT READ IT. your in to big of a hurry and will brick your phone. hell, i have been hacking phones for years and am still not comfortable with android yet. i have rooted but not installed a rom because i dont want to mess it up. hell, i havent even done the new update from VZN. im waiting for more reports to come in. just take your time and read, then worry about flashing to another rom.
If you mess your phone up just use odin and the official stock DL09.md5 to return the phone to normal. Easy.
mdisaac said:
Today I installed my first rom, it was called dl09_supah_clean_04. That worked ok but I could not receive text messages. I thought maybe I'd try another rom. So I downloaded one called hamsters rom. Once I booted the phone up with that rom I got a bunch of errors. So I restarted and now get nothing but the samsung logo flashing. I go into recovery mode, click on update.zip to load clockwork recovery and get a message saying:
e:can't mount /dev/block/vold/179:9
(no such file or directory)
e:can't mount sdcard:update.zip
Installation aborted
I'm just wondering if I am screwed here. I'm about to plug the sdcard into my computer and copy update.zip again in hopes of getting clockwork recovery to work.... just wondering if anyone has any ideas in case this doesn't work.
Click to expand...
Click to collapse
You also need to odin the DL09 modem. or SMS and other things WILL be broken.
1.4hitachi said:
If you mess your phone up just use odin and the official stock DL09.md5 to return the phone to normal. Easy.
Click to expand...
Click to collapse
When people take Odin for granted, they end up with bricks.
Odin can be your friend...as long as you use PDA and not Phone...which is counter intuitive
adrynalyne said:
When people take Odin for granted, they end up with bricks.
Click to expand...
Click to collapse
Shouldn't you say, 'when people use Odin incorrectly"? I mean, as long as he follows the instructions and un-does and kernel changes beforehand the device will be returned back to stock. Also with the official DL09.md5 package it has inside all necessary operating parts. It sounds to me like all he did was attempt a rom flash twice. Odin with the "offical" DL09.md5 will return his Fascinate to stock.
Thanks everybody! I got back to stock and let phone receive the ota update of DL09. Figured that would take care of the kernel and modem and I could install dl09_supah_clean_04. Worked like a champ. I think I learned a lot in this process as well... time will tell.
*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?