Bootloop after flashing GSI - Redmi Note 8 Pro Questions & Answers

I was flashing PHH's AOSP GSI ROM (version 208, AB, GAPPS included) to my RN8P. This is a supported ROM and should theoretically work. I did this without TWRP and wiped data using ADB. It is important to note that at this point I decided that it probably should have TWRP anyway and flashed that before flashing my ROM using
Code:
fastboot flash system (name of rom).img
I then rebooted to find my phone in a bootloop. I am letting the power drain at the moment but I have no idea what to do when I power it on again.

Related

[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!

Mi Max(hydrogen) bootloop after TWRP flashing

Hi there.
I'm using Global Developer ROM(MIUI9, 8.4.19).
And I'm trying to flash TWRP and install Custom ROM.
I asked Xiaomi for unlock my bootloader, and after 72 hours I could unlock my phone.
After that, I flashed TWRP 3.2.1-4.
Method to flash :
1. Boot into fastboot mode(vol down + power)
2. On windows command prompt, type "fastboot flash recovery twrp.img", "fastboot reboot"
but I can't boot normally, only can boot fastboot & TWRP recovery.
I tried several methods.
1. Try LazyFlasher - bootloop, nothing was changed.
2. Try to flash another ROM(8.1 OmniROM) and gapps(OpenGapps, ARM64 pico) - same bootloop, with Omni bootlogo.
3. Try to flash OmniROM and LazyFlasher - same bootloop.
I can revoke my phone by Fastboot ROM and have no problem without trivial permission reset, but I can't use TWRP still.
Any methods to flash TWRP without bootloop?
flashing twrp doesnt cause bootloop. you went wrong somewhere. did you format system partition before flashing new rom?
yusoffb01 said:
flashing twrp doesnt cause bootloop. you went wrong somewhere. did you format system partition before flashing new rom?
Click to expand...
Click to collapse
Of course.
On the other hand, definitely, just flashing TWRP causes bootloop. I assume that stock beta rom might cause bootloop by incompatibility of TWRP, but I can't return to stock stable rom because I can't use TWRP recovery so I would lose all of my data.
try using stable rom. when i bought this phone2 years ago, i could flash twrp and root miui just fine

Oneplus 5T root problem

Hello all If any one can help me ,
I was rooted running rooted stock oxygen os before on my Oneplus 5T
after flashing Oxygen OS 5.1.4 Full Zip my phone is not rooting it gets in initial oneplus logo and freeze there without loading OS
Phone is working fine after Flashing Oxygen OS 5.1.4 Full Zip without any issue its not booting after flashing either SuperSu or Magisk
Steps which I follow are
1 Flash custom recovery I have tried both Codeworkx TWRP | Blu_Spark
2 after flashing recovery boot in to recovery flash Supersu or magisk
3 reboot
when I reboot if i Flash supersu it stuck on oneplus logo, If i flash magisk it reboot itself to fastboot so Os is not loading at all.
I have to flash full Zip again every time to get it working but then I dont have root access.
I have tried at least 10 times with different even old versions of magisk and supersu with out any success.
Is there any particular recovery or different version of magisk or superuse I need to flash?
your help will be really appreciated.
Try a different approach. Instead of installing recovery, just get phone rooted first. There is a way where you can boot into twrp (without installing it), and then flash magisk/supersu zip. If your phone is rooted, then you can install twrp later (or keep oem recovery)
This is how you boot into twrp (or any recovery): fastboot boot recovery recovery.img
Let me know how it goes.
As you said boot to recovery without installing it.
One problem currently I am installing recovery and flashing root. After that phone is not booting up in to OS it stuck on oneplus logo. Then I have to force off phone boot in to recovery and flash full os zip to get it working. I can boot in to TWRP because my os didn't load. Now if I use your method and flash root file and if phone won't boot to os that means I won't be able to boot in to TWRP again to flash full os zip to get phone working atleast without root. Any idea?
Huh, frankly I have no idea why you are facing this menace. I can just give two suggestions.
1. Try with older, more stable versions of TWRP and Magisk
2. Get yourself a custom ROM, most ROM's will work flawlessly after flashing root files
Hope for the best!
I usually switch from OpenBeta to LOS and back again. Here's how I switch back to OpenBeta (steps should work for official OOS):
1) Back everything on internal storage up. This one's important
2) Boot into official OOS recovery
3) Wipe EVERYTHING (this is why you need to follow Step 1)
4) Sideload the version of OOS you want. The instructions will be right there on the recovery screen
5) Boot into Fastboot and flash TWRP
6) Flash Magisk and (optional) Xposed

Fastboot bootlooping after trying to flash custom ROM

Hey everyone. Tried to flash a custom ROM for the first (and maybe last time) on the Mi5s from China Stable V10.2 to Lineage OS16. I think i did everything correctly at first
Unlocked the bootloader with Mi Unlock, put the SDK tools into ADB folder, flashed TWRP with command prompt, made a backup, wiped data, disabled force encryption, MAGISK root, flashed Mi5s firmware (although I could only find Oreo), LOS16 (Pie), and OpenGApps
I did all of that and got stuck on the LOS boot animation. Then I wiped data + cache partitions and tried again (didn't work). I quit trying with LOS but instead tried to flash the MIUI Global Stable recovery ROM with TWRP, also only made it to the boot animation. I then did a factory wipe on TWRP and tried to restore my backup but now it would only boot to the fastboot (not even trying to load the ROM)....... I can still access TWRP so maybe I'm not so screwed but what do I do? I just want a functioning device and don't mind if I go back to China Stable although advice on trying to flash a custom ROM would be appreciated. Thanks!

Flashing LOS MicroG 17/18 ROM sends to bootloader on boot

I have a google Pixel 2 XL bootloader unlocked via unlock and unlock_critical that I want to use LOS 17.1 with MicroG built in on. It successfully flashes but boots to the bootloader when I boot. I've tried both ROMs I've compiled and the official MicroG builds, same issue. Same issue with 17.x or 18.x versions.
I can successfully flash LOS 18.x official and run it via instructions in that thread (below), which is the same way I am trying to flash LOS w. MicroG.
Anyone know the solution to this ?
Flashing as per below, normally using TWRP 3.3.0.0 also tried latest 3.5.2_9-0. One thing instructions don't mention is whether to swipe to allow changes when you first enter TWRP, I've tried it both with and without that, same results.
Wipe userdata (fastboot format userdata)
Fastboot into TWRP recovery (fastboot boot twrp.img)
Flash the latest build of Lineage OS
Reboot to bootloader and fastboot TWRP again
Reboot to system and don't install the TWRP app
in case it helps others, this was due to the lack of vendor proprietary libs that I thought i was including but wasn't. So apparently that builds flashes but sends you straight to bootloader.
generalnod said:
I have a google Pixel 2 XL bootloader unlocked via unlock and unlock_critical that I want to use LOS 17.1 with MicroG built in on. It successfully flashes but boots to the bootloader when I boot. I've tried both ROMs I've compiled and the official MicroG builds, same issue. Same issue with 17.x or 18.x versions.
I can successfully flash LOS 18.x official and run it via instructions in that thread (below), which is the same way I am trying to flash LOS w. MicroG.
Anyone know the solution to this ?
Flashing as per below, normally using TWRP 3.3.0.0 also tried latest 3.5.2_9-0. One thing instructions don't mention is whether to swipe to allow changes when you first enter TWRP, I've tried it both with and without that, same results.
Wipe userdata (fastboot format userdata)
Fastboot into TWRP recovery (fastboot boot twrp.img)
Flash the latest build of Lineage OS
Reboot to bootloader and fastboot TWRP again
Reboot to system and don't install the TWRP app
Click to expand...
Click to collapse
do you flash disable encrypt,

Categories

Resources