Related
Hello Team,
Well, I wish that there was a special special section for the Honor 8X MAX, as there was so many things we can add to it, but well, let's post in this section
Most devices that came with Android 8.1 are likely to be Treble GSI compatible, so, the thng is that you just gotta find what Partition it uses.
For this device, it was kinda tricky as it was supposed to be A partition but I found out that it on EMUI 8 neither or AB worked, so after several tests, I found out that using any EMUI 9, we gotta use AB and not A, so I tried LOS 17.1 and worked like a charm but as TWRP is not the best for this device and I did not want to bother decrypt it, then root and install GAPPS, I preferred to install AOSP 10 from phhusson now and it works like a charm. The pros of this rom are that it is already "Rooted" and "Gapped", so I would highly recommend it :good:
Requirements::
* Unlocked Bootloader (Not explained here, so you need to use HCU Unlock and purchase a credit for that);
* Your Recovery has to be stock, so if you have TWRP, I recommend to reflash the stock one;
* Choose an ARM64 AB GSI Rom from here;
BUGS:
1. The device might show as not certified, so you won't be able to use any Google services until you register your device. Guide from Androidsage to help doing that;
2. Brightness seems to be at 50% when set at a maximum. This issue might be due to the Vendor Overlays (not a 100% sure though), I am investigating this, but I am using the device as it is and it is fine for me, until we find a solution for it.
Quick Guide:
1. Turn off your phone and then start it with Power and VOL+, until you see the message of the unlocked phone;
2. Wait until you see the Stock recovery not eRecovery;
3. Wipe and reset, Type "YES" and wait for wiping;
4. Plug the USB Cable to PC, reboot the phone while pressing VOL - ;
5. You should see the Android Fastboot now;
6. On Windows download ADB tools and Linux or Mac they can be added using terminal (You can find it easily by doing a simple search);
7. To make sure the phone is correctly connected, type in the CMD Line or Terminal: fastboot devices ;
8. You should see a series of numbers, so now you can flash by typing: fastboot flash system WHATEVERGSIIMAGEYOUCHOOSE.IMG ;
9. Wait about 2-3 minutes and then when the flash is finished, type: fastboot reboot ;
10. That's it! Your phone should now boot to your preferred GSI ROM with more or less everyhing working
riadtaihi said:
Hello Team,
Well, I wish that there was a special special section for the Honor 8X MAX, as there was so many things we can add to it, but well, let's post in this section
Most devices that came with Android 8.1 are likely to be Treble GSI compatible, so, the thng is that you just gotta find what Partition it uses.
For this device, it was kinda tricky as it was supposed to be A partition but I found out that it on EMUI 8 neither or AB worked, so after several tests, I found out that using any EMUI 9, we gotta use AB and not A, so I tried LOS 17.1 and worked like a charm but as TWRP is not the best for this device and I did not want to bother decrypt it, then root and install GAPPS, I preferred to install AOSP 10 from phhusson now and it works like a charm. The pros of this rom are that it is already "Rooted" and "Gapped", so I would highly recommend it :good:
Requirements::
* Unlocked Bootloader (Not explained here, so you need to use HCU Unlock and purchase a credit for that);
* Your Recovery has to be stock, so if you have TWRP, I recommend to reflash the stock one;
* Choose an ARM64 AB GSI Rom from here;
BUGS:
1. The device might show as not certified, so you won't be able to use any Google services until you register your device. Guide from Androidsage to help doing that;
2. Brightness seems to be at 50% when set at a maximum. This issue might be due to the Vendor Overlays (not a 100% sure though), I am investigating this, but I am using the device as it is and it is fine for me, until we find a solution for it.
Quick Guide:
1. Turn off your phone and then start it with Power and VOL+, until you see the message of the unlocked phone;
2. Wait until you see the Stock recovery not eRecovery;
3. Wipe and reset, Type "YES" and wait for wiping;
4. Plug the USB Cable to PC, reboot the phone while pressing VOL - ;
5. You should see the Android Fastboot now;
6. On Windows download ADB tools and Linux or Mac they can be added using terminal (You can find it easily by doing a simple search);
7. To make sure the phone is correctly connected, type in the CMD Line or Terminal: fastboot devices ;
8. You should see a series of numbers, so now you can flash by typing: fastboot flash system WHATEVERGSIIMAGEYOUCHOOSE.IMG ;
9. Wait about 2-3 minutes and then when the flash is finished, type: fastboot reboot ;
10. That's it! Your phone should now boot to your preferred GSI ROM with more or less everyhing working
Click to expand...
Click to collapse
Hi,
Great job, very detailed.
I've faced a situation when trying to flash many GSI img's (Lineage 18, Pixel Exp+, AOSP). The recovery (stock then TWRP) returned "image is too large for the partition". I've ARE-AL00C (4/128) with unlocked BL. Is there any workaround ?
hatemelectr said:
Hi,
Great job, very detailed.
I've faced a situation when trying to flash many GSI img's (Lineage 18, Pixel Exp+, AOSP). The recovery (stock then TWRP) returned "image is too large for the partition". I've ARE-AL00C (4/128) with unlocked BL. Is there any workaround ?
Click to expand...
Click to collapse
Some images simply do not work, so you will need to check for other images simply.
Just install this one : https://github.com/phhusson/treble_...nload/v222/system-quack-arm64-ab-gapps.img.xz
root&gapps&backlight working
of course you'll need Device+ID.apk and register ID with Google but that's easy and simple
Device: Huawei 8x Max AR00
The Quack version works but sadly it is Android 10. I have found many Android 12L GSI roms that I would like to use but the brightness is an issue on all of them. Anyone know how to copy the Quack backlight vendor display and patch it to the newer GSI roms? Tried buildprop GSI wont boot (Crdroid, Lineage 19) Tried Dirty flashing, obviously didn't work. Can't seem to find the file containing the slider brightness limitations. Phherson gives rom backlight options and tried several combinations, and yes rebooted everytime none of them work. Any ideas?
riadtaihi said:
Hello Team,
Well, I wish that there was a special special section for the Honor 8X MAX, as there was so many things we can add to it, but well, let's post in this section
Most devices that came with Android 8.1 are likely to be Treble GSI compatible, so, the thng is that you just gotta find what Partition it uses.
For this device, it was kinda tricky as it was supposed to be A partition but I found out that it on EMUI 8 neither or AB worked, so after several tests, I found out that using any EMUI 9, we gotta use AB and not A, so I tried LOS 17.1 and worked like a charm but as TWRP is not the best for this device and I did not want to bother decrypt it, then root and install GAPPS, I preferred to install AOSP 10 from phhusson now and it works like a charm. The pros of this rom are that it is already "Rooted" and "Gapped", so I would highly recommend it :good:
Requirements::
* Unlocked Bootloader (Not explained here, so you need to use HCU Unlock and purchase a credit for that);
* Your Recovery has to be stock, so if you have TWRP, I recommend to reflash the stock one;
* Choose an ARM64 AB GSI Rom from here;
BUGS:
1. The device might show as not certified, so you won't be able to use any Google services until you register your device. Guide from Androidsage to help doing that;
2. Brightness seems to be at 50% when set at a maximum. This issue might be due to the Vendor Overlays (not a 100% sure though), I am investigating this, but I am using the device as it is and it is fine for me, until we find a solution for it.
Quick Guide:
1. Turn off your phone and then start it with Power and VOL+, until you see the message of the unlocked phone;
2. Wait until you see the Stock recovery not eRecovery;
3. Wipe and reset, Type "YES" and wait for wiping;
4. Plug the USB Cable to PC, reboot the phone while pressing VOL - ;
5. You should see the Android Fastboot now;
6. On Windows download ADB tools and Linux or Mac they can be added using terminal (You can find it easily by doing a simple search);
7. To make sure the phone is correctly connected, type in the CMD Line or Terminal: fastboot devices ;
8. You should see a series of numbers, so now you can flash by typing: fastboot flash system WHATEVERGSIIMAGEYOUCHOOSE.IMG ;
9. Wait about 2-3 minutes and then when the flash is finished, type: fastboot reboot ;
10. That's it! Your phone should now boot to your preferred GSI ROM with more or less everyhing working
Click to expand...
Click to collapse
After trying many different gai variants and versions I found they all have an issue with browsers. Both chrome and edge freeze after scrolling a bit. I'm wondering if this because the GSI uses too much storage space and cannot buffer? Tried to port GSI onto other partitions such as cust, prod didn't work. Even Magisk flashes successfully but does not appear in the rom. The a and b is confusing like EMUI uses both and the TWRP does not decrypt and no Verity commands don't work either. The havoc rom seems to work the best with gapps pico flashed.
~ Android 12 backlight issues had to revert to android 10
~ All GSI have the common browsers freezing. Have to use VIA browser (basic)
~ Magisk won't install have to port to ramdisk, but isn't that the TWRP recovery?
Hello, which one is the Qualcomm driver to be installed for sdm660?
I'm stuck with trying to get ArrowOS to work on my Pixel 2 XL Taimen.
Bootloader is unlocked, I have flashed TWRP 3.6.0_9-0-taimen onto the Pixel.
At some point I was able to move Arrow v12 and GAPPS zip files to the pixel by dragging the files to the phone in Windows. I was able to see the zip files in windows on the phone, but could not see them in TWRP, all the folders had lots of mixed up numbers. Eventually I found the files with File Manager in TWRP, but couldn't do anything with them. I think I have since wiped everything and can't find them now.
on my pc in SDK/platform tools, I can CMD adb devices and see the phone, but if I run fastboot devices, nothing. I have the Google USB driver activated and can see it as an Android Device in Device Manager on windows.
All I can do on the phone is boot to bootloader and get into recovery which takes me to TWRP. If I try to ADB Sideload the ArrowOS zip file to the phone (using sideload in TWRP at the same time) the system just hangs.
Did I just brick my phone? any suggestions on what i can do?
Restore your unit using the full stock ROM package - NOT OTA - from Google. That will get the unit working. To install any ROM you need to do the following.
1. Remove fingerprints and pin numbers from the device. This should disable encryption.
2. In the command prompt boot into TWRP. Do not install unless you want a bootloop.
3. Install Arrow.
As an alternative to 1 above, a USB flash drive with the USB adapter Google includes in the box will also work.
To expand on what @Strephon Alkhalikoi said:
1) TWRP seems unable to handle the encryption used by Android 12, so you probably can't download the new rom to the phone - however sideload should work
2) You should have the baseband and bootloader from the last stock rom installed
3) fastboot devices should work when the phone is in bootloader mode, whereas adb devices works in recovery
4) you may have to format data in TWRP, to clear any incompatible encryption - note that this will delete all the files on your phone
I did the alternative option with a usb drive...worked perfect...thank you so much for helping me!!!
One question...this is my first time installing a custom ROM. I really wanted to try out Android 12 and it is working really well. But my question is, from a security perspective, how secure am I in this mode? not like physical security if someone stole my phone and tried to get in, but secure from online hacking? Will security updates come to me OTA? or will I have to load them from ArrowOS site? I've been on the unsuported updates of Android 11 for a year, so I'm guessing more secure than that?
also, do the Android 12 widgets not come in this ROM, or the GApps ROM? is there a way to get them installed?
bguzz said:
One question...this is my first time installing a custom ROM. I really wanted to try out Android 12 and it is working really well. But my question is, from a security perspective, how secure am I in this mode? not like physical security if someone stole my phone and tried to get in, but secure from online hacking? Will security updates come to me OTA? or will I have to load them from ArrowOS site? I've been on the unsuported updates of Android 11 for a year, so I'm guessing more secure than that?
Click to expand...
Click to collapse
bguzz said:
also, do the Android 12 widgets not come in this ROM, or the GApps ROM? is there a way to get them installed?
Click to expand...
Click to collapse
I believe the ArrowOS developers are working on adding OTA functionality. In the meantime you can flash an update using the USB stick, or you can use adb sideload commands. If you are worried about people accessing your data, a pin and fingerprint lock does wonders.
Which widgets? If you mean the widgets found on the Pixel 6 series, those are exclusive to the Pixel devices: custom ROMs won't have them unless the developer pulls copies from a Pixel 6 / 6 Pro and adds them.
Makes sense. Thank you again.
One thing to make sure if you care about security, is that SElinux is set to enforce. This is an essential security feature that is pretty tedious for the dev to get working, so sometimes it is left as permissive.
Unfortunately, I don't know which roms have enforcing SElinux. If it doesn't say so in the rom's thread, you'll have to install and check.
bguzz said:
If I try to ADB Sideload the ArrowOS zip file to the phone (using sideload in TWRP at the same time) the system just hangs.
Click to expand...
Click to collapse
Try connecting the Pixel 2 XL through a USB hub. I had the same problem in recovery mode and the USB hub solved it.
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
Hi all, after have lost hours and hours traying to install the latest LineageOS for MicroG, I made a facotry reset of the Oneplus 9 Pro (to Android 11), than updated de devices to the latest update (incl. Android 12 and all avaiable updates) and THAN trayed to install LineageOS for MicroG following strictly the Manual of LineageOS (link). It seams to be perfect, until the first start of LIneageOS. I see the first setup screen (Welcome to LineageOS), on the left corner "Emergency call) and on the right the START button, but the screen doesent react andt on the upper right corner I see an empty battery icon. What can I do?? I'm at the end of my knowledge.
In a step of Installing LineageOS (without MicroG) it is necessary to install the dtbo and vendor boot partitions. Maybe the problem is here?
What I have installed:
- dtbo.img (20220823)
- vendor_boot.img (20220823)
- lineage-19.1-20220820-microG-lemonadep-recovery.img
- lineage-19.1-20220824-microG-lemonadep.zip
In Recovery I see "Version 19.1 (20220824)" is installed.
PS: The volume up and down button works...
(unwanted post)
enoironline said:
Hi all, after have lost hours and hours traying to install the latest LineageOS for MicroG, I made a facotry reset of the Oneplus 9 Pro (to Android 11), than updated de devices to the latest update (incl. Android 12 and all avaiable updates) and THAN trayed to install LineageOS for MicroG following strictly the Manual of LineageOS (link). It seams to be perfect, until the first start of LIneageOS. I see the first setup screen (Welcome to LineageOS), on the left corner "Emergency call) and on the right the START button, but the screen doesent react andt on the upper right corner I see an empty battery icon. What can I do?? I'm at the end of my knowledge.
In a step of Installing LineageOS (without MicroG) it is necessary to install the dtbo and vendor boot partitions. Maybe the problem is here?
What I have installed:
- dtbo.img (20220823)
- vendor_boot.img (20220823)
- lineage-19.1-20220820-microG-lemonadep-recovery.img
- lineage-19.1-20220824-microG-lemonadep.zip
In Recovery I see "Version 19.1 (20220824)" is installed.
Click to expand...
Click to collapse
boot is equivalent to recovery
you must be on lastest official firmware
there are also spare firmware you can flash to get aligned
Psk.It said:
boot is equivalent to recovery
you must be on lastest official firmware
there are also spare firmware you can flash to get aligned
Click to expand...
Click to collapse
How can I be on latest official firmware? Before installing LIneageOS for MicroG I installed all possible Updates of the stock Version of Oneplus, than during the installation process I installed the two vendor-files as described in the manual. Do you have links to the spare firmware or better Installation guides?
enoironline said:
How can I be on latest official firmware? Before installing LIneageOS for MicroG I installed all possible Updates of the stock Version of Oneplus, than during the installation process I installed the two vendor-files as described in the manual. Do you have links to the spare firmware or better Installation guides?
Click to expand...
Click to collapse
If you installed C62 (or latest version for your device) you should be OK
(you can try reading other rom theads, some have the link to spare firmware)
for set-up, i prefer taking dtbo, vendor_boot and boot images from payload.bin file already in the rom.zip (using payload_dumper tool)
once "preliminary set-up" is done, reboot to recovery, then format data and sideload the rom
if you need extra flashing (magisk, kernel, what else) reboot recovery and sideload it
Psk.It said:
If you installed C62 (or latest version for your device) you should be OK
(you can try reading other rom theads, some have the link to spare firmware)
for set-up, i prefer taking dtbo, vendor_boot and boot images from payload.bin file already in the rom.zip (using payload_dumper tool)
once "preliminary set-up" is done, reboot to recovery, then format data and sideload the rom
if you need extra flashing (magisk, kernel, what else) reboot recovery and sideload it
Click to expand...
Click to collapse
that is certainly purposeful, but much too difficult for my most modest knowledge.
Ironically, I installed the normal LineageOS without MicroG in the meantime (to be able to use the device) and it works reasonably stable. As soon as I know what I have to install additionally when, I'll probably do again first a factory reset to the original operating system of oneplus, all updates and then I try it again with lineageos for microG. Remains to be seen what else I need to install and when :-/ It's frustrating to cannot follow an official Installation guide without having souch issues.
I can't understand why it has to be so difficult and full of detours that one can't do it if one doesn't have in-depth knowledge. Really a pity.
enoironline said:
that is certainly purposeful, but much too difficult for my most modest knowledge.
Ironically, I installed the normal LineageOS without MicroG in the meantime (to be able to use the device) and it works reasonably stable. As soon as I know what I have to install additionally when, I'll probably do again first a factory reset to the original operating system of oneplus, all updates and then I try it again with lineageos for microG. Remains to be seen what else I need to install and when :-/ It's frustrating to cannot follow an official Installation guide without having souch issues.
I can't understand why it has to be so difficult and full of detours that one can't do it if one doesn't have in-depth knowledge. Really a pity.
Click to expand...
Click to collapse
unfortunately official lineage build does not support signature spoofing, this means you need gapps (Nick gapps is the most used , you can check-out also mind-gapps)
crDroid and riceOS are a couple of roms that allow signature spoofing, you will be abile.to run micrpG on those
about payload_dumper just google it, it's a tool for unpagkage images from the a rom file
about increase of complications, we all must thank you Google 1st and OnePlus (or Oppo) in second place
Psk.It said:
for set-up, i prefer taking dtbo, vendor_boot and boot images from payload.bin file already in the rom.zip (using payload_dumper tool)
once "preliminary set-up" is done, reboot to recovery, then format data and sideload the rom
if you need extra flashing (magisk, kernel, what else) reboot recovery and sideload it
Click to expand...
Click to collapse
I'm looking right now, interesting. You wrote, you prefer taking dtbo, vendor_boot AND Boot Images from payload.bin. When to load dtbo and vendor_boot is describet in the installation guide of lineageOS, but when do you use/install the from you mentioned boot image?
enoironline said:
I'm looking right now, interesting. You wrote, you prefer taking dtbo, vendor_boot AND Boot Images from payload.bin. When to load dtbo and vendor_boot is describet in the installation guide of lineageOS, but when do you use/install the from you mentioned boot image?
Click to expand...
Click to collapse
Instead of recovery
basically:
dump payload
flash btbo
flash vendor_boot
(someone suggest to reboot in fastboot)
flash boot
from fastboot menu go to recovery
finally sideload the zip
enoironline said:
Hi all, after have lost hours and hours traying to install the latest LineageOS for MicroG, I made a facotry reset of the Oneplus 9 Pro (to Android 11), than updated de devices to the latest update (incl. Android 12 and all avaiable updates) and THAN trayed to install LineageOS for MicroG following strictly the Manual of LineageOS (link). It seams to be perfect, until the first start of LIneageOS. I see the first setup screen (Welcome to LineageOS), on the left corner "Emergency call) and on the right the START button, but the screen doesent react andt on the upper right corner I see an empty battery icon. What can I do?? I'm at the end of my knowledge.
In a step of Installing LineageOS (without MicroG) it is necessary to install the dtbo and vendor boot partitions. Maybe the problem is here?
What I have installed:
- dtbo.img (20220823)
- vendor_boot.img (20220823)
- lineage-19.1-20220820-microG-lemonadep-recovery.img
- lineage-19.1-20220824-microG-lemonadep.zip
In Recovery I see "Version 19.1 (20220824)" is installed.
Click to expand...
Click to collapse
Hey just wanted you to know that I had the exact same problem, I posted about it here:
https://www.reddit.com/r/LineageOS/comments/wyr4v9
and after a few failed attempts I basically had to hose and reset to stock with MSM (which was hard since I don't have a Win computer, but that's a solution for another day).
I think the other poster is right, you do need to flash firmware first before installing. Have you tried this? I'll try it tonight and report back, as I need to get this running before Monday.
hyve9 said:
Hey just wanted you to know that I had the exact same problem, I posted about it here:
https://www.reddit.com/r/LineageOS/comments/wyr4v9
and after a few failed attempts I basically had to hose and reset to stock with MSM (which was hard since I don't have a Win computer, but that's a solution for another day).
I think the other poster is right, you do need to flash firmware first before installing. Have you tried this? I'll try it tonight and report back, as I need to get this running before Monday.
Click to expand...
Click to collapse
Actually I have the plan to go back to Stock with MSM, than reinstall all updates of the original Oneplus 9 Pro, than reinstall the actual version of LineageOS MicroG (20220824) after dumping payload and flashing dtbo, vendor_boot and boot like psk.lt wrote.
wondering what you will accive.
Psk.It said:
Instead of recovery
basically:
dump payload
flash btbo
flash vendor_boot
(someone suggest to reboot in fastboot)
flash boot
from fastboot menu go to recovery
finally sideload the zip
Click to expand...
Click to collapse
I'm trying to dump payload. I installed the latest Python version, than downloaded payload_dumper from this link , done what described on the website and now in cmd I have the Message:
File "C:\Users\X\Desktop\Payload_dumper\payload_dumper.py", line 67
<title>payload_dumper/payload_dumper.py at master · vm03/payload_dumper · GitHub</title>
SyntaxError: invalid character '·' (U+00B7)
Do I understand it right, that the script of the tool has an error? Do you have a link of a Payload_dumper Tool that works and from where I can download it? I also found this link and in the text you can download the Tool from here , but I do not trust 100% this sources :-/
enoironline said:
I'm trying to dump payload. I installed the latest Python version, than downloaded payload_dumper from this link , done what described on the website and now in cmd I have the Message:
File "C:\Users\X\Desktop\Payload_dumper\payload_dumper.py", line 67
<title>payload_dumper/payload_dumper.py at master · vm03/payload_dumper · GitHub</title>
SyntaxError: invalid character '·' (U+00B7)
Do I understand it right, that the script of the tool has an error? Do you have a link of a Payload_dumper Tool that works and from where I can download it? I also found this link and in the text you can download the Tool from here , but I do not trust 100% this sources :-/
Click to expand...
Click to collapse
I made It! Using the tool from this website (link to the tool) I was able to extract all files. Now I can start.
Last LineageOS for MicroG Version (20220824) finaly INSTALLED (what a fight!).
Many thanks to Psk.lt and hyve9 for your help!
A quick guide for newbes like me:
Install on a PC:
- adb
- the last qualcolm driver ect
- python
download on the PC:
- MSN Tool to go back to stock OS
- payload Dumper Tool (THANK YOU PSK!!!)
- the newest LineageOS for MicroG Version
On the Oneplus 9 Pro:
- With MSN Tool back to Stock OS
- Install all possible Updates (in my device it was C61!)
- Install Oxygen Updater from an app Store or apk
- Install the REALLY last Update for your device (in my Case C62)
- download the last LineageOS for MicroG Version (.zip)
- open the .zip file and copy out the payload.bin file
Than like Psk.lt wrote, with the Payload Dumper dump the payload-file and extract btbo, vendor_boot and boot files
Safe the following files under adb
- btbo
- vendor_boot
- boot
- the lineageOS for MicroG file
Start with the installation like described in the LineageOS guide, but
- use the own btbo and vendor_boot files
- for recovery, insted of using the recovery-file from LineageOS for microG, use the boot file (extractet with Payload dumper)
- finally sideload the LineageOS for MicroG file (.zip)
End
A question: in the future can I use the oxygen Updater under LineageOS for MicroG to install all the newest updates, or does it work only if using the stock OS?
enoironline said:
A question: in the future can I use the oxygen Updater under LineageOS for MicroG to install all the newest updates, or does it work only if using the stock OS?
Click to expand...
Click to collapse
you should use embedded updater (settings - system - update) but you will not be able to copy the zip if you don't have root
If you want backup the updated zip, you should sideload via pc
enoironline said:
Last LineageOS for MicroG Version (20220824) finaly INSTALLED (what a fight!).
Click to expand...
Click to collapse
Let me know how you are liking it, im debating it or CRDroid.
ajolly said:
Let me know how you are liking it, im debating it or CRDroid.
Click to expand...
Click to collapse
I'm using LineageOS with MicroG since the End of last year and had never real problems, only the installation progress is complicated (if you follow only the official installation guides of LineageOS and from LOS-MicroG). Last week I had LineageOS without MicroG installed and I must say, I did not really missed the MicroG functions, maybe because the apps I'm using do not need necessarely the functions of MicroG / would mainly need the messaging function, but can still run and function without. It dipend what you want to accive with the OS, if you want to be compleetly G-free under LineageOS, than you have to change at your own a few more things like DNS setting, systemwebview... I can't compare LinOS-MicroG with CRDroid, beacause I never used it.
What I do not like in V 19.1 vs 18.X is the bigger format of the quick setting tiles. I know that it's possible to change it, but I have to find out how to do it in the simplest way.
A function that I miss in LineageOS (for MicroG) is a Sandbox function like in Graphene, but using Shelter helps, even if not as good as a Sandbox.
What I really don't like is the fact, that LineageOS for MicroG doesn't ships Updates with the firmware, and their Installation Guide is not really helpful (do what is described by LineageOS... and it's not really what you have to do).
What I really like is how long the battery life lasts, at least with V18 and it has surely to do with my user's habits. Now to find out how it will be under V19.1.
Over all: I like it and do not want to replace it (for now).
Hello,
I flashed the latest Lineage recovery and LineageOS20 on my Google Pixel 5, and I'd like to disable encryption on the data partition. Is there an ADB command I can run, or file I can flash to achieve this? I also have Magisk 26.1 flashed.
I use this phone for a development project and encryption is getting in the way.
Thanks!
I'm surprised no one knows.
I wanted to go the TWRP route of formatting the data partition, but I can't get TWRP to boot when running Android 13. I need to be on Android 12 to boot TWRP successfully, but being on Android 12 means I can't flash LineageOS20 (requires Android 13), a real catch 22.
Otherwise, does anyone have a link to the latest LineageOS19.1 for Redfin? The link is broken on the LineageOS website and I can't locate that zip file on any other website.