Hi everyone,
I'm writing this blog post to ask for some help from the XDA community. I have a Samsung A22 SM-A225F and I want to install a custom ROM on it, preferably an Android 12 GSI. However, I'm having some trouble getting it to boot properly.
I'm following the directions on this blog post which claims to have successfully installed Android 12 GSI on the same device. The steps I'm following are as follows:
Use Odin tool to flash the stock verified ROMs on my phone to start from zero.
Flash the (magisk patched.tar) file on AP
Boot to Android and set it up then install Magisk app to check for root (I'm doing this because it doesn't work otherwise)
Flash TWRP and run multidisabler then boot again to check if everything is working.
Finally flash the system.img, I'm not sure about vbmeta so I'm skipping it.
But I keep getting a bootloop no matter what I try, I've tried wiping cache and everything.
Weirdly enough I have flashed stock Android like two days ago except that it actually booted to set up but it didn't detect the network and kept mini rebooting from time to time.
I've tried the steps in that blog for Android 11 to flash crDroid but that also didn't work, I've also tried flashing crDroid even when following the steps for Android 12. Still no success.
I'm wondering if anyone has any idea what I'm doing wrong or what I can do to fix this issue. I've read some other guides on how to install custom ROMs and GSIs on Samsung devices without TWRP but they seem too complicated for me.
If anyone can help me out or point me in the right direction, I would really appreciate it. Thanks in advance! and i'll gladly provide any information required when i have time as it's currenlty night time
what twrp u using also where u flashing it using fastboot or from TWRP ?
i recommend u using fastboot to flash GSI
Related
Hi there
I'm hoping someone can help me out with a few questions as it's been a while since I've played around with a samsung device. I have a rooted s4 mini (i9195) (I rooted it a long while ago), on Android 4.4.2. I want to do a clean flash. Do I need to do an odin flash of anything before flashing to Resurrection Remix? (As this rom is Android 7, and last I remember, when upgrading android versions there's a few extra steps?)
Speaking of Odin, will the standard Samsung USB drivers be fine for using odin?
Also I noted it said in the install instructions for Resurrection Remix to flash TWRP from this thread but it says in that thread please do not use Nougat roms with TWRP at the moment? Surely I shouldn't be flashing that TWRP if it literally says dont flash it to use with Nougat roms?
Thanks
Hi there. I made exactly your same steps time ago (from stock KitKat 4.4.2 to CM13), so it's simple: you just have to prepare 1) TWRP; 2) The ROM you'd like to flash. 3) Odin for flashing TWRP. Old Samsung drivers are more than good, this is all you'll need.
1 - go here and download the 3.1.1-0 TWRP for LTE (don't worry, it works flawlessly even if said that it doesn't on Nougat, this because OP should be updated by the developer but it'll be done when he'll have some free time, i used it for everything and i ensure its efficient).
2 - extract from the zip file the twrp.img file, then flash the twrp.img by Odin; open Odin, click on recovery on low-left corner and browse to the img file, then flash it.
3 - reboot to TWRP, do a stock rom backup and backup even all your data that you'd like to keep, TWRP backups keeps everything except the various documents, MP3s, images, ecc. and if someone should go wrong while flashing a custom rom, let's have a way to restore the actual situation. Then to have a clean flash, be sure to wipe data by TWRP menu (the 3 selected partitions are enough, don't wipe nothing else).
4 - to install a custom rom, now that you're ready to start, follow instructions that you'll find in rom's thread in OP
Happy flashing!
Hello Forum users!
Since I have lots of time right now i wanted to do some fun stuff with my Z2 Play XT17170-09, which was my previous daily driver. So i installed the custom twrp i found on xda (here), rooted it with the magisk zip (idk what the version was) and everything was fine. Until I discovered Motorola put a 32 bit ROM on there, that is. So i wanted to flash a custom ROM (also from xda) but without success. The Phone got stuck in a bootloop. I thought: no problem, I have a full backup. TWRP wasn't accessible anymore. I somehow managed to get into TWRP and restored my BU, but it didn't boot anymore (not my main problem but if you you have an idea why, please also tell me). I found the Stock ROM for my exact model and software channel (reteu) and flashed it with mfastboot, as shown here. I finally got it to work, with ID: bad key, even though I had id: N/A before this whole mess, but ok im fine with that. But now the ROM overwrites my TWRP with the stock recovery and if I try to root it with Magisk zip it gets stuck on the device unlocked, cannot be trusted (...) screen and it won't boot anymore. I can reflash the whole stock firmware as above with everything working, but I still don't have a rooted phone then. Does anyone (please?) have an idea on why this happens? I appreciate every answer, I am trying for 3 whole days already. My guess is that the boot partition gets corrupted somehow during flashing, but please correct me if that's wrong.
Thanks in advance
There's a guide somewhere here, but in short:
to get Magisk working, you must either:
A) backup and restore system and data before flashing Magisk
B) go in TWRP to advanced and in command prompt write:
echo KEEPVERITY=1>>/data/.magisk
echo KEEPFORCEENCRYPT=1>>/data/.magisk
either before or after flashing magisk, don't remember. Rather both.
If you want to play with custom ROMs, you can try GSIs. Guide: https://forum.xda-developers.com/z2-play/how-to/updated-guide-project-treble-gsi-t4063193
Klen2 said:
There's a guide somewhere here, but in short:
to get Magisk working, you must either:
A) backup and restore system and data before flashing Magisk
B) go in TWRP to advanced and in command prompt write:
echo KEEPVERITY=1>>/data/.magisk
echo KEEPFORCEENCRYPT=1>>/data/.magisk
either before or after flashing magisk, don't remember. Rather both.
If you want to play with custom ROMs, you can try GSIs. Guide: https://forum.xda-developers.com/z2-play/how-to/updated-guide-project-treble-gsi-t4063193
Click to expand...
Click to collapse
I tried, but the error remains the same. I simply installed a custom ROM and rooted it, even though i wanted to keep it on stock firmware. Anyway, thank you very much for your answer!
This problem is common in Stock Oreo
You messed up, and badly.
The first thing you need to do before installing a 64-bit ROM is install a 64-bit recovery.
But in your case this isn't possible if you don't fix your issue first, as Oreo has extra steps to make Magisk work, these extra steps can be entirely skipped (because they are no longer needed) if you flash Stock Pie instead.
The easiest way to flash TWRP your phone without the stock recovery fcking up with it, is through Stock Pie.
Since you have unlocked bootloader, you only need to get the Stock Pie ROM and flash it through adb fastboot.
Note: partition (gpt.bin) can only be upgraded. If you upgrade gpt.bin from Oreo to Pie, you won't be able to downgrade it as the security downgrade will prevent it. So in the case it gives you an error avoid flashing this file.
If you decide to flash Stock Pie, also skip the modem file (modem-HLOS.bin), you want to avoid that modem file from Android 9 because it has audio issues during calls when installing ANY custom ROM.
Instead, preserve the modem file from Stock Oreo as this one doesn't have any issues with custom ROMs.
Also make sure you issue the oem mode commands, there is one guide that doesn't have these, if you skip them, the USB (and MTP) connection on PC won't work at all.
fastboot getvar max-sparse-size (1st command)
fastboot oem fb_mode_set (2nd command)
fastboot oem fb_mode_clear (last command after you flash the last file, just before issuing reboot)
---------- Post added at 10:40 PM ---------- Previous post was at 10:36 PM ----------
I have also read you need to flash Magisk 19.3 or older, then you can update Magisk through itself (the Magisk App)
If you try to flash Magisk 20 or newer it could cause bootloops in very specific cases.
Here is a solution with Magisk Manager 7.5.1 and Magisk 20.4
Before patching, make sure both encryption and verity are checked
Patch the boot.img and flash it in bootloader
Done
After some time of sitting on ColorOS 6.1 I decided it was time to move to a Custom Rom.
I watched some tutorials and managed to unlock my bootloader and flash twrp recovery version 3.4.
Following the steps from the Evolution X guide I wiped cache/system/vendor/data/internal storage. Then copied over the rom via the "mount" option, after successfully copying the rom I went to install and flashed the rom with no issues. However, once I go to reboot I boot strait into fastboot mode (which keeps restarting until I select 'restart bootloader').
I have tried other Roms such as Covus and the pixel experience rom that was posted here and have the same issue.
Finally I tried 'fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img' with vbmeta provided in root tutorial...still nothing
As it stands I can still boot into twrp without issue so I wouldn't call the device bricked just a victim of (likely) user error.
Oh and I also tried different versions of twrp...3.3-19 and that also did not work.
Is it possible that trying to flash to an android 10 rom from android 9 is the issue?
Please let me know if you guys or girls have any ideas because I can't think of anything else
Finally thank you in advance all those who respond!
Edit: So uhhh yeah y'all make sure you update to android 10 before trying to flash an android 10 rom lol
update: I followed this guide if anyone has issues and booted successfully after a couple attempts into RealmeUI
https://forum.xda-developers.com/realme-x2/help/how-to-flash-q-firmware-based-roms-t4115987
Hey everyone! I'm sort of new to the whole custom recovery thing and while I know that there is a whole post concerning TWRP and Pixel 2XL, I would love if someone could take the time to explain, and maybe help me get it working on my phone.
BTW the reason I want to get a custom recovery is so I can flash a custom rom as Pixel OS just isn't cutting it for me anymore.
Here's what I know:
I am currently on an unlocked phone that is rooted on android 10. I heard that android 10 totally screwed up TWRP and makes it impossible to install after updating. Is that true? If so, is it possible for me to factory reset my phone to android 9 and then install TWRP after the fact? Or, have I totally screwed myself by updating to android 10? I know that I could just ask these questions on the other thread but it confuses me a lot and it would help if I could just get some clear answers.
TWRP works fine on Android 10. I would update to the latest update of Android(which is the August update for right now). Then copy any files( TWRP.zip and what ever Rom.zip) to your phone. Boot into bootloader and run the fastboot commands to boot into TWRP. Wipe data on your phone within TWRP and then proceed to flash the rim followed by TWRP.
Make sure you add the installer zip to the flashing queue when flashing a ROM or you'll get stock recovery again.
Hi, I got myself an used Motorola Moto G7 play (XT1952-1) with Android 10 Stock update (Build QPYS30.52-22-8-9) and just can't successfully install TWRP on it. What I did:
- Bootloader unlocked
- TWRP temporary loaded with fastboot (fastboot boot twrp.img)
- In TWRP 'Iinstall' selected the matching TWRP .zip and it said it was installed in both slots a and b.
But then, when I select 'restart to bootloader' and try to launch recovery, I get a bootloop (black screen with (N/A) in the top left corner. The OS as such still starts normally. So I guess the main problem here is the bootloop when trying to launch recovery...?
I tried installing over booted TWRP with unmodified boot.img and with Magisk patched boot.img, same result. The G7 play does not have a separate revovery partition, recovery is included in the boot.img
I used the TWRP files (EU) and instructions from here:
Motorola Moto G7 Play
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
My stock firmware is XT1952-1_CHANNEL_RETEU_10_QPYS30.52-22-8-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip from here:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Am I missing something? I've now searched for days (most info is outdated, taken from other places/Motorola phones with just 'G7 play' added, or is ambiguous); so can anyone *PLEASE* help me? Does anyone have a G7 play of the same type with Android 10 Stock who has successfully installed TWRP and was able to access the Recovery afterward without being stuck in a loop?
I also can't create a TWRP backup with a fastboot booted TWRP because system (and internal SD too) seems to be encrypted, and I don't seem to be able to deactivate this in the phone. Is this normal? Some places say that TWRP can decrypt when it's installed permanently...
Or could anybody patch the boot.img in above Firmware and add TWRP for me so I can just flash the boot.img?
Thanks in advance... please reply noob-friendly.
Still need a patched boot.img? Attached you'll find a boot.img with TWRP installed. I followed your links to get boot.img + twrp.img.
NO MAGISK INSTALLED!!!​Please patch before flashing if Magisk is already installed.
I put a log of the repack command into the zip that is showing the checksums of the boot header. Just to have a proof.
WoKoschekk said:
Still need a patched boot.img? Attached you'll find a boot.img with TWRP installed.
Click to expand...
Click to collapse
Thanks for trying to help, but this boot.img behaves exactly like the one I made by following the installation instructions on the TWRP website. I flashed it, restarted bootloader, then tried to go into recovery, and it bootloops (black screen with N/A in the top left corner).
But what I need is a boot.img with a WORKING TWRP recovery (that can actually be launched when recovery is selected...
Any idea why this won't work, why TWRP won't start?
@Alonso_Quixana Try the attached one. It's a boot.img patched with twrp + recovery_dtbo. The recovery_dtbo is part of the twrp.img but TWRP's installer.zip doesn't take it into account while repacking the patched boot.img. Maybe (hopefully!) that's the reason why you're able to boot TWRP but not to install it permanently.
Please try also - in any case! - the patched installer.zip that comes with a recovery_dtbo.
Sadly, you can't flash TWRP on stock ROM, in case you did sucessfully, ROM will not boot and that can cause SIM and VoLTE issues, i did flash it on mine and now VoLTE doesn't work on my phone, you can only boot it in case you want to flash an custom ROM, flash it then reboot into recovery to install GApps on the Custom Recovery that the ROM does install, but since all of the ROMs are arm64, i don't recommend it since you will have constant app restarting when changing from one app to another app
chuy19312 said:
Sadly, you can't flash TWRP on stock ROM, in case you did sucessfully, ROM will not boot and that can cause SIM and VoLTE issues, i did flash it on mine and now VoLTE doesn't work on my phone, you can only boot it in case you want to flash an custom ROM, flash it then reboot into recovery to install GApps on the Custom Recovery that the ROM does install, but since all of the ROMs are arm64, i don't recommend it since you will have constant app restarting when changing from one app to another app
Click to expand...
Click to collapse
Thanks for replying...
I've seen so-called tutorials on Youtube where someone actually succeeded in installing TWRP on his Moto G7 play (but did not mention which Android version was on the phone), and the TWRP developers too claim that their version for Moto G7 play would work, it even got an official update for Android 10 (alas they never reply to direct e-mails, those snooty guys)... some on XDA even said the flashing of a 'dirty port' worked for them. Were they all mistaken? Or did it work on Android 9? Are all XDA threads and internet posts / Youtube videos misleading / lying?
Are you REALLY sure that there is no way to install TWRP on a Moto G7 play (to be able to create a working backup of the encrypted data partition)? A 'full restorable backup of everything' is what I need...
I'm not sure about Android 10 Stock Rom, but it seems to be a 32bit system on a 64bit Kernel?
Alonso_Quixana said:
I'm not sure about Android 10 Stock Rom, but it seems to be a 32bit system on a 64bit Kernel?
Click to expand...
Click to collapse
It's a 32bit system on a 64bit CPU (Snapdragon 632). That's not unusual for Motorola devices. Open a terminal app and execute uname -a.
Alonso_Quixana said:
Thanks for replying...
I've seen so-called tutorials on Youtube where someone actually succeeded in installing TWRP on his Moto G7 play (but did not mention which Android version was on the phone), and the TWRP developers too claim that their version for Moto G7 play would work, it even got an official update for Android 10 (alas they never reply to direct e-mails, those snooty guys)... some on XDA even said the flashing of a 'dirty port' worked for them. Were they all mistaken? Or did it work on Android 9? Are all XDA threads and internet posts / Youtube videos misleading / lying?
Are you REALLY sure that there is no way to install TWRP on a Moto G7 play (to be able to create a working backup of the encrypted data partition)? A 'full restorable backup of everything' is what I need...
I'm not sure about Android 10 Stock Rom, but it seems to be a 32bit system on a 64bit Kernel?
Click to expand...
Click to collapse
I think it only works on certain Moto G7 Play variations or even only on Android 9, also, another way to install TWRP is installing an Custom ROM then flashing an flashable zip of TWRP_11 by SyberHexen on Custom ROM's Recovery
Link to TWRP_11 Flashable Zip
channel-twrp-installer-3.6.2_11.0_RC-1.0.zip | by SyberHexen for Moto G7 Play
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
In my case, flashing TWRP, even by following some tutorials made my MetroPCS Moto G7 Play to stop booting and also, VoLTE stopped working, fortunately, i had an EFS backup to restore my IMEI
Android 10 Stock Rom is an Arm (32 bits) ROM, every Custom ROM i tested are Arm64, but i don't recommend any of them since you will get constant app rebooting and notification problems since this is an 2 GB RAM device