Related
Hi there
today i've tried to update my Honor 6 , but when the download terminates and the phone boot in to recovery, appear an error and it doesn't let me upgrade.
What can i do?
anyone else has found this problem?
P.S.
previously I did root, but now I removed root, restored recovery and relocked the bootloader :crying:
up
Same thing happened to me not rotted. I think I'm going to root any way as I want touchwiz
How I fixed my failing update to B370 (OTA) H60-L04.
I had the exact same problem. I got an error while doing the OTA update, even with a stock recovery.
Special Note: If you have an exFat SD-card you should remove or convert it to ext fs before proceeding. ex-Fat filesystem has been known to cause failure of the .img flashing steps.
Special Note 2: If you do not have B109SP01, ensure that you update to that version first before proceeding. This is since the OTA update.zip is an incremental/partial update and not a "full OS" update. It adds the EMUI3.0 and installs specific .img files, not a full Android.
Disclaimer: This method did NOT delete or remove any data for me, but I can not guarantee it will not change any data.
Ensure that you have a CWM/TWRP backup or any cloud backups of contacts/photos/SMSes and any other data
you need before you continue. Settings such as XPOSED and similar may be altered/modified or disappear, but
this is most likely due to temporary removal of root privilige during this upgrade AND the new updated
EMUI 3.0 rom you will receive.
Here's how I suggest you do:
1. Use the Multi-tool again and unlock your bootloader and root the phone again.
Install the universal ADB driver if you haven't previously.
Honor6 Multi-tool download here...
2. Download the following files:
Huawei Update Extractor
^^^Install this one, download setup version 0.9.8.0.
Official
Honor 6 B109SP01 Upgrade .zip file
^^^Extract this .zip file to a temporary folder.
3. Now comes the special part. First of all you need to run the Huawei Update Extractor.
Use the default "Unknown (worstenbrood)" profile and target/select the unzipped "Update.APP" file that should
be in the B109SP01 folder that you just extracted (In the "Honor6" subfolder).
{
"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"
}
Like the picture above you will only need to extract the RECOVERY.IMG and SYSTEM.IMG files.
Ctrl-left click to select and then right click and select "Extract selected".
(Note: you will also get two ".img.header" files created, those are not needed)
Extract the files to the folder for the Honor 6 Multi-tool where you have adb.exe/fastboot.exe since we will use those commands.
4. When you have done the above extractions (it can take a while for system since it is 1.35 GB) you need to start your phone in
FASTBOOT mode. Power Off your phone and press Volume Down and connect USB to computer
(while pressing down Volume Down) to enter fastboot mode. (Same as when you are unlocking/rooting the phone from scratch).
5. Now start a command/DOS window, As Administrator to ensure no restrictions. We are now going to enter a few commands with ADB.
Go to the path where you have adb.exe/fastboot.exe for the Honor 6 Multi-tool, using cd command eg.
"cd C:\Users\XXX\Downloads\HONOR_6___6Plus_Multi-Tool\HONOR 6 Multi-Tool". Use dir command to check that you have all
files you need adb.exe/fastboot.exe and RECOVERY.IMG and SYSTEM.IMG.
6. First issue the command:
fastboot devices
This will return an identity to show that you have your phone connected. If it returns empty, please check that your phone is
properly discovered and has the right driver (install from Multi-tool if needed). Redo the command until it is discovered
7. Next, issue the following command:
fastboot flash recovery RECOVERY.img
This will flash the stock RECOVERY.img from B109SP01. It will not take a long time.
8. And finally issue the last command:
fastboot flash system SYSTEM.img
This will flash the stock SYSTEM.img from B109SP01 and IT WILL REMOVE ROOT for the time being.
Ensure that this completes properly, since it is a 1.35 GB file it will take a while. Do not disconnect or disturb this activity.
It can take several steps and a few minutes to complete. Check that you really have a final "ready" and are back in the
command prompt before this is complete. Check the RECOVERY.img result for comparison.
9. When both steps above are completed fully you can now disconnect the phone.
Press the power button a 10-15 seconds to ensure it really shuts down from the FASTBOOT mode.
Then boot up the phone again.
10. This should boot up your phone and you should notice no difference now. Root is however gone so any apps/functions
depending on root will fail. This is actually good for now, this means that above steps have worked.
(XPOSED and other apps using root are not working, certain stock features/looks are "back".)
11. Go to the "System Update" function in the regular settings. Now run the OTA update to B370 as normal or
use the Local Update functions if you want to. Do the reboots and hopefully it will run 100% and not stop with a failure.
Please review and redo steps above if it still fails.
12. After reboot it will do the necessary "Updating applications" as any Android update.
When you boot into the phone the first time things will have changed (like background, some icons etc.) but your
apps and data should remain. You will also go through a small guide, about 3-4 steps (Language/regions settings etc.)
13. Do any necessary updates from Google Play store (if any pending). Also reboot the phone into FASTBOOT mode
and re-run the Honor 6 Multi-tool to root your phone again (if needed) and install CWM/TWRP (if you wish).
14. Voilá, you should now have a B370 EMUI 3.0 phone. Please note that certain apps may have changed or lost certain
locks/functions so I recommend that you reinstall those first. Also check your "default" SMS/Webbrowser/Caller apps etc
that you would like to use if you are not using stock Huawei ones.
I recommend you check out these links for any more detailed instructions per step if needed:
Honor 6 Multi-tool
^^^ Full of small and detailed info regarding the Multi-tool and other useful Honor 6 flashing/rooting/unlocking tips.
Huawei Update Extractor tool
^^^ More info on how to use the Update Extractor Tool. It works for H60-L04 .zip/.APP files also even if it is not mentioned in thread.
Full Restoration to Stock ROM
^^^ Only perform steps 1 to 5. Steps 6-7 will GUARANTEE that you loose your data/restore to factory.
Official Huawei Honor 6 download page
^^^ Contains the proper H60-L04 V100R001C00B109SP01 Upgrade Software file to use for the RECOVERY.img and SYSTEM.IMG
that I used for this guide and for the H60-L04 (international version).
Honor 6 H60-L04 OTA Update.zip B370/EMUI.30
^^^ This is the .zip file that is downloaded for the OTA update that I have used. Note: Location I am in: Sweden.
Can be used for the manual/"dload"-folder Local Update function.
Hope this solves the problems for you.
Thanks very much
sheapchit said:
I had the exact same problem. I got an error while doing the OTA update, even with a stock recovery.
Disclaimer: This method did NOT delete or remove any data for me, but I can not guarantee it will not change any data.
Ensure that you have a CWM/TWRP backup or any cloud backups of contacts/photos/SMSes and any other data
you need before you continue. Settings such as XPOSED and similar may be altered/modified or disappear, but
this is most likely due to temporary removal of root privilige during this upgrade AND the new updated
EMUI 3.0 rom you will receive.
Here's how I suggest you do:
1. Use the Multi-tool again and unlock your bootloader and root the phone again.
Install the universal ADB driver if you haven't previously.
Honor6 Multi-tool download here...
2. Download the following files:
Huawei Update Extractor
^^^Install this one, download setup version 0.9.8.0.
Official
Honor 6 B109SP01 Upgrade .zip file
^^^Extract this .zip file to a temporary folder.
3. Now comes the special part. First of all you need to run the Huawei Update Extractor.
Use the default "Unknown (worstenbrood)" profile and target/select the unzipped "Update.APP" file that should
be in the B109SP01 folder that you just extracted (In the "Honor6" subfolder).
View attachment 3131125
Like the picture above you will only need to extract the RECOVERY.IMG and SYSTEM.IMG files.
Ctrl-left click to select and then right click and select "Extract selected".
(Note: you will also get two ".img.header" files created, those are not needed)
Extract the files to the folder for the Honor 6 Multi-tool where you have adb.exe/fastboot.exe since we will use those commands.
4. When you have done the above extractions (it can take a while for system since it is 1.35 GB) you need to start your phone in
FASTBOOT mode. Power Off your phone and press Volume Down and connect USB to computer
(while pressing down Volume Down) to enter fastboot mode. (Same as when you are unlocking/rooting the phone from scratch).
5. Now start a command/DOS window, As Administrator to ensure no restrictions. We are now going to enter a few commands with ADB.
Go to the path where you have adb.exe/fastboot.exe for the Honor 6 Multi-tool, using cd command eg.
"cd C:\Users\XXX\Downloads\HONOR_6___6Plus_Multi-Tool\HONOR 6 Multi-Tool". Use dir command to check that you have all
files you need adb.exe/fastboot.exe and RECOVERY.IMG and SYSTEM.IMG.
6. First issue the command:
fastboot devices
This will return an identity to show that you have your phone connected. If it returns empty, please check that your phone is
properly discovered and has the right driver (install from Multi-tool if needed). Redo the command until it is discovered
7. Next, issue the following command:
fastboot flash recovery RECOVERY.img
This will flash the stock RECOVERY.img from B109SP01. It will not take a long time.
8. And finally issue the last command:
fastboot flash system SYSTEM.img
This will flash the stock SYSTEM.img from B109SP01 and IT WILL REMOVE ROOT for the time being.
Ensure that this completes properly, since it is a 1.35 GB file it will take a while. Do not disconnect or disturb this activity.
It can take several steps and a few minutes to complete. Check that you really have a final "ready" and are back in the
command prompt before this is complete. Check the RECOVERY.img result for comparison.
9. When both steps above are completed fully you can now disconnect the phone.
Press the power button a 10-15 seconds to ensure it really shuts down from the FASTBOOT mode.
Then boot up the phone again.
10. This should boot up your phone and you should notice no difference now. Root is however gone so any apps/functions
depending on root will fail. This is actually good for now, this means that above steps have worked.
(XPOSED and other apps using root are not working, certain stock features/looks are "back".)
11. Go to the "System Update" function in the regular settings. Now run the OTA update to B370 as normal or
use the Local Update functions if you want to. Do the reboots and hopefully it will run 100% and not stop with a failure.
Please review and redo steps above if it still fails.
12. After reboot it will do the necessary "Updating applications" as any Android update.
When you boot into the phone the first time things will have changed (like background, some icons etc.) but your
apps and data should remain. You will also go through a small guide, about 3-4 steps (Language/regions settings etc.)
13. Do any necessary updates from Google Play store (if any pending). Also reboot the phone into FASTBOOT mode
and re-run the Honor 6 Multi-tool to root your phone again (if needed) and install CWM/TWRP (if you wish).
14. Voilá, you should now have a B370 EMUI 3.0 phone. Please note that certain apps may have changed or lost certain
locks/functions so I recommend that you reinstall those first. Also check your "default" SMS/Webbrowser/Caller apps etc
that you would like to use if you are not using stock Huawei ones.
I recommend you check out these links for any more detailed instructions per step if needed:
Honor 6 Multi-tool
^^^ Full of small and detailed info regarding the Multi-tool and other useful Honor 6 flashing/rooting/unlocking tips.
Huawei Update Extractor tool
^^^ More info on how to use the Update Extractor Tool. It works for H60-L04 .zip/.APP files also even if it is not mentioned in thread.
Full Restoration to Stock ROM
^^^ Only perform steps 1 to 5. Steps 6-7 will GUARANTEE that you loose your data/restore to factory.
Official Huawei Honor 6 download page
^^^ Contains the proper H60-L04 V100R001C00B109SP01 Upgrade Software file to use for the RECOVERY.img and SYSTEM.IMG
that I used for this guide and for the H60-L04 (international version).
Hope this solves the problems for you.
Click to expand...
Click to collapse
THANKS VERY MUCH without you I wouldn't have success
You're welcome!
Recovery.img is loaded in to the phone, but system.img not. the first part of the file is loading very quickly, but the second part don't. I have waited more then 2 hours and nothing.
fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' (410901 KB)...
OKAY [ 45.068s]
writing 'system'...
OKAY [ 13.131s]
sending sparse 'system' (460475 KB)...
Click to expand...
Click to collapse
My phones rooting is gone. But I still can't update
Sorry to hear that smldmr. The SYSTEM.img really needs to complete. Have you retried from the first step? Skip the RECOVERY.img step and just flash the SYSTEM.img until i succeeds. It should do that in less than 15 minutes in 4-5 sparse sends. If it stops, it may be something with the usb port, some sort of disconnect from your computer. Any other USB devices you have that are causing strange polling or similar. If possible switch to another port, avoid using usb-hubs.
sheapchit said:
You're welcome!
Click to expand...
Click to collapse
sorry sheapchit but i followed the guide step-by-step but i still can't update my phone
my situation is this:
root = none
bootloader status = "relocked"
system = STOCK
recovery = STOCK
phone data (i mean app & media) = the same before the guide
TigerDeveloper, is your bootloader locked after update or was it locked before you started? I had unlocked bootloader while flashing this and also unlocked after...
sheapchit said:
TigerDeveloper, is your bootloader locked after update or was it locked before you started? I had unlocked bootloader while flashing this and also unlocked after...
Click to expand...
Click to collapse
i tried to flash with bootloader locked or "relocked" at the first time
than i tried with unlocked bootloader
TheTigerDeveloper said:
i tried to flash with bootloader locked or "relocked" at the first time
than i tried with unlocked bootloader
Click to expand...
Click to collapse
OK.
Perhaps something I missed in my attempt to upgrade....
Perhaps you should do this:
1. Unlock Bootloader and ensure that you have rooted the phone.
2. Start the phone and download a filebrowser like Root Explorer or similar.
3. Ensure that you can remove the folders HWOUC if they are on the SDCARD (0) or even on external SDCARD1.
4. Also check the root folder that there is no "dload" folder from any manual attempts to update. (Delete if there is.).
These steps are to ensure that you do not have a corrupted/failing update left of the update.zip file that is downloaded
and so that a fresh one can be retrieved using the OTA update function in the Settings.
Double check that you do not have any pending/locked updates from Google Play store. If so, ensure that they are installed.
I do not know if there is a size limit on the SDCARD0 (built in 16GB storage) that has to be met.
Please check that you have adequate space left (2gb+) so that the update.zip can unpack itself properly when installing.
Remove any unneccesary/old/large apps that may cause you to loose this and clear out caches to give yourself space.
Then redo the steps to flash RECOVERY.img and SYSTEM.img and attempt a new update with the OTA function.
This may be something I did as I also experimented first trying to do the manual "dload"-folder update before doing my flashing.
after I tried it without my ext-SD Card (64 GB exFat formated SD Card), the system.img was uploaded successfully Now i have EMUI 3.0.
That's great smldmr. I have a regular ext-fs formated sdcard so I didn't anticipate exFat to be an issue. TigerDev,what is your sdcard?
sheapchit said:
That's great smldmr. I have a regular ext-fs formated sdcard so I didn't anticipate exFat to be an issue. TigerDev,what is your sdcard?
Click to expand...
Click to collapse
i have a 16 GB sdcard exfat
now i just tried to do a factory reset with stock recovery and bootloader relocked, redownloaded update via OTA, but no change
smldmr said:
after I tried it without my ext-SD Card (64 GB exFat formated SD Card), the system.img was uploaded successfully Now i have EMUI 3.0.
Click to expand...
Click to collapse
so you have update your phone without SD?
mmh... i should try it...
sheapchit
can you post here (a file i mean) of your build.prop & local.prop? (i think they are official no?)
so i can push them with adb
thanks
This guide is intended for all those who like me were not able to once update your phone (H60-L04)
here's how I solved it:
1) restore the system (rom, recovery, bootloader)
2) remove the ROOT
3) install the "beta" 3.0
TigerDev, I have the B370 local.prop/build.prop now.
The stock B109SP01 .prop files should become/restore to stock when you flash the SYSTEM.img. Did you test, like smldmr, to do my steps after you have removed your exFat sdcard?
Remove micro-sd card before download OTA and updating.
STEP BY STEP GUIDE FOR LG V20 H918 UNLOCKING BOOTLOADER, DOWNGRADING, ROOTING AND INSTALLING CUSTOM ROMS (NOOB FRIENDLY)
DISCLAIMER: I'M NOT THE DEVELOPER OF ANY OF THE BELOW SOFTWARE'S AND YOU PROCEED WITH YOUR OWN RISK AS THIS INVOLVES BRICKING OR DAMAGING YOUR MOBILE IF THE PROCEDURE IS NOT FOLLOWED CORRECTLY. I'M JUST SHARING THE WHOLE PROCESS WHICH I HAVE FOLLOWED TO ROOT AND INSTALL TWRP IN MY LGV20 H918 UNLOCKED T MOBILE.
AND I HAVE TESTED THIS IN MY OWN DEVICE AND WAS ABLE TO ROOT AND ACHIEVE TWRP.
THIS IS ONLY FOR LGV20 H918 VERSION
ENSURE INTERNET IS UP AND RUNNING IN YOUR PC
EDIT: THE WHOLE PROCESS HAS NOW BEEN AUTOMATED IN TWO SIMPLE STEPS TO PREVENT ANY POTENTIAL DAMAGE TO YOUR DEVICE. THANKS TO THE LAFSPLOIT CREATOR BRIAN @runningnak3d.
JUST FOLLOW THE PROCEDURE BELOW AND YOU SHOULD HAVE YOUR DEVICE ROOTED IN NO TIME
1. BACKUP ALL YOUR IMPORTANT DATA BEFORE PROCEEDING.
2.MAKE SURE YOU HAVE CHARGED YOUR PHONE TO AT LEAST 90 PERCENT
CHECK YOUR PHONE SOFTWARE VERSION IN SETTINGS---ABOUT PHONE----SOFTWARE INFO
IF IT IS ANYTHING BETWEEN H91810P TO H91810U MEANS IT IS ARB1 (ANTI ROLL BACK 1) AND YOU NEED TO USE LAFSPLOIT METHOD TO ROOT AND INSTALL TWRP,
IF YOUR VERSION IS H91810O OR BELOW (ARB0), YOU CAN EITHER USE DIRTYCOW OR LAFSPLOIT METHOD FOR THE SAME.
IF YOU ARE ON ARB1, PLEASE FOLLOW THE METHOD BELOW,
PART 1: DOWNGRADING
IF YOUR VERSION IS H91810 (Q, R, S, T, U) YOU NEED TO DOWNGRADE TO A LOWER VERSION ( H91810P) TO EXECUTE LAFSPLOIT.
IF YOU ARE ALREADY ON H91810P, YOU STILL NEED TO RE FLASH THE H91810P KDZ AGAIN FOR THE LAFSPLOIT SCRIPT TO WORK CORRECTLY.
DOWNLOAD H91810P KDZ FILE FROM BELOW
https://androidfilehost.com/?w=files&flid=282709
DOWNLOAD AND INSTALL ALL THE FILES BELOW IN YOUR PC
UPPERCUT AND LGUP----
http://downloads.codefi.re/autoprime/LG/Flash_Tools/LGUP/
LG DRIVERS---
http://tool.cdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
CONNECT YOUR MOBILE TO YOUR PC IN DOWNLOAD MODE (SWITCH OFF YOUR MOBILE AND CONNECT THE USB FROM PC WHILE HOLDING THE VOLUME UP BUTTON SIMULTANEOUSLY)
RUN UPPERCUT.EXE WHICH WOULD OPEN LG'S UPDATER TOOL AUTOMATICALLY.
INSIDE THE LG UPDATER TOOL, CLICK ON BIN AND SELECT THE H91810P KDZ FILE DOWNLOADED EARLIER.
NOW SELECT UPGRADE AND FLASH
ENSURE THE USB CABLE IS CONNECTED THROUGH THE FLASHING PROCESS AND WAIT FOR YOUR PHONE TO REBOOT AND THEN REMOVE THE USB CABLE.
CHECK THE SOFTWARE VERSION AND ENSURE IT IS H91810P
PART 2: UNLOCKING BOOTLOADER
HEAD TO SETTINGS---ABOUT PHONE----SOFTWARE INFO (ENSURE IT IS H91810P)
ENABLE DEVELOPER OPTION IN YOUR PHONE BY CLICKING ON THE BUILD NUMBER MULTIPLE TIMES
NOW HEAD TO SETTINGS---DEVELOPER OPTIONS
TURN ON OEM UNLOCKING, ENABLE USB DEBUGGING AND DISABLE 'VERIFY APPS OVER USB'
NOW CONNECT YOUR PHONE TO PC AND OPEN ADB COMMAND CENTER PROMPT IN YOUR PC
adb devices---->CHECK IF YOUR MOBILE IS CORRECTLY RECOGNIZED IN ADB
adb reboot bootloader--->THIS REBOOTS YOUR DEVICE IN FASTBOOT MODE
fastboot devices---->CHECK IF YOUR MOBILE IS CORRECTLY RECOGNIZED IN FASTBOOT
fastboot oem unlock---->THIS COMMAND WOULD UNLOCK YOUR BOOTLOADER AND RESET's YOUR DEVICE.
fastboot oem device-info OR fastboot getvar unlocked ----->THIS WOULD CONFIRM IF YOUR BOOTLOADER HAS BEEN UNLOCKED OR NOT.
fastboot reboot-----> THIS WOULD REBOOT YOUR DEVICE
IF THE BOOTLOADER HAS BEEN SUCCESSFULLY UNLOCKED, THE DEVICE WILL SHOW AN UNLOCKED BOOTLOADER WARNING MESSAGE WHILE BOOTING (THIS CAN BE IGNORED OF COURSE)
PART 3: CREATING A BOOTABLE LINUX USB USING FWUL
DOWNLOAD FWUL_v2.7_x86_64_15GB.zip FROM THE LINK BELOW AND EXTRACT THE IMAGE FILE SOMEWHERE IN YOUR PC.
https://androidfilehost.com/?w=files&flid=214529
DOWNLOAD RUFUS FROM BELOW AND INSTALL
https://rufus.akeo.ie/
INSERT A PEN DRIVE IN YOUR PC AND RUN RUFUS.
INSIDE RUFUS SELECT THE IMAGE FILE AND SELECT START (AFTER SELECTING START SELECT DD MODE IN THE DIALOGUE BOX) TO CREATE A BOOTABLE PEN DRIVE (WARNING: THIS WOULD FORMAT YOUR PEN DRIVE)
NOW YOU SHOULD BOOT YOUR PC FROM THE BOOTABLE USB STICK WHICH YOU HAVE JUST CREATED
THIS WOULD MAKE YOUR PC RUN LINUX OS
TYPE PASSWORD AS linux AND ENTER
PART 4: INSTALLING TWRP AND ROOTING USING LAFSPLOIT
BEFORE PROCEEDING ENSURE YOU BOOT YOUR PHONE AND DONE ALL THE BASIC SETTINGS
NOW HEAD TO THE DEVELOPER OPTIONS IN YOUR DEVICE AND ENSURE OEM UNLOCKING AND USB DEBUGGING ARE SWITCHED ON.
NOW CONNECT YOUR DEVICE TO THE PC (RUNNING LINUX OS FROM PENDRIVE) IN DOWNLOAD MODE (SWITCH OFF YOUR MOBILE AND CONNECT THE USB FROM PC WHILE HOLDING THE VOLUME UP BUTTON SIMULTANEOUSLY)
DOUBLE CLICK ON THE LG FOLDER INSIDE FWUL DESKTOP
INSIDE THAT, DOUBLE CLICK ON LGLAF(RUNNINGNAK3D) ICON WHICH WILL OPEN A TERMINAL
ENTER THE BELOW COMMANDS
git pull
git checkout h918-miscwrte
./step1.sh
THE ABOVE COMMAND FLASHES TWRP RECOVERY ONTO YOUR DEVICE.
WAIT AND PULL OUT YOUR DEVICE WHEN IT ASKS TO.
RECOMMENDED: NOW THAT TWRP HAS SUCCESSFULLY INSTALLED, YOU CAN MANUALLY FORMAT,FLASH LATEST TWRP RECOVERY AND USE ANY METHOD LIKE MAGISK OR SU FOR ROOTING.
INSIDE TWRP RECOVERY. FIRST FORMAT USING WIPE--ADVANCED FORMAT--TYPE yes AND FULL DO A FULL FORMAT, THEN FLASH MAGISK AND THE LATEST TWRP RECOVERY BELOW.
MAGISK ZIP DOWNLOAD:
https://github.com/topjohnwu/Magisk/releases/download/v16.0/Magisk-v16.0.zip
LATEST TWRP BY PHOENIX(H918):
https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
OR
IF YOU ARE UNSURE ABOUT FORMATTING AND FLASHING, JUST USE THE BELOW COMMAND TO DO ALL THE WORK AUTOMATICALLY
CONNECT YOUR DEVICE AGAIN IN DOWNLOAD MODE AND ENTER THE FOLLOWING COMMAND
./step2.sh
THE ABOVE COMMAND FORMATS YOUR DEVICE AND FLASHES MAGISK TO ACQUIRE ROOT.
TIP : IF YOU FACE ANY ENCRYPTION ERROR AFTER USING STEP2. SH, DO A ADVANCED FORMAT WITHIN TWRP AND FLASH MAGISK AND LATEST TWRP BY PHOENIX MANUALLY.
YOU ARE NOW ROOTED WITH TWRP RECOVERY INSTALLED.
REMEMBER TO BACK UP THE CURRENT ROM BEFORE FLASHING ANYTHING..... DO CHECK POST #2 FOR OTHER TWEAKS
IF YOU WISH TO UPDATE TO LATEST STOCK (10U) AND KEEP ROOT AND TWRP, JUST FOLLOW THIS LINK AND DO REMEMBER TO ROOT USING MAGISK AFTER FLASHING THE ROM BEFORE YOU BOOT.
https://forum.xda-developers.com/v20/development/rom-h91810q-stock-rom-twrp-flashable-zip-t3681312
I WOULD LIKE TO THANK ALL THE DEVOLEPERS WHO HAVE CREATED THE ABOVE SOFTWARES WITHOUT WHICH THIS ISNT POSSIBLE.
CREDITS:
@autoprime FOR HIS UPPERCUT TOOL
@steadfasterX FOR HIS FWUL TOOL
@Phoenix591 FOR HIS WORKS ON TWRP RECOVERY
AND FINALLY, @runningnak3d FOR HIS EXCELLENT WORK IN ROOTING OUR DEVICE :good:
WHAT NEXT?
NOW THAT YOU HAVE ROOTED YOUR MOBILE, I WOULD RECOMMEND DOING THE BELOW TWEAKS FOR FURTHER ENHANCED EXPERIENCE....
1.THERMAL THROTTLING
IF YOUR ARE STILL ON A STOCK BASED ROM , I WOULD STRONGLY RECOMMEND TO RECONFIGURE YOUR THERMAL FILE TO PREVENT ANY POSSIBLE LAG WHEN USING EXTENSIVELY...
FIRST DOWNLOAD THE FILE BELOW:
https://drive.google.com/file/d/0B0W3xXHgfOxvLUpKNWhrWDE0TDg/view
USE A ROOT EXPLORER (PREFERABLY ES EXPLORER) AND GO TO ROOT/SYSTEM/ETC.
YOU SHOULD HAVE A FILE NAMED thermal-engine-8996.conf
RENAME IT TO thermal-engine-8996.conf.bak (JUST FOR A BACKUP IF ANYTHING GOES WRONG)
ENSURE THE ABOVE DOWNLOADED FILE IS IN .conf FORMAT
IF IT ISN'T , RENAME TO thermal-engine-8996.conf
NOW SAVE THE FILE TO THE SAME DIRECTORY VIZ ROOT/SYSTEM/ETC
GIVE PERMISSION TO THIS FILE TO rw-r--r-- USING THE ROOT EXPLORER ( SELECT FILE--->PERMISSION--->READ WRITE, READ, READ)
FINALLY SAVE AND REBOOT.
THIS WOULD OVERWRITE THE THERMAL LINKED PERFORMANCE OF THE CPU TO AVOID ANY LAG WHEN USING EXTENSIVELY.
2. RCTD REMOVER
ALSO I WOULD STRONGLY RECOMMEND TO REMOVE THE LG'S RCTD CCMD AND TRITON MONITORS AS THESE WOULD RUN CONTINUOUSLY IN A ROOTED LG PHONE AND CONSUME LOT OF RESOURCES...
JUST INSTALL THE RCTD REMOVER APP FROM BELOW LINK:
https://labs.xda-developers.com/store/app/com.zacharee1.rctdremoverforlg
GRANT SU PERMISSION AND CHECK THE DESIRED FILES (I CHOSE ALL THREE FILES) AND CLICK ON PATCH, FLASH IMAGE AND REBOOT (THIS WOULD PATCH THE BOOT FILE, SO AGAIN IT IS ADVISABLE TO CREATE A BACKUP OF THE CURRENT BOOT IMAGE USING TWRP OR WITHIN THIS APP ITSELF)
3. SCREEN CALIBRATION:
https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor
INSTALL KERNAL AUDITOR APP FROM PLAY STORE AND GRANT SU ACCESS
CHANGE THE BELOW VALUES WITHIN THIS APP (SCREEN SETTINGS)
Minimum RGB value = 35
Saturation Intensity = 27
Screen Hue = 1520
Screen Value = 112
Screen Contrast = 132
THIS WOULD SOMEWHAT REDUCE THE BLUE TINGE AND GHOST APPEARANCES OF THE SCREEN
CREDITS: @Holyman007 for his thermal tweak @Zacharee1 for his rctd remover app
I was just about to create a post asking for a step by step for dummies so thank you very much for this! Going to do this sometime tomorrow or Tuesday and will update if I succeed or not. :good:
Got a question. Does this method stop the second screen from working?
turdbait said:
I was just about to create a post asking for a step by step for dummies so thank you very much for this! Going to do this sometime tomorrow or Tuesday and will update if I succeed or not. :good:
Got a question. Does this method stop the second screen from working?
Click to expand...
Click to collapse
this would end up with a stock rooted phone with twrp recovery if all the methods are correctly followed..
......final result would be.... you would end up with a rooted stock rom with a twrp recovery....
your second screen will work perfectly.....
please let me know if you need a different thread for installing custom rom, and to reduce the lag., install sound mod to get maximum sound output and customize second screen... i will create a noob friendly thread for these as well......
Also check the original lafsploit thread @
https://forum.xda-developers.com/v20/how-to/root-lafsploit-h918-version-t3773443
kish9046 said:
Also check the original lafsploit thread @
https://forum.xda-developers.com/v20/how-to/root-lafsploit-h918-version-t3773443
Click to expand...
Click to collapse
Thank you, I've been reading up on the main lafsploit thread for awhile but I was still not sure about the whole flashing KDZ file and stuff so when you posted this thread it was a motivator to try it out. Got a day off from work tomorrow so gonna try it then so I don't got to worry about the time.
I'm interested in the max sound output and second screen customization if you got the time and its not to much to ask. If you want to wait till either someone else comes along thats interested or till I root just so you don't waste your time I shall update hopefully sometime tomorrow. Thanks again.
kish9046 said:
sha256sum h918-twrp.img ----> THIS WOULD AGAIN THROW A HASH, CHECK IF BOTH THE HASHES ARE ABSOLUTELY SIMILAR
Click to expand...
Click to collapse
Excellent. Just a friendly suggestion, however. I would change the instruction above to use the word EXACT instead of SIMILAR, otherwise people may continue erroneously. The hash numbers must be exact.
onlineaces said:
Excellent. Just a friendly suggestion, however. I would change the instruction above to use the word EXACT instead of SIMILAR, otherwise people may continue erroneously. The hash numbers must be exact.
Click to expand...
Click to collapse
Thanks for the heads up.... Changed to EXACT...
I successfully have root now, thank you! If you're still interested in doing a guide on how to do the second screen customization I'd be grateful.
turdbait said:
I successfully have root now, thank you! If you're still interested in doing a guide on how to do the second screen customization I'd be grateful.
Click to expand...
Click to collapse
great to hear that u have root now.... will post soon on other mods including a step-by-step process on removing rct soon....
All this stuff can be found already in the forums so you posting guides is redundant js
Sent from my LG-H910 using XDA Labs
cnjax said:
All this stuff can be found already in the forums so you posting guides is redundant js
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
Thanks for the suggestion... but i thought this would help noobs like me to explore more about our device without doing any harm to it.....
Glad someone actually laid it out step by step.
kish9046 said:
Thanks for the suggestion... but i thought this would help noobs like me to explore more about our device without doing any harm to it.....
Click to expand...
Click to collapse
so i just wanted to say thank for for the very noobie step by step guide. im soooo use to odion and adb flash commands.
just 1 thing i had trouble with was trying to push magisk and twrp over. I rooted by pushing magisk over with otg but no twrp on recovery. then i saw it said it was on download mode. from dl mode i just flashed twrp to recovery.
BROKEN1981 said:
so i just wanted to say thank for for the very noobie step by step guide. im soooo use to odion and adb flash commands.
just 1 thing i had trouble with was trying to push magisk and twrp over. I rooted by pushing magisk over with otg but no twrp on recovery. then i saw it said it was on download mode. from dl mode i just flashed twrp to recovery.
Click to expand...
Click to collapse
So i assume you have both TWRP and root now?..... And can i ask which version r u in now....ARB0 or 1
kish9046 said:
So i assume you have both TWRP and root now?..... And can i ask which version r u in now....ARB0 or 1
Click to expand...
Click to collapse
Abr1 yes I am rooted with twrp.
As I said, the commands to push magisk and twrp to sd did not work. I used usb otg in twrp to push magisk, but forgot to put twrp to flash as well.
I forgot that twrp had replaced download mode, so I was going a bit nuts trying to figure out how to get twrp to recovery. Lolol
Now I'm on latest update with rtcd removed thanks to the op who hosted it on xda as a flashable zip.
Hi guys, sadly I'm at the last step and got stuck.
I did everything, and managed to get to the part where you WIPE de data using TWRP, Mount, but when I go and type
adb push Magisk...
adb push h18...
I get an error saying that Cannot stat : No such file or directory
I'm unable to figure out what I'm doing wrong
Any idea?
tenkensword said:
Hi guys, sadly I'm at the last step and got stuck.
I did everything, and managed to get to the part where you WIPE de data using TWRP, Mount, but when I go and type
adb push Magisk...
adb push h18...
I get an error saying that Cannot stat : No such file or directory
I'm unable to figure out what I'm doing wrong
Any idea?
Click to expand...
Click to collapse
As you are in twrp, you can manually flash magisk zip and twrp recovery.....
tenkensword said:
Hi guys, sadly I'm at the last step and got stuck.
I did everything, and managed to get to the part where you WIPE de data using TWRP, Mount, but when I go and type
adb push Magisk...
adb push h18...
I get an error saying that Cannot stat : No such file or directory
I'm unable to figure out what I'm doing wrong
Any idea?
Click to expand...
Click to collapse
Download magisk and twrp here https://androidfilehost.com/?fid=746010030569963731
While you are in the last step, in mount, select otg USB. You can push it to SD card and manual flash.
If you booted to system without magisk and flashing twrp, power off the phone, hold volume up, put in the USB, connect to PC. This will put you in twrp since download mode is replaced by twrp.
Now you can flash both files.
tenkensword said:
Hi guys, sadly I'm at the last step and got stuck.
I did everything, and managed to get to the part where you WIPE de data using TWRP, Mount, but when I go and type
adb push Magisk...
adb push h18...
I get an error saying that Cannot stat : No such file or directory
I'm unable to figure out what I'm doing wrong
Any idea?
Click to expand...
Click to collapse
Download magisk and twrp here https://androidfilehost.com/?fid=746010030569963731
While you are in the last step, in mount, select otg USB. You can push it to SD card and manual flash.
If you booted to system without magisk and flashing twrp, power off the phone, hold volume up, put in the USB, connect to PC. This will put you in twrp since download mode is replaced by twrp.
Now you can flash both files.
The BLU VIVO XL4 has arived.
Sorry this guide is not for very new users, it relies on certain amount of prior knowledge.
**NOTE**
Unlocking Bootloader WILL set warranty flag to "NO"
Make the read-back backup, BEFORE unlocking, so there is a possibility to restore warranty to "yes"
Getting SPFlash Tool to work on BLU VIVO XL4
I used sp flash tool version 5.18.28
Needs custom DA file and Auth file. Both have been found from a near clone device.
Open flash tool select the DA file and Auth file from the link below.
add the scatter file from archive. There is a preloader file in the archive also. This is needed for spflash tool to open the Auth file.
Stock Rom and Auth file
Then follow the guide found on youtube.
Not planning to go into too much detail about the actual pulling of the firmware, as there is already
a fantastic guide with step-by-step photos and also a video.
Just the basics
Pull stock rom with spflash tool once just from the "boot region" to get the preloader file.
Process that file with the Wwr_MTK tool to get partition table information.
And one more time pull as one large binary file from the "user region" then split it into
individual images using the tool called "Wwr_MTK" it can be found on other site(Hovatek). I cannot put a
link as it is against forum rules (no advertising other forums)
But there is a youtube video that describes the process. And gives link for download of the tool.
**NOTE-1**
The Wwr_MTK tool did not have the correct chip (mt6762 In fact the "family class" for the chip is mt6765) as an option. Because of this you will need to add it to the tool before using it. Open the downloaded zip.( I used "WwR_MTK_2.40_Eng" ). Open "Template.ini" with text editing software, in the section labeled "CPU" add "MT6765 2" , keep same format as the rest of the file. Save the changes and close Template.ini.
Now when you run the tool, you will be able to create the scatter file as you split the rom into files.
**NOTE-2**
The tool connects to internet and downloads fresh the files and scripts when you start it. There is a 30 second ad screen displayed. If you block internet to the tool, then the add screen turns into 2 minute wait screen. I am not suggesting that you hack the tool to by-pass it, just letting you know what to expect.
IT IS HIGHLY RECOMMENDED TO MAKE YOUR OWN FULL BACKUP BEFORE PERFORMING THESE STEPS
AFTER YOU HAVE MADE FULL BACKUPS
Now to start modifying
DOWNLOAD
UNLOCK BOOTLOADER
unlocking bootloader is no more complicated then then enabling OEM unlock toggle in dev options menu.
Then performing Command in terminal. Just like so many android devices.
Unlock Bootloader
1. Enable Developer options on phone:
open settings--> "about device"--> click build number 5-7 times--> go back one screen in settings
-->select more "more settings" --> scroll to bottom "Develpoer options" --> enable "usb debugging"
2. Open cmd or power shell terminal
3. reboot phone to bootloader with the following commands
Code:
adb reboot bootloader
4.Once the phone has finished loading into fastboot mode type this command
Code:
fastboot oem unlock
I also did --MIGHT be an optional step
Code:
fastboot flashing unlock
Do not think both were needed.
After each command when phone was rebooted,
it took extra time to open. But did not show the normal recovery screen while
it did the factory reset. But a reset did happen both times,
as I had the setup wizard each time.
Even after unlocking bootloader, doing a "fastboot boot *xyz.img" (boot or recovery test images)
Phone would only cycle to off then do a full reboot. Doing "fastboot flash boot boot.img" does flash the boot.
And "fastboot flash recovery recovery.img" does flash the recovery.
TWRP
1. Download TWRP From Link above
2. Enable Developer options on phone:
open settings--> "about device"--> click build number 5-7 times--> go back one screen in settings
-->select "more settings" --> scroll to bottom "Develpoer options" --> enable "usb debugging"
3. Open cmd or power shell terminal
4. reboot phone to bootloader with the following commands
Code:
adb reboot bootloader
5. Now give the command to flash twrp, assuming you downloaded the file to default download folder
Code:
fastboot flash recovery %userprofile%\downloads\TWRP-3_2_3-1020-OMFG-mod_b6-device-name-vivo-wipe-misc.img
5. Reboot to twrp. Needed to boot directly to twrp, or stock recovery will be re-flashed by phone.
Code:
fastboot oem reboot-recovery
Once inside twrp It is asking for password to unlock (decrypt)***automatic decrypt not work on this device as of YET***
this is supposed to be same password used to unlock phone.
Because this twrp does not work with encryption, every time you reboot you will have to select language, if changed from default.
To get recovery to be functional, you need to make phone patched for both "DM-Verity" and "Force-encryption"
I do this with
"Universal Disabler"
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
There is similar utiliy built into this Recovery image.
to use the built in option , Select ADVANCED, Then RM Forceencrypt
This will flash the lazypatcher with options set to remove encryption both in boot.img and /vender/*fstab : remove dm-verity.
--OR-- manually do the following steps
Steps
1. Download Zip from Link above.
2. Open TWRP
3. Open Wipe menu
4. Select format /data
5. Key in "YES" and swipe
6. Return to Home Page of TWRP
7. Choose reboot menu then recovery
8. Recovery should now have access to Internal memory (temp for now)
9. Use abd push to put the zip file downloaded above to internal memory
Code:
adb push %userprofile%\downloads\Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip /sdcard/
10. Select install menu , and install the Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip
Do not rename the file. It installs and makes the patch base on the file name.
If you want to have root also, then flash Magisk at this point.
Now the dm-verity and force encryption are off. You can flash gsi custom rom, if you desire. At the moment, I have only been able to boot the phone with working cell data and calls on the PHH-Phusion --vanilla builds. Do not know why the gapps versions do not allow rill to function.
As of the writing of this I have put up V4 of the TWRP port. This version uses the correct mount points for this phone, not the ones from the source of the port. Also corrected the device name in default.prop, to match device name. Build fingerprint has been left as is. Fixed the micro sdcard name and OTG names. Added mipe to the "misc" /"para" partition to escape a factory reset recovery loop that [uu]could[/u] happen under certain situations.
And my prefered ported recovery from LRTeam TWRP-3_2_3-1020-OMFG-mod_b6-device-name-vivo-wipe-misc.img.
DOWNLOADS
Files
1. Sp Flash tool (v 5.18.28 or newer) https://androidmtk.com/smart-phone-flash-tool
2. stock XL4 ROM, DA file, TWRP all in shared folder https://androidfilehost.com/?w=files&flid=287088
3. stock Xi+ ROM, TWRP in shared folder https://androidfilehost.com/?w=files&flid=287703
4. Unviversal DM-Patch disable tool thread
5. Youtube Guide Video to use backup image splitter tool "WWR_MTK" https://www.youtube.com/watch?v=GMAytZ56hac
Kernel sources have been published 12-12-2018, by BLU
I have them synced to GitHub while I make test builds.
https://github.com/mrmazakblu/BLU-VIVO-XL4-kernel
Default defconfig should be arch/arm64/config/k62mv1_64_bsp_defconfig. Based off of build description in "getprop"
Built kernel has not been able to be booted yet.
TWRP is first ported and provided thanks to @Voinea12
.
placeholder not really welcomed here on XDA
just pm a moderator or report this thread when you`re ready to upload something, until then, thread closed
After seeing that the Blu vivo xl4 requires an "auth file" in order to flash with spflash tool, I asked BLU to supply the file.
They responded with a big fat NO.
.......
.......
THE NEXT DAY THE FILE WAS POSTED ON A DIFFERENT THREAD.
SO THERE HELP WAS NO LONGER NEEDED.
Just made successfull readback on preloader. and currently reading full rom.
will post link when done.
here is auth file and DA file I used.
pulled firmware is here.
there are more images in complete firmware, but the ones included should be enough , as long as you NEVER do format all from spflash tool.
STOCK ROM
So far all attempts to load twrp have failed.
Also just tried to flash boot.img with the built kernel. When rebooted, phone just stayed on black screen. No back-light , nothing.
Just a repeating connect disconnect sound from pc. Long pressing power and trying to get into the bootloader menu failed.
Was able to Que up sp flash tool and keep holding the volume down button , on the next time it cycled on off preloader was caught and i was able to flash back the correct boot.img.
Working version is available now
Thread was opened.
mrmazak said:
So far all attempts to load twrp have failed.
Also just tried to flash boot.img with the built kernel. When rebooted, phone just stayed on black screen. No back-light , nothing.
Just a repeating connect disconnect sound from pc. Long pressing power and trying to get into the bootloader menu failed.
Was able to Que up sp flash tool and keep holding the volume down button , on the next time it cycled on off preloader was caught and i was able to flash back the correct boot.img.
Click to expand...
Click to collapse
My streak with SP Flash is still a losing one, the auth file works for my phone as well (Blu Vivo XI+), I just used the preloader.img that was in the update.zip and ran it through the WwR MTK Tool and got the preloader.bin to go with the auth file as you indicated you had done, that was one hurdle that your post helped me solve, but for some reason when I start reading the full rom I get about 6-10 MB into it and then it disconnects from my phone and stops. Not sure if its driver related or what, which drivers did you use for the readback?
psychofad said:
My streak with SP Flash is still a losing one, the auth file works for my phone as well (Blu Vivo XI+), I just used the preloader.img that was in the update.zip and ran it through the WwR MTK Tool and got the preloader.bin to go with the auth file as you indicated you had done, that was one hurdle that your post helped me solve, but for some reason when I start reading the full rom I get about 6-10 MB into it and then it disconnects from my phone and stops. Not sure if its driver related or what, which drivers did you use for the readback?
Click to expand...
Click to collapse
To be honest I have not installed driver specific for this. I have vcomm drivers installed, same from couple years ago.
Is the readback stopping because you set wrong hex address length in the readback tab?
mrmazak said:
To be honest I have not installed driver specific for this. I have vcomm drivers installed, same from couple years ago.
Is the readback stopping because you set wrong hex address length in the readback tab?
Click to expand...
Click to collapse
No, I got the readback of the EMMC_USER just fine and ran it through the WwR MTK tool and it gave me the hex address to use for the full rom readback, t then told me
Code:
The file size is smaller than the start position of the LK (uboot). To determine the type of processor and memory, it is necessary to read the full firmware in the SP Flash Tool, specify the parameters for reading: Start address: 0x0, Lenght: 0x1D1EC00000.
So I entered those two addresses as EMMC_USER readback. If my phone is off and I just connect it to the usb without holding any keys it gives me another error.....and I'm an idiot. just figured it out as I was looking at logs, apparently I must have changed the usb speed in sp flash which changes it's pid causing it to try and read from another port. It's downloading now
Thanks to @hanuma there is now a material themed twrp port.
The V2 version loads. But has no adb or mtp access
https://forum.xda-developers.com/showpost.php?p=78498431&postcount=95
https://mega.nz/#F!225EzQwT!t8hvGvmFoNYNvXev-Li1fQ
******EDIT*****
Most of the following problems did not repeat in same way when I tried to repeat the install process.
Main issue was with simcard. But exact process to get installed and working is still not known.
-- install after already having rooted, encryption removed stock, seems to work.
-- fresh full stock rom, full encryption, then gsi seems to not work sim card.
PHH-treble gsi images do boot this device. I do not have a bug list as yet.
working:WITH encryption removed:
1. wifi
2. camera
3. fingerprint- unlock
4. music
5. video
NOT working :WITH encyyption removed:
1. cell signal
2. cell data
3. phone
4. sms
---------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------
working:WITH encryption enabled
1. phone
2. sms
NOT working:WITH encryption enabled
1.. everything else
EDIT
Much of the force closing problems were from a corrupted external sdcard. When I removed the card , the force close messages did not come.
Getting 4G data connection was not stable. after a full reset and rom re-install I was not able to get data connection, and only able to have connection to make calls when set to 3G connection only.
some bugs in vendor I assume will need some help solving this.
EDIT 2
Finally got around to trying again. his time I started with vanilla version of phh-treble gsi.
4G data and sms, calls in out all work. Camera , video both work.
WiFi tethering did not work.
Setup that worked :
force encryption removed with universal dm-verity patcher, ( bothboot.img and vendor partitions both edited).
magisk patched boot
Would this work on Blu Vivo XI since same chipset?
sinkoo1979 said:
Would this work on Blu Vivo XI since same chipset?
Click to expand...
Click to collapse
It should. I have been working with few users with Xi+ it works for them. And another user of Xi provided a twrp port, but no details on if this read-back worked. It must have, I suppose it must have.
Please do try to do the readback for your self, and share the files. will help with twrp if I can
Guide has been revised.
The original guide suggests to format /data and patch device to remove force encryption. This works fine for stock rom, and modifying stock rom. But I have found that removing encryption will not allow the phone to work as a phone when flashed with GSI. The down side is, at the moment, there is no twrp that is working to read the encrypted /data.
mrmazak said:
Guide has been revised.
The original guide suggests to format /data and patch device to remove force encryption. This works fine for stock rom, and modifying stock rom. But I have found that removing encryption will not allow the phone to work as a phone when flashed with GSI. The down side is, at the moment, there is no twrp that is working to read the encrypted /data.
Click to expand...
Click to collapse
Can any of this be done without a computer
Decaphyz said:
Can any of this be done without a computer
Click to expand...
Click to collapse
No, you need fastboot(PC preogram) to unlock bootloader and either sp flash tool or fastboot to flash recovery.
mrmazak said:
No, need you fastboot(PC preogram) to unlock bootloader and either sp flash tool or fastboot to flash recovery.
Click to expand...
Click to collapse
Oof
mrmazak said:
Thanks to @hanuma there is now a material themed twrp port.
The V2 version loads. But has no adb or mtp access
https://forum.xda-developers.com/showpost.php?p=78498431&postcount=95
https://mega.nz/#F!225EzQwT!t8hvGvmFoNYNvXev-Li1fQ
Click to expand...
Click to collapse
I just did this, and it worked the first time. I got into the phone and set it up. But it was super laggy after a while. So I decided to reset the phone like how you would normally do to fix a problem, and now... it’s making me boot into the recovery each and every time I try and boot into the system... i installed the gsi rom "PixelExperience for AOnly" at max lees site
IndifferentBear said:
I just did this, and it worked the first time. I got into the phone and set it up. But it was super laggy after a while. So I decided to reset the phone like how you would normally do to fix a problem, and now... it’s making me boot into the recovery each and every time I try and boot into the system... i installed the gsi rom "PixelExperience for AOnly" at max lees site
Click to expand...
Click to collapse
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
thanks dude! can you give me the command to run in terminal to do it? ill try that first, then ill try flashing stock recovery!
---------- Post added at 02:47 AM ---------- Previous post was at 02:44 AM ----------
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
but i was required to wipe the sys, data, cache, and dalvik/art to have a clean install.
---------- Post added at 03:33 AM ---------- Previous post was at 02:47 AM ----------
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
YO! Oaky so basic laly when i flashed that misc recovery IT BOOTED!!!!! thank you soo much dude, your the best!
Welcome to this little thread in which I'll provide every useful information about this device based on my and other users's experiences. If you know something, that I didn't mention, please reply to this thread in order to help out each other even more effectively. Thanks and pleasant reading!
The Lenovo S5 Pro is a very decent mid-ranger with good specs and even better pricing. We all know, that chinese manufacturers tend to install bloatware on their products time to time. In our case, Lenovo didn't release a single update since 2018 Novemer to this device. It means, that it came out with Android 8.1 Oreo (2018 November Security Patch) and left untouched. This is even worse, than Meizu which is famous for it's neglecting policy of software updates for global users. Now, that we know all this, it's not a surprise, that we are here on our favourite developer forum.
*** General information | Links | Downloads | Credits ***
The official global firmware is now saved and available (thanks to our forum member nikosddesign) here: download & link to the post
Everything you will possibly need (PC software, drivers, stock camera app, VoLTE modem etc...) is available in this Yandex Disk, you just have to navigate to each one. (Most of the content is in russian, since Yandex is the russian Google, but it's not hard to find the files you'll need).
The previous links and the following tutorials are only available, because suninterbru (from 4pda forums) and radiationofthenation provided these informations and the tutorials, also so much thanks to everybody on the 4pda forums, who provided useful information and files, большое спасибо!
Even though the bootloader unlock, TWRP install and rooting should not cause data loss, be careful and create a backup. You can back up only your files and data or your whole ROM, it's up to you.
Please note, that after you've unlocked your bootloader, everytime your reboot or turn on your phone a warning will pop up during the boot process for about 1 second. On Android 9.0 Pie vendor the message pops up for about 5 seconds. The warning is about the side effects of modifying the system software and it also says, that it is not recommended to store any personal data on your device anymore. Please ignore this message, since it's only popping up, because manufacturers usually don't like, if you modify your device.
Pro tip: If you keep pressing your power button for a little longer you can skip the alert and boot faster.
*** Bootloader unlock ***
Please note, that your warranty will become invalid/void after you unlock your bootloader or root your device.
0. In your device's developer settings enable bootloader/OEM unlock and USB debugging.
1. Visit the official ZUI bootloader unlock website.
2. Enter your IMEI1 number in the first field. (You can find your IMEI numbers in Settings\About or in the dialer enter: *#06#).
3. Enter your serial number in the second field. (You can find your serial number in the fastboot menu). The one in the settings is not good in this case! (To access the fastboot menu, turn off your phone, then press the power button and after you see your screen light up, immediately press the volume down (-) button or while it's turned on and USB Debugging is enabled, simply type in the terminal/cmd ,,adb reboot bootloader").
4. In the next field enter your email adress. (Please note, that Tutanota won't work, Gmail is recommended or other not secure email providers).
5. Enter the verification numbers in the last field.
6. Tick the checkbox.
8. Click on the blue button.
7. Now check your inbox and/or spam folder, because Lenovo just sent you your custom sn.img, only for your phone.
8. Save the sn.img to your PC and install ADB drivers system-wide. (Thank you Snoop05 for your work)!
9. Open a terminal/cmd on Windows. You should be in the same directory, where your sn.img file is, with the terminal. To change directories type ,,cd your directory goes here" and hit ENTER.
10. Run the following commands:
- adb reboot bootloader
- fastboot flash unlock sn.img
- fastboot oem unlock-go
11. Congratulations! Your bootloader is now unlocked!
*** TWRP Recovery ***1. Download the .img file from here.
2. The steps are similar to the bootloader unlocking:
- adb reboot bootloader
- fastboot flash ,,downloaded" .img
- After the flashing is done DON'T reboot to the system, instead navigate to the ,,Reboot Recovery or Recovery Reboot" option and select it. (Volume keys and power key - you know the drill) This will ensure, that the TWRP Recovery doesn't get ereased on reboot(s)!
3. After you've successfully rebooted into TWRP, you should root your device with Magisk, to prevent the recovery erasure!
*** ROOT ***1. The good old SuperSU is no longer in the picture, but don't worry a new player is in the game. Download Magisk from here. (Thank your for your work topjohnwu)!
2. After you've downloaded the flashable .zip copy it to the main directory/root of your device.
3. Reboot to TWRP.
4. Click install, select the flashable .zip file.
5. The installation process should start.
6. Reboot, after finished.
7. Check if Magisk Manager is installed or not, if yes tap and update it.
8. If you did not succeed, please check the Magisk topic for solutions or reply to this thread.
*** Factory reset | Stock ROM | Unbrick | LOST IMEI/PERSIST/EFS | QCN BACKUP/RESTORE ***
!!! NEVER EVER TICK ,,ERASE ALL BEFORE DOWNLOAD" IN QFIL, OTHERWISE YOU WILL LOSE YOUR IMEI AND THE ABILITY TO CONNECT TO MOBILE NETWORKS !!!
If you accidentally clicked on that option you will have to restore someone elses QCN backup. (It will not work, if you backup your own QCN and rewrite your IMEI and restore it, so do not waste your time with that)! Luckily, a member of the 4PDA forums published their qcn backup. (большое спасибо geepnozeex)! QCN backup for Lenovo S5 Pro. (I modified the link, because the original one is no longer valid)
1. Download the linked QCN file.
2. Make sure, that you are on one of the Stock ROMs, however the recommended ROM is this one.
3. You will have to be rooted to put your device in diagnostics mode. To do that, follow this tutorial.
4. You will have to edit the QCN file with HxD, in order to write your own IMEI into.
5. Open the file with HxD and search for 08 8A 76 06 06 14 57 95 32. This is the IMEI 2. You will have to insert your IMEI 2 from the box here, but first you will have to convert it into Hexadecimal numbers.
6. Convert your IMEIs into Hexadecimal numbers here.
7. You will have to rewrite and insert your values insted of the previous one.
8. Search for 08 8A 76 06 06 04 67 98 72. This is IMEI 1. Convert your IMEI 1 into Hexadecimal numbers, too and replace.
9. Save the file (Ctrl + s)
10. Open QFIL and click on Tools, then QCN Backup/Restore.
11. Choose the QCN file, you wrote your IMEI into.
12. Click on Restore QCN.
13. There is a chance, that the process/progress bar won't finish till the end. No problem, just reboot to EDL mode through TWRP/Advanced and restore the recommended stock ROM.
14. You should have everything working fine, now.
To factory reset or unbrick your device, follow this tutorial on 4PDA. [Don't panic you don't have to know russian, just follow the instructions on the pictures! To see the pictures, click on the bold text.] ,,(спойлер (+) (Инструкция по прошивке)" ~ or ~ Download any of the previously linked STOCK ROMs to your device's main folder and flash them through TWRP. Most of them are in flashable .zip formats and should work well. A simple factory reset in TWRP is recommended before installing any of the ROMs, be careful this action will erease your data from your phone!
(Please note, that most of the time you'll have to use the QPST/QFIL method, because the flashable .zip files always expect a specific vendor version, usually a lower one, so you can upgrade with flashable .zips, but possibly can't downgrade, so you have to use QFIL)!
*** GSI custom ROMs ***
Our device is arm64-aonly, so please only use according GSIs. Note, that I will link only those GSIs, which are booted successfully on my device!
~ phhusson's official GSI list: here
~ phhusson's AOSP GSI (Android Open Source Project): here
~ developerluke's ExpressLuke GSIs: here
~ eremitein's CAOS GSI Project: here
~ eremiten's LOSQ GSI Project: here
~ igors1974's Amber GSIs: here
~ tunasahinn's and yek4perf's Tunahan's GSI builds: here
~ mrsshunt3r's albus-gsi: here
Note, that you should keep up with the developments and update your system, if needed! These are just a few GSIs, that I've tested personally on my phone, but you can always keep up with the latest news and try new GSIs out, thanks to phhusson's official GSI list!
*** How to flash an Android 10 GSI ***
1. Download the latest custom phh-magisk from here. (Thank you developerluke and phhusson)!
2. Download the latest Disable_Dm-Verity_ForceEncrypt from here. (Thank you Zackptg5 and others)!
3. Download your desired GSI.
4. You can flash from an USB-OTG flash drive or from the storage of your phone. (I personally have a dedicated USB for this purpose).
4.1 If you are coming from stock ROM you will most likely need to Format Data in this step, because the Disabler won't be able to decrypt the data and, that will cause a stuck at the boot logo!
4.2 Reboot Recovery
5. In TWRP perform a normal factory reset
6. Flash Disable_Dm-Verity_ForceEncrypt. (Cache wipe is optional).
7. Flash your GSI image.
8. Format Data (Skip this step if you already did this in 4.1)!
9. Reboot Recovery (Skip this step, too if you already did this in 4.2)!
10. Flash Magisk-phh
(11. Wipe cache/dalvik).
12. Reboot System
13. Enjoy!
*** Possible GSI bugs ***
Please note, that bugs can differ/vary on different GSIs, the numbers are not fully accurate!
1. The default camera app will work, however it doesn't support HDR, panorama or portrait modes. It also can't record in 4K resolution. Freezing is also possible. ~ 50%
2. First time, when you open the camera it'll stuck on loading, but after you go back and open it again it will work flawlessly. ~ 50%
3. No audio/microphone during phone calls. ~ 15%
*** Guaranteed GSI bugs*** 1. The infrared face unlocking will not work, only fingerprint authentication is working. ~ 100%
2. You won't be able to charge your device while it's turned off, after you plug it in, it will automatically boot up. ~ 100%
3. Auto brightness. ~ 100% (There is a fix for auto brightness below)!
*** Camera fix (GSI) ***
(If you get ,,serious camera error" or your camera freezes on HDR)
1. Download a custom camera app, where you can manually adjust the ISO level.
2. With OpenCamera, for example you have to adjust ISO to 800 and never above, because your camera will freeze!
3. So, always keep ISO 800 or under. With these settings even HDR shots are working!
*** Auto brightness (GSI) ***1. Download framework-res__auto_generated_rro.apk from this thread.
2. Follow the instructions, which are described in this post. (You will need to have root to use ,,su" commands).
3. Thank you MishaalRahman and kAs1m for the apk and the instructions!
Twrp disappears when restarting
Help, twrp disappears when restarting. After installing it by: "fastboot flash recovery trwp.img". right there I start it with the "Vol + Power" keys and it starts correctly but when you turn it off and back in, "stock recovery" appears again. I also installed it again using the same twrp, but it disappears again.
kcire_eae said:
Help, twrp disappears when restarting. After installing it by: "fastboot flash recovery trwp.img". right there I start it with the "Vol + Power" keys and it starts correctly but when you turn it off and back in, "stock recovery" appears again. I also installed it again using the same twrp, but it disappears again.
Click to expand...
Click to collapse
Hello, please don't reboot after sending the recovery image to the phone. Execute the:" fastboot reboot recovery " command. Now it is going to work.
Halwer said:
Hello, please don't reboot after sending the recovery image to the phone. Execute the:" fastboot reboot recovery " command. Now it is going to work.
Click to expand...
Click to collapse
It didn't work, given: "fastboot: usage: unknown reboot target recovery" Sorry for the long time to answer, I only have mobile data, and from this same mobile I answer, and I use google translator, I'm from Mexico.
Halwer said:
Hello, please don't reboot after sending the recovery image to the phone. Execute the:" fastboot reboot recovery " command. Now it is going to work.
Click to expand...
Click to collapse
Foto
kcire_eae said:
Foto
Click to expand...
Click to collapse
Well, it looks good. Maybe only " reboot recovery " is enough.
Halwer said:
Well, it looks good. Maybe only " reboot recovery " is enough.
Click to expand...
Click to collapse
It didn't work, friend, but I appreciate the help.
kcire_eae said:
It didn't work, friend, but I appreciate the help.
Click to expand...
Click to collapse
I'm sorry. Do an internet search and check related TWRP forums for solutions for this specific issue. For me everything is working fine. Are you sure you unlocked your bootloader first?
Halwer said:
I'm sorry. Do an internet search and check related TWRP forums for solutions for this specific issue. For me everything is working fine. Are you sure you unlocked your bootloader first?
Click to expand...
Click to collapse
Help, I did the following and I no longer start my mobile:
-fasboot flash recovery twrp.img.
-fasboot flash boot twrp.img.
-fasboot reboot.
now just start twrp even if restart restart twrp again, in the twrp browser my sdcard files are shown, maybe you can still help me please.
kcire_eae said:
Help, I did the following and I no longer start my mobile:
-fasboot flash recovery twrp.img.
-fasboot flash boot twrp.img.
-fasboot reboot.
now just start twrp even if restart restart twrp again, in the twrp browser my sdcard files are shown, maybe you can still help me please.
Click to expand...
Click to collapse
You should not have flash the recovery image to the boot partition. These partitions are not the same, be careful! Now you can save your data from TWRP via MTP connection to your computer. After that restore your phone with QPST to the latest pie ROM or to the oreo ROM from yandex. The oreo ROM is flashable from recovery, it is easier.
Halwer said:
You should not have flash the recovery image to the boot partition. These partitions are not the same, be careful! Now you can save your data from TWRP via MTP connection to your computer. After that restore your phone with QPST to the latest pie ROM or to the oreo ROM from yandex. The oreo ROM is flashable from recovery, it is easier.
Click to expand...
Click to collapse
Is it possible to just flash the boot partition (boot) again, if I get the boot.img from another rom?
I don't want to lose the stock rom:crying:
kcire_eae said:
Is it possible to just flash the boot partition (boot) again, if I get the boot.img from another rom?
I don't want to lose the stock rom:crying:
Click to expand...
Click to collapse
Maybe you can try to download a ROM file, extract it and flash the boot image, but I'm not sure if it is going to work.
Halwer said:
Maybe you can try to download a ROM file, extract it and flash the boot image, but I'm not sure if it is going to work.
Click to expand...
Click to collapse
I'm going to try, and even,
on this page there are android 9, will it be true?
"https: // mirrors.lolinet.com/ firmware / lenovo /l58041/"
but first I will do it with the "O" stock, which you mention here.
I hope it will work again.
kcire_eae said:
I'm going to try, and even,
on this page there are android 9, will it be true?
"https: // mirrors.lolinet.com/ firmware / lenovo /l58041/"
but first I will do it with the "O" stock, which you mention here.
I hope it will work again.
Click to expand...
Click to collapse
You should do the oreo version, if your were on the global oreo ROM. After that you can try the pie version, if nothing works don't worry you can do a backup of your data from twrp to your computer and flash a custom ROM or the chinese Pie version, which is recommended. With root access you can easily debloat the chinese ROM and with AdAway you can disable all communications pointing to chinese servers or websites. I also found these. Maybe you can give them a try.
After a few hours I was finally able to install the "Chinese stock rom", although I struggled, since the files of the "rom" of the l58041 do not quite coincide with the "stupdroid" tutorial and some files have two different versions, something like that:
here I chose the "ddr" .
prog_emmc_firehose_xxxx_ddr.mbn (.elf). prog_emmc_firehose_xxxx.lite.mbn (.elf).
here I chose the "retain_userdata".
rawprogram0.xml. rawprogram0_retain_userdata.xml.
and in qfil "Flat Build", however I don't know if it was the right thing because at the beginning I was asked for a password ("but that's another topic").
To add a language (without root), use local more apk.
"https: // c. mi. com / thread-2098669-1-0.html"
To root the "radiationofthenation" thread worked me.
"https:. //forum .xda-developers . com/general/help/lenovo-s5-pro-root-global-firmware-help-t3895643/page2"
kcire_eae said:
After a few hours I was finally able to install the "Chinese stock rom", although I struggled, since the files of the "rom" of the l58041 do not quite coincide with the "stupdroid" tutorial and some files have two different versions, something like that:
here I chose the "ddr" prog_emmc_firehose_xxxx_ddr.mbn (.elf). prog_emmc_firehose_xxxx.lite.mbn (.elf).
here I chose the "retain_userdata" rawprogram0.xml. rawprogram0_retain_userdata.xml.
and in qfil "Flat Build", however I don't know if it was the right thing because at the beginning I was asked for a password ("but that's another topic").
To add a language (without root), use local more apk.
"https: // c. mi. com / thread-2098669-1-0.html"
To root the "radiationofthenation" thread worked me.
"https:. //forum .xda-developers . com/general/help/lenovo-s5-pro-root-global-firmware-help-t3895643/page2"
Click to expand...
Click to collapse
I'm glad it is working for you now. Yes, you are right the tutorials flap at some points, but there are other tutorials which you can follow and make it work. For the first time I was struggling with the restoration, too. You will see, that the chinese ROM is quite good, you just have to uninstall the bloatware and disable spying DNS requests.
Halwer said:
I'm glad it is working for you now. Yes, you are right the tutorials flap at some points, but there are other tutorials which you can follow and make it work. For the first time I was struggling with the restoration, too. You will see, that the chinese ROM is quite good, you just have to uninstall the bloatware and disable spying DNS requests.
Click to expand...
Click to collapse
Ohh, explain more about spying. And also if you know something about the message that Android told me when I start. I remember that I flashed twrp.img using "fastboot", and when I asked for a password to decrypt, it only allowed me to clear cache and dalvit cache (I did wipe), and when I started again I showed a message saying that I was encrypting and a percentage, just here, I interrupted the process by turning off the cell phone, and flashed again with qfil (download). So when I start I just remember that I said something about the cell phone being restored and then I could restore the copy with my Google account. So what I think is that when the message of "TO START ANDROID ENTER YOUR PASSWORD" is displayed, it may work to interrupt or perhaps to put the incorrect password many times to automatically reset or also choose "rawprogram0.xml" in qfil (but I did not dare because it deletes it the information related to the imeil and the signal or at least that says some comments ). Now there is only one who can interpret what happened and to have clearer the restoration process, the rom seems to me very much the problem of the language is solved with "more local", I am from Mexico (At & t).
good morning i have good new
i have been backing up the global rom
just wants to go a long time it is super compressed 3.5giga and it is regular size 10.6 g
nikosddesign said:
good morning i have good new
i have been backing up the global rom
just wants to go a long time it is super compressed 3.5giga and it is regular size 10.6 g
Click to expand...
Click to collapse
Thank you, I'm sure some people will find it very useful!
Hello
it's about 4gigabyte have to be patient.
i have very bad internet connection...
ROOT (ALMOST) EVERY DEVICE WITH MAGISK + FASTBOOT
As an Android user, I understand how frustrating it will be when you desperately look for an exact rooting tutorial for your device but end up finding nothing, all one-click root tools do not work, or no custom recovery made for yours.
So, this tutorial shows you how to root a wide range of Android devices (not all, because there will be exceptions, I guess) with Magisk. First, we should take a look at the pros and cons, so that you can generally acknowledge this method.
---------------------------------------------------------------------------
PROS
- No custom recovery (TWRP, ClockworkMod,etc.) needed
- Easy to find prerequisites
- Successful root attempt CONFIRMED on my 10 devices (including popular devices, rare devices, and devices with OS based on Android)
- Support recent Android versions, including Android 10 (tested on Google Pixel XL).
CONS
- Phone brick might occur
- You might not find your device's firmware in .zip format, which will stop you from using this method.
- Not being able to unlock the bootloader (only on some device) will stop you from using this method, too.
That's about the pros and cons. I hope you guys all understand these points before going to read my tutorial and start your attempt.
---------------------------------------------------------------------------
REQUIREMENTS & STEPS
I. REQUIREMENTS
- Your device's Android version is 5.0 or up. If it's below 5.0, then you can root your device easily with any one-click tool.
- A computer & USB cable.
On your phone
- Download & install Magisk
- Download the exact firmware version (in .zip format) of your device and only extract the boot.img to any directory.
On your computer
- Download & install Fastboot, extract the folder to "Downloads" directory
- Download & install Android USB driver for Windows
(I am not sure if XDA allows inserting links in threads or not, so please search for these prerequisites on the internet, it is easy)
II. STEPS
1. Unlocking your phone's bootloader
- Open Settings > About phone > Tap on Build number about 7 times till you see a notification "You are now a developer"
- Now in the About phone tab, you can see the "Developer option". Tap on it and make sure:
+ the OEM unlocking is turned ON
+ The USB Debugging is turned On
- Plug your phone on your computer (with Fastboot & driver fully installed). Allow the USB Debugging notification on your phone
- Open Command Prompt on your computer. Enter commands below steps by steps:
cd Downloads
cd fastboot
adb reboot bootloader
(press Enter after each line to proceed)
- Your phone will reset to the bootloader menu after these commands. Next, enter this:
fastboot oem unlock
- A message asking you to make sure you want to unlock the bootloader. Use the volume and power button to choose "Yes". Your phone will reset data and reboot right after.
*Note: This method works on many Android devices, but doesn't on many devices. You might have to google a method for your own phone
2. Patching the boot.img file
After you extracted the boot.img from your device, use the Magisk app installed on your device to patch it up.
- Click the "Install" button on the first line
- Click "Select and Patch a file"
- Choose the boot.img file extracted. The patching progress will start right after.
- You will receive a file named "magisk_patched.img" after finished.
3. Flashing the "magisk_patched.img"
- Copy the "magisk_patched.img" into the Fastboot folder
- Reboot your phone to Bootloader mode by powering off and then hold Power + Volume down button simultaneously
- Open Command Prompt again, and type:
cd Downloads
cd fastboot
fastboot flash boot magisk_patched.img
- The flashing progress will begin. Wait until it finishes, and type the last command:
fastboot reboot
- Your phone will restart once again, and of course, with root access gained
---------------------------------------------------------------------------
UNROOT DEVICE
- If you want to unroot your device, you just have to flash the original boot.img file, with the same steps with flashing the magisk_patched.img!
---------------------------------------------------------------------------
This instruction is not truly detailed, so maybe you might encounter some difficulties at some point. If any, please feel free to leave your question below.
It is also the first time I create an instruction post, therefore I appreciate all of your comments. Thanks a lot <3
richarshub said:
ROOT (ALMOST) EVERY DEVICE WITH MAGISK + FASTBOOT
As an Android user, I understand how frustrating it will be when you desperately look for an exact rooting tutorial for your device but end up finding nothing, all one-click root tools do not work, or no custom recovery made for yours.
So, this tutorial shows you how to root a wide range of Android devices (not all, because there will be exceptions, I guess) with Magisk. First, we should take a look at the pros and cons, so that you can generally acknowledge this method.
---------------------------------------------------------------------------
PROS
- No custom recovery (TWRP, ClockworkMod,etc.) needed
- Easy to find prerequisites
- Successful root attempt CONFIRMED on my 10 devices (including popular devices, rare devices, and devices with OS based on Android)
- Support recent Android versions, including Android 10 (tested on Google Pixel XL).
CONS
- Phone brick might occur
- You might not find your device's firmware in .zip format, which will stop you from using this method.
- Not being able to unlock the bootloader (only on some device) will stop you from using this method, too.
That's about the pros and cons. I hope you guys all understand these points before going to read my tutorial and start your attempt.
---------------------------------------------------------------------------
REQUIREMENTS & STEPS
I. REQUIREMENTS
- Your device's Android version is 5.0 or up. If it's below 5.0, then you can root your device easily with any one-click tool.
- A computer & USB cable.
On your phone
- Download & install Magisk
- Download the exact firmware version (in .zip format) of your device and only extract the boot.img to any directory.
On your computer
- Download & install Fastboot, extract the folder to "Downloads" directory
- Download & install Android USB driver for Windows
(I am not sure if XDA allows inserting links in threads or not, so please search for these prerequisites on the internet, it is easy)
II. STEPS
1. Unlocking your phone's bootloader
- Open Settings > About phone > Tap on Build number about 7 times till you see a notification "You are now a developer"
- Now in the About phone tab, you can see the "Developer option". Tap on it and make sure:
+ the OEM unlocking is turned ON
+ The USB Debugging is turned On
- Plug your phone on your computer (with Fastboot & driver fully installed). Allow the USB Debugging notification on your phone
- Open Command Prompt on your computer. Enter commands below steps by steps:
cd Downloads
cd fastboot
adb reboot bootloader
(press Enter after each line to proceed)
- Your phone will reset to the bootloader menu after these commands. Next, enter this:
fastboot oem unlock
- A message asking you to make sure you want to unlock the bootloader. Use the volume and power button to choose "Yes". Your phone will reset data and reboot right after.
*Note: This method works on many Android devices, but doesn't on many devices. You might have to google a method for your own phone
2. Patching the boot.img file
After you extracted the boot.img from your device, use the Magisk app installed on your device to patch it up.
- Click the "Install" button on the first line
- Click "Select and Patch a file"
- Choose the boot.img file extracted. The patching progress will start right after.
- You will receive a file named "magisk_patched.img" after finished.
3. Flashing the "magisk_patched.img"
- Copy the "magisk_patched.img" into the Fastboot folder
- Reboot your phone to Bootloader mode by powering off and then hold Power + Volume down button simultaneously
- Open Command Prompt again, and type:
cd Downloads
cd fastboot
fastboot flash boot magisk_patched.img
- The flashing progress will begin. Wait until it finishes, and type the last command:
fastboot reboot
- Your phone will restart once again, and of course, with root access gained
---------------------------------------------------------------------------
UNROOT DEVICE
- If you want to unroot your device, you just have to flash the original boot.img file, with the same steps with flashing the magisk_patched.img!
---------------------------------------------------------------------------
This instruction is not truly detailed, so maybe you might encounter some difficulties at some point. If any, please feel free to leave your question below.
It is also the first time I create an instruction post, therefore I appreciate all of your comments. Thanks a lot <3
Click to expand...
Click to collapse
It's different for a/b devices where root has to be accessed by booting into the phone from recovery to boot with root
([emoji3590]09-09-18[emoji3590])
PoochyX said:
It's different for a/b devices where root has to be accessed by booting into the phone from recovery to boot with root
([emoji3590]09-09-18[emoji3590])
Click to expand...
Click to collapse
Hi PoochyX,
Thanks for your reply, could you be more specific, please? Does it mean that this method cannot work on a/b devices?
I will edit my instruction again if needed.
Thanks for your suggestions!