Related
WelcomeFirst of all make sure You know the Basics which are:
-You need to have a unlocked Bootloader
-You need to have the Orange Fox Recovery installed
-You need to have a Kernel and a Vendor Image
-You need to have a Treble A-Only Generic System Image (GSI)
-(Optional) A actual Magisk Installer zip File
-(Optional) A actual Open GApps Installer zip File
(Just use Google and You will find everything)
Alright. Now to the flashing!
-Make sure You have the needed Basics on Your Device including the Files You want to flash
-Wipe everything including data, caches, system, vendor
-Now flash a Vendor and Kernel Image to Your Device
-(You can download My "Vendor Installer" or)
-Flash a Treble AOSP ROM for Your Device and wipe System again
-Flash the Generic System Image using the Image Install from TWRP
DONE!
If You want to install Root and GApps on Your Device:
-Reboot to the Recovery and wipe Data/Caches again
-Install Magisk and GApps (Nothing else yet)
-Reboot to the System
DONE!
This Thread will be updated from Time to Time with new Vendor Installers and better Instructions. Feel free to talk about GSI ROMs in this Thread. I will keep it moderated as good as i can!
Download Links:
https://sourceforge.net/projects/orangefox/files
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Vendor Installer from Me: https://drive.google.com/drive/folders/1onzbCmoy18WlNDNFpq67z0Bv7QHB1d-b?usp=sharing
Actual Vendor: OMNI with EAS Kernel
Hello, I can not flash this vendor file. The orange fox returns ERROR7
q13017 said:
Hello, I can not flash this vendor file. The orange fox returns ERROR7
Click to expand...
Click to collapse
There is a more actual thread around the Mix 2 Forum. Try to search for it over Google, it provides more actual Vendors if i'm not wrong
Hi all! has someone managed to install and use the Pixel experience GSI image? It's stuck on the google logo loading screen for me, maybe i need another vendor?
Atcastells said:
Hi all! has someone managed to install and use the Pixel experience GSI image? It's stuck on the google logo loading screen for me, maybe i need another vendor?
Click to expand...
Click to collapse
Same issue here - the last working version is from March 2019.
If I put a gsi with a vendor from custom firmware, will my phone die?
Since the Pie update GSIs are not working because of System-as-root partiton But ASUS launched a new update in which GSIs are working.
READ WHOLE THREAD CAREFULLY.
REQUIREMENTS:
Unlocked bootloader (After Unlocking bootloader you will get a Red END OF STATE Warning. Don't Worry Press Power Button on that screen
Decrypted Data
Should be on latest firmware
If You're Using PitchBlack Recovery:
1. Boot into Recovery
2. Click On Advanced > Additional > Special > Setting OTA
3. Uncheck "Disable DM-Verity" Option Here
4. Done, Now You Can Use PitchBlack To Flash GSI on Pie Vendor.
INSTALLATION METHOD:
1. Download Any GSI of A/B type.
2. Download latest magisk manager zip
3. Patch your boot.img with Magisk (Tick on Preserve dm-verity by clicking on Advanced settins in magisk) or Download from Here
4. Boot into Recovery and Wipe Data, Dalvik Cache. Do not wipe system
5. Flash patched boot.img
Note: If your data is Encrypted then This step should be done with pitchblack otherwise your data may remain encrypted
6. Flash GSI image
7. Flash latest Magisk.
8. Go to Wipe option > Select Advanced Wipe > Tick on system > Click on Repair or Resize > Click on Resize.
9. Optional : Flash Gapps According to your choice If Gapps are not included in GSI.
10. Reboot System.
There is a possibility That your device will reboot again after asus logo. Don't worry
HIT THANKS IF I HELPED YOU:good:
do you see the red state warning after booting into gsi
sir iam unable to flash gapps after flashing the gsi. TWRP says the gapps variant is incompatible. I tried to flash arm 64 pico for pie. The gsi though boots. I flashed RR pie gsi (A/B) with pie vendor.. Please help Thanks in advance
jeno33 said:
sir iam unable to flash gapps after flashing the gsi. TWRP says the gapps variant is incompatible. I tried to flash arm 64 pico for pie. The gsi though boots. I flashed RR pie gsi (A/B) with pie vendor.. Please help Thanks in advance
Click to expand...
Click to collapse
Sorry I didn't mentioned in guide, that you've to modify script of gapps to get it working. I'll upload modified gapps tomorrow. Again I apologize
jeno33 said:
do you see the red state warning after booting into gsi
Click to expand...
Click to collapse
Red state warning is due to unlocked bootloader. It'll remain as long as bootloader is unlocked. But that doesn't create any problem except for increasing boot time by 5-6 seconds.
use A/B type cannot flash gapps,error 64. A type can flash gapps. Why?
gxfuzion92 said:
use A/B type cannot flash gapps,error 64. A type can flash gapps. Why?
Click to expand...
Click to collapse
Updater-script needs to be modified inside gapps, because gapps wrongly detects architecture as arm.
Install this gappshttps://drive.google.com/file/d/1nS2z4emxHovZ0x3CqXl59r8oBqx9DiPU/view?usp=drivesdk
I have modified the script
what rums for example are loaded and working?
currently the Havoc-OS-v2.0-20181027-GSI-ARM64-Aonly-Official is being loaded and running.
tried miui, flyme, Havoc-OS other versions
Is there any video tutorial?
Any tutorial videos?
gxfuzion92 said:
use A/B type cannot flash gapps,error 64. A type can flash gapps. Why?
Click to expand...
Click to collapse
Hey you able to flash any GSI except havoc 2.0 ??
I'm not able to access your document
Guys I successfully installed HAVOC-OS located https://forum.xda-developers.com/project-treble/trebleenabled-device-development/gsi-havoc-os-t3930030. The steps I followed are mentioned below
1. Wipe everything except internal storage.
2. Flashed BRK3 Vendor https://mega.nz/#F!wFFQUYbI!GZvNOBSn1wVn8U9mQDzBiw!IQsjlYzA
2. Installed Endurance GSI kernel https://forum.xda-developers.com/galaxy-s9/samsung-galaxy-s9--s9-cross-device-development/kernel-endurance-kernel-v1-0-t3849434
3. Flashed the system image for ARM 64 A only
4. Boot system
5. Reboot to recovery and Flashed Mgisk
6. Gapps will fail to install at first. Just goto wipe -> Adv wipe -> system partition -> Resize. Reboot to recovery and flash Gapps
7. Reboot and enjoy
8. You can test other GSI Roms also and report. The thread is located at https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Thanks buddy. I was looking for the ways to run the GSI. And the method works. Good job
thanks for the guide! im still on an unrooted s9, but if everything works ill definetly make the jump. Can you tell us more about stability, bugs and if there are things not working
So after testing the ROM for 2 days I can say that
1. It is very stable and can be used as a daily driver
2. Everything works, I am not sure about Bluetooth audio though, haven't checked it
3. It can be heavily customized. Unlike LOS, where we have only few of these features available
4. Battery life is the best I got using any other ROM out there (check the screens below). and I am the guy who gets 3 hrs of SOT, when others claimed 5+ hrs on the same ROM.
5. Security patch is latest even as compared to the TW ROMs
6. Regarding camera... Its the same as LOS pie. Use gcam by idan 3.5 fixed and you are good to go.
fingerprint working?
andreMusers said:
fingerprint working?
Click to expand...
Click to collapse
Yes it is
Thanks for trying this out. I'm only a few months in with my exynos S9 on android pie, so I haven't yet learned the details about rooting/recovery for this phone.
I'll wait for your next update regarding daily use, and would love a more detailed step-by-step for installation if that's not too much trouble. I'm honestly loving those screenshots.
How about IMEI, BRK3 Vendor safe..?
Ok here is the detailed tutorial on how to install a GSI rom
1. First you need to wipe everything in TWRP. Just like you do, when you clean flash any rom
2. Than install the BRK3 vendor. Link is provided by the OP. It's a flashable zip file so just flash it like any other zip.
3. Flash the Endurance GSI kernel. Link is in the OP.
4. Next, download the GSI rom from the link in the OP. Remember to download the ARM 64 A-only variant.
5. Extract the files and you should get a . Img file. Copy that in the SD card
6. In the TWRP, goto install. Select flash image from the bottom right corner of your screen. Now browse the image file, that you copied and choose system image and install.
7. Boot to the system and than boot back to the recovery.
8. Now flash the magisk
9. If you try to install gapps, it will give an error regarding space. So just goto wipe -> advance wipe > system repartition > resize
After resize, you will be able to install gapps.
Flash gapps, automatic brightness fix ( link in the rom thread), AOD fix ( link in the rom thread) and reboot.
burninitup said:
Ok here is the detailed tutorial on how to install a GSI rom
1. First you need to wipe everything in TWRP. Just like you do, when you clean flash any rom
2. Than install the BRK3 vendor. Link is provided by the OP. It's a flashable zip file so just flash it like any other zip.
3. Flash the Endurance GSI kernel. Link is in the OP.
4. Next, download the GSI rom from the link in the OP. Remember to download the ARM 64 A-only variant.
5. Extract the files and you should get a . Img file. Copy that in the SD card
6. In the TWRP, goto install. Select flash image from the bottom right corner of your screen. Now browse the image file, that you copied and choose system image and install.
7. Boot to the system and than boot back to the recovery.
8. Now flash the magisk
9. If you try to install gapps, it will give an error regarding space. So just goto wipe -> advance wipe > system repartition > resize
After resize, you will be able to install gapps.
Flash gapps, automatic brightness fix ( link in the rom thread), AOD fix ( link in the rom thread) and reboot.
Click to expand...
Click to collapse
Thanks for the extra instruction man, will test this out soon.
burninitup said:
Ok here is the detailed tutorial on how to install a GSI rom
1. First you need to wipe everything in TWRP. Just like you do, when you clean flash any rom
2. Than install the BRK3 vendor. Link is provided by the OP. It's a flashable zip file so just flash it like any other zip.
3. Flash the Endurance GSI kernel. Link is in the OP.
4. Next, download the GSI rom from the link in the OP. Remember to download the ARM 64 A-only variant.
5. Extract the files and you should get a . Img file. Copy that in the SD card
6. In the TWRP, goto install. Select flash image from the bottom right corner of your screen. Now browse the image file, that you copied and choose system image and install.
7. Boot to the system and than boot back to the recovery.
8. Now flash the magisk
9. If you try to install gapps, it will give an error regarding space. So just goto wipe -> advance wipe > system repartition > resize
After resize, you will be able to install gapps.
Flash gapps, automatic brightness fix ( link in the rom thread), AOD fix ( link in the rom thread) and reboot.
Click to expand...
Click to collapse
Doesn't work. Stuck on boot logo, loading forever.
Zwulf said:
Doesn't work. Stuck on boot logo, loading forever.
Click to expand...
Click to collapse
me too dont know any fix
EDIT: Somehow i managed to boot the rom but sim won't get detected
Double tap and AOD - work correctly? On snap it does not work well
My Baseband version is now unknown
I have an SM-G960F and its german
EDIT:I just flashed the latest firmware from soldier and now sim card gets detected
Masterofchicken said:
My Baseband version is now unknown
I have an SM-G960F and its german
EDIT:I just flashed the latest firmware from soldier and now sim card gets detected
Click to expand...
Click to collapse
So camera isn't working ,root is still present with magisk and i couldn't disable it with the adb command so safetynet doesn't pass ,i'll say it's not really usable ?
Has anyone found a fix for getting stuck at the s9 logo?..wanting to move to GSI ROMs
I have tried this,
After flash GSI rom, reboot recovery, reboot system and I have bootloop with the first logo Galaxy S9. Can anybody please help me?
@arunrawat2112
Finally I was able to flash some roms but none of them work properly. Can you please help me?
Hello, I have a Samsung Galaxy A6+ with latest fw installed.
(italian version)
A605FNXXU7CUD4
The phone is totally useless after the update to android 10, it takes AGES to perform any action, even open the Camera or open a Message.
Already tried to wipe everything, hard reset, reinstall fw. Still useless.
Since I’d like to downgrade to Android 9 to have back a useful phone, I tried to install the latest Android 9 fw with Odin.
A605FNXXS5BTB1
But it fails, saying SW REV CHECK FAIL : [aboot] Fused 7 > Binary 5
What can I do?
Is there any chance to downgrade this phone?
Thank you
1. Unlock your bootloader.
2. Flash custom recovery for your device.
3. Go to custom recovery (TWRP) and flash any downloaded custom rom (for your device), GSI or save stock firmware as flashable zip with tool like ClassyKitchen.
4. Flash Magisk or RMM-bypass-v3 in TWRP to protect your bootloader from getting locked again.
Backup your personal data at first, of course.
nqnxev said:
1. Unlock your bootloader.
2. Flash custom recovery for your device.
3. Go to custom recovery (TWRP) and flash any downloaded custom rom (for your device), GSI or save stock firmware as flashable zip with tool like ClassyKitchen.
4. Flash Magisk or RMM-bypass-v3 in TWRP to protect your bootloader from getting locked again.
Backup your personal data at first, of course.
Click to expand...
Click to collapse
Almost done, but I can't find any custom rom available for download. Can someone help? Since wwith twrp I cannot install a stock rom. Thanks in advance.
I managed to flash a so called Ari's rom, but I think the phone is now bricked. It is on bootloop on the first screen of Samsung (with phone name and so on) and with SET WARRANTY BIT : KERNEL at top left. I think it is time to trash it or does someone have any hint? Thanks
Ecto1000 said:
I managed to flash a so called Ari's rom, but I think the phone is now bricked. It is on bootloop on the first screen of Samsung (with phone name and so on) and with SET WARRANTY BIT : KERNEL at top left. I think it is time to trash it or does someone have any hint? Thanks
Click to expand...
Click to collapse
I proposed three different options: custom rom, GSI (generic system image) or conversion stock firmware to flashable form. If there's no good custom rom for A6+, then don't worry - you can still try another options. Try playing with Generic System Images:
1. Flash your current stock firmware as usual in Odin.
2. Unlock bootloader and flash TWRP.
3. Go to TWRP.
4. Wipe partitions cache, dalvik, data, system (don't wipe vendor partition - it's needed).
5. Flash GSI image (recommended will be at first phhusson's AOSP (Android 9 or 10)) as "system image". You always need to choose and download "arm32_binder64" variant of img file.
6. Reboot to your new system.
Second option is to convert stock Android 9 firmware into flashable form.
1. Download ClassyKitchen tool.
2. Import downloaded Android 9 stock firmware (for your phone) into it and save it as flashable zip.
3. Go to TWRP.
4. Wipe cache, dalvik, data, system and vendor.
5. Flash your previously done zip with Android 9 as any other flashable zip in TWRP.
6. Flash Magisk or RMM-state-bypass-v3 in TWRP to prevent your bootloader from getting locked again.
7. Reboot.
I went for the second option, in Classykitchen I loaded the stock android 9 rom and selected
BUILD ZIP ROM (for recovery).
Then installed with TWRP following your wipe indications.
Success.
But when I went to install RMM-state-bypass-v3 I got the error impossile to mount /system.
So I rebooted twrp and before anything I manually mounted SYSTEM in twrp in the dedicated MOUNT menu, and I did everything again from wipe to install.
Is this procedure correct?
Success, success also for RMM-state-bypass-v3.
I rebooted but I'm again stuck in the same loop described in my previous reply.
When I selecr REBOOT in twrp, do I have to flag anything? For example System?
Regarding the first option, if I go there:
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
exactly which file do I have to download among ASSETS of any release?
Thank you very much
Ecto1000 said:
I went for the second option, in Classykitchen I loaded the stock android 9 rom and selected
BUILD ZIP ROM (for recovery).
Then installed with TWRP following your wipe indications.
Success.
But when I went to install RMM-state-bypass-v3 I got the error impossile to mount /system.
So I rebooted twrp and before anything I manually mounted SYSTEM in twrp in the dedicated MOUNT menu, and I did everything again from wipe to install.
Is this procedure correct?
Click to expand...
Click to collapse
Yes, it's correct. If RMM bypass or Magisk.zip was flashed without any errors in TWRP then everything is okay. Just reboot to system in TWRP after that - there is option to reboot directly to system. First boot always can take a bit longer than next boots.
Ecto1000 said:
exactly which file do I have to download among ASSETS of any release
Click to expand...
Click to collapse
You always need to get any "arm32_binder64" (always AB) image. Gapps or vanilla is just your choice. Just get Android 9 or 10 image and flash it as "system image" (but wipe at first partitions specified in my previous post - don't wipe only Vendor partition, because it contains important things). Android 12 GSI still aren't stable. Android 11 - maybe will work properly. Android 9 and 10 should work fine. There is even short article about GSI on Galaxy A6+ with some fixes for that device attached:
Samsung Galaxy A6 Plus (2018)
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
You can try of course other GSI's as well:
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Thank you very much, appreciated.
But something weird happens: I install the ROM with success. If then I try to install Magisk (or Rmm) it fails with error 7.
And twrp says No Os installed if I reboot.
But if I try to install Magisk after rebooting into twrp after installing the ROM it goes without errors.
But anyway I have the issues of No Os installed.
Ecto1000 said:
Thank you very much, appreciated.
But something weird happens: I install the ROM with success. If then I try to install Magisk (or Rmm) it fails with error 7.
And twrp says No Os installed if I reboot.
But if I try to install Magisk after rebooting into twrp after installing the ROM it goes without errors.
But anyway I have the issues of No Os installed.
Click to expand...
Click to collapse
You need to reboot to recovery after flashing new system, because just after flashing TWRP doesn't recognize it - that is why you see that "no OS installed". Just reboot your phone to recovery again (you have such option in TWRP). In case of GSI (except maybe CAOS, LineageOS Q/R mod) Magisk or RMM bypass is not needed.
Btw, in case of any problems with hardware support on GSI flash also that patch in TWRP (it may be needed to mount "Vendor" partition in TWRP before flashing that fixes):
Fixes.zip
drive.google.com
Thank you again for your help.
I already rebooted to recovery and twrp keeps saying NO OS.
I'm using twrp 3.5.2_10-0.
I'm starting to suspect that this behaviour is due to the fact that this version of twrp could be too much new and unstable for my phone.
So I'd like to install an older version of twrp with Odin, as explained here:
TWRP for SM-A605FN Samsung Galaxy A6+
How to Install TWRP 3.2.3-1 on Galaxy A6+ SM-A605FN Android 8.0.0 Oreo. Once you installed TWRP recovery on your Samsung Galaxy A6+ SM-A605FN, you can customize it, Rooting or installing custom ROM
www.recovery-mode.com
But I cannot manage to go into download mode again, even from REBOOT menu of twrp it doesn't work, I keep staying in the loop explained before.
Moreover your first option of GSI need me to go into download mode to install the latest stock ROM with Odin.
I just manage to get into the attached screen.
Any idea?
Thank you again
It's not possible to ignore that message and just flash latest stock firmware via Odin? Odin refuses flashing latest stock firmware?
Other builds of TWRP for your devices you'll find here:
Releases · roynatech2544/TWRP_device_samsung_a6plte
Contribute to roynatech2544/TWRP_device_samsung_a6plte development by creating an account on GitHub.
github.com
But don't use TWRP older than 3.4.0, because it doesn't have support for "Vendor" partition.
Yes, I managed to ignore that screen and go in download mode again.
I tried to follow your first option since the second one was not successful.
Installed latest stock and then twrp 3.5.0-1.
Wipe as you explained, I flash the Gsi
system-quack-arm32_binder64-ab-gapps.img
The flash is very fast, but no errors, is it normal?
After that I reboot to recovery in order to flash
Disable_DM-Verity_ForceEncrypt_11.02.2020
it goes but just at the end it gives the error
failed to mount /odm no such file or directory.
And if I reboot to system the phone loops as always.
I'm losing all hope...
Ecto1000 said:
system-quack-arm32_binder64-ab-gapps.img
Click to expand...
Click to collapse
It's okay, but it's possible that you'll always need "vndklite" images for working camera.
Ecto1000 said:
The flash is very fast, but no errors, is it normal?
Click to expand...
Click to collapse
If you flashed it as "System Image" and it was successful then yes - should be fine. DM-Verity isn't needed for GSI - only RMM bypass v3 is sometimes needed (on CAOS, Lineage Q/R mod and maybe in case of some other images). On usual A600FN RMM bypass is not needed on phhusson AOSP. Just format "Data" partition (format, not only wipe) - it will remove encryption for you.
Procedure of flashing should be like that:
1. Wipe: cache, dalvik, data, system ("Vendor" partition leave untouched, because it's important for GSI - that is why you needed to flash stock firmware at first, because it adds vendor files for your phone, but it's needed only once, just don't wipe "Vendor").
2. Flash your GSI as "System Image".
3. Reboot phone (to recovery again).
4. Mount your "data", "vendor" and "system" partition.
5. Flash your zips: RMM bypass v3 (optionally Magisk).
5. Reboot to your new system now.
In case of any hardware support problems, reboot to TWRP again, mount "Vendor" partition and flash that fixes:
Fixes.zip
drive.google.com
Try to boot Android 10 or Android 9 images. If it will succeed, then you can try flashing Android 11 images and check what works, and what not. According to that article
nqnxev said:
It's okay, but it's possible that you'll always need "vndklite" images for working camera.
Click to expand...
Click to collapse
I don't know what are those images. Can you explain better?
When I proceed with RMM bypass V3 I see the errors in the attached image. It seems like there is a problem in writing to /system.
Can this be related to the hardware support problems you mentioned?
I tried with different versions of Twrp already and with Havoc Os too.
Should I try with flashing a different ROM ?
Thanks again
Ecto1000 said:
I don't know what are those images. Can you explain better?
Click to expand...
Click to collapse
Just look at filename of system images. But as I see, it's apparently important on Android 11 and newer. For now, try to boot Android 10 or 9. Let's try with that image:
https://github.com/phhusson/treble_experimentations/releases/download/v222/system-quack-arm32_binder64-ab-vanilla.img.xz
1. Decompress that image.
2. Copy to SD card or to internal storage.
3. Wipe cache, dalvik, data, system.
4. Format data partition (it's needed only once).
5. Flash downloaded and extracted file as "System Image".
6. Reboot phone to recovery (again).
7. Select in TWRP: Mount -> system, data, vendor.
8. Flash RMM bypass v3 (or Magisk).
9. Reboot now to system.
10. In case of some things not working, go back to TWRP and mount vendor partition (Mount -> tick "Vendor" -> go back to flashing zips) and flash that:
Fixes.zip
drive.google.com
11. Reboot to system again and check if now everything works properly.
Ecto1000 said:
When I proceed with RMM bypass V3 I see the errors in the attached image. It seems like there is a problem in writing to /system.
Click to expand...
Click to collapse
Yes, because you need to mount that partitions in TWRP:
Mount -> tick "system", "vendor" and "data" - and now flash whatever you want.
The only "receipt" which isn't giving installation errors is following your last instructions but avoiding to reboot to recovery after ROM flash (used Vanilla), and using Magisk v22 with unticked the line called "skip digest check" . See attached images.
Anyway, still no success to get into android.
Also tried fixes.zip.
Maybe I have to try with sideload ?
Ecto1000 said:
The only "receipt" which isn't giving installation errors is following your last instructions but avoiding to reboot to recovery after ROM flash (used Vanilla), and using Magisk v22 with unticked the line called "skip digest check" . See attached images.
Anyway, still no success to get into android.
Also tried fixes.zip.
Click to expand...
Click to collapse
Everything seems to be okay in your photos. What happens when you press "Reboot System"?
nqnxev said:
Everything seems to be okay in your photos. What happens when you press "Reboot System"?
Click to expand...
Click to collapse
The phone goes into loop with the attached screen and black screen alternatively.
On the top you can see SET WARRANTY BIT: KERNEL, it should be normal right?
Do I have to set something inside MOUNT of twrp before rebooting to system?
Ecto1000 said:
The phone goes into loop with the attached screen and black screen alternatively.
On the top you can see SET WARRANTY BIT: KERNEL, it should be normal right?
Do I have to set something inside MOUNT of twrp before rebooting to system?
Click to expand...
Click to collapse
I've never had such problem, but according to that thread it seems that it's a fault of modified kernel (so don't flash Magisk with GSI, because it patches kernel).
Try to flash stock firmware, unlock bootloader, flash TWRP, format "data" partition, wipe partitions (cache, dalvik, system, data) and flash GSI image as "system image". And reboot to system.
Don't flash RMM and Magisk for now - and check if system will run properly.
Hey!
I unlocked the phone (LLD-L31) with PotatoNV and installed TWRP 3.2.1-0 (from this page: https://ministryofsolutions.com/2020/03/honor-9-lite-emui9-1-twrp-and-root-lld-l31-l21-l22-al10.html), so far so good.
Now I found LOS 18 and 19 (testing) for this device: https://sourceforge.net/projects/andyyan-gsi/
But the sideload doesn't work.
Error: insufficient permissions for device.
I can see the phone via 'adb devices' (in the main menu of the TWRP)
BUT if I start adb sideload in TWRP I get no permissions.
tried sudo, but with the same result.
best regards
lay
#Edit1:
I restarted the adb server with as sudo
adb kill-server
sudo adb start-server
Now it shows Total xfer: 0.00x and breaks.
I think it has something to do with the img.xz files.
I just deleted the xz and tried to sideload it as img.
#Edit2:
ok, the ISOs are compressed.
'unxz blabla.iso.xz'
But the same result: Total xfer: 0.00x and breaks
Simply flash image in fastboot
https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/
-Alf- said:
Simply flash image in fastboot
https://forum.xda-dlinelineage-19.1-20220410-UNOFFICIAL-arm64_bvS.imgage-19.1-20220410-UNOFFICIAL-arm64_bvS.imgeveloplineage-19.1-20220410-UNOFFICIAL-arm64_bvS.imgers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/
Click to expand...
Click to collapse
THANKS!
so it works via 'sudo fastboot flash system blabla.img'
So... LineageOG 19 (testing) gets 'invalid sparce file format at header magic' while flashing, but installes then everything, after that, it's hanging.
After that I tried this step from the link above:
"4. Run command fastboot reboot, unplug your phone, when appears on screen yellow warning, press and hold for 3 sec Volume Up . In eRecovery select 'Wipe data/factory reset'.Reboot ."
Now it does not start the system, but the TWRP (without touchscreen), So i can not use it. Even if I flash LineageOS 18. If I now flash TWRP again and restart, I get to eRecovery and have no TWRP. If I reboot then in eRecovery, I get to LineageOS 18. For my understanding.... VERY strange!
The LineageOS boots and boots and boooooots now...
#Edit1:
tried now the ROMs from your link.
18.1 shows 'invalid sparce file format at header magic' and fails on install.
17.1 without GAPPS succeeds the flashing, but did not reboot in eRecovery, but the TWRP. There I did the same (wipe data, cache, davlik / factory reset) with the error 'unable to wipe cache'.
and it also does NOT boot the system, but TWRP without touchscreen
#Edit2:
I think the phone is dead
maby because of the TWRP wiping the data
The strange thing is, I can still write to the system partition and flash another LineageOS. But it never reboots to system, just to TWRP (in TWRP I can not mount 'system')
#Edit3:
I can not even reboot to fastboot. It always boots the TWRP
#Edit4:
formated (repaired) system in ext4 again
Now it can be mounted, but I can not get to fastboot-mode and get no device via adb.
I can just boot to eRecovery now. So I try the only one thing, that is there: recovery via wifi. It's downloading now the EMUI 9.1. So we'll see.
It's just crazy!
layalala said:
Now it does not start the system, but the TWRP (without touchscreen), So i can not use it. Even if I flash LineageOS 18. If I now flash TWRP again and restart, I get to eRecovery and have no TWRP
Click to expand...
Click to collapse
Your problem is that you don't read carefully.
Why do you have TWRP installed???
layalala said:
It's just crazy!
Click to expand...
Click to collapse
Indeed!
the problem was, that I first followed enother tutorials and then swiched to yours
so the TWRP was already there.
The point is, I got it!!!
After downloading new EMUI via wifi in eRecovery, I got everything back. Meanwhile my VM in the QubesOS did not want to accept the USB-Controller I used for adb-fastboot. So i switched to Windows and followed your tutorial. BUT with the ROMs from Andy Yan (https://4pda.to/forum/index.php?showtopic=896420&st=10780#entry100487186). And everything works! Even the testing LOS 19! Android 12 on that old phone, yeah! but it works rather good.
Your ROM (LOS 18.1) did not work for me. It showed error in header while flashing and broke the process. The ROM from Andy Yan (LOS 19) also showed an error in header while flashing, but the process worked after that.
now I'll try to root it and hope that this will work well
layalala said:
now I'll try to root it and hope that this will work well
Click to expand...
Click to collapse
did rooting succeed?
epicmann24 said:
did rooting succeed?
Click to expand...
Click to collapse
yes!
layalala said:
yes!
Click to expand...
Click to collapse
may i ask which gsi image and which magisk zip did you flash? as for me rooting does not work.
epicmann24 said:
which magisk zip did you flash
Click to expand...
Click to collapse
Running EMUI 9.1 you have to flash magisk_patched recovery_ramdisk (on EMUI 9.1 ramdisk is included in the recovery_ramdisk).
Also you can follow this guide:
https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/post-84305543
You can use files linked in this post, recovery_ramdisk and erecovery are the same for ANE and LLD devices. Use TWRP linked on this post (important!).
Edit: you can get root rights also via SuperUser:
1. In TWRP flash Zip.file
2. Install Phh Superuser apk .(if needed)
https://mega.nz/file/A4sWFYxZ#9KMkvKRgzU7oCvgThPFQOpv_wKAnLZcZVWcJ03HDyNE
layalala said:
the problem was, that I first followed enother tutorials and then swiched to yours
so the TWRP was already there.
Click to expand...
Click to collapse
Hello,
Everything worked; even to the Lineage 19 rom, but, I couldn't install OpenGapps 12l (error 70).
I tried to replace the system "LOSQ - LineageOS 17.1-[10]-unofficial-GSI" via TWRP (system install) and I had the same problem, in addition to not being able to boot by eRecovery to download EMUI by Wi-Fi.
also, on TWRP, I don't have the option to mount "system"
How did you do?
[2022/07/06 - EDIT]
--> eRecovery done
--> Download in progress
--> EMUI 9 Install done
--> go test lineage 18.1 first
Rahinsoo said:
I don't have the option to mount "system"
Click to expand...
Click to collapse
This option is only on GSI vndk-lite version
Keep in mind, that on the Honor 9 lite, in the latest firmwares, the system partition is only 2312 Mb, if I'm not mistaken (on ANE-LX1, the system is 3270 Mb). So those GSI ROMs that work on ANE (Losq, LiR, PE+ etc.) probably won't work on LLD.
https://forum.xda-developers.com/t/kernel-emui-9-p20-lite-phenix-kernel.4241503/post-87085313
-Alf- said:
This option is only on GSI vndk-lite version
Keep in mind, that on the Honor 9 lite, in the latest firmwares, the system partition is only 2312 Mb, if I'm not mistaken (on ANE-LX1, the system is 3270 Mb). So those GSI ROMs that work on ANE (Losq, LiR, PE+ etc.) probably won't work on LLD.
https://forum.xda-developers.com/t/kernel-emui-9-p20-lite-phenix-kernel.4241503/post-87085313
Click to expand...
Click to collapse
That's right, I managed to install open gapps pico in some instance, especially on the bvs_vndklite versions.
What is the difference between bvs version and bvs_vndklite version?
Rahinsoo said:
That's right, I managed to install open gapps pico in some instance, especially on the bvs_vndklite versions.
What is the difference between bvs version and bvs_vndklite version?
Click to expand...
Click to collapse
Very simplistically written:
generally, vndk-lite build are designed for vndk-lite vendors, vndk for vndk vendors.
But on Phhusson AOSP based GSI ROMs there is one change from v300 version (or so): A/B non-lite builds are read-only (due to new phh patches),
A/B vndk-lite builds are in r/w mode, i.e. allow mount system and system modifications.
-Alf- said:
Very simplistically written:
generally, vndk-lite build are designed for vndk-lite vendors, vndk for vndk vendors.
But on Phhusson AOSP based GSI ROMs there is one change from v300 version (or so): A/B non-lite builds are read-only (due to new phh patches),
A/B vndk-lite builds are in r/w mode, i.e. allow mount system and system modifications.
Click to expand...
Click to collapse
Can I use this version without particular problems on my honor 9 lite?
Rahinsoo said:
Can I use this version without particular problems on my honor 9 lite?
Click to expand...
Click to collapse
Read carefully.
Oh, I'm sorry, I misunderstood ^^'
my question was for the vndklite version because I'm having a hard time figuring out the difference.
Rahinsoo said:
my question was for the vndklite version
Click to expand...
Click to collapse
I answered you, didn't I?
Currently I tested several roms. Only certain Andy Yan roms in the version without Gapps work correctly and allow the installation of Gapps.
OK test:
- lineage-18.1-20220616-UNOFFICIAL-arm64_bvS-vndklite
+ Open Gapps pico OK
- lineage-18.1-20220616-UNOFFICIAL-arm64_bvS-vndklite.img --> OK
+ Gaaps --> pico OK ---> play store does not start --> cannot factory reformat (automatic boot on TWRP)
- lineage-19.1-20220613-UNOFFICIAL-arm64_bgS-vndklite.img --> OK
+ Gaaps --> pico OK --> play store does not start --> cannot factory reformat (automatic boot on TWRP)
- lir-v316-220325-arm64-bgZ-lite.img --> OK
+Gaaps --> pico OK --> play store OK --> factory reformat impossible (automatic boot on TWRP)
What is the procedure for factory reformatting to work normally without booting to TWRP?
Rahinsoo said:
Currently I tested several roms. Only certain Andy Yan roms in the version without Gapps work correctly and allow the installation of Gapps.
OK test:
- lineage-18.1-20220616-UNOFFICIAL-arm64_bvS-vndklite
+ Open Gapps pico OK
- lineage-18.1-20220616-UNOFFICIAL-arm64_bvS-vndklite.img --> OK
+ Gaaps --> pico OK ---> play store does not start --> cannot factory reformat (automatic boot on TWRP)
- lineage-19.1-20220613-UNOFFICIAL-arm64_bgS-vndklite.img --> OK
+ Gaaps --> pico OK --> play store does not start --> cannot factory reformat (automatic boot on TWRP)
- lir-v316-220325-arm64-bgZ-lite.img --> OK
+Gaaps --> pico OK --> play store OK --> factory reformat impossible (automatic boot on TWRP)
What is the procedure for factory reformatting to work normally without booting to TWRP?
Click to expand...
Click to collapse
Why do you have TWRP there? You don't need it to install GSI. And if you have TWRP installed instead of Recovery, then it should be clear...