getting bootloop on every gsi I flashed
steps followed-
1.Install Pixel Experience(For Vendor and Kernel) also tried with letest china beta
2.Wipe system,data
2.Flash System.img
3.flash permissiver for system as root
also tried other vendors such as superior,China beta letest etc.
also device is unencrypted
what I am doing wrong ?
I tried Android Q gsi with evolution x vendor and got a bootloop. Tried it with Pixel experience Caf vendor luckily it booted but the problem it had was this weirdly low brightness which couldn't be increased, so it was useless.. I don't know what's the problem.. please help!!
Related
Hey.
I tried today with flashing a custom ROM for my Pixel 2 after being on stock "for too long" and my ROM of choice Unofficial LineageOS 15.1 booted up without any problem.
Here is my issue at the moment that is driving me crazy..
Every time I am trying with flashing a custom kernel on a custom ROM for my Pixel 2, my phone is getting stuck at the bootloader screen and refuses to boot back into the system/ROM no matter what I am doing. I can see that LineageOS is/was flashed to the B Slot and I am thinking, shouldn't latest ElementalX for 8.1 based ROMS be flashed to the same slot that is set in TWRP?
Is it any solution out there so I can get my phone to fully boot on a custom ROM with a custom kernel flashed, and not screwing around with changing between slot A and B for making thing(s) work as intended? Or is this a total dead end?
This whole Dual Slot thing is confusing..
xFirefly93 said:
Hey.
I tried today with flashing a custom ROM for my Pixel 2 after being on stock "for too long" and my ROM of choice Unofficial LineageOS 15.1 booted up without any problem.
Here is my issue at the moment that is driving me crazy..
Every time I am trying with flashing a custom kernel on a custom ROM for my Pixel 2, my phone is getting stuck at the bootloader screen and refuses to boot back into the system/ROM no matter what I am doing. I can see that LineageOS is/was flashed to the B Slot and I am thinking, shouldn't latest ElementalX for 8.1 based ROMS be flashed to the same slot that is set in TWRP?
Is it any solution out there so I can get my phone to fully boot on a custom ROM with a custom kernel flashed, and not screwing around with changing between slot A and B for making thing(s) work as intended? Or is this a total dead end?
This whole Dual Slot thing is confusing..
Click to expand...
Click to collapse
Don't let the dual slot confuse you, our phones/TWRP typically do a good job selecting the slots for you.
Common procedure to install custom ROMs/Kernels is to do the following:
•Boot into TWRP
•Wipe Dalvik Cache & Data partitions only
•Flash ROM
•Flash Kernel
•Flash TWRP walleye installer zip
•Reboot to first boot (if this doesn't boot, reinstall ROM, reinstall Kernel, as it is trying to boot off another slot)
•Reboot back to TWRP
•Flash TWRP walleye installer zip
•Flash Magisk 16.x (if you want root)
•Reboot - profit!
This is what I have to do every time I flash a new ROM, if it boots back to bootloader, boot to TWRP, reinstall ROM/Kernel/Root. Reboot. Enjoy
djer34 said:
Don't let the dual slot confuse you, our phones/TWRP typically do a good job selecting the slots for you.
Common procedure to install custom ROMs/Kernels is to do the following:
•Boot into TWRP
•Wipe Dalvik Cache & Data partitions only
•Flash ROM
•Flash Kernel
•Flash TWRP walleye installer zip
•Reboot to first boot (if this doesn't boot, reinstall ROM, reinstall Kernel, as it is trying to boot off another slot)
•Reboot back to TWRP
•Flash TWRP walleye installer zip
•Flash Magisk 16.x (if you want root)
•Reboot - profit!
This is what I have to do every time I flash a new ROM, if it boots back to bootloader, boot to TWRP, reinstall ROM/Kernel/Root. Reboot. Enjoy
Click to expand...
Click to collapse
Thanks a lot! Will screenshot and save this for future references & needs!
I has a pretty big problem of that Crash Dump screen some hours ago and i still can't get to fix it. Here is the story, after trying Havoc 2.0 rom i decided to go back to stock so in TWRP i erased the system, cache (dalvik cache and cache), data and internal storage (i wiped internal storage because TWRP just couldn't decrypt it even though the passwd was correct), after that i flashed the stock OOS rom and the TWRP installer (all these being booted on twrp), but when i rebooted into recovery the twrp splash screen just froze there, so i tried to boot twrp through fastboot, but then the crash dump screen apeared, this post: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892 said this was a way to recover from that problem so i tried it, it worked as far as booting into OOS is concerned, but when i try to boot into twrp through fastboot the crash dump screen keeps showing up.
Any ideas?
mateuxi said:
I has a pretty big problem of that Crash Dump screen some hours ago and i still can't get to fix it. Here is the story, after trying Havoc 2.0 rom i decided to go back to stock so in TWRP i erased the system, cache (dalvik cache and cache), data and internal storage (i wiped internal storage because TWRP just couldn't decrypt it even though the passwd was correct), after that i flashed the stock OOS rom and the TWRP installer (all these being booted on twrp), but when i rebooted into recovery the twrp splash screen just froze there, so i tried to boot twrp through fastboot, but then the crash dump screen apeared, this post: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892 said this was a way to recover from that problem so i tried it, it worked as far as booting into OOS is concerned, but when i try to boot into twrp through fastboot the crash dump screen keeps showing up.
Any ideas?
Click to expand...
Click to collapse
Use bluespark twrp not official
ON rom 8.1 best is official twrp
on rom 9.0 best is blues park twrp
yldlj said:
Use bluespark twrp not official
Click to expand...
Click to collapse
akswap said:
ON rom 8.1 best is official twrp
on rom 9.0 best is blues park twrp
Click to expand...
Click to collapse
It worked!
Now i'm installing all my mods again.
Thanks!
UPDATE:
Nevermind, it boots into twrp, but it wont boot OOS, i already tried erasing all the partitions (system, data and cache) and installing OOS and bluspark TWRP.
It turns on, shows the bootloader unlocked screen and then it reboots back to twrp.
UPDATE 2:
Fixed it by erasing all data on oneplus recovery, thanks again, my phone is back from the death (a quite unrooted one).
Fixed it by erasing all data on oneplus recovery, thanks again, my phone is back from the death (a quite unrooted one).
Click to expand...
Click to collapse
When u upgrade from os 8.1 to 9 .0 after flash install blues spark twrp.
When Downgrade 9.0 to 8.1 use official OnePlus6Oxygen_22_OTA_007_all_1805131952_O_MR1.zip
& flash official Twrp & Stable magisk only
for 8.1
1- must have a copy of Oxigen Fastboot ROM 8.1
2- Oxigen 8.1 rom ( Revovery) .zip
3- twrp-installer-enchilada-3.2.3-0zip & img file
for 9.0
4- twrp-3.2.3-x_blu_spark_v9.86_op6.zip & img file
5- magisk 16.7 beta & 17.1 Stable
6- official 9.0 Stable rom
7- tool all in One (PC)
Enjoy flashing
I was on crDroid, and other aosp ROMs for a month, but yesterday I wanted to test MIUI 12, so I flashed CN Closed Beta miui 12, I installed miui_PHOENIX_20.5.28_ef1f0d470e_10.0! It doesn't include Gapps so I decided to install xiaomi.eu build. It stuck on Bootanimation. I couldn't go back to TWRP and install something else cause TWRP won't show any storage or data partition ( It's happening now again and again after I install any AOSP or MIUI ROM) To recover from bootloop I downloaded fastboot image (phoenix_images_V11.0.15.0.QGHCNXM) to flash with XiaomiFlash Tool. Successfully unbricking the device, I try to install EU build again but it won't just boot. And also I can't use twrp data partition again cause it somehow breaks all the partitions. I have to reflash fastboot image. I even tried to go back on Indian Build of POCO X2 but due to anti-rollback check it fails again and again. I can't boot any AOSP rom, tried a few, nor even EU builds or Indian Builds. I can only Install MIUI 12 Closed Beta or MIUI 11 stable both Chinese roms. What Went wrong and how to install AOSP roms again or flash EU builds?
Jyotirmay Goldsmith said:
I was on crDroid, and other aosp ROMs for a month, but yesterday I wanted to test MIUI 12, so I flashed CN Closed Beta miui 12, I installed miui_PHOENIX_20.5.28_ef1f0d470e_10.0! It doesn't include Gapps so I decided to install xiaomi.eu build. It stuck on Bootanimation. I couldn't go back to TWRP and install something else cause TWRP won't show any storage or data partition ( It's happening now again and again after I install any AOSP or MIUI ROM) To recover from bootloop I downloaded fastboot image (phoenix_images_V11.0.15.0.QGHCNXM) to flash with XiaomiFlash Tool. Successfully unbricking the device, I try to install EU build again but it won't just boot. And also I can't use twrp data partition again cause it somehow breaks all the partitions. I have to reflash fastboot image. I even tried to go back on Indian Build of POCO X2 but due to anti-rollback check it fails again and again. I can't boot any AOSP rom, tried a few, nor even EU builds or Indian Builds. I can only Install MIUI 12 Closed Beta or MIUI 11 stable both Chinese roms. What Went wrong and how to install AOSP roms again or flash EU builds?
Click to expand...
Click to collapse
After you install xiaomi.eu rom, if you are stuck at boot logo, try this
1. flash twrp again with fastboot mode and boot into twrp
2. format data partition ( you lose all data)
3. now flash xiaomi.eu rom again and reboot
AdrenalineX said:
After you install xiaomi.eu rom, if you are stuck at boot logo, try this
1. flash twrp again with fastboot mode and boot into twrp
2. format data partition ( you lose all data)
3. now flash xiaomi.eu rom again and reboot
Click to expand...
Click to collapse
When I flash any rom now, it stucks to bootloop and I can't format or flash anything on top of that, I have to flash fastboot images of Chinese Rom 11.0.15 through xiaomiflashtool, all rooms are stuck to bootanimation except miui12 CN ROM.
AdrenalineX said:
After you install xiaomi.eu rom, if you are stuck at boot logo, try this
1. flash twrp again with fastboot mode and boot into twrp
2. format data partition ( you lose all data)
3. now flash xiaomi.eu rom again and reboot
Click to expand...
Click to collapse
Remove the first few lines from the flash all.bat which does not begin with'fastboot' to overcome ARB.
i am facing the same problem after i tried to update 12.6 to 12.7 of bliss rom, found any fix?
SOLVED
checkout this thread https://forum.xda-developers.com/poco-x2/help/11-0-15-0-to-poco-x2-11-0-7-0-t4095185
(Story Telling) FIX BOOTLOOP "JUST A SEC" REDMI 5 ROSY MIUI 11 AND NO INSTALLED OS
Code:
* I am not responsible for bricked devices, dead SD cards, etc
* you point the finger at me for messing up your device, I will laugh at you.
Hi There, before we going how to fix bootloop at just sec on MIUI 11 there is story of my phone
i've flashing much of custom ROM Android 10 (Pixel Experience, AOSP Extended, Havoc, AICP, Paranoid Android etc). when i installed new ROM i always full wipe include data, system, dalvik, vendor, substratum (not sd card and OTG) i'am using Batik Recovery btw (custom TWRP). Someday i want to install Pixel Experience Plus PixelExperience_Plus_rosy-10.0-20201012-0737-OFFICIAL.zip But TWRP always say No OS Installed, But Paranoid Android is fine, then the other day i want to go back use MIUI 11, so i flash it (flash all) using MIUIflash with FASTBOOT ROM. But always get bootloop at Just a sec, i try to install use zip Rom trough TWRP get same problem bootloop at Just a sec, then i'am trying to find how to fix it But unavailable at anywhere so i just try this ( i don't know wich one is fix it but it works).
i'am not give a tutorial but i tell what i do
First i use all these file at my SD Card and 100% of Batery and use Batik Recovery BR-rosy-S-1.5.0-20190622-0421-OFFICIAL.zip
1. MIUI 11 Zip file ROM miui_HM5Global_V11.0.2.0.ODAMIXM_25c20fae94_8.1.zip
2. Pixel Experience 10.0 PixelExperience_Plus_rosy-10.0-20201012-0737-OFFICIAL.zip
3. Retro Custom Kernel Retro-Kernel-FinalAF.zip
4. xDoge Custom Kernel xDoge-rosyKernel-r34.zip
5. Batik Recovery BR-rosy-S-1.5.0-20190622-0421-OFFICIAL.zip
6. Lazy Flasher lazyflasher-no-verity-opt-encrypt
7. MIUI_Region_Fix_Indonesia.zip
i though my phone has wrong kernel or firmware, so this is what i do.
flash all of these file using Batik Recovery (maybe all custom recovery is same)
1. Retro Custom Kernel Retro-Kernel-FinalAF.zip
2. PixelExperience_Plus_rosy-10.0-20201012-0737-OFFICIAL.zip
3. Wipe Everything
4. ROM miui_HM5Global_V11.0.2.0.ODAMIXM_25c20fae94_8.1.zip
Then MIUI 11 is work...
But there is stuck location at Tiongkok and one step last
flash MIUI_Region_Fix_Indonesia.zip (mine is Indonesia, You is just find Region_fix file of your country)
thankyou and sorry for my bad english
I think it's possible that you accidentally erased the persist partition (containing DRM related files, sensor registry, your wifi, bluetooth, mac address) when you flashed some ROM.
Maybe you can extract persist.img from the official ROM and flash the persist partition in recovery.
MIUI V11.0.2.0.ODAMIXM Stable Official Update for Redmi 5 Global (rosy)
Hello there,
I have some sort of a problem (although my phone is still working.. yet)
I recently flashed my OnePlus 6 with LineageOS 19.1 (coming from OxygenOS 11.1.2.2).
I flashed "copy_partitions.zip" first and then the official LineageOS 19.1 ROM without GApps,
but because I wanted to use some features, which needed at least the presence of Google Services, I flashed the "LineageOS for microG" (19.1) ROM.
Which worked like a charm.. besides I was very unhappy because of the lack of customization regarding color-theming and the changes made to the QuickSettings of Android 12 in general..
So I thought I could clean flash LineageOS 18.1 / ("Lineage for microG") to get the old theming back..
So what I did was installing the official custom LineageOS recovery from 18.1 (because microG had none for 18.1),
hit "Factory Reset" and afterwards applied the Lineage 18.1 zip over adb.
A message "Update package is older than the current build, expected a build newer than timestamp [...] but package has timestamp [...] and downgrade not allowed" along with the Question to install anyway appeared right after sideloading it to the phone.
I decided to hit "Yes" because I don't needed to backup any data from the phone and wanted to wipe clean anyways... (which I thought I did with "Factory Reset)
So I installed and afterwards rebooted to recovery to flash Magisk aswell..
After rebooting to system then, the phone entered the fastboot loop.
No matter what I do, it still doesn't boot to system after installing 18.1 from LineageOS recovery (also tried with the newest microG recovery from 19.1).
I also known you would wipe system, cache and data (and maybe vendor aswell) prior to a clean custom ROM flash (via TWRP)..
So flashed TWRP 3.6.2 (latest) for enchilada and tried to wipe my system, vendor and cache, but didn't manage to find "system" or "cache" on the advanced wipe menu, so I formatted and wiped data and wiped vendor.
Then installed LOS 18.1 via TWRP also..
But same problem - fastboot only.
also after my TWRP journey, sometimes when flashing the LOS recovery and booting it, a message appears on screen:
Failed to bind mount /mnt/staging/emulated/media/0 [...]
The thing is, I can install LOS 19.1 (microG) without any problems and it would boot,
but I just want to downgrade and I found no guide for my device (or any with ramdisk and A/B slots)..
And there is also no link to MSMDownloadTools for Android 10 (because onepluscommunityserver.com is offline)..
The links from this post and some other posts I found aren't working anymore..
- Is there a way to go back to LineageOS 18.1? What would be the intended way (not doing a downgrade but flashing clean)?
- Is my phone softbricked somehow? (partitions broken or corrupt?)
- Is it a firmware problem?
(I am on security patch from November 2021)
But I don't know what exactly happened to my firmware when flashing Lineage 19.1 over OOS 11.1.2.2
This is my first post as it is my first Android phone/flashing experience in general.. so I hope I got everything right from all I found out until now..
I really appreciate any help / even if it is just saying I messed up and need to go EDL mode... (if it truly is the case)
Thanks in advance.
You people are great!
o/