i tried to relock the bootloader just now but it keeps on rebooting to hboot so i just unlock again and it booted fine albeit being factory reset.
so the question is, after i fastboot oem lock , what should i do to reboot it normally instead of reboot to hboot?
do i need to download RUU exe file and execute it?
i also re flash original recovery since i don't feel like using custom ROM for the time being, i just want to wait for official OTA.
If you want to go back totally stock, then yes just run the RUU again.
M.
It will not boot if you have custom rom installed and oem locked. Hence it keeps rebooting into bootloader with a some warning on the top.
Unlock it again to resume the boot and lose all the settings or run a ruu as suggested before me.
Sent from my iPad using Tapatalk HD
beware if you have a 1.28 based rom (or updated OTA) i dont think a 1.26 based RUU will work. I didnt for me, i had to flash CWM recovery again and a .zip with 1.28.
so we need a new RUU to get back to stock if we have updated hboot.
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.
Hi,
a couple of weeks back i rooted the phone (HTC DESIRE 820 dual sim) with twrp recovery. I was looking to find some custom lollipop rom. Yday official OTA update was released and i downloaded it. Tried installing it but it would not install the update.
I extracted the OTA.zip file using winrar and then firmware.zip file. I used the recovery.img and flashed it using flashify app from the play store. Tried installing OTA update now, still no success.
Then using the same app i tried to flash the boot.img file. This is where is problem started. It will not go beyond the fastboot.
I tried reflash the entire firmware.zip using
fastboot flash zip firmware.zip
I get this error.
FAILED (remote: 12 signature verify fail)
How can i fix this. Hope i have not bricked the device. Please can someone Help
Stock ROM HTC 820 dual sim (INDIA) (4.4)found, fixed my device
i found the stock rom and was was able to fix my device. Please not the stock rom is for only India specific device.The link to stock rom is
https://mega.nz/#!ccAwHCIb!pfI1rxoQQr79Q9YMr3KA6yms6klsfyMjrO35qSOq4Mg
The steps i used to flash rom
fastboot devices
fastboot oem rebootRUU
fastboot flash zip <zip file>
fastboot reboot
After flashing , i have also update htc 820 to lollipop update, no issues. Everything works fine.
can you plz explain all steps to solve this problem..
Hi. I'm now on unlocked htc 10 with s-on. How can I back to clean, stock, oryginal condition? I tried to flash stock via ruu.exe and adb but it is failed. Relocking bootloader nothing helped. I tried some things but i got lost in this many theards. I will be very grateful if somebody help me and show me instructions. Actually i'm on m firmware.
boot into fastboot & paste the command below
copy the results & post here (remove imei from the post)
PHP:
fastboot getvar all
As you mentioned flashing the leaked nougat ruu ill assume you're on 401.x FW with the lastest ruu being 1.90.401.5
1. install twrp, restored untouched system & boot image, flash stock recovery
2. s-off downgrade to 1.90.401.5 , relock bootloader & run ruu
i see you edited your post
1. Rename zip to 2PS6IMG.zip
2. Copy zip onto sd card
3. Boot into download mode (download mode should detect the 2PS6IMG.zip)
4. Press volup to flash
Also flashing this will wipe your data , and it may render your phone *impossible* to receive future ota updates as it's an unofficial release from htc.
For example: lets say htc released a new nougat ota which updates you phone to 2.3x.401.x , that ota may only update phones on FW 1.95.401.4 & not 2.28.401.9
You would still be able to flash a 2.3x.401.x or above ruu (if available) or you could s-off & downgrade to 1.95.401.4 then accept ota
Personally i wouldn't flash it as yet as the official OTA is only around the corner (HTC said Q4)
@Diz so the 2.28.x is for unofficial/developers? Can I do it on unlocked bootloader?
Ps. i want to do it without s-off
Hi Guys,
Yesterday friend gave me his m8 with S-OFF but boot-loader locked. Want to flash TWRP but the commands failed. I heard that twrp can't be flashed with locked boot loader. So can I unlock it again using htc dev or it will cause problem? Or any other idea.
Phone is not running any OS stuck in boot loop.
'Thanks.
EDIT: OK SOLVED. Re-unlocked with htc dev and everything is fine. Twrp installed.
ahsan64 said:
Hi Guys,
Yesterday friend gave me his m8 with S-OFF but boot-loader locked. Want to flash TWRP but the commands failed. I heard that twrp can't be flashed with locked boot loader. So can I unlock it again using htc dev or it will cause problem? Or any other idea.
Phone is not running any OS stuck in boot loop.
'Thanks.
Click to expand...
Click to collapse
AFAIK you should be able to flash twrp with s-off&locked bootloader-only fails for s-on&locked bootloader
however you can just download a proper firmware package ( unsigned ) for your device variant
remove all the content except android-info.txt
then rename the twrp.img to recovery and zip both android-info and the recovery.img
rename it to 0P6BIMG.zip and flash it in hboot
( put the zip in sd card formatted as fat32 then reboot to bootloader-hboot then it will ask you to update confirm it and you are done )
lock&unlock bootloader method but required root
https://forum.xda-developers.com/showthread.php?t=2708571
also htc dev method should work fine but no need to unlock it imo
ahmed.ismael said:
AFAIK you should be able to flash twrp with s-off&locked bootloader-only fails for s-on&locked bootloader
however you can just download a proper firmware package ( unsigned ) for your device variant
remove all the content except android-info.txt
then rename the twrp.img to recovery and zip both android-info and the recovery.img
rename it to 0P6BIMG.zip and flash it in hboot
( put the zip in sd card formatted as fat32 then reboot to bootloader-hboot then it will ask you to update confirm it and you are done )
lock&unlock bootloader method but required root
https://forum.xda-developers.com/showthread.php?t=2708571
also htc dev method should work fine but no need to unlock it imo
Click to expand...
Click to collapse
Thanks but i just went simple and re unlock the boot loader again.
ahsan64 said:
Yesterday friend gave me his m8 with S-OFF but boot-loader locked. Want to flash TWRP but the commands failed. I heard that twrp can't be flashed with locked boot loader.
Click to expand...
Click to collapse
I see you've solved your issue. FYI, it's correct you cannot flash custom recovery (unsigned recovery image) with locked bootloader; and s-off does not bypass that restriction.