Related
We know that Moto Z2 Force is not compatible with Treble. However, devs worked hard and some users got it working.
I use more than 10 hours, going and coming back, reseting, etc. and could not make it work.
Until now, I'm following the steps bellow and wish to discuss what we can do to get Treble in our device.
I've tested 4 to 5 A/B arm64 images from here and follow the general guidance from here.
I'm using XT1789-05 model (the International one, not branded) and this could be the cause of the issues.
I lost SIM card recognition in some "sucessful" attemps.
[AOSP ROM] - (tested with Magisk installed and without) and from [Stock]
Fastboot -w
Boot treble TWRP
Format data
Flash GSI image
Flash MindTheGapps.zip
Mount vendor
Flash bootSPLfix.zip
Mount vendor
Flash post 1 and post 2
Flash Permissiver
Mount vendor
Flash FBE disabler
Then format data again
Boot up
<Lost SIM card recognition>
…
I've posted the logs here: https://forum.xda-developers.com/showpost.php?p=77355827&postcount=49
The closer I could dig for some "error" are:
While flashing FBE Disabler
sed: /vendor/etc/*fstab*: No such file or directory
While flashing Trebble/POST-sGSI_2_v0.17.zip
...
sed: /vendor/build.prop: No such file or directory
grep: /vendor/manifest.xml: No such file or directory
grep: /vendor/etc/init/hw/*: No such file or directory
sed: -i requires an argument
sed: -i requires an argument
sed: /vendor/manifest.xml: No such file or directory
sed: /vendor/lib64/[email protected]_vendor.so: No such file or directory
sed: /vendor/lib64/[email protected]: No such file or directory
ls: /vendor/bin/hw/android.hardware.biometrics.fingerprint*: No such file or directory
Did you flash LineageOS before flashing the GSI image?
Marcowe said:
Did you flash LineageOS before flashing the GSI image?
Click to expand...
Click to collapse
No, thank you. I've learned to do that. But now, it's difficult to get root (https://forum.xda-developers.com/showpost.php?p=77391204&postcount=351).
Also, I'm facing a very strange thing that the screen changes color, got distorted. When using stock and AOSP ROMs, everything is normal...
Technical said:
No, thank you. I've learned to do that. But now, it's difficult to get root (https://forum.xda-developers.com/showpost.php?p=77391204&postcount=351).
Also, I'm facing a very strange thing that the screen changes color, got distorted. When using stock and AOSP ROMs, everything is normal...
Click to expand...
Click to collapse
But when you flash the sGSI image you will lose Lineage LOL
Just a suggestion to those still trying to get a GSI like, Android Q Generic GSI found here : https://developer.android.com/preview/gsi-release-notes#
We just got it to boot easier then a regular ROM would too.
-Fastboot boot TWRP
-Wipe Dalvik, Data and System.
-Flash the vbmeta.img
-Flash the system .img GSI via TWRP
-Factory Reset
-Reboot in BootLoader
-fastboot -w
-Start
-No LOS was NOT Necessary to boot this or any GSI build
Hopes this can help some of you out....
HACK3DANDR0ID said:
Just a suggestion to those still trying to get a GSI like, Android Q Generic GSI found here : https://developer.android.com/preview/gsi-release-notes#
We just got it to boot easier then a regular ROM would too.
-Fastboot boot TWRP
-Wipe Dalvik, Data and System.
-Flash the vbmeta.img
-Flash the system .img GSI via TWRP
-Factory Reset
-Reboot in BootLoader
-fastboot -w
-Start
-No LOS was NOT Necessary to boot this or any GSI build
Hopes this can help some of you out....
Click to expand...
Click to collapse
Never heard of a vbmeta.img. Where do I get this? Is it specific to this phone or is it generic?
fierogt42 said:
Never heard of a vbmeta.img. Where do I get this? Is it specific to this phone or is it generic?
Click to expand...
Click to collapse
https://source.android.com/security/verifiedboot
https://android.googlesource.com/platform/external/avb/+/master/README.md#Build-System-Integration
HACK3DANDR0ID said:
Just a suggestion to those still trying to get a GSI like, Android Q Generic GSI found here : https://developer.android.com/preview/gsi-release-notes#
We just got it to boot easier then a regular ROM would too.
-Fastboot boot TWRP
-Wipe Dalvik, Data and System.
-Flash the vbmeta.img
-Flash the system .img GSI via TWRP
-Factory Reset
-Reboot in BootLoader
-fastboot -w
-Start
-No LOS was NOT Necessary to boot this or any GSI build
Hopes this can help some of you out....
Click to expand...
Click to collapse
Can you post a complete tutorial for Moto Z2 force to install Android 10 with root access?
Original thread.
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software. *This is not entirely true for Realme devices since bootloader unlock or custom rom flash via TWRP or fastboot does not void your warranty but rooting does.
* So I heard. But that's question of detail.
* Same statement for XDA.
[DETAILED DESCRIPTION]:
I've spent my whole afternoon testing. And found out there are way more well made gsi roms out there and theoretically all of them should work. First, you gotta read this one. Then pick a gsi rom. I recommend one that has everything (must be AB image) since we don't have a working twrp yet thus can't flash opengapps but if the image file contains it then it's good to go. Go there. Pick one. Make sure it has ab-gapps-su in it's name meaning it's A/B partition dependent treble rom. Gapps means it has gapps ofc. Su means it has built in superuser (that you can ignore later for you'll be replacing it with Magisk naturally). After picking a gsi rom image successfully you can download it to your external sd card and flash it via twrp (yes, that half ass twrp for rmq provided on xda) or you can flash it via fastboot flash system system.img. Wiping data, cache, dalvik, system is necessary before doing so. Also formatting data in twrp after flashing the system image helps a lot just as OP said. If you want to try out other gsi roms you must flash stock vendor image file and do the flashing circle again. If you don't flash stock rom or stock vendor img before doing so your new gsi rom won't be able to work with screen lock. At least that's what I got on 4 different gsi roms. And one more thing. These gsi systems doesn't seem to support exfat file system. Meaning they'll want to format your external sd card. This can by bypassed if you flash lineage os boot.img. And then Magisk and at last modified vbmeta.img for RMQ. That file will make realme vendor think nothing is changed and won't try to fck you over with recovery destroyed issue.
[Prerequisites]:
unlocked bootloader
twrp recovery
External SD card
[BUGS]:
Face unlock and fingerprint isn't present on gsi roms which means they cannot work
Screen lock issue in cases when you don't flash stock vendor.img before migrating from one custom rom, be it gsi or zip to system gsi.img
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM OTHER ROM]:
!! Most of these steps are precaution !!
Read these points carefully to have a basic knowledge what you're about to do
Pick a gsi image of your choice (official Android 9 Pie, especially AOSP is highly advised)
Put your image file onto your external SD card for your internal one will likely be erased
You should grab the appropriate vendor.img and boot.img files for your device by decompressing the 7z files
Get the modified vbmeta.img file for spoofing system to boot
Get Magisk
Get SuperSu remover(Beware! It also removes Magisk if installed)
Get Lineage OS boot.img
It's better to be safe than sorry so you better download whole rom package too
Put all these files onto your external SD card
Make sure you have your twrp recovery on your external SD card too
If you done everything well you should have these on your external SD: twrp, desired system gsi.img as AB variant, your vendor.img, modified vbmeta.img, stock boot.img, Lineage OS boot.img, color os flashable.ozip/zip, Magisk, SuperSu remover
Wipe system, data, dalvik, cache
Flash stock vendor.img as vendor
Flash system gsi.img as system
Flash lineage os boot.img as boot
Flash twrp.img as recovery
Flash modified vbmeta.img as vbmeta
Reboot to system (if the device reboots into recovery you'll have to format data sadly)
After reboot successful and you've done the initial google setup steps reboot to recovery and flash superuser unroot
Flash Magsik
Reboot, now you should have a working aosp like system as I do
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM COLOR OS]:
!! You could have the same files as above just to make sure but system gsi.img,vbmeta.img,SuperSu remover,Magisk and Lineage OS boot.img should be enough if everything goes as planned and system boots for first try !!
Read the frequently asked questions, step one previously
Get your desired system gsi.img
Put your system gsi.img, twrp.img, Magisk, SuperSu remover, vbmeta.img, Lineage OS boot.img onto your external SD card
Wipe data, system, cache, dalvik
Flash system gsi.img as system
Flash lineage os boot.img
Flash twrp.img as recovery
Flash vbmeta.img ad vbmeta
Reboot (if reboots to recovery you have to format data) then do the Android setup
Reboot to recovery
Flash SuperSu remover.zip
Flash Magisk.zip
Reboot
Now your device should have successfully booted up
In case the gsi rom would be stuck on boot logo then you may reboot back to recovery by holding down volume up + power button and flash permissiver_v5.zip. It helped me boot Pixel Experience gsi rom.
Update.:
As you already know development on realme devices suck beacuse of ****ty or incomplete sources, lack of developers interest and biggest reason is lack of community support.
Our man here @BabluS is a legendary developer of Asus Zenfone Max M1 Pro and is willing to compile stable ROMs for our device. But, he needs some donations to buy the device. He has already compiled Android 10 (PE) for our device which is 99% stable. To continue this tremendous work he needs to have the device in hand.
Reasons To Donate:
1. Official PixelExperience ROM
2. Official POSP ROM
3. Will maintain & provide public Device Trees/Sources (So anyone can compile ROMs)
4. More development for realme 5 Pro
Name : Baswanth Madhav Saladi
Donate Using UPI: [email protected]
Donate using Paypal : [email protected]
Send screenshots of payment to @orgasmtron
We have to reach 6-7k in total out of which we have collected 2.6k..
Keep donating & get closer to stable custom ROM experience. Kudos!
All the donations will be public.Anyone can view and verify them.All details will be transparent.
NOTE:
We will update money collection daily evening. All details will be transparent.
List of Donators will get updated here
CLICK HERE TO CHECK!
Has anybody got Android 10 working properly?
tonibm19 said:
Has anybody got Android 10 working properly?
Click to expand...
Click to collapse
Yes. Method is same.
greenys' said:
Yes. Method is same.
Click to expand...
Click to collapse
Yeah but I mean, everything is working fine?
Fingerprint? Camera?
tonibm19 said:
Yeah but I mean, everything is working fine?
Fingerprint? Camera?
Click to expand...
Click to collapse
Dunno. As I said I never tried Android Q. But I presume fingerprint is missing and I'm quite sure no 48mp camera is present either.
What GSI File for Realme 5 Pro
what type GSI Image for Realme 5 pro, A or AB type?
Tegarcs142 said:
what type GSI Image for Realme 5 pro, A or AB type?
Click to expand...
Click to collapse
AB. On Android 9 and above you must use AB variant. It doesn't matter whether or not does your device use seamless updates. If you try to flash A only variant your device won't boot.
I installed GSI resurrection remix on my Realme 5 Pro and when I trying install Gapps get error not enough system partition. So I use resize file system in twrp and it worked.
Tegarcs142 said:
I installed GSI resurrection remix on my Realme 5 Pro and when I trying install Gapps get error not enough system partition. So I use resize file system in twrp and it worked.
Click to expand...
Click to collapse
Nice. Which twrp did you use?
greenys' said:
Nice. Which twrp did you use?
Click to expand...
Click to collapse
3.3.1-0
Tegarcs142 said:
... So I use resize file system in twrp and it worked.
Click to expand...
Click to collapse
Hi, can you please tell me what option you clicked for resizing the system partition?
the steps you did.
I tried doing that but don't find the option in TWRP.
For better experience with using gsi make sure to check Screenshot resolution if it's lower than our Device
Change Resolution :
1) download termux app
https://play.google.com/store/apps/d...?id=com.termux
2) run commands:
su
wm size 1080x2340
3) reboot*device
Enjoy better experience with gsi
greenys' said:
Original thread.
[DETAILED DESCRIPTION]:
I've spent my whole afternoon testing. And found out there are way more well made gsi roms out there and theoretically all of them should work. First, you gotta read this one. Then pick a gsi rom. I recommend one that has everything (must be AB image) since we don't have a working twrp yet thus can't flash opengapps but if the image file contains it then it's good to go. Go there. Pick one. Make sure it has ab-gapps-su in it's name meaning it's A/B partition dependent treble rom. Gapps means it has gapps ofc. Su means it has built in superuser (that you can ignore later for you'll be replacing it with Magisk naturally). After picking a gsi rom image successfully you can download it to your external sd card and flash it via twrp (yes, that half ass twrp for rmq provided on xda) or you can flash it via fastboot flash system system.img. Wiping data, cache, dalvik, system is necessary before doing so. Also formatting data in twrp after flashing the system image helps a lot just as OP said. If you want to try out other gsi roms you must flash stock vendor image file and do the flashing circle again. If you don't flash stock rom or stock vendor img before doing so your new gsi rom won't be able to work with screen lock. At least that's what I got on 4 different gsi roms. And one more thing. These gsi systems doesn't seem to support exfat file system. Meaning they'll want to format your external sd card. This can by bypassed if you flash lineage os boot.img. And then Magisk and at last modified vbmeta.img for RMQ. That file will make realme vendor think nothing is changed and won't try to fck you over with recovery destroyed issue.
[Prerequisites]:
unlocked bootloader
twrp recovery
External SD card
[BUGS]:
Face unlock and fingerprint isn't present on gsi roms which means they cannot work
Screen lock issue in cases when you don't flash stock vendor.img before migrating from one custom rom, be it gsi or zip to system gsi.img
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM OTHER ROM]:
!! Most of these steps are precaution !!
Read these points carefully to have a basic knowledge what you're about to do
Pick a gsi image of your choice (official Android 9 Pie, especially AOSP is highly advised)
Put your image file onto your external SD card for your internal one will likely be erased
You should grab the appropriate vendor.img and boot.img files for your device by decompressing the 7z files
Get the modified vbmeta.img file for spoofing system to boot
Get Magisk
Get SuperSu remover(Beware! It also removes Magisk if installed)
Get Lineage OS boot.img
It's better to be safe than sorry so you better download whole rom package too
Put all these files onto your external SD card
Make sure you have your twrp recovery on your external SD card too
If you done everything well you should have these on your external SD: twrp, desired system gsi.img as AB variant, your vendor.img, modified vbmeta.img, stock boot.img, Lineage OS boot.img, color os flashable.ozip/zip, Magisk, SuperSu remover
Wipe system, data, dalvik, cache
Flash stock vendor.img as vendor
Flash system gsi.img as system
Flash lineage os boot.img as boot
Flash twrp.img as recovery
Flash modified vbmeta.img as vbmeta
Reboot to system (if the device reboots into recovery you'll have to format data sadly)
After reboot successful and you've done the initial google setup steps reboot to recovery and flash superuser unroot
Flash Magsik
Reboot, now you should have a working aosp like system as I do
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM COLOR OS]:
!! You could have the same files as above just to make sure but system gsi.img,vbmeta.img,SuperSu remover,Magisk and Lineage OS boot.img should be enough if everything goes as planned and system boots for first try !!
Read the frequently asked questions, step one previously
Get your desired system gsi.img
Put your system gsi.img, twrp.img, Magisk, SuperSu remover, vbmeta.img, Lineage OS boot.img onto your external SD card
Wipe data, system, cache, dalvik
Flash system gsi.img as system
Flash lineage os boot.img
Flash twrp.img as recovery
Flash vbmeta.img ad vbmeta
Reboot (if reboots to recovery you have to format data) then do the Android setup
Reboot to recovery
Flash SuperSu remover.zip
Flash Magisk.zip
Reboot
Now your device should have successfully booted up
In case the gsi rom would be stuck on boot logo then you may reboot back to recovery by holding down volume up + power button and flash permissiver_v5.zip. It helped me boot Pixel Experience gsi rom.
Click to expand...
Click to collapse
Hi
I wanna install fortnite on RMQ
Through epic games I should register a realme account (but I can do that only with a Chinese phone number which I don't have )
Any solution pls
Tarikooo said:
Hi
I wanna install fortnite on RMQ
Through epic games I should register a realme account (but I can do that only with a Chinese phone number which I don't have )
Any solution pls
Click to expand...
Click to collapse
Wth no. Idk. It's not even a gsi related thing. I have no idea sorry.
hi guys i tried flashing havoc 3.0 gsi, and it works great. which one gapps should i use?
Does fingerprint and face unlock work?
This method worked on global rm5p.
I tried to flash the GSI Miui Erfan, but when entered in the initial settings, the screen cannot be touched.
Salmankapuas said:
I tried to flash the GSI Miui Erfan, but when entered in the initial settings, the screen cannot be touched.
Click to expand...
Click to collapse
Don't bother with miui. Only aosp or caf.
i flashed GSI rom, pixel, OxygenOS but the system cannot boot, only stuck on boot loading screen, is that normal?? how do i fix it?
Hi everyone!
I've been testing installing Lineage 17.1 custom ROMs on merlin, here are the steps I followed plus a LOS 17.1.
I found out that this ROM works better than MIUI and its very stable as a daily driver.
Tested on Redmi Note 9 Global (merlin) - CPU (Helio G85) - ROM/RAM: 64GB/3GB, initialy flashed over MIUI 12.0.3 Global
This are the steps I followed:
Unlock bootloader (of course)
Backup all sensitive data (it maybe lost if things go wrong)
For you in case things go wrong, also download the exact fastboot rom of the MIUI version you are using from xiaomifirmwareupdater.com (it has to be fastboot ROM becouse it contains stock recovery)
Flash a TWRP with new MIUI kernel support
Download TWRP build by wzsx15, for example
Download a modifed vbmeta.img, like the one provided in this thread
Flash like this:
Bash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash recovery recovery.img
Test TWRP, at least verify it can mount and read /data.
Wipe data, cache and dalvik
Flash LOS 17.1 for merlin (details below), or anything you want to test
Details about provided LOS 17.1:
LineageOS 17.1 - UNOFFICIAL | A10.
Released : 11/02/'21
By @CosmoFreak001 & @chcepizze
SElinux permissive
Changelog:
• Fixed VoLTE
• Fixed Brightness bug
• Fixed all major bugs
• Fixed Double tap to wake
• Fixed Offline Charging
Download
Source (build using generic kernel for Mediatek Helio G85)
Works at least over:
MIUI 12.0.4 Global and less
MIUI 12.0.1 Indonesia and less
--------------
⚠WARNING⚠
MIUI 12.0.5 Global (and 12.0.2 Indonesia) and any higher version, would probably need a downgrade.
--------------
In case things go wrong:
TWRP dosen't work correctly and now my system can't boot
Restore stock recovery, vbmeta and boot partition
Go to fastboot
Extract recovery.img file from your stock fastboot ROM and flash it like this
Code:
fastboot flash recovery recovery.img
Reboot, if system dosen't boot, go to next step
Extract vbmeta.img file from stock fastboot ROM and flash it like this
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Reboot, if it can't boot, go to next step
Extract boot.img file from your stock fastboot ROM and flash all (recovery, vbmeta and boot partition) it like this
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
TWRP ask's me for a passoword
It's the first PIN number of the lockscreen you set when you first run the system
My PIN doesn't work or my phone never had a PIN and still asks me for one
Maybe /data is not accesible (TWRP compatibility problem)
Try mounting /system and /vendor partition
Navigate through them and verify you can see files and folder
If TWRP is unable to mount any partition restore stock recovery partition
If TWRP can see and mount partitions other than /data:
You can format /data (you are losing ALL data including internal storage)
I don't wont to lose all my data!
Restore stock recovery
Good work, Please note that the rom does not boot on every vendor version, So include the list of the vendors working for rom, As far as I know, it has booted successfully on MIUI 12.0.3 Global and 12.0.1 Indonesia.
Communos said:
Good work, Please note that the rom does not boot on every vendor version, So include the list of the vendors working for rom, As far as I know, it has booted successfully on MIUI 12.0.3 Global and 12.0.1 Indonesia.
Click to expand...
Click to collapse
Thanks. You are right I will add those comments.
thanks for this
Hello members after a long daunting minutes ,hours and days asking for the procedures in this forum on how i can install the custom rom on the Redmi note 9 Merlin MT 6768 3GB Ram ,64GB Rom Global version MiUI 12.0.3.0 i have managed to to install the 17.1 lineage through some experiences, First thanks to the two members who have been of help namely SparXFusion and Ma269 after i have read their post on this forum. Here is what i did i was on MIUI v11.0.4.0 which i later updated to 12.0.3.0 for this to work . Below is the procedure which i have been following and i discovered that the TWRP files i downloaded works fine from v 11.0.4 to 12.0.4.0 PROCEDURE
1- Download the TWRP file from this site : https://mega.nz/file/SuZn2QqZ#jJ6xRku...
2- Download the ADB file from this site : https://androidmtk.com/download-minim..
3- Below command prompts
fastboot devices
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot flash misc misc.bin
fastboot boot recovery.img
Once boot in TWRP open Wipe/format then type yes. Then go to install to get the 17.1 lineage custom rom from internal or external storage if it was downloaded there . Then fine you are good to go
All in all i have noticed that to set the email its not working may the experts explain my observation.
Waiting to hear from some members the solution
One other question is where to get the Gapps for this rom 17.1 lineage merlin mt 6768
gruka said:
Hello members after a long daunting minutes ,hours and days asking for the procedures in this forum on how i can install the custom rom on the Redmi note 9 Merlin MT 6768 3GB Ram ,64GB Rom Global version MiUI 12.0.3.0 i have managed to to install the 17.1 lineage through some experiences, First thanks to the two members who have been of help namely SparXFusion and Ma269 after i have read their post on this forum. Here is what i did i was on MIUI v11.0.4.0 which i later updated to 12.0.3.0 for this to work . Below is the procedure which i have been following and i discovered that the TWRP files i downloaded works fine from v 11.0.4 to 12.0.4.0 PROCEDURE
1- Download the TWRP file from this site : https://mega.nz/file/SuZn2QqZ#jJ6xRku...
2- Download the ADB file from this site : https://androidmtk.com/download-minim..
3- Below command prompts
fastboot devices
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot flash misc misc.bin
fastboot boot recovery.img
Once boot in TWRP open Wipe/format then type yes. Then go to install to get the 17.1 lineage custom rom from internal or external storage if it was downloaded there . Then fine you are good to go
All in all i have noticed that to set the email its not working may the experts explain my observation.
Waiting to hear from some memmbers the solution
Click to expand...
Click to collapse
Misc.bin isn't necessary for flashing twrp,
And what do you mean by "that to set the email it's not working"?
when you put your email on the email app you never log in , and one other question is which is the best gapps for this rom 17,1 lineage merlin
gruka said:
when you put your email on the email app you never log in , and one other question is which is the best gapps for this rom 17,1 lineage merlin
Click to expand...
Click to collapse
Pico Open Gappa or flame Gapps basic, both are fine.
And it's the stock email app, I never used it, so I don't know about that.
Redmi Note 8, I've successfully installed TWRP, then without taking backup attempted to wipe everything (including vendor & system).
Wiping of data failed.
Tried installing Pixel OS (non Plus version using ADB side loading), the OS started with the Google logo then it rebooted to TWRP.
Then I formatted data using Ext2 then using Ext4 then tried to wipe everything again and it worked (wiping everything system, data and vendor).
Tried installing Pixel OS again, but this time not even the Google logo appeared, just Redmi and then it reboots to TWRP.
I tried installing Pixel OS Plus, same.
I tried installing stock Mi ROM Global, this time it is stuck on the MIUI logo without doing anything, I have to reboot into recovery manually.
Tried Potato OS, same, stuck on startup potato logo.
crDroid, same, stuck on startup logo.
Now the only thing working on this piece of metal is TWRP, what to do?
Here are the logs from TWRP (compressed in 7z format): https://drive.google.com/file/d/1sfgYId00k-VRpzQ5VVC2mpP0rBRP1StB/view?usp=sharing
Oh, and one more thing, even though now TWRP doesn't show red error lines and writes successful after OS installation, there is only one line that bothers me on the screen saying: init_user0_failed, but it's not in red.
asaeles said:
Redmi Note 8, I've successfully installed TWRP, then without taking backup attempted to wipe everything (including vendor & system).
Wiping of data failed.
Tried installing Pixel OS (non Plus version using ADB side loading), the OS started with the Google logo then it rebooted to TWRP.
Then I formatted data using Ext2 then using Ext4 then tried to wipe everything again and it worked (wiping everything system, data and vendor).
Tried installing Pixel OS again, but this time not even the Google logo appeared, just Redmi and then it reboots to TWRP.
I tried installing Pixel OS Plus, same.
I tried installing stock Mi ROM Global, this time it is stuck on the MIUI logo without doing anything, I have to reboot into recovery manually.
Tried Potato OS, same, stuck on startup potato logo.
crDroid, same, stuck on startup logo.
Now the only thing working on this piece of metal is TWRP, what to do?
Here are the logs from TWRP (compressed in 7z format): https://drive.google.com/file/d/1sfgYId00k-VRpzQ5VVC2mpP0rBRP1StB/view?usp=sharing
Oh, and one more thing, even though now TWRP doesn't show red error lines and writes successful after OS installation, there is only one line that bothers me on the screen saying: init_user0_failed, but it's not in red.
Click to expand...
Click to collapse
flash vbmeta :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
you can find vbmeta in any A10 rom
reboot to recovery and flash latest stable OrangeFox as a normal zip
it will reboot to recovery
do a clean flash with your prefered rom
(you can find DFE here)
loopypalm said:
flash vbmeta :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
you can find vbmeta in any A10 rom
reboot to recovery and flash latest stable OrangeFox as a normal zip
it will reboot to recovery
do a clean flash with your prefered rom
(you can find DFE here)
Click to expand...
Click to collapse
Ok, I've downloaded an unofficial PixelOS for Samsung Galaxy A10, but inside the ZIP file I can't find something called vbmeta, where can I find it? Also if you have a specific A10 ROM in mind, please indicate.
loopypalm said:
flash vbmeta :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
you can find vbmeta in any A10 rom
reboot to recovery and flash latest stable OrangeFox as a normal zip
it will reboot to recovery
do a clean flash with your prefered rom
(you can find DFE here)
Click to expand...
Click to collapse
Also why A10 specifically? I mean this is a Xiaomi device after all, so is this vbmeta thing generic? Same across all devices?
loopypalm said:
flash vbmeta :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
you can find vbmeta in any A10 rom
reboot to recovery and flash latest stable OrangeFox as a normal zip
it will reboot to recovery
do a clean flash with your prefered rom
(you can find DFE here)
Click to expand...
Click to collapse
It worked
loopypalm said:
flash vbmeta :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
you can find vbmeta in any A10 rom
reboot to recovery and flash latest stable OrangeFox as a normal zip
it will reboot to recovery
do a clean flash with your prefered rom
(you can find DFE here)
Click to expand...
Click to collapse
Now Pixel Experience is working, but up till now I have two major issues:
1) SIM card is not working (it's saying network disconnected)
2) This mobile is for my kid and Google Family Link for children was working fine and now it is saying "Can't set up supervision on this device", so the issue is not with my son's google account it's now with the device itself.
Does Google sense rooting? Is Pixel OS rooted out of the box?
I mean my daughter has the same model and I unlocked OEM installation and flashed TWRP and Google Family link is working
asaeles said:
Now Pixel Experience is working, but up till now I have two major issues:
1) SIM card is not working (it's saying network disconnected)
2) This mobile is for my kid and Google Family Link for children was working fine and now it is saying "Can't set up supervision on this device", so the issue is not with my son's google account it's now with the device itself.
Does Google sense rooting? Is Pixel OS rooted out of the box?
I mean my daughter has the same model and I unlocked OEM installation and flashed TWRP and Google Family link is working
Click to expand...
Click to collapse
try another rom (the rom i suggest is RRos)
and see if the sim network is connected (if not, it might be a sensor problem)
about google things = i don't know, i hate google ...
Connectivity problems lead me to suspect it could be a firmware issue: either start from the beginning by going back to stock with MiFlash or try changing the firmware (see https://xiaomifirmwareupdater.com/firmware/ginkgo/).
loopypalm said:
try another rom (the rom i suggest is RRos)
and see if the sim network is connected (if not, it might be a sensor problem)
about google things = i don't know, i hate google ...
Click to expand...
Click to collapse
Thanks, here's a gift ;-) https://i.pinimg.com/originals/74/c0/e5/74c0e55d1fe725793e18758dcef11f72.png
Hello everybody,
I have phone Xiaomi Redmi Note 8 (2021)
I have succesfuly unlocked bootloader. I wish to use GSI installed via DSU Loader and i managed to boot default GSI room offered by system this way.
Also i have used app "DSU Sideloader" and succesfuly managed to boot lineageOS GSI.
The issue is when i root the phone. (classic boot.img extraction from stock rom, modification of the boot.img within Magisk aplication, than flash modified boot.img via adb tools)
After flashing modified boot.img i can no longer boot GSI, boot process will stop on MIUI screen. Stock ROM is working fine (rooted or not rooted)
When i flash original boot.img everything is working fine but phone is not rooted.
Is there any fix for this problem? I wish to have phone rooted AND use GSI
After countless hours of searching over internet i have not found topic related to this specific issue.
Also I have tried
fastboot flash --disable-verity --disable-verification boot boot.img
and modified vbmeta.img
fastboot --disable-verification flash vbmeta vbmeta.img
no difference
But i have no idea what is holding back boot.... any help would be much appreciated
GSI related info:
Treble and VNDK - device supported
Architecture ARM64
A/B operating system
Dynamic Partitions
Talking about working GSI is there anybody which managed to install GAPPS on GSI installed via DSU? Is that even possible? how without twrp recovery?
i know that GSIs with preinstalled gapps exists i just want modular approach and install just google apps which i use.
I have found that resizing GSI system partition could help flash gapps via Ex Kernel Manager directly from the phone.
My big question is if you can resize GSI system partition without TWRP? since Note 2021 does not support recovery, if yes how?
Or can you actually set bigger system partition than system image with this command ? --el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
(following manual steps for gsi installation)
adb shell setprop persist.sys.fflag.override.settings_dynamic_system true
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
what would be number for 20GB size in this command? --el KEY_USERDATA_SIZE 8589934592 how i can write it correctly?
i have enough space to assign big userdata partition.
CyraxMD said:
Is there any fix for this problem? I wish to have phone rooted AND use GSI
Click to expand...
Click to collapse
I wish to have at least a working GSI installed lol.. how did u manage to boot into fastbootd ?
fastboot reboot fastboot reboots into normal fastboot/bootloader on my linux machine..
vegan_monk said:
I wish to have at least a working GSI installed lol.. how did u manage to boot into fastbootd ?
fastboot reboot fastboot reboots into normal fastboot/bootloader on my linux machine..
Click to expand...
Click to collapse
was not neccessary, check this guide which i maked how to do it:
CyraxMD said:
was not neccessary, check this guide which i maked how to do it:
Click to expand...
Click to collapse
Nice work man. Surely makes life easier for many, but in my case:
I followed all of the steps. After the GSI installation i tapped on reboot on the notification field and it rebooted into fastboot. I can not enter the GSI aswell as the recovery. Only fastboot and MIUI ROM
I installed MIUI13 from official sources via ./flash_all.sh inside the MIUI13 Recovery folder some days ago. I've done this because i think i soft bricked my device or messed with the partitions before, because i tried to flash a system image directly to the 'super' partition, becasue no fastbootd.
vegan_monk said:
Nice work man. Surely makes life easier for many, but in my case:
I followed all of the steps. After the GSI installation i tapped on reboot on the notification field and it rebooted into fastboot. I can not enter the GSI aswell as the recovery. Only fastboot and MIUI ROM
I installed MIUI13 from official sources via ./flash_all.sh inside the MIUI13 Recovery folder some days ago. I've done this because i think i soft bricked my device or messed with the partitions before, because i tried to flash a system image directly to the 'super' partition, becasue no fastbootd.
Click to expand...
Click to collapse
thx mate,
asuming you are trying to do this on Note 8 2021
ensure that you have your bootloader unlocked and your original rom is NOT rooted. You can also before you do anything with GSI custom releases test official GSI which should be available to you via DSU (connect phone via wifi not data services)
Recovery is not supported for Note 8 2021 thats why i havent mess with it despite i would love to have it. Also in my case - recovery was not needed to load unofficial GSI (just pc with adb drivers and sdk platform tools latest version).
fastbootd is not required in this case either
in some cases modified vbmeta.img is required to make it work.
if you somehow soft-bricked your device try https://www.xiaomitool.com/V2/ that should help you recover back to normal state.
CyraxMD said:
thx mate,
asuming you are trying to do this on Note 8 2021
ensure that you have your bootloader unlocked and your original rom is NOT rooted. You can also before you do anything with GSI custom releases test official GSI which should be available to you via DSU (connect phone via wifi not data services)
Recovery is not supported for Note 8 2021 thats why i havent mess with it despite i would love to have it. Also in my case - recovery was not needed to load unofficial GSI (just pc with adb drivers and sdk platform tools latest version).
fastbootd is not required in this case either
in some cases modified vbmeta.img is required to make it work.
if you somehow soft-bricked your device try https://www.xiaomitool.com/V2/ that should help you recover back to normal state.
Click to expand...
Click to collapse
many thanks for your reply mate,
i managed to flash miui12.5 again with flah_all.sh with official sources fastboot ROM via terminal. now i have recovery again. my computer has the latest adb tools installed.
i tried your dsu loader method on miui12.5 again but sadly it says "installation failed". on miui13 it said "installation success" but could not boot into it. I'm a little bit confused rn lol. i tried the phh's AOSP arm64 AB vanilla and phh's AOSP arm64 AB VNDKlite vanilla
and yes, i have the 2021 biloba version of the note 8
vegan_monk said:
many thanks for your reply mate,
i managed to flash miui12.5 again with flah_all.sh with official sources fastboot ROM via terminal. now i have recovery again. my computer has the latest adb tools installed.
i tried your dsu loader method on miui12.5 again but sadly it says "installation failed". on miui13 it said "installation success" but could not boot into it. I'm a little bit confused rn lol. i tried the phh's AOSP arm64 AB vanilla and phh's AOSP arm64 AB VNDKlite vanilla
and yes, i have the 2021 biloba version of the note 8
Click to expand...
Click to collapse
hmm you said you have recovery? do you mean twrp or cwm? if thats the case i want it too
CyraxMD said:
hmm you said you have recovery? do you mean twrp or cwm? if thats the case i want it too
Click to expand...
Click to collapse
sorry to disappoint u mate but its just the miui recovery
GSI has better performance than MIUI? Could you tell the pros and cons that you have found?
CyraxMD said:
Hello everybody,
I have phone Xiaomi Redmi Note 8 (2021)
I have succesfuly unlocked bootloader. I wish to use GSI installed via DSU Loader and i managed to boot default GSI room offered by system this way.
Also i have used app "DSU Sideloader" and succesfuly managed to boot lineageOS GSI.
The issue is when i root the phone. (classic boot.img extraction from stock rom, modification of the boot.img within Magisk aplication, than flash modified boot.img via adb tools)
After flashing modified boot.img i can no longer boot GSI, boot process will stop on MIUI screen. Stock ROM is working fine (rooted or not rooted)
When i flash original boot.img everything is working fine but phone is not rooted.
Is there any fix for this problem? I wish to have phone rooted AND use GSI
After countless hours of searching over internet i have not found topic related to this specific issue.
Also I have tried
fastboot flash --disable-verity --disable-verification boot boot.img
and modified vbmeta.img
fastboot --disable-verification flash vbmeta vbmeta.img
no difference
But i have no idea what is holding back boot.... any help would be much appreciated
GSI related info:
Treble and VNDK - device supported
Architecture ARM64
A/B operating system
Dynamic Partitions
Talking about working GSI is there anybody which managed to install GAPPS on GSI installed via DSU? Is that even possible? how without twrp recovery?
i know that GSIs with preinstalled gapps exists i just want modular approach and install just google apps which i use.
Click to expand...
Click to collapse
After seeing your video I understand that you was able to fix your initial problem:
"The issue is when i root the phone. (classic boot.img extraction from stock rom, modification of the boot.img within Magisk aplication, than flash modified boot.img via adb tools)
After flashing modified boot.img i can no longer boot GSI, boot process will stop on MIUI screen. Stock ROM is working fine (rooted or not rooted)
When i flash original boot.img everything is working fine but phone is not rooted."
It seem that you have been able to fix that problem, havent you? Have you had any problem using rooted GSI lineage? I am very insterested in rooting my phone using a GSI rom. I am going to follow your tutorial.
thanks