GUIDE: Install GSI Treble Roms on Honor 8X Max ARE-AL00 - Honor 8X Guides, News, & Discussion

GUIDE: Install GSI Treble Roms on Honor 8X Max ARE-AL00 - Honor 8X Guides, News, & Discussion

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?

Related

[Guide]Lenovo S5 K520: TWRP, Root and Decrypt data

Hello everyone, after struggling for a few hours I managed to finally disable force encryption in my phone (so that TWRP could backup the data partition).
I'd like to write a quick list of what I did in the form of a guide to unlocking the bootloader, installing TWRP and getting root with Magisk. I'm just a user, not a developer and this guide is brief, it's not a detailed tutorial and does not include trivial steps (like how to install drivers for your OS).
Warnings: Although small, there is always the chance this bricks your phone. I take no responsibilities.
This will factory reset your phone so back up everything before you start.
My phone is Lenovo S5 (K520) Global version (see screenshot) I don't know if this will work for other firmwares.
Prerequisites:
Install Phone, ADB and Fastboot drives. You can get ADB and Fastboot binaries from here:
https://forum.xda-developers.com/showthread.php?t=2588979
Download this archive:
http://www.mediafire.com/?4dcvzw1hdmzfn10
It contains all the files used in this guide.
Alternatively, download all the files used from their sources.
You will need an SD card or a USB flash drive with an OTG adapter.
Copy the following files to it:
A. "Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip"
(Downloaded from http://forum.xda-developers.com/showthread.php?t=3817389 )
B. "Magisk-v18.0.zip"
(Downloaded from http://forum.xda-developers.com/showthread.php?t=3473445 )
C. (optional) "\stock\boot.img"
(Downloaded from the global firmware @ 4pda)
If you chose to use Micro SD card, you can insert it now.
Note: I know there is a way to push these files directly to TWRP from PC through USB instead of using SD Card/Flash drive but I've never tried it.
Lets start:
1. Go to 'Settings>About phone' and tap on "Lenovo version" several times until developer options are enabled.
2. Go to 'Settings>System>Developer options' and enable "OEM unlocking" (Note: for me this option was greyed out and I had to connect to wifi and wait for a minute or two).
Optional: Enable "USB debugging" if you wish to enter fastboot via ADB.
3. Turn off the phone and press and hold 'Volume down'+'Power' buttons until you see "fastboot mode" on the phone screen (alternatively, don't turn off the phone and instead enter fastboot mode via ADB (adb.exe reboot bootloader)).
4. Connect the phone to the PC via USB and open a command prompt in the location that you installed fastboot binary to.
Type (after each command press enter):
Code:
fastboot devices
To verify that the phone is recognized. And if it is type:
Code:
fastboot oem unlock
Now on the phone LCD navigate to "Yes" with volume buttons and press power to select it.
Your phone will factory reset, this will take a few minutes. Let it finish.
5. Put the TWRP image in your fastboot path. I used "recovery-twrp-3.2.3-crn-seoul(v3.2.3-1).img" downloaded from this URL:
https://forum.xda-developers.com/android/development/lenovo-s5-k520-twrps-t3863860
But I included 2 more files that I found (I did not try them).
6. Enter fasboot mode again and type:
Code:
fastboot flash recovery recovery-twrp-3.2.3-crn-seoul(v3.2.3-1).img
(Substitute "recovery-twrp-3.2.3-crn-seoul(v3.2.3-1).img" with the recovery filename of you choice)
7. If successful, disconnect the USB cable and enter Recovery mode, do not turn off or reboot the phone because upon restart the phone will revert to stock recovery (I.E. delete TWRP).
To enter Recovery mode press and hold 'Volume down'+'Power' buttons until you see "fastboot mode" and from there choose "Recovery mode" with the volume buttons and confirm with the power button.
(Alternatively, you can try holding 'Volume up'+'Power' to directly enter Recovery mode but I found it a little finicky)
8. In TWRP, swipe to allow changes. Press cancel when asked for a password to decrypt data.
If you chose to use a USB flash drive with an OTG adapter, connect it and mount it (Mount>usb-otg).
9. Go to Wipe>format data, type "yes" and confirm (if you have any data like installed apps, contacts etc., it will be deleted).
10. Go to Install and install "Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip".
The files will be in (/external_sd/ or /usb-otg/).
11. Install "Magisk-v18.0.zip"
Important note: If you want to keep encryption (if you don't care if TWRP can't access /data/) and just obtain root, skip steps 9 and 10.
12. Reboot to system and wait for a few minutes for the initial setup.
If for some reason boot fails (nothing happens after 10 minutes) and you can still enter TWRP (hold 'Volume up'+'Power'), then you can revert the changes by restoring the stock boot image (TWRP>Install>Install image>boot.img - put a checkmark on "boot").
If this worked for you, please tell us by replying to this thread.

Thanks a lot man. This phone is a beast in quality/price when talking about hardware. Costs a bit more than 100€ and has the same hard than others at 180-200€ at least. Bad thing is software but with TWRP and root everything is possible . Just found what project treble is, amazing possibilities. Can't beliebe nobody replied yet to yor post. Its a great guide and you show all the sources from where your downloads come. As you said in another thread its better this way so people can trust your content more:
C4lculated said:
I also wanted to root but I didn't want to run a bunch of unknown programs (from XN Logos), so I managed to install TWRP and root with magisk. I wrote a guide on how to do it:
https://forum.xda-developers.com/ge...ide-lenovo-s5-k520-twrp-root-decrypt-t3882402
Click to expand...
Click to collapse
I am yet waiting for my Lenovo S5 to arrive but I will give this guide a try. I was about to follow XN logos (stupdroid) guide/software but I prefer yours. Just one question... have you checked whether the TWRP v3.2.3 (latest) from dmilz make proper working backups? Can I trust that a full backup will be loaded correctly after installing any unofficial ROM, to go back to stock if necessary? I made once the mistake of relying a TWRP and later I found out that one was ok for flashing but didn't create working backups. I asked him also the same question, but I guess you also tried yourself to make a backup and restore from it using TWRP.
Next step will be to flash an Android 8.1 or 9 GSI rom (did I already say I'm amazed by GSI/project treble roms? just found about them last days). I will update you about my luck following your guide

does anyone enable lte bands, 4 and 28?

just bought this phone, currently on shipping..
I'll first try with twrp + aosp 9 GSI

Hi man, have you upgrade to gsi
acost91 said:
Thanks a lot man. This phone is a beast in quality/price when talking about hardware. Costs a bit more than 100€ and has the same hard than others at 180-200€ at least. Bad thing is software but with TWRP and root everything is possible . Just found what project treble is, amazing possibilities. Can't beliebe nobody replied yet to yor post. Its a great guide and you show all the sources from where your downloads come. As you said in another thread its better this way so people can trust your content more:
I am yet waiting for my Lenovo S5 to arrive but I will give this guide a try. I was about to follow XN logos (stupdroid) guide/software but I prefer yours. Just one question... have you checked whether the TWRP v3.2.3 (latest) from dmilz make proper working backups? Can I trust that a full backup will be loaded correctly after installing any unofficial ROM, to go back to stock if necessary? I made once the mistake of relying a TWRP and later I found out that one was ok for flashing but didn't create working backups. I asked him also the same question, but I guess you also tried yourself to make a backup and restore from it using TWRP.
Next step will be to flash an Android 8.1 or 9 GSI rom (did I already say I'm amazed by GSI/project treble roms? just found about them last days). I will update you about my luck following your guide
Click to expand...
Click to collapse
Kindly drop the procedure am hitting brick with all the method i used .????????

Stock firmware lenovo k520
I have tried your method on ROM that is based on China and also globally, and TWRP was successfully installed, and I have also tried several Rom GSI, and only AOSP Extended is successful, but with Bluetooth bugs it cannot be turned on, if others want flash files and stock firmware for k520, just let me know, thanks.

Working on S5 Pro too?
Hi! Can it work on S5 Pro too? I really want to root this device and I don't find out a way to get this happening. Thanks!

Does this work for s5 pro l58041?
Thanks

B4ph0 said:
I have tried your method on ROM that is based on China and also globally, and TWRP was successfully installed, and I have also tried several Rom GSI, and only AOSP Extended is successful, but with Bluetooth bugs it cannot be turned on, if others want flash files and stock firmware for k520, just let me know, thanks.
Click to expand...
Click to collapse
Hi! Sorry for offtopic!
Could you please PM me the link on AOSP extended image which you installed. Thank you!

Hello! Did somebody managed to install GCAM to Lenovo S5? I'm trying and I can;t do this, magisk modules are not loading...

so far I've used 2 alternative rom and works fine, aosp & octopus os, especially octopus os

I need some help..
Did anyone had lenovo s5 persist.img..
I lost my persist afer flashing global rom.208st via qfil..
I check the rom has no persist.img

Please visit to https://youtu.be/wbpV59kutJM for tutorial flash and upgrade Lenovo S5 in YouTube

hello guys, i always get into download mode,after press reboot system (twrp), any solution for my problem ?

has anyone achieved unlocking bands in this phone?

Please port miui 11 9.10.30 mi-room pie 9.0 redmi note 4x SD625 to lenovo S5.
https://megaroms.net/miui-11-9-10-30-stable-port-for-redmi-note-4-4x/
https://sourceforge.net/projects/miui-ports.whats-new.p/files/mido/miroom/

After unlocking bootloader, is there anyway to remove the hideous "software can't check for corruption" warning? Thanks.
---------- Post added at 01:44 AM ---------- Previous post was at 01:39 AM ----------
Suryo75 said:
hello guys, i always get into download mode,after press reboot system (twrp), any solution for my problem ?
Click to expand...
Click to collapse
This means no rom is installed in your phone. Either you accidentally wipe system in twrp, or the rom is corrupted.
Download the deodexed stock rom below and flash with twrp. Should fix your problem.
https://drive.google.com/open?id=13tRqo5eSpRiVJwKiA-iSj2GyIF353ATQ

jychung93 said:
After unlocking bootloader, is there anyway to remove the hideous "software can't check for corruption" warning? Thanks.
---------- Post added at 01:44 AM ---------- Previous post was at 01:39 AM ----------
This means no rom is installed in your phone. Either you accidentally wipe system in twrp, or the rom is corrupted.
Download the deodexed stock rom below and flash with twrp. Should fix your problem.
https://drive.google.com/open?id=13tRqo5eSpRiVJwKiA-iSj2GyIF353ATQ
Click to expand...
Click to collapse
thank you i'll try

Could you plz make tutorial about getting back to stock unroot...thx

Twrp gone
Hello sir thank you for this wonderful tutorial,
But I have a problem , after booting to TWRP , then boot to system after that when I try to go back to recovery mode TWRP , twrp is gone , stock recovery back

[ZE620KL/Android 9][TREBLE] COMPLETE GUIDE: Unlocking, Rooting & Flash GSI + Fixes

[ZE620KL/Android 9][TREBLE] COMPLETE GUIDE: Unlocking, Rooting & Flash GSI + Fixes
Unlocking bootloader to Flashing GSI (Asus Zenfone 5 [ZE620KL] / Android 9.0)
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* 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.
*/
About :
The last guide could leads to soft brick, as the instructions were not clear nor the files not supported for Android 9.0.
Here is a complete guide with TWRP 3.3.0 for Android 9.0, clear instructions and multiple fixes for GSI.
It has been tested on stock version v16.0615.1903.92.
Requirements :
- A stock version V16.0610.XXXX.XX or higher
- A phone on Android 9.0 (not 8.0!)
- A fully working USB cable
- Latest ADB / Fastboot drivers
- Bootloader unlocker (download latest from Asus website or from here)
- TWRP 3.3.0 image
- Android9EncryptionDisablerZE620KL.zip
- Magisk v19.3
Instructions :
Unlocking Bootloader
1. Backup all your important data.
2. Install the bootloader unlocker APK, and follow the steps. You will loss your warranty here, and it will factory reset your data
3. If there is any issue here, go into your stock recovery (volume down + power button) and factory reset.
Installing TWRP
4. Shutdown your device & boot in fastboot mode using volume up + power button.
5. Check that the connection between your device and your computer by typing this in your command line :
Code:
fastboot devices
6. Flash TWRP recovery using :
Code:
fastboot flash recovery <twrp_name>.img
7. Now reboot in recovery mode using :
Code:
fastboot oem reboot-recovery
8. In TWRP, select Wipe > Format Data > enter "yes" and confirm
9. Return to the main menu, select Reboot > Recovery
10. Do 8. & 9. and again
11. Using TWRP or ADB, install Android9EncryptionDisablerZE620KL.zip (on TWRP, go into Install > find Android9EncryptionDisablerZE620KL.zip > Install zip)
If everything has gone successfully, you now have a custom recovery.
As for some GSIs, a patched boot partition may cause bootloop, you should try installing Magisk after installing the GSI. If you want to keep your stock ROM, go directly to "Magisk Installation" section.Installing a GSI
This step may vary depending on the different GSIs distribution. I assume you install Havoc OS v2.7 GSI which actually works on this device.
1. Backup all your important data using TWRP backup.
2. Select the arm64-aonly GSI image you want, and move it on your external SD.
3. Wipe Data, Dalvik, and Cache.
4. Go back in the main menu of TWRP, and reboot to recovery.
5. Remove Magisk if it was previously installed, by using its uninstaller script.
6. Flash the GSI to system partition.
7. Boot and perform a factory reset.
Installing Magisk
1. Add the Magisk zip archive to your external storage.
2. Boot into TWRP recovery, and install the zip.
3. Enjoy!
Bug fixes:
Insufficient storage in the system partition to flash GApps : Download your OpenGApps archive on your external SD, and use MagicGApps 2018.9.23 to install GApps.
Auto-Brightness doesn't work: Download framework-res__auto_generated_rro.apk from here.
Using a root explorer or command-line, push the APK to /vendor/overlay.
Then run the following command in a rooted terminal or ADB shell:
Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/framework-res__auto_generated_rro.apk
My camera doesn't work well (green tint on face camera) and/or the app doesn't boot: If Asus Camera doesn't launch on your GSI, you should probably edit your /system/build.prob file.
You need to edit ro.product.model, ro.product.brand, ro.product.name, ro.product.device, ro.product.manufacturer & ro.build.product properties to be:
Code:
ro.product.model=ASUS_X00QD
ro.product.brand=asus
ro.product.name=WW_Phone
ro.product.device=ASUS_X00QD
ro.product.manufacturer=asus
ro.build.product=ZE620KL
You can instead use Google Camera mod (port from Arnova8G2 & modded by 5Z community, thanks to them!), which works well (edit: there is a bug on HavocOS, we can't access settings).Bonus:
- You can reinstall DTS Headphone:X here.
- For booting your kernel in Permissive mode, check here
Sources:
TWRP 3.3.0 : On GitHub
If you need help or if you want to help on ZE620KL development go here:
https://t.me/Zenfone5Dev
(We will continue to update & help here though.)
Many thanks to all of the Zenfone 5 community (particularly Emincan, Pandolfi and Lmajkej),
Phhusson & Erfan for their works on GSI, and Shakalaca for its work on TWRP 3.3.0!

On HavocOS v2.8 GSI (13-08-2019):
It works:
- Almost anything
- Adaptive Brightness (after manual fix)
- Notch overlay
- DTS Headphone X (after manual installation)
- NFC
- Face unlock
- Stock camera (after manual fix)
- Magisk
- SDcard access
It doesn't works:
- VoLTE / VoWifi
- Google Camera settings
- External speaker amplifier (NXP amp)
- APT-X / APT-X HD bluetooth
- Low microphone in normal use
- No microphone in calls (only headphone microphone works)

GCam settings
But my google camera keep crashing when I want to go into camera settings

Hi thanks for this tutorial, this is my first time rooting my phone. I'm encountering a problem with my sd card after installing havoc os, everytime i try to move, save or any write functionality i do to my sd card, it always says the android version isn't compatible. I could still see my files from my sd, but everytime it asks permission it always say this

bentley0928 said:
But my google camera keep crashing when I want to go into camera settings
Click to expand...
Click to collapse
Same issue here. I will update the thread when I will find a more working GCam port (perhaps, this GCam port works well on ZenUI)
Jolo110 said:
Hi thanks for this tutorial, this is my first time rooting my phone. I'm encountering a problem with my sd card after installing havoc os, everytime i try to move, save or any write functionality i do to my sd card, it always says the android version isn't compatible. I could still see my files from my sd, but every time it asks permission it always say this
Click to expand...
Click to collapse
It's a known issue, the GSI maintainer @vince31fr is working on it. I don't have it, but I can advice you to use Solid File Manager, which works like a charm on my device.

"- No microphone in calls (only headphone microphone works)"
Funny... I'm on stock latest firmware and I have this issue, so I thought I try something new, and this has that issue. It can't be a coincidence. Something is ****ed up with this device.

Wonder if this will work for the Zenfone 5 Lite (or 5Q)? I wanna root my 5Q so bad haha

Thanks for the great instructions! Steps 1 through 11 worked perfectly for me, then I installed LineageOS (lineage-17.0-20191231-UNOFFICIAL-treble_arm64_avN.img) and it works properly. Then when I go back to TWRP and install Magisk v20.1 it reboots into an endless Lineage bootup logo animation (not boot loop). I can get an adb shell, but now also the external SD card has become invisible. Any suggestions?
UPDATE: I switched over to the patched Magisk version from PHH (https://forum.xda-developers.com/zenfone-5/general/ze620kl-add-support-to-evey-android-9-t3966918) and everything works perfectly now!

Hi!! I thanks for these instructions you gave. I know this post is a bit older. But is the only one I think could help me.
I got an ZE620KL and I'm trying to root this device. I have some experience in unlocking bootloader and rooting devices. But this one... Is giving me a lot of work. Researching in a lot of forums and websites I tried a lot of things with no success. In theory, is just install the official apk provided by ASUS and run the application. But the app doesn't work for a long time as I researched (error accusing network problem). I tried unlock via fastboot commands but I always got stucked by "remote: permission denied" even with latest drivers and ADB Fastboot installed. And yes... I let my device with no one security feature enabled and didn't worked. I tried everything even after wiped data / cache and factory reset and no progress.
In my researches, I realized something about 'oem unlock'. It appears to be the key to solve this. And I guess the tool to work with this is the damn unlock tool from ASUS which don't work! Also, I've heard about workaround with Magisk by flashing a custom recovery to achieve the root. Magisk no longer supports zip files to flash. Only '.img' and '.tar' files. I'd like to find some light here... I don't know what to do. I appreciate any help!

Hello do I need to flash Android9EncryptionDisablerZE620KL.zip if Im gonna flash a non-GSI custom ROM? Or its only for GSI Treble ROM?

[email protected] said:
Hi!! I thanks for these instructions you gave. I know this post is a bit older. But is the only one I think could help me.
I got an ZE620KL and I'm trying to root this device. I have some experience in unlocking bootloader and rooting devices. But this one... Is giving me a lot of work. Researching in a lot of forums and websites I tried a lot of things with no success. In theory, is just install the official apk provided by ASUS and run the application. But the app doesn't work for a long time as I researched (error accusing network problem). I tried unlock via fastboot commands but I always got stucked by "remote: permission denied" even with latest drivers and ADB Fastboot installed. And yes... I let my device with no one security feature enabled and didn't worked. I tried everything even after wiped data / cache and factory reset and no progress.
In my researches, I realized something about 'oem unlock'. It appears to be the key to solve this. And I guess the tool to work with this is the damn unlock tool from ASUS which don't work! Also, I've heard about workaround with Magisk by flashing a custom recovery to achieve the root. Magisk no longer supports zip files to flash. Only '.img' and '.tar' files. I'd like to find some light here... I don't know what to do. I appreciate any help!
Click to expand...
Click to collapse
Im not sure if you still have your phone or you have successfully unlocked bl. but I found an updated version of their tool which works.
*tried unlocking from android 10 not working, it says device model not supported*
Zenfone 5 Unlock BL

cf100clunk said:
Thanks for the great instructions! Steps 1 through 11 worked perfectly for me, then I installed LineageOS (lineage-17.0-20191231-UNOFFICIAL-treble_arm64_avN.img) and it works properly. Then when I go back to TWRP and install Magisk v20.1 it reboots into an endless Lineage bootup logo animation (not boot loop). I can get an adb shell, but now also the external SD card has become invisible. Any suggestions?
UPDATE: I switched over to the patched Magisk version from PHH (https://forum.xda-developers.com/zenfone-5/general/ze620kl-add-support-to-evey-android-9-t3966918) and everything works perfectly now!
Click to expand...
Click to collapse
Do you still have the patched Magisk zip file, the original link in the post seems not working

[ROM][A51] HAVOC OS for Samsung Galaxy A51 [GSI]

Hey Guys,
Before you dive in, irrespective of your reading speed read this carefully and slowly for better understanding but if you cannot focus and read it slowly then you better give up music for a few weeks.
About the Device
Before you jump in and get your hands dirty.. you should know that what you will be installing is Generic System Image, It is not specifically made for your device so if you are going to install some other GSI other than this, you might face some issues.
If you are a beginner, you should Go Through Project Treble, just for the sake of knowledge.
Also Galaxy A51 has A/B partition and Supports Project Treble though remember that Treble Devices are not same as A/B devices and Vice Versa.
Things You’ll Need
A Computer (not an iPad)
Internet [requirement around 6 gigs (4.8 gigs optional, for downloading stock Firmware, Highly Recommended)]
Samsung Galaxy A51 (will not work on A50)
Patience and a madcap attitude.
Resources
Download Odin from the link given below and extract it in a folder.
https://odindownload.com/download/Odin3_v3.13.3.zip
Adb and Fastboot Drivers
https://gsmusbdrivers.com/download/adb-fastboot-drivers/#
Samsung Drivers
https://developer.samsung.com/mobile/file/68b2dc40-3833-4a8b-b58e-32f7aca25c00
Havoc OS GSI
Havoc-OS - Browse /arm64-ab at SourceForge.net
Don’t forget to check that there is “arm64” and “ab” written on the name of the file
Other option is with Gapps (it means the rom will come with Google Play services built in
otherwise it is Vanilla Android.
GSI Flasher
(It is used for converting your img file into flashable Zip)
https://drive.google.com/file/d/1J8OlI2CCXpvAJ5FhFlR2b_y58eHQERGs/view?usp=sharing
Extract it you’ll find three folders gsi, META-INF, scripts, keep all of them inside the GSI
Flasher extracted folder.
Twerp Recovery
twrp-a51-3.5.0_10-1_ianmacd.tar | by androidhowto for Utilities (androidfilehost.com)
Do not use any other in this case you might get mounting errors.
Encryption Disabler
Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip | by androidhowto for Utilities (androidfilehost.com)
Its Show time
1. Go to settings and go to about phone, tap build number 7 times and a dialog will appear, you are now a developer.
2. Go to additional setting or search developer options in the settings search bar
3. Once in the developer settings find OEM unlock and turn in on, scroll down and also turn on USB debugging, your phone will ask the permission for accessing the data by your computer.
4. Turn off your device. Get a usb cable and connect it to your computer.
5. While phone is off first press Volume UP and Volume Down together, and then then insert the usb cable into the phone while holding the buttons wait for two seconds. a blue screen will come up telling you about consequences and life choices.
6. Long press the Volume Up Button and a new blue screen will show up asking you for unlocking the bootloader. Press Volume Up to confirm. You device will erase everything and reset itself ( Don’t forget to take backup of your Data).
7. After the setup screen appears skip everything in the setup and enable developers option and enable USB debugging in the developer options.
8. Turn off your device again and Repeat step 5.
9. Press Volume up for entering the download mode
10. Now in your computer, Install Odin and open Odin.exe you’ll find your device as comm: xx
Now click on the AP button and select the twerp you downloaded.
Press start and twerp will be installed in your device. Your device will reboot don’t let it boot to one ui, press all three buttons together and hold, as soon as the screen goes black release only the volume down button. Keep holding the Volume UP and power buttons for 3 seconds and then release, you find yourself in twerp. If you miss it repeat the process again but don’t let it boot to One Ui.
In twerp press wipe => format data =>type yes. Press home button and again go to wipe advanced select Data, Cache and Dalvik and swipe to clear.
Press home again. Go to reboot and select recovery, twerp wil reboot. Once it reboots transfer the encryption disabler to your phone and in twerp press install select the storage, sdcard or internal storage, where you have stored the file, select it and swipe to install.
Now in your computer extract the Havoc os image and rename it as “system.img”.
Extract the GSI flasher, copy system.img and paste it in the gsi folder of the GSI Flasher.
Select gsi, Meta-inf, scripts and compress them into a zip and transfer into the phone.
Now in twerp Press install, select the zip file and swipe to install. Also install Gapps or Magisk if you want (though normal magisk will have problem try install phh_magisk, discussed later).
Reboot and KABLAMO You have installed Havoc OS.
Bugs
A small random issue in Auto Brightness
If you root with magisk and install modules, after you reboot your phone will get into a bootloop. Use Phh_Magisk but I aint sure if it’ll work or not Your call madcap.
NONE OF THE FILES IN THIS TUTORIAL HAVE ANYTHING TO DO WITH ME. If SOMETIHING HAPPENS I AM NOT RESPONSIBLE. ONLY DO IT AT YOUR OWN RISK.
Troubleshooting.
If you find errors in twerp, such as unable to mount vendor or system_root, or data. Then you got to install the stock One Ui Back again, therefore it is highly recommended to keep with yourself the stock firmware. You will need It. And it is 4.78 gigs. You can download it from
Model : SM-A515F - Galaxy A51 — Samfrew.com
To reinstall the stock firmware first extract it and the open odin and repeat steps 8 and 9, once your device is detected in Odin press the respective buttons and select the respective files such as for BL button select the file With BL in the name. Do it for buttons, BL, AP(once you select the file it will take long for it load into odin so do not panic and let it load, it might become unresponsive but use patience and wait.)CP , CSC. Click on start and you’ll have ONE Ui back on your device.
To Lock the bootloader repeat steps 5 and 6.
If you still want more stability and Control You can install a different Kernel NDataX from (@Hendamanu) https://forum.xda-developers.com/m/hendramanu.11224917/

I'd like you to please correct the title and write GSI instead of custom rom as both are different things and the title can be considered misleading.

Yillié said:
I'd like you to please correct the title and write GSI instead of custom rom as both are different things and the title can be considered misleading.
Click to expand...
Click to collapse
Oh, my bad.. changed it.

GrandmaGotGuns said:
Oh, my bad.. changed it.
Click to expand...
Click to collapse
Thanks a lot

Is stable? Does the fingerprint on the screen work?

LichtEstarossx said:
Is stable? Does the fingerprint on the screen work?
Click to expand...
Click to collapse
Its Stable and yes fingerprint works as well. Battery life is also good almost 9 hours of screen on time for my device.

GrandmaGotGuns said:
Its Stable and yes fingerprint works as well. Battery life is also good almost 9 hours of screen on time for my device.
Click to expand...
Click to collapse
I will try to test it although another question arose, the encryption works in the twrp or is it to disable the dm verity?

LichtEstarossx said:
I will try to test it although another question arose, the encryption works in the twrp or is it to disable the dm verity?
Click to expand...
Click to collapse
You need to flash disable dm verity before flashing the gsi.. one ui encrypts the data.

I'll soon update this for Android 11 (R)

I did all the steps correctly (started oneui before), but now it won't start the system, is there any way to fix it?

LichtEstarossx said:
I did all the steps correctly (started oneui before), but now it won't start the system, is there any way to fix it?
Click to expand...
Click to collapse
What android version are you at?

GrandmaGotGuns said:
What android version are you at?
Click to expand...
Click to collapse
I had android 10
one ui 2.5
although it is rare that the gsi does not work

LichtEstarossx said:
I had android 10
one ui 2.5
although it is rare that the gsi does not work
Click to expand...
Click to collapse
If you are using the same gsi mentioned above then it should work. Not all GSIs will run on your device. Did you successfully install twerp?

GrandmaGotGuns said:
If you are using the same gsi mentioned above then it should work. Not all GSIs will run on your device. Did you successfully install twerp?
Click to expand...
Click to collapse
use havoc 3.8 vanilla arm64 ab
and I tried phh aosp but it didn't work

LichtEstarossx said:
use havoc 3.8 vanilla arm64 ab
and I tried phh aosp but it didn't work
Click to expand...
Click to collapse
Model : SM-A515F - Galaxy A51 — Samfrew.com
Model : SM-A515F | Samsung Firmware Database
samfrew.com
Upgrade to android 11, first install one ui 3 from the site above. I'll update it for Android 11 [R].

GrandmaGotGuns said:
Model : SM-A515F - Galaxy A51 — Samfrew.com
Model : SM-A515F | Samsung Firmware Database
samfrew.com
Upgrade to android 11, first install one ui 3 from the site above. I'll update it for Android 11 [R].
Click to expand...
Click to collapse
for now reinstall oneui 2.5, I will try to compile orangefox for android 10, and about the brightness bug in the gsi I know how to correct it, if there is any way to contact you to talk about it, say so

LichtEstarossx said:
for now reinstall oneui 2.5, I will try to compile orangefox for android 10, and about the brightness bug in the gsi I know how to correct it, if there is any way to contact you to talk about it, say so
Click to expand...
Click to collapse
If you are talking about gsi fix then im not sure that it'll work. I tried patching other gsi's for specifically efor xynos but the success rate is 50%. Sure let's talk here

GrandmaGotGuns said:
If you are talking about gsi fix then im not sure that it'll work. I tried patching other gsi's for specifically efor xynos but the success rate is 50%. Sure let's talk here
Click to expand...
Click to collapse
What I say is not a patch, it is one of the phh oberlays for aosp gsi, after I have time I will try to make one, but that overlay would only be for the a51, not for another Samsung
If it is about gsi I am relatively knowledgeable about that, although as far as I know it was not necessary to use this zip to enter gsi, I think the super partition must be modified to install gsi

LichtEstarossx said:
What I say is not a patch, it is one of the phh oberlays for aosp gsi, after I have time I will try to make one, but that overlay would only be for the a51, not for another Samsung
If it is about gsi I am relatively knowledgeable about that, although as far as I know it was not necessary to use this zip to enter gsi, I think the super partition must be modified to install gsi
Click to expand...
Click to collapse
I attach my telegram username in case you need something more specific.
(nicopizza) Add the @

Can someone plz assist........I got the rom installed on issues
Root chkr says I'm rooted but substratum says I'm not Magisk I don't think I have the patch img. for it..... plz can someone hlp

Flashing GSI ROMs onto Your Nord N10 5G

DISCLAIMER!!!
Any lost data, bricked device or issues caused by attempting everything below is not my fault. You assume responsibility of your own actions. This has ONLY BEEN TESTED ON A BE2026!! You have been warned!
What You'll Need
Full Fastboot/ADB installed, system wide helps
-- My method is use the ADB Quick Installer (here: ADB Reborn), then also download the platform-tools and put everything in the ADB Folder (here: Select for your OS)
A GSI ROM
-- So far, only tested /e/OS DeGoogled GSI ROM, which is Android 10 based. ZERO issues thus far (here, arm64 ab: CLICKY) this rom does have issues with Wifi if you patch the boot.img with Magisk. Recommend testing 11 Based GSI's instead like LeOS which is based off of eOS
GAPPS if you so choose
Stock vbMeta.img
-- found here from OnePlus: OnePlus Software ... just select the Nord N10 and click download. or find it on a post here
Video instructions
text instructions
Instructions
1.) Download your selected GSI ROM, GAPPS (if needed), Magisk Manager, stock firmware and make sure ADB is system wide installed
2.) Unlock your bootloader
-- 2a.) Go to Settings, then About phone, tap Build number a bunch to enable developer settings
-- 2b.) Go back and select System, then Developer Settings, enable USB Debugging and OEM Unlock
-- 2c.) Plug in device, give PC developer control, and reboot to bootloader with "adb reboot bootloader"
-- 2d.) Once in bootloader mode, use "fastboot flashing unlock" to unlock the bootloader. Device will wipe and reboot to system
3.) Plug your Device into your computer, open Command prompt and type the following command. It may ask for Debugging permission on device, select yes
Code:
adb reboot bootloader
4.) Now that you're back on the Bootloader, you can use fastboot commands to get started flashing your GSI, first command to enter is
Code:
fastboot reboot fastboot
5.) You're now in Fastbootd, this allows for easier flashing. You now need your vbmeta.img. Use the command below
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
6.) Reboot fastbootd with the command from step 4, then use the commands below once rebooted
Code:
fastboot erase system
fastboot delete-logical-partition product
fastboot flash system GSI.img
fastboot -w
fastboot reboot
7.) You should now have your GSI flashed onto your device! That simple
Do NOT patch the boot.img with Magisk Manager and flash it. It breaks Wifi and Bluetooth on every single GSI Right now. If I find a work around, I will post it here.
How to Root your GSI Based ROM and keep Wifi Working!!
1.) Go to the PixelExperience ROM page and download just the Custom Recovery (here: PixelExperience Post)
2.) Once you have the recovery, reboot to bootloader
Code:
adb reboot bootloader
3.) Flash the recovery
Code:
fastboot flash recovery recovery.img
4.) Reboot to recovery, then download MagiskManager APK from Github (just follow along, I promise, here: Magisk)
5.) Select Apply Update by USB in the Recovery, and sideload with the Magisk APK (it works, trust me)
Code:
adb sideload MagiskManager.apk
6.) Reboot device, select the Magisk Icon and you're Rooted and ROM'd with working Wifi!

Thanks for the nice guide; I currently have a few problems right with installing this resurrection remix GSI:
1) I can't seem to get gapps installed on the GSI. There's never enough space, and due to the weird way the partitions on the N10 work, I can't resize the system partition in order to fit them in. Do you have any solutions for this problem?
2) I've created an overlay for the N10 in order to obtain auto brightness. It works well, but stops working after the first or second reboot. Again, do you have any solutions for this problem?
Thanks in advance.

Generic123. said:
Thanks for the nice guide; I currently have a few problems right with installing this resurrection remix GSI:
1) I can't seem to get gapps installed on the GSI. There's never enough space, and due to the weird way the partitions on the N10 work, I can't resize the system partition in order to fit them in. Do you have any solutions for this problem?
2) I've created an overlay for the N10 in order to obtain auto brightness. It works well, but stops working after the first or second reboot. Again, do you have any solutions for this problem?
Thanks in advance.
Click to expand...
Click to collapse
Personally I don't use any ROMs that have Google in them at all, so flashing gaps is something I don't think I can help you with. You could try my root method, but instead of flashing for root, Flash the gapps zip file. I found the method to root this completely by mistake. And it just happened to be the only way that worked
I did also notice that no matter what I do the screen is exceptionally bright on this phone even at its lowest setting. I have yet to try to find a solution for this because it discovered that the Sim slot on my phone is bad so I went back to my razor phone because now I have to warranty my phone

KaptinBoxxi said:
Personally I don't use any ROMs that have Google in them at all, so flashing gaps is something I don't think I can help you with. You could try my root method, but instead of flashing for root, Flash the gapps zip file. I found the method to root this completely by mistake. And it just happened to be the only way that worked
I did also notice that no matter what I do the screen is exceptionally bright on this phone even at its lowest setting. I have yet to try to find a solution for this because it discovered that the Sim slot on my phone is bad so I went back to my razor phone because now I have to warranty my phone
Click to expand...
Click to collapse
Ah, I used to own the RP2. Sold it because the battery life for my device was so mediocre. Anyways, I don't think it's possible to install GAPPS separately; they have to be integrated into what GSI I want to install or I just can't get them to fit. It seems like the traditional partitions like system have been combined into a single "super" partition. Also, when your N10 comes back from repair, you can try this overlay I've built. It should fix auto-brightness and maybe fixes the brightness curve(so the lowest setting should be much less bright).

Generic123. said:
Ah, I used to own the RP2. Sold it because the battery life for my device was so mediocre. Anyways, I don't think it's possible to install GAPPS separately; they have to be integrated into what GSI I want to install or I just can't get them to fit. It seems like the traditional partitions like system have been combined into a single "super" partition. Also, when your N10 comes back from repair, you can try this overlay I've built. It should fix auto-brightness and maybe fixes the brightness curve(so the lowest setting should be much less bright).
Click to expand...
Click to collapse
I disable auto-brightness entirely, but its still exceptionally bright. Its so weird. I still have it, haven't sent it in yet, so I'll give it a shot soon
Actually just realized its the GSI I'm using, the sim card doesn't work. Gonna try a different gsi and see what happens

I learned a lot with this tutorial. Thank you very much.
I'll begin to try some GSI roms now and see which one adapts best for me. I don't use Google either, so this GSI project was like finding a gold mine next door ha ha ha.
Thank you again.
EDIT: I was too optimistic, because following this guide only takes me to this error
Code:
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
What can I do to avoid this?
Thank you again.

bbabel said:
I learned a lot with this tutorial. Thank you very much.
I'll begin to try some GSI roms now and see which one adapts best for me. I don't use Google either, so this GSI project was like finding a gold mine next door ha ha ha.
Thank you again.
EDIT: I was too optimistic, because following this guide only takes me to this error
Code:
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
What can I do to avoid this?
Thank you again.
Click to expand...
Click to collapse
I suggest this method instead

MetaruSonikkuX said:
I suggest this method instead
Click to expand...
Click to collapse
I tried that method and also failed. I noticed when the script was working that it had the same errors like me: every file the script tried to flash to slot a was followed by FAILED (remote: 'Not enough space to resize partition').
So I decided to restore everything with this tool (and downgrade to Android 11 in the process) and now this guide works as it should. Right now I'm trying to use Havoc OS and the future looks bright
Thank you.

bbabel said:
I tried that method and also failed. I noticed when the script was working that it had the same errors like me: every file the script tried to flash to slot a was followed by FAILED (remote: 'Not enough space to resize partition').
So I decided to restore everything with this tool (and downgrade to Android 11 in the process) and now this guide works as it should. Right now I'm trying to use Havoc OS and the future looks bright
Thank you.
Click to expand...
Click to collapse
Could you post your experience? I tried LoS 18.1 and couldn't get microg installed, then tried AOSP 11 with gapps and kept getting a google authentication error.

MetaruSonikkuX said:
Could you post your experience? I tried LoS 18.1 and couldn't get microg installed, then tried AOSP 11 with gapps and kept getting a google authentication error.
Click to expand...
Click to collapse
You have to use GSIs with GAPPS in them to get gapps for now. no way around it

MetaruSonikkuX said:
Could you post your experience? I tried LoS 18.1 and couldn't get microg installed, then tried AOSP 11 with gapps and kept getting a google authentication error.
Click to expand...
Click to collapse
As KaptinBoxxi says, look for a GSI rom with GAPPS included, otherwise you'll have a lot of problems. I'd start for Pixel Experience but you can look for other roms here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list

Generic123. said:
Ah, I used to own the RP2. Sold it because the battery life for my device was so mediocre. Anyways, I don't think it's possible to install GAPPS separately; they have to be integrated into what GSI I want to install or I just can't get them to fit. It seems like the traditional partitions like system have been combined into a single "super" partition. Also, when your N10 comes back from repair, you can try this overlay I've built. It should fix auto-brightness and maybe fixes the brightness curve(so the lowest setting should be much less bright).
Click to expand...
Click to collapse
Is there a tutorial on making these that you followed? The one I found on phh wiki didn't go so well

[GUIDE] [ROOT] Fix the Qualcomm CrashDump: Keep your data, apps and retain root.

This will not work if your phone bricked after updating to Android 12. You should use the MSM in this case. This guide details downgrading to an earlier version of Android 11 FROM a newer Android 11. You have been warned.
This evening after updating my phone (installing to inactive slot + flashing with Magisk as I have done many times before), I restarted only to receive a Qualcomm CrashDump.
Unlike what I've read online, my one seemed to be a bit more severe. I could not boot into recovery mode (black screen; had to power phone off) and entering Fastboot did not fix the issue. After spending several hours reading through XDA, Stack Overflow, various other sites etc I finally managed to get it fixed. Not only that, but I kept ALL my data AND my root. It's like nothing ever happened.
The issues I faced:
- Mistakenly had USB debugging off (which cannot be enabled when your phone is soft bricked). This made using ADB for initial diagnostics virtually impossible
- Recovery mode showed a black screen; not accessible.
- Installing TWRP, only to find my device passcode (PIN) wasn't allowing me to decrypt my phone data so I could make a backup
- My phone was buggered
How I solved it: Given recovery mode was blank, I flashed TWRP to my recovery drive via Fastboot to bring it back. Because USB debugging was OFF and TWRP wasn't decrypting my data (meaning I couldn't back up any data or download the ROM to my internal storage without wiping it), I activated ADB Sideload within TWRP and then used this to downgrade my version of OxygenOS! After a reboot I received the Qualcomm error one more time, before it continued to boot into OxygenOS with all my data intact.
Your bootloader should already be unlocked. If it isn't, chances are you will be saying goodbye to your data
These steps may not work for everybody, but I wanted to give back what I learned from this, and it was rather unconventional and against the grain of what others have suggested. With that said, do so at your own risk.
This is a simple guide. I will explain the tools you will need and how to fix the issue. Anything beyond that (i.e. installing SDK platform tools) can be researched.
This is written assuming you are on Windows, although the steps are generally quite similar.
Tools Needed:
A computer to download and install:
- SDK Platform Tools/ADB (https://developer.android.com/studio/releases/platform-tools)
- TWRP for OnePlus 8 Pro (https://forum.xda-developers.com/t/...wrp-for-oneplus-8-8pro-official-beta.4341707/)
- OnePlus 8 Pro Drivers (You will need this installed if it isn't already for your phone to appear in SDK Platform Tools. You may need to disable driver signature enforcement on Windows 10)
- The version of OxygenOS you were running before the CrashDump occurred (https://forum.xda-developers.com/t/oneplus-8-pro-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4084315/)
Steps to take - Initial Setup and Installation of TWRP:
1. Download everything above and then install SDK Platform Tools + OnePlus 8 Pro Drivers if you don't already have them.
2. Enter Fastboot mode on your phone and then connect it to the computer.
3. Ensure the TWRP .img file is in the same directory as your SDK Platform Tools install
4. Open up command prompt with SDK Platform Tools installed and type in
Code:
fastboot devices
Confirm your device ID appears along with "fastboot" beside it.
4. If the device is being recognised, we're ready to install TWRP. Note: Remember your Bootloader must be unlocked for the next steps. While in Fastboot mode, your phone will tell you if your bootloader is locked or unlocked. Now that we've confirmed it is unlocked, Type in:
Code:
fastboot flash recovery_a twrpname.img
followed by:
Code:
fastboot flash recovery_b twrpname.img
5. You can now boot into recovery mode! On your phone, use the volume keys to navigate and choose Recovery so you can enter TWRP
Downgrading to an older version:
When I installed TWRP, I was horrified to see that I couldn't decrypt my phone with my pin code. Apparently this is an ongoing problem with TWRP and the ability to decrypt your phone data varies between devices and builds of TWRP.
1. Now that you have entered TWRP, enter the "Advanced" settings and enable "ADB Sideload".
2. On the computer, type in
Code:
adb devices
. You should see your device appear.
3. Ensure the OxygenOS file is in the same directory as your SDK Platform Tools install
4. Type in
Code:
adb sideload updatename.zip
and let it flash to your phone.
And that's it! Reboot your phone. You may receive the Qualcomm error one last time, so kiss that sucker goodbye with a final reboot (I pressed power + volume up but then it continued to boot as normal; much to my surprise) and you should be good to go.
Hope this helps. This is my first ever guide, but my phone bricked itself this afternoon and it took me 3-4 hours of research to figure out what to do. This community played its role in helping me, and I'm sure someone out there will appreciate this information - definitely wanted to give back. I didn't see any information like this outside of wiping the phone entirely... I'm pretty stubborn and didn't want to do that.
This is definitely a "dirty flash", although given I couldn't even boot into the updated version, I would say a downgrade is definitely just fine in this instance.

I assume that you where using Android 11?
Because in the current situation with android 12 and hard bricking your phone with fastboot flashing this guide is potentially dangerous. As far as i know you should not flash twrp to android 12 right now.
Please correct me if i mixed things up here or if i am wrong. Its better to loose data and use MSM if you are concerned.
You might wanna include this guide in case someone needs to read it before doing anything.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Anyway thanks for your effort here.

xtcislove said:
I assume that you where using Android 11?
Because in the current situation with android 12 and hard bricking your phone with fastboot flashing this guide is potentially dangerous. As far as i know you should not flash twrp to android 12 right now.
Please correct me if i mixed things up here or if i am wrong. Its better to loose data and use MSM if you are concerned.
You might wanna include this guide in case someone needs to read it before doing anything.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Anyway thanks for your effort here.
Click to expand...
Click to collapse
Thank you and you're right. I've added this warning to the top of the post!

Develop Bugs

welcome