[ROM][A51] HAVOC OS for Samsung Galaxy A51 [GSI] - Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot

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

Related

[RECOVERY][OFFICIAL] TWRP for Galaxy S9 (Exynos)

Thread moved to https://forum.xda-developers.com/galaxy-s9/samsung-galaxy-s9--s9-cross-device-development/twrp-exynos-t3763464.
Changelog:
Note that this page only includes device-specific changes. For global TWRP changes, go to twrp.me.
Mar 16, 2018 (twrp-3.2.1-1):
Add system_image, vendor_image
Rename display name of /odm to "Carrier Configs"
Mar 15, 2018:
Initial version
Guides:
Be aware that Android Verified Boot requires data (including those in internal storage) to be cleared after you unlocked bootloader and flash custom binaries. ("to protect user data, all state transitions wipe the data partitions and ask the user for confirmation before data is deleted." - https://source.android.com/security/verifiedboot/verified-boot)
It is normal to get prompts like "Integrity verification failed. You have to reset the device to factory settings."
However, this will only happen when there is "state transition" so only when you switch from locked to unlocked or vice versa.
Part 1 - HOW-TO FLASH TWRP:
1. In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
2. Go to Settings -> Developer options and enable OEM Unlock option.
Notice: This is "state transition" mentioned eailier.
3. Download and Install Samsung Mobile Phones Drivers.
- Option 1: Download and Install Smart Switch for PC.
- Option 2: Download and Install standalone driver package.
4. Download and extract Odin (Samsung's Flash Tool) to your computer.
5. Download a .tar image of TWRP.
6. Reboot your device to download mode.
- Hold [VOLUME DOWN] + [BIXBY] + [POWER] for approx. 15 seconds.
- Read the warning carefully.
- If you agree, press [VOLUME UP] to get into Download mode. If you don't agree, STOP.
7. Open Odin and place that TWRP tar file in the [AP] slot.
8. Connect your phone.
9. Hold [VOLUME UP] + [BIXBY] + [POWER] on your phone and then press start on Odin.
10. Wait for the phone to reboot. DO NOT release [VOLUME UP] + [BIXBY] + [POWER] or you may not reboot into TWRP.
Part 2 - HOW-TO INITIALIZE TWRP: (for new phones)
1. If you completed Part 1 successfully, you should be in TWRP now. At this point, you will reach the screen asking you if you want to allow system modifications.
2. Select "Keep /system RO". (Don't swipe right or you may not be able to boot into system if you failed to complete next steps. However, you can swipe right to allow modifications if you are confident that you can complete next steps.)
3. Go to "Wipe" menu of TWRP and you will find "Format Data". Press "Format Data" and type "yes" to continue.
4. Go to "Reboot" menu and Press "Recovery" to reboot TWRP.
5. Download the special dm-verity and force encryption disabler zip on your computer.
6. Transfer the zip to your phone.
- Option 1: MTP: Connect your phone with computer and just copy the zip to internal storage. (similar to how you transfer files when in system.)
- Option 2: ADB: Connect your phone with computer and run command "adb push /path/to/zip /sdcard/".
- Option 3: External SD: Copy the zip to an external SD and then insert the card to your phone.
7. Go to "Install" menu of TWRP and flash the zip.
TWRP is initialized and fully functional at this stage.
jesec said:
Now you can either reboot into system or root, flash custom ROMs via TWRP.
Click to expand...
Click to collapse
In theory you can, but so far no one including myself has been able to root from this.
See this thread https://forum.xda-developers.com/galaxy-s9/development/twrp-samsung-s9-t3763548/
I wiped my data for nothing!
Wow that was fast twrp already.
Nice work Jesec and thank you:thumbup:
Now lets see how long till some dummy asks if it works on the snapdragon lol
sent from my Pixel 2 XL or Note FE
@jesec if this twrp is becoming the official one I suggest you to include some of my features/fixes as for example img flash to specific partitions, OTG fix and more (also people on the s9+ thread reported that usb wasn't working), check my device tree here.
Have a nice day!
Can we flash SuperSU/Magisk instead of the dm-verity disabler? To root as well as for disabling dm-verity at the same time?
Tkkg1994 said:
@jesec if this twrp is becoming the official one I suggest you to include some of my features/fixes as for example img flash to specific partitions, OTG fix and more (also people on the s9+ thread reported that usb wasn't working), check my device tree here.
Have a nice day!
Click to expand...
Click to collapse
Please follow the contribution and code review process of TWRP if you want to contribute.
I will review the changes.
After following the instructions exactly in the OP, I flashed SuperSU v2.82-SR5-20171001224502. My S9 is rooted and everything is working great!
Thanks
(NOTE to North Americans: Don't get your hopes up, although I am in Canada, I have the Exynos version SM-G960F)
flar2 said:
After following the instructions exactly in the OP, I flashed SuperSU v2.82-SR5-20171001224502. My S9 is rooted and everything is working great!
Thanks
(NOTE to North Americans: Don't get your hopes up, although I am in Canada, I have the Exynos version SM-G960F)
Click to expand...
Click to collapse
Will we see a kernel of yours ?
I mean after the news that AOSP GSI images are booting, one of the greatest kernel developer coming to S9 would be like the cherry on the top.
Paradoxxx said:
Will we see a kernel of yours ?
I mean after the news that AOSP GSI images are booting, one of the greatest kernel developer coming to S9 would be like the cherry on the top.
Click to expand...
Click to collapse
Maybe. I got this phone mostly for testing Button Mapper and High Brightness Mode. I couldn't resist trying to build a kernel this morning. It booted after a couple tries, but there was no wifi.
flar2 said:
Maybe. I got this phone mostly for testing Button Mapper and High Brightness Mode. I couldn't resist trying to build a kernel this morning. It booted after a couple tries, but there was no wifi.
Click to expand...
Click to collapse
Sounds like a good start to me
I'm sure Samsung people, and myself would love some kernel magic.
For both Samsung and AOSP flavors
https://www.xda-developers.com/samsung-galaxy-s9-aosp-android-oreo-project-treble/
flar2 said:
Maybe. I got this phone mostly for testing Button Mapper and High Brightness Mode. I couldn't resist trying to build a kernel this morning. It booted after a couple tries, but there was no wifi.
Click to expand...
Click to collapse
It is regarding an unpatched fimc , we had this issue on s8
Fennec_1 said:
It is regarding an unpatched fimc , we had this issue on s8
Click to expand...
Click to collapse
I'm guessing this involves editing a firmware binary?
(Sorry for OT, though it is development related)
flar2 said:
I'm guessing this involves editing a firmware binary?
(Sorry for OT, though it is development related)
Click to expand...
Click to collapse
Yup, im not sure about which fimc-<name>.bin needed to be patched on s9
Although this wont be a problem if you running gsi
Fennec_1 said:
It is regarding an unpatched fimc , we had this issue on s8
Click to expand...
Click to collapse
flar2 said:
I'm guessing this involves editing a firmware binary?
(Sorry for OT, though it is development related)
Click to expand...
Click to collapse
Fennec_1 said:
Yup, im not sure about which fimc-<name>.bin needed to be patched on s9
Although this wont be a problem if you running gsi
Click to expand...
Click to collapse
That was for camera issues, the wifi issue is secure storage related.
mwilky said:
That was for camera issues, the wifi issue is secure storage related.
Click to expand...
Click to collapse
Ah, thanks for correcting me
I've had a few issues with FRP randomly being triggered and not allowing TWRP to boot at all. Still not sure what causes it (might be because I changed my google account password) but I've successfully been able to reflash stock without losing the data partition, so you can re-root without losing anything. Had to remove the USERDATA image from the stock AP tar file to not wipe USERDATA tho.
flar2 said:
Maybe. I got this phone mostly for testing Button Mapper and High Brightness Mode. I couldn't resist trying to build a kernel this morning. It booted after a couple tries, but there was no wifi.
Click to expand...
Click to collapse
Change wifi paths in config

[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

[17Jun20][Guide] [P/Q]How to root Note10/Note 10+ & Flash TWRP (Exynos only)

How to Root Samsung Galaxy Note 10+ & Flash TWRP (Exynos Only)
NOTICE :
Before you move further, make clear that rooting device -
- Your warranty will be void
- Some of functions may not work on rooted device, some function may get back with un rooting, some may never.
- All your data on device will be lost
- Flashing custom binaries may brick (Usually soft but can be hard brick too) your device, so follow it on your own risk!
If you are ready with condition, move further -
Click to expand...
Click to collapse
Important : Since android Q, there is changes in rooting process, specially if you needs root with TWRP, So here I am dividing this guide in two parts.
1.Root with self preparing files (No TWRP) - Here you needs to patch stock files yourself. No TWRP installed.
2.Root with TWRP - You needs to just flash pre-patched files, Here you needs to have ROM installed same base as per files available. Though mostly latest verson will be available.
PART 1 : (Root Pie/Q base with magisk with patching files yourself, No TWRP)
Before moving to root device, must read every single instruction given below as any small mistake can lead to fail to achieve root or may brick the device.
A.Preparing Root files
You need to patch file to flash using Odin to root device.
1. Download stock firmware for your device (google search will give you many sites to download it) some common are e.g. Sammobile, Samfirmware tool)
you need to download file according your region and model (Dial *#1234# will give you details of existing firmware, download accordingly)
2. Once you finish download, extract files and keep all files on PC. From extracted files a file with name AP_[device_model_sw_ver].tar.md5 copy to your device.
3.Download Latest Magisk Manager and Install to your device
4.Open Magisk Manager - Magisk (first one) - Install - select to "Select and Patch file" - Navigate file you have copied to device (AP_[device_model_sw_ver].tar.md5)
5.Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
6.Copy patched file magisk_patched.tar to Your PC
7.Download latest Odin (one is attached to end of this post) and extract to a folder on PC (I recommend on desktop)
Now next step is to modification on device
B. Unlocking Bootloader
This is a basic step to root device. Go to settings - about phone - Software Information - tap multiple times on "Build number" - This will open developer option.
Now in settings at the end, you will have new option "Developer options" - look for OEM unlocking - Enable it.
(PS : If you don't see this option then you may need to wait up to 7 days or more to appear or may be on some operator you will get it never. Without this option you can not root your device, sorry!)
Once you have enable OEM unlock option, switch off your device and reboot to download mode.
To put device in download mode - Press Volume Up & then Press Volume Down (Keep holding both) and connect device to PC with USB cable
When device start to download mode,long press volume up to unlock the bootloader. This will wipe your data and automatically reboot
Now let finish setup and again enable developer options (as said above), and confirm that the OEM unlocking option exists and grayed out!
If it is not then you can not root device!
Once you see this option and greyed out, you are ready to flash custom binary and root your device
C.Installation (Flashing) custom binaries
1. Switch off the device and reboot to download mode (As said earlier) and select volume up to continue
2. Open Odin (downloaded from above instruction) as administrator
Select magisk_patched.tar file you have patched (as above instruction copied to PC) for AP tab of Odin
Select BL,CP and CSC file (Extract from stock firmware you have downloaded) with according respective tab of Odin (This is important, DON'T flash only magisk_patched.tar )
3.From Odin option - uncheck Auto Reboot option
4.Now start flashing and wait till it finish. When you see a PASS sign on Odin, disconnect device.
Now magisk is successfully finished but yet you need to follow instructions below.
D. Factory reset & Boot with magisk
After disconnecting device, keep holding Vol down + Side key to exit from download mode.
Here is very important - when you see device reboot As soon as the screen turns off, immediately press Volume Up + Side Key to boot to recovery partition. continue pressing the volume up button until you see the stock recovery screen.
In the stock recovery menu, use volume buttons to navigate through menus, and the power button to select the option. Select Wipe data/factory reset to wipe the data of the device.
Select Reboot system now, and immediately press Volume Up + Side Key. After seeing the bootloader warning screen, release all buttons so it can boot to the system.
The device will automatically reboot for the first time it boots. This is completely normal and done by design.After the device is booted up, do the usual initial setup. You shall see Magisk Manager in your app drawer; if not, manually install the APK you downloaded and continue to the next step. The app would be a stub and it shall automatically upgrade to the full Magisk Manager when you open it.
Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Voila! Enjoy Magisk
PART 2 : (Root Q base with TWRP)
This requires to have your device on same base as per base of pre-patch files. I am giving link below of my ROM
http://www.mediafire.com/folder/d4ugie4yadxu6/N975F - Click link - First select your device (N970/N975/N976) - download file Instructions_Root_TWRP_BootloopFix.pdf
This file have complete details about how to root with stock recovery/TWRP. Also all required patched files will be available in "Q" folder of your device section,
Also "Q" folder have file BASE_N97*.txt - Name of this file indicates Model and base used for patched files, you should have same base installed.
Important :
Due to the fact that some devices no longer uses ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to boot to recovery every time if you want Magisk. Since both Magisk and recovery lives in the same partition, what you actually end up getting when you choose to boot to recovery will be determined by how long you press volume up.
(Powering up normally) → (System with NO Magisk)
(OEM Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
(OEM Recovery Key Combo) → (Splash screen) → (Keep pressing volume up) → (Actual recovery)
For more details read Installation guide by @topjohnwu from Here
All credit and thanks go to
@topjohnwu for magisk & Guide.
geiti94 for TWRP Here OP & Source
ianmacd for latest TWRP - Here OP & Source
Happy rooting!
Xposed
Just tried and eDxposed working fine.
- Install EdXposed installer
- from magisk download install Ritu-core module
- from magisk download install Ritu - EDxposed (yahfa)
Done.
We strongly recommend to make EFS backup as soon as you root device and store it to safer place
Don't you lose some Samsung function when you root and even relock the bootloader?
MrPhilo said:
Don't you lose some Samsung function when you root and even relock the bootloader?
Click to expand...
Click to collapse
Who cares?
Development can't go without this.
We developer need to risk it. No way.
Nice, already patched the rom to flash with odin. What is the button combination for recovery ?
Did that for a friend of mine on the S10e, guess the steps are all the same ??
Nice, so you will start to make roms ?
Keep it coming :laugh:
optx said:
Nice, already patched the rom to flash with odin. What is the button combination for recovery ?
Did that for a friend of mine on the S10e, guess the steps are all the same ??
Click to expand...
Click to collapse
OP updated for combo key
dr.ketan said:
OP updated for combo key
Click to expand...
Click to collapse
Many thanks, now i just have to wait for the Note 10+ to arrive in a few hours :highfive:
dr.ketan said:
Who cares?
Development can't go without this.
We developer need to risk it. No way.
Click to expand...
Click to collapse
Waiting for your guide, twrp, magisk and so on...
I am not developer, just tester, but still need root...
Dr Ketan. Most Welcome My Bro. Follow you since Note 9. U rock my bro :good:
namfat said:
Waiting for your guide, twrp, magisk and so on...
I am not developer, just tester, but still need root...
Click to expand...
Click to collapse
Twrp not available and possible only after samsung release kernel source code. Great news is @ianmacd getting N10 who known for twrp development. :good:
dr.ketan said:
Twrp not available and possible only after samsung release kernel source code. Great news is @ianmacd getting N10 who known for twrp development. :good:
Click to expand...
Click to collapse
That's really good to hear.
With you and the guy you've mentioned we have everything we need.
Cheers!
Did you have the OEM unlock right away in Developer options ? Cant see it on mine...
First Phone ever that has no OEM unlock right away ...
dr.ketan said:
Twrp not available and possible only after samsung release kernel source code. Great news is @ianmacd getting N10 who known for twrp development. :good:
Click to expand...
Click to collapse
OK then, please share root instruction first.
I dont know if N10 have the same problem but it happened with latest base on S10 5G that only using stock recovery if need rooted.
optx said:
Did you have the OEM unlock right away in Developer options ? Cant see it on mine...
First Phone ever that has no OEM unlock right away ...
Click to expand...
Click to collapse
My device have OEM unlock option available. If you dont have, maybe you need to wait for 7 days.
OP Updated with full instruction about how to root.
Kindly go through detail before proceed.
I'm assuming this is for Exynos version ONLY?
No where do I see this prerequisite posted anywhere but has always been in the past.
cpufrost said:
I'm assuming this is for Exynos version ONLY?
No where do I see this prerequisite posted anywhere but has always been in the past.
Click to expand...
Click to collapse
I have added to title but prerequisite is having OEM unlock enable which I believe not having on snapdragon isn't?
dr.ketan said:
I have added to title but prerequisite is having OEM unlock enable which I believe not having on snapdragon isn't?
Click to expand...
Click to collapse
So far with the SD when you go into developer mode there is no OEM unlock and I doubt it will show up later.
Don't know what is wrong. I have OEM turned on, Downloaded latest magisk manager, flashed all 4 parts. It did not work. If I flash stock, all is fine. Any clues ?
Pinu'u said:
Don't know what is wrong. I have OEM turned on, Downloaded latest magisk manager, flashed all 4 parts. It did not work. If I flash stock, all is fine. Any clues ?
Click to expand...
Click to collapse
OEM lock should be turned off AFAIK
Thx, will give it a try after flashing back stock.Irritating that OP says turn on ...

Redmi Note 8 Pro Guide [Firmwares | ROOT CN/GLOBAL | TWRP Recovery]

Redmi Note 8 Pro
[Begonia]
[Global Version Only]​
WARNING: Before attempting to root your device, do note that by unlocking your bootloader and modifying your device with root, ROMs, etc... you are risking voiding your warranty! I am NOT responsible for what you do to your device either, so follow these instructions at your own risk. Make sure you know what you're doing, it's best to understand the process rather than just copy and paste commands and such.
Firmwares
Global Stable
V10.4.1.0.PGGMIXM
V10.4.2.0 to V11.0.10
V11.0.1.0 PGGMIXM
V11.0.3.0 PGGMIXM
V11.0.4.0 PGGMIXM
V11.0.6.0
China Stable
V10.4.4.0.PGGCNXM
V10.4.6.0.PGGCNXM
V10.4.8.0.PGGCNXM
V10.4.9.0.PGGCNXM
V10.4.10.0.PGGCNXM
V10.4.11.0.PGGCNXM
V11.0.1.0QGGCNXM
China Beta
V9.9.25
V9.10.17
India Stable
V10.4.3.0.PGGINXM
V11.0.1.0 PGGINXM
Europe (EEA)
V10.4.5.0.PGGEUXM
Indonesia
V10.4.2.0.PGGIDXM
V11.0.1.0PGGIDXM
Russia
V10.4.2.0.PGGRUXM
USB Drivers
Download
Unlock Bootloader
Enable OEM Unlocking
Unlock Here
Installing TWRP Recovery and ROOT
Enable USB Debugging - Goto Settings / Additional settings / Developer options / USB Debugging & USB debugging (Security settings) - Enable (If you have not activated Developer options, then Goto Settings / About phone / tap MIUI version 7 times - now developer options enabled.
Global Version
GLOBAL firmware V10.4.5.0.PGGEUXM only
Drivers installed properly
Enabled USB Debugging (enabled developers menu)
1. Turn Off
2. Go to Fastboot mode (Volume - + Power)
3. Connect to the PC
4. Download and extract in C drive, "Run as administrator" and execute "ifelixit+FLASHER+TOOLKIT+Begonia.bat".
5. Choose 1 (TWRP recovery) and enter or Choose 2 (Root Only)
Immediately disconnect the phone from the PC, otherwise it will go to reboot on command and the stock recovery will be restored.
6. Put the Minimal ADB and Fastboot in C: of your PC.
Transfer the Recovery.img in Fastboot folder
Open Fastboot folder and Press Shift+Right Click and Select Open Command Window Here at the CMD type fastboot devices and enter (check if it's recognized the device).
7. Type fastboot flash recovery recovery.img and enter (TWRP will be installed)
8. Disconnect the phone from the PC, hold the Power button as the screen goes blank immediately hold Volume + the TWRP splash screen will appear and disappear still hold the button when the TWRP splash screen appears a second time release Volume +. If Chinese language change to English. If TWRP will ask you the password (this means that there is DATA encryption)click on CANCEL and get to the main screen.
We go to the mount, put check on data, system, vendor, nvdata and MicroSD card (if the phone has a memory card).
Press home to return to the main screen Choose Advanced-File Manager item >system_root / system / folder at the bottom there is a recovery_fromboot.p file delete it.
Go back to Advanced and select Close AVB2.0 and flash the archive with a swipe to the right.
Again, we go along the Advanced-File Manager path in the root, look for the supersu folder in it, select the SuperSu_installer.zip fileand flash it with a swipe to the right. This is an archive from Magisk_19.4 it will patch boot. The firmware of this archive should go WITHOUT a single error, all lines should be white and at the end of DONE. If everything was done without errors in the TWRP select the Reboot-System. The first boot will be a little long and Don't Panic when boot up check the Magisk Manager>Settings>Update Settings>Stable Channel.
Stock boot IMG for V10.4.5.0.PGGEUXM just in case bootloop
TWRP for Begonia
If error occurs..
1. Go to Minimal ADB and Fastboot in C: of your PC. Open Fastboot folder and Press Shift+Right Click and Select Open Command Window Here at the CMD type fastboot devices and enter (check if it's recognized the device).
2. Enter the following commands: fastboot flash boot boot.img and Enter then fastboot flash recovery recovery.img and Enter. We have flashed clean boot and TWRP.
3. Disconnect the phone from the PC, hold the Power button as the screen goes blank immediately hold Volume + the TWRP splash screen will appear and disappear still hold the button when the TWRP splash screen appears a second time release Volume +. The recovery_fromboot.p file is already deleted earlier.
5. Go to Mount in TWRP check data, system, vendor, nvdata and now you can decrypt DATA by formatting in TWRP Wipe-Fotmat Data, write yes and swipe.
6. Disconnect the phone from the PC, hold the Power button as the screen goes blank immediately hold Volume + the TWRP splash screen will appear and disappear still hold the button when the TWRP splash screen appears a second time release Volume +. If Chinese language change to English. If TWRP will ask you the password (this means that there is DATA encryption)click on CANCEL and get to the main screen.
We go to the mount, put check on data, system, vendor, nvdata and MicroSD card (if the phone has a memory card).
Press home to return to the main screen Choose Advanced-File Manager item >system_root / system / folder at the bottom there is a recovery_fromboot.p file delete it.
Go back to Advanced and select Close AVB2.0 and flash the archive with a swipe to the right.
Again, we go along the Advanced-File Manager path in the root, look for the supersu folder in it, select the SuperSu_installer.zip fileand flash it with a swipe to the right. This is an archive from Magisk_19.4 it will patch boot. The firmware of this archive should go WITHOUT a single error, all lines should be white and at the end of DONE. If everything was done without errors in the TWRP select the Reboot-System. The first boot will be a little long and Don't Panic when boot up check the Magisk Manager>Settings>Update Settings>Stable Channel.
Proof of Video that Redmi Note 8 Pro Rooted
https://www.youtube.com/watch?v=P4rBUT9qR-0&feature=youtu.be​
Contributors
Nikas
esleer
Xakep1993
SPIRITic
m3lbrunton
Lyelik74
@topjohnwu
TWRP Community
XDA Community
Xiaomi Community
How to Root Redmi Note 8 Pro Chinese Version
Redmi Note 8 Pro
[Begonia]
[Chinese Version Only]​
How to Root and installing Google Pay
Download
Magisk-release.zip
Magisk-uninstaller
Magisk app release apk
1. Download magisk-uninstaller.zip and magisk-release.zip and transfer in MicroSD
2. Reboot to TWRP Recovery
3. Install and look for the supersu folder>select the file SuperSu_instsller.zip and install.
4. Make Wipe, Advanced Wipe, Dalvik/Art Cache, Data and Cache and swipe
5. Make Wipe and Format Data
6. Mount the SD card, install magisk-uninstaller.zip to remove the old Magisk
7. Install magisk-release.zip Install the new Magisk v20.2
8. Advanced > File Manager >system_root / system > Delete the recovery_fromboot.p file
9. Advanced (put 2 checkmarks) Close AVB2.0
10. Advanced (put 2 ticks) RM Force encrypt
11. Reboot System
12. Pass authorization, install the Magisk app-release.apk
13. Click in the application: Check SafeNet status
Installing Google Pay
Download
Google Pay Module
1. Download in the Google Pay market
2. Download the Gpay.zip module for Magisk.
3. Open Magisk Manager>Modules and install Gpay.zip module and reboot
4. Open Magisk Hide
5. Look for Google Pay and Google Services Framework and check then close the application
6. Launch Google Pay and enter your data and card details.
7. The bank will check and wait for the confirmation code via SMS.
9. For GPay to work you must configure the lock with a password or pattern.
Gcam Stable for Redmi Note 8 Pro
GCam Stable for Redmin Note 8 Pro
Download:
GCam Stable
Changelog:
Stable release for Redmi Note 8 Pro!
-> Fixed excessive noise on aux cameras (thanks to Savitar).
-> Separate AWB settings for lenses.
-> Opening settings from aux cameras is not crashing anymore but lens will be reseted to main after exiting settings (need to use proper config wyroczen_rn8pro_3.xml)
Settings:
- Configs for this version
GCam for Redmi Note 8 Pro
There are two versions of Google camera available:
Google camera mode
Night Sight
PhotoSphere
Photobooth
Slow Motion
RAW support
HDR+
Motion
Panorama
Lens Blur
Google Lens
Portrait
What's not working
Google Camera 6.1.021
Portrait mode
Video mode
Slow Motion
Night Sight
Google Camera 5.1.018
All working
Download 6.1.021
Download 5.1.018
Contributors
Arnova8G2
BSG
GPay in Redmi Note 8 Pro
Instructions
1. Download GPay in Playstore (Don't open it)
2. Go to Magisk Manager > Magisk Hide > GPay
3. Install GPay Magisk Module and reboot
4. Open GPay and Bind a card.
Nice
Not working, bootloop. To fix bootloop, need to flash original boot.img - need to put original boot.img from ROM we have in adb folder and run command "fastboot flash boot boot.img".
Before posting such tutorials I suggest to check is it even working, because on chinese version of device this will NOT WORK.
chudy88 said:
Not working, bootloop. To fix bootloop, need to flash original boot.img - need to put original boot.img from ROM we have in adb folder and run command "fastboot flash boot boot.img".
Before posting such tutorials I suggest to check is it even working, because on chinese version of device this will NOT WORK.
Click to expand...
Click to collapse
And this is not a Chinese version tutorials.
Read above before doing some things.
WARNING: Before attempting to root your device, do note that by unlocking your bootloader and modifying your device with root, ROMs, etc... you are risking voiding your warranty! I am NOT responsible for what you do to your device either, so follow these instructions at your own risk. Make sure you know what you're doing, it's best to understand the process rather than just copy and paste commands and such.
Did you read about it?
madsponge26 said:
And this is not a Chinese version tutorials.
Click to expand...
Click to collapse
Where do you wrote it? I don't see. You'd better fix this guide, bacause now everyone with chinese device, if they do what u wrote here, will have a bootloop cause of you.
Did't work. Still loop the boot screen.
After do that ,it couldn't boot to system because the boot.img.
wuxeon said:
Did't work. Still loop the boot screen.
After do that ,it couldn't boot to system because the boot.img.
Click to expand...
Click to collapse
You have chinese device, or global or EU? Or other?
wuxeon said:
Did't work. Still loop the boot screen.
After do that ,it couldn't boot to system because the boot.img.
Click to expand...
Click to collapse
You should indicate Global or CN version? What boot.img?
chudy88 said:
Where do you wrote it? I don't see. You'd better fix this guide, bacause now everyone with chinese device, if they do what u wrote here, will have a bootloop cause of you.
Click to expand...
Click to collapse
It clearly states: [Global Version Only]
Can someone confirm it's working on global though? Including rooting?
donkyshot said:
It clearly states: [Global Version Only]
Click to expand...
Click to collapse
Yeah yeah, OP added it after my post. And it's not true - should work also on EU version.
That's why amateurs shouldn't make such threads.
chudy88 said:
Where do you wrote it? I don't see. You'd better fix this guide, bacause now everyone with chinese device, if they do what u wrote here, will have a bootloop cause of you.
Click to expand...
Click to collapse
And what's your contribution towards fixing the problem ? ?
Do some work instead of whining and waiting for others to give you the solution on a plate.
chudy88 said:
donkyshot said:
It clearly states: [Global Version Only]
yeah yeah, OP added it after my post
Click to expand...
Click to collapse
Okay sorry I didn't know.
This thread is obviously taken from here : http://c.mi.com/thread-2529429-1-0.html
I think it should be clearly stated in the thread as it is a more complete guide than this copy.
Click to expand...
Click to collapse
robbie_lpl said:
And what's your contribution towards fixing the problem ? ?
Do some work instead of whining and waiting for others to give you the solution on a plate.
Click to expand...
Click to collapse
Still better than breaking peoples phones. I'm warning potential users to not do this if they have chinese device, that's my contribution.
chudy88 said:
Still better than breaking peoples phones. I'm warning potential users to not do this if they have chinese device, that's my contribution.
Click to expand...
Click to collapse
When signing up for this website you sign a waiver that you are the sole person responsible for your device. Bootloops too.
Don't wanna have it bricked ? Don't mess with it.
Nobody's telling you to do that.
How about some gratitude and appreciation for those who take the time and trouble looking for a solution. Sponging off others work and whingening about it ?
Show some manners.
robbie_lpl said:
When signing up for this website you sign a waiver that you are the sole person responsible for your device. Bootloops too.
Don't wanna have it bricked ? Don't mess with it.
Nobody's telling you to do that.
How about some gratitude and appreciation for those who take the time and trouble looking for a solution. Sponging off others work and whingening about it ?
Show some manners.
Click to expand...
Click to collapse
What time, what solution?! Method posted by OP for this device is known for weeks already... And its just copied solution from other tutorials for older Xiaomi phones... I can bet that OP even didn't check it and I won't be surprised if he even don't have this phone... Besides, I still don't have solid proof that it works, even on global/EU version of device.
in the end this tutorial is working or not on global?
holymoz said:
in the end this tutorial is working or not on global?
Click to expand...
Click to collapse
Not working.

GUIDE: Install GSI Treble Roms on Honor 8X Max ARE-AL00

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?

Categories

Resources