Related
I tried sending my Incredible to Amazon, but they sent it back saying they couldn't get the data to reset.
How do I get my Incredible all the way back to stock? It currently has s-off. I want it unrooted, s-on, just like it's new.
Thanks!
You'll need to flash a stock ROM (known as an RUU). You'll have to Google around to find it (you might be able to find some on here even). You'll then need to rename it to something like PG05IMG.zip (the download page for the RUU file should specify which filename to use).
You'll put the RUU .zip file in the root of your SD card and then you'll boot into HBOOT where it should automatically flash it.
I've never done it before, so there might be someone else who can help you even more. This will just get you started.
Does this seem like what I should do?
http://forum.xda-developers.com/showthread.php?t=1227279
zipzoomeroo said:
Does this seem like what I should do?
http://forum.xda-developers.com/showthread.php?t=1227279
Click to expand...
Click to collapse
Yes, that is the proper step. If that link does not work for whatever reason. Download the RUU from this website:
pvillecomp.com
I am not sure about how to go s-on. I do not want to provide false information about that. I am sure someone can explain that step.
Before using the steps found on the link above, you will need to flash the s-on patch found on the unrevoked forever site. If you ruu before going s-on, you would have to flash clockwork recovery again, apply the s-on patch, and then run the ruu again. Also after you finish the ruu i would do a factory reset and wipe the emmc and sdcard.
Thank you, I appreciate the information cmlusco
cmlusco said:
Before using the steps found on the link above, you will need to flash the s-on patch found on the unrevoked forever site. If you ruu before going s-on, you would have to flash clockwork recovery again, apply the s-on patch, and then run the ruu again. Also after you finish the ruu i would do a factory reset and wipe the emmc and sdcard.
Click to expand...
Click to collapse
Thanks for this info.
Sent from my Galaxy Nexus using XDA App
I wanted to flash LeeDroid's rom. After I flashed the boot image I realized that I haven't put the rom into the root of the phone's storage! silly me. I tried rebooting the system but it won't boot. Then I tried the unbrick methods on the forum but found no luck. At last I tried relocking it and restore it using RUU but it still won't work! It is saying that I got the wrong version of RUU, but where can i find the RUU for 1.28? Hope someone can help!!
chowdyg said:
I wanted to flash LeeDroid's rom. After I flashed the boot image I realized that I haven't put the rom into the root of the phone's storage! silly me. I tried rebooting the system but it won't boot. Then I tried the unbrick methods on the forum but found no luck. At last I tried relocking it and restore it using RUU but it still won't work! It is saying that I got the wrong version of RUU, but where can i find the RUU for 1.28? Hope someone can help!!
Click to expand...
Click to collapse
What country are you in, which network are you on and did you buy your phone sim free?
If you go into fastboot mode and then boot into CWM using the command:
fastboot boot <CWM img file>.img
You'll then be able to use adb to push the rom zip onto your device which you can then flash with CWM.
If the RUU says you have the wrong version you probably have the RUU for another region/carrier.
It's pretty much impossible to permanently brick the one x (without s-off) so don't worry, you'll get it working eventually.
Thanks man. I am in Hong Kong and i am pretty sure it is sim free. after I tried running the RUU i have relocked the bootloader. for some reason I can't even get into recovery right now! When I try the RUU it saids the image version is 1.28.708.10 and I get error140
chowdyg said:
Thanks man. I am in Hong Kong and i am pretty sure it is sim free. after I tried running the RUU i have relocked the bootloader. for some reason I can't even get into recovery right now! When I try the RUU it saids the image version is 1.28.708.10 and I get error140
Click to expand...
Click to collapse
Which RUU did you download?
rogersnm said:
Which RUU did you download?
Click to expand...
Click to collapse
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_HK_1.26.708.2
I guess it is not the right one is it
chowdyg said:
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_HK_1.26.708.2
I guess it is not the right one is it
Click to expand...
Click to collapse
You can't install the 1.26 RUU after you've updated hboot with the 1.28 OTA.
Try installing this RUU: http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.103.14_release_257077_signed.exe, it's the same region but a newer version.
Flash the stock 1.28 recovery image and relock your bootloader before trying to install the RUU.
The 1.28 recovery image can be found here: http://hoxroms.serveftp.com/Asia_1.28_RUU/recovery_signed.img
rogersnm said:
You can't install the 1.26 RUU after you've updated hboot with the 1.28 OTA.
Try installing this RUU: http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.103.14_release_257077_signed.exe, it's the same region but a newer version.
Flash the stock 1.28 recovery image and relock your bootloader before trying to install the RUU.
The 1.28 recovery image can be found here: http://hoxroms.serveftp.com/Asia_1.28_RUU/recovery_signed.img
Click to expand...
Click to collapse
Thanks so much!!
but i have already relocked the bootloader without flashing the recovery image ... would that make a difference?
If the RUU runs successfully then don't worry about it, if it throws another error then flash the stock recovery and try again.
rogersnm said:
If the RUU runs successfully then don't worry about it, if it throws another error then flash the stock recovery and try again.
Click to expand...
Click to collapse
Thanks again. but how do i do it with the bootloader locked
chowdyg said:
Thanks again. but how do i do it with the bootloader locked
Click to expand...
Click to collapse
Just unlock it by running "fastboot flash unlocktoken Unlock_code.bin" like you did before and then relock it after
rogersnm said:
Just unlock it by running "fastboot flash unlocktoken Unlock_code.bin" like you did before and then relock it after
Click to expand...
Click to collapse
now it is saying error 170. whenever i try to flash something it just says waiting for device
chowdyg said:
now it is saying error 170. whenever i try to flash something it just says waiting for device
Click to expand...
Click to collapse
Disconnect and reconnect your phone, reboot your phone and your pc, try again.
ps. Make sure you relocked your bootloader
rogersnm said:
Disconnect and reconnect your phone, reboot your phone and your pc, try again.
ps. Make sure you relocked your bootloader
Click to expand...
Click to collapse
Thank you so much!! problem solved!!
I need an HTC One M8 Telus/Koodo RUU for my phone. I flashed GPE Rom and it works great but i want the 5.0 update of my carrier but i can't flash it because i am on a custom rom so i would like to revert back to stock in order to flash the 5.0 update.
Any help or suggestion would be appreciated
marawan31 said:
I need an HTC One M8 Telus/Koodo RUU for my phone. I flashed GPE Rom and it works great but i want the 5.0 update of my carrier but i can't flash it because i am on a custom rom so i would like to revert back to stock in order to flash the 5.0 update.
Any help or suggestion would be appreciated
Click to expand...
Click to collapse
Go back to stock, and take the OTAs. Then re-root and enjoy your new firmware.
Visit this thread:
http://forum.xda-developers.com/showthread.php?t=2701376
or this thread:
http://forum.xda-developers.com/showthread.php?t=2710735
I cant do that because i am not s-off
marawan31 said:
I cant do that because i am not s-off
Click to expand...
Click to collapse
Incorrect. This is the method that you use if you are not S-Off.
If you were S-Off, you would just update firmware manually, with no need to go back to stock.
thanks for your help!
ok the second link you posted led me to a canadian nandroid backup.
thanks a lot for your help man
Edit: my hboot is 3.18 and its the only one missing
what should i do?
marawan31 said:
thanks for your help!
ok the second link you posted led me to a canadian nandroid backup.
thanks a lot for your help man
Edit: my hboot is 3.18 and its the only one missing
what should i do?
Click to expand...
Click to collapse
I would suggest asking if anyone has a link to one in that thread.
I'm on Telus too, but I am running WWE firmware. I ALWAYS have the new firmware before Telus. Just sayin.
S-Off is a good thing to have. I know it seems like $25 is a lot to pay to get it, but if you think of all the hassle it saves trying to update firmware, and the other freedom it gives you (I'm using the Sprint Harman/Kardon version's audio files and ADSP) it is very reasonably priced.
xunholyx said:
I would suggest asking if anyone has a link to one in that thread.
I'm on Telus too, but I am running WWE firmware. I ALWAYS have the new firmware before Telus. Just sayin.
S-Off is a good thing to have. I know it seems like $25 is a lot to pay to get it, but if you think of all the hassle it saves trying to update firmware, and the other freedom it gives you (I'm using the Sprint Harman/Kardon version's audio files and ADSP) it is very reasonably priced.
Click to expand...
Click to collapse
i just flashed the one saying 3.x. its a 5.0 nandroid backup and all is working except wifi for some weird reason. looks like the firmware wasnt updated.
i have nothing against paying 25$ its just that sunshine never worked for me. It always said it didnt like my kernel and that i should try with a stock and i was too lazy tbh
marawan31 said:
i just flashed the one saying 3.x. its a 5.0 nandroid backup and all is working except wifi for some weird reason. looks like the firmware wasnt updated.
i have nothing against paying 25$ its just that sunshine never worked for me. It always said it didnt like my kernel and that i should try with a stock and i was too lazy tbh
Click to expand...
Click to collapse
Use 3.34.661.4 backup for 4.4.4 but wifi will not work on your device yet because you have hboot 3.18.0000
Find the 2.23.661.2 -> 3.34.661.4 - thanks @shaboobla on this thread : http://forum.xda-developers.com/showthread.php?t=2701376
Extract out firmware.zip from that OTA zip (with 7-zip)
then you can flash this firmware in RUU mode (but you need to relock bootloader because your device is S-On)
Later .. you can check software update and accept OTA to 4.20.661.2
ckpv5 said:
Use 3.34.661.4 backup for 4.4.4 but wifi will not work on your device yet because you have hboot 3.18.0000
Find the 2.23.661.2 -> 3.34.661.4 - thanks @shaboobla on this thread : http://forum.xda-developers.com/showthread.php?t=2701376
Extract out firmware.zip from that OTA zip (with 7-zip)
then you can flash this firmware in RUU mode (but you need to relock bootloader because your device is S-On)
Later .. you can check software update and accept OTA to 4.20.661.2
Click to expand...
Click to collapse
how would i flash a firmware in RUU mode? you mean like renaming it to some weird name like PG.... and placing it in root of sdcard and going in fasboot? or is it something else because tbh i have never heard of flashing something in RUU mode
thanks for your help, really appreciate it.
EDIT: I just found out i can go to RUU mode with "fastboot oem rebootRUU".
so i can flash the firmware with "fastboot flash zip firmware.zip"
thanks again for all your help guys
marawan31 said:
how would i flash a firmware in RUU mode? you mean like renaming it to some weird name like PG.... and placing it in root of sdcard and going in fasboot? or is it something else because tbh i have never heard of flashing something in RUU mode
thanks for your help, really appreciate it.
EDIT: I just found out i can go to RUU mode with "fastboot oem rebootRUU".
so i can flash the firmware with "fastboot flash zip firmware.zip"
thanks again for all your help guys
Click to expand...
Click to collapse
You found it
1. Make sure you restore the 3.34.661.4 backup first and reboot
2. Boot to bootloader
3. relock bootloader - fastboot oem lock
4. flash the firmware in RUU mode
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip <---- again for the 2nd time
fastboot reboot
5. check software update
6. accept, download, install
7. done
Flash TWRP 2.8.5.0 if you want to flash a custom ROM
ckpv5 said:
You found it
1. Make sure you restore the 3.34.661.4 backup first and reboot
2. Boot to bootloader
3. flash the firmware in RUU mode
fastboot oem rebootRUU
fastboot flash zip hbootMOD3.zip
fastboot flash zip hbootMOD3.zip <---- again for the 2nd time
fastboot reboot
4. check software update
5. accept, download, install
6. done
Flash TWRP 2.8.5.0 if you want to flash a custom ROM
Click to expand...
Click to collapse
You renamed the firmware to hbootMOD3.zip? or do i also need to flash the hboot? if so which hboot do i flash?
lol sorry im easily confused
marawan31 said:
You renamed the firmware to hbootMOD3.zip? or do i also need to flash the hboot? if so which hboot do i flash?
lol sorry im easily confused
Click to expand...
Click to collapse
Ahh.. sorry ... I was in a hurry ... just copy paste from my own note that meant for my personal modded firmware. Edited the post.
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip <---- again for the 2nd time
fastboot reboot
ckpv5 said:
Ahh.. sorry ... I was in a hurry ... just copy paste from my own note that meant for my personal modded firmware. Edited the post.
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip <---- again for the 2nd time
fastboot reboot
Click to expand...
Click to collapse
oh ok thanks man!!
ill post back with the result
marawan31 said:
oh ok thanks man!!
ill post back with the result
Click to expand...
Click to collapse
Just don't forget to relock bootloader before flashing firmware.zip
fastboot oem lock
ckpv5 said:
Just don't forget to relock bootloader before flashing firmware.zip
fastboot oem lock
Click to expand...
Click to collapse
yea i was going to do it and also for the sake of completeness flashing the stock recovery(3.34.661.4) after the restore, just in case someone else has the same problem
You can do that but not really needed because the signed firmware.zip will restore stock recovery.
ckpv5 said:
You can do that but not really needed because the signed firmware.zip will restore stock recovery.
Click to expand...
Click to collapse
oh didnt know that, i guess i wont then
I just wanted to thank you guys for helping me out!
I did everything and now i am on android 5.0.1 (although i ran into a small problem: process com.android.phone is not responding, factory reset from recovery fixed it)
Hope this thread helps someone else with similar problems
https://photos.google.com/album/AF1QipNmb1q2tT6uldWZLHQSLD1fsauQYRMlkHmA5y1g/photo/AF1QipPXGvhZ063BpX0f30U4O7d6ZYQgTkgeowCWDywd
Sorry for reviving such an old thread, but I'm trying to get my htc one m8 up and running again. It was functioning on lineage os but wasn't very stable, couldn't find any other roms that would successfully flash on it, I decided to try and go back to stock after a few beers one night night, now the phone has been sitting in a drawer with no os or recovery on it. There doesn't seem to be any still functioning links to any Canadian RUU's that I can use. I'm not s-off, bootloader is "relocked". I'd like to go back to stock marshmallow because I only use this thing to play music and as a tv remote. I'm hoping someone might have an old RUU lying around.
I guess if not my best option is just to unlock the bootloader again and try flashing the same lineage os again. Since I relocked does that mean I have to go through the htc website to get the unlock token again like I did ages ago? They probably don't even have this phone on there anymore. Hopefully I didn't actually turn this thing into a brick.
Please see my comments in red font below:
350Rocket said:
https://photos.google.com/album/AF1QipNmb1q2tT6uldWZLHQSLD1fsauQYRMlkHmA5y1g/photo/AF1QipPXGvhZ063BpX0f30U4O7d6ZYQgTkgeowCWDywd
Photo link is coming up with 404 error for me. Better to do fastboot getvar all, then post the results (cut and paste from command prompt), so we can see all the info on the phone (delete IMEI and serial number before posting).
Sorry for reviving such an old thread, but I'm trying to get my htc one m8 up and running again. It was functioning on lineage os but wasn't very stable, couldn't find any other roms that would successfully flash on it,
If you can be more specific about which ROMs you tried (plus info about your device from getvar as noted above), then we might be able to advise why they did not flash. Did you get error messages, and if so, what exactly were they?
I decided to try and go back to stock after a few beers one night night, now the phone has been sitting in a drawer with no os or recovery on it.
What exactly did you do (step by step, with any relevant file names, etc. - more detail is better).
I presume you intentionally relocked the bootloader in attempt to run some RUU. But would like clarification on this (and where that happened in the sequence of events)
There doesn't seem to be any still functioning links to any Canadian RUU's that I can use. I'm not s-off, bootloader is "relocked". I'd like to go back to stock marshmallow because I only use this thing to play music and as a tv remote. I'm hoping someone might have an old RUU lying around.
Far as I know, Canadian versions don't have RUU.
I guess if not my best option is just to unlock the bootloader again and try flashing the same lineage os again. Since I relocked does that mean I have to go through the htc website to get the unlock token again like I did ages ago? They probably don't even have this phone on there anymore. Hopefully I didn't actually turn this thing into a brick.
One option (maybe the best one) is to restore a stock TWRP back from the collection: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You will need to unlock the bootloader to do this. You can either reuse the unlock bin code you used originally (if you still have it). Otherwise, you should be able to request a new bin code from HTCDev.com. Far as I know, that still works for this phone.
Click to expand...
Click to collapse
So I just spent the last couple hours trying to root my phone. Only to realize that when I unlocked the bootloader i requested the wrong unlock.bin file. Instead of selecting the htc m8 file, I selected all other supported devices. I don't know if this is the cause of my problem, but since I can't reboot to bootloader, I feel that it is. Is the solution as simple as relocking the bootloader and then unlocking it with the correct unlock.bin file. Or can i just get the correct file and unlock it again. I don't know if any of it will work since the phone won't go into the bootloader. Thought I would as people that know more than me before I brick my phone.
Getting all the stock files from here and then using your cpu to flash everything you should be fine.
jayandare said:
Getting all the stock files from here and then using your cpu to flash everything you should be fine.
Click to expand...
Click to collapse
Ok, Thought I would have to be able to reboot to bootloader in order to flash but I will give that a try. Was there supposed to be a link or did you just mean "from here" as in the xda site?
Tskizzle said:
Ok, Thought I would have to be able to reboot to bootloader in order to flash but I will give that a try. Was there supposed to be a link or did you just mean "from here" as in the xda site?
Click to expand...
Click to collapse
Stock ruu method ,lock bootloader first
manish dubey said:
Stock ruu method ,lock bootloader first
Click to expand...
Click to collapse
Ok thanks. I'll do some searching and figure out how to do that, then try and flash the stock ruu. I'll report back if I have any issues. Thank you again.
Tskizzle said:
Ok thanks. I'll do some searching and figure out how to do that, then try and flash the stock ruu. I'll report back if I have any issues. Thank you again.
Click to expand...
Click to collapse
So I've been reading around and come across some conflicting info. So I finally found the fastboot command to lock the bootloader but some have said to flash the stock ruu first while others say after. Can anyone clear this up for me and let me know if it makes a difference?
S-OFF - no need to relock the bootloader, just run the appropriate RUU
S-ON - relock the bootloader and then run the appropriate RUU
cheers.
Mr Hofs said:
S-OFF - no need to relock the bootloader, just run the appropriate RUU
S-ON - relock the bootloader and then run the appropriate RUU
cheers.
Click to expand...
Click to collapse
Thanks for the help. I think I can handle this now. Is it worth it to go S-off? I'm gonna root once I am back to stock
Tskizzle said:
Thanks for the help. I think I can handle this now. Is it worth it to go S-off? I'm gonna root once I am back to stock
Click to expand...
Click to collapse
Quick reattack on this. I never actually went away from stock. As I couldn't get into the bootloader I never flashed twrp or anything so do I really need to flash the stock RUU? Just trying to figure out for knowledge purposes. Am I basically flashing the RUU to start over from scratch or is it just a precautionary thing?
I was thinking of selling my phone and I would like to downgrade it to nougat.
I'm using leedroid and this is the information on my phone:
UNLOCKED
FUSED
CID-BS_US001
MID-2PS650000
S-OFF
Compilation number 3.16.617.9
I know that with s-off it is easier to perform the downgrade but I do not want to break my phone so if someone could help me I would appreciate it a lot!
I was looking for the firmware on this page:
https://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520
but I do not know which is the one indicated for my phone, I also do not know which RUU I should flash.
I would look for the 2.41.617 RUU and flash that, then do the "erase persist" command which you can find in the guides section in the "solution no signal" thread.
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
Mr Hofs said:
I would look for the 2.41.617 RUU and flash that, then do the "erase persist" command which you can find in the guides section in the "solution no signal" thread.
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
Click to expand...
Click to collapse
I found the firmware 2.51.617.32 and the RUU 2.51.617.32 of the htc page, would these work?
and what to do with the RRU if it is an exe?
Sorry but I have never done a downgrade before.
edu_ss said:
I found the firmware 2.51.617.32 and the RUU 2.51.617.32 of the htc page, would these work?
and what to do with the RRU if it is an exe?
Sorry but I have never done a downgrade before.
Click to expand...
Click to collapse
Exe could work but is down to if your Java and HTC fastboot is configured well on your PC. I prefer the zip as its much easier and no commands are needed.
Mr Hofs said:
Exe could work but is down to if your Java and HTC fastboot is configured well on your PC. I prefer the zip as its much easier and no commands are needed.
Click to expand...
Click to collapse
i found a zip file https://androidfilehost.com/?fid=962021903579491246 this is better right?
edu_ss said:
i found a zip file https://androidfilehost.com/?fid=962021903579491246 this is better right?
Click to expand...
Click to collapse
If i had to do this i would use the zip, but that's still my opinion.
If the RUU doesn't work the first time you can flash the 2.41.617 firmware first (via fastboot) and then flash the RUU, then erase persist.
Should do the trick
Mr Hofs said:
If i had to do this i would use the zip, but that's still my opinion.
If the RUU doesn't work the first time you can flash the 2.41.617 firmware first (via fastboot) and then flash the RUU, then erase persist.
Should do the trick
Click to expand...
Click to collapse
thanks for your help! everything ended well!
edu_ss said:
thanks for your help! everything ended well!
Click to expand...
Click to collapse
Good to hear that ?