Htc one m8 bootlooped after flashing SuperSU v2.02 on TWRP v3.0.0-0

[braydenp]

Help me , I was trying to get s-off on my m8 with firewater, and it wasn't working because superSU wouldn't grant shell access(it wasn't the pro version), so i looked on the internet and found a supersu v2.02 zip file. I flashed it in twrp/recovery then after rebooting, it got stuck in a bootloop. the phone is rooted/unlocked, access to recovery, no access to adb/fastboot because my phone wont connect to the pc.
does anyone know a fix to this? Pretty desperate because this is the only phone I got.

 

[braydenp]

also I was stupid enough not to have a backup saved :/ I tried everything... formatting from bootloader, wiping phone in recovery.. nothings working.

 

[redpoint73]

You are using methods from 3 years ago. You need to look at the current (or at least, the most updated as possible) root and s-off methods for your device.

so i looked on the internet and found a supersu v2.02 zip file. I flashed it in twrp/recovery then after rebooting, it got stuck in a bootloop.

In particular, that SuperSU is ancient (3 years?) and probably wouldn't work with any Android version on the phone, except KitKat.

Assuming you were on Marshmallow before trying to root (most folks are, at this point) the proper SuperSU version would be the current stable SuperSU, which is 2.79: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703

Literally, you were using a SuperSU versions that is 77 iterations obsolete. Flashing the proper version SuperSU should solve the bootloop issue. Although your user data is now gone, since you wiped/factory reset (which as you now known, is not a valid fix for the problem).

I was trying to get s-off on my m8 with firewater, and it wasn't working because superSU wouldn't grant shell access

Getting shell SU access won't help you. Firewater stopped being supported 2-1/2 years ago. Since it had an online server component required to work, nothing you do will get firewater to work. So you can stop trying.

The only valid s-off method is sunshine app ($25 US): http://theroot.ninja/

 

[braydenp]

You are using methods from 3 years ago. You need to look at the current (or at least, the most updated as possible) root and s-off methods for your device.




In particular, that SuperSU is ancient (3 years?) and probably wouldn't work with any Android version on the phone, except KitKat.

Assuming you were on Marshmallow before trying to root (most folks are, at this point) the proper SuperSU version would be the current stable SuperSU, which is 2.79: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703

Literally, you were using a SuperSU versions that is 77 iterations obsolete. Flashing the proper version SuperSU should solve the bootloop issue. Although your user data is now gone, since you wiped/factory reset (which as you now known, is not a valid fix for the problem).




Getting shell SU access won't help you. Firewater stopped being supported 2-1/2 years ago. Since it had an online server component required to work, nothing you do will get firewater to work. So you can stop trying.

The only valid s-off method is sunshine app ($25 US): http://theroot.ninja/

I slight had a feeling that's why firewater wasn't working xD. I guess sunshine is the only way... well,.. i did get the latest version of supersu, but i noticed that i still can't get past bootloop eitherway because I have no OS installed from wiping my device in my attempt of "fixing" things. I gotta somehow find a 4.20.666.2 backup zip to flash(if there's even any on the internet) :/

 

[redpoint73]

I guess sunshine is the only way

No guesswork here. Sunshine is the only way.

Unless you count spending $150+ on a javacard. Which of course makes no sense, when sunshine costs $25.

i did get the latest version of supersu, but i noticed that i still can't get past bootloop eitherway because I have no OS installed from wiping my device in my attempt of "fixing" things.

If you wiped "system" in the TWRP "Advanced" wipe section, then you wiped the OS, and therefore (somewhat obviously) have no OS to boot.

If you were wiping things, without knowing what they are, or what the result would be; then that behavior needs to stop immediately!

Also, another good basic rule of thumb (good common sense on any Android device) is not to do any mods (root, custom ROM, etc.) without first knowing how to return to stock.

You can return to stock by using the guide and files in the following thread. Important to note, that these are not flashable zips. You need to follow the instructions carefully, extract the files and save them to the proper location on the phone, then boot TWRP and Restore (not Install like a ROM or other flashable zip): https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

 

[braydenp]

I did give that a try earlier.. my only problem is, I Haven't been able to connect to adb/fastboot ever since I got into the bootloop(probably because I can't get past reboot), not even mount usb storage, nor does adb sideload works, how can I get adb to work so i can return to stock?

 

[redpoint73]

i tried that kind of... my only problem is, I cant connect to adb/fastboot(adb devices wont work in cmd) ever since I got into the bootloop. mount usb storage doesn't work, nor does adb sideload, how can I get adb to work so i can return to stock?

Make sure you are in the correct mode:

Fastboot only works in bootloader-fastboot mode.

adb only works in OS (not an option, in the current condition) or in TWRP.

You should also be able to access the phone's internal storage (and SD card, if you have one) on your PC, when phone is booted to TWRP. In which case, you can copy the needed TWRP stock backup files to internal storage or SD.

 

[braydenp]

i got an sd card and can access internal storage so no worries in that area, just curious, is there another way to get the device serial/imei number?

 

[braydenp]

oh wait nvm found it, it was in barcode

 

[redpoint73]

i got an sd card and can access internal storage so no worries in that area, just curious, is there another way to get the device serial/imei number?

You mean, for the purpose of putting the TWRP backup folder in the right place?

If so, you can simply boot into TWRP, select Backup, then make a "dummy" backup by selecting to backup boot.img (just because it's the smallest thing to backup) and picking the desired the backup location (SD card or internal storage). TWRP will then create the necessary folder structure (including serial number), and you can simply copy the downloaded/extracted stock TWRP backup folders to that location.

It's actually preferable to do it this way, as any error in folder structure/names will result in TWRP not "seeing" the backup and unable to restore it.

 

[braydenp]

You mean, for the purpose of putting the TWRP backup folder in the right place?

If so, you can simply boot into TWRP, select Backup, then make a "dummy" backup by selecting to backup boot.img (just because it's the smallest thing to backup) and picking the desired the backup location (SD card or internal storage). TWRP will then create the necessary folder structure (including serial number), and you can simply copy the downloaded/extracted stock TWRP backup folders to that location.

It's actually preferable to do it this way, as any error in folder structure/names will result in TWRP not "seeing" the backup and unable to restore it.

Yes. it created the folder all for me with the code on it. what do i do with the 4.20.666.2_ckpv5.zip folder? it looks like its got some important OS stuff in it, & ty for pointing out that the boot stuff goes into the recovery.img folder

 

[braydenp]

nvm about the extra folder i just added the system 'n data stuff in the recovery folder and its working now. thank you for helping me
:victory: on step 11 now pretty much done, ty )

 

[braydenp]

huh... :/ the fastboot flash recovery x.xxx.xx.x_recovery.img command ain't working in fastboot

 

[braydenp]

i got the fastboot flash recovery to work, ran it, rebooted to get ota's but nothing came, still no OS i guess because its still stuck in bootloop and after doing all of that, twrp is gone.

 

[braydenp]

yeah, no OTA's, installed twrp again and it gets rid of twrp when i run the flash recovery file in fastboot then no ota's afterwards... i wonder if its because im running the recovery.img file from the sdk/adb file location instead of twrp/backup/serialno./... on the device, is that where I'm going wrong or is it something else? the boot, system and data files installed nicely though

 

[redpoint73]

Yes. it created the folder all for me with the code on it. what do i do with the 4.20.666.2_ckpv5.zip folder? it looks like its got some important OS stuff in it

Looks like you figured it out, but in interest of not confusing anyone else which may read this post: the zip folder contains all the folders which makeup the stock TWRP backup. So yes, it's not just important, it's the whole point of what you are trying to restore. The instructions are very explicit about what to do with the zip. You need to extract it on a computer, then save the extracted folders to the exact location on the phone (although it can be SD card or internal storage) indicated in the instructions.

ty for pointing out that the boot stuff goes into the recovery.img folder

The boot folder (extracted from the zip) goes in the TWRP folder on the phone, which has nothing to do with the recovery.img

Be careful there not to mix up the terms. They are 2 very different things (TWRP folders vs. recovery.img).

recovery.img is either TWRP itself, or the stock recovery (the "official" HTC recovery for installing OTAs, etc.).

---------- Post added at 09:45 AM ---------- Previous post was at 09:39 AM ----------

i got the fastboot flash recovery to work . . . and after doing all of that, twrp is gone.

The fastboot flash recovery command over-writes TWRP with the "stock" (official HTC) recovery (which is needed to install OTAs). So literally, the reason TWRP is gone, is due to the fact that you literally performed the action to erase it, and replace it with the stock recovery.

Am I understanding you correctly, that the phone is not booting to OS properly, but when you do to Settings and check for updates, there are none?

 

[braydenp]

Looks like you figured it out, but in interest of not confusing anyone else which may read this post: the zip folder contains all the folders which makeup the stock TWRP backup. So yes, it's not just important, it's the whole point of what you are trying to restore. The instructions are very explicit about what to do with the zip. You need to extract it on a computer, then save the extracted folders to the exact location on the phone (although it can be SD card or internal storage) indicated in the instructions.



The boot folder (extracted from the zip) goes in the TWRP folder on the phone, which has nothing to do with the recovery.img

Be careful there not to mix up the terms. They are 2 very different things (TWRP folders vs. recovery.img).

recovery.img is either TWRP itself, or the stock recovery (the "official" HTC recovery for installing OTAs, etc.).

---------- Post added at 09:45 AM ---------- Previous post was at 09:39 AM ----------



The fastboot flash recovery command over-writes TWRP with the "stock" (official HTC) recovery (which is needed to install OTAs). So literally, the reason TWRP is gone, is due to the fact that you literally performed the action to erase it, and replace it with the stock recovery.

Am I understanding you correctly, that the phone is not booting to OS properly, but when you do to Settings and check for updates, there are none?

When i try to flash the 4.20.666.2_recovery.img while its in the sdktools folder on my pc it wont install OTA's.
fastboot wont reach my phones internal storage twrp/backups/SerialNO./Recovery.img when i try flashing with the recovery.img in my phones storage. i got all the paths set up properly for fastoot/abd.. why wont it reach unless i have the recovery.img in sdktools folder on my pc? after i flash the recovery.img from sdkfile no OTA's are popping up after the phone reboots

 

[braydenp]

error: cannot load '4.20.666.2_Recovery.img' when i try flashing it from twrp/backups/SerialNO./Recovery.img

 

[redpoint73]

When i try to flash the 4.20.666.2_recovery.img while its in the sdktools folder on my pc it wont install OTA's, fastboot wont reach the twrp/backups/SerialNO./Recovery.img on my phones internal storage when i try flashing it. i got all the paths set up properly for fastoot/abd.. why wont it work unless i have the recovery.img in sdktools folder on my pc?

Fastboot is for flashing a file from your computer, to your phone. I've never seen anyone try to fastboot flash a file that resides on the phone's SD or internal storage; I don't think you can do that, nor is there a reason to do so.

Not receiving OTAs is not a problem with how you have stock recovery installed. If you have the right recovery (matches the TWRP, and it's installed, and matches the firmware) then the problem is somewhere else. Might just be a bug in the OTA system.

I'd like to verify you are restoring the right version number TWRP backup, and the right number recovery. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).

---------- Post added at 02:13 PM ---------- Previous post was at 02:11 PM ----------

error: cannot load '4.20.666.2_Recovery.img' when i try flashing it from twrp/backups/SerialNO./Recovery.img

Not a valid way to run the fastboot command, as already mentioned. The file should be on the computer, not on the phone.

Let me try to explain it in simple terms:

TWRP: Makes backup files of the ROM and kernel (boot.img), and can restores those. These backup files are saved to the phone's internal storage or SD. By moving/copying the files from the stock backup collection, you are "tricking" TWRP into thinking it is a backup that you made with TWRP. Everything is done by the phone, the computer is just used to move the files to the phone.

Fastboot: Use fastboot to replace TWRP with the "stock" recovery, which is required for OTA. The file and tool (fastboot) reside on the computer.

 

[braydenp]

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.666.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:******
(bootloader) imei: *******
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c7c8c7ac
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.007s
alright, well my only problem now it getting the OTA's, everything is setup like in the tutorial proper versions for my OS...