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,
I am "building" (first had to fix the LCD etc.) a de-googled DAISY. I managed to unlock the bootloader, install TWRP, and root the original OS (Android One 10).
The problems started when I tried to install a custom ROM (at first Havoc, but other gave the same results). Just as instructed (YT, other pages, here...) I:
- formatted via TWRP
- REBOOT to TWRP
- wipe all except SD
- install ROM from zip
...and at this point I came across an error message
Error applying update: 7 (Error code: : kInstallDeviceOpenError)
Updater process ended with ERROR: 1
Many solutions suggest flashing boot.img from the ROM package, but (WHY?!?) all ROM's ((Havos, crDroid etc.) for daisy have no such file, although other devices have boot.img in their package.
I'm pretty much clueless... :/
Help, and thanks in advance...
mothzart said:
Hi,
I am "building" (first had to fix the LCD etc.) a de-googled DAISY. I managed to unlock the bootloader, install TWRP, and root the original OS (Android One 10).
The problems started when I tried to install a custom ROM (at first Havoc, but other gave the same results). Just as instructed (YT, other pages, here...) I:
- formatted via TWRP
- REBOOT to TWRP
- wipe all except SD
- install ROM from zip
...and at this point I came across an error message
Error applying update: 7 (Error code: : kInstallDeviceOpenError)
Updater process ended with ERROR: 1
Many solutions suggest flashing boot.img from the ROM package, but (WHY?!?) all ROM's ((Havos, crDroid etc.) for daisy have no such file, although other devices have boot.img in their package.
I'm pretty much clueless... :/
Help, and thanks in advance...
Click to expand...
Click to collapse
Error 1 usually means wrong install package or wrong TWRP.
Are you using TWRP by offain?
[SOLVED]
The whole problem was that TWRP was wrong (not even offain as far as I remember). But I got a HUUUUGE amount of help (MANY THANX!!!!) from opal06 (main maintainer for crDroid on daisy) on Telegram channel dedicated to crDroid on daisy.
So If anyone hase similar problems - go to Telegram group - they will help you!
After flashing right (modified) TWRP versions, evrthng went fine, although I got to admit it was pretty complicated for [unlock + TWRP + custom rom + root] combo. On lavender it was much easier
cya all, good luck!
I check this in two apps both giving different answers.
Also I saw
andriyhar said:
Thank you.
Flash img ok.
Click to expand...
Click to collapse
He flashed a/b image
I check in the terminal using
getprop ro.build.ab_update
Got false
But when i flash havoc-os a only system it bootloop
So my question is am i suppose to flash a only or ab?
Also if you have used gsi i'd be glad to hear your experience.
Reading this thread
Aonly or A/B
Treble Check tell me Aonly and Treble Info tell me A/B. Which one must I choose?
forum.xda-developers.com
has lead me to believe
That i should flash a/b img
You can actually force A/B by flashing this zip:
MakeMeSAR.zip | by erfanoabdi for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Then it should flash A/B GSIs properly.
Will my recovery support it though.( Orange Fox by bekirakil)
Also I've only got 3.12GB system partition with no way of resizing it as this device has a dynamic partition
Plus the file name is makemesar and I'm sure that my devices is all ready system as root enabled.
This is just for ensuring you have AB, you can ignore it
System partition, hmmm, you can only flash small roms
I can confirm that you are suppose to use a/b img.
I flashed https://download.havoc-os.com/arm64-ab/Havoc-OS-v4.1-20210208-arm64-ab-Official.img.xz.
Unlike A-only img it booted and worked kindof.
I will not recommend this though as there is no way flash gapps for android 11 and not enough space to flash with a/b with gapps.
Also switched backed to lineage as it was causing random reboots.
Any help over making gsi stable will be much appreciated.
This post is meant for another fourm
When I restored the backup it failed but I was able to boot to lineage os which still contain gapps and magisk.
Since it showed failed I clean install everything again. The recovery read something like something something product partition, odm partion, system partiton.
Don't know if these logs are useful but I've attracted them below
Hello.
After I received my new Poco f3, the first I've done was unlocking the bootloader. 7 days later, everything was done and I flashed lineageos.
>Fastboot boot twrp.img>advanced>flash current twrp.
After that I've wiped and format data. Then I flashed lineageos. After that I've tried to flash gapps, but that results in "error 70 Not enough space. I've tried pico and nano package. The question is now, how am I able resize the system partition ? I googled to find solutions but what I've found, just scared the sh*it out of me. Some people experimented with gparted and hardbricked their device, because they destroyed their bootloader.
In twrp>wipe>advanced wipe there is no system partition shown. Dunno why.
I didn't dare to >Fastboot erase system (Or Fastboot format system) before I flash los. Is this safe and could be a possible solution? I also don't understand how this "a/b" partitions Work. My old Poco f1 didn't had those.
would be really grateful for help.
Yeah this phone is really tricky to mod. I rooted mine and for some reason still didn't have write permissions on root folders.
Tried to delete lockscreen keys just for testing purposes and it messed up the phone. After that even twrp restore couldn't fix it. So I flashed the stock firmware via mi flash tool and locked the bootloader for good.
I find that what you get from rooting this phone is just not worth the risk with its tendency to mess things up really bad at the slightest mistakes, especially because the EDL is locked.
It used to be so simple with older phones. But unfortunately google is trying their best to make phones impossible to modify. And they're getting pretty close now.
user0u said:
I rooted mine and for some reason still didn't have write permissions on root folders.
Click to expand...
Click to collapse
I had the same problem. I've read that just flashing magisk.apk in twrp isn't supported well anymore. You have to modify boot.img in magisk app, and then flash the modified boot.img with Fastboot. For me, that solves the problem (see Instructions. To extract the boot.img from rom.zip I used Payload dumper ).
Long story short, I still didn't managed to resize the system partition
I got an other idea! Is it possible to "inject" gapps into the system.img before I flash it ?!
Did you ever figure it out?
According to installation guide by lineageOS, MindTheGapps is the recommended Gapps for android 11
Google apps | LineageOS Wiki
wiki.lineageos.org
Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
if you are gonna download MindTheGapps, then use the arm64 version
Fandroid Tech said:
Did you ever figure it out?
Click to expand...
Click to collapse
No, I just jused arrowos with the integrated gapps package. Maybe I will try the "mindthegapps" version in the next weeks and give feedback
I'm using orange fox recovery, bugged by this error when I flash opengapps after flashing lineage0s 18.1.
Following is what fixed the issue for me.
1. download latest firmware for the device
2. update zip from ofox recovery- with vendor partition mounted.
3. reboot to recovery and then flashed opengapps nano (this time check the flag for unmount vendor)