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!
Basically I unlocked bootloader and tried to load ROM. I tried the Desire and Cynagen. I was not successful at either. I manage to do a factory reset and the phone is working, except my wi-fi is shot, and when i recieve the initial OTA update it starts to download and then stops and I get the triangle of death as I call it with the lil android guy. I realy dont know what the hell Im doing and I need inch by inch restoring ROM for dummies instruction. I would like to go back to stock.I have been in threads but i get lost on certain things. I dont know what a adb is or how to acess it. I did read the noobies guide.. Please help as I am ready to chuck this thing out the window, i love my N1
I have searched the ORIGINAL SHIPPING TUTORIAL
and one other thread but i guess i cant post links.
please help!!!
do a search for adb for dummies on this site. it should help
Buck Shot said:
Basically I unlocked bootloader and tried to load ROM. I tried the Desire and Cynagen. I was not successful at either. I manage to do a factory reset and the phone is working, except my wi-fi is shot, and when i recieve the initial OTA update it starts to download and then stops and I get the triangle of death as I call it with the lil android guy. I realy dont know what the hell Im doing and I need inch by inch restoring ROM for dummies instruction. I would like to go back to stock.I have been in threads but i get lost on certain things. I dont know what a adb is or how to acess it. I did read the noobies guide.. Please help as I am ready to chuck this thing out the window, i love my N1
I have searched the ORIGINAL SHIPPING TUTORIAL
and one other thread but i guess i cant post links.
please help!!!
Click to expand...
Click to collapse
did you try to load rom in the recovery img? This also happened to me (triangle with the android guy) and I thought I couldnt flash custom roms. For some reason the regular reboot to recovery mode gives me the triangle of death as you call it.
I got around this by loading in into bootloader mode then going to my command console, getting to my skd tools folder, and then typing
fastboot boot (whatever recovery img you used)
Then everything worked perfectly.
They are going to move this to General....
You did not follow the steps correctly it sounds.
Did you Load Amon Ras Recovery?
IF YES,
GO into Recovery
WIPE data
Flash Cyanogen's Latest ROM
Flash Google Apps available on Cyanogen's front page Post
In future ALWAYS nandroid Backup...
If you did not load Amon Ra's Recovery, you should go do this from fastboot.
I'll try to explain it to you:
1. The Bootloader is unlocked (you see the open lock at the first screen)? If you don't see the lock this is the first you should do or send it directly in for repair!
2. Then you have to flash the Recovery ROM (http://forum.xda-developers.com/showthread.php?t=611829) This you need to flash an update.zip Exact instalation guide is in the Link.
3. The ROM. If you want Stock then here you'll find it as an update.zip: http://android.modaco.com/content/g...-online-kitchen-optional-root-insecure-himem/
Choose one without includet Radio ROM!!! (See below why!)
4. Copy the ROM to your SD Card Root
5. Go into Recovery ROM (Vol Down with Power and then select recovery with the Volume button). There you select wipe and choose the first entry there (wipe data and cache)
6. Stay in Recovery ROM and selct Flash from update.zip and select the update.zip. Wait until everything is done and you are promted to reset your N1.
(DON'T MESS AROUND WITH THE RADIO ROM IF YOU DON'T KNOW EXACTLY WHAT YOU ARE DOING. DON'T UNDERSTAND ME WRONG, I THINK YOU HAVE NO GLIMPS WHAT YOU ARE DOING SO BETTER LEAVE THE RADIO ROM ALONE!!! YOU MAY BRICK (DESTROY) YOUR PHONE WITH IT!!! If you dont believe: http://android.modaco.com/content/g...odaco-com/303716/nexus-cannot-on-after-flash/)
7. There should be no 7. Everything should be fine by now.
Hope I could help.
** 100 Posts **
Stheoft u are my hero!!! Now hold do I get the multitouch update? lol sorry
DID YOU EVERY KNOW THAT UR MY HERRRRRRROOOOO
edit: i got it, im back to square one... thanks alot for all ur help
@ Buck Shot, this is a development forum... threads with question shud go in the general forum... these are making the development forum a mess....
Hi all,
I'm expecting my Galaxy S to arrive in the next couple of days, and I have a couple of questions about it.
I'm coming from an HTC Magic which I bought off eBay pre-rooted (see sig), so I'm not exactly up to speed with the process of rooting a phone for the first time.
Firstly, how hard is it to root the SGS? I've seen that it can be done with just an ADB command and an update.zip, is this right? Do I even have to use the ADB command? Is there a way to boot into recovery from the phone itself if I have an SD card I prepared earlier?
Secondly, what's the availability of custom ROMs like? One of the first things I want to do with the phone is nuke all the Samsung crapware from it and take it back to vanilla Android, if possible. The Magic has more ROMs available for it than you can shake a stick at, but I figure that the SGS is a much newer device, so won't have as many around at the moment. Is there anything precluding the production of custom ROMs? I've heard tales of encrypted drivers being the norm for Samsung, which sounds a bit crap.
Thanks in advance guys, I'm looking forward to my new phone (if not the bill for it, heh), and playing around with it in good old XDA fashion... and sorry if these questions have been asked before
whats your reason for wanting to root the phone immediately after you receive it?
I also thought through this, because i did it with my xperia. You can change the samsung touchWiz homepage via LauncherPro app
The only reason i would do it, would be to get froyo on a custom rom, but im going to wait and see if samsung do the good thing and give it to us via an update. As of yet there arent any custom roms for this anyway i dont think
It's easy to root the phone.
Download the update.zip file from this thread: http://forum.samdroid.net/f49/superuser-su-busybox-i9000-v-2-01-07-2010-a-1355/
Or direct link here
Copy the file to the internal storage card of the phone using Kies or whatever method you like.
Disconnect the usb cable
Turn off the phone
Press and hold these buttons at the same time: volume up+home+power, keep them pressed until you see the samsung logo.
Use volume rocker to navigate to update.zip and then press home to select.
Phone will reboot and you are now rooted with superuser.
The whole process takes less than 5 minutes.
I'm not responsible for anything
Cant you just have the latest firmware update added to update.zip?
rooting is only needed for custom roms etc?
TO OP
Rooting the phone is very easy and is a simple as flashing an update zip with SU + busybox with the stock recovery image, quite funny actually that they allow stock recovery to flash any signed zip .
As to the second question i am also very keen to know myself as i believe it should be very easy to create custom roms as i have edited /system directory mutlipul times myself and i believe i have came across a method to get JIT onto our device however i need the help of someone using a linux computer and as a few good skills with android .. PM ME.
sensi_ said:
whats your reason for wanting to root the phone immediately after you receive it?
Click to expand...
Click to collapse
So I can restore all my apps from my Magic... although now that I'm running CM6, that may not be as feasible as it was this morning
Just a stupid question ... do we need to root the phone each time we flash a new ROM ??
Well, given that all the stock ROM needs is a simple update.zip flashing, it looks like the stock bootloader has security off. Like "S-OFF" on the Dream/Magic HBOOT. All you need for root access is the su program and the superuser.apk thing. Awesome.
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?