Related
This is for real, folks. The first working custom recovery for Asus ZenPad 8.0 Z380M and a method to flash it under a locked bootloader. This took quite a bit of work to make, partly due to having to find a way to bypass the locked bootloader. And because of a kernel configuration issue that limited the size of the initial ramdisk, which took some serious effort to weed out. @lss1977 helped to port it to this device. And of course, credits to TeamWin for TWRP.
In addition to this thread, the current Z300M/Z301M TWRP thread and the the old Z300M recovery/rooting thread may be helpful. These models share the same hardware and software base, so most things that apply to one tablet also apply to the other.
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
REQUIREMENTS
Windows PC
SP Flash Tool version 5.1532 (only this version will bypass security checks)*
MediaTek VCOM drivers (available through Windows Update)
Z380M scatter file, attached
Recovery image, attached
Z380M preloader file (optional), available inside the stock firmware download
ZenPad Z380M tablet upgraded to Android N
* If you prefer to use a more recent SP Flash Tool, check out the special image file below.
This won't be a guide on how to use SP Flash Tool. There are plenty of good guides out there like this one on how to set up drivers, load scatter files, flash and make backups with SP Flash Tool. If you're not familiar with this software or how to flash MediaTek devices in general, please do your research before attempting this. I will just get straight to the specifics about the ZenPad 8.
FIRST TIME INSTALLATION
For a locked bootloader:
At this point you should have your tablet powered off, the drivers installed, all of your data backed up, and SP Flash Tool v5.1532's Download tab open and loaded with the tablet's scatter file. Open the download agent file DA_PL.bin, replacing the default MTK_AllInOne_DA.bin. (You can use the AllInOne DA if you want, but the procedure involves extra steps as described below.) Load the extracted TWRP recovery image (twrp-3.2.1-0-z380m.img) under the recovery partition line in the partition table. Click the Download button inside SPFT. Now just connect the USB cable to your tablet and your computer's USB port. It should start the download process automatically and disconnect when finished.
Alternative Method:
If you're using MTK_AllInOne_DA.bin, you have to hold the Volume Up key as you insert the cable, which puts the device into an emergency download mode. In addition, you will need to have the stock preloader*.bin file loaded inside SPFT for it to be able to communicate with your tablet. The preloader is available inside the official zip file download. Do not flash the preloader (untick the box) or any partitions other than recovery. You just need to have a valid bin file selected under the Preloader line.
For an unlocked bootloader:
If you have used the Asus unlock tool to unlock your device, you will still not be able to use fastboot flash to install a custom recovery. However, you can do a "hot boot" or a tethered boot of TWRP. This method doesn't require SP Flash Tool. Download the TWRP image, put your tablet in fastboot mode and connect to PC. Then run this command to boot TWRP dynamically:
fastboot boot twrp-3.2.1-0-z380m.img
Once inside TWRP, flash twrp-3.2.1-0-z380m.img to Recovery using Install -> Install Image. Then reboot to recovery. You may be able to use TWRP in the tethered boot mode, but that could result in glitches due to different parameters passed by the bootloader to the kernel. That's why flashing is recommended.
To update from your installed TWRP version to a new one, just transfer the image to your tablet, then boot to TWRP and install it by going to Install -> Install Image and flashing to Recovery.
START RECOVERY
With the tablet powered off, hold the Volume Up and Power keys together until you get to a menu where you can select "recovery". Use Vol. Up to scroll and Vol. Dn to select. If you have a locked bootloader, it will show a Yellow State message because the recovery is not signed by the OEM. Just press volume up to boot it. On the welcome screen of TWRP it will ask you about modifying the system partition, I suggest you go with Keep System Read-only. Doing otherwise will complicate your OTA updates.
WARNING: Never start the stock recovery from the bootloader menu on this device. It is programmed by the bootloader to instantly wipe your data without any warning. Also, be aware that Android installs the stock recovery at every normal boot cycle. So you either have to flash the TWRP every time you want to run it, or disable the automatic recovery installation in the stock firmware. Any kind of mod to the boot image will prevent the automatic recovery installation. If you're not sure which recovery you have installed, you can always do a 'adb reboot recovery' from Android without risk of data loss.
What works: Basically everything... access to major partitions, decrypted userdata partition, decrypted adoptable storage, external SD card, ADB, USB-OTG, touch interface, splash screen, installing stock Asus OTA/web FW updates
What doesn't work: (no known problems yet, but please report any)
Not guaranteed to work: factory reset
DOWNLOAD
(Updated February 3, 2018: updated kernel to firmware 5.3.18; up-to-date TWRP 3.2.1 sources)
SP Flash Tool v5.1532
Z380M Scatter file for all storage sizes (right click, Save link as...)
Recovery image
Signed image for Flash Tool only -- may be flashed with recent SP Flash Tool versions -- DO NOT INSTALL USING ANY OTHER METHOD -- tested with SPFT 5.1736.
Development and experimental files
Source code
P.S. The thanks button doesn't bite.
Nice one now lets get some custom roms done.
Has anyone installed this yet? I see the file has been downloaded a few times. Any feedback is welcome.
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
lss1977 said:
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
Click to expand...
Click to collapse
The way I did it was to edit the init.rc file inside the boot ramdisk and comment out the service block that calls install_recovery.sh. I used the MTK boot image unpack/repack tools. I don't know, it seems like changing anything on the system partition will break OTA updates because of dm-verity. Because that depends on verifying each block of the file system. I have never even mounted the system as R/W in recovery.
how to create scater file from text posted? I copied all text to MT8163_Android_scatter.txt file but when open with splash tools give error "scatter file is invalid"
please atach your working scatter file to other atachments
PxYra said:
how to create scater file from text posted? I copied all text to MT8163_Android_scatter.txt file but when open with splash tools give error "scatter file is invalid"
please atach your working scatter file to other atachments
Click to expand...
Click to collapse
OK, I added the scatter file as a download. It was a pain in the ass to copy & paste. (But it did work.)
Problem fixed downloaded new version of flashtool 5.16 and scatter working
Ok I installed TWRP on Z380M P00A, and wanna say to other
1. Use VCOM drivers only from splash tool official site
2. To install VCOM drivers first need enter chinese recovery tablet, then in windows device manager you see USB device, install manualy drivers (don forget in windows disable driver signature)
3. Use only SP-Flash-Tool-v5.1532.00, newer or older version not properly working with this phone
Ok, thanks for the update, PxYra. Just to let you know, there are signed versions of VCOM drivers floating around so you don't need to mess with signature enforcement. Here's one: https://www.androidfilehost.com/?fid=24591000424943663. They are also updated by Windows so you can just let Windows Update install them.
Thanks for your work.
Flashing procedure works only with "MTK_AllInOne_DA.bin" method for me. But this is OK!
(Updated May 6, 2017: added kernel from firmware 5.3.7, source code cleanup)
Click to expand...
Click to collapse
is it possible to get the older versions? I need Android 6.x, because of xposed-Framework for my Zenpad 8.0 Z380M.
Greets Freisei
Hey freisei...
I never posted a version for Android 6. There was just one based on the 5.3.6 kernel, practically the same as the current one. That's why I didn't keep it. I could try to build one for you if you want, but I can't test it of course. Does this recovery not boot at all on the old firmware?
It's strange that the DA_PL.bin method didn't work for you. What happened when you tried it? I suppose the old preloader doesn't allow it(?).
hello guys, you think lineage os official version for asus z380kl (p024) will work on our z380m ?
---------- Post added at 08:19 PM ---------- Previous post was at 08:05 PM ----------
Can anyone help me? after selecting recovery img, pressing download and inserting usb cable, nothing happens. Thanks in advance
lss1977 said:
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
Click to expand...
Click to collapse
hello friend, can you please upload that file? I deleted it, but now I need it to revert to official recovery, as my zenpad is bricked! It would be of great help! thanks!
Pires_7 said:
hello friend, can you please upload that file? I deleted it, but now I need it to revert to official recovery, as my zenpad is bricked! It would be of great help! thanks!
Click to expand...
Click to collapse
Your ZenPad didn't brick because you deleted install_recovery.sh. It's because you modified the system partition. Making any mods to system is bad advice unless you know exactly what you're doing. Even mounting it in r/w mode can break it. That's because dm-verity has tripped and is blocking access to changed blocks of the file system. So you have 3 options: mod your boot image fstab file to disable dm-verity, restore the original system image block-for-block (either from backup or official firmware converted to an img file), or wipe userdata (lss reported that to work).
Pires_7 said:
hello guys, you think lineage os official version for asus z380kl (p024) will work on our z380m ?
Click to expand...
Click to collapse
Nope, no chance.
diplomatic said:
Your ZenPad didn't brick because you deleted install_recovery.sh. It's because you modified the system partition. Making any mods to system is bad advice unless you know exactly what you're doing. Even mounting it in r/w mode can break it. That's because dm-verity has tripped and is blocking access to changed blocks of the file system. So you have 3 options: mod your boot image fstab file to disable dm-verity, restore the original system image block-for-block (either from backup or official firmware converted to an img file), or wipe userdata (lss reported that to work).
Nope, no chance.
Click to expand...
Click to collapse
Ok. I made some real s*it, I think I deleted every partition except recovery. Can you provide me a twrp backup or some way around my problem?
What do you mean you deleted every partition except recovery? There's like 28 partitions. You would have to work hard to accomplish that.
My first suggestion is to extract a system.img from the Asus stock firmware zip using this. Then flash it with SP Flash Tool. You might also try to install a full firmware zip from TWRP. Although I have no idea if that will work or if it's even safe to try.
diplomatic said:
What do you mean you deleted every partition except recovery? There's like 28 partitions. You would have to work hard to accomplish that.
My first suggestion is to extract a system.img from the Asus stock firmware zip using this. Then flash it with SP Flash Tool. You might also try to install a full firmware zip from TWRP. Although I have no idea if that will work or if it's even safe to try.
Click to expand...
Click to collapse
i was able to extract system.new.dat from stock firmware zip, but it extracts to a system folder. How do I flash this through sp flash tool?
OK, the system folder you don't need. It should have produced a system.img file also. That's the file you need to flash. Just select it for the system partition row in the partition list and then Download. Hopefully that will be enough.
EDIT: I just looked at the script, and realized the system.img.img file gets deleted in the process. So what you need to do is start the extraction, then after it makes system.img.img, when it starts extracting individual files, hit Ctrl+C. Then you'll end up with the img file.
Thank you very much! it works! YOU are the BEST!
please tell me, in your scatter file, address partition_name: frp (0x80a5000) is correct? if i format this partition (frp), google account remove?
I've bricked my phone and am in need of help!
What I've done:
Unlocked bootloader with a code from DC-Unlocker then using minimal ADB and Fastboot to unlock
Flashed TWRP 3.1.1
Installed Magisk
Took TWRP backup - but I was unable to backup Data (I believe this was due to encryption - recovery.log shwed errors initially on Bluedorid files)
Wiped data with TWPR to try and do a factory reset
This is where my problems started and now I cant restore boot with TWPR the error is "No such file or directory"
I can ADB pull my recovery.log which says
Read info file, restore size is 12444160
Restoring 6 partitions...
Total restore size is 4512MB
I:Restore filename is: /external_sd/TWRP/BACKUPS/L5NDU17B18000539/Stock V7 2018-06-23--16-58-45/boot.emmc.win
I:Restore file system is: 'emmc'.
I:Restore file system is: 'emmc'.
Restoring Boot...
Error opening: '' (No such file or directory)
I can restore OEM recovery and do a factory reset but it hangs at 99%
power down then it goes back to factory reset and goes to 100% - message "Reset Successful!"
but... then it gets stuck in a boot loop
I've tried downloading other stock ROMS and extracting and flashing images via fastboot (Boot, cust, product, recovery, system, vendor, version)
I've tried Huawei Multi-tool but I lack the Userdata.img disk image
I've tried flashing Resurrection Remix N v5.8.5 For Honor 9 (STF) but without success, although the TWRP install says it is successful and the vendor.img flashes fine.
I've tried extracting UPDATE.app files and putting them in sd_card/dload and then 3 button resetting
I've tried the above in external_sd/dload (not sure why - desperation)
I've tried looking on as many threads as I can find on XDA but with no luck
I can always get to fastboot, flash TWRP or OEM recovery, I can also run ADB commands via Putty (in command line they display strangely)
Any suggestions would be greatly appreciated! I am at a loss an quite frustrated, and have been working on this for maybe 15 hours now.:crying:
LOL, Stop your mumbo-jumbos.
I guess you'r still with nougat partitioning because you're using a pretty much outdated twrp.
So just dload flash a nougat 'service repair firmware' from the same region you're firmware is actually, and not any random update.app you 'made' yourself.
For this you'll need a micro-sdcard (or usb-otg) exfat formated :
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
Fixed!
Thank you, I think I even saw this thread but for some reason did not download the file, also the exfat formatting tip was excellent. I owe you a beer!
Can I always use this method to go back if I totally destroy things again even If I update to Oreo?
oslo83 said:
LOL, Stop your mumbo-jumbos.
I guess you'r still with nougat partitioning because you're using a pretty much outdated twrp.
So just dload flash a nougat 'service repair firmware' from the same region you're firmware is actually, and not any random update.app you 'made' yourself.
For this you'll need a micro-sdcard (or usb-otg) exfat formated :
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
Click to expand...
Click to collapse
Unfortunatly, there only nougat 'service repair firmware' available publicly as far I know.
So, for now, you can only use this when on nougat.
When on oreo, you should use HuRUpdater with oreo's Twrp.
Or if you're oreo device is really messed badly, a paying app called DC-Phoenix then HuRUpdater.
Hello everyone, after a long attempt at unlocking the bootloader i finally got it, i flashed TWRP and got a prompt for encryption password, and my password wasn't working and i also tried default_password,so i read that the format data option will decrypt the phone and people said wouldn't do anything to system, so i did it and now everytime i reboot it boots straight into recovery no matter what i try, it will also boot into fastboot, so i tried to find a stock ROM for TA-1056 but couldn't find it anywhere, the only the i found was a single ROM for the TA-1060, can anyone help? i really appreciate it!
Completely Bricked
Me too need a stock rom of ta 1056. Please help if you could manage to provide a helping hand... ?
I had the same issue like yours, looping in twrp. then i tried to flash it with a so called stock rom from net, guess what it went completely bricked and I donnow what to do. ??
mrabudi said:
Hello everyone, after a long attempt at unlocking the bootloader i finally got it, i flashed TWRP and got a prompt for encryption password, and my password wasn't working and i also tried default_password,so i read that the format data option will decrypt the phone and people said wouldn't do anything to system, so i did it and now everytime i reboot it boots straight into recovery no matter what i try, it will also boot into fastboot, so i tried to find a stock ROM for TA-1056 but couldn't find it anywhere, the only the i found was a single ROM for the TA-1060, can anyone help? i really appreciate it!
Click to expand...
Click to collapse
It's simple. just get the stock recovery (and boot, optional) to flash it with fastboot and go to recovery and wipe it and you'll be ok.
and also using the twrp on this phone is not a great idea to wipe.
if you wanna wipe. please use "fastboot -w" to wipe the phone while bootloader is unlocked. or stock recovery to wipe.
Because twrp built this recovery with only formatting option was ext4 to /data and /cache. So the phone cannot operate properly. Which leads to fake failed decryption notification.
Data partition must need to be formatted under f2fs format.
And finding rom for this phone is pretty easy. Just find some nb0 file for this phone (any variant of this phone should work) and extract it with "nb0 extractor" and then flash it with SP Flash tool by mediatek.
That's my way. I don't know how will you do. But normally you only need the nb0 file and then flash it with OST LA (Nokia's flash tool based off Intel's SUT L1/L3 tool).
My Nokia 1 TA-1047 stuck at Nokia logo screen
Hi guys, sorry I'm newbie so after a long time surfing for solutions, I couldn't solve my own problem. That's why I come here to ask for your supports
Firstly I unlocked bootloader, installed TWRP and rooted my device and enjoyed it. But after decided to wipe (factory reset) this phone with TWRP, and my problem began...
1. I got stuck in TWRP loop booting. After that I tried to fastboot system.bin, cache.bin and recovery.bin from Stock Firmware but it still hung at Nokia logo booting
2. I still kept trying with SP Flash Tool, Miracle Box but there was still no hope:
- SP Flashtool v5_1548 gave me error: BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)
- Miracle Box 2.27A told me there was an error (i don't remember the code) occured in the location (i can't remember its code either)...
Anyone can solve it please help!!!! I love this phone much and as of now still suffering day by day since I can't do anything with it.
Kindly appreciate any suggestion and solution.
Thank you all!
cuantonhonhoi said:
Hi guys, sorry I'm newbie so after a long time surfing for solutions, I couldn't solve my own problem. That's why I come here to ask for your supports
Firstly I unlocked bootloader, installed TWRP and rooted my device and enjoyed it. But after decided to wipe (factory reset) this phone with TWRP, and my problem began...
1. I got stuck in TWRP loop booting. After that I tried to fastboot system.bin, cache.bin and recovery.bin from Stock Firmware but it still hung at Nokia logo booting
2. I still kept trying with SP Flash Tool, Miracle Box but there was still no hope:
- SP Flashtool v5_1548 gave me error: BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)
- Miracle Box 2.27A told me there was an error (i don't remember the code) occured in the location (i can't remember its code either)...
Anyone can solve it please help!!!! I love this phone much and as of now still suffering day by day since I can't do anything with it.
Kindly appreciate any suggestion and solution.
Thank you all!
Click to expand...
Click to collapse
So here's the thing. The rom you downloaded from internet (about 2 GB) or ripped from your phone and reflashing from flash tool will NOT WORK.
The first reason you can't flash the ROM was:
You got into flashing mode but you didn't do the right way so it failed the downloading DA for the phone. Try again and it should work (Don't go into fastboot mode)
2nd reason:
Because of the unsupported chip that MiracleBox read. It said the phone was 6573 or something while the phone chip is 6737M.
So the app will create the wrong version of the scatter for the phone. Leads to the flash tool app downloading the wrong command and Download Agent for the phone makes the phone can't be flashed.
You need to get the official nb0 file for this phone (TA-1060 or 66 should also works, mine was TA-1047. Since it's a universal ROM so any variant of the phone can also work) and then extract the ROM. Then you can get the scatter text file from that nb0 ROM and then flash it over flash tool (version 5 recommended, version 3 more likely not work).
Remember to look at line with partition "metadata" and then edit "boundary_check" to false.
PLUS:
If you flash it with your own dumped EMMC rom or flash it by dd-ing the partition in recovery will kinda work. But when you update the ROM over OTA (Google Play services's System Update app)
It will most likely bootlooped the phone when it's trying to verify the 2nd partition of the same recovery or kernel flashed into the phone (https://source.android.com/security/verifiedboot) and flash the updated one.)
So flashing from official ROM is mandatory.
And you can flash it over Intel's (Nokia modified) flash tool app SUTL3 (aka. OST LA) but I can't get it to work so you just stick with Flash Tool v5 from MediaTek and you'll be good.
Link:
The nb0 ROM (Security update around May 2018): https://drive.google.com/file/d/1XqwEAGG7GMaspzV2J_yzCxnRei8zsOJd/view
(Source: https://romprovider.com/2018/09/nokia-1-ta-1060-firmware/)
nb0 extractor, requires java installed (If extracting hurts your hard disk performance aka. frozen or lag. Don't worry, It actually works, DON'T DO ANYTHING. It will notify you once it's done.): https://forum.xda-developers.com/general/general/tool-unpack-repack-nb0-rom-t3495091
Smart Phone Flash Tool from MediaTek: https://spflashtools.com/
My fixed scatter file that actually works from nb0 file: https://drive.google.com/open?id=1gRoADGHBm4vIAw3NeDyc_h9QWj12XUrC
And don't use twrp for wiping the phone. Use "fastboot -w" to wipe or use stock recovery.
TWRP will wipe the data parition but in ext4 format and make the phone bootlooped. We need f2fs in order to make the phone's /data partition run correctly. (Unless you know how to make the phone not having encryption flag when booting up every first time. Or modify TWRP to wipe the /data partition with make_f2fs and not make_ext4 app. Or using make_f2fs in recovery to directly wipe /data partition over terminal, the actual partition is in /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata.)
Or you just do this (I'm not tested it yet): Google "twrp f2fs format"
kutiz21 said:
So here's the thing. The rom you downloaded from internet (about 2 GB) or ripped from your phone and reflashing from flash tool will NOT WORK.
The first reason you can't flash the ROM was:
You got into flashing mode but you didn't do the right way so it failed the downloading DA for the phone. Try again and it should work (Don't go into fastboot mode)
2nd reason:
Because of the unsupported chip that MiracleBox read. It said the phone was 6573 or something while the phone chip is 6737M.
So the app will create the wrong version of the scatter for the phone. Leads to the flash tool app downloading the wrong command and Download Agent for the phone makes the phone can't be flashed.
You need to get the official nb0 file for this phone (TA-1060 or 66 should also works, mine was TA-1047) and then extract the ROM. Then you can get the scatter text file from that nb0 ROM and then flash it over flash tool (version 5 recommended, version 3 more likely not work).
Remember to hide/delete line with partition "metadata" in scatter.txt and you can flash it perfectly.
PLUS:
If you flash it with your own dumped EMMC rom or flash it by dd-ing the partition in recovery will kinda work. But when you update the ROM over OTA (Google Play services's System Update app)
It will most likely bootlooped the phone when it's trying to verify the 2nd partition of the same recovery or kernel flashed into the phone (https://source.android.com/security/verifiedboot) and flash the updated one.)
So flashing from official ROM is mandatory.
And you can flash it over Intel's (Nokia modified) flash tool app SUTL3 (aka. OST LA) but I can't get it to work so you just stick with Flash Tool v5 from MediaTek and you'll be good.
Link:
The nb0 ROM (Security update around May 2018): https://drive.google.com/file/d/1XqwEAGG7GMaspzV2J_yzCxnRei8zsOJd/view
(Source: https://romprovider.com/2018/09/nokia-1-ta-1060-firmware/)
nb0 extractor, requires java installed (If extracting hurts your hard disk performance aka. frozen or lag. Don't worry, It actually works, DON'T DO ANYTHING. It will notify you once it's done.): https://forum.xda-developers.com/general/general/tool-unpack-repack-nb0-rom-t3495091
Smart Phone Flash Tool from MediaTek: https://spflashtools.com/
My fixed scatter file that actually works from nb0 file: https://drive.google.com/open?id=1gRoADGHBm4vIAw3NeDyc_h9QWj12XUrC
And don't use twrp for wiping the phone. Use "fastboot -w" to wipe or use stock recovery.
TWRP will wipe the data parition but in ext4 format and make the phone bootlooped. We need f2fs in order to make the phone's /data partition run correctly. (Unless you know how to make the phone not having encryption flag when booting up every first time. Or modify TWRP to wipe the /data partition with make_f2fs and not make_ext4 app. Or using make_f2fs in recovery to directly wipe /data partition over terminal, the actual partition is in /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata.)
Or you just do this (I'm not tested it yet): Google "twrp f2fs format"
Click to expand...
Click to collapse
Thanks for your comment. I have recently bought that version (TA-1047) and I see that is more complicated to root it securely than I thought… Your comment gave me hope to try it. So, could you please say me if it is posible to do it without breaking it? I will read your comment when I have more time but I thank you for it!
As I see there is only stock rom for TA-1060 version, but as you say it is posible to recover it in case of breaking it, isn't it?
Thanks. :fingers-crossed:
pabloluih said:
Thanks for your comment. I have recently bought that version (TA-1047) and I see that is more complicated to root it securely than I thought… Your comment gave me hope to try it. So, could you please say me if it is posible to do it without breaking it? I will read your comment when I have more time but I thank you for it!
As I see there is only stock rom for TA-1060 version, but as you say it is posible to recover it in case of breaking it, isn't it?
Thanks. :fingers-crossed:
Click to expand...
Click to collapse
It's really easy to root the phone actually. Just unlock bootloader, install twrp recovery and install magisk.
And if you broke the phone's ROM. Just bring it to Nokia. Or flash it by yourself with the ROM I linked above by SP Flash Tool software.
Anyway the ROM is universal. So any variant of the phone can be flashed. (Proves that the elabel partition has 5 certifications images for 5 different models)
Just take sometime and read my words there.
kutiz21 said:
It's really easy to root the phone actually. Just unlock bootloader, install twrp recovery and install magisk.
And if you broke the phone's ROM. Just bring it to Nokia. Or flash it by yourself with the ROM I linked above by SP Flash Tool software.
Anyway the ROM is universal. So any variant of the phone can be flashed. (Proves that the elabel partition has 5 certifications images for 5 different models)
Just take sometime and read my words there.
Click to expand...
Click to collapse
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
pabloluih said:
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
Click to expand...
Click to collapse
That's weird. If you unlocked the bootloader and install adb/fastboot (must be latest version. Older version will not recognize the phone, download platform-tools from google dev site, don't download adb tools off XDA) + Nokia's driver from emulated CD drive (every time you plug the phone to computer with official rom, you'll see it) properly then it should be able to work.
You need to check the fastboot device driver Device Manager (devmgmt.msc) and see if the driver is properly installed yet.
You can only use "fastboot -w" once the bootloader is unlocked. And booting up the phone. It will say the bootloader is in Orange state.
You need to unlock oem bootloader from developer settings when the stock rom is there. And in fastboot too
Here is how you unlock it:
Enable oem unlock from dev settings
Then reboot to fastboot mode (bootloader)
Do this:
"fastboot oem key "serial number string converted to md5, not imei strings" "
"fastboot oem unlock"
Volume up
Then you are actually unlocked the bootloader.
Unlock from developer settings only will not do the trick. It only allows you to have ability unlock the bootloader in fastboot.
If you stuck on the Encryption unsuccessful screen. Try wipe it with stock recovery or "fastboot -w" (if you properly unlocked the bootloader)
If you think you can't do anything anymore. Just flash the ROM provided you above.
If you need the extracted ROM for SP flash tool and the fastboot driver. I can link it to you.
Most of all drivers will automatically install off Windows Update if you're on Windows 10 (except the fastboot driver, and yes. SP flash tool drivers are also provided by Windows 10 too)
Also. You should update the phone to the latest software update when flashing stock rom too. Because newer builds for this phone is compatible-friendly with GSI rom (Treble ROMs like AOSP Android 9 or 8.1 by phhusson)
Updates on Android 9/10
pabloluih said:
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
Click to expand...
Click to collapse
Nokia might harden the security of the device so you can't use Magisk on stock rom.
This Guide will explain how to root your LG G8X
* Disclaimer*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed. Please do some research
* YOU are choosing to make these modifications, and if
* you blame me in any way for what happens to your device, I will laugh at you.
*Wait, what? No. Me or somebody else will help you
Click to expand...
Click to collapse
Prerequisites
Unlock phone using the guide here: https://forum.xda-developers.com/t/guide-how-to-unlock-bootloader-of-lg-g8x.4198025/
Do not restore abl before rooting.
Magisk Patched Boot (20e, Indian Variant): https://drive.google.com/file/d/1s2A7RUOptXer5LGMtbGV9SKg0kcyL_NP/view?usp=drivesdk
1. Download the magisk patched boot.
2. Copy it over to your fastboot directory.
3. Connect phone in fastboot mode.
How to put phone to fastboot mode?
#1: Using Button Combination
Power off phone, press and hold Vol- and insert usb cable. You’ll be in fastboot
#2: Using ADB
Connect phone to pc, enable USB Debugging. Then run this command
Code:
adb reboot fastboot
4. Now run the command
Code:
fastboot flash boot Magisk_Patched.img
fastboot reboot
5. Download and install Magisk Manager
6. Done! Your phone is rooted now.
To restore Network follow the guide in bootloader unlock thread...
If you have a different G8X variant or are on a different firmware
1.Backup boot_a or boot_b using QFIL (Partition Manager>Read Data, Check Bootloader unlock guide for more details)
2. Install Magisk Manager
3. Click on Install and use Patch image function.
4. Save the boot image to pc.
5. Flash it in Fastboot using the command given above.
Known Issues: FP is broken
Thankyou
(copypasta'ed from the other thread)
For those who have yet to do this, I suggest extracting boot_a/b at the same time you flash the abl image. Prior to doing the fastboot oem unlock, use the Magisk patch file option (installed on the same or another device, and doesn't need to be rooted) to create a rooted boot image using adb push/pull. Once you fastboot oem unlock, go back into the bootloader and instead of fastboot flash boot, you can fastboot boot magisk_patched.img.
Once you go through the setup, you can open Magisk, which will download and install the full Manager app, at which point it will most likely reboot. You will need to fastboot boot again, and you should be able to do a normal Magisk install. I've usually found that as long as the patched boot is of the same Android version and within a few month of the patch level, it'll boot happily enough to do this. Afterwards, you can restore your abl image as you no longer need to use fastboot commands.
Doing this allows Magisk to save the stock boot image, and also allows you to get OTA updates by restoring the stock image right before any updates. Otherwise you will never be able to do an OTA update as it checks if the boot partition has been modified before installing the updates. Since there are no kdz for the US carrier models, your only other option would be to "brick" your device to try get your carrier's service center to restore a working firmware image.
-- Starfox
Sorry I posted in the wrong thread. I've deleted the contents, but wasn't able to delete the post itself
Guys, I am trying to follow this guide using the "different variant" method, but as soon as I boot after flashing boot.img the touchscreen doesn't work. Only way to get it back is to flash the boot_a.bin and boot_b.bin using QFIL. What am I doing wrong?
Is there a magisk patched image for the g850u20i
Is there an update for magisk patch image for 20b (unlocked US variant)?
Edit: Got my 20b version rooted.
Downloaded stock rom for the G850QM20b, extracted the kdz file to dz to .img grabbed the stock boot_a.img file and ran it in Magisk manager app, took the converted .boot.a.img (now renamed magisk_patched_clT14.img) and dropped it in platform tools, went fast boot, then flashed it. Came back up great, no issues and root access is clear.
Dapeplezchamp said:
Is there a magisk patched image for the g850u20i
Click to expand...
Click to collapse
I have 20j and I can't even get into edl or fastboot... Can you get into fastboot mode? I've tried adb and button combos
robnitro said:
I have 20j and I can't even get into edl or fastboot... Can you get into fastboot mode? I've tried adb and button combos
Click to expand...
Click to collapse
I cannot.I've tried everything I know to do.I'm so cautious with this phone because I got it at a steal off of eBay and would hate to brick it.
Dapeplezchamp said:
I cannot.I've tried everything I know to do.I'm so cautious with this phone because I got it at a steal off of eBay and would hate to brick it.
Click to expand...
Click to collapse
follow the video here, I got it to work
hold power and vol down , itll countdown to reboot.... as soon as it does that- while holding down and power tap the up button
How to Unlock Bootloader and Root Lg G8x + (also a Video Guide)
All fix avilable (no network solved) Watch it carefully do it step by step as showen in my video you will never brick if you follow my video :):love: All required files are in the video description This guide Tested on the firmware (20e...
forum.xda-developers.com
Is there a image for the g850UM20g?
edit:
I have a copy of boot_a but in the fastboot it tells me that I am using abl_b and I don't know if boot_a is compatible with abl_b and i can't enter EDL mode
So my understanding is you can have a rooted phone, but FP will be broken no matter what and possibly audio as well. You can fix this by reinstalling a Pie version from KDZ, fix it then reinstalling a 10, but then the root will be gone (but the bootloader remains unlocked). Is this correct?
zdanee said:
So my understanding is you can have a rooted phone, but FP will be broken no matter what and possibly audio as well. You can fix this by reinstalling a Pie version from KDZ, fix it then reinstalling a 10, but then the root will be gone (but the bootloader remains unlocked). Is this correct?
Click to expand...
Click to collapse
Yes, rooting will be gone and Bootloader remains unlocked forever. You have to root it again in A10
For anyone in the future: you can have both root and fingerprint. Follow the bootloader unlock guide up to the point where you have to backup your boot_a. After that you don't use the patched boot_a in the instructions, instead patch your own version with magisk and flash that instead with QFIL. I now have a working V20h EU version with root, fingerprint and working audio.
Anu one have LMG850UM 20f magisk patched boot file?
Country china
Lg g8x
Kanhei015 said:
Anu one have LMG850UM 20f magisk patched boot file?
Country china
Lg g8x
Click to expand...
Click to collapse
I do. But it's an EU version, so I'm not sure it would work for you. However it's easy to just make your own!
- Install Magisk manager on the phone. You don't need open bootloader or anything for that
- Get your own 20f boot_a using QFIL
- Copy your own boot_a to the phone or on an SD card
- In Magisk Manager you choose to install magisk, select patching an IMG file method and give it the boot_a
- If Magisk reports success you'll now have a magisk_patched_boot_a file. Copy that back to your PC
- Using QFIL flash that in place of your original boot_a
- Keep a copy of your original boot_a thou, you can go back with QFIL at any time.
- If you mess up royally and the phone doesn't boot, you can still recover it by re-flashing your firmware with LGUP 1.17. You'll have to download your region's firmware for that and you'll loose all data, so make a backup beforehand!
edit: double post
zdanee said:
For anyone in the future: you can have both root and fingerprint. Follow the bootloader unlock guide up to the point where you have to backup your boot_a. After that you don't use the patched boot_a in the instructions, instead patch your own version with magisk and flash that instead with QFIL. I now have a working V20h EU version with root, fingerprint and working audio.
Click to expand...
Click to collapse
Hi, thanks for sharing the steps!
I followed your steps but don't have audio/network/fingerprint after flashing patched boot. Later I also tried to restore abl_a/b, then I had audio and network working, but still no fingerprint.
In my case, fingerprint stopped working once bootloader is unlocked, before even flashing the patched boot.
Did you have working fingerprint right after you flash patched boot? Did you restored abl_a/b?
I also tried to follow another post to get fingerprint working, but I can only find 10b kdz of my variant (twn), I downgraded to android 9 using that kdz, still cannot get fingerprint to work.
james508959 said:
Hi, thanks for sharing the steps!
I followed your steps but don't have audio/network/fingerprint after flashing patched boot. Later I also tried to restore abl_a/b, then I had audio and network working, but still no fingerprint.
In my case, fingerprint stopped working once bootloader is unlocked, before even flashing the patched boot.
Did you have working fingerprint right after you flash patched boot? Did you restored abl_a/b?
I also tried to follow another post to get fingerprint working, but I can only find 10b kdz of my variant (twn), I downgraded to android 9 using that kdz, still cannot get fingerprint to work.
Click to expand...
Click to collapse
I also messed up at first, since there were no ready-made boot_a for my region/version I just grabbed the indian one for 20e, and yes, that did break my audio, fingerprint and possibly network, I didn't test that one. I did have a KDZ for my region thou, so I flashed back a 10c version, I needed the 1.17 tool, not the 1.14 or 1.16 one (those did not work) and in my case I needed the second version of 10c, not the first one to fix the fingerprint. After flashing 10c I did all the steps and regained my fingerprint reader without an issue (so no, it did not work right away, I did need to go into the service menu and do the test), audio and network also worked right away. After that I flashed my latest KDZ (20h) and using magisk manager made my own boot_a and was able to root with a working fingerprint. I did not dare to update Magisk after this thou, I only needed it to grant root for my adblocker, and it's hidden from everything else, I don't think I'll ever even start magisk again, so I don't really want to update it either.
Did you restore abl_a/b at all? I can only get into download mode (to use LGUP) after I restore abl_a/b.
Anyways, I think flashing using LGUP overrided the abl, and that's why audio and network worked right away (to my understanding)
My LGUP tool worked fine, but there only 10b for my TWN variant, I couldn't find 10c anywhere... (only 10b, 20a, 20b available)
I never flashed other's patched boot, I used QFIL to get my boot_a.bin and patched it using Magisk on another phone. Then I used fastboot to flash boot. (I did this right after unlocked BL, all before I restored abl).
Did you also use QFIL to get boot_a or did you use KDZ extractor? I'm having problem with my KDZ extractor tool, encoding issue or sth.
My variant is G850EMW, should I try the indian 10c kdz (which is also G850EMW)? Would that work? Not sure what risk cross region flashing poses, or even if LGUP would let me flash it at all.
james508959 said:
Did you restore abl_a/b at all? I can only get into download mode (to use LGUP) after I restore abl_a/b.
Anyways, I think flashing using LGUP overrided the abl, and that's why audio and network worked right away (to my understanding)
My LGUP tool worked fine, but there only 10b for my TWN variant, I couldn't find 10c anywhere... (only 10b, 20a, 20b available)
I never flashed other's patched boot, I used QFIL to get my boot_a.bin and patched it using Magisk on another phone. Then I used fastboot to flash boot. (I did this right after unlocked BL, all before I restored abl).
Did you also use QFIL to get boot_a or did you use KDZ extractor? I'm having problem with my KDZ extractor tool, encoding issue or sth.
My variant is G850EMW, should I try the indian 10c kdz (which is also G850EMW)? Would that work? Not sure what risk cross region flashing poses, or even if LGUP would let me flash it at all.
Click to expand...
Click to collapse
No, I did not restore abl_a/b, and after KDZ the bootloder remained open, so there is no need to, the phone still reports an open bootloader at boot. If it _does_ override it thou it seems it's not neccessary to have, as I could root the phone and could keep the open bootloader anyways.
I used QFIL to get my own boot_a, and used it again to flash it back too.
My EU (Hungarian T-mobile) version is also G850EMW. My understanding is that if LGUP lets you flash a KDZ it's probably gonna work, but in the worst case scenario as long as you have a known good KDZ for your model you can always come back to that, so I guess you can experiment?
I've also only found a 20b version of KDZ for TWN, but it's release date is similar to 20h in the EU, so maybe these numbers doesn't mean they are the same KDZ, only that 20x meant it's Android 10 and the letter is the revision. Based on this it's possibe you don't need a 10c to restore your fingerprint, just try the earliest 10x KDZ you can get your hands on (for me the 10c was the earliest one). Alternatively you can try the 10c I used for mine, it's EU Hungarian, but the default language is still English and you'll re-flash it anyways: https://lg-firmwares.com/downloads-file/21667/G850EMW10c_00_OPEN_EU_DS_OP_1122
Figured it out.
Dear all,
I am trying to replace the stock OS on my Lenovo tablet with some more open alternative, like LineageOS. I got as far as installing a modified version of TWRP on it and got root access.
I also found some unofficial gis LOS images but I couldn't install them via TWRP as the SYSTEM partition does not show up when I have to select which partition I want to install the image to. Mounting (ticking) the system partition in TWRP makes no difference. These are the partitions listed:
Boot
Vendor Image
Recovery
Modem (Image)
Persist (Image)
Splash
So I went ahead, and installed it from fastboot like this:
fastboot flash system image.img
Click to expand...
Click to collapse
The command succeeded, but when restarting, the device gets back to fastboot. I can boot into TWRP as well, but no matter what image I try to install, I get the same result.
I wonder what I am doing wrong... A few years back I have converted several phones to LOS and others with no problem. But I have no experience with gis. Maybe that's the problem.
Could someone more experienced help me? maybe I am trying the wrong gis images.
Thanks for any pointers in advance!