Bootloop to bootloader - One (M8) Q&A, Help & Troubleshooting

So I tried to root my phone by downloading weaksauce, said root worked, root checker confirmed. Downloaded TWRP from google play, installed. Tried to boot to recovery and that is all the phone will let me do now.
I can boot to twrp, flash different roms, connect via fastboot.
I have tried 4 different roms, going back to stock, updating the firmware, updating the boot.img, switching to philz recovery, going back to TWRP, the RUU (model id error), switching to super CID, switching my MID
So basically all I can access on my phone now is the bootloader and whatever recovery I put on it.

Related

[VZW Edition]Cannot get into Recovery Mode

When I try to get in custom recovery, it seems that its working(Entering recovery mode in splash) but then boots into fastboot. when stock, it doesnt.
Ive tried adb reboot bootloader, Flashify, TWRP Manager, and hboot method.
This happened after changing CID and MID to make this device to unlock LTE freq, but I rolled back it all...so i think this couldnt be an issue. Of course i've wiped data and cache, flashed Stock image, relock and unlock.
sorry for my bad english.

Help Please. Soft-Bricked Device

Hello all!
I recently flashed the 4.16.xx firmware to my device. I am now stuck on the Bliss Rom bootscreen for some reason. Booting into recovery takes me to stock recovery and the phone isn't being recognized through ADB on several different PC's.
Am I screwed here? Any options?
Thanks for any input.
Try going into the fastboot option from the hboot (or called bootloader to many people. To get to hboot, do power and volume down when the phone is booting up. ) and try flashing your TWRP recovery from there. Also make sure your drivers are working.
If you don't know how to flash recovery just Google it, you should be fine.
Dw, dont panic, it'll be fine xD
Zomb!e said:
I recently flashed the 4.16.xx firmware to my device. I am now stuck on the Bliss Rom bootscreen for some reason. Booting into recovery takes me to stock recovery and the phone isn't being recognized through ADB on several different PC's.
Click to expand...
Click to collapse
Stock recovery is the logical result for flashing firmware, unless the firmware was hacked to remove stock recovery.
adb not working, is also normal. You need to be in OS or recovery to use adb commands (and I don't know whether you can with stock recovery). adb does not work in bootloader.
If you flashed an official firmware with s-on, then not boot is also the expected result.
You need to unlock the bootloader again, flash TWRP back onto the phone, and flash a ROM.
redpoint73 said:
Stock recovery is the logical result for flashing firmware, unless the firmware was hacked to remove stock recovery.
adb not working, is also normal. You need to be in OS or recovery to use adb commands (and I don't know whether you can with stock recovery). adb does not work in bootloader.
If you flashed an official firmware with s-on, then not boot is also the expected result.
You need to unlock the bootloader again, flash TWRP back onto the phone, and flash a ROM.
Click to expand...
Click to collapse
Hey thanks for the reply!
I figured it out finally and forgot to update the post. I ended up finding and flashing a Lollipop RUU from the SDcard and that got me booted up. Then I just had to re-flash TWRP, re-root and flash a new rom.
All is well now. Thanks for trying to help out.

Sprint HTC one m9 fail

I previously rooted my htc one with s-off as well. Had TWRP 2.8.6.4 and Viper ROM. I recently decided to use the htc again and tried updating everything. First, I flashed new Viper ROM. ROM wouldnt boot up but gave successful install. I can only assume because the firmware was out of date on my phone. I then tried flashing TWRP 302 img and now phone wont boot into twrp. I was able to get into download mode, bootloader and thats it. I downloaded the Batch tool and did cmd/ adb reboot download. It took my phone to a black screen with a security warning about flashing any rom not fron htc can get you info stolen. I then tried fastboot flash zip rom.zip Unfortunately the rom.zip i had from Sneakyghost's firmware page isnt compatible with my sprint phone. I am looking for the correct zip to flash. It seems that i am committed at this point to this method because i cannot reboot into bootloader anymore. At least i think i cannot. Any help is greatly appreciated. Thank you
I was able to restart phone back into bootloader
i can access download mode as well but cannot boot into recovery mode
Software status : modified
Unlocked
s-off
Whenever i try flashing a slightly older version of TWRP i get a successful flash on both phone and computer but it still wont reboot into recovery

How To Flash Custom Recovery for Androidone

So, I was attempting to root my phone(CanvasA1- 4GB) today running stock android marshmallow(6.0.1) , I successfully unlocked the boot loader in fastboot using adb, after which I flashed TWRP recovery, Which was successful but then, When I rebooted into recovery, I saw my old stock google's recovery running , I tried 2-3 more times flashing the recovery in fastboot but the probem was still the same :crying:. Then I came to know that we have to flash a special type of boot img of some 17.5mb approx, When I attempted to flash this "boot" image, I received an error saying file size too large, Hence I couldn't flash it, I am still running the stock recovery, With my bootloader unlocked, I need to root my phone, Please help someone, Thanks in advance .
http://forum.xda-developers.com/cro...-master-tool-unlock-bootloader-t2997696/page1 use this tool and flash custom recovery simple
You can search for Android One Toolkit. Iwas encountering the same problem but this app solved my Problem.
Sorry dont have Link for the Same.
Same here. I unlocked the bootloader successfully and flashed TWRP recovery. But it shows system/default recovery only. Now stuck in bootloop.
Tried clearing cache/date etc. nothing worked. Don't know what to do.

Pixel C OTA using Flashfire - stuck on "waiting for fastboot command"

I have a Pixel C, rooted using the Nexus Rootkit, TWRP and SuperSU.
All was fine and was on build N2G48C.
I had an OTA notification for Oreo, so I downloaded the OPR6.170623.010 Oreo OTA file, and used FlashFire to apply this.
Now everytime it reboots it goes past the Google logo, then to the "waiting for fastboot command" screen. I've tried rebooting to Recovery and I get the same thing!
Google didn't seem to help, so please can anyone else help?
I was manually flashing rather then using flashfire, but I was getting the same problem. First, flash just the stock room (no root or TWRP) and check that it boots. Mine would, but every time I tried to flash TWRP, it would bootloop to fastboot.
You may want to download the full rom, not just the ota. You can modify the flash batch file to not wipe the tablet, or just flash the components.
What was finally successful for me was to flash TWRP and NOT let it finalize. It should ask if you want to mount R/W so it can keep the rom from overwriting the recovery. I told it no, then flashed the Magisk zip for root. I haven't tested SuperSU, but just replace it here to try. This got me a proper boot to Oreo, with Magisk working correctly.
If I understand it right, and I haven't booted to recovery to check, the rom will likely have overwritten TWRP. Worst case, I have to reflash recovery whenever I want to do a backup or update my rom, but that isn't something I do often on this tablet.

Categories

Resources