Listen guys, sorry I've screwed this up so badly. I got a developer edition from swappa, and it came rooted with the stock sense ui. It was rooted, twrp installed. S-on, NOT, s-off was enabled.
I switched to gpe edition seamlessly through twrp. Now, looking to go back to stock sense ui and cannot.
Here's what I've done attempting to go back.
Attempted RUU for developer edition software. No luck because of error in software, error 155.
Tried to flash the RUU zip and that too errored out on me.
I then figured it was because of S-on, so tried to figure that out... Unsuccessfully.
Then thought I needed stock recovery, flashed that with error and now stuck with no recovery at all. Fastboot flash recovery recovery. IMG didn't work. Yeah, so no recovery.
Then I thought RUU wouldn't work because I'm unlocked bootloader. So, I locked the boot loader via fastboot OEM lock.... Probably not good
Fastboot menu days tampered, relocked.
Oh, Wi-Fi doesn't work either.... I forgot to mention that before I attempted to flash a stock sense ROM with no root.
Sow now what? Any advice?
mcgrathpatj said:
Listen guys, sorry I've screwed this up so badly. I got a developer edition from swappa, and it came rooted with the stock sense ui. It was rooted, twrp installed. S-on, NOT, s-off was enabled.
I switched to gpe edition seamlessly through twrp. Now, looking to go back to stock sense ui and cannot.
Here's what I've done attempting to go back.
Attempted RUU for developer edition software. No luck because of error in software, error 155.
Tried to flash the RUU zip and that too errored out on me.
I then figured it was because of S-on, so tried to figure that out... Unsuccessfully.
Then thought I needed stock recovery, flashed that with error and now stuck with no recovery at all. Fastboot flash recovery recovery. IMG didn't work. Yeah, so no recovery.
Then I thought RUU wouldn't work because I'm unlocked bootloader. So, I locked the boot loader via fastboot OEM lock.... Probably not good
Fastboot menu days tampered, relocked.
Oh, Wi-Fi doesn't work either.... I forgot to mention that before I attempted to flash a stock sense ROM with no root.
Sow now what? Any advice?
Click to expand...
Click to collapse
The command is fastbooot flash recovery.img. No caps on the img and no space after the period, if that helps. Plus recovery only once, not twice.
You are placing the recovery.img into your fastboot folder, correct?
EDIT: fastboot oem unlock to unlock your bootloader again.
fastboot flash recovery xxxxxxx.img is the command i used. probably looked conufsing as i didn't use a proper variable for the image file but rather recovery.img
xunholyx said:
The command is fastbooot flash recovery.img. No caps on the img and no space after the period, if that helps. Plus recovery only once, not twice.
You are placing the recovery.img into your fastboot folder, correct?
EDIT: fastboot oem unlock to unlock your bootloader again.
Click to expand...
Click to collapse
It's fastboot flash recovery recovery.img
The first recovery tells the device the location to which you want to flash it, in this case "recovery" for the recovery partition and the second one is the file you wish to flash in this case "recovery.img".
---------- Post added at 07:26 PM ---------- Previous post was at 07:04 PM ----------
mcgrathpatj said:
fastboot flash recovery xxxxxxx.img is the command i used. probably looked conufsing as i didn't use a proper variable for the image file but rather recovery.img
Click to expand...
Click to collapse
Do you know what software version you were on?
Just try the Developer Edition RUU again. If you're S-ON which you are, then bootloader needs to be relocked. I can't think of a reason why it shouldn't work, even if recovery is gone it completely returns device to stock(Including recovery).
You don't have to do the CID/MID part seeing as you're S-ON and you need S-OFF to do that. I don't think you used the converted GPE but instead a GPE ROM
I donwloaded the RUU for the Develoer Edition and it errored out at 155. I must have tried this 5-6 times.
I think I finally figured this out, so it may be useful for someone else. Who knows.
1) I downloaded another users NANDROID backup from the Dev Edition from this thread: http://forum.xda-developers.com/showthread.php?t=2701376
2) I flashed TWRP, restored the NANDROID from the above thread using TWRP.
3) Then, I flashed the original STOCK corresponding recovery from the same thread.
4) I was able to reboot and wifi FINALLY worked properly on a sense rom. I downloaded the OTA and it updated successfully, upon reboot through, wifi was broken again.
5) Re-locked the bootloader via fastboot oem lock, then performed the RUU for the Dev Edition from this thread here: http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777
The RUU just completed successfully, so I think I'm out of the woods. But man oh man that was painful.
Related
HTC One X Quadcore, Virgin Mobile Australia, CID HTC_023, bootloader unlocked, SDK and Sync manager up to date.
I followed root instructions per Ausdroid which summarizes MoDaCo method using "r3-endeavor-insecurebootandroot" except it doesn't tell you when to backup your existing ROM. So no backup of the stock ROM (believe I feel dumb enough about it).
After reading up a bit more, installed Clockworkmod-5.8.4.0 and backed up the working ROM (presumably r3-endeavor-insecurebootandroot).
Since video was not working and caused forced reboots, I flashed the boot img that was in the r3-endeavor-insecurebootandroot.zip file. No luck, so I decided to go to MoDaCo website and try one of the ROMs he has there. The Sense and Vanilla ROMs there resulted in being stuck in the HTC brilliant screen (left it there plugged in overnight since Paul mentions that one should be patient on first boot).
Ok, so tried various other ROMs, no luck. Always erased cache before and after and tried various combinations of wiping data, factory resets, both in phone and in Clockwork etc., no luck. Tried the OneX All in One Kit v1.0 to reflash the Kernel to stock 2.6.39.4 (not even sure that's the one I should be using), no luck. Ok, so I'm guessing it's time to use the RUU. Found a cool method to bypass Filefactory premium and managed to download my RUU: RUU_ENDEAVOR_U_ICS_40_hTC_Asia_SEA_WWE_1.29.728.12_Radio_1.1204.105.14_release_261350_signed. Presumably the correct one since I used fastboot to give me the 1.29.728.12 as well as the CID info HTC_023.
Following XDA instructions on RUU recovery, I relocked the bootloader, confirmed the version and tried running the RUU.
The RUU tried to run but I get an error
Error Code: -5001 : 0x80070002
Error Information:
>SetupNew\setup.cpp (142)
Suggestions?
forgot to mention using win 7, and already tried a few windows support fixes for 0x80070002 errors.
bump
Anyone know what this error might mean?
QUOTE=requiem11;30025087]HTC One X Quadcore, Virgin Mobile Australia, CID HTC_023, bootloader unlocked, SDK and Sync manager up to date.
I followed root instructions per Ausdroid which summarizes MoDaCo method using "r3-endeavor-insecurebootandroot" except it doesn't tell you when to backup your existing ROM. So no backup of the stock ROM (believe I feel dumb enough about it).
After reading up a bit more, installed Clockworkmod-5.8.4.0 and backed up the working ROM (presumably r3-endeavor-insecurebootandroot).
Since video was not working and caused forced reboots, I flashed the boot img that was in the r3-endeavor-insecurebootandroot.zip file. No luck, so I decided to go to MoDaCo website and try one of the ROMs he has there. The Sense and Vanilla ROMs there resulted in being stuck in the HTC brilliant screen (left it there plugged in overnight since Paul mentions that one should be patient on first boot).
Ok, so tried various other ROMs, no luck. Always erased cache before and after and tried various combinations of wiping data, factory resets, both in phone and in Clockwork etc., no luck. Tried the OneX All in One Kit v1.0 to reflash the Kernel to stock 2.6.39.4 (not even sure that's the one I should be using), no luck. Ok, so I'm guessing it's time to use the RUU. Found a cool method to bypass Filefactory premium and managed to download my RUU: RUU_ENDEAVOR_U_ICS_40_hTC_Asia_SEA_WWE_1.29.728.12_Radio_1.1204.105.14_release_261350_signed. Presumably the correct one since I used fastboot to give me the 1.29.728.12 as well as the CID info HTC_023.
Following XDA instructions on RUU recovery, I relocked the bootloader, confirmed the version and tried running the RUU.
The RUU tried to run but I get an error
Error Code: -5001 : 0x80070002
Error Information:
>SetupNew\setup.cpp (142)
Suggestions?
forgot to mention using win 7, and already tried a few windows support fixes for 0x80070002 errors.[/QUOTE]
have u tried to install the RUU in fastboot mode?
GUARDIANBD said:
have u tried to install the RUU in fastboot mode?
Click to expand...
Click to collapse
Thanks for the reply. It's a good point that is occasionally not mentioned. I've always assumed that the RUU is to be run while in bootloader with fastboot command window open and RUU exe located within the fastboot directory. I used "fastboot devices" to confirm that the pc has recognized the HOX. I also disconnected everything and tried to run the RUU exe file on its own in order to manually flash the exe file contents, but the RUU does not run properly giving me the 0x80070002 windows error message.
three things I have yet to try:
1 install the stock recovery tool (still relying on CMW)
2 run the RUU on another computer (read somewhere that this helped someone's RUU issue when they tried it on an XP)
3 try to download the RUU again
not sure if any of these would help.
By chance, did you mean that the RUU can be somehow executed as a fastboot command? If so I haven't seen anything about it and would appreciate a detailed description of how to do that.
tanks
I think you have to flash stock recovery and lock the bootloader to flash ruu. Don't quote me though. Worth a try.
Sent from my now amazing HTC One X thanks to TeamVenoms ViperX rom
smidgeox said:
I think you have to flash stock recovery and lock the bootloader to flash ruu. Don't quote me though. Worth a try.
Sent from my now amazing HTC One X thanks to TeamVenoms ViperX rom
Click to expand...
Click to collapse
I've tried with the bootloader locked but not with the stock recovery flashed. I'll try it and report back. Any other suggestions are welcome.
thanks for replying.
Partial success
Downloaded the RUU again and this time it worked (who knows why). The RUU gets cracking and then stops telling me that my battery is less than 30% (it shows 100% in my third-party battery monitor).
So I decided to unpack the ROM.zip file from the %temp% directory as instructed in the wiki, but this time, fastboot flash boot boot.img results in a FAILED Remote something or other.
? Do I have to unlock the bootloader in order to manually flash the boot.img and the system.img files from the RUU?
For anyone who might be in the same position here's what worked for me:
Note, these are not step by step instructions!
RUU windows error -> Redownloaded the RUU file and it worked fine
RUU complains about battery less than 30% -> Connect to a different USB port
ROM.zip boot.img can't flash due to FAILED REMOTE error -> unlock boot loader again and then flash boot.img
ROM.zip boot.img flashed OK but System.img fails says file to large -> re-lock boot loader and start the RUU again
requiem11 said:
Downloaded the RUU again and this time it worked (who knows why). The RUU gets cracking and then stops telling me that my battery is less than 30% (it shows 100% in my third-party battery monitor).
So I decided to unpack the ROM.zip file from the %temp% directory as instructed in the wiki, but this time, fastboot flash boot boot.img results in a FAILED Remote something or other.
? Do I have to unlock the bootloader in order to manually flash the boot.img and the system.img files from the RUU?
For anyone who might be in the same position here's what worked for me:
Note, these are not step by step instructions!
RUU windows error -> Redownloaded the RUU file and it worked fine
RUU complains about battery less than 30% -> Connect to a different USB port
ROM.zip boot.img can't flash due to FAILED REMOTE error -> unlock boot loader again and then flash boot.img
ROM.zip boot.img flashed OK but System.img fails says file to large -> re-lock boot loader and start the RUU again
Click to expand...
Click to collapse
I should imagine that the bootloader needs to be unlocked to be able to flash any sort of .img file.
Have you flashed the ruu with stock recovery yet? I suggest you try this if you haven't already, if this fails. Ensure you have the correct matching RUU, then flash stock recovery, lock bootloader and try that.
Someone correct me if I am wrong but each ROM has a matching boot.img that needs to be flashed before flashing the rom.
Look on YouTube cursed4eva has an easy to follow video about going back to stock ROM
nixey55 said:
Someone correct me if I am wrong but each ROM has a matching boot.img that needs to be flashed before flashing the rom.
Look on YouTube cursed4eva has an easy to follow video about going back to stock ROM
Click to expand...
Click to collapse
Indeed, the boot.img contains the kernel & with s-on devices, boot.img's aren't flashed through recovery so it needs to be done on a computer with fastboot (fastboot flash boot boot.img).
---------- Post added at 05:13 PM ---------- Previous post was at 05:10 PM ----------
requiem11 said:
Downloaded the RUU again and this time it worked (who knows why). The RUU gets cracking and then stops telling me that my battery is less than 30% (it shows 100% in my third-party battery monitor).
So I decided to unpack the ROM.zip file from the %temp% directory as instructed in the wiki, but this time, fastboot flash boot boot.img results in a FAILED Remote something or other.
? Do I have to unlock the bootloader in order to manually flash the boot.img and the system.img files from the RUU?
For anyone who might be in the same position here's what worked for me:
Note, these are not step by step instructions!
RUU windows error -> Redownloaded the RUU file and it worked fine
RUU complains about battery less than 30% -> Connect to a different USB port
ROM.zip boot.img can't flash due to FAILED REMOTE error -> unlock boot loader again and then flash boot.img
ROM.zip boot.img flashed OK but System.img fails says file to large -> re-lock boot loader and start the RUU again
Click to expand...
Click to collapse
Also, i forgot to mention. MAKE sure you hold the power and down volume key down to enter the bootloader, then enter 'fastboot' to be able to flash the boot.img in fastboot , i thik that might be the reason you're getting the failed error.
smidgeox said:
Indeed, the boot.img contains the kernel & with s-on devices, boot.img's aren't flashed through recovery so it needs to be done on a computer with fastboot (fastboot flash boot boot.img).
---------- Post added at 05:13 PM ---------- Previous post was at 05:10 PM ----------
As a point of clarification, the RUU contains the associated boot.img and system.img required to get back to stock. If your RUU fails for some reason, there are instructions in the HTC One X wiki for extracting the RUU file and manually flashing the boot.img and system.img
Also, i forgot to mention. MAKE sure you hold the power and down volume key down to enter the bootloader, then enter 'fastboot' to be able to flash the boot.img in fastboot , i thik that might be the reason you're getting the failed error.
Click to expand...
Click to collapse
Yes, I did enter the bootloader correctly.
nixey55 said:
Someone correct me if I am wrong but each ROM has a matching boot.img that needs to be flashed before flashing the rom.
Click to expand...
Click to collapse
You're right as to the point that each ROM has a matching boot.img, but in which order you flash them doesnt matter at all.
Unlock the bootloader again and flash a custom ROM, it's usually the easiest way out. Don't bother using the boot.img root method as custom ROMs are pre rooted almost 99 percent of the time.
Sent from my Inspire 4G using Tapatalk 2
requiem11 said:
HTC One X Quadcore, Virgin Mobile Australia, CID HTC_023, bootloader unlocked, SDK and Sync manager up to date.
I followed root instructions per Ausdroid which summarizes MoDaCo method using "r3-endeavor-insecurebootandroot" except it doesn't tell you when to backup your existing ROM. So no backup of the stock ROM (believe I feel dumb enough about it).
After reading up a bit more, installed Clockworkmod-5.8.4.0 and backed up the working ROM (presumably r3-endeavor-insecurebootandroot).
Since video was not working and caused forced reboots, I flashed the boot img that was in the r3-endeavor-insecurebootandroot.zip file. No luck, so I decided to go to MoDaCo website and try one of the ROMs he has there. The Sense and Vanilla ROMs there resulted in being stuck in the HTC brilliant screen (left it there plugged in overnight since Paul mentions that one should be patient on first boot).
Ok, so tried various other ROMs, no luck. Always erased cache before and after and tried various combinations of wiping data, factory resets, both in phone and in Clockwork etc., no luck. Tried the OneX All in One Kit v1.0 to reflash the Kernel to stock 2.6.39.4 (not even sure that's the one I should be using), no luck. Ok, so I'm guessing it's time to use the RUU. Found a cool method to bypass Filefactory premium and managed to download my RUU: RUU_ENDEAVOR_U_ICS_40_hTC_Asia_SEA_WWE_1.29.728.12_Radio_1.1204.105.14_release_261350_signed. Presumably the correct one since I used fastboot to give me the 1.29.728.12 as well as the CID info HTC_023.
Following XDA instructions on RUU recovery, I relocked the bootloader, confirmed the version and tried running the RUU.
The RUU tried to run but I get an error
Error Code: -5001 : 0x80070002
Error Information:
>SetupNew\setup.cpp (142)
Suggestions?
forgot to mention using win 7, and already tried a few windows support fixes for 0x80070002 errors.
Click to expand...
Click to collapse
Can you upload the file RUU_ENDEAVOR_U_ICS_40_hTC_Asia_SEA_WWE_1.29.728.12_Radio_1.1204.105.14_release_261350 I can't download it form filefactory !
Not sure where I'd upload it for you to get it, but I followed some instructions that I found here and it worked using Safari
http://o-ogy.blogspot.com.au/2012/02/how-to-use-filefactory-premium-cookie.html
There are a lot of steps, but follow them carefully and it should work.
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
Hi guys,
I have an HTC One M9 Dev Edition. It is rooted, bootloader unlocked (since dev ed) and s-on. I had 2.8.617.4. I have been getting notifications to update it to 2.11.xxx.x, but since I was rooted, I couldn't update. So I thought of reverting back to stock to get the OTA. I booted to recovery (TWRP 2.8.7.0), tried restoring to the nandroid system that I had a backup of. That failed, with system is read only error or similar error message. So I followed step 5 from this guide - http://forum.xda-developers.com/one-m9/general/best-unlocking-bootloader-rooting-guide-t3087354.
After finishing the steps, my phone is now stuck on the htc logo. I'm not sure what is wrong. I can boot into recovery. One thing I notice is when I boot to download mode, I still see the OS as 2.8.617.4. I tried flashing system again, I still see the same thing and the same problem. I need your help fixing this. Thanks.
Step 5 in that guide says "Coming Soon"?
Are you on stock recovery or twrp?
I sincerely hope you did not lock your bootloader without ticking "allow oem unlock" in developer settings.
iElvis said:
Step 5 in that guide says "Coming Soon"?
Are you on stock recovery or twrp?
I sincerely hope you did not lock your bootloader without ticking "allow oem unlock" in developer settings.
Click to expand...
Click to collapse
Oh, I'm sorry, I meant Extra Section after step 5. No, I didn't lock my bootloader. I'm on dev edition, so my bootloader was unlocked right from the beginning.
I am on stock recovery. But I can flash twrp. My download mode is working, and I am able to flash different images, so I don't think my phone is bricked or anything.
At this point, I just need to get my phone back to a working condition. I'm sure someone can tell me how to do that.
Edit: Can it be because I tried to flash an older firmware (1.32.617.3) than what I currently have (2.8.617.4)?
slvrhwk said:
Edit: Can it be because I tried to flash an older firmware (1.32.617.3) than what I currently have (2.8.617.4)?
Click to expand...
Click to collapse
Good, don't relock.
That is almost certainly your problem. You just need to get back to current stock to take the ota. That thread is out of date IMO. You should look at one of the other back to stock threads, though ignore statements about relocking.
iElvis said:
Good, don't relock.
That is almost certainly your problem. You just need to get back to current stock to take the ota. That thread is out of date IMO. You should look at one of the other back to stock threads, though ignore statements about relocking.
Click to expand...
Click to collapse
I downloaded a system image of the current version of OS I am at. Do you think flashing that will work?
You probably have an bootloop because of the kernel.You are S-ON user so you probably have to flash the right (stock) kernel for the untouched system.img you have flashed.
If you try to make a wipe to data partition (even better a factory restore) could also help you but you are going to lose all your data.
If you want to flash a stock kernel (boot.img) just extract it from the same RUU you extracted system.img .
In order to flash it give the command
Code:
fastboot flash boot boot.img
After that give the command
Code:
fastboot getvar all
and copy-paste everything here (except your IMEI number).
Phone specs:
Code:
RELOCKED
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.16.0.0000
RADIO-1.23.213311491.05G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.20.531.4 (1.54.401.5)
eMMC-boot 2048MB
So I'm trying to update my One M8, and I think I messed up pretty bad. I tried running the RUU updater for my T-Mobile variant (found on HTC's ROM Download page), but got the infamous "error 155." However, my bootloader is re-locked. Therefore, according to all the forum posts I could find, I shouldn't be getting that error. I've run a few commands since then, including fastboot oem writecid 11111111 and fastboot erase cache. Somehow, I've managed to get to the point where my phone won't even boot into recovery, it just gets stuck at the "Entering recovery..." screen. However, while stuck on this screen, the phone does respond to ADB commands. I can get root shell access, but I'm not sure what to do with it.
I've tried flashing TWRP 3.0.0.0 to no avail. I've tried running fastboot boot <twrp filename here>, also to no avail. I'm pretty much stuck with a phone that only boots into fastboot, and a weird purgatory-recovery where I can achieve shell access. The RUU file fails to update no matter what I do.
Is there a way I can fix this, or have I completely bricked my phone?
Thank you for your time.
RalphORama said:
Phone specs:
Code:
RELOCKED
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.16.0.0000
RADIO-1.23.213311491.05G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.20.531.4 (1.54.401.5)
eMMC-boot 2048MB
So I'm trying to update my One M8, and I think I messed up pretty bad. I tried running the RUU updater for my T-Mobile variant (found on HTC's ROM Download page), but got the infamous "error 155." However, my bootloader is re-locked. Therefore, according to all the forum posts I could find, I shouldn't be getting that error. I've run a few commands since then, including fastboot oem writecid 11111111 and fastboot erase cache. Somehow, I've managed to get to the point where my phone won't even boot into recovery, it just gets stuck at the "Entering recovery..." screen. However, while stuck on this screen, the phone does respond to ADB commands. I can get root shell access, but I'm not sure what to do with it.
I've tried flashing TWRP 3.0.0.0 to no avail. I've tried running fastboot boot <twrp filename here>, also to no avail. I'm pretty much stuck with a phone that only boots into fastboot, and a weird purgatory-recovery where I can achieve shell access. The RUU file fails to update no matter what I do.
Is there a way I can fix this, or have I completely bricked my phone?
Thank you for your time.
Click to expand...
Click to collapse
Have you flashed both stock recovery for the RUU in particular youre flashing and re-locked BL, and are you installing a version number that is equal to or higher than the one you already have installed.
Completely stock phone should flash RUU, as long as its not a version down from whats installed, ie, trying to flash LP when MM is already flashed on phone, UNLESS of course youre s-off and supercid, because with supercid you should be able to flash any RUU .
But i had similar issues, im s-on, so i had to revert to stock LP completely, then flashed HTC__001 Stock MM for my phone, failing all that there is always the option of copying a nandroid on here to ur sd card, boot into twrp and restore the Nandroid just to get it up and running again.
I would run the RUU, let it sit at first screen, goto start button and type in %temp%, find the folder inside temp that ruu just created, (sort by date), pull the rom.zip from that to ur desktop, Unzip it and get the files recovery and boot.img, flash them both to ur phone via fastboot, if it still works, then restart ur phone and it should load up, you could then try to install the RUU from windows again, failing that after flashing recovery and boot, goto ur stock recovery and wipe and reset then reboot phone.
It doesnt sound like hard brick, just soft brick, it should be ok.
If you try to flash a Android MM ruu i suggest to flash a lower ruu first. Usually the big jump from the 3.16 boot loader to a 3.19 boot loader is too much.
Or flash the standalone firmware first and then the full ruu.
The high version of TWRP doesn't work because your bootloader is too low (3.16) if you want a working TWRP then use a 2.7 version.
If you can get to the bootloader then it's just a softbrick. A hardbrick is only when the bootloader is not accessible anymore or when the phone doesn't boot up in any way anymore.
Cheers
Mr Hofs said:
Or flash the standalone firmware first and then the full ruu.
Click to expand...
Click to collapse
This is most likely the solution. In particular, if OP is trying to install MM RUU, there is a new peculiarity (requirement?) with all MM RUUs, where you need to have MM firmware in order to run the RUU, or else you will have Error 155.
Find the firmware.zip that matches the version number of the RUU, flash it; then try the RUU again.
---------- Post added at 09:42 AM ---------- Previous post was at 09:35 AM ----------
gazza35 said:
Have you flashed both stock recovery for the RUU
Click to expand...
Click to collapse
You don't need stock recovery to RUU. Folks keep saying this, and its not true.
You need stock recovery to OTA, but you do not need it for RUU. OTA and RUU are two very different things.
gazza35 said:
because with supercid you should be able to flash any RUU .
Click to expand...
Click to collapse
This is also not true. You need to match MID and CID (or SuperCID) in order to flash an RUU. SuperCID bypasses the CID check, but you still need to pass the MID check.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
gazza35 said:
But i had similar issues, im s-on, so i had to revert to stock LP
Click to expand...
Click to collapse
Same peculiarity with the MM RUU I mentioned above (need to flash the MM firmware if coming from LP) also applies if you try to downgrade back to LP. Meaning, you need to flash the LP firmware, then LP RUU.
Mr Hofs said:
If you try to flash a Android MM ruu i suggest to flash a lower ruu first. Usually the big jump from the 3.16 boot loader to a 3.19 boot loader is too much.
Or flash the standalone firmware first and then the full ruu.
The high version of TWRP doesn't work because your bootloader is too low (3.16) if you want a working TWRP then use a 2.7 version.
If you can get to the bootloader then it's just a softbrick. A hardbrick is only when the bootloader is not accessible anymore or when the phone doesn't boot up in any way anymore.
Cheers
Click to expand...
Click to collapse
Thank you (and everyone else) for your replies! Out of curiosity, where can I find a lower RUU? I can only find the most recent one from HTC's website.
EDIT: I flashed TWRP 2.7 and I was able to boot into recovery! I love progress.
RalphORama said:
Out of curiosity, where can I find a lower RUU? I can only find the most recent one from HTC's website.
Click to expand...
Click to collapse
You can find the links for older T-Mob RUUs here: http://forum.xda-developers.com/showthread.php?t=2714456
Is it possible to have a working phone without a recovery installed ?
Unlocked bootloader, flashed twrp 3.0.1.0, phone wouldn't boot into recovery.
Relocked bootloader cause phone is s-on, ran 401 ruu but can't get into stock recovery but otherwise phone works ok
:banghead:
There is always a recovery installed. Either the stock one or the custom one. What does it do when you go to the recovery?
10rdan said:
Is it possible to have a working phone without a recovery installed ?
Unlocked bootloader, flashed twrp 3.0.1.0, phone wouldn't boot into recovery.
Relocked bootloader cause phone is s-on, ran 401 ruu but can't get into stock recovery but otherwise phone works ok
:banghead:
Click to expand...
Click to collapse
Just fyi, but I'm pretty sure you can flash RUU in RUU mode with bootloader unlocked.
Phone works fine without recovery, but you can't take an ota, flash roms (custom recovery) or wipe data/cache.
I'd unlock again, and flash either stock recovery, run the RUU again, or flash TWRP 3.0.2-2. Why were you using such an old version in the first place? That's likely the cause of your issue in getting the phone to boot to TWRP.
jollywhitefoot said:
Just fyi, but I'm pretty sure you can flash RUU in RUU mode with bootloader unlocked.
Phone works fine without recovery, but you can't take an ota, flash roms (custom recovery) or wipe data/cache.
I'd unlock again, and flash either stock recovery, run the RUU again, or flash TWRP 3.0.2-2. Why were you using such an old version in the first place? That's likely the cause of your issue in getting the phone to boot to TWRP.
Click to expand...
Click to collapse
With s-on you need to relock the bootloader to use official signed ruu files. When he flashed the ruu he could be seeing the exclamation mark that is normal as a warning before entering the stock recovery for which you need to push a volume and power button combo (don't know them heads up)
A possibility is to clear the cache and try to enter again (as this was a thingy on older HTC devices) or indeed as suggested at least to use the latest twrp available
Mr Hofs said:
With s-on you need to relock the bootloader to use official signed ruu files. When he flashed the ruu he could be seeing the exclamation mark that is normal as a warning before entering the stock recovery for which you need to push a volume and power button combo (don't know them heads up)
A possibility is to clear the cache and try to enter again (as this was a thingy on older HTC devices) or indeed as suggested at least to use the latest twrp available
Click to expand...
Click to collapse
It doesn't get as far as red exclamation mark, that's what I was waiting for. I'll try the newer version of twrp tomorrow after I've unlocked bootloader again. Do you think the same unlock code will work again?
10rdan said:
It doesn't get as far as red exclamation mark, that's what I was waiting for. I'll try the newer version of twrp tomorrow after I've unlocked bootloader again. Do you think the same unlock code will work again?
Click to expand...
Click to collapse
Yes i think it does work again. But that's a try and find out. There is always the possibility i could be wrong.
Edit :
This is why i love s-off....no more relocking / unlocking the BL with also an increased chance of bricks. The BL isn't made to be relocked and unlocked over and over.
Mr Hofs said:
With s-on you need to relock the bootloader to use official signed ruu files.
Click to expand...
Click to collapse
Sorry, but I believe this is misinformation, possibly residual to older HTC devices. I've heard this going back to the M7.
You need to be s-off to flash in download mode, but s-on can flash signed firmware and ruu's in RUU mode. I'm s-off so I can't test at the moment, but I'm about 99% that my information is correct.
S-on, you can only flash same or newer, though. You can't flash older firmware.
See post 19 here:
http://forum.xda-developers.com/htc-10/how-to/unlocked-official-ruu-t3378540/page2
I'm 100% that you can flash signed firmware package in ruu mode with bootloader unlocked and s-on.
jollywhitefoot said:
Sorry, but I believe this is misinformation, possibly residual to older HTC devices. I've heard this going back to the M7.
You need to be s-off to flash in download mode, but s-on can flash signed firmware and ruu's in RUU mode. I'm s-off so I can't test at the moment, but I'm about 99% that my information is correct.
S-on, you can only flash same or newer, though. You can't flash older firmware.
See post 19 here:
http://forum.xda-developers.com/htc-10/how-to/unlocked-official-ruu-t3378540/page2
I'm 100% that you can flash signed firmware package in ruu mode with bootloader unlocked and s-on.
Click to expand...
Click to collapse
That's new to me. Hopefully it isn't just tied to the developers edition then.
Thanks for the information
Mr Hofs said:
This is why i love s-off....no more relocking / unlocking the BL with also an increased chance of bricks. The BL isn't made to be relocked and unlocked over and over.
Click to expand...
Click to collapse
I'll bare that in mind, will unlock tomorrow again and try newer twrp. Only reason I relocked was to run ruu to get phone running again.
jollywhitefoot said:
Just fyi, but I'm pretty sure you can flash RUU in RUU mode with bootloader unlocked.
Phone works fine without recovery, but you can't take an ota, flash roms (custom recovery) or wipe data/cache.
I'd unlock again, and flash either stock recovery, run the RUU again, or flash TWRP 3.0.2-2. Why were you using such an old version in the first place? That's likely the cause of your issue in getting the phone to boot to TWRP.
Click to expand...
Click to collapse
Where can I find 3.0.2.2, can only see 3.0.2.0 on twrp site?
Cheers
Edit.... Found it. ?
@jollywhitefoot
I've got stock recovery back on phone. Can you think of any reason, other than old version, as to why twrp wouldn't boot after flashing it ?
Will try again tomorrow.
10rdan said:
@jollywhitefoot
I've got stock recovery back on phone. Can you think of any reason, other than old version, as to why twrp wouldn't boot after flashing it ?
Will try again tomorrow.
Click to expand...
Click to collapse
I'm not exactly sure, but up until 3.0.2.2 Captain Throwback didn't even have the device and was working blind. I know he was trying different things to make it compatible with different variants, too, so in my mind that was a test build. I'm not sure why they have it on the downloads page. For me, I always download it from the download section of the twrp thread.