Database Users

A newbie who screwed up

Hi everybody. I'm Quistnix and I'm a compulsive tinkerer.
Whenever I get my hands on a new piece of hardware, I just have to fiddle with the software. My iPod Touch has been jailbroken, bricked, unbricked, re-jailbroken, broken, repaired and jailbroken. My pc has been running a lot of different editions of Linux and Windows, and has been screwed even more times when I tried to install those.
To the point: I'v got a HTC Magic (32b) and I'm very happy with it. However, I just had to go and put some custom roms on it. I was kinda overconfident and hopscotched from one guide to the other until I got a result I liked. Unfortunately, the end result turned out to be a phone running Android Dev Phone 1, Firmware 1.6 without any backups to restore to.
In it's current state wifi won't run, I don't have root access, Recovery Flasher returns "Flash FAILED.", Terminal won't give me SU rights and it's one of those 'perfect' devices that don't allow fastboot.
Apart from those issues everything seems to work fine, so if it's going to stay like this I'll still end up with a great and perfectly functional phone. Still, I'd like to ask if there is a way to either get it back to its original state, or to make it run a custom rom.
Any help is greatly appreciated.

Quistnix said:
Hi everybody. I'm Quistnix and I'm a compulsive tinkerer.
Whenever I get my hands on a new piece of hardware, I just have to fiddle with the software. My iPod Touch has been jailbroken, bricked, unbricked, re-jailbroken, broken, repaired and jailbroken. My pc has been running a lot of different editions of Linux and Windows, and has been screwed even more times when I tried to install those.
To the point: I'v got a HTC Magic (32b) and I'm very happy with it. However, I just had to go and put some custom roms on it. I was kinda overconfident and hopscotched from one guide to the other until I got a result I liked. Unfortunately, the end result turned out to be a phone running Android Dev Phone 1, Firmware 1.6 without any backups to restore to.
In it's current state wifi won't run, I don't have root access, Recovery Flasher returns "Flash FAILED.", Terminal won't give me SU rights and it's one of those 'perfect' devices that don't allow fastboot.
Apart from those issues everything seems to work fine, so if it's going to stay like this I'll still end up with a great and perfectly functional phone. Still, I'd like to ask if there is a way to either get it back to its original state, or to make it run a custom rom.
Any help is greatly appreciated.
Click to expand...
Click to collapse
have a look at the numerous threads on how to replace the perfect SPL with goldcard method. once you're done with that, replace the recovery, choose a rom and flash.

nmesisca said:
have a look at the numerous threads on how to replace the perfect SPL with goldcard method. once you're done with that, replace the recovery, choose a rom and flash.
Click to expand...
Click to collapse
Thanks a lot, I'll give it a shot tonight

In case somebody else stumbles upon this thread with the same problem:
Using Jester's guide I created a goldcard, and Amon's guide helped me to un-perfect it. After that I could one-click-root without trouble.
I'm currently using the build installed by the ROM v2.16.707.3 from Amon's guide, and it's great.
The only problem left is that I tried to install Amon's [ROM] [32A & 32B] [10-Oct-2009] RAv1.6.2 and got stuck with a never-ending boot screen. This was easily reverted with a backup. I´m going to try installing another rom soon, to see if that helps.

the reason you got stuck in a boot loop is because you didnt wipe your ext partition. you can do that using amon ra's newest recovery. easy peasy lemon squeezy. you need to wipe whenever you flash a new hero rom or any other now now-a-days. do you have adb set up?

edit: Never mind, it's all running beautifully. Thanks!

Soft brick installing GingerbreadlatinIME.zip

I just tried flashing the Gingerbreadime.zip and followed the directions to the letter and I experienced my first soft brick. The phone went into a boot loop at the mytouch screen. Luckily I was able to go into Recovery and restored the backup I had made after rooting and turning s=off. It appears to have restored okay as I still have root etc. Does anyone have any idea how or why this happened ? This zip was posted in Droid-Life and was advertised as good for all android 2.2 devices. I have never used adb but have it set up on my phone so I guess I had better get more familiar with it. I have flashed my Vibrant numerous times using Odin and Rom manager but I don't believe that there is a similar program for the Mt4g (Odin that is) I guess I have been spoiled by my Vibrant as it seems to have more options to recover with and are easier to use from what I can tell. I do love this MT4g though It is probably the best all around phone I have ever owned. Any and all info and help is greatly appreciated.:

to my knowledge there has been no gingerbread port for our device yet. Your lucky you didn't brick your device.

tenbeau said:
I just tried flashing the Gingerbreadime.zip and followed the directions to the letter and I experienced my first soft brick. The phone went into a boot loop at the mytouch screen. Luckily I was able to go into Recovery and restored the backup I had made after rooting and turning s=off. It appears to have restored okay as I still have root etc. Does anyone have any idea how or why this happened ? This zip was posted in Droid-Life and was advertised as good for all android 2.2 devices. I have never used adb but have it set up on my phone so I guess I had better get more familiar with it. I have flashed my Vibrant numerous times using Odin and Rom manager but I don't believe that there is a similar program for the Mt4g (Odin that is) I guess I have been spoiled by my Vibrant as it seems to have more options to recover with and are easier to use from what I can tell. I do love this MT4g though It is probably the best all around phone I have ever owned. Any and all info and help is greatly appreciated.:
Click to expand...
Click to collapse
There are people experiencing the same thing in the Nexus forum. Personally I would stay away from anything that is not specifically built for this phone as its a completely different OS than Vanilla or Moto Droid or etc. etc.

bobsbbq said:
to my knowledge there has been no gingerbread port for our device yet. Your lucky you didn't brick your device.
Click to expand...
Click to collapse
yes I a sure am. I trusted the Dorid-Life site and should not have. Thanks for the swift response...

setzer715 said:
There are people experiencing the same thing in the Nexus forum. Personally I would stay away from anything that is not specifically built for this phone as its a completely different OS than Vanilla or Moto Droid or etc. etc.
Click to expand...
Click to collapse
I sure intend to and I should have got on this forum before I even attempted to flash it. Right now everything seems fine except I cannot get into recovery only clockworkimode recovery. I am holding down the volume down button and pressing the power button at the same time and the device just reboots. Any ideas and what could be causing that? I am embarassed to say that my ignorance that pushed me to flash that zip is probably at the root of it. Any steps that I can take to enable me to get into stock recovery to check and make sure S=off?
Edit: Just pulled battery and sim card and than put them back in and the device went into stock recovery and s=off so I hope that all is okay and I did not create some ghosts that will show up when I attempt to flash a rom later on.

Please post questions in Q&A section.

I did the same thing. I flashed the .zip file from droid life forum and got a success message when I installed it through recovery and mine never bootlooped. I didn't get the gingerbread keyboard but it didn't bootloop either
Sent from my HTC Glacier using XDA App

tenbeau said:
I sure intend to and I should have got on this forum before I even attempted to flash it. Right now everything seems fine except I cannot get into recovery only clockworkimode recovery. I am holding down the volume down button and pressing the power button at the same time and the device just reboots. Any ideas and what could be causing that? I am embarassed to say that my ignorance that pushed me to flash that zip is probably at the root of it. Any steps that I can take to enable me to get into stock recovery to check and make sure S=off?
Edit: Just pulled battery and sim card and than put them back in and the device went into stock recovery and s=off so I hope that all is okay and I did not create some ghosts that will show up when I attempt to flash a rom later on.
Click to expand...
Click to collapse
I think you mean bootloader? You only have 1 recovery. If you flashed clockwork you no longer have stock recovery. Vol Down + Pwr gets you to bootloader or SPL where it shows S=off.

I did not flash the zip (sounds like an overkill to flash a zip for new KB). I ADB pushed both files and got a FC on multi-touch KB... oh well, I like HTC_IME better anyway

tenbeau said:
I sure intend to and I should have got on this forum before I even attempted to flash it. Right now everything seems fine except I cannot get into recovery only clockworkimode recovery. I am holding down the volume down button and pressing the power button at the same time and the device just reboots. Any ideas and what could be causing that? I am embarassed to say that my ignorance that pushed me to flash that zip is probably at the root of it. Any steps that I can take to enable me to get into stock recovery to check and make sure S=off?
Edit: Just pulled battery and sim card and than put them back in and the device went into stock recovery and s=off so I hope that all is okay and I did not create some ghosts that will show up when I attempt to flash a rom later on.
Click to expand...
Click to collapse
make sure fastboot is checked off otherwise you cant get into the bootloader. to make sure it is off go to: menu, settings, applications and uncheck fastboot. you're good to go then. to get into recovery, you can do it thru bootloader or by opening up rom manager and clicking on the "reboot to recovery" option

setzer715 said:
There are people experiencing the same thing in the Nexus forum. Personally I would stay away from anything that is not specifically built for this phone as its a completely different OS than Vanilla or Moto Droid or etc. etc.
Click to expand...
Click to collapse
the website was not specific enough. the port at the current moment is for motorola droid devices. they should have been more specific instead of saying any rooted 2.2 android phone. even if you do get it on your phone, its only going to force close every time you try and type something. thats what happened to me, so after about 24 hours i said **** it and removed it. swype in my opinion is better anyway. im trying to port the g2 swype to our phone so we can have a swype with a mic on the keyboard. oddly, ours didnt come with one.

[Q] A sort of newbie query but...

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.

Clockwork Mod without USB

I know this is possible depending on the phone, but on the Vibrant I have not found a way to install clockwork mod without using USB. I saw that mobile odin was an option for some samsung phones but not the Vibrant.
My usb port is dead, no warranty etc. I bought it for 70 in like new condition with knowledge that the port was bad. I figured that the port needed to be soldered back down. But after taking the phone apart, I don't see anything wrong with it. Its not loose on the board, but the socket itself is loose inside.
The baseband is KA2 Eclair. I got it rooted with the oneclickroot tool.
On a side note, the phone also came with pictures of the seller and all his girlfriends naked . Not pretty

So let me review what you want to do, you want to install CWR without having a USB port. Seems easy enough.
Firstly, find a app that will let you connect to your phone to your computer, apps like Dropbox, Box, and this app i put up on these forums a bit ago will do more than just the job HERE
install one of those, which ever you like. I'll use the MIUI File Manager as a example throughout this post because its the easiest.
Open the app, go to the FTP and start service, go to your computer open MY COMPUTER and type in ftp://all your #'s
Put this file in your ROOT meaning just in sdcard/ no folders just drag and drop it in there. DO NOT RENAME,EXTRACT OR ANYTHING TO THE .ZIP just put it in the sdcard/
*Thanks for the CWR file from Woodrube and S15*
Now go into Recovery mode on your phone
Power + Volume up and down ( i think )
Press REINSTALL PACKAGES
It SHOULD say something like booting into clockwork recovery.
it will reboot, if it goes to clock work recovery, GREAT. If not, press Reinstall Packages AGAIN and it should directly go there.
Just reply if i'm explaining something wrong or if you need more help.

Or you could just download and install rom manager and flash clockworkmod through there. No offense xriderx, just seems like a lot of work to just install cwr that a single app can do as well.

djquick said:
Or you could just download and install rom manager and flash clockworkmod through there. No offense xriderx, just seems like a lot of work to just install cwr that a single app can do as well.
Click to expand...
Click to collapse
To each his own, Rom Manager never has worked great on my phone. Even bricked it completely once and I don't believe it was user error.

Relevant guide, +1 cookie. One suggestion though, organize the steps a bit further so there is a clear distinction between steps.
ie:
• Now go into Recovery mode on your phone, Power + Volume up and down ( i think )
• Press REINSTALL PACKAGES. It SHOULD say something like booting into clockwork recovery. it will reboot, if it goes to clock work recovery, GREAT. If not, press Reinstall Packages AGAIN and it should directly go there."
Anywho, to the OP: Since it's rooted, why aren't you simply downloading ROM Manager from the market and installing CWR from there?
edit/ beaten

Don't get me wrong, your tutorial is spot on, I just never had any problems with ROM manager before so I threw it out as a suggestion.
Sent from my Nexus S using xda premium

working on it now, big thanks!

TheEnternal said:
working on it now, big thanks!
Click to expand...
Click to collapse
As far as the port goes, Eugene, Krylon360 and myself all fried ours when we were porting the V4G - so you may not visibly see anything wrong with it at all.

Thanks guys, I ended up semi bricking the phone . Even though it was my 6th droid device. Not sure what I did, I was in recovery and everything was working, then went to reboot and it was stuck on the Galaxy screen, could no longer get into recovery. Too bad that USB port was out . I ended up just reselling it to a guy for parts and still made some profit off it. Shame though, that AMOLED display was beautiful. Ended up getting a G2X yesterday for 195, just missed one at 150 on craigslist. Already got it up with CM 7.2 with a minor OC. Hopefully towards then end of this year I might be able to get a Galaxy 2 for cheap.

hi.
pls need help.
have the same phone. my usb is not working too.
t-mobile vibrant t959.
its CM7.2 skang-kang flashed.
have issue with mute-unmute.
and need to get it back to froyo.
how to do it without usb?
card slot is working fine.

zukko said:
hi.
pls need help.
have the same phone. my usb is not working too.
t-mobile vibrant t959.
its CM7.2 skang-kang flashed.
have issue with mute-unmute.
and need to get it back to froyo.
how to do it without usb?
card slot is working fine.
Click to expand...
Click to collapse
Download the files you need to your phone and flash them
Sent from my HTC Sensation 4G using XDA

johnson8cyl said:
Download the files you need to your phone and flash them
Sent from my HTC Sensation 4G using XDA
Click to expand...
Click to collapse
i have tried this.
but gingerbread loader and froyo loader are different.
it gave an error at flashing and stopped flashing.

Hmmm. That would require fastboot huh. Don't know of a wireless way to use that. Is there an unroot procedure you could do from your sdcard without a cord and then re-root to gb perhaps?
Sent from my HTC Sensation 4G using XDA

and i'm asking for something like this.
but i ask for froyo not unroot.
to flash from sd card.

it gives an error
Amend scripting (update-script) is no longer supported.
Amend scripting was deprecated by Google in Android 1.5
it was necessary to remove it when upgrading to the clockworkMod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and updare-binary) to create working update zip packages.
installation aborted.

I don't think it is possible to downgrade to froyo from CM7 without ODIN. I might be wrong but that is how i remember it.
Though i did find this thread..
http://forum.xda-developers.com/showthread.php?t=1149158
But i don't know how that worked for people. You might wanna research a little bit more. IMO you are better off going to ICS.

Br1cK'd said:
Just use Odin, don't shortcut it. The OP here has a very very basic idea of the reason and necessity to change these files, and has not provided a complete set of steps in two different "guides" he has posted here, and nobody has been successful as per the reports.
Bottom line, save both yourself and dev in the future a headache, and just use Odin.
Click to expand...
Click to collapse
its very sad ((((

Just a reminder to some who have USB port problems. I'm not trying to insult anyone's intelligence here but remember Samsung phones are picky about USB cables.
I know because my phone was Semi bricked while doing Odin. Turned out my original Samsung cable went bad halfway through Odin'ing a new bootloader. After two months of playing with it I tried literally 5 different data cables that all fully worked for other phones and a few cheap off the street cables. Some would not even charge my vibrant but would work fine for data and charge on my wife's LG Quantum. Hard to find good micro-USB cables here in Peru. Finally I ended up modifying my original cable with another cable's micro-usb connector and wrapping a separate ground wire around the shield to get it to work. Samsung phones must require really good shielding to communicate and possibly not all cables have the shield connected on both sides or are properly shielded.

zukko said:
hi.
pls need help.
have the same phone. my usb is not working too.
t-mobile vibrant t959.
its CM7.2 skang-kang flashed.
have issue with mute-unmute.
and need to get it back to froyo.
how to do it without usb?
card slot is working fine.
Click to expand...
Click to collapse
Check out 'mobileODIN' on the market.

[How-To] Install OTA Update on after Root/Custom Recovery

*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?