I tried methods that worked on the A51 and other devices, however, I was not successful in trying to install a GSI, I believe that the only TWRP we have so far is not compatible with super partitions, we will have a new build soon, or there is some other method that works?
Related
This thread is meant to address all the common hurdles that are commonly faced by people who are new to treble devices (chef to be specific) and help them to troubleshoot/avoid some small yet critical steps during flashing new ROMs and working with fastboot and recovery in general. It will be continually updated with new stuff as it goes along.
I will be referring to the Motorola One Power and Moto P30 Note as chef only from now on.
The unlocking guide is available in This XDA Thread!
IMPORTANT:
1. Flashing refers to the process of doing a clean flash, with the inclusion of fastboot -w command
2. Latest ADB and Fastboot drivers are required to be installed, else the installation may halt mid-way.
3. Stock ROM refers to the Android One ROM for the Motorola One Power [XT 1942-2]
IMPORTANT: AS OF RIGHT NOW, PEOPLE WHO HAVE INSTALLED STOCK PIE (EITHER VIA UPDATE OR FIRMWARE) WILL NOT BE ABLE TO USE ANY OTHER ROM OTHER THAN THE STOCK PIE ROM. RADIO INTERFACE LAYER IS BROKEN IN OREO SOURCE BUILT ROMS AND THAT CURRENTLY INCLUDES LINEAGE 16 SO PLEASE WAIT FOR PIE SOURCE CODE FROM MOTOROLA FOR THAT TO BE FIXED.
1. I unlocked my chef . How do I flash TWRP in place of the stock recovery?
Solution:Currently you cannot as there is no recovery partition in the device. You have to manually boot TWRP onto the device using fastboot to use it. Follow as directed:
Boot the device into fastboot mode
Use command fastboot boot <path/to/TWRP.img> to boot TWRP temporarily.
2. I am done with TWRP and I want to flash Lineage OS 16 on my chef. I simply flash the .zip archive right?
Solution:No. Before you flash anything,
Take a backup of atleast your EFS and PERSIST partitions using TWRP and off-load it for safekeeping to restore in future if needed. You can also trigger a full backup if you require.
SUPER IMPORTANT: Flash this .zip file to copy the System A/B partitions. If this step is skipped, you will be responsible to brick your own device. THIS STEP IS ONLY REQUIRED ONCE AND ONLY ONCE IN THE LIFETIME OF YOUR DEVICE! YOU WON'T BE NEEDING THIS THE NEXT TIME YOU FLASH ANY ROM. .
After that, flash your dearest custom ROM and get going.
For Lineage OS 16, follow This XDA Thread.
3. I am done testing LOS 16, I want to flash a GSI. Shall I use a stock Vendor Image for the GSI on my chef?
Solution:No. The stock Vendor image is causing bootloop issue in most GSIs. It is recommended to use Lineage OS Vendor to flash a GSI on chef. So flash LOS and then flash your favourite GSI.
Also, Super Important: for those who haven't used lineage before flahing a GSI, it is required to boot Lineage OS first before flashing a GSI.
4. I am done experimenting, I want to go back to the stock image. How do I proceed?
Solution:Follow this XDA thread for it. And don't install OTA updates directly from the device. It will come in the next step.
5. I want to install OTA updates on the stock ROM. How do I proceed?
Solution:Follow this XDA post for it. The installation process is described here. You have to be clever enough to get the appropriate OTA update.
Credits:
@erfanoabdi : TWRP, LOS 16, AB partition management
@rushiranpise : Unlocking guide
@dayask : Testing the process, guide for reflashing stock ROM
@nageen9211 : Testing ROMs
For any additional queries, feel free to contact us at our Telegram Group
For more regular updates, follow our Telegram Channel
Always remember: You have to be smarter than your smartphone to be able to use it!
Cheers and Happy Flashing!
Note to readers
The above guide is for stock kernels only (including lineage)
The custom Darkone Kernel has constant updates and fixes major bugs often. Please follow the linked thread to test it out if you want to. Cheers!
Anyone have flashed GSI ROM? FOr me after flash GSI HavocOS have bootloop :/
DIdn't flash copy system A/B partitions, stuck on bootloop with custom roms.
Watched some youtube videos and didn't read this post before flashing custom ROM. Flashed Custom ROM without flashing A/B partitions. Now I have a phone stuck on bootloop when done anything in TWRP. or I can use my phone with stock ROM installed by fastboot method.
Installing or restoring anything from TWRP results in boot loop.
Restoring the backup I made before flashing, completes the restoration process normally. But when rebooting to system, TWRP prompts me that no OS is installed. If I reboot anyway, its either stuck on bootloop or reboots to recovery and asks me to try again or factory reset, or boots into bootloader mode.
Installing custom ROM begins with Step 1, takes a bit time and starts step 2 and shows completed. Doesn't echos any comments. But when i reboot, same prompt shows saying no OS installed. Reboot anyway and stuck on bootloop or reboots to recovery and aks me to try again or factory reset, or boots into bootloader mode.
Now I installed stock ROM with fastboot method and phone is boots up into system just fine.
Sometimes TWRP can't mount anything.
So am I stuck with stock rom or is there any solutions?
Also, installing stock ROM with fastboot mode showed this error in between scripts
(bootloader) is-logical:xxx_a: not found
and
(bootloader) is-logical:xxx_b: not found
but is able to use the phone just fine with stock ROM.
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... ((
The issue I have is that I am unable to install any custom rom in the phone, I am only able to correctly install xiaomi.eu roms and also miui global roms using fastboot method. Any custom rom I try, like Pixel Experience, but also many others, the phone will boot loop. Tried android 10 and android 9 roms, also tried to flash roms coming from an older global miui rom, just like one tutorial recomended to do, but still nothing. In TWRP there are no errors, rom seems to install correctly, but when I reboot the phone it will boot loop.
Another weird issue is that only some versions of TWRP will install on my phone, right now I am using Orangefox 10.0.3, version 10.0.4 just won't install, I flash it but nothing happens. TWRP versions from mauronofrio won't install for some unknown reason.
I'm at a loss really as to what is happening.
Xiaomi063 said:
The issue I have is that I am unable to install any custom rom in the phone, I am only able to correctly install xiaomi.eu roms and also miui global roms using fastboot method. Any custom rom I try, like Pixel Experience, but also many others, the phone will boot loop. Tried android 10 and android 9 roms, also tried to flash roms coming from an older global miui rom, just like one tutorial recomended to do, but still nothing. In TWRP there are no errors, rom seems to install correctly, but when I reboot the phone it will boot loop.
Another weird issue is that only some versions of TWRP will install on my phone, right now I am using Orangefox 10.0.3, version 10.0.4 just won't install, I flash it but nothing happens. TWRP versions from mauronofrio won't install for some unknown reason.
I'm at a loss really as to what is happening.
Click to expand...
Click to collapse
1. Try the latest OrangeFox beta - https://forum.xda-developers.com/mi-8/development/official-orangefox-recovery-project-t4039531
2. If you have any issues with it, then report (with logs) in the OrangeFox thread.
I wanted to start this thread to keep up with the information i've gathered working with this.
So far, magisk roms seem to work fine.
Working with other roms built for other OP7P models is not, however, ive had good progress with one. I initially tried havoc (didn't know it but it was Q based) and flashing each partition in fastboot worked, but i had no service. No sim error in fact. I then used a recovery msm tool and went back to OOS. Proximity sensor broke for some reason.
I then tried the same thing but with a Pie based Havoc rom. No dice, twrp wont even boot (twrp would boot on the opposite slot and install to both). Even with installing twrp, it wouldnt load it or the os. Now, im going to continue testing things out here, but if anyone has any more info or wants to try this, that would be awesome.
Update: Tried Aosip, same as Havoc pie. I found I was able to store my OOS Pie installation on slot B, and reboot to it by changing slots with
Code:
fastboot --set-active=other
fastboot format userdata
fastboot reboot
Hi XDAVIANS,
I have the MOTO EDGE 20 - Berlin (XT2143-1). I was trying the new PixelExperience 13+ ROM. However, after flashing the PixelExperience recovery I am getting stuck in a boot loop. It's the same for the Lineage OS recovery for Berlin. The new ones don't work. I tried multiple versions (fresh flash). Ultimately, I am stuck in the bootloop. Finally, I flashed the stock ROM with RSA tool to get back in action. However, in one thread I read some users had the same issue and they were able to solve the issue and flash the recovery with a specific version "lineage-19.1-20221203-recovery-berlin". Can anyone help me with this recovery file. I couldn't find it in any repositories (Seems the older versions were removed).
Thanks in advance. I am bored of A12 and want to switch to A13.
I have a solution since I just did this. LineageOS and Pixel Experience are so similar to the point that the instructions are also the same. Mind you, I have used these exact builds: lineage-20.0-20230211-nightly-berlin-signed.zip, 2023/01/12 release of Pixel Experience 13 Plus Edition. It's simple really: Follow the exact instrucions on LineageOS install guide up until "Installing LineageOS from recovery" where instead of the LineageOS zip file you'll use the Pixel Experience. It will give you two errors on screen about some verification error and system downgrade, just say that you want to continue.
https://wiki.pixelexperience.org/devices/berlin/install, this is the official pixel experience install guide for motorola edge 20 specifically, scroll down to the FLASHING DTBO AND VENDER BOOT PARTITIONS section and follow those steps, and flash the recovery image again. That should solve your issue.
AJ47AJ47 said:
https://wiki.pixelexperience.org/devices/berlin/install, this is the official pixel experience install guide for motorola edge 20 specifically, scroll down to the FLASHING DTBO AND VENDER BOOT PARTITIONS section and follow those steps, and flash the recovery image again. That should solve your issue.
Click to expand...
Click to collapse
Pixel Experience seems to be flashing the system on partition A, while LineageOS is flashing it on B and it's probably why it works. It's just a bug at the moment with Pixel Experience. Make sure you're using Platform Tools instead of Minimal ADB and Fastboot since that one is quite old at this point.
Hi all. Thanks a lot for the valuable suggestions. I solved the issue by flashing the boot.img file after the dtbo and vendor_boot images. That did the trick and I am using Android13 now. Such an amazing experience.
it happended to me aswell.
i was stuck bootloop and the only way to solve that was after i used the dtbo and vendor from lineageOS. For some reason those from Pixel Experience does'nt work