Blank/black screen flickers on and off after flashing GSI - Moto E5 Questions & Answers

Using XT1921-1
Latest TWRP
Have tried LOS 15, LOS 16, AOSP 8.1, AOSP 9.0
Have tried flashing in fastboot and TWRP
Have tried every combo of wipe/factory reset/format data and magisk flash possible
have tried stock recovery, have tried no verity, have tried stock boot.img
nothing works. only able to produce powered on (black and blank) screen that turns on and off for a minute before returning to bootloader
PLEASE HELP
think i might need a 8.0 GSI but cant find one anywhere

Related

TWRP doesn't work + Dm-verity problem

Hi.
I had Freedom OS on my op3t. I gave it to my friend for review and he installed stock 7.0 on my Oneplus 3t.
After he made a review I wiped everything, then I entered into TWRP ( it worked) and try to install my backup. After flashing it I tried to turn on system but there was bootloop (I tried to do it 3 times) and because nth helped, I downloaded new FreedomOS to flash it but now, when I enter to TWRP I see:
DM- verity is not started in enforcing mode and may not work properly,
then is start booting to twrp but TWRP stay on main screen.. I try flash diffirent versions but every time TWRP doesn't work.
Device is unlocked.
Any idea?

Gsi Bootloop not booting

Hi guys.
The problem is gsi is Bootlooping every time in custome vendor stock vendor no matter how much i try to install with different methods by different vendors rom.
Tried formatting many times, changing file system, flashing vbmeta, even flashed on both slots nothing happened same Bootloop.
Even tried flashing no verify decryption zip, magisk.
Don't get it what's the problem its booting but Bootlooping.
If gsi is not supported or corrupt img so it'll not boot right? But booting means it gets installed.
But every time the gsi get stuck at bootanimation
Need help what to do now because it installing successfully everytime but at the end Bootlooping.
Tried ported gsi roms
And official gsi roms
Those are not booting..
Urgent help will be appreciated and I'll be very thankful.
:good:
arya_tech said:
Hi guys.
The problem is gsi is Bootlooping every time in custome vendor stock vendor no matter how much i try to install with different methods by different vendors rom.
Tried formatting many times, changing file system, flashing vbmeta, even flashed on both slots nothing happened same Bootloop.
Even tried flashing no verify decryption zip, magisk.
Don't get it what's the problem its booting but Bootlooping.
If gsi is not supported or corrupt img so it'll not boot right? But booting means it gets installed.
But every time the gsi get stuck at bootanimation
Need help what to do now because it installing successfully everytime but at the end Bootlooping.
Tried ported gsi roms
And official gsi roms
Those are not booting..
Urgent help will be appreciated and I'll be very thankful.
:good:
Click to expand...
Click to collapse
You should try generic gsi from this site https://mirrors.lolinet.com/firmware/gsi/
Choose generic AB.. currently latest one is from 11th July @ Developer Preview 5.
Download Havoc os, flash it on slot A.
Reboot to slot B, wipe everything and reboot to recovery again.
Then flash gsi file, permissiver v4, darkness kernel, magisk canary, and disable force encryption.
Wait for it to boot up. ?
How to reboot to slot B and flash to slot A? Zip files are flashing like custom roms, GSI images are for slot A, slot B and AB. Sorry but I'm noob in flashing GSI roms. I never succeeded with that... ((

[James] Moto E5 Play won't boot into Custom ROM(s)

Device variant: XT19121-2 James
Chipset: MSM8920
After repeated failed flashes I am on stock firmware using this guide. Phone boots and works normally right now, but I can't seem to flash any Custom ROMs on to my phone. I was using this post to flash Lineage OS 15.1, which worked successfully at first, but the WiFi wasn't working so I reflashed it. It still didn't work so I did it again, wiping Dalvik/Cache too. After the second flash attempt, my phone began to only flicker on and off. I made sure to always clean flash, factory resetting, wiping Cache and Dalvik, even formatting data, but no matter what I do it doesn't work. Also attempted other GSI images (arm, A-only) like AOSP, ResurrectionRemix and phhusson's Lineage OS 15.1 But they all failed too. I am using TWRP for James v 3.3.1 although I did also try other TWRP images like v 3.2.1 . But it makes no difference. Also used Magisk v19 like some guides suggested but whether I have Magisk or not, it doesn't work. Even made sure to push the fstab.qcom file to /vendor. Anytime a Custom ROM is flashed whether zip or GSI img it goes past the initial "bad key" or "N/A" screen and starts flickering on and off. Bootloader and TWRP works fine, but that's about it. Everytime a flash fails I go back to stock firmware (which always works) and try another ROM. I wonder why the first attempt worked but doesn't anymore even if I mirror the exact steps I took from stock. If anyone has any solutions I would be really grateful. Let me know if you need any more information.
have you taken any recent OTA updates?
mikeshutte said:
have you taken any recent OTA updates?
Click to expand...
Click to collapse
Nope. Still on the 8.0.0 version the stock firmware comes in.
tkhan7916 said:
Nope. Still on the 8.0.0 version the stock firmware comes in.
Click to expand...
Click to collapse
Okay give this a try, I'm assuming you have old root access and TWRP installed.
Download any Android 9 GSI of your liking, boot to TWRP.
Do a complete nandroid backup of the stock firmware.
Do a factory reset then wipe system partition.
Next flash your GSI that you downloaded to your system partition.
After flashing is complete of the GSI reboot to recovery.
After reboot completed flash your open Gapps zip. Then reflash Magisk.
if you get a error message when flashing g apps then you will need to use magic g apps with magisk as it will install them systemless. I have to do this on my device because the partition doesn't have enough space.
Give that a try and let me know how it goes if you have any questions feel free to ask.
---------- Post added at 10:09 PM ---------- Previous post was at 09:59 PM ----------
tkhan7916 said:
Nope. Still on the 8.0.0 version the stock firmware comes in.
Click to expand...
Click to collapse
mikeshutte said:
Okay give this a try, I'm assuming you have old root access and TWRP installed.
Download any Android 9 GSI of your liking, boot to TWRP.
Do a complete nandroid backup of the stock firmware.
Do a factory reset then wipe system partition.
Next flash your GSI that you downloaded to your system partition.
After flashing is complete of the GSI reboot to recovery.
After reboot completed flash your open Gapps zip. Then reflash Magisk.
if you get a error message when flashing g apps then you will need to use magic g apps with magisk as it will install them systemless. I have to do this on my device because the partition doesn't have enough space.
Give that a try and let me know how it goes if you have any questions feel free to ask.
Click to expand...
Click to collapse
I also just noticed you are using the latest version of TWRP 3.3.1. I'm not sure if you originally rooted and installed TWRP with the original patched version by Cody or not, but if so make sure with the new version that you format your data partition to f2fs. As this will ensure correct mounting of the data partition.
mikeshutte said:
Okay give this a try, I'm assuming you have old root access and TWRP installed.
Download any Android 9 GSI of your liking, boot to TWRP.
Do a complete nandroid backup of the stock firmware.
Do a factory reset then wipe system partition.
Next flash your GSI that you downloaded to your system partition.
After flashing is complete of the GSI reboot to recovery.
After reboot completed flash your open Gapps zip. Then reflash Magisk.
if you get a error message when flashing g apps then you will need to use magic g apps with magisk as it will install them systemless. I have to do this on my device because the partition doesn't have enough space.
Give that a try and let me know how it goes if you have any questions feel free to ask.
Click to expand...
Click to collapse
Followed these steps exactly, including formatting the data partition to f2fs, and the same problem still persists. Screen just keeps turning on and off in a loop without booting into the ROM. I downloaded the Lineage OS 16.0 GSI A-only Arm version for reference.
I am having the same issue
Using XT1921-1
Latest TWRP
Have tried LOS 15, LOS 16, AOSP 8.1, AOSP 9.0
Have tried flashing in fastboot and TWRP
Have tried every combo of wipe/factory reset/format data and magisk flash possible
have tried stock recovery, have tried no verity, have tried stock boot.img
nothing works. only able to produce powered on (black and blank) screen that turns on and off for a minute before returning to bootloader
PLEASE HELP
think i might need a 8.0 GSI but cant find one anywhere
I eventually got RR to boot on the james xt-1921-3 I installed XT1921-3_JAMES_T_MPCS_8.0.0_OCPS27.91-150-5-1-3_cid21 as a base, then used boot and vendor partitions from JAMES_T_OCP27.91-51-4_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC and it finally worked.
tkhan7916 said:
Followed these steps exactly, including formatting the data partition to f2fs, and the same problem still persists. Screen just keeps turning on and off in a loop without booting into the ROM. I downloaded the Lineage OS 16.0 GSI A-only Arm version for reference.
Click to expand...
Click to collapse
Message me, I'll host a TWRP backup for the XT-1921-3 that boots RR 6.1
Download the file from this post https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 , then using fastboot, flash the vendor and boot img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
then boot into recovery and flash the file from that post to disable dm-verity and force encrytion, after that flash magisk, then reboot to bootloader, at command prompt-
fastboot erase userdata
fastboot erase cache
fastboot reboot
that should get you booted - profit
mrbox23 said:
Message me, I'll host a TWRP backup for the XT-1921-3 that boots RR 6.1
Click to expand...
Click to collapse
Do you still have that back up by any chance and could ypu send it to me?

Is my phone bricked?

Yesterday, I managed to unlock my bootloader using PotatoNV and tried to install ProtonAOSP GSI:
Code:
fastboot erase system
fastboot flash system <gsi>.img
Note that I'm on EMUI 9.1.0.252 (C636E2R1P9) and my phone model is VTR-L29. Didn't try to root it or replace the recovery with TWRP. Anywho, I went to the recovery as soon as I flashed the GSI to factory reset it. Little did I know, I booted to eRecovery and factory reset it there. I thought it was "just okay" and proceeded to boot into the "real" recovery. I factory reset it once again and try booting my device into the GSI. I waited for it to boot and panicked once it starts bootlooping. I tried flashing different GSIs from phhuson and ponces (Pie, 10, 11 and 12) with the same commands and steps I used earlier. STILL BOOTLOOPING!
Any fixes? Cheers!
Nope sir
Btw I'm using Phh 412 GSi AOSP
I didn't face any bootloop
I just fastboot erase then flash system
After that I just factory reset on erecovery
I didn't face bootloop
Btw I'm on Emui 9.0

Galaxy M21 (SM-M215G) Latest Stock Factory Firmware CWD1 Refuses to flash non-OneUI5.1 GSI ROMs. Pls help if anyone knows solutuion.

1> The Shamshung recent firmware upgrade CWD1 might have some patches that makes rooting problemtic. I flashed TukiROM1.2 with Magisk 26.1 (boot.img patch method) the first time and it worked but as soon as I connected to wifi somehow it upgraded to Magisk Delta (thats how I came to know about the existence of Magisk Delta). Both Magisk 24.3 & 26.1 are not surviving reboots even after flashing (Magisk.OTA.persistence-v1.zip). So staying rooted on a stock factory rom is still an issue. I will try TukiRom1.3 though I request OP to compress the ROM file from 2.7GB to lesser if possible.
2> GSI RAW image files don't go past the bootlogo screen. I tried system image files Elixir, LPOS, Crdroid, EvolutionX, Derpfest etc., none of them booted no matter what dmverity or multidisaabler etc. I flashed before or after. The same raw images used to boot on the same device when it was Andoid 11 but now on Andoid 13 Stock Factory ROM CWD1 GSI images dont boot.
3> Since Magisk is either bootlooping the device after reboot/ After flashing Magisk/or Magisk patched images not surviving reboots, so when I flash the Stock boot image it goes straight to download mode with Vbmeta signed using public key etc errors, or if I flash Magisk patched boot image from TWRP it stuck on Shamshung logo.
4> I have tried some of Dev Roynas ROMs [https://sourceforge.net/projects/a51-builds-by-royna/files/] but they all end up with [TWRP error : 1 Assert failed : update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")] also same error through Sideload.
5> I tried (systemrw_1.32_flashable) by Dev Lebigmac but since the altercation between XDA & Lebigmac on March 2023 he got banned from XDA, I cant get hold of (systemrw_1.4_flashable) to try to check if CWD1 Update is RO-Rom and anything other than 1UI5.1 based wont flash etc.
If anyone has any solutions for CWD1 Factory Stock Rom pls assist. TIA

Categories

Resources