Related
Hi All this is just a quick tutorial to help you all root your devices, on later firmwares
This 100% works ive done it over and over without any problems. I am currently on october patch latest firmware for my A105FN. As you may know Samsung have now added extra security meaning even if you have already unlocked your bootloader after you patch the firmware with magisk, flash patched firmware and reboot you will be greeted with that dreadfull message, Only official binaries allowed and your device will be locked and wont boot untill you reflash stock firmware again. The below will help get you out of the prenormal kg state, and save's you a 7 days waiting period as we dont have any TWRP available for our device at this time. Also note due to the extra security magisk cant be flashed with the whole firmware no more, as each time you flash the firmware your back at square 1.
Note: You will need 7-zip - google is your freind
1. Download odin: https://odindownloader.com/download/odin3-v3-13-3.
2. download the latest stock firmware for your device via SamMobile
3. Download latest Magisk Manager - https://www.google.co.uk/amp/s/forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/amp/
4. Flash latest firmware via odin and let device boot up and finish setting up.
5. Grab Your Firmware AP_A105FXXXX.tar.md5 remove the md5 so its a tar file makes it easier to work with. Copy it to your device storage.
6. Install latest magisk manager, and open check advanced settings to make sure recovery is checked, select install image / patch image and select the AP file you put on your device, magisk will patch and save as magisk_patched on your internal storage. Copy this back to your pc and extract it.
7. Download this https://forum.xda-developers.com/attachment.php?attachmentid=4818715&d=1568308074 thanks to @droidzer1 and extract the vbmeta.img.
8. Make a new folder on you pc it's temporary so you know where your files are. From the Ap magisk_patch.tar you extracted, copy the boot.img, recovery.img, and the downloaded vbmeta.img from step 7. And place them in the new folder you created, using your mouse select all 3 and right click select 7-zip add to archive, select tar format and name it magisk.tar.
9. Now we have all the files ready back to your device, if your bootloader is already unlocked skip this step and move to the next. For those that havent unlocked there bootloader 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, if the OEM switch is not there proceed to step 10. If it is and you enabled it it might ask you to factory reset if not it will be this way to complete the unlock bootloader.......
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.
10. Remove any account you have on your device go to settings, look for time and date automatic time zones, turn it off and set date back 8 days from now (example 30th today change date to 22nd) restart device. Now go straight back into automatic time zones settings and turn it back on. Again reboot device, when device reboots turn it off. You can now enter download mode and it should say checking instead of prenormal that means you good to go. Those of you that had no OEM switch in developer mode please now check.... if it's there enable it and go back to step 10 unlocking bootloader then proceed to step 11.
11. Open odin and select in the ap tab the magisk.tar you created earlier. Plug in your usb whilst holding vol-up and vol-down together to boot into download, press vol-up to proceed. Press start on odin and soon as it finishes and device reboots and you see the bootloader message hold power and vol-up until into stock recovery, select wipe factory reset then select reboot device, this the same as soon as you see bootloader unlocked message hold power and the vol-up together this time count to 7.... and release. Phone wont boot it will go blackscreen and reboot, dont worry this is normal, again do the exact same at bootloader unlocked msg screen hold power and vol-up count to 7... release, now phone will boot and you can set it up.
Note: you will need to reinstall magisk manager and on 1st open it will ask do to additional setup, let it do its thing, then device will reboot,
Remeber every time your device reboots you will have to do the power and vol-up to boot system with root.
I hope this guide help you and a big thank you to @afaneh92 for his original guide
thnaks man
how do i install twrp?
if it is possible, can i flash GSI?
tttt7hhhhjjjk said:
thnaks man
how do i install twrp?
if it is possible, can i flash GSI?
Click to expand...
Click to collapse
No the twrp that was made for our device, wont work with new versions of magisk, or any newer firmware we are going to have to wait until the the new kernel source is released by samsung unfortunatly, its impossible to say when or if they do.... so its just root for now.
mikeyb123 said:
No the twrp that was made for our device, wont work with new versions of magisk, or any newer firmware we are going to have to wait until the the new kernel source is released by samsung unfortunatly, its impossible to say when or if they do.... so its just root for now.
Click to expand...
Click to collapse
thanks for the fast reply man :good:
I gave up rooting this phone, ended up bootloop 3 times and always has to flash it to get the phone working again
timba123 said:
Any chimeratool tricks for no oem unlocking in developer options? On a102u1
Click to expand...
Click to collapse
no.. chimera tool cant unlock the bl on usa variants
hello Thanks for this method but not working after install again magisk manager , say app magisk is not installed and not root
When I was creating the magisk_patch file with magisk manager go to advanced settings and check recovery mode
is it correct?
THIS MIGHT WORK FOR YOUR DEVICE BUT IF ANY DAMAGE IS DONE TO YOUR DEVICE I AM NOT RESPONSIBLE! AND THIS WILL ONLY WORK ON A10. [SM-A105, SM-A107 AND MORE]
1. You need to install the exact firmware for your model onto your PC. [I recommend a website called updato or install samware and get the firmware there.]
2. Install Odin 3.14.1. If you already have it go to the next step.
3. Unlock your bootloader. If you have done this please go to the next step but if not please go to 3.a
3a. !UNLOCKING YOUR BOOTLOADER WILL FACTORY RESET YOUR DEVICE! - Go to settings and go to about phone, then tap the build number until a message comes on the bottom of the screen saying "You are now a developer!" or something close to that. Go to developer settings by going back to the settings menu and scrolling all the way down to see it. After going to developer options turn on "OEM Unlocking" and tap allow. Also just in case turn on USB Debugging. After that turn off your device. After your phone is turned off press "Volume Up"+ "Volume Down" and plug in a USB from your PC simultaneously, you should see a splash screen with a warning. Hold "Volume Up" for until 7 seconds or less and you should see another warning to confirm you want to unlock the bootloader. Press "Volume Up". You will get a warning when you boot up the phone, just press "Power".
4. After the phone booted up, do the normal setup. Then go to Chrome and download Magisk Manager.
5. Then, go to your pc, and locate the firmware you have downloaded and copy the AP tar file onto your phone.
6. Open magisk manager, tap install, and tap "Select and Patch a File".
7. Select the AP tar file you copied from your PC and wait for the process to be done.
8. You should see a new file called "magisk_patched.tar" and transfer the file to your PC.
9. Open Odin on your PC, and turn off your device and turn it on using "Volume Up", "Volume Down" and USB combination.
10. You should see the same warning sign. Just press "Volume Up" once. Do not hold it just press it once.
11. Your PC will make a sound alerting you that the phone has connected.
12. On the BL section on Odin, open your firmware location and select the file with BL in front of it.
13. On the AP section on Odin, open the "magisk_patched.tar" file you had transferred from the phone.
14. On the CP section on Odin, open your firmware location and select the file with CP in front of it.
15. On the CSC section on Odin, open your firmware location and select the file with CSC in front of it.
16. On Odin, look for a section called Options on the left-hand side. Click options, and turn off auto restart.
17. Click start and wait for the process to finish.
18. After the process is finished, please take the USB out.
19. !!THIS IS THE HARD PART!! - You need to hold down "Volume Down" and "Power". After the screen goes black immediately hold "Volume Up" and "Power". This will direct you to the stock recovery of the phone.
20. If the recovery says, "NO SYSTEM FOUND", don't worry as for then your phone is not A/B partitioned and that's okay and you will need to skip 21 for now and select Reboot System and do the normal setup. But if you can see options in the recovery, please use the "Volume keys" to scroll and "Power" to select. Select Wipe Data and confirm.
21. After the erasing process, just let the phone boot up, and do the setup.
22. Install Magisk Manager if your phone hasn't already downloaded it.
23. !!!FOR THE NON A/B PARTITIONED IF YOU ARE A/B PARTITIONED THEN PLEASE GO TO THE NEXT STEP!!! If you boot up normally - (System without magisk)
Booting up with "Volume Up" and "Power" - (System with magisk)
24. Enjoy Magisk!
If you have any questions please comment them down below!
Thanks to Topjohnwu for creating the method and MAKING magisk.
Downaroo said:
THIS MIGHT WORK FOR YOUR DEVICE BUT IF ANY DAMAGE IS DONE TO YOUR DEVICE I AM NOT RESPONSIBLE! AND THIS WILL ONLY WORK ON A10 ONLY [SM-A105xx].
1. You need to install the exact firmware for your model onto your PC. [I recommend a website called updato or install samware and get the firmware there.]
2. Install Odin 3.14.1. If you already have it go to the next step.
3. Unlock your bootloader. If you have done this please go to the next step but if not please go to 3.a
3a. !UNLOCKING YOUR BOOTLOADER WILL FACTORY RESET YOUR DEVICE! - Go to settings and go to about phone, then tap the build number until a message comes on the bottom of the screen saying "You are now a developer!" or something close to that. Go to developer settings by going back to the settings menu and scrolling all the way down to see it. After going to developer options turn on "OEM Unlocking" and tap allow. Also just in case turn on USB Debugging. After that turn off your device. After your phone is turned off press "Volume Up"+ "Volume Down" and plug in a USB from your PC simultaneously, you should see a splash screen with a warning. Hold "Volume Up" for until 7 seconds or less and you should see another warning to confirm you want to unlock the bootloader. Press "Volume Up". You will get a warning when you boot up the phone, just press "Power".
4. After the phone booted up, do the normal setup. Then go to Chrome and download Magisk Manager.
5. Then, go to your pc, and locate the firmware you have downloaded and copy the AP tar file onto your phone.
6. Open magisk manager, tap install, and tap "Select and Patch a File".
7. Select the AP tar file you copied from your PC and wait for the process to be done.
8. You should see a new file called "magisk_patched.tar" and transfer the file to your PC.
9. Open Odin on your PC, and turn off your device and turn it on using "Volume Up", "Volume Down" and USB combination.
10. You should see the same warning sign. Just press "Volume Up" once. Do not hold it just press it once.
11. Your PC will make a sound alerting you that the phone has connected.
12. On the BL section on Odin, open your firmware location and select the file with BL in front of it.
13. On the AP section on Odin, open the "magisk_patched.tar" file you had transferred from the phone.
14. On the CP section on Odin, open your firmware location and select the file with CP in front of it.
15. On the CSC section on Odin, open your firmware location and select the file with CSC in front of it.
16. On Odin, look for a section called Options on the left-hand side. Click options, and turn off auto restart.
17. Click start and wait for the process to finish.
18. After the process is finished, please take the USB out.
19. !!THIS IS THE HARD PART!! - You need to hold down "Volume Down" and "Power". After the screen goes black immediately hold "Volume Up" and "Power". This will direct you to the stock recovery of the phone.
20. If the recovery says, "NO SYSTEM FOUND", don't worry as for then your phone is not A/B partitioned and that's okay and you will need to skip 21 for now and select Reboot System and do the normal setup. But if you can see options in the recovery, please use the "Volume keys" to scroll and "Power" to select. Select Wipe Data and confirm.
21. After the erasing process, just let the phone boot up, and do the setup.
22. Install Magisk Manager if your phone hasn't already downloaded it.
23. !!!FOR THE NON A/B PARTITIONED IF YOU ARE A/B PARTITIONED THEN PLEASE GO TO THE NEXT STEP!!! If you boot up normally - (System without magisk)
Booting up with "Volume Up" and "Power" - (System with magisk)
24. Enjoy Magisk!
If you have any questions please comment them down below!
Click to expand...
Click to collapse
What about Samsung Galaxy A10s can you tell me please
Ragheb Aloqab said:
What about Samsung Galaxy A10s can you tell me please
Click to expand...
Click to collapse
I am sure you can, but before trying this method please take a full backup
works for a105m bit 5?
daniromerohn said:
works for a105m bit 5?
Click to expand...
Click to collapse
should work, but keep a backup just incase
Downaroo said:
THIS MIGHT WORK FOR YOUR DEVICE BUT IF ANY DAMAGE IS DONE TO YOUR DEVICE I AM NOT RESPONSIBLE! AND THIS WILL ONLY WORK ON A10. [SM-A105, SM-A107 AND MORE]
1. You need to install the exact firmware for your model onto your PC. [I recommend a website called updato or install samware and get the firmware there.]
2. Install Odin 3.14.1. If you already have it go to the next step.
3. Unlock your bootloader. If you have done this please go to the next step but if not please go to 3.a
3a. !UNLOCKING YOUR BOOTLOADER WILL FACTORY RESET YOUR DEVICE! - Go to settings and go to about phone, then tap the build number until a message comes on the bottom of the screen saying "You are now a developer!" or something close to that. Go to developer settings by going back to the settings menu and scrolling all the way down to see it. After going to developer options turn on "OEM Unlocking" and tap allow. Also just in case turn on USB Debugging. After that turn off your device. After your phone is turned off press "Volume Up"+ "Volume Down" and plug in a USB from your PC simultaneously, you should see a splash screen with a warning. Hold "Volume Up" for until 7 seconds or less and you should see another warning to confirm you want to unlock the bootloader. Press "Volume Up". You will get a warning when you boot up the phone, just press "Power".
4. After the phone booted up, do the normal setup. Then go to Chrome and download Magisk Manager.
5. Then, go to your pc, and locate the firmware you have downloaded and copy the AP tar file onto your phone.
6. Open magisk manager, tap install, and tap "Select and Patch a File".
7. Select the AP tar file you copied from your PC and wait for the process to be done.
8. You should see a new file called "magisk_patched.tar" and transfer the file to your PC.
9. Open Odin on your PC, and turn off your device and turn it on using "Volume Up", "Volume Down" and USB combination.
10. You should see the same warning sign. Just press "Volume Up" once. Do not hold it just press it once.
11. Your PC will make a sound alerting you that the phone has connected.
12. On the BL section on Odin, open your firmware location and select the file with BL in front of it.
13. On the AP section on Odin, open the "magisk_patched.tar" file you had transferred from the phone.
14. On the CP section on Odin, open your firmware location and select the file with CP in front of it.
15. On the CSC section on Odin, open your firmware location and select the file with CSC in front of it.
16. On Odin, look for a section called Options on the left-hand side. Click options, and turn off auto restart.
17. Click start and wait for the process to finish.
18. After the process is finished, please take the USB out.
19. !!THIS IS THE HARD PART!! - You need to hold down "Volume Down" and "Power". After the screen goes black immediately hold "Volume Up" and "Power". This will direct you to the stock recovery of the phone.
20. If the recovery says, "NO SYSTEM FOUND", don't worry as for then your phone is not A/B partitioned and that's okay and you will need to skip 21 for now and select Reboot System and do the normal setup. But if you can see options in the recovery, please use the "Volume keys" to scroll and "Power" to select. Select Wipe Data and confirm.
21. After the erasing process, just let the phone boot up, and do the setup.
22. Install Magisk Manager if your phone hasn't already downloaded it.
23. !!!FOR THE NON A/B PARTITIONED IF YOU ARE A/B PARTITIONED THEN PLEASE GO TO THE NEXT STEP!!! If you boot up normally - (System without magisk)
Booting up with "Volume Up" and "Power" - (System with magisk)
24. Enjoy Magisk!
If you have any questions please comment them down below!
Thanks to Topjohnwu for creating the method and MAKING magisk.
Click to expand...
Click to collapse
Does this work on the SM-A102U? Or is there any custom recovery for it?
Tyreethetruth said:
Does this work on the SM-A102U? Or is there any custom recovery for it?
Click to expand...
Click to collapse
Should work with any Samsung galaxy a10, so if it works, enjoy!
Odin keeps crashing when it is nearly complete
I have done this yet however it crashes when I follow your steps with a text box like "Odin Downloader has stop working". I have even gone to the extent where I have turned the magisk_patched.tar into a .tar.md5 file and still the same old error. How do I fix it?
If you require more info, I have a sm-a105fn/ds running android 9. Whenever it is on the "userdata" stage in odin, it crashes. I am using Odin 3 v3.13.1
error in boot and go back to download mode
Not working
I tried and once the flashing was done it rebooted to Download Mode instead and says "error verifying vbmeta image ok_not_signed (3)"
Bad Thread..
My older thread is way mor organized, and doesnt have the 16gb issue that you have... you just copied afanehs thread and made it look bad..
cmz6996 said:
Bad Thread..
My older thread is way mor organized, and doesnt have the 16gb issue that you have... you just copied afanehs thread and made it look bad..
Click to expand...
Click to collapse
I'm sorry, I wasn't copying as I thought of it myself but you're right it has the same steps as afanehs thread. Your thread is more organized and mine doesn't fix the 16gb issue that i had. I'm sorry for the inconvenience
Downaroo said:
I'm sorry, I wasn't copying as I thought of it myself but you're right it has the same steps as afanehs thread. Your thread is more organized and mine doesn't fix the 16gb issue that i had. I'm sorry for the inconvenience
Click to expand...
Click to collapse
No worries, I was abit rough, but try and fix it up. GL In the future!
What to do if it is stuck in recovery in odin. Help me please
.
I have a samsung galaxy a10e sm-a102u and I don't have oem unlocking as an option. Please help
Models:
SM-G770F or SM-G770F/DS
Frequently used key combinations keys:
FORCE REBOOT: Hold "Volume Down" and "Bixby/Power" button.
DOWNLOAD MODE: With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via a cable. Release the buttons after you see the "Warning" screen and then press "Volume Up"
RECOVERY MODE: With the phone off, hold "Volume Up" and "Bixby/Power" button.
Some facts:
1. S10 Lite uses dynamic partition which means there is only one "super" partition (instead of "system", "vendor", "product").
3. S10 Lite uses A-only partition which means there is only one set of system partition.
3. S10 Lite uses 2 stage init (2SI).
4. KNOX will be tripped after you flash a custom image. As a result, Samsung Pay and Secure Folder will become permanently (even after restore to stock firmware) unusable and your warranty may be voided. However, many jurisdictions including the European Union has law mandating manufacturer to provide hardware warranty even if user modifies the software.
5. Samsung devices are almost impossible to hard brick (render the device unusable without a hardware-level repair) as critical sections including the bootloader are well-protected. However, if you do things incorrectly, you may soft brick your phone, but that can usually be resolved by resetting to factory settings (wipe data and cache) or restoring to stock firmware (check out Stage 4).
Tools needed:
On your computer:
1. Odin 3.14.4 or newer
2. Samsung Android USB driver
3. SamFirm or other tools/websites to download official firmwares
4. Android Verified Boot Metadata Image with verification disabled (vbmeta_disabled.tar)
On your device:
1. Magisk Manager (Canary builds)
Stage 1: Know your model and carrier code (CSC)
1. Open "Settings"
2. Go to "About phone" -> "Software information"
3. Pay attention to "Service provider SW ver."
4. Starting with "SM-", for example "SM-G770F", that's the model of your phone.
5. Immediately after that, there are two 3-letter code, for example "OXM_PHE". The second 3-letter code "PHE" is your CSC.
6. Remember your model and CSC.
Stage 2: Unlock the bootloader
WARNING: ALL data on your device, including apps, settings and files in internal storage, will be lost. You do not need to repeat this if you didn't re-lock your bootloader.
1. Open "Settings"
2. Turn on "Developer mode" by going to "About phone" -> "Software information" and pressing "Build number" for several times.
3. Go to main menu of "Settings" and at the bottom you will find "Developer options"
4. Go to "Developer options". You will find a toggle "OEM unlocking". Turn it on.
5. Skip to step 8 if your device reboots to "Unlock bootloader?" screen. Make sure the toggle is on and then turn off your phone.
6. With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via a cable. (don't use charging only cables)
7. Release the buttons after you see the "Warning" screen. Then, hold the "Volume Up" button.
8. You will see "Unlock bootloader?" screen. Proceed and unlock your bootloader by pressing "Volume Up" button.
9. Your device will be reset to factory settings. Proceed with the Setup Wizard. Only connect to network via Wi-Fi or cellular and skip everything else. (to save time as data will be cleared again later.)
10. Repeat step 1-4 to validate that "OEM Unlocking" is on. If it is not, turn it on.
11. Repeat step 6.
12. Release the buttons after you see the "Warning" screen. This time, press (not hold) the "Volume Up" button.
13. You will see "Downloading" screen. On the top left, there are some important info.
14. Pay attention to "OEM LOCK" and "REACTIVATION LOCK". If both of them are "OFF", you have unlocked the bootloader.
Stage 3: Disable Android Verified Boot
1. Reboot to DOWNLOAD mode. If you are already in the download mode, skip to step 2.
2. Download Odin 3.14.4 or newer and make sure Samsung USB drivers are installed.
3. Open Odin and put the vbmeta_disabled.tar into USERDATA slot and click "Start"
4. Your device will reboot but it will not boot into system as vbmeta signature has changed.
5. Your device will reboot into RECOVERY mode automatically and prompt "You have to reset your device to factory settings". Use "Volume Up" or "Volume Down" button to move and "Power/Bixby" button to select. Confirm and reset the device to factory settings.
6. This is the last time the data on the device has to be cleared. Afterwards, if you don't re-lock bootloader or re-enable the Android Verified Boot, you will not lose your data. Be aware, a stock firmware package contains a Android Verified Boot Metadata Image (vbmeta.img) with verifications enabled. You will need to flash the vbmeta_disable image (put into USERDATA slot) along with the stock firmware (use BL, AP, CP, CSC slots) to make sure AVB is not re-enabled and the data is preserved.
With bootloader unlocked and AVB disabled, it is now possible to boot modified images on the device.
(Stage 4 and below are method to root your phone using your own odin files, if you wish to use a prepatched for a faster way to get root, go to OPTIONAL)
Stage 4: Obtain the official firmware and upgrade
1. Open SamFirm
2. Type in your model and your region (CSC) and click "Check Update"
3. "Download" and you will get a zip file.
4. Extract it and you will get 5 files (AP, BL, CP, CSC and HOME_CSC). All files are in tar format and can be opened by 7-Zip, WinRAR or other software.
5. Check the version code, for example (G770FXXU2BTD2). The last 4 letters (BTD2) indicates the version of the firmware. If the version is the same as your current firmware, skip to Stage 5.
Your data will be preserved if you do it right but it is good to have a backup.
6. Open Odin on your computer and reboot your device to DOWNLOAD mode.
7. Put AP, BL, CP files in their Odin slots. It takes time to verify the firmware so be patient.
8. Put HOME_CSC file in CSC slot. Be careful here. Unlike AP, BL, CP slots, you should NOT use CSC file for CSC slot. Instead, you should use HOME_CSC file. CSC file contains partition table (PIT) which will erase all your data.
9. Put vbmeta_disabled file in USERDATA slot so AVB remains disabled and your data preserved.
10. Click "Start" and wait for it to finish. Allow the device to boot into system to complete the upgrade process. Do NOT interrupt/disconnect phones/hold button. It needs to complete the process without interruption or strange BUGs may appear.
Stage 5: Extract boot (kernel) image from firmware
If you are having trouble creating tar file, you can skip to Stage 6. (NOT RECOMMENDED as AP is basically full system image. It is huge (takes long time to flash/process) and Magisk may misbehave.)
1. Extract boot.img.lz4 from the AP file.
2. Use 7-Zip to create a tar archive which contains boot.img.lz4 only. (or "tar cvf boot.tar boot.img.lz4")
Stage 6: Patch the boot (Kernel) image via Magisk
1. Transfer the tar archive (or the AP file if you skipped stage 5) to your phone.
2. Open Magisk Manager.
3. Click top-right "Install" button
4. Make sure "Recovery Mode" is off in Options.
5. Click "Next" and select "Select and Patch a File" in Method.
6. Select the file you transferred to your phone in step 1.
7. Click "Next" and "LET'S GO".
8. Transfer the patched file (in Download/magisk_patched.tar) to your computer
9. Reboot the device to DOWNLOAD mode.
10. Open Odin, put patched file to AP slot and then click "Start".
11. After reboot, Magisk is installed and you will have the root access.
HOW TO upgrade the firmware
Repeat stage 4-6.
(OPTIONAL) Use prepatched magisk boot
1. Make sure that the model and firmware version of the pre-patched image is the exact SAME as yours.
2. Open Odin on your computer.
3. Reboot your device to DOWNLOAD mode.
4. Put pre-patched image into AP slot.
5. "Start"
BEWARE: PREPATCHED BOOT ONLY TESTED ON BTD2 ONEUI 2.1 FIRMWARE
(https://drive.google.com/file/d/1chFXa2w_t2EgbfQIiVDOVR2KUeiwFpUs/view?usp=sharing)
Telegram Support Chat: https://t.me/joinchat/FrDuSBgUxDGSZ1vVmej7fw
*reserved*
Thank you for this amazing guide and the file without which it would not have been possible.
Be sure to join my TG group, if you are interested in AOSP, there's a lineage build testing currently running.
Thanks for this.
But it really is the most difficult way to root i have seen.. I'm not sure how many will try all this just to root a phone.
Awesome
sosimple said:
Thanks for this.
But it really is the most difficult way to root i have seen.. I'm not sure how many will try all this just to root a phone.
Click to expand...
Click to collapse
This will be done by absolutely everyone who wants to root his Galaxy S10 Lite. ABSOLUTLEY EVERYONE!
hey guys i ve just bought s10 lite and rootted it with method upside. but i was apple user for a 3 years before that i used to note 3-4-5 series and it was easy to rootable also i was getting useable stuff like grenify or nice equaliser type apps. ı would like to know how can i enjoy my phone with rooted ? for example i have iphone x with me still and its jailbreaked and there are repo sites that help to get to download app or modules to make you happy with your phone. do we have such stuff in android going on right now ? thanks again for rooting and helps.
4TheBesT said:
hey guys i ve just bought s10 lite and rootted it with method upside. but i was apple user for a 3 years before that i used to note 3-4-5 series and it was easy to rootable also i was getting useable stuff like grenify or nice equaliser type apps. ı would like to know how can i enjoy my phone with rooted ? for example i have iphone x with me still and its jailbreaked and there are repo sites that help to get to download app or modules to make you happy with your phone. do we have such stuff in android going on right now ? thanks again for rooting and helps.
Click to expand...
Click to collapse
If you are not sure what's the purpose of rooting a phone you shouldn't be doing it. "To make you happy with your phone" is a really subject question with no right answer, that depends on your specific needs.
If you ask about modules check out Magisk Modules.
---------- Post added at 09:57 PM ---------- Previous post was at 09:52 PM ----------
Hello, just to confirm that the steps detailed in this guide works, thanks OP, at least this gives us more freedom.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
no able to root with this method ! .. step ( v-meta disabler ) with system CP,AP,HOME CSC fail with official binary .. i follow you're steps !
i guess the file v-meta disabler u have attached is not compatible with my device ?! and yes i have same you'res BTD2 ONEUI 2.1 FIRMWARE
teenoo said:
This will be done by absolutely everyone who wants to root his Galaxy S10 Lite. ABSOLUTLEY EVERYONE!
Click to expand...
Click to collapse
In my case, I flashed latest FW (July 2020), Magisk Manager (the "install" buttons were not visible at first, but after some reboots they were). Created patched boot with Magisk Manager, unlocked bootloader (in settings & in bootloader), flashed modified boot image and it worked. At first boot, it restarted, and wen back to recovery, stating that system is corrupted, gave option to factory reset, so I did, it restarted again, and again, and then it booted fine. No VMBETA flashing needed. The trick, was (I suppose) doing the factory reset after flashing the modded kernel. Finally, when the phone booted, I did the usual first-run setup and enabled developer settings / adb installed Magisk Manager - it completed the setup, everything was fine after that.
Is there any way to unlock the bootloader and root SM-G770U1?
kamill85 said:
In my case, I flashed latest FW (July 2020), Magisk Manager (the "install" buttons were not visible at first, but after some reboots they were). Created patched boot with Magisk Manager, unlocked bootloader (in settings & in bootloader), flashed modified boot image and it worked. At first boot, it restarted, and wen back to recovery, stating that system is corrupted, gave option to factory reset, so I did, it restarted again, and again, and then it booted fine. No VMBETA flashing needed. The trick, was (I suppose) doing the factory reset after flashing the modded kernel. Finally, when the phone booted, I did the usual first-run setup and enabled developer settings / adb installed Magisk Manager - it completed the setup, everything was fine after that.
Click to expand...
Click to collapse
I was about to give up on the July update until I read this and tried a few more things. Bad internet caused missing "Install" buttons and I tried patched the WHOLE AP...instead of just patching a boot.tar like in Stage 5. So gooder internet, Odin-ing only the AP with the Magisk patched boot.tar, another wipe,
Code:
adb install .\MagiskManager-v7.5.1.apk
and I was rooty tooty.
I didn't care about burning everything on the phone. I think that some of the extra steps here were for trying to minimize the wipes. Thanks for the extra hope @kamill85 !
Are there download links for official images somewhere without paying? Everywhere i searched you needed to sign in and pay..
Thanks,
SamFirm
sosimple said:
Are there download links for official images somewhere without paying? Everywhere i searched you needed to sign in and pay..
Thanks,
Click to expand...
Click to collapse
Did you look up SamFirm like in the instructions? It pointed me to this page: https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 That says it's deprecated but it was able to get me the July 2020 FW for the S10e. I didn't try the other thing, Updato that it points you to. I ran the exe in the zip and pushed a few buttons and it worked for me. No waiting 20 hours. Hope that helps!
dim42 said:
Did you look up SamFirm like in the instructions? It pointed me to this page: https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 That says it's deprecated but it was able to get me the July 2020 FW for the S10e. I didn't try the other thing, Updato that it points you to. I ran the exe in the zip and pushed a few buttons and it worked for me. No waiting 20 hours. Hope that helps!
Click to expand...
Click to collapse
Thanks. What Deprecated meant? What iis the difference from original?
the show stopper said:
Is there any way to unlock the bootloader and root SM-G770U1?
Click to expand...
Click to collapse
+1
Also curious if anyone's gotten this working with the US version
So if i do this ill never ever be able to use Samsung pay ever again?
Vaughnn said:
Models:
SM-G770F or SM-G770F/DS
Frequently used key combinations keys:
FORCE REBOOT: Hold "Volume Down" and "Bixby/Power" button.
DOWNLOAD MODE: With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via a cable. Release the buttons after you see the "Warning" screen and then press "Volume Up"
RECOVERY MODE: With the phone off, hold "Volume Up" and "Bixby/Power" button.
Some facts:
1. S10 Lite uses dynamic partition which means there is only one "super" partition (instead of "system", "vendor", "product").
3. S10 Lite uses A-only partition which means there is only one set of system partition.
3. S10 Lite uses 2 stage init (2SI).
4. KNOX will be tripped after you flash a custom image. As a result, Samsung Pay and Secure Folder will become permanently (even after restore to stock firmware) unusable and your warranty may be voided. However, many jurisdictions including the European Union has law mandating manufacturer to provide hardware warranty even if user modifies the software.
5. Samsung devices are almost impossible to hard brick (render the device unusable without a hardware-level repair) as critical sections including the bootloader are well-protected. However, if you do things incorrectly, you may soft brick your phone, but that can usually be resolved by resetting to factory settings (wipe data and cache) or restoring to stock firmware (check out Stage 4).
Tools needed:
On your computer:
1. Odin 3.14.4 or newer
2. Samsung Android USB driver
3. SamFirm or other tools/websites to download official firmwares
4. Android Verified Boot Metadata Image with verification disabled (vbmeta_disabled.tar)
On your device:
1. Magisk Manager (Canary builds)
Stage 1: Know your model and carrier code (CSC)
1. Open "Settings"
2. Go to "About phone" -> "Software information"
3. Pay attention to "Service provider SW ver."
4. Starting with "SM-", for example "SM-G770F", that's the model of your phone.
5. Immediately after that, there are two 3-letter code, for example "OXM_PHE". The second 3-letter code "PHE" is your CSC.
6. Remember your model and CSC.
Stage 2: Unlock the bootloader
WARNING: ALL data on your device, including apps, settings and files in internal storage, will be lost. You do not need to repeat this if you didn't re-lock your bootloader.
1. Open "Settings"
2. Turn on "Developer mode" by going to "About phone" -> "Software information" and pressing "Build number" for several times.
3. Go to main menu of "Settings" and at the bottom you will find "Developer options"
4. Go to "Developer options". You will find a toggle "OEM unlocking". Turn it on.
5. Skip to step 8 if your device reboots to "Unlock bootloader?" screen. Make sure the toggle is on and then turn off your phone.
6. With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via a cable. (don't use charging only cables)
7. Release the buttons after you see the "Warning" screen. Then, hold the "Volume Up" button.
8. You will see "Unlock bootloader?" screen. Proceed and unlock your bootloader by pressing "Volume Up" button.
9. Your device will be reset to factory settings. Proceed with the Setup Wizard. Only connect to network via Wi-Fi or cellular and skip everything else. (to save time as data will be cleared again later.)
10. Repeat step 1-4 to validate that "OEM Unlocking" is on. If it is not, turn it on.
11. Repeat step 6.
12. Release the buttons after you see the "Warning" screen. This time, press (not hold) the "Volume Up" button.
13. You will see "Downloading" screen. On the top left, there are some important info.
14. Pay attention to "OEM LOCK" and "REACTIVATION LOCK". If both of them are "OFF", you have unlocked the bootloader.
Stage 3: Disable Android Verified Boot
1. Reboot to DOWNLOAD mode. If you are already in the download mode, skip to step 2.
2. Download Odin 3.14.4 or newer and make sure Samsung USB drivers are installed.
3. Open Odin and put the vbmeta_disabled.tar into USERDATA slot and click "Start"
4. Your device will reboot but it will not boot into system as vbmeta signature has changed.
5. Your device will reboot into RECOVERY mode automatically and prompt "You have to reset your device to factory settings". Use "Volume Up" or "Volume Down" button to move and "Power/Bixby" button to select. Confirm and reset the device to factory settings.
6. This is the last time the data on the device has to be cleared. Afterwards, if you don't re-lock bootloader or re-enable the Android Verified Boot, you will not lose your data. Be aware, a stock firmware package contains a Android Verified Boot Metadata Image (vbmeta.img) with verifications enabled. You will need to flash the vbmeta_disable image (put into USERDATA slot) along with the stock firmware (use BL, AP, CP, CSC slots) to make sure AVB is not re-enabled and the data is preserved.
With bootloader unlocked and AVB disabled, it is now possible to boot modified images on the device.
(Stage 4 and below are method to root your phone using your own odin files, if you wish to use a prepatched for a faster way to get root, go to OPTIONAL)
Stage 4: Obtain the official firmware and upgrade
1. Open SamFirm
2. Type in your model and your region (CSC) and click "Check Update"
3. "Download" and you will get a zip file.
4. Extract it and you will get 5 files (AP, BL, CP, CSC and HOME_CSC). All files are in tar format and can be opened by 7-Zip, WinRAR or other software.
5. Check the version code, for example (G770FXXU2BTD2). The last 4 letters (BTD2) indicates the version of the firmware. If the version is the same as your current firmware, skip to Stage 5.
Your data will be preserved if you do it right but it is good to have a backup.
6. Open Odin on your computer and reboot your device to DOWNLOAD mode.
7. Put AP, BL, CP files in their Odin slots. It takes time to verify the firmware so be patient.
8. Put HOME_CSC file in CSC slot. Be careful here. Unlike AP, BL, CP slots, you should NOT use CSC file for CSC slot. Instead, you should use HOME_CSC file. CSC file contains partition table (PIT) which will erase all your data.
9. Put vbmeta_disabled file in USERDATA slot so AVB remains disabled and your data preserved.
10. Click "Start" and wait for it to finish. Allow the device to boot into system to complete the upgrade process. Do NOT interrupt/disconnect phones/hold button. It needs to complete the process without interruption or strange BUGs may appear.
Stage 5: Extract boot (kernel) image from firmware
If you are having trouble creating tar file, you can skip to Stage 6. (NOT RECOMMENDED as AP is basically full system image. It is huge (takes long time to flash/process) and Magisk may misbehave.)
1. Extract boot.img.lz4 from the AP file.
2. Use 7-Zip to create a tar archive which contains boot.img.lz4 only. (or "tar cvf boot.tar boot.img.lz4")
Stage 6: Patch the boot (Kernel) image via Magisk
1. Transfer the tar archive (or the AP file if you skipped stage 5) to your phone.
2. Open Magisk Manager.
3. Click top-right "Install" button
4. Make sure "Recovery Mode" is off in Options.
5. Click "Next" and select "Select and Patch a File" in Method.
6. Select the file you transferred to your phone in step 1.
7. Click "Next" and "LET'S GO".
8. Transfer the patched file (in Download/magisk_patched.tar) to your computer
9. Reboot the device to DOWNLOAD mode.
10. Open Odin, put patched file to AP slot and then click "Start".
11. After reboot, Magisk is installed and you will have the root access.
HOW TO upgrade the firmware
Repeat stage 4-6.
(OPTIONAL) Use prepatched magisk boot
1. Make sure that the model and firmware version of the pre-patched image is the exact SAME as yours.
2. Open Odin on your computer.
3. Reboot your device to DOWNLOAD mode.
4. Put pre-patched image into AP slot.
5. "Start"
BEWARE: PREPATCHED BOOT ONLY TESTED ON BTD2 ONEUI 2.1 FIRMWARE
(https://drive.google.com/file/d/1chFXa2w_t2EgbfQIiVDOVR2KUeiwFpUs/view?usp=sharing)
Telegram Support Chat: https://t.me/joinchat/FrDuSBgUxDGSZ1vVmej7fw
Click to expand...
Click to collapse
Anyway to get to pass the safety nets?
Yes i pass safety net, but i use systemizer and with it i cant pass.
When I switch off systemizer in magisk I pass safety net
Hello,
I am sorry if this is annoying in any way. I have spent the whole day trying to figure out how to root my Samsung Galaxy A11 and already wiped it twice.
There is not TWRP custom recovery available for it. To my understanding so far, I need TWRP if I want to install custom ROMs. I really do not care about installing custom ROMs. I have been trying to figure out how to root using the stock ROM.
Everywhere I look it says that I need to patch the stock ROM before flashing it by patching the boot.img file in the stock ROM download. I have downloaded several GBs of ROMs over a very slow connection and none of them has the boot.img file. I have the tar.md5 files (AP, BL, CP, CSC) but not boot.img. How do I proceed in this situation?
My phone model: SM-A115F/DS
Baseband version: A115FXXU1ATG1
Country: Egypt
Any help will be much appreciated.
yomamabinlaggin said:
Hello,
I am sorry if this is annoying in any way. I have spent the whole day trying to figure out how to root my Samsung Galaxy A11 and already wiped it twice.
There is not TWRP custom recovery available for it. To my understanding so far, I need TWRP if I want to install custom ROMs. I really do not care about installing custom ROMs. I have been trying to figure out how to root using the stock ROM.
Everywhere I look it says that I need to patch the stock ROM before flashing it by patching the boot.img file in the stock ROM download. I have downloaded several GBs of ROMs over a very slow connection and none of them has the boot.img file. I have the tar.md5 files (AP, BL, CP, CSC) but not boot.img. How do I proceed in this situation?
My phone model: SM-A115F/DS
Baseband version: A115FXXU1ATG1
Country: Egypt
Any help will be much appreciated.
Click to expand...
Click to collapse
I have managed to find this saviour.
https://forum.xda-developers.com/showpost.php?p=79106875&postcount=6
I downloaded a random J6 firmware in another site.
You have to use 7zip software, it's free, much better than WinRar and supports tons of compression formats. Do these steps with 7zip:
-Unpack zip file.
-Rename the "*.tar.md5" to "*.tar".
-Open the ".tar" file and unpack "boot.img.lz4".
-Unpack "boot.img.lz4" file.
-It's done, you now have the "boot.img" file you were looking for
Click to expand...
Click to collapse
Just one thing to point out, 7zip did not work properly to extract the boot.img from boot.img.lz4. I used the solution in this answer. https://superuser.com/a/1533657
Now, let's see if I can patch the boot.img
How to ROOT and, but...
yomamabinlaggin said:
Hello,
I am sorry if this is annoying in any way. I have spent the whole day trying to figure out how to root my Samsung Galaxy A11 and already wiped it twice.
There is not TWRP custom recovery available for it. To my understanding so far, I need TWRP if I want to install custom ROMs. I really do not care about installing custom ROMs. I have been trying to figure out how to root using the stock ROM.
Everywhere I look it says that I need to patch the stock ROM before flashing it by patching the boot.img file in the stock ROM download. I have downloaded several GBs of ROMs over a very slow connection and none of them has the boot.img file. I have the tar.md5 files (AP, BL, CP, CSC) but not boot.img. How do I proceed in this situation?
My phone model: SM-A115F/DS
Baseband version: A115FXXU1ATG1
Country: Egypt
Any help will be much appreciated.
Click to expand...
Click to collapse
Hey there. I'm searchin' for TWRP for my A11 and no use.No one compile it and nobody can't write full f*****' guide how to build TWRP without any config file (or how to create 'em for building from 0). But honestly I'm not about TWRP.
Why do we need TWRP for Android 10!?
A: Samsung lock phones /system partition to Read-Only state. You can get root but you can't mount your partition as Read-Write, make changes in it. It's only waste of time.
How can I install ROOT for my samsung A**?
A: Very simple. I suggest you using Magisk Manager for it!
What do I need and what do I must do?
A:
1. You need unlock the bootloader of your phone (data will be lost).
2. You need original USB cable (from box of phone).
3. Yon need last firmware to your phone. (I'm using SamFirm or Frija)
4. Windows 7 or higher.
5. 7-Zip
6. Odin
How:
Stage I: Bootloader.
0. Remove all Google and Samsung Accounts
1. Make data backup (for recoverying)
2. Go to Settings -> Developer Options -> ADB Debug (set Enabled) (Search in web how to get Developer options Settings menu)
3. Go to Settings -> Developer Options -> OEM Unlock (set Enabled)
4. Turm off Phone and wait for 10 seconds.
5. Plug USB of Phone to your PC BUT PHON MYST BE UNPLUGGED!
6. Push and hold buttons: VOLUME UP and VOLUME DOWN and plug USB from PC to your Phone and still hold buttons!
7. When phon will be realy you'll see a light blue screen that ask you: Shall I unlock bootloader (Long press Volume UP), Shall I enter in download mode (short 'click' Volume Up) or I must turn off (Hold Volude Down)
8. Press and Hold VOLUME UP
9. On screen you'll se the message you'll unlock your bootloader... To hell Press POWER BUTTON.
10. Phone goes to reboot and start WIPING PROCESS!
11. That it. You unlocked bootloader. But will you install ROOT?
If so:
12. Make first setup of your phone but don't set google account and etc. Just make it working.
13. Go to Settings -> Developer Options -> ADB Debug (set Enabled)
14. Validate that's you've done everything right: Find OEM Unlock if toogle is gray and not responging to your actions then you've done right!
15. No download firware to your PC.
16. After you had downloaded firmware for your phone you'll fave few files you need file with prefix "AP_" open it with 7-Zip.
17. Get from it file: "boot.img.lz4" and put to some location at your PC.
18. Pack your "boot.img.lz4" with 7-Zip to "boot.img.lz4.tar" (YOU MUST USE *.TAR ARCHIVE TYPE)
19. Install Magisk Manager to your phone and put your archive "boot.img.lz4.tar" to location: Internal Memory/Download
20. Connect to WiFi and run Magisk Manager.
21. Make Kernel Patch with Magisk: Select: "Install Magisk" -> "Patch boot image" -> in file picker navigate and select "boot.img.lz4.tar"
22. (Magisk will do everything)
23. When it's done in folder "Internal Memory/Download" will be magisk_patched.tar copy it to your Windows.
24. (On PC) Run Odin as Administrator. And in tab "Options" unselect checkbox "Auto Reboot"
25. Turn off your phone and wait for 10 seconds, then Press and hold VOLUME UP and VOLUME DOWN and plug in your USB from PC to phone.
26. Phone will ask you what do need to do, just click VOLUME UP and you enter into Download mode
27. Odin must show you COM number.
28. Select as AP file "magisk_patched.tar" and press Start.
29. If you see PASS! in Odin - You've done! If ERR! then you failed to unlock the bootloader!
30. Now turn of fyour phone and enter into Recovery Mode (on turned off phone hold POWER + VOLUME UP)
30.a. If you failed to enter try in with ADB command: 'adb reboot recovery' (no quotes)
31. In Recovery Mode Make: Factory reset + Clear Cash partition.
32. Power on your phone. Again make FULL PHONE SETUP an reinstall Magisk Manager
33. PROFIT!
Spoiler: Quick Links
Official LineageOS 16.0 (15.02.2021)
.401 Stock Images (C432)
Stock Recovery
Stock E-recovery
Official TWRP (3.7.0)
Official TWRP (3.4.0-1)
Modified TWRP (3.4.0)
Heavily Modified TWRP (3.4.0)
Magisk Patched Recovery (25.2)
Magisk-Delta Patched Recovery (25.2-delta)
Stock Kernel (4.9.148)
Phenix Kernel (4.9.319 by Turex)
Phenix Permissive Kernel (4.9.319 by Iceows)
Phenix Permissive Kernel (4.9.235 by Abdelhay.ali)
Phenix Enforcing and Permissive Kernel for Android 13 (4.9.319 by Abdelhay.ali)
Selinux Rules for Android 13 (by Abdelhay.ali)
Everything Else (47GB)
Special key combos:
Power + Vol+ = Recovery Mode
While USB connected, Power + Vol+ = Erecovery Mode
While USB connected, Vol- = Fastboot
Plug USB while holding down Vol+ + Vol- = Download Mode
Power + Vol+ + Vol- = Force Dload
Flashing Any GSINote:Phh is "retiring". Community of builders created trebledroid initiative to keep his work alive. Don't expect same level of quality for a while.
Use vndklite variants.
At no point you need to wipe /data or any other partition. Just do factory reset.
If you want to backup via twrp you need to have encryption disabled.
Almost all chromium based browsers including chrome freeze after few minute of use. That is caused by DRM not working as intended in gsis. To fix it flash DRM fix.
Permissive kernel shouldn't be used daily. Please only use it for debugging purposes.
Prerequisites:
ADB and Fastboot Installed (1)
Any Arm64 AB GSI image (1) (2) (3) (4) (5)
Google apps package (Optional) (1) (2) (3) (4)
TWRP
Unlocked Bootloader
Spoiler: Android 12 and Below
Spoiler: GSI with GAPPS
Tick "Enable OEM Unlock" from developer options
Boot into fastboot: Hold vol- while usb connected and phone rebooting
Flash gsi image: fastboot flash system drag & drop img file to console
Flash Stock Recovery: fastboot flash recovery_ramdisk and drag & drop img file to console
Boot into recovery: power + vol+ while NOT connected to pc
Factory reset: Factory Reset > Type yes > Press power
Boot into system
Spoiler: Vanilla GSI + Gapps + Zips
Tick "Enable OEM Unlock" from developer options
Boot into fastboot: Hold vol- while usb connected and phone rebooting
Flash gsi image: fastboot flash system drag & drop img file to console
Flash Phenix Kernel (Optional): fastboot flash kernel and drag & drop img file to console
Flash this TWRP: fastboot flash recovery_ramdisk and drag & drop img file to console
Boot into recovery: power + vol+ while NOT connected to pc
Factory reset: Wipe > Swipe Factory Reset
Resize system: Wipe > Advanced Wipe > Tick System > Repair or Change File System > Swipe Resize File System
if it fails issue these commands from your computer:
adb shell "/sbin/e2fsck -fp /dev/block/platform/hi_mci.0/by-name/system"
adb shell "/sbin/resize2fs /dev/block/platform/hi_mci.0/by-name/system"
Encrypt or Decrypt /Data (Optional): Mount > Tick Vendor > adb push drag & drop fstab file to console /vendor/etc
Flash DRM fix (Optional): ''
Flash NFC fix (Optional / Might not Work): ''
Flash Gapps Zip (Optional): ''
Boot into system: Reboot > System
Spoiler: Android 13 and Beyond(?)
Tick "Enable OEM Unlock" from developer options
Boot into fastboot: Hold vol- while usb connected and phone rebooting
Flash gsi image: fastboot flash system drag & drop img file to console
Flash one of these kernel (Optional): fastboot flash kernel and drag & drop img file to console
Flash this TWRP: fastboot flash recovery_ramdisk and drag & drop img file to console
Boot into recovery: power + vol+ while NOT connected to pc
Factory reset: Wipe > Swipe Factory Reset
Flash this AIO fix : Advanced > ADB Sideload > Swipe to Start Sideload > Write adb sideload and drag & drop zip file to console
Flash Gapps Zip (Optional): ''
Boot into system: Reboot > System
Spoiler: Tweaks
Spoiler: TWRP on Erecovery, Magisk on Recovery Setup
Flash over to erecovery:
Boot into fastboot: Hold vol- while usb connected and phone rebooting
Flash one of these (1) (2) twrp images: fastboot flash recovery_ramdisk and drag & drop img file to console
Boot into twrp: power + vol+ while NOT connected to pc
Push twrp to /cache: adb push drag & drop img file to console /cache
Flash twrp to erecovery: Install > Install Image > Select twrp image from /cache folder > Pick erecovery_ramdisk partition > Swipe
After you set up your phone and made sure you don't need stock recovery, flash magisk:
Boot into fastboot: Hold vol- while usb connected and phone rebooting
Flash magisk patched image: fastboot flash recovery_ramdisk and drag & drop img file to console
From now on this is how you boot:
No keypress: System (Long yellow warning)
Power & Vol+ before Yellow Warning : System with magisk (Short yellow warning)
Vol+ on Yellow Warning : TWRP
If you want to return to stock erecovery, do these:
Boot into twrp
Push erecovery image to /cache: adb push drag & drop img file to console /cache
Flash erecovery to erecovery: Install > Install Image > Select erecovery image from /cache folder > Pick erecovery_ramdisk partition > Swipe
Spoiler: Passing Safetynet (For Android 12 and Below
Keep in mind that Safetynet is deprecated and Google is encouraging developers to switch to Play Integrity API. To pass safetynet you need to have 3 checkmarks, as such you'll need to follow all 3 instructions I'm about to give you.
Spoiler: Evaluation Type Basic
Disable "Spoof Pixel 5" & Enable Safetynet in phh options then reboot.
Download YASNAC from play store and check for "Evaluation Type" from result.
If it says Basic and others fail you can skip this part.
If test fails or doesn't finish do these:
Install Magisk
Enable Zygisk & Enforce denylist
Install Universal SafetyNet Fix module by kdrag0n
Now check YASNAC again. It should finish test and say Basic in evaluation type.
Spoiler: Basic Integrity Fail
This happens because root is detected most of the time.
If your GSI has Dynamic Root, uncheck root from phh settings.
If your GSI has SU, securize from phh settings.
If you had to flash magisk because of evaluation type, tick google play and google play services in denylist.
If those didn't fix, contact GSI maintainer.
Spoiler: CTS Profile Match Fail
This happens because build fingerprint is not play certified.
Make sure you have safetynet option ticked in phh settings and do these:
Edit /data/adb/phh/secure
Add these 2 lines to bottom:
resetprop_phh ro.build.fingerprint HUAWEI/ANE-LX1/HWANE:9/HUAWEIANE-L01/9.1.0.368C432:user/release-keys
resetprop_phh ro.build.version.security_patch 2020-08-01
Reboot and test again.
Everytime you untick safetynet you have to edit this file again. You can also pick any other fingerprint from here should you choose to. You need both fingerprint and patch date. If you want to simulate other devices add following lines:
resetprop_phh ro.product.brand HUAWEI
resetprop_phh ro.product.device HWANE
resetprop_phh ro.product.manufacturer HUAWEI
resetprop_phh ro.product.model ANE-LX1
resetprop_phh ro.product.name ANE-LX1
Spoiler: Passing Play Integrity (For Android 13 and Beyond)
If you want to pass it you're going to have to read this wall of text. I can't shorten it.
What is Play Integrity:
Google enforces Play Inregrity once your api level is set to 33 (android 13). I currently don't have enough information about it other than apps can decide which checks to perform on your device. One of those checks is called strong integrity. We can't pass strong integrity because it requires hardware backed checks which our device lack. However you can still fool some apps that don't enforce strong integrity.
How you can fool it:
Ever since magisk retired magiskhide, some forks have been made to keep it maintained and improved. One of those forks is Magisk Delta. Before you head over to it's github and install it, you still need to install a valid CTS fingerprint. Then you can install Magisk Delta.
Steps:
Disable Spoof Pixel 5 & Enable Safetynet from phh settings if they exist.
Add these 2 lines to bottom of /data/adb/phh/secure (create if it doesnt exist) & Reboot
resetprop_phh ro.build.fingerprint HUAWEI/ANE-LX1/HWANE:9/HUAWEIANE-L01/9.1.0.368C432:user/release-keys
resetprop_phh ro.build.version.security_patch 2020-08-01
If you have magisk :
- Download Magisk Delta apk
- Change .apk to .zip
- Install it as magisk module
If you don't have magisk :
- Download & install Magisk Delta apk
- Patch recovery_ramdisk & flash it via fastboot
Enable Zygisk and MagiskHide from Magisk Delta App
Install this module : https://github.com/HuskyDG/safetynet-integrity-fix/releases
MAKE SURE GMS IS NOT IN HIDELIST
Reboot and test safetynet. (Feel free to link any app that tests for Play Integrity)
Spoiler: I went back to EMUI, why it looks like aosp?
That happens because EMUI stores it's themes and few stock apps in /data/hw_init folder. When you factory reset with stock recovery, they are preserved. But when you use twrp to factory reset they are removed. Doing factory reset once from twrp is enough to make EMUI think it's corrupted, in acuality it isn't. To fix it you can either let EMUI update from system settings or you can download this, extract hw_init folder and push folder to /data from twrp with this command :
adb push drag & drop hw_init folder to console /data
Flashing LineageOS 16.0Note:Stock kernel from EMUI .300> have trouble with wifi. Use Phenix 4.9.319 or above to fix it.
Prerequisites:
ADB and Fastboot Installed (1)
Google apps package (Pick Pie or 9.0 editions) (1) (2) (3) (4)
LineageOS Zip (From Archive or From Mega)
Phenix Kernel (Else you won't have wi-fi)
TWRP (3.4.0 is needed for factory reset functionality)
Unlocked Bootloader
Spoiler: Steps
Tick "Enable OEM Unlock" from developer options
Boot into fastboot: Hold vol- while usb connected and phone rebooting
Flash this TWRP: fastboot flash recovery_ramdisk and drag & drop img file to console
Flash Phenix Kernel (Required for Wi-Fi): fastboot flash kernel and drag & drop img file to console
Boot into twrp: power + vol+ while NOT connected to pc
Flash lineage zip: Advanced > ADB Sideload > Swipe to Start Sideload > Write adb sideload and drag & drop zip file to console
Factory reset: Wipe > Swipe Factory Reset
Boot into Vanilla LineageOS or Keep following to flash gapps
Encrypt or Decrypt /Data (Optional): Mount > Tick Vendor > adb push drag & drop fstab file to console /vendor/etc
Flash gapps zip: Advanced > ADB Sideload > Swipe to Start Sideload > Write adb sideload and drag & drop zip file to console
Boot into system: Reboot > System
Getting Stock Firmware Files And DowngradingSources:
A certain russian site (linking is prohibited)
EMUI's System Updater (via root)
Firmware Finder (Revived)
HiSuite
Huawei Update Extractor
HuRUpdater Guide / HuRUpdater Download (For older builds)
HwOTA8 (For Emui 8)
Spoiler: Getting Individual Images
Firmware finder has been revived and you can use that to get your prefered cust or build.
If you need only one image not the whole build, I uploaded each one you'd typically need below.
CUST.img
DTS.img
ERECOVERY_KERNE.img
ERECOVERY_RAMDI.img
ERECOVERY_VBMET.img
ERECOVERY_VENDO.img
FASTBOOT.img
KERNEL.img
ODM.img
PRODUCT.img
RECOVERY_RAMDIS.img
RECOVERY_VBMETA.img
RECOVERY_VENDOR.img
SYSTEM.img
VBMETA.img
VENDOR.img
XLOADER.img
They are from .401 c432.
If you wiped /data once you probably won't have emui themes etc if you go back to emui. To fix that you can push hw_init folder (in data.7z) to /data. Not the contents of it, just put the folder in root of /data. It should be like this: /data/hw_init
Spoiler: Hisuite
Connect your phone to pc and open up hisuite. Check for updates and if it finds one it'll download following files update_full_base.zip, update_full_ANE-L01_hw_eu.zip and update_full_cust_ANE-L01_hw_eu.zip to your documents folder. update_full_base.zip file contains main UPDATE.APP. You can extract images from it with Huawei Update Extractor
Spoiler: EMUI's System Updater
Flash magisk patched image from quick links. After you get root in EMUI allow system updater to do its job and update. It'll ask to reboot, allow it. It will throw you back to system after reboot because recovery is not stock. Get a file manager that allows root access. Allow system updater to download again. But this time do not allow it to reboot. First one downloaded OTA, second one downloaded FullOTA. Which is better for archival purposes. After download is done go to /data/update with a root file explorer. Copy HwOUC folder to internal storage and from there to your pc. There should be 3 folders with numbers. You can find our main update_full_base.zip in one of them.
Spoiler: Downgrading
Spoiler: From EMUI 9 to EMUI 9
Spoiler: Using just the SYSTEM.IMG
Get files of your prefered build. I recommend build .278. Extract SYSTEM.IMG from UPDATE.APP via huawei update extractor and flash it with fastboot flash system . Factory reset with stock recovery then flash any TWRP except for the official ones. Official TWRPs freezes when wiping /data which is what we need to do. After wiping /data boot into system. You should have aosp background with square app icons if you did correctly. Check for system updates and it should find your current build. Download and install.
Spoiler: Using dload from Certain Russian Site
BOOTLOADER WILL RELOCK, DON'T DO THIS IF YOU DON't HAVE YOUR BL CODE
For this you need to have a sd card that is formated as exfat. Fat32 doesn't allow >4gb files so exfat is required. Download your prefered build from Androidhost.ru or mega link above. Inside the zip file you'll find a folder named dload. Extract this folder to somewhere and transfer it to your sd card. Folder structure should look like below. Hw_eu and L01/L21 will depend on your region and single/dual sim status. After this unplug your phone and shut it down. Start pressing vol- vol+ and power all at the same time. Different kind of yellow warning will appear and a screen with blue progress bar over black background will appear. If you downloaded correct variant for your phone it'll start progressing. After process is done you'll boot into stock emui with NO yellow warning. This is because your bootloader is locked. Do whatever you want at this point but remember, unlocking bootloader again will low level factory reset your phone.
-/storage/AAAA-BBBB/dload
---/update_sd
---/ANE-L01_hw_eu
---/ANE-L21_hw_eu
Spoiler: From EMUI 9 to EMUI 8
If I recall correctly there is only one way to do this. You can't dload between emui versions. You also need to be on stock emui for hisuite to function. Some people say a specific hisuite version is required but it wasn't the case for me. Plug your phone to pc, hisuite should show up beside your phone in drives section. Install it and open it. Do whatever it instructs you to function correctly. After you see your phone in app click Update button. Then click on "Earlier Versions". It'll show version 8.0.0.167 along with some warnings. Rest it pretty straightforward. Follow along and it'll return you back to emui 8. But if you're doing this to unlock your bootloader, build .167 is not enough. Exploit that dc-unlocker uses is patched in this version. So you have to roll back further. I had success with .125 build but up until .150 could work. Link to .125 build.
edit ? : Revised guide
Frax3r said:
Hello there! Alive parts of this forum is still filled with simple help requests so I decided to put together a simple all-in-one thread that basically covers most stuff. I don't wanna get into bootloader unlocking because right now only free way to do so is with potatoNV which I do not know how to use. Dc-unlocker is an option too but it is 4€ so pick your poison.Special key combos:
Power + Vol+ = Recovery Mode
While USB connected, Power + Vol+ = Erecovery Mode
While USB connected, Vol- = Fastboot
Plug USB while holding down Vol+ + Vol- = Download Mode
Power + Vol+ + Vol- = Force Dload
Flashing LineageOS 16.0Prerequisites:
Emui Version below 9.1.0.300
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Los16 zip
Official TWRP
Stock recovery_ramdis.img
Your choice of gapps zip
Steps:
Get the Prerequisites
I recommend sending los 16 zip, recovery_ramdis.img and gapps zip to sd card if possible
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send adb reboot bootloader command from console
After restart write fastboot flash recovery_ramdisk to console and drag twrp-3.5.2_9-0-anne.img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Allow modifications
Press Install and select los 16 zip file
If you want to disable encryption do it now
Press Install and press Install Image
Select and flash stock recovery_ramdis.img to recovery_ramdisk partition
Press Reboot and select shut down
Press and hold power + vol+ buttons until short yellow warning shows up
Select factory reset and type yes, while it is doing that plug the phone to pc
After factory reset is complete select reboot option and hold down vol- until you're at fastboot
Repeat step 6-7-8
Los 16 don't need to be resized so go to install and select gapps zip
Reboot to system
Flashing Any GSIPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
GSI image (1) (2)
Official TWRP
Stock recovery_ramdis.img
Your choice of gapps zip (Optional)
Notes:If you're gonna use Phh's AOSP11 and anything that based on it (with the exception of @eremitein's stuff), use arm64-ab-vndklite variant. For anything else use full vndk version. Full vndk version of Phh's AOSP11 does not allow you to resize system on any twrp.
Steps for gapps versions:
Get the Prerequisites
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send adb reboot bootloader command from console
After restart write fastboot flash system to console and drag gsi .img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
You should be at stock recovery_ramdisk, do a factory reset
You're good to boot up the system
Steps for vanilla versions with custom gapps:
Get the Prerequisites
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
If you want to disable encryption do it now
Send adb reboot bootloader command from console
After restart write fastboot flash system to console and drag gsi .img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
You should be at stock recovery_ramdisk, do a factory reset
Plug your phone back and press reboot from screen
While booting press and hold vol- button until you're at fastboot
Write fastboot flash recovery_ramdisk to console and drag twrp-3.5.2_9-0-anne.img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Allow modifications
Press Wipe, press Advanced Wipe, select System, press Repair or Change File System, press Resize File System, swipe to resize
Press Install, select and flash gapps zip
Reboot to system
Disable EncryptionPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Official TWRP
Stock recovery_ramdis.img
Notes:You can disable encryption at any step, even after booting, but in order to disable it you have to do a factory reset from stock recovery_ramdis. Because of this I recommend doing between flashing gsi and flashing gapps.
Steps:
Get the Prerequisites
Boot to TWRP (power + vol+ after shutting down)
Allow modifications
Press Mount, select Vendor
Connect phone to PC
You can do next part 2 ways, if you're good with command line interface use steps 7 through 11, if not skip to step 12
Type adb shell and press enter
Type nano /vendor/etc/fstab.hi6250 and press enter
Remove fileencryption=aes-256-xts:aes-256-cts part from 16th line, make sure there's only one comma between check and reservedsize
Press Ctrl + X then Y and press enter
Go to step 18
Type adb pull /vendor/etc/fstab.hi6250 and press enter
If you have adb in your $PATH go to your user profile folder, if not go to folder where adb.exe resides
Open fstab.hi6250 via a text editor (please use notepad++)
Remove fileencryption=aes-256-xts:aes-256-cts part from 16th line, make sure there's only one comma between check and reservedsize
Save file and open a command prompt
Send this command adb push ./fstab.hi6250 /vendor/etc/fstab.hi6250
View attachment 5422531
Now you need to do a factory reset with stock recovery_ramdis.img, if you have it installed go to step 21 if not do 19 or 20 first
If you have TWRP installed, press Install and press Install Image then select and flash stock recovery_ramdis.img to recovery_ramdisk partition
If not shut down phone, connect it to pc and hold down vol- until you're at fastboot, then write this command fastboot flash recovery_ramdisk and drag recovery_ramdis.img over to console then press enter
Shut down phone and unplug it from pc
Press and hold power+ vol+ until you see short yellow warning
Press Factory Reset and type yes
You've successfully decrypted your phone and you're good to boot up or flash gapps
Getting Stock Firmware Files And DowngradingPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Huawei Update Extractor
Firmware Zip (EMUI8 and EMUI9)
HiSuite
Erecovery
EMUI's System Updater (via root)
HuRUpdater Guide / HuRUpdater Download
HwOTA
Getting stock files are problematic because of huawei. Least shadiest way to get them are the hardest so bear with me.
Androidhost.ru : Click the EMUI9 from prerequisites and search p20 lite. You should get a wide variety of versions to pick from. Make sure to match the Cust in the file to yours if you don't know what you're doing. C432 for Europe for example. After you download the zip file open it up and find the dload folder. You can either get this folder and paste it right into your sd card to force dload or you can open this folder and extract update_sd.zip. Inside update_sd.zip you'll find a file named UPDATE.APP. Use Huawei Update Extractor to open this file and there you'll see all the partitions you need. If HUE gives error while opening it, go to settings and untick "Verify file checksum". You can extract .img files by right clicking and selecting extract option on each partition. Normally you can't open these .img files but after pushing them through simg2img you'll be able to explore them too. But lets be real if you need guides for this, all you need is recovery_ramdis.img.
Using Dload Folder : Your sd card can't be FAT32 for this. FAT32 by nature don't allow files larger than 4gb so you can't get this folder to your sd card. Format it to ExFat via any guide on the internet then copy the dload folder to your sd card's root. It can't be inside any folders. Then shut your phone and press Power + Vol+ + Vol- all at the same time. It'll boot to erecovery which'll check the integrity of files then install them regardless of your EMUI version. So it is a good way to downgrade. Keep in mind tho you can't dload back to emui 8 from emui 9. And any successful dload will lock your bootloader back.
Hisuite : You can actually get firmware files pretty easily with hisuite but it requires real work. You see, hisuite downloads firmware files right into your documents folder. Connect your phone to pc and open up hisuite. Check for updates and if it finds one it'll download following files update_full_base.zip, update_full_ANE-L01_hw_eu.zip and update_full_cust_ANE-L01_hw_eu.zip. It might not get all 3 files most of the time so you have to copy each of them and update a few versions consecutively to get them. Keep in mind, it deletes each update file after it is successful so make sure to make a copy of them some place else. I recommend reverting back to EMUI8 through hisuite and then updating it to latest one to get all files. It is tidious but you need to do this once. It doesnt update you to .370 from .132. It'll send you .132 then .200 then .368 then latest whatever. You can actually use these files with HuRu updater or HwOTA to manually update. Or you can get the UPDATE.APP inside them and extract images with Huawei Update Extractor.
Erecovery : This one requires some network knowledge and it'll only get you the latest version so I don't think it worth the hassle. You need a router that allows you to change dns address for DHCP clients. Which most of them do these days. Now you need to create and run a dns server on your pc. I recommend adguard home. Pihole works too. Use Windows Subsystem For Linux or Docker to install either of them. Once you get them up and working set them to log dns requests. I believe you know where this is going. Open your router's interface and enter adguard home/pihole ip address which maps back to your pc's local address. Check if it works or not by opening up few sites on your phone which should be connected to your wifi and isn't set up to use a different dns server. If all is good open up erecovery on your phone and connect to your wifi. If you set it up correctly it should get the latest version from huawei which will show up on your log. Use that url to download it to your pc and extract it same as others. There was a paid service that used this method to send specific versions to your erecovery.
EMUI's System Updater : This is tricky and my favorite. Get the official TWRP .img and patch it with magisk manager. Then flash it via fastboot. I know, "twrp and magisk? wtf?" just do it. It takes a long time to boot but it works don't question me right now. After you get root in EMUI allow system updater to do its job and update. It'll ask to reboot, allow it. It will throw you back to system after reboot cuz recovery is hijacked. duh. Get a file manager that allows root access. Allow system updater to download again. But this time do not allow it to reboot. First one downloaded OTA, second one downloaded FullOTA. Which is better for archival purposes. After download is done search for a folder named HwOUC in /system. Copy it to internal storage and from there to your pc. You can find our main UPDATE.APP inside update_full_base.zip. Other zips include cust and all that which HuRu and HwOTA requires.
MagiskPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Stock recovery_ramdis.img
Notes:Officially speaking magisk support for our device is dead. Magisk decided to retire magisk-in-recovery method which our phone uses. But hey it is still working without modifications unlike a-only devices so that's a win. As a foot note, you CAN use twrp image instead of stock recovery_ramdis.img but it'll take longer to boot. Using .380's recovery_ramdis.img on .278 build will not work. Make sure to match your EMUI build with ramdisk you're flashing. Ask me how I know.
Steps to install older version:
Get the Prerequisites
No, I mean literally just get the Prerequisites and thats it
Open up your browser and find a bin service (pastebin will suffice)
Create a paste with following
Code:
{
"app": {
"version": "8.0.7",
"versionCode": "4834",
"link": "https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk",
"note": "https://cdn.jsdelivr.net/gh/topjohnwu/[email protected]/app/src/main/res/raw/changelog.md"
},
"stub": {
"versionCode": "18",
"link": "https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/stub-release.apk"
},
"uninstaller": {
"link": "https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-uninstaller-20210117.zip"
},
"magisk": {
"version": "v21.4",
"versionCode": "21400",
"link": "https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-v21.4.zip",
"note": "https://topjohnwu.github.io/Magisk/releases/21400.md",
"md5": "ee6dd05579776e7de3a6077087846e53"
}
}
Get the paste's raw url
Take the recovery_ramdis.img to internal storage
Install magisk manager 8.0.7
Open it's settings and select custom channel
Write the raw url you just created
Allow it to check for updates and it'll find that 21.4 is the latest version
Click install and select recovery_ramdis.img
After it finishes patching get the magisk_patched.img to your pc
Get your phone to fastboot mode
After connecting to pc, write this fastboot flash recovery_ramdisk to console and drag magisk_patched.img over to console and press enter
Now if you enter recovery it'll boot to android with magisk but if you boot normally it will not detect magisk so each time you restart you have to use Power + Vol+ combo in order to get magisk
Remember to switch custom channel to stable channel if you want to receive updates.
I know that you can pretty much reduce the amount of flashing and restarting by flashing twrp to erecovery but since erecovery is a lifeline for most people here I decided not to get into that. But for those who are interested check this thread.
Edit: Grammar
Click to expand...
Click to collapse
I wish good luck to those who will use your guide .
Among other things, the HwOTA and HuRupdater methods have not worked since February (unless someone has the necessary files stored on the disk). Huawei changed servers and Firmware Finder is dead.
EMUI 8 firmware download doesn't work for the same reasons .
avenger.forsyth said:
I wish good luck to those who will use your guide .
Click to expand...
Click to collapse
Everyone has the right to write a guide, but the author must know what he is writing about. Guide made by the "copy/paste" method will not help anyone very much...
Frax3r said:
Hello there! Alive parts of this forum is still filled with simple help requests so I decided to put together a simple all-in-one thread that basically covers most stuff. I don't wanna get into bootloader unlocking because right now only free way to do so is with potatoNV which I do not know how to use. Dc-unlocker is an option too but it is 4€ so pick your poison.Special key combos:
Power + Vol+ = Recovery Mode
While USB connected, Power + Vol+ = Erecovery Mode
While USB connected, Vol- = Fastboot
Plug USB while holding down Vol+ + Vol- = Download Mode
Power + Vol+ + Vol- = Force Dload
Flashing LineageOS 16.0Prerequisites:
Emui Version below 9.1.0.300
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Los16 zip
Official TWRP
Stock recovery_ramdis.img
Your choice of gapps zip
Steps:
Get the Prerequisites
I recommend sending los 16 zip, recovery_ramdis.img and gapps zip to sd card if possible
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send adb reboot bootloader command from console
After restart write fastboot flash recovery_ramdisk to console and drag twrp-3.5.2_9-0-anne.img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Allow modifications
Press Install and select los 16 zip file
If you want to disable encryption do it now
Press Install and press Install Image
Select and flash stock recovery_ramdis.img to recovery_ramdisk partition
Press Reboot and select shut down
Press and hold power + vol+ buttons until short yellow warning shows up
Select factory reset and type yes, while it is doing that plug the phone to pc
After factory reset is complete select reboot option and hold down vol- until you're at fastboot
Repeat step 6-7-8
Los 16 don't need to be resized so go to install and select gapps zip
Reboot to system
Flashing Any GSIPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
GSI image (1) (2)
Official TWRP
Stock recovery_ramdis.img
Your choice of gapps zip (Optional)
Notes:If you're gonna use Phh's AOSP11 and anything that based on it (with the exception of @eremitein's stuff), use arm64-ab-vndklite variant. For anything else use full vndk version. Full vndk version of Phh's AOSP11 does not allow you to resize system on any twrp.
Steps for gapps versions:
Get the Prerequisites
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send adb reboot bootloader command from console
After restart write fastboot flash system to console and drag gsi .img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
You should be at stock recovery_ramdisk, do a factory reset
You're good to boot up the system
Steps for vanilla versions with custom gapps:
Get the Prerequisites
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send adb reboot bootloader command from console
After restart write fastboot flash system to console and drag gsi .img over to console and press enter
If you want to disable encryption do it now
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
You should be at stock recovery_ramdisk, do a factory reset
Plug your phone back and press reboot from screen
While booting press and hold vol- button until you're at fastboot
Write fastboot flash recovery_ramdisk to console and drag twrp-3.5.2_9-0-anne.img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Allow modifications
Press Wipe, press Advanced Wipe, select System, press Repair or Change File System, press Resize File System, swipe to resize
Press Install, select and flash gapps zip
Reboot to system
Disable EncryptionPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Official TWRP
Stock recovery_ramdis.img
Notes:You can disable encryption at any step, even after booting, but in order to disable it you have to do a factory reset from stock recovery_ramdis. Because of this I recommend doing between flashing gsi and flashing gapps.
Steps:
Get the Prerequisites
Boot to TWRP (power + vol+ after shutting down)
Allow modifications
Press Mount, select Vendor
Connect phone to PC
You can do next part 2 ways, if you're good with command line interface use steps 7 through 11, if not skip to step 12
Type adb shell and press enter
Type nano /vendor/etc/fstab.hi6250 and press enter
Remove fileencryption=aes-256-xts:aes-256-cts part from 16th line, make sure there's only one comma between check and reservedsize
Press Ctrl + X then Y and press enter
Go to step 18
Type adb pull /vendor/etc/fstab.hi6250 and press enter
If you have adb in your $PATH go to your user profile folder, if not go to folder where adb.exe resides
Open fstab.hi6250 via a text editor (please use notepad++)
Remove fileencryption=aes-256-xts:aes-256-cts part from 16th line, make sure there's only one comma between check and reservedsize
Save file and open a command prompt
Send this command adb push ./fstab.hi6250 /vendor/etc/fstab.hi6250
View attachment 5422531
Now you need to do a factory reset with stock recovery_ramdis.img, if you have it installed go to step 21 if not do 19 or 20 first
If you have recovery_ramdis.img in your sd card, press Install and press Install Image then select and flash stock recovery_ramdis.img to recovery_ramdisk partition
If not shut down phone, connect it to pc and hold down vol- until you're at fastboot, then write this command fastboot flash recovery_ramdisk and drag recovery_ramdis.img over to console then press enter
Shut down phone and unplug it from pc
Press and hold power+ vol+ until you see short yellow warning
Press Factory Reset and type yes
You've successfully decrypted your phone and you're good to boot up or flash gapps
Getting Stock Firmware Files And DowngradingPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Huawei Update Extractor
Firmware Zips
HiSuite
Erecovery
EMUI's System Updater (via root)
HuRUpdater Guide / HuRUpdater Download (don't work anymore)
HwOTA (don't work anymore)
Getting stock files are problematic because of huawei. Least shadiest way to get them are the hardest so bear with me.
Androidhost.ru : Click the "Firmware Zips" from prerequisites and search p20 lite. You should get a wide variety of versions to pick from. Make sure to match the Cust in the file to yours. C432 for Europe for example. After you download the zip file open it up and find a folder named "dload". You can either get this folder and paste it right into your sd card to force dload or you can open this folder and extract update_sd.zip. Inside update_sd.zip you'll find a file named UPDATE.APP. Use Huawei Update Extractor to open this file and there you'll see all the partitions you need. If HUE gives error while opening it, go to settings and untick "Verify file checksum". You can extract .img files by right clicking and selecting extract option on each partition. Normally you can't open these .img files but after pushing them through simg2img you'll be able to explore them too. But lets be real if you need guides for this, all you need is recovery_ramdis.img.
Using Dload Folder : Your sd card can't be FAT32 for this. FAT32 by nature don't allow files larger than 4gb so you can't get this folder to your sd card. Format it to ExFat via any guide on the internet then copy the dload folder to your sd card's root. It can't be inside any folders. Then shut your phone and press Power + Vol+ + Vol- all at the same time. It'll boot to erecovery which'll check the integrity of files then install them regardless of your EMUI version. So it is a good way to downgrade. Keep in mind tho you can't dload back to emui 8 from emui 9. And any successful dload will lock your bootloader back.
Hisuite : You can actually get firmware files pretty easily with hisuite but it requires real work. You see, hisuite downloads firmware files right into your documents folder. Connect your phone to pc and open up hisuite. Check for updates and if it finds one it'll download following files update_full_base.zip, update_full_ANE-L01_hw_eu.zip and update_full_cust_ANE-L01_hw_eu.zip. You only need update_full_base.zip file, others are used to work on HuRUpdater and HwOTA but they are deprecated since February. Inside update_full_base.zip you'll find UPDATE.APP which you can extract images from with Huawei Update Extractor.
Erecovery : This one requires some network knowledge and it'll only get you the latest version so I don't think it worth the hassle. You need a router that allows you to change dns address for DHCP clients. Which most of them do these days. Now you need to create and run a dns server on your pc. I recommend adguard home. Pihole works too. Use Windows Subsystem For Linux or Docker to install either of them. Once you get them up and working set them to log dns requests. I believe you know where this is going. Open your router's interface and enter adguard home/pihole ip address which maps back to your pc's local address. Check if it works or not by opening up few sites on your phone which should be connected to your wifi and isn't set up to use a different dns server. If all is good open up erecovery on your phone and connect to your wifi. If you set it up correctly it should get the latest version from huawei which will show up on your log. Use that url to download it to your pc and extract it same as others. There was a paid service that used this method to send specific versions to your erecovery.
EMUI's System Updater : This is tricky and my favorite. Get the official TWRP .img and patch it with magisk manager. Then flash it via fastboot. I know, "twrp and magisk? wtf?" just do it. It takes a long time to boot but it works don't question me right now. After you get root in EMUI allow system updater to do its job and update. It'll ask to reboot, allow it. It will throw you back to system after reboot cuz recovery is hijacked. duh. Get a file manager that allows root access. Allow system updater to download again. But this time do not allow it to reboot. First one downloaded OTA, second one downloaded FullOTA. Which is better for archival purposes. After download is done search for a folder named HwOUC in /system. Copy it to internal storage and from there to your pc. You can find our main UPDATE.APP inside update_full_base.zip. Other zips include cust and all that which HuRu and HwOTA used to require.
MagiskPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Stock recovery_ramdis.img
Notes:Officially speaking magisk support for our device is dead. Magisk decided to retire magisk-in-recovery method which our phone uses. But hey it is still working without modifications unlike a-only devices so that's a win. As a foot note, you CAN use twrp image instead of stock recovery_ramdis.img but it'll take longer to boot. Using .380's recovery_ramdis.img on .278 build will not work. Make sure to match your EMUI build with ramdisk you're flashing. Ask me how I know.
Steps to install older version:
Get the Prerequisites
No, I mean literally just get the Prerequisites and thats it
Open up your browser and find a bin service (pastebin will suffice)
Create a paste with following
Code:
{
"app": {
"version": "8.0.7",
"versionCode": "4834",
"link": "https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk",
"note": "https://cdn.jsdelivr.net/gh/topjohnwu/[email protected]/app/src/main/res/raw/changelog.md"
},
"stub": {
"versionCode": "18",
"link": "https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/stub-release.apk"
},
"uninstaller": {
"link": "https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-uninstaller-20210117.zip"
},
"magisk": {
"version": "v21.4",
"versionCode": "21400",
"link": "https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-v21.4.zip",
"note": "https://topjohnwu.github.io/Magisk/releases/21400.md",
"md5": "ee6dd05579776e7de3a6077087846e53"
}
}
Get the paste's raw url
Take the recovery_ramdis.img to internal storage
Install magisk manager 8.0.7
Open it's settings and select custom channel
Write the raw url you just created
Allow it to check for updates and it'll find that 21.4 is the latest version
Click install and select recovery_ramdis.img
After it finishes patching get the magisk_patched.img to your pc
Get your phone to fastboot mode
After connecting to pc, write this fastboot flash recovery_ramdisk to console and drag magisk_patched.img over to console and press enter
Now if you enter recovery it'll boot to android with magisk but if you boot normally it will not detect magisk so each time you restart you have to use Power + Vol+ combo in order to get magisk
Remember to switch custom channel to stable channel if you want to receive updates.
I know that you can pretty much reduce the amount of flashing and restarting by flashing twrp to erecovery but since erecovery is a lifeline for most people here I decided not to get into that. But for those who are interested check this thread.
Edit: Grammar
Edit 2: Update about HwOTA and HuRUpdate
Click to expand...
Click to collapse
Oh, man! Are you serious?
I don't know what anyone expects from a guide... Is it better to just repeat the same thing over and over again? "Flash system with fastboot, factory reset with stock recovery, flash and boot twrp, resize system, flash gapps" is literally the summary of this. That summary is what you'll get as an answer if you ask for help on any telegram group. Instead of saying flash twrp, I wrote how you can flash twrp. Thats why it's so long. This guide is for "how" not "what".
Frax3r said:
I don't know what anyone expects from a guide... Is it better to just repeat the same thing over and over again? "Flash system with fastboot, factory reset with stock recovery, flash and boot twrp, resize system, flash gapps" is literally the summary of this. That summary is what you'll get as an answer if you ask for help on any telegram group. Instead of saying flash twrp, I wrote how you can flash twrp. Thats why it's so long. This guide is for "how" not "what".
Click to expand...
Click to collapse
I would say that even so far, people have managed to install GSI, Magisk, etc. .
Btw, Recovery and eRecovery are the same for all models and build numbers . They are even compatible with LLD and BND models.
Frax3r said:
Thats why it's so long
Click to expand...
Click to collapse
It is long because because of procedures that are too complicated, e.g. chapter "Disable Encryption" .
It is long because of duplicate procedures, e.g. chapter "Flashing Any GSI".
Sorry but Chapter "Magisk" is useless. Nowadays nobody needs to install the old Magisk. Rather focus on some of the nuances of installing Magisk on EMUI 9.1 that would be helpful.
Frax3r said:
Officially speaking magisk support for our device is dead. Magisk decided to retire magisk-in-recovery method which our phone uses.
Click to expand...
Click to collapse
No comment...
Frax3r said:
Get the official TWRP .img and patch it with magisk manager
Click to expand...
Click to collapse
No comment...
Have a good day!
Frax3r said:
Hello there! Alive parts of this forum is still filled with simple help requests so I decided to put together a simple all-in-one thread that basically covers most stuff. I don't wanna get into bootloader unlocking because right now only free way to do so is with potatoNV which I do not know how to use. Dc-unlocker is an option too but it is 4€ so pick your poison.
I have uploaded all my resources for this device to here. Inside EMUI folder you'll find some of the versions that I archived with the methods I explained on getting firmwares section. You can find recovery_ramdis.img from each of these version inside RECOVERY_RAMDISK folder as well.Special key combos:
Power + Vol+ = Recovery Mode
While USB connected, Power + Vol+ = Erecovery Mode
While USB connected, Vol- = Fastboot
Plug USB while holding down Vol+ + Vol- = Download Mode
Power + Vol+ + Vol- = Force Dload
Flashing LineageOS 16.0Prerequisites:
Emui Version below 9.1.0.300
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Los16 zip
Official TWRP
Stock recovery_ramdis.img
Your choice of gapps zip
Steps:
Get the Prerequisites
I recommend sending los 16 zip, recovery_ramdis.img and gapps zip to sd card if possible
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send this command from pc : adb reboot bootloader
When you're at fastboot write fastboot flash recovery_ramdisk to console and drag & drop twrp-3.5.2_9-0-anne.img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Allow modifications
Press Install and select los 16 zip file
If you want to disable encryption do it now
Press Install and press Install Image
Select and flash stock recovery_ramdis.img to recovery_ramdisk partition
Press Reboot and select Recovery
Press Factory Reset and type yes, while it is doing that plug the phone to pc
Press Reboot and when screen is off start holding down vol- until you're at fastboot
Repeat step 6-7-8
Los 16 don't need to be resized so press Install and select gapps zip
Press Reboot System
Flashing Any GSIPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
GSI image (1) (2)
Official TWRP
Stock recovery_ramdis.img in recovery_ramdisk partition
Your choice of gapps zip (Optional)
Notes:If you're gonna use Phh's AOSP11 and anything that based on it (with the exception of @eremitein's stuff), use arm64-ab-vndklite variant. For anything else use full vndk version. Full vndk version of Phh's AOSP11 does not allow you to resize system on any twrp.
Steps for gapps versions:
Get the Prerequisites
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send this command from pc : adb reboot bootloader
When you're at fastboot write fastboot flash system to console and drag & drop gsi .img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Press Factory Reset and type yes
When it is done press Reboot
Steps for vanilla versions with custom gapps:
Get the Prerequisites
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send this command from pc : adb reboot bootloader
When you're at fastboot write fastboot flash system to console and drag & drop gsi .img over to console and press enter
If you want to disable encryption do it now
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Press Factory Reset and type yes, while it is doing that plug the phone to pc
Press Reboot and when screen is off start holding down vol- until you're at fastboot
Write fastboot flash recovery_ramdisk to console and drag & drop twrp-3.5.2_9-0-anne.img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Allow modifications
Press Wipe, press Advanced Wipe, select System, press Repair or Change File System, press Resize File System, swipe to resize then go back to main screen
Press Install, select and flash gapps zip
Press Reboot System
Disable EncryptionPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Official TWRP
Stock recovery_ramdis.img
Notes:You can disable encryption at any step, even after booting, but in order to disable it you have to do a factory reset from stock recovery_ramdis. Because of this I recommend doing between flashing gsi and flashing gapps.
Steps:
Get the Prerequisites
Flash and boot TWRP
Allow modifications
Press Mount, select Vendor
Connect phone to PC
You can do next part 2 ways, if you're good with command line interface use steps 7 through 11, if not skip to step 12
Type adb shell and press enter
Type nano /vendor/etc/fstab.hi6250 and press enter
Remove fileencryption=aes-256-xts:aes-256-cts from 16th line, make sure there's only one comma between check and reservedsize
Press Ctrl + X then Y and press enter
Go to step 18
Type adb pull /vendor/etc/fstab.hi6250 and press enter
If you have adb in your $PATH go to your user profile folder, if not go to folder where adb.exe is
Open fstab.hi6250 via a text editor (please use notepad++)
Remove fileencryption=aes-256-xts:aes-256-cts from 16th line, make sure there's only one comma between check and reservedsize
Save file and open a command prompt
Send this command adb push ./fstab.hi6250 /vendor/etc/fstab.hi6250
View attachment 5422531
Now you need to do a factory reset with stock recovery_ramdis.img
If you have recovery_ramdis.img in your sd card, press Install and press Install Image then select recovery_ramdis.img and pick recovery_ramdisk partition
If you don't have recovery_ramdis.img in your sd card, shut down phone, connect it to pc and hold down vol- until you're at fastboot, then write this command fastboot flash recovery_ramdisk and drag recovery_ramdis.img over to console then press enter
Shut down your phone and unplug it from pc
Press and hold power+ vol+ until you see short yellow warning
Press Factory Reset and type yes
You've successfully decrypted your phone and you're good to boot up or flash gapps
Getting Stock Firmware Files And DowngradingPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Huawei Update Extractor
Firmware Zips
HiSuite
Erecovery
EMUI's System Updater (via root)
HuRUpdater Guide / HuRUpdater Download (don't work anymore)
HwOTA (don't work anymore)
Getting stock files are problematic because of huawei. Least shadiest way to get them are the hardest so bear with me.
Androidhost.ru : Click the "Firmware Zips" from prerequisites and search p20 lite. You should get a wide variety of versions to pick from. Make sure to match the Cust in the file to yours. C432 for Europe for example. After you download the zip file open it up and find a folder named "dload". You can either get this folder and paste it right into your sd card to force dload or you can open this folder and extract update_sd.zip. Inside update_sd.zip you'll find a file named UPDATE.APP. Use Huawei Update Extractor to open this file and there you'll see all the partitions you need. If HUE gives error while opening it, go to settings and untick "Verify file checksum". You can extract .img files by right clicking and selecting extract option on each partition. Normally you can't open these .img files but after pushing them through simg2img you'll be able to explore them too. But lets be real if you need guides for this, all you need is recovery_ramdis.img.
Using Dload Folder : Your sd card can't be FAT32 for this. FAT32 by nature don't allow files larger than 4gb so you can't get this folder to your sd card. Format it to ExFat via any guide on the internet then copy the dload folder to your sd card's root. It can't be inside any folders. Then shut your phone and press Power + Vol+ + Vol- all at the same time. It'll boot to erecovery which'll check the integrity of files then install them regardless of your EMUI version. So it is a good way to downgrade. Keep in mind tho you can't dload back to emui 8 from emui 9. And any successful dload will lock your bootloader back.
Hisuite : You can actually get firmware files pretty easily with hisuite but it requires real work. You see, hisuite downloads firmware files right into your documents folder. Connect your phone to pc and open up hisuite. Check for updates and if it finds one it'll download following files update_full_base.zip, update_full_ANE-L01_hw_eu.zip and update_full_cust_ANE-L01_hw_eu.zip. You only need update_full_base.zip file, others are used to work on HuRUpdater and HwOTA but they are deprecated since February. Inside update_full_base.zip you'll find UPDATE.APP which you can extract images from with Huawei Update Extractor.
Erecovery : This one requires some network knowledge and it'll only get you the latest version so I don't think it worth the hassle. You need a router that allows you to change dns address for DHCP clients. Which most of them do these days. Now you need to create and run a dns server on your pc. I recommend adguard home. Pihole works too. Use Windows Subsystem For Linux or Docker to install either of them. Once you get them up and working set them to log dns requests. I believe you know where this is going. Open your router's interface and enter adguard home/pihole ip address which maps back to your pc's local address. Check if it works or not by opening up few sites on your phone which should be connected to your wifi and isn't set up to use a different dns server. If all is good open up erecovery on your phone and connect to your wifi. If you set it up correctly it should get the latest version from huawei which will show up on your log. Use that url to download it to your pc and extract it same as others. There was a paid service that used this method to send specific versions to your erecovery.
EMUI's System Updater : This is tricky and my favorite. Get the official TWRP .img and patch it with magisk manager. Then flash it via fastboot. I know, "twrp and magisk? wtf?" just do it. It takes a long time to boot but it works don't question me right now. After you get root in EMUI allow system updater to do its job and update. It'll ask to reboot, allow it. It will throw you back to system after reboot cuz recovery is hijacked. duh. Get a file manager that allows root access. Allow system updater to download again. But this time do not allow it to reboot. First one downloaded OTA, second one downloaded FullOTA. Which is better for archival purposes. After download is done search for a folder named HwOUC in /system. Copy it to internal storage and from there to your pc. You can find our main UPDATE.APP inside update_full_base.zip. Other zips include cust and all that which HuRu and HwOTA used to require.
MagiskPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Stock recovery_ramdis.img
Notes:Officially speaking magisk support for our device is dead. Magisk decided to retire magisk-in-recovery method which our phone uses. But hey it is still working without modifications unlike a-only devices so that's a win. New installer for magisk kinda broken for our device, because of that I recommend installing and booting an older version. It's safe to update it afterwards from magisk manager. As a foot note, you CAN use twrp image instead of stock recovery_ramdis.img but it'll take longer to boot. Using .380's recovery_ramdis.img on .278 build will not work. Make sure to match your EMUI build with ramdisk you're flashing. Ask me how I know.
Steps to install older version:
Get the Prerequisites
No, I mean literally just get the Prerequisites and thats it
Open up your browser and find a bin service (pastebin will suffice)
Create a paste with following
Code:
{
"app": {
"version": "8.0.7",
"versionCode": "4834",
"link": "https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk",
"note": "https://cdn.jsdelivr.net/gh/topjohnwu/[email protected]/app/src/main/res/raw/changelog.md"
},
"stub": {
"versionCode": "18",
"link": "https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/stub-release.apk"
},
"uninstaller": {
"link": "https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-uninstaller-20210117.zip"
},
"magisk": {
"version": "v21.4",
"versionCode": "21400",
"link": "https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-v21.4.zip",
"note": "https://topjohnwu.github.io/Magisk/releases/21400.md",
"md5": "ee6dd05579776e7de3a6077087846e53"
}
}
Get the paste's raw url
Take the recovery_ramdis.img to internal storage
Install magisk manager 8.0.7
Open it's settings and select custom channel
Write the raw url you just created
Allow it to check for updates and it'll find that 21.4 is the latest version
Click install and select recovery_ramdis.img
After it finishes patching get the magisk_patched.img to your pc
Get your phone to fastboot mode
After connecting to pc, write this fastboot flash recovery_ramdisk to console and drag magisk_patched.img over to console and press enter
Now if you enter recovery it'll boot to android with magisk but if you boot normally it will not detect magisk so each time you restart you have to use Power + Vol+ combo in order to get magisk
Remember to switch custom channel to stable channel if you want to receive updates.
I know that you can pretty much reduce the amount of flashing and restarting by flashing twrp to erecovery but since erecovery is a lifeline for most people here I decided not to get into that. But for those who are interested check this thread.
Edit: Grammar
Edit 2: Update about HwOTA and HuRUpdate
Edit 3: Simplify some steps and add my own mega.nz archive
Click to expand...
Click to collapse
Only now I have time to read your instructions carefully, what is this nonsense ???
Frax3r said:
Officially speaking magisk support for our device is dead. Magisk decided to retire magisk-in-recovery method which our phone uses. But hey it is still working without modifications unlike a-only devices so that's a win. New installer for magisk kinda broken for our device, because of that I recommend installing and booting an older version.
Click to expand...
Click to collapse
I'll give you some advice if I may - don't write about things you don't understand! And this applies not only to Magisk.
avenger.forsyth said:
It is long because because of procedures that are too complicated, e.g. chapter "Disable Encryption" .
Click to expand...
Click to collapse
Is it better to just link decryption zip or write what that decryption zip does?
avenger.forsyth said:
It is long because of duplicate procedures, e.g. chapter "Flashing Any GSI".
Click to expand...
Click to collapse
People use gapps versions because they don't want to waste time by flashing zips. That's why it's 2 part. Gapps one is shorter.
Frax3r said:
Officially speaking magisk support for our device is dead. Magisk decided to retire magisk-in-recovery method which our phone uses.
Click to expand...
Click to collapse
Magisk-in-recovery as in "magisk hijacking recovery" not "installing magisk using recovery". You can't even find huawei section in it's installation instructions. Look here and here. As for the nuance you asked, installing magisk in EMUI is literally same as installing it in GSI or LOS. You patch the image, flash the image, boot the image.
Frax3r said:
As a foot note, you CAN use twrp image instead of stock recovery_ramdis.img but it'll take longer to boot. Using .380's recovery_ramdis.img on .278 build will not work. Make sure to match your EMUI build with ramdisk you're flashing. Ask me how I know.
Click to expand...
Click to collapse
I added "ask me how I know" part for a reason. I tried. You CAN patch official twrp with magisk and it WILL boot. If a person unlocks their bootloader for the first time how is he supposed to get stock recovery_ramdis.img? Get the mmcblock of recovery_ramdisk? How is he supposed to do that if he flashes twrp over to recovery_ramdisk partition? We can't use "fastboot boot" so that's out of option. Use a different recovery_ramdis.img you might say. I TRIED. .380's recovery_ramdis.img patched with latest magisk won't boot if you're at .278. I created a folder where I patched .380 recovery with each different version of magisk starting from 20.4 up to latest version and none of them booted on los 16 which was installed upon .278. It is not universal as you might think.
-Alf- said:
Only now I have time to read your instructions carefully, what is this nonsense ???
I'll give you some advice if I may - don't write about things you don't understand! And this applies not only to Magisk.
Click to expand...
Click to collapse
Care to elaborate? I am open to constructive criticism. As for what I know, I do know that you won't find yourself bootlooping if you follow these steps by the letter. I saw your instructions on los 16 and other threads too. Here's a criticism for you, do not tell people to wipe /data or factory reset with twrps and especially do not expect them to flash twrp over to erecovery. Wiping /data or factory reset from twrp always resulted in phone freezing for me. I guess twrp in erecovery could fix freezing but there's a reason why they are asking for help and you expect them to overwrite their only lifeline. 1-2 extra rebooting and flashing won't hurt anyone. When you wipe /data or factory reset with most twrps, including official one, some folders that needs to be untouched (huawei am i right) gets deleted. So you have to use stock recovery_ramdis.img or an advanced twrp which compansates it. Check the tishserg's twrp for example. I use that not the official twrp for these things. And it can write to erecovery which is exactly why I didn't advocate on using it in this guide. Have a good day...
Frax3r said:
Here's a criticism for you, do not tell people to wipe /data or factory reset with twrps and especially do not expect them to flash twrp over to erecovery. Wiping /data or factory reset from twrp always resulted in phone freezing for me.
Click to expand...
Click to collapse
Use recommended TWRP, not 3.4.0. and above, which is not fully compatible with hi6250 devices (including official one). Did you know?
Btw, I never advised anyone to do a factory reset in TWRP, on the contrary
https://forum.xda-developers.com/t/...twrp-3-2-1-0-12-05-2018.3789306/post-85472227
Frax3r said:
New installer for magisk kinda broken for our device, because of that I recommend installing and booting an older version.
Click to expand...
Click to collapse
Everyone knows that it is possible to install the latest version right away...
-Alf- said:
Use recommended TWRP, not 3.4.0. and above, which is not fully compatible with hi6250 devices (including official one). Did you know?
Btw, I never advised anyone to do a factory reset in TWRP, on the contrary
https://forum.xda-developers.com/t/...twrp-3-2-1-0-12-05-2018.3789306/post-85472227
Everyone knows that it is possible to install the latest version right away...
Click to expand...
Click to collapse
Yes you said that here. However my own experience says otherwise. Before my current los 16 installation I used official 3.5.2. Flashed los, flashed stock recovery, flashed phenix kernel, flashed gapps all from it. I even used nano from adb shell to edit fstab.hi6250. I used backup and restore only on kernel partition but it was successful anyway. What that incompatibility be? Is it boot override thing? If you have twrp in recovery and send reboot to recovery from android it just keeps booting to twrp in each reboot even tho you select otherwise from twrp's reboot menu. BTW tishserg's twrp have an option to remove that override if you find yourself in that loop. As for factory reset part, you said format /data here. We had a discussion here because of that. My bad on reading wrong. While writing this I realised incompatibility is probably about formating /data on twrp 3.4.0 and above. If that is the case I'll update the post. Good thing I didn't tell people to format /data from twrp. My steps might be long but they are correct. It is wrong to call all this a nonsense.
Everyone might know it is possible to install latest magisk but not everyone knows how to install an older version now that magisk's future is uncertain. After magisk removes magiskhide from its code people are gonna wanna go back to latest version that worked while waiting for module version of it. Patching twrp image with magisk is highlight of this post but it is literally what flashing magisk.zip (.apk to .zip) from twrp does with the latest version. If patching twrp is bad then why is my guide to installing an older version, which allows you to select which image to patch, is the target? + With that .json, you can make magisk manager patch the image with your own modified version of magisk should you upload it somewhere and change the links.
Hi,
I'm building trying to port Ubuntu Touch to this device and I'm running into a few challenges. I have already reverted to stock 2 times and re-unlocked the bootloader (starting from EMUI 9). So far I have only flashed recovery_ramdisk with twrp as I was worried I might not be able to revert to stock if I flashed erecovery.
Question 1: Is this correct or a misunderstanding?
Installing Ubuntu Touch requires the data partition to be formatted to ext4. I can do that from twrp, but someone (maybe you) wrote that wiping the data partition with twrp was liable to create trouble.
Q2: Same question as above.
I understand Huawei requires the kernel and ramdisk to reside in separate images on separate partitions. So I have used this guide (https://wiki.postmarketos.org/wiki/Huawei_P10_Lite_(huawei-warsaw)) to separate the boot.img produced in my build, and then flashed these two image files to the kernel and recovery_ramdisk partitions respectively. However, examining the LOS 16.0 rom that can be installed, I see that it contains a "boot.img".
Q3: Can I flash my boot.img without separating into kernel and ramdisk first, and if so, which partition should I flash?
Q4: After flashing the image files I built (kernel.img and ramdisk.img along with system.img), do I need to reboot to a recovery (if so, which?) and wipe something (if so, what?) before rebooting?
aribk said:
Hi,
Question 1: Is this correct or a misunderstanding?
Q2: Same question as above.
Q3: Can I flash my boot.img without separating into kernel and ramdisk first, and if so, which partition should I flash?
Q4: After flashing the image files I built (kernel.img and ramdisk.img along with system.img), do I need to reboot to a recovery (if so, which?) and wipe something (if so, what?) before rebooting?
Click to expand...
Click to collapse
Hello,
If I understood you correctly you're asking if you can flash stock erecovery after you've modified it. Answer is yes, you can flash twrp on it and when you're done you can flash stock erecovery image over it. Fastboot won't allow you to flash anything on erecovery partition tho. So you need to use certain twrps that are capable of flashing over erecovery. s_mak and tishserg twrps should allow that iirc. First flash any one of those twrps to recovery_ramdisk then boot into it afterwards flash same twrp image to erecovery partition from inside the twrp.
Yes, if you look at last few replies in this thread that was exactly the conversation. However that is only the case with official twrp. If you use s_mak or tishserg's twrps from the mega link in the thread you should be able to wipe without a problem.
Last 2 questions are beyond me I'm afraid. PostparketOS and Ubuntu Touch are inherently very different to android and they could require some stuff that are unique to them. However I would imagine you wouldn't need to wipe anything after flashing those images.
aribk said:
Hi,
I'm building trying to port Ubuntu Touch to this device and I'm running into a few challenges. I have already reverted to stock 2 times and re-unlocked the bootloader (starting from EMUI 9). So far I have only flashed recovery_ramdisk with twrp as I was worried I might not be able to revert to stock if I flashed erecovery.
Question 1: Is this correct or a misunderstanding?
Installing Ubuntu Touch requires the data partition to be formatted to ext4. I can do that from twrp, but someone (maybe you) wrote that wiping the data partition with twrp was liable to create trouble.
Q2: Same question as above.
I understand Huawei requires the kernel and ramdisk to reside in separate images on separate partitions. So I have used this guide (https://wiki.postmarketos.org/wiki/Huawei_P10_Lite_(huawei-warsaw)) to separate the boot.img produced in my build, and then flashed these two image files to the kernel and recovery_ramdisk partitions respectively. However, examining the LOS 16.0 rom that can be installed, I see that it contains a "boot.img".
Q3: Can I flash my boot.img without separating into kernel and ramdisk first, and if so, which partition should I flash?
Q4: After flashing the image files I built (kernel.img and ramdisk.img along with system.img), do I need to reboot to a recovery (if so, which?) and wipe something (if so, what?) before rebooting?
Click to expand...
Click to collapse
aribk said:
So far I have only flashed recovery_ramdisk with twrp as I was worried I might not be able to revert to stock if I flashed erecovery.
Question 1: Is this correct or a misunderstanding?
Click to expand...
Click to collapse
Misunderstanding. You can revert to stock via eRecovery & wi-fi.
Huawei has Recovery and eRecovery, each has different functions.
You can use the following combinations in your phone:
- Recovery + eRecovery (stock FW)
- TWRP instead of Recovery + eRecovery
- Recovery + TWRP instead of eRecovery
aribk said:
wiping the data partition with twrp was liable to create trouble.
Q2: Same question as above.
Click to expand...
Click to collapse
Same answer as above. Formatting (not wiping) data with TWRP 3.4+ is dangerous (running stock EMUI).
Q3: All this only works on EMUI 8 as far as I know.
Q4: follow the instructions, imo.
P.S.: as you can see, mobile Linux projects such as Ubuntu Touch, postmarketOS or Sailfish OS work only partially on Hua/Ho phones,but we already talked about that .
-Alf- said:
Same answer as above. Formatting (not wiping) data with TWRP 3.4+ is dangerous (running stock EMUI).
Click to expand...
Click to collapse
Re-reading your answer above, I see I'd like to double check: Is this dangerous only if you are running stock EMUI, or would it also be dangerous to use TWRP 3.4+ to format the data partition when you wish to run a different system on the device, as in my case?
aribk said:
aribk said:
or would it also be dangerous to use TWRP 3.4+ to format the data partition when you wish to run a different system on the device, as in my case?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Hard to say, no one has experience with different system . But I don't think it matters - see Mr. Frax3r's post above (and read carefully bro ).
I'm bumping the thread, few improvements are made for android 13.
Thank you for the update.
I have modified Phenix_4.9.235-phenix-1.0 rebased on Harmonyos to make it permissive which make most A13 GSIs boot normally on my phone. I have attached the updated one.
Frax3r said:
After you set up your phone and made sure you don't need stock recovery, flash magisk:
Click to expand...
Click to collapse
magisk-patched stock recovery remains functional, available and usable.