Hello Everyone I am hoping there is a solution to this however I have been unable to find anything.
I flashed the latest OTA image via sideload and everything was fine until I tried to install TWRP. When trying to install the latest TWRP I could find ( 3.1.0-0RC2 ) my phone would then boot loop. I tried this process several times and each time after installing my phone would boot loop for 10 minutes until I forced it into fastboot, fast booted the TWRP image, and finally sideload the OTA once again.
I have seen a couple threads which I believe indicate that May update changed/broke something with the bootloader but I will be honest I
haven't read into it much.
This is on a Google version of the device with the bootloader unlocked. (failed to mention that).
Thanks in advance.
Bijiont said:
Hello Everyone I am hoping there is a solution to this however I have been unable to find anything.
I flashed the latest OTA image via sideload and everything was fine until I tried to install TWRP. When trying to install the latest TWRP I could find ( 3.1.0-0RC2 ) my phone would then boot loop. I tried this process several times and each time after installing my phone would boot loop for 10 minutes until I forced it into fastboot, fast booted the TWRP image, and finally sideload the OTA once again.
I have seen a couple threads which I believe indicate that May update changed/broke something with the bootloader but I will be honest I
haven't read into it much.
This is on a Google version of the device with the bootloader unlocked. (failed to mention that).
Thanks in advance.
Click to expand...
Click to collapse
Please read the other Posts about this
Flash the bootloader from april.
****************************
Download last months 7.1.2 factory image.
Extract it and find "bootloader-marlin-xxxxblahblah.img".
Rename it to "bootloader.img" for simplicity's sake, then move it to the side.
:Flash-all" the latest factory image, after its done stay in fastboot.
Run "fastboot flash bootloader_a bootloader.img" from wherever you moved the file to
Disregard if "partition_a" isnt your primary, once the command is ran it will auto flash to the primary partition.
Boot and setup, reboot back to bootloader.
Boot and install twrp, then reboot to recovery.
Delete fstab.marlin in main directory, then flash preferred supersu (i use 2.79 sr3).
Reboot to system and your done. from here reboot to recovery or bootloader to flash your preferred kernel and mods.
Was able to get this all sorted out.
If anyone else happens to see this thread with the same issues and missed the April bootloader deal you can find a good overview Here
To get the April bootloader image which is something I have never loaded myself you need to download the Factory Image from April then extract it. Inside there you will see the bootloader image.
Hope this helps anyone else who didn't read far enough into this issue.
Related
I just flashed the July security update, MTC19Z, using the flash-all script that it comes with then flashed TWRP 3.0.2 before the first boot and it never went to the boot screen with the Google logo, just on the warning page about my OS not being able to get checked. I thought maybe I needed to let it boot the first time so I reflashed with flash-all, let it boot up the first time, then flashed TWRP with the same results.
Not really looking for technical support, I'm sure the update broke TWRP just making a thread for awareness/discussion.
I submitted a bug report to TWRP's GitHub. It can be found here.
I flashed all the *.img manually and then flashed the newest twrp and it booted up fine...
I just flashed bootloader, radio, boot, system, vendor with fastboot then booted right into TWRP and flashed supersu not issues.
That is so strange, I guess I'll give it another go in a bit.
from bullhead-mtc19z ,the bootloader is updating to bhz10p ,not bhz10m again .
i think it will make some problems.
Every time i flash the latest TWRP for the HTC One M8 GPE on the newest update 6.0.1 June security update, when flashed in fastboot, once it completes, it will automatically boot into twrp, i select the option to allow system modifications, and when i reboot into system it boots just fine, but when booting back into the bootloader, and into TWRP I'm greeted with this screen.
any help would be appreciated, i tried searching the forum, but had no luck finding anyone else with this issue
Because you use command
fastboot boot NameOfTWRP.img
To correctly install TWRP, use command
fastboot flash recovery NameOfTWRP.img
ckpv5 said:
Because you use command
fastboot boot NameOfTWRP.img
To correctly install TWRP, use command
fastboot flash recovery NameOfTWRP.img
Click to expand...
Click to collapse
Thanks for the prompt reply!, I'll give it a try when i get home!
So i had success flashing TWRP properly, and can now boot into it, back up my OS etc, however, when i flash the latest version of chainfire root via TWRP i get a boot loop every time, I'm wiping the cache after preforming the flash, have any ideas what i might be doing wrong?
DeathSentinels said:
Showever, when i flash the latest version of chainfire root via TWRP i get a boot loop every time
Click to expand...
Click to collapse
What version number SuperSU are you using exactly? A lot of times, folks use what they think is the "latest", but when asked what version number, we find out its not even close to current (which has the common result of bootloop).
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.
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.
Shortly after receiving my bootloader unlock code, I made a real mess. First, I tried to install TWRP via these instructions: https://twrp.me/huawei/huaweihonorview10.html
Specifically, I used the ADB/Fastboot method. Unfortunately, when I went to reboot to recovery by holding power+vol-up, it always took me to the Huawei eRecovery, not TWRP. I assumed the install failed after multiple attempts, and thought I would try to root with Magisk so I could use the TWRP app to flash the recovery instead.
I downloaded the ramdisk.img from here: https://drive.google.com/drive/folders/1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
I found this link here: https://forum.xda-developers.com/honor-view-10/how-to/honor-source-program-t3732573
I then proceeded to patch it with Magisk and flashed the patched .img file. After doing this, the phone would bootloop a few times before ending up at the eRecovery again. I cannot get the eRecovery to get the packaged data for the Upgrade/Install recovery option, but when I choose the Factory Reset option, it reboots to TWRP (weird!) for about 3 seconds and then reboots to bootloader. I tried reflashing the original ramdisk.img when in the bootloader, but this made no noticeable difference.
My next guess is to try flashing recovery_ramdisk.img to try to remove TWRP and restore whatever stock image that was. I want some advice from the community first because I fear this may make things worse!
I saw that Magisk did in fact cause bootloops due to a compiler bug, according to this post: https://www.xda-developers.com/magisk-16-bootloop-crash-fix-huawei-honor-support/
Has anyone run into a similar issue? I assume since I can still get to the bootloader I can fix it, but I'm at a loss as to what the best next step is.
I flashed that recovery_ramdisk image. The result is that instead of booting to TWRP for a few seconds, it reboots into another eRecovery which allows me to do a factory reset and wipe the cache. After doing these, I still can't access the system.
So it turns out my device is BLK-104 and the problem was that I tried to flash files for BLK-109!
I'm surprised things worked as well as they did!