Related
Between problems with Clockwork recovery and being unable to read a ROM on my SD card (signature won't verify) has caused me to just stay rooted. If anyone has advice on how I can flash a rom with the above issues let me know.
Could I have screwed up unlocking nand protection?
It sounds like you should stick with the stock ROM.
If you simply follow the directions it isn't difficult.
twin001 said:
If you simply follow the directions it isn't difficult.
Click to expand...
Click to collapse
exactly, which is why "It sounds like you should stick with the stock ROM" will be the best for All of us.
jgarozzo said:
Between problems with Clockwork recovery and being unable to read a ROM on my SD card (signature won't verify) has caused me to just stay rooted. If anyone has advice on how I can flash a rom with the above issues let me know.
Could I have screwed up unlocking nand protection?
Click to expand...
Click to collapse
Why dont you flash stock RUU then follow toast root tutorial 1 and 2?
Your first problem was not using toast method and the more stable recovery. Second is giving up without trying them.
Unrevoked and clockwork are not as functional mostly because the clockwork recovery doesn't properly wipe or devices. This causes serious issues when you go to flash a new rom.
People use them because they are easy and are to lazy to read the thread so don't realize the issues. Then get frustrated when it doesn't work.
Are you rooted yet? If not, I used neckface's step by step method cuz I had problems setting up ADB. It takes a bit longer, but is very straight forward. I also used Amon Ra's recovery(really liked it on my G1) Once you're rooted flashing is easy. Just make sure whatever rom you use to READ all the instructions. Also, make sure your sd card isn't corrupt and that the roms are on the root of your card. Hope this helps, there are alot of benefits to full root and using the great roms they have out for our phones.
I did root toasts method
jgarozzo said:
I did root toasts method
Click to expand...
Click to collapse
Where are you now, i mean only root with no custom recovery?
jgarozzo said:
I did root toasts method
Click to expand...
Click to collapse
Clockwork recovery isn't used with toasts method, it is a modified Amon Ra recovery. If you are rooted, I would go do toasts part 2 again. at the end you will flash the recovery and shouldn't have any problems, make sure you wipe data, davlik cache and cache with that recovery before flashing a new ROM.
Edit: Ok, when I downloaded the files from toasts method 2 wasn't clockworkmod recovery. Thought I better caveat that just in case something changed in the last couple weeks.
jgarozzo said:
Between problems with Clockwork recovery and being unable to read a ROM on my SD card (signature won't verify) has caused me to just stay rooted. If anyone has advice on how I can flash a rom with the above issues let me know.
Could I have screwed up unlocking nand protection?
Click to expand...
Click to collapse
Have you tried formating your sd card i was having problems with my phone not reading the roms on my sd card and formated it and haven't had the problem since.
brandenk said:
It sounds like you should stick with the stock ROM.
Click to expand...
Click to collapse
yeah, i have to agree.. ive unlocked my windows mobile phones but never rooted until i got my evo.. i was a little nervous but the tutorials are very nice and easily explained.. just followed each step one after another without rushing until everything was good to go.. i have no interest in trying out froyo since a few things arent working at the moment but in actuality you wont have any problems if you are just patient.. i only use fresh roms because ive learned thats the rom of my choice, ive tried others but always went back to fresh so basically im just sticking to whatever flipz releases.. most ppl that indupt having issues are those that rushed the latest ota after it is constantly said to just wait for the devs to add it to their roms.. just be patient and follow the directions slowly and you should be good! and dont give up, when you get stuck you can always come to the forums.. ohh and instead of just creating a new thread of the same questions over and over and over again just start reading around because you will read someone having issues that you havent come across yet and when you actually do run into those problems you will already know how to fix them.. heres a fine example to unroot just load the stock RUU, that questions has been asked over and over again yet ppl that like to be spoonfed just create a new topic instead of using the search button.. i wasnt even sure how to unroot until i read the first topic that was created and since then lazy ppl keep asking that question instead of reading.. ppl are hear to help at xda, but it doesnt get annoying helping those that are just plain out lazy! dont give up bro.. just keep reading, we were all newbies at one time
now as to the reason why i quoted.. if your planning on just giving up when you have issues then sticking to stock is really just the best thing to prevent you from getting frustrated
lol, wow I just saw your two other threads you started. If you are having problems, really, just start back from the beginning and start over. Maybe you forgot to wipe, or as someone else mentioned try formatting your sd card, etc.
starting from scratch and I can't get it to read the pc36img.zip file to root
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=715915
Did you do the last update?
agreed. start over and do the Toast1 and Toast2 then install RaAmon. I personally like Flipz ROMs. i followed the steps provide to flash the FreshROM and all went well.
move slowly. if something fails, come back and RTFM before you move on blindly.
good luck.
for more help, i'd suggest you include some amount of detail. most folks out here are looking for help/advice. think of it this way...when you go to the doctor or dentist what do they need to know? what/where/when/how/etc ... you don't ONLY say "doc, i'm broke". you say what is wrong/what did you do, where it hurts, when did it work last, how did you get to this point, etc.
in the same way, if you simply say "i can't make it work"...well, we don't really care. but if you say, "i'm stuck at this point. i tried yadayadayada", then the nerds in this community will be unable to prevent themselves from chiming in. it's part of a nerds personality.
if you have read the documentation and followed it, you should have an idea as to which step failed. let's start there.
starting from scratch
I power off and power on and looks ready to read the PCIMG36.zip (goes 4 lines down) and then nothing. It wont read the file. I have tried a variety of pc36img.zip files and a variety of microSD cards, same result, it doesn't read and the progress bar doesn't show.
re:
I'm going to have to agree with you! I am no programmer or hacker but can follow direction and I have tried many of the different way to root my phone so I could tether it and they are all incomplete, missing some part of the equasion. I was able to tether my instintHD in like 5 mins and I have been messing with this for hours.
Start from scratch and use the simple root app. I would also refrain feom doing nand unlocking as I had problems where I would actually lose privilages with that.
Sent from my Evo 4G using XDA App
jgarozzo said:
Between problems with Clockwork recovery and being unable to read a ROM on my SD card (signature won't verify) has caused me to just stay rooted. If anyone has advice on how I can flash a rom with the above issues let me know.
Could I have screwed up unlocking nand protection?
Click to expand...
Click to collapse
Stick with stock
I recently had to give up my rooted preordered Incredible for a refurb due to heat issues and reboot (loop) issues. For those looking for a guide as to what to do if you have to return your phone to Verizon and want to unroot. I welcome any comments to update/add to this information:
1) Make a NANDROID Backup if you want to simply port it over to your new phone
2) Mount your phone as DISK DRIVE
3) Walk the directories and delete any cached thumbnails of web sites you have visited
4) Copy any pictures you want to keep which were saved on the phone
5) Reboot into ClockWork recovery
6) Wipe the Dalvik Cache
7) Wipe the Data/Factory Reset
8) Go back
9) Wipe Data (main menu)
10) Power Down your phone
11) Remove your SD Card
12) Download one of the RUU's which are hosted around the web:
http://www.shipped-roms.com/shipped/Incredible/
13) Turn on your phone and plug it in to your USB
14) Run the RUU and let it do it's thing. When its done, so are you
15) If you have a screen protector, remember to remove it.
Any additions are welcome!
Yes it will revert everything back to normal, that's called an RUU btw
Cool
Anyone know if this also removes the more hidden data, such as the cached images of the web sites you have visited? In other words, if I run the RUU, is the phone ready to just be handed over?
if i root and uninstall some apps, will this restore my phone to stock and allow me to get all future HTC updates?
jdmba said:
Anyone know if this also removes the more hidden data, such as the cached images of the web sites you have visited? In other words, if I run the RUU, is the phone ready to just be handed over?
Click to expand...
Click to collapse
I don't think so, but it's easy enough to do a wipe and then apply the RUU (and hey, for the hell of it, you could wipe again).
Steps?
[deleted ... first post updated]
I'm pretty sure the RUU will completely wipe your phone. However, you can take giantcrazy's advice and wipe before running the RUU.
One more try
[deleted ... first post updated]
Ok, here is what you want to do.
there would be two things you need to un do before sending them back this phone.
make sure it says S-ON.
and then make sure you have stock recovery.
If you have these two things, your gold bod.
Probably to noob to know any better
After going through a lot of threads this one seems appropriate. I am looking for how to go back to stock DI. After Unrevoked3, ota leak and unofficial froyo leak, my DI wont connect to VZW anymore, all out going calls are busy. Talked to my VZW guys, they are cool with me, tried to help nothin'. Today tried Unrevoked forever and official froyo leak, still no VZW connection. I looked into this a lot before I tried these mods I don't know what went wrong, I would not have been able to do this with out such easy tools as are provided today. "I NEED HELP" to get back to stock, "PLEASE". I have looked into SDK and Adb, as I have been lead to believe there is no way to return to 2.1 and the right radio without these tools. At this moment I have not been able to find clear enough explanations on how to use these tools, this is where I maybe over my head. I assume my radio is fried, I don't care if no "S on", I just need those obvious things; version, kernel, baseband, to be stock. Any help will be appreciated, big thanks for any suggestions
A Lex and Er said:
After going through a lot of threads this one seems appropriate. I am looking for how to go back to stock DI. After Unrevoked3, ota leak and unofficial froyo leak, my DI wont connect to VZW anymore, all out going calls are busy. Talked to my VZW guys, they are cool with me, tried to help nothin'. Today tried Unrevoked forever and official froyo leak, still no VZW connection. I looked into this a lot before I tried these mods I don't know what went wrong, I would not have been able to do this with out such easy tools as are provided today. "I NEED HELP" to get back to stock, "PLEASE". I have looked into SDK and Adb, as I have been lead to believe there is no way to return to 2.1 and the right radio without these tools. At this moment I have not been able to find clear enough explanations on how to use these tools, this is where I maybe over my head. I assume my radio is fried, I don't care if no "S on", I just need those obvious things; version, kernel, baseband, to be stock. Any help will be appreciated, thanks
Click to expand...
Click to collapse
Ok, there is so much here I will do my best.
number one, having s-on is just as important as having a radio thats either 2.15x or 1.x, now that the OTA 2.2 update is sending out, you can send the phone back with 2.2 and 2.15x radio.
what you need to make sure of, is two things, you have s-on,
and you have stock recovery.
ACD168 said:
Ok, there is so much here I will do my best.
number one, having s-on is just as important as having a radio thats either 2.15x or 1.x, now that the OTA 2.2 update is sending out, you can send the phone back with 2.2 and 2.15x radio.
what you need to make sure of, is two things, you have s-on,
and you have stock recovery.
Click to expand...
Click to collapse
Thank you, and really they wont know if the ota was pushed to me? I found the S on tool, I didn't know there was one, I had only read on about S off. I don't know how to find/replace stock recovery, I will start searching though. Much appreciation, my better half is not as thrilled about my learning experience as I am.
I already rooted and unrooted once, will I get stock recovery back after unrooting?
A Lex and Er said:
Thank you, and really they wont know if the ota was pushed to me? I found the S on tool, I didn't know there was one, I had only read on about S off. I don't know how to find/replace stock recovery, I will start searching though. Much appreciation, my better half is as thrilled about my learning experience as I am.
Click to expand...
Click to collapse
Your welcome, I'm happy to see you are learning so quickly. S-on is very helpful for those warranty returns of the phone.
Verizon has no idea whether or not you got the ota, or better yet what version you have or if you are rooted, ect.
If you tell me what your hboot it, radio, software version, s-on or s-off, if rooted or not, and if you have the stock recovery or clockwork and I will try and guide you to where you want to be..
if you need help getting to the stock recovery this must mean you are rooted, and this can be achieved by downgrading the phone by un-rooting, I'd suggest running s-off while you are rooted, then
androidforums.com/incredible-all-things-root/99828-video-howto-unroot-incredible-downgrading.html
sorry can't post links yet,
to help you un-root and get that stock recovery back.
A Lex and Er said:
I already rooted and unrooted once, will I get stock recovery back after unrooting?
Click to expand...
Click to collapse
To find out real fast if you have the stock recovery or clockwork-mod recovery, boot into HBOOT, (power off phone, hold vol down and power til screen turns on) and then vol down to select recovery and push the power button I think to select and then if you get a red triangle that means stock recovery.
Also need to return phone
I just got off with Asurion and they are over nighting a replacement. I had rooted my phone, installed some root only apps like wireless tethering and set cpu, removed some bloat like CityID and Tweet/Peep, and changed the boot animation. No custom ROM or radio update.
Then I wanted to get the OTA update so I applied s-off and flashed back to stock recovery.
So what do I need to do to return this phone. I know I will need to apply s-on. Then should I flash a stock 2.1 or just revert the changes I made to boot animation, restore the bloatware, and remove the root apps? Do I need to remove any other files that go with being root?
Thanks.........MM
ACD168 said:
Your welcome, I'm happy to see you are learning so quickly. S-on is very helpful for those warranty returns of the phone.
Verizon has no idea whether or not you got the ota, or better yet what version you have or if you are rooted, ect.
If you tell me what your hboot it, radio, software version, s-on or s-off, if rooted or not, and if you have the stock recovery or clockwork and I will try and guide you to where you want to be..
if you need help getting to the stock recovery this must mean you are rooted, and this can be achieved by downgrading the phone by un-rooting, I'd suggest running s-off while you are rooted, then
androidforums.com/incredible-all-things-root/99828-video-howto-unroot-incredible-downgrading.html
sorry can't post links yet,
to help you un-root and get that stock recovery back.
Click to expand...
Click to collapse
Hello,
I wanted to thank you again for the help this last weekend. I apologize for not returning for more of the help you offered me. My wife only has every other weekend off and we have an 18mo. old son, both of whom deserved my time more than my DI. I love my DI but it wasn't giving me much love.
Although VZW isn't always the nicest to my pocket book, I have never been taken care of as well by any other provider(s) employees, thank you. As I mentioned in my first post, my VZW guys are cool with me. Yesterday I went into the store and the manager offered to help me. He managed to reconnect my DI to the network but no 3g's. He believes my problem is just a coincidence because he had another customer with a similar problem over the weekend, with no mod's. Still I need to exchange my DI, it doesn't look like 3g's is going to turn on.
My real issue is still getting custom recovery off and stock recovery back on, then unrooting will be a breeze. The videos you lead me to are one of the sources I have been working with, however to reverse the leaked ota, Downgrade leaked ota video, requires SDK and adb knowledge, this is where I am noob. At this time my VZW manager who is in school for programing is attempting to help me (he has a over clocked Palm Pre Plus, 1Ghz), this is very cool of him, well beyond what is expected. (I am in no way encouraging anyone to rely on their VZW employees for this kind of help, this is a unique situation, I have been building a relationship with my VZW guys for two years+, not all VZW employees have a clue about mod's, and mod's technically void the warranty) I am hoping to learn enough about these tools, SDK and adb, to help myself before the next time, and I will hopefully be gaining some of this knowledge from my friends at my VZW store soon. I will also be looking forward to the help I receive from fine people such as yourself and people in this community in future endeavors.
I will stop basically hijacking this thread now
Thanks to all of the people who support these community's, with out whom many of us would never get our foot in the door. Much appreciation to ACD168 for being there to help me.
Take the time and learn to do it right the first time.
A Lex and Er said:
Hello,
I wanted to thank you again for the help this last weekend. I apologize for not returning for more of the help you offered me. My wife only has every other weekend off and we have an 18mo. old son, both of whom deserved my time more than my DI. I love my DI but it wasn't giving me much love.
Although VZW isn't always the nicest to my pocket book, I have never been taken care of as well by any other provider(s) employees, thank you. As I mentioned in my first post, my VZW guys are cool with me. Yesterday I went into the store and the manager offered to help me. He managed to reconnect my DI to the network but no 3g's. He believes my problem is just a coincidence because he had another customer with a similar problem over the weekend, with no mod's. Still I need to exchange my DI, it doesn't look like 3g's is going to turn on.
My real issue is still getting custom recovery off and stock recovery back on, then unrooting will be a breeze. The videos you lead me to are one of the sources I have been working with, however to reverse the leaked ota, Downgrade leaked ota video, requires SDK and adb knowledge, this is where I am noob. At this time my VZW manager who is in school for programing is attempting to help me (he has a over clocked Palm Pre Plus, 1Ghz), this is very cool of him, well beyond what is expected. (I am in no way encouraging anyone to rely on their VZW employees for this kind of help, this is a unique situation, I have been building a relationship with my VZW guys for two years+, not all VZW employees have a clue about mod's, and mod's technically void the warranty) I am hoping to learn enough about these tools, SDK and adb, to help myself before the next time, and I will hopefully be gaining some of this knowledge from my friends at my VZW store soon. I will also be looking forward to the help I receive from fine people such as yourself and people in this community in future endeavors.
I will stop basically hijacking this thread now
Thanks to all of the people who support these community's, with out whom many of us would never get our foot in the door. Much appreciation to ACD168 for being there to help me.
Take the time and learn to do it right the first time.
Click to expand...
Click to collapse
First off, you are very welcome my friend, anything I can do to help do hesitate to ask!, and your not hijacking any thread brother, that's what these threads are for!!!
Thats real cool of the VZW employees!!
adb and sdk isnt that difficult I can help you!!
Read my post about warranty exchange.
I know alot of people are "better safe than sorry" mentality. but I have returned 2 phones that were fully rooted, updated, s-off running custom roms and I had no issues. in fact ive never had an issue using warranty exchange. ive exchanged phones that I broke (like broke.. with pieces coming off). I just call and tell the operator lady my phone doesnt work, i dont know why.. it was just working earlier and now it wont turn on.. they send me a new phone and I send back the broken one and everyone is happy.
They only confirm that the numbers on the phone match your account. Not the reasons you are sending it Back. the warhouse guy that opens your box isnt the same guy you talked to, nor do they have information about your phone call to the tech. They simply open the box, scan the numbers and move on.
dont stress to much about it
Great info here
Thanks to every one of you on this thread. I am finally breaking free from WinMo and getting Dinc after a lot of research. I like Verizon but hate the bloatware they pack onto Androids and all the other phones, so I will be fiddleing with ROMs. If I screw up I am looking here first to see how to get it back to stock so I can get my new one with the insurance coverage.
Everytime I get to serouosly looking around these forums I learn great new stuff. I will donate to the XDA someday soon!
Okay. so im a noob. Just need to ask. What do you guys mean by stock recovery? I just rooted my phone but need to unroot to send it in for work at Verizon. Could you help me out?
Hey, I have 2.1 (Eclair) Wildfire here. Never updated.
Before I root with unrEVOked, I'd like to ask about one thing.
It it possible for it to brick the phone? And if so, at which stage exactly and how can I prevent it?
Could anyone give me an answer?
Rooting and flashing is allmost save. If you follow the guides for rooting / flashing you will go a very save way.
Okay, there is also a liitle chance to brick it. You get a bluescreen while flashing = good chance of a brick (but if this happens there is still a chance to get it back to life). Your cat plays with the usb cable while flashing = also nice way to brick it. Or you just didnt follow the rules of flashing.
If I got this blue screen, how would I go about fixing it?
how to fix your phone or computer?
your computer... dunno.
your Phone...
If you try to flash a custom rom and your pc crashes or something and it fails, try to reflash with a standart www-ruu rom from shipped roms.com.
NEVER use a stock-froyo rom for reflashing!
You have to root again but mosttimes it will work.
I though you meant bluescreen on a phone... I haven't used windows for ages, I got confused.
Bump......
still waiting for goood answer too
Don't root it if you are so paranoid. :/ It doesn't brick the phone at all (Can't see any reports anywhere that Unrevoked bricked 2.1 Wildfires while rooting.)
Obviously, as no thing is 100% certain, there has to be disclosures that "Use it properly else it will be bricked... etc", but, if you follow the proper procedure and use some common sense, its next to impossible.
It's technically possible... Writing the recovery is the dangerous part... But it only lasts 5 seconds..? Something like that, so if the connection breaks (Phone dies, computer dies, usb dies, battery explodes, all of the above) WITHIN that five seconds then you're sc00d. If you're paranoid, don't, and miss out.
---snip---
*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?
Hi, I've been struggling big time to update my device to Android 13. I bought mine when only 1.1.7 hotfix was out and therefore, now that I have unlocked the bootloader (yes, even unlock critical) and rooted the device, I'm not able to install 1.1.8, let alone Android 13. I have already bricked one and managed to get a new one but I don't want to risk it again. I've searched all over Google to a proper guide to update to Android 13, even with sideload, but it gives me an error regarding the payload file, at about 48% of the progress. Tried the *#*#682#*#* method but it stops with error code 20. I have tried flashing the stock boot file but same thing, code 20 from manual update. I'm pretty much desperate at this point and I'm even thinking about unrooting, lock the bootloader again and hopefully update it without an itch, but I really wouldn't want to wipe the device, so, if there's somebody there that could help me through a 100% working process, I'll always be in your debt.
Enzucuni said:
Hi, I've been struggling big time to update my device to Android 13. I bought mine when only 1.1.7 hotfix was out and therefore, now that I have unlocked the bootloader (yes, even unlock critical) and rooted the device, I'm not able to install 1.1.8, let alone Android 13. I have already bricked one and managed to get a new one but I don't want to risk it again. I've searched all over Google to a proper guide to update to Android 13, even with sideload, but it gives me an error regarding the payload file, at about 48% of the progress. Tried the *#*#682#*#* method but it stops with error code 20. I have tried flashing the stock boot file but same thing, code 20 from manual update. I'm pretty much desperate at this point and I'm even thinking about unrooting, lock the bootloader again and hopefully update it without an itch, but I really wouldn't want to wipe the device, so, if there's somebody there that could help me through a 100% working process, I'll always be in your debt.
Click to expand...
Click to collapse
The best part of this whole thing is that you're rooted.
Do a backup with Swift Backup or what ever your backup app you prefer. Wipe it back to stock without locking the bootloader, make sure your sim card is not inserted then do your OTA updates.
As for the second device you bricked, there's a unbrick tool here:
unbrick tool- EDL Flash-Read-Repair Region Change tool
unbrick tool Now available for Nothing Phone1.. Features: Read Firmware (EDL) (locked bootloader) Flash Firmware (EDL) (locked bootloader) backup EFS (EDL) (locked bootloader) Wipe FRP & userdata (EDL) (locked bootloader) Size: 2.7GB Version...
forum.xda-developers.com
Just need to get or make a EDL cable then flash and you'll be back in business.
HermitDash said:
The best part of this whole thing is that you're rooted.
Do a backup with Swift Backup or what ever your backup app you prefer. Wipe it back to stock without locking the bootloader, make sure your sim card is not inserted then do your OTA updates.
As for the second device you bricked, there's a unbrick tool here:
unbrick tool- EDL Flash-Read-Repair Region Change tool
unbrick tool Now available for Nothing Phone1.. Features: Read Firmware (EDL) (locked bootloader) Flash Firmware (EDL) (locked bootloader) backup EFS (EDL) (locked bootloader) Wipe FRP & userdata (EDL) (locked bootloader) Size: 2.7GB Version...
forum.xda-developers.com
Just need to get or make a EDL cable then flash and you'll be back in business.
Click to expand...
Click to collapse
First bricked device was replaced in RMA. But yeah, rooted, unlocked and yet nothing works. I was thinking about wiping it, even if I don't really want to because it's a pain every time. Man, Android modding when to ****e and I'm leaning more and more towards getting an iPhone and call it a day, maybe with a jailbreak
Enzucuni said:
First bricked device was replaced in RMA. But yeah, rooted, unlocked and yet nothing works. I was thinking about wiping it, even if I don't really want to because it's a pain every time. Man, Android modding when to ****e and I'm leaning more and more towards getting an iPhone and call it a day, maybe with a jailbreak
Click to expand...
Click to collapse
Swift does their backups well so from wipe to setup depending on how many apps ya got took like 20 mins to do?
Once you get to A13 tho, my god the battery life is amazing. I don't use my NP1 as a daily driver but it sits in my pocket along with my daily OP7Pro and it out lasts it by a mile. Really hyped for the NP2 and what they bring optimization wise.
Or in your case you could carry both and see how you feel about it xD
Oh and it's likely the patched boot image (while rooted) that's causing the update errors. Once you restore the stock boot image you should be able to update without issue.
HermitDash said:
Swift does their backups well so from wipe to setup depending on how many apps ya got took like 20 mins to do?
Once you get to A13 tho, my god the battery life is amazing. I don't use my NP1 as a daily driver but it sits in my pocket along with my daily OP7Pro and it out lasts it by a mile. Really hyped for the NP2 and what they bring optimization wise.
Or in your case you could carry both and see how you feel about it xD
Oh and it's likely the patched boot image (while rooted) that's causing the update errors. Once you restore the stock boot image you should be able to update without issue.
Click to expand...
Click to collapse
I actually restored it but to no avail. Same errors as described
Enzucuni said:
I actually restored it but to no avail. Same errors as described
Click to expand...
Click to collapse
Welp, back to stock you go then haha ADB it to EDL then run the unbrick tool and you should be at 0
I might be actually lazy enough to wait for a hint of a custom twrp-like recovery and go from there
Enzucuni said:
I might be actually lazy enough to wait for a hint of a custom twrp-like recovery and go from there
Click to expand...
Click to collapse
Might not be stable on first release but yea that's in the rumor pipelines
Yeah, I think I'll wait. A12 is still really nice. Some bugs here and there but perfectly usable and battery is basically infinite.
First of all, to jailbreak the iPhone and set it up correctly with all the needed software that jailbreaking provides nowdays ... is actually harder than it was a few years ago.
Secondly, if you had just read through the full topic containing the Nothing OS repo, you would have found several people with the same problem that u had, who had solved it successfully.
Go back to stock, wipe, and redo the official step-by-step of updating, will work like a charm. if you want to jailbreak. First, read through the posts of others to see if there are any problems that you would like to avoid, and if there are, don't do it.
You are lucky enough to have had your first device replaced by a new one just like that. Updating while rooted was always a problem for Android, and it always varied per device. it was up to the one who is rooting to check the situation regarding his/her specific model
You could try flashing the fastboot ROMs made by @ot_inc (it's not 100% safe for your data so make a backup in any case).
[Restore NothingOS & Magisk] Nothing Phone(1) Fastboot ROM(Full ROM) & boot.img Global v1.1.6
Fastboot ROM and boot.img for NothingPhone(1) are now available. v1.1.6 is available. Sorry for my poor English, I'm Japanese. https://reindex-ot.github.io/
forum.xda-developers.com
kriistofor said:
First of all, to jailbreak the iPhone and set it up correctly with all the needed software that jailbreaking provides nowdays ... is actually harder than it was a few years ago.
Secondly, if you had just read through the full topic containing the Nothing OS repo, you would have found several people with the same problem that u had, who had solved it successfully.
Go back to stock, wipe, and redo the official step-by-step of updating, will work like a charm. if you want to jailbreak. First, read through the posts of others to see if there are any problems that you would like to avoid, and if there are, don't do it.
You are lucky enough to have had your first device replaced by a new one just like that. Updating while rooted was always a problem for Android, and it always varied per device. it was up to the one who is rooting to check the situation regarding his/her specific model
Click to expand...
Click to collapse
Where is the step by step ? The one that actually works ?
hmm, honestly it may be on somewhere in the first few pages (not the first one) but you can also search the google, now there are several sites quoting options for updating nothing phone.
sorry if i sounded harsh
anyways, if you go back to stock, and update the device from 1.1.7 to 1.5 incl. all hotfix updates, it should go smoothly.
I also said if you want to jailbreak in one moment in my post when i meant to say if you want to root.
Rooting nowdays is easy and hard at the same time. easy to pull off, but hard to understand that now there are several different steps that need to be done to turn the rooted device into a fully functional one. and for many it is not worth it, but for those that are interested, I would just advise reading through all the posts carefully and learning to search efficiently. Not only will you find the answer yourself, thus remembering it more clearly, but you will also be introduced to facts you were unaware of.
good luck, the most important step is to go back to stock succesfully, read the whole nothing os repo thread just to make sure you are not missing something
kriistofor said:
hmm, honestly it may be on somewhere in the first few pages (not the first one) but you can also search the google, now there are several sites quoting options for updating nothing phone.
sorry if i sounded harsh
anyways, if you go back to stock, and update the device from 1.1.7 to 1.5 incl. all hotfix updates, it should go smoothly.
I also said if you want to jailbreak in one moment in my post when i meant to say if you want to root.
Rooting nowdays is easy and hard at the same time. easy to pull off, but hard to understand that now there are several different steps that need to be done to turn the rooted device into a fully functional one. and for many it is not worth it, but for those that are interested, I would just advise reading through all the posts carefully and learning to search efficiently. Not only will you find the answer yourself, thus remembering it more clearly, but you will also be introduced to facts you were unaware of.
good luck, the most important step is to go back to stock succesfully, read the whole nothing os repo thread just to make sure you are not missing something
Click to expand...
Click to collapse
Umm.. no, you're not sounding harsh. And I've already done that: "google it" and stuff. This is why I post teh question here. This is not my first time at this lol !
kriistofor said:
hmm, honestly it may be on somewhere in the first few pages (not the first one) but you can also search the google, now there are several sites quoting options for updating nothing phone.
sorry if i sounded harsh
anyways, if you go back to stock, and update the device from 1.1.7 to 1.5 incl. all hotfix updates, it should go smoothly.
I also said if you want to jailbreak in one moment in my post when i meant to say if you want to root.
Rooting nowdays is easy and hard at the same time. easy to pull off, but hard to understand that now there are several different steps that need to be done to turn the rooted device into a fully functional one. and for many it is not worth it, but for those that are interested, I would just advise reading through all the posts carefully and learning to search efficiently. Not only will you find the answer yourself, thus remembering it more clearly, but you will also be introduced to facts you were unaware of.
good luck, the most important step is to go back to stock succesfully, read the whole nothing os repo thread just to make sure you are not missing something
Click to expand...
Click to collapse
You said, "Go back to stock, wipe, and redo the official step-by-step of updating, will work like a charm."
Where are you getting this from ?