Phone is stuck in bootloop! [SOLVED] - Verizon HTC One (M9)

Hi,
I understand this is probably a common problem with a simple fix, but this is my first attempt to root. My phone is unlocked and s-off, running 3.37.605.7. I used TWRP to install SuperSU and then after rebooting, it was stuck in a bootloop. After doing some research I think maybe I installed the wrong version of SuperSU, but I can't figure out how to fix it. I did a backup with adb beforehand, but when I tried restoring it said to unlock my phone and confirm, and I can't unlock my phone. I tried doing the restore command with TWRP open and it seemed to do something at first, but then nothing. I'm really stuck and would appreciate some help.
Thanks!

Are you wanting to keep the data you have on the phone or, would you be OK with starting fresh?

RoyalDrew said:
Are you wanting to keep the data you have on the phone or, would you be OK with starting fresh?
Click to expand...
Click to collapse
I'm fine with losing data. Actually I just flashed the RUU again and it's working again. I'll try to root again later.

jrzee45 said:
I'm fine with losing data. Actually I just flashed the RUU again and it's working again. I'll try to root again later.
Click to expand...
Click to collapse
After you get TWRP back, flash View attachment BETA-SuperSU-v2.65.zip to get root.
I just went through the same mess as you with the newer SuperSu versions. I read somewhere that 2.65 was the latest that would work and this is the zip I used.

RoyalDrew said:
After you get TWRP back, flash View attachment 4082602 to get root.
I just went through the same mess as you with the newer SuperSu versions. I read somewhere that 2.65 was the latest that would work and this is the zip I used.
Click to expand...
Click to collapse
Just flashed 2.65 and it worked! Thanks so much.

Unable to boot
Anyone having issues with this ROM. I flashed using TWRP 2.8.7.0, S-OFF and Unlocked, after flashing, phone reboots into aboot and i select reboot, and it rebots to aboot again without booting to the rom.

Related

HTC m9 - Bootloop After Installing BETA SuperSU 2.68 - Running TWRP 3.0.0-2

Hi everyone,
Stuck in BootLoop After Installing BETA-SuperSU-v2.68-20160228150503.zip. I installed using TWRP. Install looks it went fine then I rebooted and bootloop.
HTC M9 (t-mobile)
Unlocked
TWRP version - twrp-3.0.0-2-hima
After installing "BETA-SuperSU-v2.68-20160228150503.zip" my phone is stuck in bootloop. It has rebooted at least 5 times. I then was able to get into HTC download mode.
What can I do now? I have a full nandroid backup.
cloves said:
Hi everyone,
Stuck in BootLoop After Installing BETA-SuperSU-v2.68-20160228150503.zip. I installed using TWRP. Install looks it went fine then I rebooted and bootloop.
HTC M9 (t-mobile)
Unlocked
TWRP version - twrp-3.0.0-2-hima
After installing "BETA-SuperSU-v2.68-20160228150503.zip" my phone is stuck in bootloop. It has rebooted at least 5 times. I then was able to get into HTC download mode.
What can I do now? I have a full nandroid backup.
Click to expand...
Click to collapse
Restore your boot partition or dirty flash rom
Fixed
Thanks thicklizard for the quick reply,
Ended up booting back into twrp and installing BETA-SuperSU-v2.65-20151226141550.zip (aka version 2.65). Connected phone the PC while I was in TWRP, copied older zip file then installed. That fixed the issue and now I am rooted.
cloves said:
Thanks thicklizard for the quick reply,
Ended up booting back into twrp and installing BETA-SuperSU-v2.65-20151226141550.zip (aka version 2.65). Connected phone the PC while I was in TWRP, copied older zip file then installed. That fixed the issue and now I am rooted.
Click to expand...
Click to collapse
Im having the same issues i flashed over the supersu 2.65 but still stock... what older zip file did u install?
willardwellls said:
Im having the same issues i flashed over the supersu 2.65 but still stock... what older zip file did u install?
Click to expand...
Click to collapse
Flashed via twrp 3.0.0-2
This is the file:
https://download.chainfire.eu/752/SuperSU
FYI, if you are flashing a ROM, sometimes they have superSU already built in. So no need to flash your own superSU. That is the case with Viper ROM. Also make sure your firmware matches the firmware that the rom is using.
I had the same problem with SuperSU 2.76. I wiped dalvik cache and cache twice, flashed SuperSU 2.64 and no more bootloop. No backup, stock ROM. I almost crapped myself a little. About to give this thing it's first ROM flash.
Just had the same problem. Put on 2.65 and it's now booting into the OS. Thanks!
Thanked God i found this post, tried latest stable also beta seems bootloop never ends. Try v2.6 all become alive. Many thanks Sir
Same problem after installing latest SuperSu version from TWRP recovery: eternal bootloop. I didn't know what was wrong and tried different supersu versions but I became reluctant to keep trying that method after the second time... Gladly, I found your thread before doing anything else (even posting myself a thread) and now I can continue my evil rooting plans :victory: Thank you for asking and thanks for replying you prevented me to re-lock my phone and do everything from scratch. It's my first root
You're welcome guys, rooting this htc has been the best thing i have done. Let's keep the HTC community in here alive and well!
I recommend once you get the root part done backup then install xposed framework. No ads, YouTube play back without screen being on, best software once you are rooted.
Sent from my HTC One M9 using Tapatalk
cloves said:
You're welcome guys, rooting this htc has been the best thing i have done. Let's keep the HTC community in here alive and well!
I recommend once you get the root part done backup then install xposed framework. No ads, YouTube play back without screen being on, best software once you are rooted.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I beg to differ about xposed. One wrong mod and you're phone is bricked.
Beamed in by telepathy.
I have not had any problems with exposed and that's why I said make a backup on your card. I have installed multiple Xposed modules and have not had any issues I have not seen anybody break the phone either. As I mentioned make a trip back up what is the point of rooting your phone if you're not going to use it to its full potential that's just me
Sent from my HTC One M9 using Tapatalk
Me too - Bootloop
I have an AT&T HTC One M9. Bootloader is HtcDev Unlocked, S-On, and TWRP is installed...
I previously messed up my phone bad by trying to install a OS ROM that didn't work right... So, I used my PC to overwrite it with the HTC OTA version, and that worked. I went into the M9 and tried to download and run SunShine, to get S-OFF, but it said it couldn't temproot, I don't know why, it's pissing me off, and SunShine suggested I root the device with another means. I downloaded SuperSU 2.69 and tried that, it installed okay (I guess) and said it might loop a few times. Try 100! Infinite loop. I tried SuperSU 2.65, but it said, "it's already patched!" and the system ROM had not been backed up. (I'm assuming SuperSU patches whatever is in the system partition?)
Anyhow, it's currently stuck in an infinite loop. I'm going to try re-putting the HTC OTA system ROM on it (great, I lose another half-day at this), and then re-try SuperSU 1.65.
Any idea why SunShine won't S-OFF a device? Why won't temproot work? Any other (good) way to root it?
Twrp question?
I have twrp 3.0.0 installed I make a backup of system and boot... when I boot in the first time on twrp displays a message saying something about OTA protection if I want to receive otas and protect the recovery??? What is that... sorry for my bad English is not my mother language...
thanks dude
Skorpyun812 said:
I had the same problem with SuperSU 2.76. I wiped dalvik cache and cache twice, flashed SuperSU 2.64 and no more bootloop. No backup, stock ROM. I almost crapped myself a little. About to give this thing it's first ROM flash.
Click to expand...
Click to collapse
i am stuck and say my phone going to crab but your post save me
cheers
---------- Post added at 10:53 AM ---------- Previous post was at 10:51 AM ----------
White91 said:
I have twrp 3.0.0 installed I make a backup of system and boot... when I boot in the first time on twrp displays a message saying something about OTA protection if I want to receive otas and protect the recovery??? What is that... sorry for my bad English is not my mother language...
Click to expand...
Click to collapse
i think your s-on on bootloader mape it off then install recovery

Htc One M8 Bootloop

Hi, I have and HTC One M8 6.0 with twrp 2.8.7.0. When I was going to turn of my phone to flash supersu, it gave me the option to install it there. So I said yes on the twrp menu. It never turned on again(stuck in the logo). I can access the bootloader but I think that usb debugging is off. In bootloader when you go to factory reset, it gives an error in twrp(failed). Is there anyway I cant lock the bootloader because usb debigging is off, when doing the steps to lock the bootloader(the ones in htcdev), it says <waiting for device>. I have nothing in the phone right now. Any way to fix the bootloop?
Thanks.
pasatmalo said:
Is there anyway I cant lock the bootloader because usb debigging is off
Click to expand...
Click to collapse
Relocking bootloader is done by fastboot, not adb. Fastboot and adb are related, but different requirements:
adb: only worksin OS or alternately TWRP. Requires debugging on.
fastboot: Only works in bootloader-fastboot mode, does not require debugging on.
However, I don't immediately suggest relocking the bootloader (presumably to RUU to stock); at least until trying some other things (below). As it may be possible to just do the root properly and make the phone work; rather than RUU and starting over.
pasatmalo said:
Hi, I have and HTC One M8 6.0 with twrp 2.8.7.0. When I was going to turn of my phone to flash supersu, it gave me the option to install it there.
Click to expand...
Click to collapse
The TWRP root option doesn't work. That is the whole reason for flashing SuperSU.
Also, you should use SuperSU current stable version 2.76. Some previous builds will also probably be fine, but you may need to flash an insecure kernel separately on some older versions for the full system root. SuperSU builds before 2.52 or so simply will not work on Marshmallow, and will result in being stuck on the HTC logo screen.
My recommendation, is to install current version TWRP 3.0, then try to flash SuperSU 2.76, and see if it gets the phone working (and with root). If not, we'll go from there.
Also, I also would advise in the future, to always make a TWRP backup before rooting or other mods. That way, if the mod/root fails, you can simply restore the backup in TWRP, and have a working phone. Too many folks skip this step. Maybe since it goes unmentioned in root guides. But its really just basic (and wise) procedure for rooting/modding.
redpoint73 said:
However, I don't immediately suggest relocking the bootloader (presumably to RUU to stock); at least until trying some other things (below). As it may be possible to just do the root properly and make the phone work; rather than RUU and starting over.
The TWRP root option doesn't work. That is the whole reason for flashing SuperSU.
Also, you should use SuperSU current stable version 2.76. Some previous builds will also probably be fine, but you may need to flash an insecure kernel separately on some older versions for the full system root. SuperSU builds before 2.52 or so simply will not work on Marshmallow, and will result in being stuck on the HTC logo screen.
My recommendation, is to install current version TWRP 3.0, then try to flash SuperSU 2.76, and see if it gets the phone working (and with root). If not, we'll go from there.
Also, I also would advise in the future, to always make a TWRP backup before rooting or other mods. That way, if the mod/root fails, you can simply restore the backup in TWRP, and have a working phone. Too many folks skip this step. Maybe since it goes unmentioned in root guides. But its really just basic (and wise) procedure for rooting/modding.
Click to expand...
Click to collapse
Hi thanks very much, I just solved it by flashing a newer version of SuperSu like you said. One question, to update TWRP from 2.8.7.0 to 3.0.2.0. Do I need to reflash it from the computer, and if so, will it wipe my data? Im pretty new so I dont know much. In TWRP I cant flash the new one because I cant see the .img.
Thanks.
pasatmalo said:
I just solved it by flashing a newer version of SuperSu like you said. One question, to update TWRP from 2.8.7.0 to 3.0.2.0. Do I need to reflash it from the computer, and if so, will it wipe my data?
Click to expand...
Click to collapse
Yes, flash from computer with fastboot. No, it won't wipe your data. But always backup anything important to you, just to be safe, even when not flashing things.
Also, if you already flashed proper version SuperSU, and the phone is working; there isn't in immediate need to update TWRP. Unless you intend on flashing other things with recovery, or creating TWRP backups. In which case, its recommended to use an updated version.

Can't boot into recovery after cm14.1 nightly official

So as the title says, after flashing cm14. 1 can't go into recovery anymore, it just a black screen. I tried to use flashify but nothing, a couple of apps show that I have twrp 3.0.2.1 but can't get into it... Help?
Cheers
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Which thread is this from please?
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Yeah man im in the same boat, if i get time ill try this twrp recovery. Where did that recovery come from?, it seems like the CM recovery for 14.1 nightly high jacks the recovery partition (i call it that,i dont know the term for it)
Sent from my ONEPLUS A3000 using Tapatalk
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Hw4ng3r said:
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Click to expand...
Click to collapse
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Thanks a lot guys, that did the trick, and done with flashify
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
@JKMB888 it does work 100% is as simple as flashing the TWRP. Actually, i installed it with CM 14.1 running just fine
Sent from my ONEPLUS A3000 using Tapatalk
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Edit: I found the solution, i had a pattern lock screen and i removed it!
HC4Life said:
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Click to expand...
Click to collapse
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
GrandMasterB said:
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
Click to expand...
Click to collapse
Look at my edited reply...
m4manusraj said:
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Click to expand...
Click to collapse
actually flashify did the trick for me as I had no access to a pc for the time
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
i am facing just the same situation with cm14.1 nightly and can't boot into recovery
i tried flashing the recovery image provided by you i.e. twrp-3.0.2-22-oneplus3.img but i face the same problem again
when i go into the recovery all i see is a black screen with a white notification light on and it remains there untill i switch off my phone manually using the power button
i tried facing the problem when i installed the cm14.1 nightly
i was unable to login snapchat as i device was rooted as said by the message on snapchat
so i decided to unroot my device via supersu FULL UNROOT option
after a reboot i successfully logged into snapchat
then i tried to root it again
i went into recovery to flash the supersu zip
and since then i have been unable to see the twrp recovey
please help me
This thread is a life save. Tried everything and it drove me nuts not getting into recovery.
THANK YOU!
gangangan2 said:
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
Click to expand...
Click to collapse
Thank you so much it's work for me now..
After I got the recovery back, I flashed CM13 again and ARM64 6.0 Nano Gapps for my Oneplus 3, but I'm getting an error after the "preparing apps' screen is loaded saying that - unfortunately the process android.process.media has stopped one plus 3 boot and then the phone switches off.
Any solution to this? I've already tried flashing different versions of CM13.
Thank you!! I was looking for hours.
This link fixed the problem!
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Hey, guys. I'm pretty sure I bricked my phone and there's no way to get out.
So I was on CM13 official builds on my OP3. Then, on the OTA update system they have, I got moved onto the CM14.1. I downloaded from here and went into my twrp recovery to flash. I made a clean flash and then proceeded to go back to system. I thought everything was ok until I realised I hadn't flashed a gapps package which I pretty much need to survive as all my contacts backups etc. are on there. I powered off my phone and went to go back into the recovery after downloading gapps 7.1 micro. It went past the *You're device can not be trusted'* and then went to the oneplus screen. After that, it stayed like that for about 30 secs and powered off. At first, I thought I messed something up and tried again. I repeated that for about 3 times and it didn't work. I tried going into the normal system and coming back to recovery and it didn't work still. In fact, now I can't even get into system. Now, i can only boot up to fastboot, where my computer still doesn't realise my phone is plugged in.
Anyone got any ideas on how to fix this? I wouldn't say I'm a noob at this because I have flashed many times before but I'm relatively new to the scene. I didn't see this thread before i ripped my hair out and i think wrecked my phone @JKMB888
EDIT: I sorted it out with help from Naman Bhalla's unbrick thread and this. A certain combo works and now I'm on CM14.1 enjoying life

OnePlus 3 keeps booting into TWRP Recovery Mode - PLEASE HELP!!

I will try to explain what happened as best as possible.
I wanted to install the AKT Profile on my un-rooted one plus 3 and so I decided to root it.'
I looked up on google and used the OP3 All In One ToolKit to unlock bootloader and flash TWRP.
Then I booted up phone to download SuperSu in order to flash it.
This is where the problem began. I went into TWRP recovery mode and it asked for a password and that stopped the nandroid backup too. but I googled and found out that doing a Wipe helps you bypass the password bug, so I did that. Now I went ahead and did a nandroid backup.
This is where I don't understand what's going on. How much ever I try to reboot the device, it ONLY loads me back into TWRP Recovery screen.
I even tried to restore the backup, it completes the restore but I dont see any reboot option right after it is done, So i have to long press power button to reload back into TWRP.
Now I'm confused as to what to do and would REALLY appreciate help, ASAP.
P.S - I'm a noob so I probably wont understand high level jargon
thank you guys in advance :crying:
SOLVED : I flashed TWRP 3.0.3 once again and somehow it got fixed
'' doing a wipe help you bypass the password''... Well yes probably, but depending on what type of wipe, you might have wiped your rom/system. So if that is the case, there is no rom to boot into, and your stuck in twrp recovery. Restoring an empty Nandroid wont do anything either. So my guess is you will have to download stock or custom rom and do a fresh install.
If needed, this method works very well.
I used it to day, with success.
Good luck !
Thank you. but will this work with latest TWRP 3.0.3 or will i have to use old one as mentioned in that post?
Use latest twrp 3.0.4.0. Also for clean install with OOS 4.02 or OB11. Also keep both firmware and supersu/magisk superuser close by. You can find all dl-links on xda.
rshah0429 said:
I will try to explain what happened as best as possible.
I wanted to install the AKT Profile on my un-rooted one plus 3 and so I decided to root it.'
I looked up on google and used the OP3 All In One ToolKit to unlock bootloader and flash TWRP.
Then I booted up phone to download SuperSu in order to flash it.
This is where the problem began. I went into TWRP recovery mode and it asked for a password and that stopped the nandroid backup too. but I googled and found out that doing a Wipe helps you bypass the password bug, so I did that. Now I went ahead and did a nandroid backup.
This is where I don't understand what's going on. How much ever I try to reboot the device, it ONLY loads me back into TWRP Recovery screen.
I even tried to restore the backup, it completes the restore but I dont see any reboot option right after it is done, So i have to long press power button to reload back into TWRP.
Now I'm confused as to what to do and would REALLY appreciate help, ASAP.
P.S - I'm a noob so I probably wont understand high level jargon
thank you guys in advance :crying:
Click to expand...
Click to collapse
Had the same problem and panicked like hell. I just switched a few twrp recoveries (modded and official) and found one that worked and phone booted.
Seagorilla2 said:
Use latest twrp 3.0.4.0. Also for clean install with OOS 4.02 or OB11. Also keep both firmware and supersu/magisk superuser close by. You can find all dl-links on xda.
Click to expand...
Click to collapse
thank you. i will try this
Seagorilla2 said:
Use latest twrp 3.0.4.0. Also for clean install with OOS 4.02 or OB11. Also keep both firmware and supersu/magisk superuser close by. You can find all dl-links on xda.
Click to expand...
Click to collapse
I can't find TWRP 3.0.4.0 Can you please link it?
rshah0429 said:
I can't find TWRP 3.0.4.0 Can you please link it?
Click to expand...
Click to collapse
See Here
https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img
Its not official but working for me...
Try flashing the stock recovery. I got stuck in recovery loop after the OTA update got installed over twrp. Flashed the stock recovery and right away it booted me to the rom.
It's a problem of older twrp with nougat so you need to flash twrp new version

Help With Twrp+Root

Hey guys n gals
Smashed my s8+ the other day accidentally so picked up a z2 play for something completely different for me, but I am having issues with recovery and then root..
I've unlocked the bootloader that was simple, my problem first starts with doing Twrp, I flash it, boot up, then instantly prompted with the password for decryption. From what I read on the post for installing Twrp that should come after? My data partition vanishes and I think I changed it to ext4 so it worked, phone booted and all was well, so I went to do magisk 16 (I'm running stock 8.0) flash it all is well then when I boot up the phone just boots, shows the unlocked bootloader message, then keeps doing that and sometimes it boots to recovery randomly..
Not sure if I've missed something when doing thel processes but followed the instructions to the letter and I always end up having to reinstall stock and start fresh. Any help would be greatly appreciated!
Saome time the Magisk make you a bootloop. try to uninstall it.
Mark2014 said:
Saome time the Magisk make you a bootloop. try to uninstall it.
Click to expand...
Click to collapse
Via TWRP?
CptUnicorns said:
Via TWRP?
Click to expand...
Click to collapse
Yep, download Magisk uninstaller ZIP file and flash it.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Categories

Resources