Hi there
I had some problems booting into Recovery and ERecovery. It would always stay endless in the Warning screen where it says that the Device is unlocked.
I run into it because of TWRP not Formating Data properly.
https://dl.twrp.me/anne/
twrp-3.5.1_9-0-anne.img14.6M 2021-03-13 15:27:54 ESTtwrp-3.5.0_9-0-anne.img13.2M 2020-12-27 21:03:29 EST
This Versions get stuck at:
Code:
Formatting Data using mkfs.f2fs...
Done
After it beeing stuck I could usually reach erecovery and wipe . But at one point it wouldn't work and I couldn't reacht the two and also couldn't stop the device from endless starting after shutting down.
I tried to flash several images from this one: https://androidhost.ru/1nfK
After flashing odm.img I could access the reflashed Stock Recovery and E-Recovery.
Update: Erasing Data with fastboot also works.
Note: It would show Google instead of Huawei at startup and in fastboot FRP:Unlocked doesn't show anymore after flashing odm.img
Else:To reach erecovery or twrp recovery I retried often to hold power and volume up when the device is turned off. It then vibrates two times when it works. I hat sometimes to try for 10 Minutes to reach one of the to.
I unlocked with PotatoNV. The phone can be opened quite comfortable with a straight package plastic like from a cabel or electric device and a hairdrier.
Update: I can actually not format Data with any of these TWRPs. This was working before flashing the odm or maybe an other image.
twrp-3.5.1_9-0-anne.img14.6M 2021-03-13 15:27:54 ESTtwrp-3.5.0_9-0-anne.img13.2M 2020-12-27 21:03:29 ESTtwrp-3.4.0-1-anne.img13.2M 2020-09-26 14:58:13 EDTtwrp-3.4.0-0-anne.img13.2M 2020-08-21 17:03:57 EDT
I could format with adb shell:
anne:/etc # mkfs.f2fs /dev/block/mmcblk0pXX
F2FS-tools: mkfs.f2fs Ver: 1.10.0 (2018-01-30)
Info: Disable heap-based policy
Info: Debug level = 0
Info: Label =
Info: Trim is enabled
Info: No support kernel version!
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 106086400 (51800 MB)
Info: zone aligned segment0 blkaddr: 512
Info: [/dev/block/mmcblk0p57] Discarding device
Info: Secure Discarded 0 MB
Info: Overprovision ratio = 0.880%
Info: Overprovision segments = 459 (GC reserved = 235)
Info: format successful
benaep said:
I can actually not format Data with any of these TWRPs.
Click to expand...
Click to collapse
Yes, you have installed wrong TWRP (version 3.4.0.x and 3.5.0.x is not fully compatible with our device and it's strongly NOT recommended do 'wipe data' runnig stock ROM , it may brick the phone).
Use recommended TWRP:
Recommended and tested TWRP Recovery
EMUI 8 Stock ROMs: 3.2.1-0 by pretoriano80 (with data decryption on Android 8 ) https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw EMUI 8 Custom ROMs: 3.2.1.0 by Catuva21...
forum.xda-developers.com
-Alf- said:
Yes, you have installed wrong TWRP (version 3.4.0.x and 3.5.0.x is not fully compatible with our device and it's strongly NOT recommended do 'wipe data' runnig stock ROM , it may brick the phone).
Use recommended TWRP:
Recommended and tested TWRP Recovery
EMUI 8 Stock ROMs: 3.2.1-0 by pretoriano80 (with data decryption on Android 8 ) https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw EMUI 8 Custom ROMs: 3.2.1.0 by Catuva21...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the direction Alf. So for the Newest Linage OS build that would be:
Pie Custom ROMs:
3.4.0-0-emui9_eR
MEGA
MEGA provides free cloud storage with convenient and powerful always-on privacy. Claim your free 20GB now
mega.nz
right?
benaep said:
Thanks for the direction Alf. So for the Newest Linage OS build that would be:
Pie Custom ROMs:
3.4.0-0-emui9_eR
MEGA
MEGA provides free cloud storage with convenient and powerful always-on privacy. Claim your free 20GB now
mega.nz
right?
Click to expand...
Click to collapse
If you want to flash LOS from TWRP (idk why, but it's your choice), use 3.2.1 by pretoriano80 (wiping etc.) After installing custom ROM, you can replace 3.2.1. with 3.4.0.0-emui9_eR.
-Alf- said:
If you want to flash LOS from TWRP (idk why, but it's your choice), use 3.2.1 by pretoriano80 (wiping etc.) After installing custom ROM, you can replace 3.2.1. with 3.4.0.0-emui9_eR.
Click to expand...
Click to collapse
Hi Alf
Thanks for the reply. Very gratefull for this. I'm trying since Weeks to get this running.
I just want a phone with minimal Google. I had /e/ but I didn't find a build and back in the days linage would be fine.
You think there is something which makes more sense?
benaep said:
I just want a phone with minimal Google
Click to expand...
Click to collapse
Then install "v" variant , e.g.
LOS 17.1-unoff.
https://sourceforge.net/projects/treblerom/files/LOSQ/2020.10.17/losq-v224-201017-arm64-bvN.img.xz/download
LOS 18.1-unoff.
https://sourceforge.net/projects/treblerom/files/LiR/2021.03.18/lir-v302-210318-arm64-bvZ.img.xz/download
and install opengapps - pico, nano, micro... , what suits you.
-Alf- said:
Then install "v" variant , e.g.
LOS 17.1-unoff.
https://sourceforge.net/projects/treblerom/files/LOSQ/2020.10.17/losq-v224-201017-arm64-bvN.img.xz/download
LOS 18.1-unoff.
https://sourceforge.net/projects/treblerom/files/LiR/2021.03.18/lir-v302-210318-arm64-bvZ.img.xz/download
and install opengapps - pico, nano, micro... , what suits you.
Click to expand...
Click to collapse
Yo Alf
Thanks for the Links to the Image files. I would never have found them myself. I tried now a few hours to make them run.
Formating and Wiping works with 3.2.1 by pretoriano80
I tried both images, but am not shure. I get an invalid zip file error when I copy it on the device. Sideload doesn't work. No connection or Success or Success 00.00 X.
I make it a zip on linux with --> unxz --> img2simg --> Create Zip Directory wit xarchiver.
I tried different combinations of this. First I forgot about simg and just made a zip out of the img.
Code:
/tmp/recovery.log: 1 f...57322 bytes in 0.010s)
~ >>> adb sideload /home/bni/Downloads/losq17.zip
adb: failed to read command: Success
~ >>> adb sideload /home/bni/Downloads/losq17.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
~ >>> adb pull /tmp/recovery.log /home/bni/Downloads/recovery.log
/tmp/recovery.log: 1 f...59228 bytes in 0.007s)
Code:
~ # twrp install /image/LOS17_SIMG.zip
Installing zip file '/image/LOS17_SIMG.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
Invalid zip file format!
Error installing zip file '/image/LOS17_SIMG.zip'
Done processing script file
benaep said:
I get an invalid zip file error when I copy it on the device.
Click to expand...
Click to collapse
Of course, it is not a flashable .zip file.
You have to install it as image file, unpack .zip package, transfer exctracted .img file to the SD card. In TWRP go to Install , select Install image, choose lineage .img file , mark "system image" and flash.
If you need to do a factory reset , first replace TWRP with stock recovery and perform factory reset in recovery.
Or, flash Lineage.img in fastboot,without TWRP, wipes, errors etc. (make sure to have the stock recovery flash) - https://forum.xda-developers.com/t/losq-lineageos-17-1-18-1-unofficial-gsi.4219291/post-84305543
Easy to way to install a GSI on your Samsung A21s without installing a Virtual Linux.
NFC, Screen Cast, and USB MTP unfortunately is not working with AOSP 10 and 11. Backup all your data.
If don't want to make one, download my Pre-Rooted GSIs below and flash.
*Unlock your Bootloader and wipe your data using your stock recovery and quickly boot to Download Mode and flash the super.tar on Odin (AP):
Android 10 -> Download (MediaFire)Android 11 -> Download (MediaFire)Android 11 - AOSP 11.0 v306 -> Download (MEGA) - NEWAndroid 10 Screenshots
1. Requirements:
1. Unlock your Bootloader2. Download and Install a Linux Subsystem -> Ubuntu Subsystem -> "Tutorial How to install Linux Subsystem on Windows 10 | or search how to"3. GSI Android 10 A/B Gapps -> Download only the "arm64, A/B". I recommend releases from Treble Experimentations AOSP like "system-roar-arm64-ab-gapps.img.xz". 4. Samsung.zip -> There's all needed tools and files - Odin, 7-Zip ZS etc...
- Download Samsung.zip and extract the folder "Samsung" to your desktop, and extract your chosen GSI using to this folder.
- Download your stock firmware and extract the super.img.lz4 file from AP_A217XXXXXXXXXX_XXX_XXXX_REV00_XXX.tar.md5 with 7-Zip ZS.
- Now extract super.img.lz4 using 7-Zip ZS (don't use 7-zip) to Samsung folder. Rename super.img to stock_super.img.
2. Convert stock_super.img to raw_super.img:Open CMD ad use this codes:
cd C:\Users\%USERNAME%\Desktop\Samsungsimg2img.exe stock_super.img raw_super.img
Wait...
3. Extract raw_super.img:On your Samsung folder, use SHIFT key of your keyboard + right click and click at "Open Linux Shell Here", wait a little, and use this code and wait the extraction:
./lpunpack --slot=0 raw_super.img
*If the extraction is completed, verify if there's this files odm.img, system.img, vendor.img and product.img. Delete or rename system.img and product.img, then extract your GSI to Samsung folder and rename the xxx.img file to system.img.
4. Pack all the files and Flash:No math here! Just use this code on Terminal and wait (Ignore errors like "Partition system, vendor, odm will resize..." or "Invalid sparce file format at header magic...")
./lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:5557452800 --group main:3819597824 --partition system:readonly:3340271616:main --image system=./system.img --partition vendor:readonly:474976256:main --image vendor=./vendor.img --partition odm:readonly:4349952:main --image odm=./odm.img --sparse --output ./super.img
Wait....
Use 7-Zip to archive the super.img to .tar (super.tar) and flash it on Odin (AP) and wait the phone to boot.
Unlock your Bootloader and wipe your data using your stock recovery and quickly boot to Download Mode and flash the super.tar on Odin (AP):
Notes:I not responsible for any damage on your phone. If anything occurs, just flash your stock regional firmware through Odin.
If this tutorial did not work, you did something wrong or your phone is not supported. Don't forget to wipe your data through Recovery, it's very important.
If you want Magisk working on your A21s I recommend you to report to an issue Topjohnwu at Github.
Dear Wer99,
I Successfully Made A Non-Rooted GSI By Following Your [Tutorial / Guide],
I'm Wondering How Could I Add SuperSU & Root Permission In It
GSI : [CherishOS, AOSP10, AOSP11]
Wer99 said:
Easy to way to install a GSI on your Samsung A21s without installing a Virtual Linux.
NFC, Screen Cast, and USB MTP unfortunately is not working with AOSP 10 and 11. Backup all your data.
If don't want to make one, download my Pre-Rooted GSIs below and flash.
*Unlock your Bootloader and wipe your data using your stock recovery and quickly boot to Download Mode and flash the super.tar on Odin (AP):
Android 10 -> Download (MediaFire)Android 11 -> Download (MediaFire)Android 11 - AOSP 11.0 v306 -> Download (MEGA) - NEWAndroid 10 Screenshots
1. Requirements:
1. Unlock your Bootloader2. Download and Install a Linux Subsystem -> Ubuntu Subsystem -> "Tutorial How to install Linux Subsystem on Windows 10 | or search how to"3. GSI Android 10 A/B Gapps -> Download only the "arm64, A/B". I recommend releases from Treble Experimentations AOSP like "system-roar-arm64-ab-gapps.img.xz". 4. Samsung.zip -> There's all needed tools and files - Odin, 7-Zip ZS etc...
- Download Samsung.zip and extract the folder "Samsung" to your desktop, and extract your chosen GSI using to this folder.
- Download your stock firmware and extract the super.img.lz4 file from AP_A217XXXXXXXXXX_XXX_XXXX_REV00_XXX.tar.md5 with 7-Zip ZS.
- Now extract super.img.lz4 using 7-Zip ZS (don't use 7-zip) to Samsung folder. Rename super.img to stock_super.img.
2. Convert stock_super.img to raw_super.img:Open CMD ad use this codes:
cd C:\Users\%USERNAME%\Desktop\Samsungsimg2img.exe stock_super.img raw_super.img
Wait...
3. Extract raw_super.img:On your Samsung folder, use SHIFT key of your keyboard + right click and click at "Open Linux Shell Here", wait a little, and use this code and wait the extraction:
./lpunpack --slot=0 raw_super.img
*If the extraction is completed, verify if there's this files odm.img, system.img, vendor.img and product.img. Delete or rename system.img and product.img, then extract your GSI to Samsung folder and rename the xxx.img file to system.img.
4. Pack all the files and Flash:No math here! Just use this code on Terminal and wait (Ignore errors like "Partition system, vendor, odm will resize..." or "Invalid sparce file format at header magic...")
./lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:5557452800 --group main:3819597824 --partition system:readonly:3340271616:main --image system=./system.img --partition vendor:readonly:474976256:main --image vendor=./vendor.img --partition odm:readonly:4349952:main --image odm=./odm.img --sparse --output ./super.img
Wait....
Use 7-Zip to archive the super.img to .tar (super.tar) and flash it on Odin (AP) and wait the phone to boot.
Unlock your Bootloader and wipe your data using your stock recovery and quickly boot to Download Mode and flash the super.tar on Odin (AP):
Notes:I not responsible for any damage on your phone. If anything occurs, just flash your stock regional firmware through Odin.
If this tutorial did not work, you did something wrong or your phone is not supported. Don't forget to wipe your data through Recovery, it's very important.
If you want Magisk working on your A21s I recommend you to report to an issue Topjohnwu at Github.
Click to expand...
Click to collapse
I tried all of this and I even went as far as trying to literally change the filesystem UUID and the filesystem of system.img as well, I detected some issues when booting a GSI and it's that the filesystem and the filesystem UUID's had to match (filesystem had to be EXT2 for some reason), and after I did all of that, I flashed the super.img to my phone but after a few seconds of it trying to boot (10 seconds after it's past the unlocked bootloader screen) it just reboots and kicks me to fastboot mode, a friend of mine told me that if it booted to fastboot it meant that the bootloader was able to pass instructions to the OS but failed, hence why it kicked me to fastboot, and after that I tried with different GSIs and neither of them worked sadly.
Also in the attributes I'd recommend changing "readonly" to "none" so that the partitions are Read/Write from super.img, after flashing super.img, just edit the fstab file (located in "/etc/fstab" for recovery) and replace "ro" in the mount points with "rw" so that you can read and write data to them, the point of this is to make the partitions read and write so that you can edit them and install anything you'd like, and that's exactly the reason I did it.
After some time we got a modded magisk apk that does work and doesn't have the legacy device detection issue that it had before, due to the phone using dynamic partitions and using a ramdisk, Magisk would detect the device as legacy and it would use "SAR_init", something that the device doesn't needs and because the boot process fails, it reboots.
Also, before I realized that you could make the partitions inside super.img read/write, I would usually use readonly and it wouldn't work either, I'd appreciate if you could help me with this.
Wer99 said:
Easy to way to install a GSI on your Samsung A21s without installing a Virtual Linux.
NFC, Screen Cast, and USB MTP unfortunately is not working with AOSP 10 and 11. Backup all your data.
If don't want to make one, download my Pre-Rooted GSIs below and flash.
*Unlock your Bootloader and wipe your data using your stock recovery and quickly boot to Download Mode and flash the super.tar on Odin (AP):
Android 10 -> Download (MediaFire)Android 11 -> Download (MediaFire)Android 11 - AOSP 11.0 v306 -> Download (MEGA) - NEWAndroid 10 Screenshots
1. Requirements:
1. Unlock your Bootloader2. Download and Install a Linux Subsystem -> Ubuntu Subsystem -> "Tutorial How to install Linux Subsystem on Windows 10 | or search how to"3. GSI Android 10 A/B Gapps -> Download only the "arm64, A/B". I recommend releases from Treble Experimentations AOSP like "system-roar-arm64-ab-gapps.img.xz". 4. Samsung.zip -> There's all needed tools and files - Odin, 7-Zip ZS etc...
- Download Samsung.zip and extract the folder "Samsung" to your desktop, and extract your chosen GSI using to this folder.
- Download your stock firmware and extract the super.img.lz4 file from AP_A217XXXXXXXXXX_XXX_XXXX_REV00_XXX.tar.md5 with 7-Zip ZS.
- Now extract super.img.lz4 using 7-Zip ZS (don't use 7-zip) to Samsung folder. Rename super.img to stock_super.img.
2. Convert stock_super.img to raw_super.img:Open CMD ad use this codes:
cd C:\Users\%USERNAME%\Desktop\Samsungsimg2img.exe stock_super.img raw_super.img
Wait...
3. Extract raw_super.img:On your Samsung folder, use SHIFT key of your keyboard + right click and click at "Open Linux Shell Here", wait a little, and use this code and wait the extraction:
./lpunpack --slot=0 raw_super.img
*If the extraction is completed, verify if there's this files odm.img, system.img, vendor.img and product.img. Delete or rename system.img and product.img, then extract your GSI to Samsung folder and rename the xxx.img file to system.img.
4. Pack all the files and Flash:No math here! Just use this code on Terminal and wait (Ignore errors like "Partition system, vendor, odm will resize..." or "Invalid sparce file format at header magic...")
./lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:5557452800 --group main:3819597824 --partition system:readonly:3340271616:main --image system=./system.img --partition vendor:readonly:474976256:main --image vendor=./vendor.img --partition odm:readonly:4349952:main --image odm=./odm.img --sparse --output ./super.img
Wait....
Use 7-Zip to archive the super.img to .tar (super.tar) and flash it on Odin (AP) and wait the phone to boot.
Unlock your Bootloader and wipe your data using your stock recovery and quickly boot to Download Mode and flash the super.tar on Odin (AP):
Notes:I not responsible for any damage on your phone. If anything occurs, just flash your stock regional firmware through Odin.
If this tutorial did not work, you did something wrong or your phone is not supported. Don't forget to wipe your data through Recovery, it's very important.
If you want Magisk working on your A21s I recommend you to report to an issue Topjohnwu at Github.
Click to expand...
Click to collapse
Also, Just so you know, the recovery that we have is OrangeFox R11 which is currently an alpha build, thanks to magisk I was able to use the tool "dd" in termux to flash the recovery.img to /dev/block/by-name/recovery (aka the recovery partition) and this helped me bypass DL mode which is even worse now that I upgraded to U5 (I regret it and I tried downgrading from recovery instead of DL mode but the linux kernel itself protects the mmcblk0boot0 partition which is supposed to be the partition where the "BL" is located, and I tried flashing the sboot.bin file to that partition and it didn't work due to it being protected
Anyways back to the original topic, I don't know how but after flashing OrangeFox R11 with dd in android (I used su with magisk of course because), OrangeFox managed to boot with stock vbmeta and this build was supposedly built with A10's firmware in mind, not A11's firmware, so I have some hopes that flashing super.img from recovery might work if given the right vendor and firmware, I even flashed a vbmeta that was made for U3 from OrangeFox and it booted without any issues, oddly enough OneUI booted with that U3 vbmeta.img
LonelyCracker said:
Dear Wer99,
I Successfully Made A Non-Rooted GSI By Following Your [Tutorial / Guide],
I'm Wondering How Could I Add SuperSU & Root Permission In It
GSI : [CherishOS, AOSP10, AOSP11]
Click to expand...
Click to collapse
You don't need SuperSU anymore, There's already a fixed magisk for it, Here's the links:
[SHARING] HOW TO ROOT A21S STOCK ROM WITH MAGISK
Hello friends I just want to share how to root A21S stock rom in case anybody needs it: 1. Unlock bootloader 2. (On PC) Extract boot.img.lz4 from AP...tar file, then copy it to phone 3. (On phone) Install ZArchiver to extract boot.img from...
forum.xda-developers.com
[ROOT] Modified Magisk for Galaxy A21S (R)
It seems that the A21S hasn't had any root since it was released (other than pre-rooted GSI ROMS) When flashing Magisk, the phone went into bootloop, and the only way to fix it was to flash stock rom via Odin. After some analysis, it seems that...
forum.xda-developers.com
David112+ said:
You don't need SuperSU anymore, There's already a fixed magisk for it, Here's the links:
[SHARING] HOW TO ROOT A21S STOCK ROM WITH MAGISK
Hello friends I just want to share how to root A21S stock rom in case anybody needs it: 1. Unlock bootloader 2. (On PC) Extract boot.img.lz4 from AP...tar file, then copy it to phone 3. (On phone) Install ZArchiver to extract boot.img from...
forum.xda-developers.com
[ROOT] Modified Magisk for Galaxy A21S (R)
It seems that the A21S hasn't had any root since it was released (other than pre-rooted GSI ROMS) When flashing Magisk, the phone went into bootloop, and the only way to fix it was to flash stock rom via Odin. After some analysis, it seems that...
forum.xda-developers.com
Click to expand...
Click to collapse
Yeah I Know But I'm Just Interested In Making A Prerooted GSI
LonelyCracker said:
Yeah I Know But I'm Just Interested In Making A Prerooted GSI
Click to expand...
Click to collapse
What's the point of making a prerooted GSI with an outdated root method?
You can't even install modules with SuperSU
To David112+ :
In My Opinion, Prerooted GSI Is Way Better.
You Could See The Comparison I Made Here.
Also Making One GSI Could Gain Me Lots Of Experience.
So I Couldn't Think Of The Reason Why Not
Magisk Patched Stock [Firmware / ROM] Also Have It Own Problem,
Which You Could Find Here.
LonelyCracker said:
To David112+ :
In My Opinion, Prerooted GSI Is Way Better.
You Could See The Comparison I Made Here.
Also Making One GSI Could Gain Me Lots Of Experience.
So I Couldn't Think Of The Reason Why Not
Magisk Patched Stock [Firmware / ROM] Also Have It Own Problem,
Which You Could Find Here.
Click to expand...
Click to collapse
I don't think you've realized or checked the group of the phone but a load of people have already rooted their ROMs with Magisk and so far they have no problems, and still, everyone agrees that installing modules somewhere from the internet is the responsibility of the end user.
And I'm pretty sure that everyone agrees that magisk is the best root method, and even if you wipe data, you can just reinstall the Magisk apk to get the root prompt and finish setting it up, or better yet. use the systemizer module to systemize the magisk apk so that it's installed in system instead of data.
Making a prerooted GSI is just a waste of time, I'd rather just make normal GSI that's flashable on the phone and just install Magisk or systemize the Magisk APK.
I do agree that making a GSI flashable for the phone makes you gain a lot of experience but you're wasting your time into something that barely anyone is going to use, due to the fact that it has SuperSU which is old and outdated and most people prefer Magisk anyways because it's updated and not only that but you can pretty much install anything you'd like with the modules.
To David112+ :
Sorry To Disagree With You, I Was Trying To Acheive A Goal There .
My Goal Was To Get ADB (Android Debug Bridge) With "adb root" Working On Magisk Patched Stock [Firmware / ROM]. After Many Research & Attempt To Acheive That, I Gave Up... I Gained Some Knowledge There Too. I Know That Stock Rom Are For Production Purpose & I Can't Gain Root Access Using ADB (Android Debug Bridge).
Hopefully I Could Get Help Somewhere.
But Fun Fact Is...
I Water-Damaged My Phone
Question :
1.) Is It Possible To Make A Non Rooted GSI & Patch It With Magisk ? How ?
LonelyCracker said:
To David112+ :
Sorry To Disagree With You, I Was Trying To Acheive A Goal There .
My Goal Was To Get ADB (Android Debug Bridge) With "adb root" Working On Magisk Patched Stock [Firmware / ROM]. After Many Research & Attempt To Acheive That, I Gave Up... I Gained Some Knowledge There Too. I Know That Stock Rom Are For Production Purpose & I Can't Gain Root Access Using ADB (Android Debug Bridge).
Hopefully I Could Get Help Somewhere.
But Fun Fact Is...
I Water-Damaged My Phone
Question :
1.) Is It Possible To Make A Non Rooted GSI & Patch It With Magisk ? How ?
Click to expand...
Click to collapse
Custom ROMs should work with ADB root normally
2. To install Magisk just use the links that I shared in this post (https://forum.xda-developers.com/t/...d-gsis-for-samsung-a21s.4269227/post-84975373)
After upgrading to U5, I can't install these GSIs anymore. It bootloop all the times
To David112+ :
But Is Not Possible To Use ADB (Android Debug Bridge) On Magisk Patched Stock [Firmware / ROM]. What I Was Saying Is To Use "adb root" On Magisk Patched Stock [Firmware / ROM]
I'm Only Able To Use The Command "adb root" In Custom GSI Built By Wer99.
Not Every Custom Build GSI Are Prerooted.
Maybe You're Right Magisk Is Better Than Old Little SuperSU. But I Need "adb root" To Work With It
thatha said:
After upgrading to U5, I can't install these GSIs anymore. It bootloop all the times
Click to expand...
Click to collapse
If you have magisk with stock ROM, good news for you, I'll be working a guide in how to get a GSI installed as a magisk module, I tested this with ShapeShiftOS and I got as far as the boot animation of ShapeShiftOS, Once I was booted I checked ADB and sdcard was encrpyted and that's why it wasn't able to start correctly, it was just stuck in the google logo with a loading bar, I'm gonna try decrypting data, formatting and then installing the module
If this does work then I'll be releasing a guide in how to get a GSI of your preference working as a magisk module
Explanation: Thanks to Magisk's Magic Mount feature, I'm able to systemlessly swap the assets of OneUI with a Custom ROM's of my choosing, such as ShapeShiftOS
Edit: This idea is discarded, Because of the userdata partition being encrypted I can't use ShapeShiftOS, and even after decrypting I can't use it because OneUI gets stuck in "Starting android" when using the boot image with patched fstab and magisk
And if I download gsi android 11 through mediafire, will I have to do all this procedure? or just flash on odin? A21S ANDROID 11.
To Oroki:
These GSI Is Ready To Be Flashed.
LonelyCracker said:
To Oroki:
These GSI Is Ready To Be Flashed.
Click to expand...
Click to collapse
but will i have to do topic 2 and 3?
To Oroki :
Please Explain What Do You Mean By Topic 2 & 3
LonelyCracker said:
To Oroki :
Please Explain What Do You Mean By Topic 2 & 3
Click to expand...
Click to collapse
2. Converta stock_super.img em raw_super.img: e3. Extrato raw_super.img:
To Oroki :
Those Step You Provide Aren't Necessary Anymore
It's Patched Which Mean You Don't Have To Do Anything To It
Sorry For Late Reply
Platform-Tools
Windows - Mac OS - Linux
Drivers
Windows 64 Bit - 32 Bit - Mac OS
Zip
Stock Firmware (Android 11) - Bootloader Unlock
GSI ROM (PixelExperience_Plus_arm64-ab-11.0-20211011-UNOFFICIAL.img.xz)
product_gsi.img
Root Magisk (rename the .apk file extension to .zip) installing using recovery OrangeFoxR11.1 - twrp_3.6.1-11-0
****COMMAND****
flash stock - flash gsi
adb reboot bootloader
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
exit
adb reboot fastboot
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot flash product product_gsi.img
fastboot flash boot boot2.img
fastboot flash system pixel.img
fastboot flash recovery recovery2.img
fastboot -w
fastboot reboot
exit
Click to expand...
Click to collapse
Spoiler
- boot boot2.img and recovery recovery2.img <---- optional
- fastboot flash system pixel.img <---- rom-name
Procedure to install the GSI custom ROM
- Extract Platform Tools + Stock Firmware + GSI ROM + gsi product (in the same folder) and launch commands, easy
List + GSI
II'm test before, thanks
Si alguien lo prueba para hacerle saber cómo le está yendo
I've already tried it and it can't install the rom, I don't know if I'm executing the command wrong or what, but it didn't work for me.
Kira565 said:
I've already tried it and it can't install the rom, I don't know if I'm executing the command wrong or what, but it didn't work for me.
Click to expand...
Click to collapse
1. https://mirrors.lolinet.com/firmware/moto/astro/official/
2. Ctrl + F download rom "RPL31" (RPLS31, not)
3. After you install the Stock ROM and the device starts correctly, activate usb debugging and execute these commands:
adb reboot fastboot
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot flash product product_gsi.img
fastboot flash system ROM.img
fastboot -w
fastboot reboot
exit
Por favor de um jeito pelo Orange Fox sem PC
Alexsjvr1 said:
Melhor da um jeito pelo Orange Fox sem utilização de PC por favor
Click to expand...
Click to collapse
Alexsjvr1 said:
1. https://mirrors.lolinet.com/firmware/moto/astro/official/
2. Ctrl + F download rom "RPL31" (RPLS31, not)
3. After you install the Stock ROM and the device starts correctly, activate usb debugging and execute these commands:
adb reboot fastboot
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot flash product product_gsi.img
fastboot flash system ROM.img
fastboot -w
fastboot reboot
exit
Click to expand...
Click to collapse
thanks bro I already tried several I am currently on corvus gsi
Alexsjvr1 said:
Hello! How are you? This is my first post on this page, and I wanted to share the method to install GSI ROM on this One Fusion, I do it at the request of a friend
It is a simple process that does not take more than 15 minutes, come on! !
SDK tools platform 7-Zip
Windows - Mac OS - Linux
Windows Drivers 64 Bit 32 Bit - Mac OS
Stock Firmware (Android 11) - Bootloader Unlock
GSI ROM (PixelExperience_Plus_arm64-ab-vndklite-11) - product_gsi.img
Magisk (rename the .apk file extension to .zip) installing using custom recovery
or you can try this already patched image magisk_patched
COMMAND
Spoiler
- boot boot2.img and recovery recovery2.img <---- optional
- fastboot flash system pixel.img <---- rom-name
Procedure to install the GSI custom ROM
- Extract Platform Tools + Stock Firmware + GSI ROM + gsi product (in the same folder) and launch commands, easy
Here is a link that I find interesting to share for those who have not yet decided which rom to install 15 best custom ROMs
Click to expand...
Click to collapse
its faster and stable, but the multimedia audio via Bluetooth does not work.
In Logcat... Bluetooth is crazy and has battery drain... the rom needs a FIX.
I RECOMMEND CrDroid GSI ctrl+f (-arm64-bgZ-lite.img.xz)
crDroid.net - increase performance and reliability over stock Android for your device
official crDroid ROM blog
crdroid.net
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
reddermanu said:
its faster and stable, but the multimedia audio via Bluetooth does not work.
In Logcat... Bluetooth is crazy and has battery drain... the rom needs a FIX.
Click to expand...
Click to collapse
You can fix the bluetooth media audio disabling the A2DP offload in PHH settings, I have also experienced the battery drain issue on most GSIs, try to stick to AOSP as I haven't met any battery drain there.
reddermanu said:
its faster and stable, but the multimedia audio via Bluetooth does not work.
In Logcat... Bluetooth is crazy and has battery drain... the rom needs a FIX.
Click to expand...
Click to collapse
Solution to Bluetooth connection problem
To fix the Bluetooth connection problem, simply go to Settings/PHH Treble Settings/Misc Features and check the Force-disable A2DP offload option. Then, restart the phone.
KUATIKO said:
I RECOMMEND CrDroid GSI ctrl+f (-arm64-bgZ-lite.img.xz)
crDroid.net - increase performance and reliability over stock Android for your device
official crDroid ROM blog
crdroid.net
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
Click to expand...
Click to collapse
crDroid exelent option
I got the following error when I executed the command fastboot flash system image:
target reported max download size of 536870912 bytes
Invalid sparse file format at header magic
sending sparse 'system_a' 1/6 (524212 KB)...
OKAY [ 13.213s]
writing 'system_a' 1/6...
OKAY [ 2.874s]
sending sparse 'system_a' 2/6 (518272 KB)...
OKAY [ 13.113s]
writing 'system_a' 2/6...
FAILED (remote: Operation not permitted)
finished. total time: 31.563s
Click to expand...
Click to collapse
The bootloader is unlocked and I flashed the stock rom as described on tutorial.
lteixeiramnc said:
I got the following error when I executed the command fastboot flash system image:
The bootloader is unlocked and I flashed the stock rom as described on tutorial.
Click to expand...
Click to collapse
@lteixeiramnc you must use the latest version of fastboot https://developer.android.com/studio/releases/platform-tools.
crdroid is the best https://sourceforge.net/projects/tr...om-v316-220330-arm64-bgZ-lite.img.xz/download
disable the A2DP offload in PHH settings!
Alexsjvr1 said:
Hello! How are you? This is my first post on this page, and I wanted to share the method to install GSI ROM on this One Fusion, I do it at the request of a friend
It is a simple process that does not take more than 15 minutes, come on! !
SDK tools platform - 7-Zip
Windows - Mac OS - Linux
Windows Drivers 64 Bit 32 Bit - Mac OS
Stock Firmware (Android 11) - Bootloader Unlock
GSI ROM (PixelExperience_Plus_arm64-ab-vndklite-11) - product_gsi.img
Magisk (rename the .apk file extension to .zip) installing using custom recovery
or you can try this already patched image magisk_patched
COMMAND
Spoiler
- boot boot2.img and recovery recovery2.img <---- optional
- fastboot flash system pixel.img <---- rom-name
Procedure to install the GSI custom ROM
- Extract Platform Tools + Stock Firmware + GSI ROM + gsi product (in the same folder) and launch commands, easy
Here is a link that I find interesting to share for those who have not yet decided which rom to install 15 best custom ROMs
Click to expand...
Click to collapse
@dpkg-i-foo-deb @Alexsjvr1 masters!
can i install a android12 gsi??
latest pixelexperience for example?
reddermanu said:
@dpkg-i-foo-deb @Alexsjvr1 masters!
can i install a android12 gsi??
latest pixelexperience for example?
Click to expand...
Click to collapse
Yes+info: https://teletype.in/@syoker/XT2073-FlashGSIROM_EN
Alexsjvr1 said:
Yes+info: https://teletype.in/@syoker/XT2073-FlashGSIROM_EN
Click to expand...
Click to collapse
@Alexsjvr1 best android 12 gsi rom for astro? help with link... I don't know which one to download
reddermanu said:
@Alexsjvr1 best android 12 gsi rom for astro? help with link... I don't know which one to download
Click to expand...
Click to collapse
These are the most used:
Pixel Experience Plus
Release Pixel Experience Plus 12.1 v412 · ponces/treble_build_pe
Initial PE+ build Sync with April sources of PE+ Sync with AOSP 12.1 v412 (thanks @phhusson) Clean flash is not required if coming from normal version!
github.com
SuperiorOS
xiaomemeindex.com
CorvusOS
Tipz Team Builds - Browse /GSIs/CorvusROM/Beta/20220423 at SourceForge.net
sourceforge.net
crDroid
Gsi_projects - Browse /v412/crDroid-8.4 at SourceForge.net
sourceforge.net
Alexsjvr1 said:
These are the most used:
Pixel Experience Plus
Release Pixel Experience Plus 12.1 v412 · ponces/treble_build_pe
Initial PE+ build Sync with April sources of PE+ Sync with AOSP 12.1 v412 (thanks @phhusson) Clean flash is not required if coming from normal version!
github.com
SuperiorOS
xiaomemeindex.com
CorvusOS
Tipz Team Builds - Browse /GSIs/CorvusROM/Beta/20220423 at SourceForge.net
sourceforge.net
crDroid
Gsi_projects - Browse /v412/crDroid-8.4 at SourceForge.net
sourceforge.net
Click to expand...
Click to collapse
thank for the direct linksssssss