Let me first start off by saying that I am on a Mac.
I used these directions to get my phone unlocked and get ClockworkMod Recovery or whatever running on my Nexus S 4G.
I then loaded Cynogen onto my SD card, booted into Clockwork, wiped my phone, then tried to install Cynogen. It failed- it couldn't install boot.img or something.
Now, when I try to boot up my phone, it just shows the Google logo with the unlocked icon below it. It never successfully boots. I can still get into Clockwork Recovery, but below every menu section over the logo, it always shows some error like
Code:
E: failed to something something /cache
Can you guys please, PLEASE instruct me on how to get my phone working normally? I don't need it unlocked, just running the stock OS.
Anyone who can successfully help me do this on a Mac will receive a nice PayPal donation if they wish.
Thank you so much in advance.
And yeah, I know I shouldn't have been attempting this because I am such a n00b.
westinl said:
Let me first start off by saying that I am on a Mac.
I used these directions to get my phone unlocked and get ClockworkMod Recovery or whatever running on my Nexus S 4G.
I then loaded Cynogen onto my SD card, booted into Clockwork, wiped my phone, then tried to install Cynogen. It failed- it couldn't install boot.img or something.
Now, when I try to boot up my phone, it just shows the Google logo with the unlocked icon below it. It never successfully boots. I can still get into Clockwork Recovery, but below every menu section over the logo, it always shows some error like
Code:
E: failed to something something /cache
Can you guys please, PLEASE instruct me on how to get my phone working normally? I don't need it unlocked, just running the stock OS.
Anyone who can successfully help me do this on a Mac will receive a nice PayPal donation if they wish.
Thank you so much in advance.
And yeah, I know I shouldn't have been attempting this because I am such a n00b.
Click to expand...
Click to collapse
What version of CWM did you flash?
Pm me and we will use a chat service (aim, yahoo messenger) and I will walk u through it.
My suggestion of what I would do is this. Find a windows computer somehow. Go to the development section and look for the sticky about rooting the ns4g. Look for the link to flash the d720 back to stock. Download all those files to a flash drive. Take the drive to the windows computer and set things up then flash the phone back to out of the box stock.
Then you can go back to the Mac and do the root and 3024 cwm recovery and rename the sh file that puts stock recovery back in at boot time. After all this you can do what you want but I would suggest staying with the stock experience. This might be extreme to fix this but in my opinion, I wouldn't waste time trying to fix it, especially since you are new to this. It's like computers, yeah you could try to fix it but you could be opening a can of worms. It might take less wasted time putting it back to complete stock instead of f-ing around trying to figure out what happened and how to fix it. You could take hours trying to fix an install of windows that keeps falling on it's face, or you could format and install windows fresh and new in maybe thirty minutes. Which is easier?
CM7 will not work at the moment because it still uses 2.3.3, go find instructions for a 2.3.4 Nandroid. if you want though,i heard that supeaosp works on a ns4g.
Sent from my Nexus S using XDA App
westinl said:
Let me first start off by saying that I am on a Mac.
I used these directions to get my phone unlocked and get ClockworkMod Recovery or whatever running on my Nexus S 4G.
I then loaded Cynogen onto my SD card, booted into Clockwork, wiped my phone, then tried to install Cynogen. It failed- it couldn't install boot.img or something.
Now, when I try to boot up my phone, it just shows the Google logo with the unlocked icon below it. It never successfully boots. I can still get into Clockwork Recovery, but below every menu section over the logo, it always shows some error like
Code:
E: failed to something something /cache
Can you guys please, PLEASE instruct me on how to get my phone working normally? I don't need it unlocked, just running the stock OS.
Anyone who can successfully help me do this on a Mac will receive a nice PayPal donation if they wish.
Thank you so much in advance.
And yeah, I know I shouldn't have been attempting this because I am such a n00b.
Click to expand...
Click to collapse
Dude, you can't flash regular Nexus S ROMs on the Nexus S 4G.
Reflash the latest clockwork recovery.
Use fastboot flash recovery recovery.img
then...
Go to recovery, mount the USB storage, and put this zip on the usb storage:ROM
Go to recovery and flash that zip
here's the recovery that works. cwm and stock. How many times is this going to happen with new people and this phone in this forum section before a new subsection is made? We are going to be putting out a lot of these unnecessary fires with people making first time mistakes until something is done so as to not confuse them. Some don't realize that there are different versions of the same phone that aren't necessarily compatible with each other.
The way things are set up now, it isn't making this problem go away. I think that a different method should be tried if the current one isn't working too well. I'm flogging a dead horse now......
I'm looking to root my new NS4G as well -- and do it right the first time. On a Mac as well.
If the similarly-suited OP had issues I'm a bit more skeptical about my effort.
A separate forum might be necessary so people with the D720 hardware don't have near-brick experiences.
Sent from my PC36100 using XDA Premium App
soooo....did the op ever get it running again? i wonder if anyone ever took up on his paypal offer
You know the guy I'm talking about: while he's sitting in the VD clinic with an itchy crotch, he's praying to God: "Oh God, please don't let it be herpes. If it's not herpes I swear I won't visit another whorehouse as long as I live."
Then, as soon as the doctor announces that he's just got a case of jock itch and he should put some anti-fungal on it, the guy runs to the whorehouse to celebrate....
Because, see, just a few days ago I semi-bricked my Evo running after a failed Unrevoked. Not sure why it failed, but the phone would lock up every 15 seconds. So I flashed a stock image to repair the damage, and then a newer one, and wound up with a phone that worked except it wouldn't read the SD card or USB port (charging would only occur if the phone was turned off).
So as I was working my way through the fix I kept promising myself that if I got it fixed I'd just keep it stock unrooted and be happy with it.
Then, thanks to the good fold here, I managed to get the device running again the way it should. Wheeew, I thought, I'm happy now.
But... of course... it only took a few hours before the "root" itch hit me again. Fixing the semi-brick issue required installing z4root, and that app gave me a taste of da root acces... and ooooh did it taste goooood! Problem with z4root, though is that you're still s-on, and it's my understanding that if you're s-on and take the new GB update, you're SOL (at least for the time being). And I wanted to be s-off for the peace of mind it offered.
So my desire for real permanent root got the better of me. I decided that the reason unrevoked had failed for me the first time probably had something to do with all the cr*p I had installed on my phone. So I used Titanium backup along with z4root to back up the stuff I'd installed since getting my phone back and re-flashed the stock 2.2 image that had worked for me, and started with afresh phone.
Tried unrevoked one more time and... viola! It worked!!!
I'm happy now... a happy, unrepentant sinner!
Anyway, if you've read through all this: bless you.
I do have a couple of questions:
1) Am I correct that being s-off means I can now install unsigned ROMs the same way I installed the stock image I am on? (basically, rename it PC36IMG.zip, put it on the root of the SD card and boot into the bootloader and let it install)?
2) do I need to run "unrevoked forever"? I'm not clear on this. Getting some conflicting information from searching. My best guess, from what I've read, is that the latest unrevoked includes all the stuff that unrevoked forever does.
-Is blessed-
1. You don't need to make a PC36IMG to flash a rom; just download the file, then backup your current rom, do a full wipe, then flash the rom zip
2. You don't need to flash the forever zip; it was used to give you nand unlock -s-off- in the older versions of unrevoked, and was incorporated into the new one.
And keep applying that jock itch.
And once you flash a couple roms, you will get the itch to start using the kitchen and playing with your own custom rom, its only a matter of time, lol
I probably try two a week now. Its amazing how much work these guys do.
Unrevoked forever is incorporated in Unrevoked now. So need for that.
Also, you dont flash them in the bootloader. Boot into the bootloader, then use volume down to go down to the option that says "recovery" then use the power button to select. It will boot into recovery menu which should have a list of options, go down to flash zip from sdcard, then select zip from sdcard. It will show you a list of everything on your sdcard. Navigate to wherever your rom .zip file is that you downloaded and select it. It will ask you if you want to flash, select yes.
PS dont forget to wipe before you flash. ("Wipe all user data/factory reset" option when your in recovery.)
RileyGrant said:
Unrevoked forever is incorporated in Unrevoked now. So need for that.
Also, you dont flash them in the bootloader. Boot into the bootloader, then use volume down to go down to the option that says "recovery" then use the power button to select. It will boot into recovery menu which should have a list of options, go down to flash zip from sdcard, then select zip from sdcard. It will show you a list of everything on your sdcard. Navigate to wherever your rom .zip file is that you downloaded and select it. It will ask you if you want to flash, select yes.
PS dont forget to wipe before you flash. ("Wipe all user data/factory reset" option when your in recovery.)
Click to expand...
Click to collapse
OK, so that's pretty much the same as with the Nook flashing Phiremod (a Cyanogenmod variant).
Hi there,
I had been umming and arring about rooting and installing a new ROM one of my familys HTC Heroes for some time now and finally after reading lots of "How to's" on lots of different forums I decided to take the plunge and give it a go using the guide on here.
Both my wifes phone and my sons phone are sim unlocked Orange HTC Heros running 2.1-Update 1.
Rooting it was easy. One press of a button and I was there. Its pretty much worked OK and I have sucessfully made three backups of the wifes Hero.
My main query and this is the bit I have not really been able to find much info about despite spending a day trawling through the forums looking for similar queries is this:
Having flashed my recovery image file, the first time I reboot I can get into the recovery mode just fine. From here I can make a backup of the current ROM after which the Hero reboots and goes back into the OS as it should.
If I then shut it down and reboot using the HOME key + POWER option It does not go into the recovery mode. I get the screen with an image of the phone next to a red triangle with an exclamation mark in it.
Using the advice from various forums whilst searching for further advice / hints I have left the phone for up to half an hour but it stays on this screen. The only way to get it out of this screen it to pull the battery.
If I then boot up the phone and reflash the recovery image, I can then get into the recovery mode once again but for ONE BOOT ONLY.
I have tried AmonRA Revcovery v1.7.01. and also the Clockwork Recovery 2.5.0.7 images and both produce the same results. I have tried flashing the images via ROM Manager and also via Android Terminal Emulator
My question is this: Do I have to flash the recovery image EVERY time I want to open the recovery mode or is there something I have missed? At present I have held back from installing a new ROM in case I go past a point of no return where I brick the phone. Neither my wife or son would be too pleased despite my son wanting a better ROM on his.
Apologies for writing "War and Peace" but I wanted to make sure I had covered all I could and hope this is a) not a query already posted elswhere which I have missed b)posted in the right place. Apologies to any forum mods if its not.
Regards
Rhinestone.
hmm look on the unlokr.com or something like that. They use some simple passes and it's the way i did it. the on;y difference is that my phone wasn't blocked on a carrier...
1.there is a program that roots the hero's rom
2.after that i recommend installing clockwork recovery mode (it doesn't need signed zips)
3.if you don't feel safe doing this, i recommend to stop... I know that the 2.1 rom is boring but you can end up with a bricked phone after this...
The official 2.1 update has a script that reflashes the stock recovery every time the phone is shut down.
Hunt about for a modified 2.1 rom, all of them have had that script removed. I'm not a huge fan of sense now, but when I did use it, I found villainrom to be a good 2.1 sense rom.
TheReverend210 said:
The official 2.1 update has a script that reflashes the stock recovery every time the phone is shut down.
Hunt about for a modified 2.1 rom, all of them have had that script removed. I'm not a huge fan of sense now, but when I did use it, I found villainrom to be a good 2.1 sense rom.
Click to expand...
Click to collapse
This, just flash a custom ROM and it will stick.
Hello,
Problem might be with rooting, possible it has not been rooted completely or anything messed up. You can try this for rooting.
http://unrevoked.com/
If you are sure its rooted completely, then check out Superuser apps, if its there, and you are rooted, if not then download terminal emulator and type "su" command, if its doesnt display any error then its rooted.
Other then this,
problem might be with the recovery images you are flashing, download droid explorer its a window application, its has an option of flashing recovery with one click, simply choose recovery image & flash it, clockmod recovery or amonr any of this you can get in xda.
Ok, i realize i have a different phone from this thread but it is close and my problems closely reflect the issues ive seen with the Galaxy S.
A little background. Im no perfect i know what im doing when it comes to rooting. I have an HTC Tbolt and rooted many of those, an older touch pro 2, and this is first time doing a samsung. I am getting the hang of ODIN (i wish everyone would just use this program instead of bouncing back and forth between heimdall and ODIn but whatever) Im liking ODIN cause it works well. I was successful at flashing a new rom into this Samsung phone. 95% of it worked, wifi i think didnt but everything else worked. While trying to fix the phones wifi somehow i have stopped the phone from booting into CMW recovery unless forced or booting into a rom. I can get into CMW but i must hold down the Vol Down button to get there, otherwise a clean basic boot takes me to the stock android system recovery screen and will not boot a rom.
I have something backwards or out of order. I am just trying to get the rom to identify the installed CMW and the installed ROM through CMW but it wont do it.
Any help would be appreciated, i dont want my GF to find out i jacked her phone lol
Which phone do you have? SGS? I can just talk about SGS+ but I guess its similiar.
Try to install CWM with Odin, normally it should replace the stock recovery (haven't heard of both running at once).
Once you have installed CWM you can install your custom ROM with CWM (look at the install instructions).
If you want to install stock ROM with Odin it will replace your CWM with stock Recovery.
Post the link of the thread/recovery you want to flash.
annqx said:
Which phone do you have? SGS? I can just talk about SGS+ but I guess its similiar.
Try to install CWM with Odin, normally it should replace the stock recovery (haven't heard of both running at once).
Once you have installed CWM you can install your custom ROM with CWM (look at the install instructions).
If you want to install stock ROM with Odin it will replace your CWM with stock Recovery.
Post the link of the thread/recovery you want to flash.
Click to expand...
Click to collapse
Its a stratosphere. Im using the root and / or stock files in the root method. I use ODIN to flash the StratCWMRecovery.tar.md5 and if i tick "reboot" then it reboots into CWM i install a rom or stock rom and it finishes. I reboot the phone and it instantly goes back to android system recovery. If you like ill make a short video to give you an idea of whats going on.
I will note that im close to making a jig but its not 100% bricked obviously. 3 button method still works (and unecessary at this point since all the phone does is go straight into the stock bootloader) and then after i install CWM i can force it in to CWM but it wont actualy boot into it.
From a programing standpoint i feel the pointers or partitions are incorrect. Its like booting a computer that has a hard drive with windows installed however getting the bios to tell it to boot from the hard drive isnt working. THats the easiest way to explain this.
One thing i want to note is the only errors i am getting are when i try to partition the SD card from CWM. I get an error saying sdparted is not found.
I am not getting a full understanding of how the root system works on this phone.
Again any help is appreciated.
Made a short video. Its uploading now. http://www.youtube.com/watch?v=tFZ5Adm5AdQ
So whatever i did i was able to fix. I think me being a very visual person and normally having access to all files i need or could use in a situation is always nice. Here, i didnt but i found them. Here's the link. Its obviously for stratosphere but i took about 10 minutes and let ODIN install all these files and it worked.
original posting but the link doesnt work for download
http://rootzwiki.com/topic/11183-eh2-full-factory-odin-restore/
where i downloaded it
http://www.fileswap.com/dl/t4D235pUTO/SCH-I405.EH2_rel.md5.html
Again this is for stratosphere. Since it really helped me return to stock and allow me to re root in about 15 minutes this thread should be moved but there is no stratosphere area
*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?