Stuck in boot loop when trying to return to stock.

[el80ne]

I'm stuck in a boot loop after trying to return to stock.

I followed precisely the instructions written by 5m4r7ph0n36uru in the section titled "Restore using a RUU".

On my BadBoyz unlocked rom where I was still on OS version 1.16.617.6 I did was flash with the latest full RUU version 2.42.617.7 then relocked my ROM with fastboot oem lock command.

I've tried clearing the cache and factory reset as instructed in HTC docs to try when stuck in boot loops. I can't get it to go past the boot screen.

Was I wrong to flash to the latest RUU I found in the spreadsheet section for my phone model? Should I have flashed with the RUU of the version I originally had on my phone to return to stock?

Any ideas would be greatly appreciated. Thanks in advanced.

 

[mauiblue]

I know that the OP had posted this about a week ago but I was wondering if you had your issue with the phone resolved? I found only when I used the SD card process to flash a RUU zip file I would be successful in flashing another OS/firmware. On my U11, I only was successful in first flashing a older version of the OS on to my phone before I was able to boot my phone up. On my U12+ I was successful in flashing the original (latest) OS. Good luck.

Sent from my coconut frond hut using Tapatalk

 

[Matty1993]

I'm stuck in a boot loop after trying to return to stock.

I followed precisely the instructions written by 5m4r7ph0n36uru in the section titled "Restore using a RUU".

On my BadBoyz unlocked rom where I was still on OS version 1.16.617.6 I did was flash with the latest full RUU version 2.42.617.7 then relocked my ROM with fastboot oem lock command.

I've tried clearing the cache and factory reset as instructed in HTC docs to try when stuck in boot loops. I can't get it to go past the boot screen.

Was I wrong to flash to the latest RUU I found in the spreadsheet section for my phone model? Should I have flashed with the RUU of the version I originally had on my phone to return to stock?

Any ideas would be greatly appreciated. Thanks in advanced.

Hey mate can i ask did you boot the rom before locking the bootloader to see if the OS was functional ? Also how many times did you try flash the updated RUU before locking the bootloader,

Youve locked the bootloader down again anyway and will display as relocked in bootloader mode, youve made things a bit harder for yourself here,

Never ever relock the bootloader whilst the system is non functional keep it unlocked until you know the OS is ok, in general now youve locked it your device would usually require a very specific RUU full signed and exact main version match, however luckily for you if you havent already fixed it ive found a way to fix it without sending to HTC if you dont have the exact RUU needed to revive it,

What i want you to do is download the full RUU.zips for your model from the google spread sheet main version wont be an issue will be best to get all releveant RUUs with matching CID from there also

https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit?usp=sharing


Now download the HTC_10 batch tool and install it

http://forum.xda-developers.com/showpost.php?p=67056758&postcount=4

After its installed, place your RUU.zip into your local drive "C://" as an example where your batch tool is installed place the RUUs 1 at a time into /android/com, no more than 1 at a time when flashing

Full length of where RUU needs to be put in simple termns is C://android/com

Now minimise to the desktop, then right click on the batch tool icon and run as administrator,

NOT the HTC FUU icon !

Once the batch tool has booted, press the number 3 on the keyboard and then enter, this will take you to the fastboot terminal,

Take note the screen should be purple and the location on the screen should be as follows C:// is only for example your drive letter may be different,

C://Android/com

Now boot the phone to download mode and connect to pc,

Now type the following,

Fastboot devices

If that didnt work type

htc_fastboot devices

Your device should display now with a serial number,


Now type

fastboot oem rebootRUU

If that didnt work type

htc_fastboot oem rebootRUU


Now type

fastboot flash zip example.zip

If that didnt work type

htc_fastboot flash zip example.zip

!!example is the name of your RUU if you dont want to type it out drag and drop from the minimised window in C://Android/com,

Now your device will start flashing the RUU to your device, in my experience this is the only fastboot terminal that will revive a dead htc in your case without the exact signed ruu it requires,

It will also let you rollback from oreo to nougat whereas any other fastboot terminal you use will give you RUU error Main version fail in info or RUU error zip from usb command,


Try this it will work if you need clearer instructions you can check my thread out, this is pretty much the same case but without the device saying corrupt either way you still have non functional OS and oem unlock will be off FRP lock will be enabled and you wont be able to unlock the bootlaoder again without a functional OS as the full RUUs wipe the device completely resseting everything

My thread link is here for more infomation if needed

https://forum.xda-developers.com/u11/help/fixed-htc-u11corruptrelockeds-t3855157

Thanks

 

[el80ne]

Hey thanks for the reply! Actually I was able to get my phone back up and working again after having gleaned quite a bit of useful info from your very informative OP.

Fortunately I didn't have to go the route of running the HTC 10 batch tool, since I really wasn't looking forward to having to set up a virtual windows machine or having to trust a windows emulator like Wine just to run a dos batch tool. Actually I got the message pretty quick reading your first post that relocking the bootloader was a pretty terrible idea and set right away to unlocking it again. I was able to do it going through the HTC routine of cutting and pasting the ASCII key to HTC web form and having the Unlock_code.bin emailed to me again. It was different from the original ascii and unlock file they sent me the first time, but it did the trick.

It was smooth sailing from there, as I was able to boot to recovery and flash TWRP, which I then used to install the latest BadBoyz rom running Oreo and it just worked.

I was a little surprised, because I was under the impression I would have to apply all my OTAs manually since I was upgrading from Marshmellow. So even though I had a busted /system partition that wasn't letting me boot into the latest HTC RUU stock, that didn't seem to matter. Flashing with the latest RUU must hav the OTAs intact on a separate partition that the latest bad boyz rom just worked out of the box.

I'd been meeting to update this post, sorry to make you type all that out again when your first post was great. It tipped me off to scrutinize that HTC10 batch script line by line to see what was so special about it. Turns out, not a whole lot; I figured I could manage to do all that running the android bridge from my linux console just fine. But it was extraordinarily insightful in practically giving me a written line by line instruction set on how to recover my phone from command line. It was about as straightforward as it gets. I totally appreciate your help! :good:

Hey mate can i ask did you boot the rom before locking the bootloader to see if the OS was functional ? Also how many times did you try flash the updated RUU before locking the bootloader,

Youve locked the bootloader down again anyway and will display as relocked in bootloader mode, youve made things a bit harder for yourself here,

Never ever relock the bootloader whilst the system is non functional keep it unlocked until you know the OS is ok, in general now youve locked it your device would usually require a very specific RUU full signed and exact main version match, however luckily for you if you havent already fixed it ive found a way to fix it without sending to HTC if you dont have the exact RUU needed to revive it,

What i want you to do is download the full RUU.zips for your model from the google spread sheet main version wont be an issue will be best to get all releveant RUUs with matching CID from there also

https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit?usp=sharing


Now download the HTC_10 batch tool and install it

http://forum.xda-developers.com/showpost.php?p=67056758&postcount=4

After its installed, place your RUU.zip into your local drive "C://" as an example where your batch tool is installed place the RUUs 1 at a time into /android/com, no more than 1 at a time when flashing

Full length of where RUU needs to be put in simple termns is C://android/com

Now minimise to the desktop, then right click on the batch tool icon and run as administrator,

NOT the HTC FUU icon !

Once the batch tool has booted, press the number 3 on the keyboard and then enter, this will take you to the fastboot terminal,

Take note the screen should be purple and the location on the screen should be as follows C:// is only for example your drive letter may be different,

C://Android/com

Now boot the phone to download mode and connect to pc,

Now type the following,

Fastboot devices

If that didnt work type

htc_fastboot devices

Your device should display now with a serial number,


Now type

fastboot oem rebootRUU

If that didnt work type

htc_fastboot oem rebootRUU


Now type

fastboot flash zip example.zip

If that didnt work type

htc_fastboot flash zip example.zip

!!example is the name of your RUU if you dont want to type it out drag and drop from the minimised window in C://Android/com,

Now your device will start flashing the RUU to your device, in my experience this is the only fastboot terminal that will revive a dead htc in your case without the exact signed ruu it requires,

It will also let you rollback from oreo to nougat whereas any other fastboot terminal you use will give you RUU error Main version fail in info or RUU error zip from usb command,


Try this it will work if you need clearer instructions you can check my thread out, this is pretty much the same case but without the device saying corrupt either way you still have non functional OS and oem unlock will be off FRP lock will be enabled and you wont be able to unlock the bootlaoder again without a functional OS as the full RUUs wipe the device completely resseting everything

My thread link is here for more infomation if needed

https://forum.xda-developers.com/u11/help/fixed-htc-u11corruptrelockeds-t3855157

Thanks

 

[Matty1993]

Hey thanks for the reply! Actually I was able to get my phone back up and working again after having gleaned quite a bit of useful info from your very informative OP.

Fortunately I didn't have to go the route of running the HTC 10 batch tool, since I really wasn't looking forward to having to set up a virtual windows machine or having to trust a windows emulator like Wine just to run a dos batch tool. Actually I got the message pretty quick reading your first post that relocking the bootloader was a pretty terrible idea and set right away to unlocking it again. I was able to do it going through the HTC routine of cutting and pasting the ASCII key to HTC web form and having the Unlock_code.bin emailed to me again. It was different from the original ascii and unlock file they sent me the first time, but it did the trick.

It was smooth sailing from there, as I was able to boot to recovery and flash TWRP, which I then used to install the latest BadBoyz rom running Oreo and it just worked.

I was a little surprised, because I was under the impression I would have to apply all my OTAs manually since I was upgrading from Marshmellow. So even though I had a busted /system partition that wasn't letting me boot into the latest HTC RUU stock, that didn't seem to matter. Flashing with the latest RUU must hav the OTAs intact on a separate partition that the latest bad boyz rom just worked out of the box.

I'd been meeting to update this post, sorry to make you type all that out again when your first post was great. It tipped me off to scrutinize that HTC10 batch script line by line to see what was so special about it. Turns out, not a whole lot; I figured I could manage to do all that running the android bridge from my linux console just fine. But it was extraordinarily insightful in practically giving me a written line by line instruction set on how to recover my phone from command line. It was about as straightforward as it gets. I totally appreciate your help! :good:

Glad its sorted mate,

Always keep your bootloader unlockes so you can flash unsigned firmware as unfortunately finding signed_ruu.zip with specific versions is very difficult, and batch tool contains HTC official code for flashing and also lets you flash a lower main version and rollback the bootloader from oreo back to nougat no other fastboot terminal i used would allow it when i did it would always give RUU error main version fail,


Lucky the bootloader let you flash token, mine wouldnt even let me do that i got killswitches enabled on BL, FRP & OEMunlock please unlock lol

And thats no probs on the detailed tutorials i got kinda like ocd where i gotta explain stuff really into detail haha sometimes i dont even notice, keep the BL unlocked thouhh and you should be fine