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?
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.
Alright, here goes.
So one day I was interested in flashing a new custom ROM (Preferably LineageOS) to my Huawei Mate 10 Lite. Long story short, it's now soft bricked. Only TWRP is working.
But, that's not enough information. Here's the fully story.
After realizing I could not get the Bootloader unlock code using the official method, I've tried DCUnlocker. I paid, and got my code.
I've installed HiSuite, 274829 drivers and finally unlocked the Bootloader. Now, the phone said "This device is unlocked and can't be trusted", but it booted fine. YES!
After that, I downloaded LineageOS 15.1 and flashed it. Before flashing it, I formatted everything, wiped cashe, davlick ect... And.. made my biggest mistake.
Not making a nandroid backup (dammit).
Don't ask me why, I thought it would go well (ugh).
Anyways, I flashed it, error 7. Alright, removed the assert lines. Flashed it again, and it worked, but right at the end, another error? It was error 7, again, but a little different.
This time, it said "failed to mount /dev/block/bootdevice/by-name/vendor at /vendor: device or resource busy"
Okay, now I'm starting to get worried. Like, REALLY WORRIED.
It also said it failed to execute a line in the updater script, one of the last lines. But I would not delete it, just in case.
When I tried to boot, nothing. Went back to Google.
At this point, I learned that any Treble ROM will NOT work with Android version of 7.1. shhhiiii
I was on EMUI 5.1 aka 7.0, and this was worrying. At this point, I tried to return to EMUI 5.1, but since there was no backup, well...... To Google we go!
I did not find any stock room that running EMUI 5.1, but only found EMUI 8.0. I did find a stock room on 7.1, but I'm not paying 15 dollars for it. Not about that life.
I tried the dload method, but apparently my sdcard is on FAT32, and because of that I cannot upload the UPDATE.APP to it.
I've also tried eRecovery, but to no avail. "Failed to get package".
So now I'm stuck on a couple of options, and I need help from you, the XDA community.
1) Remove the line that's causing the issue but at the cost of it maybe not working
2) Somehow format the sdcard and somehow upload the update.app to it
3) Somehow update Android's system to Project Treble, although not sure it's possible since there is no OS.
4) ?????????????????
Please, help me. I'm in hell right now.
Try grabbing the required update files from the teammt site, using the huawei update extractor to grab the partitions you need and then manually flashing with fastboot.
I have the mate 10 pro and usually after getting into a bootloop I flash the kernel, system & recovery_ramdisk then everything starts working as it should
No don't do that, if you are on 7.1 do not flash files from an 8.0 rom because there is more to an oem update then the kernel and sys partition.
If you are in twrp you can flash noCheck recovery. Then you can take your update.zip, hw.zip and data.zip (the 3 files you download from firmware finder, newer firmware might only have 2 files do to an updated data structure by huawei) and send commands to install them in the nocheck recovery. This way every partition will be updated to 8.0 base, this is like the erecovery method but better.
I meant for the original rom, not the 8.0 one, probably should have clarified that in my post
Raptorta said:
No don't do that, if you are on 7.1 do not flash files from an 8.0 rom because there is more to an oem update then the kernel and sys partition.
If you are in twrp you can flash noCheck recovery. Then you can take your update.zip, hw.zip and data.zip (the 3 files you download from firmware finder, newer firmware might only have 2 files do to an updated data structure by huawei) and send commands to install them in the nocheck recovery. This way every partition will be updated to 8.0 base, this is like the erecovery method but better.
Click to expand...
Click to collapse
Well, okay.
I have the 7.0 structure of EMUI 5.1, and right now all I have is the update.zip for the 8.0 Oreo filmware of my EXACT model. I don't have hw or data.
So, I have a couple of questions...
From what I understand, you are trying to solve the problem using method 3, making it Oreo based. If so, how do I go about doing that?
Okay, sure, I can flash noCheck, but finding update, hw, and data for my model, let alone the 7.0 version is pretty hard.
Also, when I find it, what exactly do I have to do???
"Send commands to flash the files" whaaaaat??
All I have rn is adb, fastboot, and on my phone I have TWRP, eRecovery (won't work) and the update.app thingy
Maybe I could format the sdcard to ExFAT, move the 8.0 update.app and install it using the dload method?
Okay so whats your exact model number and your region number (Cxxx). Maybe there is something on Firmware finder.
As for the commands:
You can push files to internal memory with ADB, For example if we have all 3 files and no check recovery we could push them with commands (Taken from the EMUI downgrade script cuz im lazy right now, Thanks to @ante0, @Atarii, @dkionline, @frantm, @Last****ingdroid, @mankindtw, @Pretoriano80, @shimp208, @zanooda123)
adb push ZIPS-HERE/update.zip /data/update/HWOTA/update.zip
adb push ZIPS-HERE/update_all_hw.zip /data/update/HWOTA/update_all_hw.zip
adb push ZIPS-HERE/update_data_public.zip /data/update/HWOTA/update_data_public.zip
adb push images/nocheck.img /data/update/nocheck.img
After that we can send shell commands to queue updates into buffer for the recovery so when the device reboots into recovery mode these commands are executed (this is used for official OTA's as well)
adb shell "echo --update_package=/data/update/HWOTA/update.zip > /cache/recovery/command"
adb shell "echo --update_package=/data/update/HWOTA/update_all_hw.zip >> /cache/recovery/command"
adb shell "echo --update_package=/data/update/HWOTA/update_data_public.zip >> /cache/recovery/command"
After this we push our nocheck recovery to the recovery partition overwriting TWRP
adb shell dd if=/data/update/nocheck.img of=/dev/block/bootdevice/by-name/recovery_ramdisk
After this all we have to do is reboot the device to recovery and the buffered commands run, installing the original firmware through the original recovery resulting in a perfect installation of the firmware with partition table overwrites if necessary.
This most might have become a little complicated, but I think this is the best way to update your system.
Raptorta said:
Okay so whats your exact model number and your region number (Cxxx). Maybe there is something on Firmware finder.
As for the commands:
You can push files to internal memory with ADB, For example if we have all 3 files and no check recovery we could push them with commands (Taken from the EMUI downgrade script cuz im lazy right now, Thanks to @ante0, @Atarii, @dkionline, @frantm, @Last****ingdroid, @mankindtw, @Pretoriano80, @shimp208, @zanooda123)
adb push ZIPS-HERE/update.zip /data/update/HWOTA/update.zip
adb push ZIPS-HERE/update_all_hw.zip /data/update/HWOTA/update_all_hw.zip
adb push ZIPS-HERE/update_data_public.zip /data/update/HWOTA/update_data_public.zip
adb push images/nocheck.img /data/update/nocheck.img
After that we can send shell commands to queue updates into buffer for the recovery so when the device reboots into recovery mode these commands are executed (this is used for official OTA's as well)
adb shell "echo --update_package=/data/update/HWOTA/update.zip > /cache/recovery/command"
adb shell "echo --update_package=/data/update/HWOTA/update_all_hw.zip >> /cache/recovery/command"
adb shell "echo --update_package=/data/update/HWOTA/update_data_public.zip >> /cache/recovery/command"
After this we push our nocheck recovery to the recovery partition overwriting TWRP
adb shell dd if=/data/update/nocheck.img of=/dev/block/bootdevice/by-name/recovery_ramdisk
After this all we have to do is reboot the device to recovery and the buffered commands run, installing the original firmware through the original recovery resulting in a perfect installation of the firmware with partition table overwrites if necessary.
This most might have become a little complicated, but I think this is the best way to update your system.
Click to expand...
Click to collapse
Okay, so here goes again.
My exact build number is RNE-L21C432B137, and my region number is +972 (country).
Anyways, by "ZIPS-HERE" what do you mean? This post isn't very well explained. Sure, you did include some major details, but I can't really understand it.
Also, I'm still wondering, is the dload method still a viable option? Thank you!
Okay so you have an rne-l21c432
https://pro-teammt.ru/firmware-database/?firmware_model=Rne-l21c432&firmware_page=0
From here you can download firmwares for your device.
If you want to try the dload method you can but you should look for the exact same firmware (b137) to be safe, format your sdcard and follow the instructions for that method.
But for that you need the stock recovery which you can get by extracting it from the firmware. After that you can flash it the same way you flashed twrp.
Raptorta said:
Okay so you have an rne-l21c432
https://pro-teammt.ru/firmware-database/?firmware_model=Rne-l21c432&firmware_page=0
From here you can download firmwares for your device.
If you want to try the dload method you can but you should look for the exact same firmware (b137) to be safe, format your sdcard and follow the instructions for that method.
But for that you need the stock recovery which you can get by extracting it from the firmware. After that you can flash it the same way you flashed twrp.
Click to expand...
Click to collapse
Okay, could you tell me step by step, what to do?
I'm unable to format sd card. I need a reader.
Right this second, I'm on TWRP. What do I do?
In the site you've linked, I can find 6 versions of the software.
These are the names of it:
RNE-L21C432B137CUSTC432D001 (2.96GB, FullOTA-MF, v: 161084)
RNE-L21C432B137CUSTC432D001 (2.96GB, FullOTA-MF, v: 160963)
RNE-L21C432B137 (2.96GB, FullOTA-MF, v: 134022)
RNE-L21C432B137 (465.45MB, OTA-MF, v: 134021)
RNE-L21C432B137 (465.45MB, OTA-MF, v: 133902)
RNE-L21C432B137 (2.96GB, FullOTA-MF, v: 133901)
I have no idea what "v" stands for.
So, what do I download, and what do I do? Please help.
Also, could you use "English"? Meaning, explain it step by step.
Like, give examples, ect...
EXAMPLE:
Flash the custom rom using TWRP
Example:
Tap LineageOS from the selection menu in "Install" in TWRP
Swipe to install
Thank you so much!
UPDATE: I cannot download anything.
This XML file does not appear to have any style information associated with it. The document tree is shown below.
Literally, every single link I go to, nothing. This site is useless.
Do you have Discord by any chance? Talking via a forum is really inefficient. If so, send me in PM's your discord.
Hi everyone,
I ran out of ideas with my problem, and could really use some help / advice with this.
Trying to updgrade my STF-L09C432 from B368 to B385 using HuRu updater, something went wrong and now it bootloops after the blue Honor logo.
Fastboot, Huawei eRecovery and TWRP are still working and accessible, my device is bootloader unlocked and says FPR unlock in fastboot mode.
So here's the detailed steps and procedure which I followed:
0) TWRP Backup of System + Data
1) Load three update files (FullOTA) via FF: update.zip (update.zip), update_data_full_public.zip (update_data_full_public.zip), update_full_STF-L09_hw_eu.zip (STF-L09_hw_eu/update_full_STF-L09_hw_eu.zip)
2) Create folder on SD-card with above files and TWRP v0.3 as recovery.img and the HuRu 0.4 zip file. Additionally I've left the HuRu 0.3 in the same folder renamed as HuRUpdater_0.3_old.zip
3) Installed the HuRu 0.4 from TWRP with zip verification disabled (tried before with enabled, but it failed -> call me stupid but I've double checked the checksum with a new download, so I took the risk).
4) the installation log showed warnings about some missing .zip files, but I ignored those as well, as I've never heard of them and didn't have them from FF.
5) rebooted the system and caught the first bootloop
Now I tried myself to fix it the following way, but unsuccessful until now:
1) Flashed TWRP into recovery_ramdisk because I didn't know the right procedure to boot into it
2) Flashed the new B385 versions of KERNEL.img, RAMDISK.img and RECOVERY_RAMDIS.img which I extracted from the UPDATE.APP -> still bootloop
3) Flashed TWRP into recovery_ramdisk again because I still didn't know the right procedure to boot into it
4) Flashed the old B368 versions of KERNEL.img, RAMDISK.img which I extracted from the UPDATE.APP, but not the RECOVERY_RAMDIS.img this time -> still bootloop
5) Then I've managed to boot into TWRP finally, and tried to restore my previous backup as a last resort, but that still didn't resolve my bootloop
Anybody has any idea what I could still try? Maybe I'm missing something obvious, or I'm still to new to this to see what is wrong.
If possible I'd like to keep my data intact, but I could probably extract most of it out of the backup, if nothing else helps.
Thank you very much!
Best regards,
Chris
Nobody has an idea?
Maybe the Seniors on the Honor9, @OldDroid or @zxz0O0?
After I've tried to restore the previous TWRP backup, now also TWRP won't boot anymore, therefore I'm stuck with fastboot or the Huawei stock recoveries...
Schrubbi said:
Nobody has an idea?
Maybe the Seniors on the Honor9, @OldDroid or @zxz0O0?
After I've tried to restore the previous TWRP backup, now also TWRP won't boot anymore, therefore I'm stuck with fastboot or the Huawei stock recoveries...
Click to expand...
Click to collapse
well, aslong as its still unlocked (frp & bl) i'm able to help.
Do you have telegram? if so, send me your username through pm.
Regards
I managed to get into TWRP again when I've installed the latest kernel and recovery images. After that I've realized that I still had Magisk installed and Active.
Uninstalling that solved my bootloop for now.
Unfortunately my backup restore just returned me to the previous version B368 which I already had installed... so lets see what happens if I apply the update again
---------------------
Edit:
Update applied, without magisk installed, still bootloop... At least the way back was quicker this time
Any hints what's going wrong are appreciated!
Hello I've downloaded latest stock firmware/ROM from: https://dlcdnets.asus.com/pub/ASUS/...2202-ASUS-32.2050.2050.34-1.1.1-2210-user.zip
But unable to find any guide or tool on how to install it? From searching I understand there's supposed to be a flashfile_AFT.cmd, but can't find it in the zip. I've unlocked bootloader already. thanks
Flashing a working device? Just copy to root dir and reboot.
The instructions said to choose the zip from recovery, but stock recovery doesn't have an option to "install from zip". I only managed to flash the stock firmware after installing twrp.
Hermann2306 said:
Flashing a working device? Just copy to root dir and reboot.
Click to expand...
Click to collapse
That's also what instructions said, but I never got the notification you are supposed to get. Also, we are more likely to want to flash the stock firmware on a non-working device and I really can't find how we are supposed to do it with stock firmware.
For the updatenotification you maybe have to activate something like "apply updates on reboots / automatic updates" in developer options.
If the device only boots to fastboot you need a raw firmware file with the flashall.bat (I think it was WW-AI2202-32.2004.2004.84-REL-2206-M2.13.33.11-ASUS_1.1.1-user-20220722.zip for example). You can find it on romdevelopers.
All I had to do was take the firmware zip, plop it into my 'home' directory (i.e. not the actual root directory!), and I got the notification that an update was available via that zip. Standard installation after that.
I had and continue to have root access through Magisk, though I did have to apply that 'after update' magisk function before rebooting to complete the update. Rebooting without doing that loses your root access.
Yes, i mean that folder. Its "root" If you use the standard filemanager.
ok this will update the phone but if a phone was bricked, does any stock ROM file exist that can be flashed via fastboot?
Or is there a script which can be used to flash the contents inside payload.bin through fastboot? there are lots of files if payload.bin is extracted, not sure if everything it meant to be flashed?