Develop Bugs

Boot looping issue

Was messing around with my phone flashing roms to see what I liked best and got too far ahead of myself and forgot to wipe data and cache. Now, I'm stuck in some kind of "boot loop" and can't get back into ClockWorkRecovery(Via root) to perform a restore. My computer just isn't recognizing that I have my phone connected now although it did previously. Is there anything I can do in this situation, or am I basically screwed?
Edit: I solved the issue on my own, it just took lots of playing around and disconnecting/reconnecting before I was able to get back into CWR. If a mod sees this, go ahead and delete this thread it has no purpose.

HELP
Please, i have the same issue
My phone has been bootlooping for a week now, so much i decided to give up.
Please please please tell me how you got back to clockwork and then from there what to do
Thank you so so much in advance

My guess, and this is only a guess, is to try the following.
Assuming you have already flashed the ENG build...
1. Place a new update.zip (clockwork recovery) onto root of the phone's SD card (probably using a card reader, just to be on the safe side).
1.5 Turn the Phone off, if it's on.
2. Hold down Volume Down + Power Button to turn on the phone and boot into the phone's default recovery.
3. Press Volume Up + Power button to get the selectable menu.
4. Select the "Apply update.zip" option (2nd one down).
5. This should boot you into the Clockwork Recovery.
From there, locate the ROM you want to use that's meant for the Slide (like SlidemeRoot 5).
1. Download the ROM.
2. Navigate to the mount menu in clockwork and select the option to mount the card as USB Mass Storage.
3. Plug the phone into the PC (via USB cable).
4. Copy the ROM to the card.
(My trick here is to redownload ROMs. I've seen my phone bootloop when the ROM doesn't download all the way.)
1. Unmount USB.
2. Navigate to the Wipe Data/Factory Reset option.
3. Select Yes from the menu to wipe everything.
4. Locate the install any zip option and install the ROM
5. When that's done, select the reboot option.
From here, you can just leave the phone alone until it boots. If you worry or want to watch, use adb to watch the logs.
1. In command prompt, navigate to where you have ADB installed.
2. type in: adb logcat
3. Enjoy.
For me, the first boot for SlidemeRoot took at least a minute. I could see the logs rolling along, so I just left it alone until the logs slowed down and then stopped. By then, the phone looked like it was ready to go (complete with normal screen, signal, and everything).

I did the same thing, but I havent flashed my rom with the eng build, is there anything I can do, or is my phone hosed? My phone wont boot, and I cant get it to boot up in clockwork, so I cant reflash it...

[Q] Phone soft bricked? Unable to used ADB or Memory Card

Hello everyone,
I got my AT&T HTC M9 yesterday with 1.32.502.9. I unlocked the bootloader and installed TWRP successfully. I tried Installing Android Revolution 4.1 and didn't noticed the installation failed. When I restarted the phone it got stuck on the HTC logo. Someone after messing with the phone I ended up loosing TWRP and I'm back to the stock recovery with only these options:
reboot system now
apply updates from ADB
wipe data/fatory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
apply from phone storage
apply from sd card
My phone is stuck at the logo screen and I cannot sideload or flash anything from the SD memory card or phone storage. My phone gives me an error when I try to flash from the SD card and my computer now does not detect my M9 (all drivers were installed previously as well as the SDK)
I don't want to do anything else yet because I'm afraid I will make things worse. Could any body advice me on how to fix my phone?
Thank you!

I was able to fix it.
Admin: Please delete this thread. Thank you!

tchan said:
I was able to fix it.
Admin: Please delete this thread. Thank you!
Click to expand...
Click to collapse
@tchan how did you fix it? I am in the same situation myself.

MightyRaith said:
@tchan how did you fix it? I am in the same situation myself.
Click to expand...
Click to collapse
You have to switch to the download mode on your M9 and use the fastboot command to flash a custom recovery (TWRP2050 worked for me). Make sure your SDK is up to date and you download and install all the HTC drivers for the M9.
This might help: http://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133

tchan said:
You have to switch to the download mode on your M9 and use the fastboot command to flash a custom recovery (TWRP2050 worked for me). Make sure your SDK is up to date and you download and install all the HTC drivers for the M9.
This might help: http://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133
Click to expand...
Click to collapse
Sadly I cannot enter download mode or recovery mode the phone simply reboots I had TWRP installed with LeeDroid and everything was peachy now I can't do a single thing with it lol.

MightyRaith said:
Sadly I cannot enter download mode or recovery mode the phone simply reboots I had TWRP installed with LeeDroid and everything was peachy now I can't do a single thing with it lol.
Click to expand...
Click to collapse
Shut the phone off,wait 10 seconds then hold volume down and start button. After a few seconds, it wil vibrate, release the buttons and it should start in donwload mode (black background).

MightyRaith said:
Sadly I cannot enter download mode or recovery mode the phone simply reboots I had TWRP installed with LeeDroid and everything was peachy now I can't do a single thing with it lol.
Click to expand...
Click to collapse
Turn on you phone and wait about 10 seconds after seeing the HTC logo. Hold down the volume up button and power button for a few seconds until the phone vibrates, as soon as that happens switch to the volume down button and power button that should put the phone in "download mode." Connect your phone to your PC. On your command prompt you can type "fastboot devices" to check and make sure your phone is good to go. After that, you should be able to flash TWRP which in turn would allow you to flash a custom rom and fix your phone.

tchan said:
Hello everyone,
I got my AT&T HTC M9 yesterday with 1.32.502.9. I unlocked the bootloader and installed TWRP successfully. I tried Installing Android Revolution 4.1 and didn't noticed the installation failed. When I restarted the phone it got stuck on the HTC logo. Someone after messing with the phone I ended up loosing TWRP and I'm back to the stock recovery with only these options:
reboot system now
apply updates from ADB
wipe data/fatory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
apply from phone storage
apply from sd card
My phone is stuck at the logo screen and I cannot sideload or flash anything from the SD memory card or phone storage. My phone gives me an error when I try to flash from the SD card and my computer now does not detect my M9 (all drivers were installed previously as well as the SDK)
I don't want to do anything else yet because I'm afraid I will make things worse. Could any body advice me on how to fix my phone?
Thank you!
Click to expand...
Click to collapse
please be patient
I don`t have m9 now but if you do this solution,maybe your phone boot up again ( this solution works on m8 )
I don`t think your phone bricked or damaged memory
you can do this solution,maybe your phone fixed !
1- charge your phone then update the htc usb driver and adb tools
2- then boot to the bootloader and flash the latest twrp recovery again ( don`t forgot do erase cache)
3- download other rom like viper rom then copy it on the flash memory ( to install rom with otg cable and flash memory)
4-do full wipe ( internal and external memory - system - cache - dalvik cache)
5- install rom from flash memory and do full wipe again in aroma installer
6- then restart your phone and wait to phone boot up again
7- if don`t boot up,go to the bootloader and flash boot.img from rom ( you should extract rom to see it )
after all you can s-off your phone if you like
good work:good:

my_android said:
please be patient
I don`t have m9 now but if you do this solution,maybe your phone boot up again ( this solution works on m8 )
I don`t think your phone bricked or damaged memory
you can do this solution,maybe your phone fixed !
1- charge your phone then update the htc usb driver and adb tools
2- then boot to the bootloader and flash the latest twrp recovery again ( don`t forgot do erase cache)
3- download other rom like viper rom then copy it on the flash memory ( to install rom with otg cable and flash memory)
4-do full wipe ( internal and external memory - system - cache - dalvik cache)
5- install rom from flash memory and do full wipe again in aroma installer
6- then restart your phone and wait to phone boot up again
7- if don`t boot up,go to the bootloader and flash boot.img from rom ( you should extract rom to see it )
after all you can s-off your phone if you like
good work:good:
Click to expand...
Click to collapse
Thanks for replying but I was able to fix my phone a few hours after. Those are the right steps but you're missing some details. HTC has now changed things a bit and added the "download mode." Flashing in bootloader does not work any more.

Glad your all sorted !

Me 2 help !!!!
tchan said:
Hello everyone,
I got my AT&T HTC M9 yesterday with 1.32.502.9. I unlocked the bootloader and installed TWRP successfully. I tried Installing Android Revolution 4.1 and didn't noticed the installation failed. When I restarted the phone it got stuck on the HTC logo. Someone after messing with the phone I ended up loosing TWRP and I'm back to the stock recovery with only these options:
reboot system now
apply updates from ADB
wipe data/fatory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
apply from phone storage
apply from sd card
My phone is stuck at the logo screen and I cannot sideload or flash anything from the SD memory card or phone storage. My phone gives me an error when I try to flash from the SD card and my computer now does not detect my M9 (all drivers were installed previously as well as the SDK)
I don't want to do anything else yet because I'm afraid I will make things worse. Could any body advice me on how to fix my phone?
Thank you!
Click to expand...
Click to collapse
Everytime i try to send commands its does not respond , adb devices=NOTHING adb get-state=NOTHING
what did u flash ? When i reboot it only shows a red triangle with a exclamation point and now my computer does not detect my m9
Also have tried to start the RUU from the htc website with no luck it only goes as far a the accept licseing

May be you have to update adb/fastboot or your Htc's drivers...

tchan said:
Hello everyone,
I got my AT&T HTC M9 yesterday with 1.32.502.9. I unlocked the bootloader and installed TWRP successfully. I tried Installing Android Revolution 4.1 and didn't noticed the installation failed. When I restarted the phone it got stuck on the HTC logo. Someone after messing with the phone I ended up loosing TWRP and I'm back to the stock recovery with only these options:
reboot system now
apply updates from ADB
wipe data/fatory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
apply from phone storage
apply from sd card
My phone is stuck at the logo screen and I cannot sideload or flash anything from the SD memory card or phone storage. My phone gives me an error when I try to flash from the SD card and my computer now does not detect my M9 (all drivers were installed previously as well as the SDK)
I don't want to do anything else yet because I'm afraid I will make things worse. Could any body advice me on how to fix my phone?
Thank you!
Click to expand...
Click to collapse
I cant enter recovery mood or download mode adb is not reconized i even tryed adb get-state and nothing shows up
tried to sideload and when its done is say e:veracation failed then show this screen again

You're best sending it to htc.
Sent from my HTC One M9 using Tapatalk

bricked, stuck on recovery mode, what should I do next?

Hello,
I was trying to unlock the sim. I installed ZVC and later I wanted to change it ZVG. I used a software named "flashery" (or something like that), but I just flashed the root.img, and rebooted. Now the system boot into loops, only appears LG logo. I am able to enter into the recovery menu, which looks like:
=========================================
Android system recovery <3e>
KOT49I.LS980ZVC
reboot system now
apply update from external sdcard
apply update from cache
apply update from ADB
wipe data/factory reset
wipe cache partition
===========================================
It seems that the only way for me is to use "apply update from ADB", and my computer is able to detect the device by "adb devices"
Would you please let me know what are the next steps should I follow?
Thanks very much!!

Op3 only boots into twrp after failed update

Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...

I have the same problem

Here the same but with CM14 after a wrong download & install now Recovery Loop
How to solve???

I had this problem too. Flash the Oxygen recovery OB7. It will update automatically and turn on. But be patient because it takes a lot.

sibmon said:
Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...
Click to expand...
Click to collapse
The way I found works is to start from scratch and yes you will lose all data on the phone. Had to do this yesterday because I messed a few things up.
Make sure you have the modified recovery (1.28), Beta 9 Full (1.3GB), and SuperSU (SR5) if you want root, on your computer. And you will need your computer for these steps.
1. Boot to TWRP > Wipe > Format Data. There's a warning screen you just type yes and press enter. This should set your /data partition to F2FS; all other partitions will remain EXT4. (The TWRP MTP didn't pop up on me so then I had to reflash twrp from fastboot). If your PC see's your device after this step, skip to step 9, but my guess is, when you format data, the required files for MTP disappears with it.
2. Power off your device.
3. Put device into fastboot mode (start device by holding volume up + power)
4. Connect device to PC.
5. fastboot flash recovery modded_twrp.img
6. Disconnect device from computer and shut down phone.
7. Load recovery (start device by holding volume down + power)
8. Connect to PC
9. TWRP MTP should be working; transfer the recovery file, beta9, and super SU (if you want root) to your internal storage.
10. I usually disconnect my phone from my PC at this point.
11. Go to Install > sdcard > media folder (your files should be here).
12. Flash Beta 9 zip.
13. Reflash modded TWRP (click Install Image button and you should see your TWRP file).
14. Reboot to Recovery (I noticed that click on Reboot and Recovery freezes TWRP on me, so you can manually power down by holding power button down).
15. Swipe to accept modifications
16. If you don't need root, you're all done. The first boot takes like 5 min.
For some reason for root, it doesn't work if you try without freeing up some space in the system folder. What you can do is:
1. In TWRP > Mount > tick off System > head back out to main menu
18. Advanced > File Manager > > system folder > app folder > and delete some google apps (ie. calendar, gmail, chrome; should be enough; can be downloaded from play store later)
19. Flash SuperSU SR5.
20. Wipe Cache and Dalvik, reboot.
I've noticed that if you don't root, your device will be encrypted on first boot of beta 9 (which causes some issues in TWRP not being able to mount the /data partition and decryption passwords not working in TWRP.

Same problem here, **** broken OB9 update.
EDIT: For those with the same problem, download stock recovery from here, flash it using adb, boot into recovery (might say that installation of update failed, it did for me) and then reboot to system.
Now it booted successfully and says that I have Open Beta 9. TWRP and SuperSU installations worked just fine after that.

I used twrp-3.0.2-22 to reflash beta 9 all is well.
I have same problem with twrp-3.0.2-1.28. Just boot into bootloader and flash twrp-3.0.2-22.

Can I flash that twrp-3.0.2-22 after I'm already on beta 9?
Nevermind I saw that it encrypts on first boot. I'll just wait for root again until after the final comes out.

No need for clean installation like hw4ng3r said.
I'll copy my other post's edit here if someone needs it.
For those with the same problem, download stock recovery from here, flash it using adb, boot into recovery (might say that installation of update failed, it did for me) and then reboot to system.
Now it booted successfully and says that I have Open Beta 9. TWRP and SuperSU installations worked just fine after that.
Click to expand...
Click to collapse
Got 145849 AnTuTu result with OB9. Might be able to get a better result if I were to clean install, but I've just dirty flashed every update since 3.2.5.

karliyo said:
No need for clean installation like hw4ng3r said.
Click to expand...
Click to collapse
Very true.
I interpreted the OP's comment as:
1. Already on TWRP
2. Tried full wipe and install (all data lost anyways)
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
Tumpster said:
Can I flash that twrp-3.0.2-22 after I'm already on beta 9?
Nevermind I saw that it encrypts on first boot. I'll just wait for root again until after the final comes out.
Click to expand...
Click to collapse
I've read that .22 TWRP doesn't have decryption issues of the /data partition like .28 has, but don't take my word for it. And the encryption happened to me when I flashed Beta9 from TWRP .28 and rebooted system without flashing Super SU.
The decryption of the /data partition in TWRP seems to be an issue if the file system is F2FS on Beta 8 and Beta 9. I haven't had any issues with EXT4.

sibmon said:
Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...
Click to expand...
Click to collapse
Download stock recovery from OnePlus site (on very bottom) ,flash it using fastboot and than sideload new beta 9

Pixel Experience boot loop + string of stupid decisions: is there any way out?

Hi there,
I think I (soft? hard?) bricked my whyred today after trying to install Pixel Experience (Android 10). At this time, I'm left with a flashed PE Plus that is stuck at the Google logo animation (e.g. unable to access USB debug settings); stock MIUI recovery; and fastboot, which is not recognized by ADB as I haven't had a successful boot since I flashed PE, so I can't turn USB debug on. I think I've exhausted my options, but maybe someone has a smart solution.
For those who think they can help, let me describe in detail what I did:
0) I became a dev, turned USB debug on, installed Minimal ADB and Fastboot, latest Xiaomi drivers, moved flashable zips into internal storage etc.
1) I unlocked my bootloader through Mi Unlock.
2) I successfully flashed TWRP-3.3.1.0-whyred via ADB/Fastboot and rebooted. After getting back into MIUI, I booted into recovery, which was back to stock (MIUI seems to have overwritten my recovery). At that point (probably a big mistake) I gave up on flashing TWRP and went ahead to boot right into it via ADB instead, without flashing.
3) After a successful boot into TWRP 3.3.1.0, it asked me for a decryption password. Nothing worked, so I kept googling and found out that my version of android needs TWRP 3.3.1.1, which was not on the official TWRP website yet, to decrypt automatically. I booted into TWRP 3.3.1.1 via ADB (but didn't flash), made a backup of my stock ROM, did a wipe (art/dalvik cache, cache, data, system, vendor), flashed Pixel Experience and rebooted.
4) Bootloop, I was stuck on the Google loading animation for over 20 minutes, nothing happened.
5) I panicked.
6) I tried to flash TWRP 3.3.1.1 via ABD but my PC didn't recognize my phone - probably because, for lack of successful boots, I have not managed to turn on USB debug.
7) I tried to connect to Mi Assistant through stock recovery. It didn't recognize my phone, probably for the above reason.
8) I did a data wipe through stock recovery and rebooted, hoping for whatever issue kept PE from booting normally to get resolved.
9) I'm stuck on the same Google loading animation for over 40 minutes now, no progress.
Does any of you guys see a way out, or is this story over? To recap, I have: 1) PE Plus in bootloop, no access to dev settings, 2) stock MIUI recovery with options to reboot, wipe data or connect to Mi Assistant, 3) stock fastboot, 4) a backup of my previous system on internal storage, 5) ADB on my computer that doesn't recognize my phone - no USB debugging. I don't know where to turn. I don't care much about data, I have everything in the cloud, but I'd like to save the phone if possible.
Thanks a lot.
Edit: Problem resolved - even though the connected device didn't show up in ADB on PC (adb devices came back empty), the phone was still responsive to fastboot reboot and fastboot flash recovery via PC, so I could flash TWRP 3.3.1.1 & clean flash PE. For anyone struggling with PE bootloops: make sure to 1) use TWRP 3.3.1.1 to flash, 2) do a dalvik/cache wipe after flashing the ROM and 3) not to install the TWRP app before the first successful boot - it was neglecting either 2) or 3) that caused my bootloop. The ROM itself is amazing!

mkohan said:
Hi there,
I think I (soft? hard?) bricked my whyred today after trying to install Pixel Experience (Android 10). At this time, I'm left with a flashed PE Plus that is stuck at the Google logo animation (e.g. unable to access USB debug settings); stock MIUI recovery; and fastboot, which is not recognized by ADB as I haven't had a successful boot since I flashed PE, so I can't turn USB debug on. I think I've exhausted my options, but maybe someone has a smart solution.
For those who think they can help, let me describe in detail what I did:
0) I became a dev, turned USB debug on, installed Minimal ADB and Fastboot, latest Xiaomi drivers, moved flashable zips into internal storage etc.
1) I unlocked my bootloader through Mi Unlock.
2) I successfully flashed TWRP-3.3.1.0-whyred via ADB/Fastboot and rebooted. After getting back into MIUI, I booted into recovery, which was back to stock (MIUI seems to have overwritten my recovery). At that point (probably a big mistake) I gave up on flashing TWRP and went ahead to boot right into it via ADB instead, without flashing.
3) After a successful boot into TWRP 3.3.1.0, it asked me for a decryption password. Nothing worked, so I kept googling and found out that my version of android needs TWRP 3.3.1.1, which was not on the official TWRP website yet, to decrypt automatically. I booted into TWRP 3.3.1.1 via ADB (but didn't flash), made a backup of my stock ROM, did a wipe (art/dalvik cache, cache, data, system, vendor), flashed Pixel Experience and rebooted.
4) Bootloop, I was stuck on the Google loading animation for over 20 minutes, nothing happened.
5) I panicked.
6) I tried to flash TWRP 3.3.1.1 via ABD but my PC didn't recognize my phone - probably because, for lack of successful boots, I have not managed to turn on USB debug.
7) I tried to connect to Mi Assistant through stock recovery. It didn't recognize my phone, probably for the above reason.
8) I did a data wipe through stock recovery and rebooted, hoping for whatever issue kept PE from booting normally to get resolved.
9) I'm stuck on the same Google loading animation for over 40 minutes now, no progress.
Does any of you guys see a way out, or is this story over? To recap, I have: 1) PE Plus in bootloop, no access to dev settings, 2) stock MIUI recovery with options to reboot, wipe data or connect to Mi Assistant, 3) stock fastboot, 4) a backup of my previous system on internal storage, 5) ADB on my computer that doesn't recognize my phone - no USB debugging. I don't know where to turn. I don't care much about data, I have everything in the cloud, but I'd like to save the phone if possible.
Thanks a lot.
Click to expand...
Click to collapse
I'm new to this phone as well (but not to Android). Try the following:
Download TWRP from here -> https://androidfilehost.com/?fid=6006931924117884758
Download Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip from here -> https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
Power off phone. Hold down volume down and power button to boot into fastboot
Give the command fastboot flash recovery twrp-3.3.1-1-whyred.img to flash the recovery you downloaded earlier.
Boot into recovery
Flash Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip that you downloaded earlier
The above steps will at least ensure that you retain TWRP and it doesn't get overwritten by stock MIUI recovery
After that, check whether or not your phone/ROM has anti-rollback enabled and take appropriate steps accordingly.

Ok so i flashed PE 10 plus today and was met with the same problem.
Heres how i solved it
Goto fastboot option by pressing volume down and power button
Connect to pc (If it doesnt recognize, reinstall Adb drivers and phone drivers)
If it asks for decryption password just press cancel
Wipe data/internal/vendor (wont be able to wipe dalvik as it wont mount)
Flash PE 10 Plus and nothing else.
It should boot just fine.
However i run into bootloop if i flash latest magisk so i cant root my phone :/
Hope this helps

mkohan said:
Edit: Problem resolved - even though the connected device didn't show up in ADB on PC (adb devices came back empty), the phone was still responsive to fastboot reboot and fastboot flash recovery via PC, so I could flash TWRP 3.3.1.1 & clean flash PE. For anyone struggling with PE bootloops: make sure to 1) use TWRP 3.3.1.1 to flash, 2) do a dalvik/cache wipe after flashing the ROM and 3) not to install the TWRP app before the first successful boot - it was neglecting either 2) or 3) that caused my bootloop. The ROM itself is amazing!
Click to expand...
Click to collapse
hey read your post
actually adb and fastboot are two different things.
and recovery is flashed using fastboot commands not adb.
sometimes if a rom is not booting it may have issues with encryption.