[SOLVED] Cannot boot anything after not bumping multirom twrp - G3 Q&A, Help & Troubleshooting

Hello lads,
I'm having the following problem:
I wanted to install the latest Dirty Unicorns weekly, as I'm using Multirom TWRP, I also reinjected Multirom after install, which places an openscript recovery script for twrp which is run everytime I try to boot into twrp, which doesnt get removed as I'm not able to boot into the rom, because bootloader gives out a "secure boot error" because the rom is not bumped anymore because of that. Can I somehow get into twrp without running that open recovery script?
Edit:
Flashed the usual TWRP via fastboot, now my device is operating again!

Related

Help trying to install twrp H811 TMO Marsh.

Hello so I've been trying to install twrp, so then after I can root. However whenever I boot into twrp using ADB, then install the twrp image, then after it's "successful", and I try to boot into recovery, it doesn't boot into twrp. I've tried using the buttons and it just shows the LG reset your phone option, and I've said yes but it just reboots my phone. And when I use adb to reboot into recovery it just reboots my phone. Any ideas? Here's the link: http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227

Trying to fix a recovery/gapps issue

I have a Samsung Galaxy G4 (T-Mobile version). I had a boot loop on Recovery problem with it. I reflashed the recovery a couple of times, TWRP and CM recovery. Neither wants to start up when I try to boot into recovery. (I have tried adb and using the keys.) Usually when I would flash a new kernel it would drop into recovery. When I upgraded to the nightlies, it went into recovery, installed the kernel, and rebooted.
Now I have a CM 13 kernel, but I am missing the proper gapps package.
Is there a way to install the gapps package with heimdall? Is there a trustable twrp app I can sideload? Is there a trick to get gapps to install with adb?
Looking for a useful solution. Thanks!
After flashing twrp using Odin, are you immediately trying to boot into recovery or are you restarting the phone and booting the rom?

Tried flashing Lineage OS but ended up stuck in a boot loop.

I unlocked the bootloader following Motorolas steps. I then flashed the latest version of TWRP avaiable on the development forum and then flashed Lineage OS + the root zip they provide and gapps. I couldn't figure out how to get out of the bootloop so I've since gone back to stock. Any idea what I was missing?
TWRP:
https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629
Lineage:
https://forum.xda-developers.com/moto-z-play/development/rom-unofficial-cyanogenmod-14-1-t3495644
Did you read the notices and entries on the Linage last pages of the thread that people are having it fail on the install, the latest release? That would be a clue...
I even tried flashing Pure Nexus but that too was stuck on a loop. I left it for about 10 minutes as it was loading. :/
I did the same thing like you on my first attempt, on my second I was able to install Lineage OS successfully. I'll provide the steps I did.
First attempt steps:
1. Unlocking the bootloader using Motorola website
2. Installing TWRP from the same link in your post.
At that point I tried booting the phone, but the phone was booting to TWRP only, tried wiping, format data from TWRP with no luck.
3. From TWRP flashed Lineage OS zip file and GAPPS nano package (the latest version of TWRP is able to see SD card).
At that point I was able to to boot LOS only after executing "fastboot erase user data". Doing the same from within TWRP was not doing the job. The problem was that after each reboot the phone was getting into bootloop again and "fastboot erase userdata" was necessary.
4. At that point I noticed that TWRP thread starts with warning that you have to install a patcher to disable this "verity" feature of the bootloader may be. And I installed the patcher "Verity_FE_patcher.zip"
The patcher didn't fix the issue and went back to stock Nougat using the guide below:
https://forum.xda-developers.com/moto-z-play/how-to/moto-z-play-reteu-firmware-otas-t3557917
First I tried "flashall.bat" , but it didn't wor.k and I flashed all the files manually using the guide . The phone booted normally and I updated it with one OTA update.
Second attempt steps:
1. I wanted to install the verity patcher before anything else and I boot TWRP 3.1.0.1 without flashing it. It booted normally and I realized that the SD card was formated and the patcher zip file is not there. I reboot the system and the phone got in bootloops again even the TWRP was not installed. I coppied the patcher zip, LOS zip, GAPPS zip on SD card . I tried to boot (without flashing) TWRP again, but for some reason TWRP was not able to boot.
2. I flashed TWRP
3. Booted TWRP and flashed verity patcher.
4. Wiped from TWRP and boot the system
At that point I was able to boot the stock firmware with TWRP installed and I was able to restart the phone normally.
5. Flashed LOS and nano GAPPS
Now everything seems to work properly.
Hope this will help.
Thanks. I'll give this a shot tonight. Our first attempts sound very alike.

boot certification error with bump'd twrp imgs

Hi
I've tried 3 different twrp images, all supposedly bumped (take this one for example), but when I try to boot to recovery with any of them I still get the boot certification verify error and can't get into recovery
running rooted 5.0 stock wiped, installed by instructions in linked threads
Thanks
update: used autorec, can now access recovery... but it's twrp 2.8.6... can I install fulmics on this version, or how do I update it?
update 2: TIL that you can update twrp from inside twrp and it still works, but that still leaves me confused with the above problems

[SOLVED] HELP! i'm stuck in a boot loop! :(

my flashing history:
i was on audax (oos based nougat rom) with blu spark kernel before, then went to official ob1, then back to audax, then back to stock oos nougat and now i flashed audax and after clean flashing it, it just wont boot up.
when i try to boot up i see the 1+ logo but then it reboots to recovery. i also tried flashing stock nougat again and also flashed stock kernel manually but it also doesnt work.
i always do:
1. wipe system/dalvic/cache/data
2. install ROM
3. wipe dalvik/cache
4. flash magisk (also tried without flashing magisk)
5. reboot
i've been looking on the interwebs all day but nothing worked.. help pls :/
EDIT: problem was blu spark twrp. Maybe installing Oreo ****ed it up. I flashed codeworkx newest twrp universal build and now Im able to boot again!! Btw: I also found that magisk 15.0 prohibits a proper boot up and results in a boot loop. version 15.2, however, does the trick!
when it auto reboot to recovery, formate data
When s**t happens, it is wise to start everything from scratch:
-boot in fastboot mode and flash stock recovery with "fastboot flash recovery recovery.img" (rename recovery.img with your recovery filename), then reboot recovery and select english, advanced, adb sideload;
-flash stock OS with "adb sideload rom.zip" (rename rom.zip with your Oxygen OS filename).
Procedure will require some minute because of the large file size. Remember to save all your data on internal storage first!
I advice you to flash original recovery because often sideloading in TWRP leads to some error.
Your phone will boot again... after that you may reflash TWRP, Magisk etc
I had the same issue. Bootloop and jumb into recovery by itself. You have to flash magisk 15.2 via recovery and will be boot.
redatak said:
I had the same issue. Bootloop and jumb into recovery by itself. You have to flash magisk 15.2 via recovery and will be boot.
Click to expand...
Click to collapse
He says that it occurs even without Magisk... I had a similar trouble once, and the only way to solve it was the procedure I wrote above...
I dont know if you can boot it w/o root
redatak said:
I dont know if you can boot it w/o root
Click to expand...
Click to collapse
Why not? Stock OS is not rooted.
jonsat said:
Why not? Stock OS is not rooted.
Click to expand...
Click to collapse
He said audrax not stock oos
SOLVED! TWRP was the only variable left that I didn't think of. See initial post for solution. thx for help!

Categories

Resources