Related
I just make my mobile unlock(KIW-TL00C01), I have tried
1. extract the image of UPDATE.app from B228 and fastboot flash (failure)
https://forum.xda-developers.com/honor-7/general/guide-beginners-how-to-root-update-fix-t3255452
2. using e-recovery(internal recovery), put firmware zip file(B228) in dload directory in SDcard, inform failed at 5%,
if you put that file in root directory of SDcard, it would stop at 5%.
3. install the 3rd part firmware from TWRP recovery(installed, but reboot would make the touch screen support in all the place, and boot loops)
I have tried install a different firmware through the adb when the touch screen is broken.
I use the following command, I didn't find a one could work.
Code:
recovery --update_package=/external_sd/firmware.zip
The one thing I could do to is put the UPDATE.app of B430 into dload, and retry the method 2 or my mobile is complete brick.
I wonder does the Huawei update the signature or firmware of TrustZone?
I don't know anything I could do to make it work.
if you want to downgrade, you first have to dload the rollback package, then the actual firmware
the rollback package
Click to expand...
Click to collapse
Oh I don't know that before, but where could I get that?
hizukiayaka said:
I just make my mobile unlock, I have tried
1. extract the image of UPDATE.app from B228 and fastboot flash (failure)
https://forum.xda-developers.com/honor-7/general/guide-beginners-how-to-root-update-fix-t3255452
2. using e-recovery(internal recovery), put firmware zip file(B228) in dload directory in SDcard, inform failed at 5%,
if you put that file in root directory of SDcard, it would stop at 5%.
3. install the 3rd part firmware from TWRP recovery(installed, but reboot would make the touch screen support in all the place, and boot loops)
I have tried install a different firmware through the adb when the touch screen is broken.
I use the following command, I didn't find a one could work.
Code:
recovery --update_package=/external_sd/firmware.zip
The one thing I could do to is put the UPDATE.app of B430 into dload, and retry the method 2 or my mobile is complete brick.
I wonder does the Huawei update the signature or firmware of TrustZone?
I don't know anything I could do to make it work.
Click to expand...
Click to collapse
where are you getting your files ? what is the Full version of your phone KIW-TL00C00 or KIW-TL00C01 or KIW-TL00HC00 ?
you must use the exact version for your phone.
the only useful info on the Honor 7 link you posted is how to flash from dload
nowhere did you say you put update.app in dload folder on ext_sdcard and flash with power + volume up and volume down
First determine the correct file for your phone and then flash it correctly
clsA said:
where are you getting your files ? what is the Full version of your phone KIW-TL00C00 or KIW-TL00C01 or KIW-TL00HC00 ?
you must use the exact version for your phone.
the only useful info on the Honor 7 link you posted is how to flash from dload
nowhere did you say you put update.app in dload folder on ext_sdcard and flash with power + volume up and volume down
First determine the correct file for your phone and then flash it correctly
Click to expand...
Click to collapse
I tried to use the match file, but failed in rollback, it would always inform me that system update failed.
hizukiayaka said:
I tried to use the match file, but failed in rollback, it would always inform me that system update failed.
Click to expand...
Click to collapse
Follow this : https://forum.xda-developers.com/honor-5x/how-to/guide-entering-fastboot-using-key-t3400869
After you entered fastboot, flash twrp, then restart to recovery and copy stock firmware to sdcard.
Even if it fails, you can hold VOL+ button during startup to enter eRecovery, where you can revert to stock using nothing but wireless LAN
P/S : I'm also stuck at bootloops trying to install lineage and mokee, please post a guide if you have done it successfully
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?
Hi everyone,
I have an 10.8 inch wifi only tablet imported from China, non-pro, model CMR-W09C00 which was running firmware B123.
I was playing around trying to convert it to a global firmware and tried to flash it with the same firmware 123 but for CMR-W09C432 using Huawei Firmware Finder.
Turns out this was a pretty bad idea
Now the tablet is not booting and I can't figure out how to recover. Here's what I tried:
1. eRecovery is not working, it downloads the firmware completely and tries to install but fails. It did work fully once before I tried to flash the wrong firmware.
2. Wiping cache and data partition does nothing
3. I have access to fastboot and can unlock/lock the bootloader at will.
4. I have the full-OTA zip file for the original firmware CMR-W09C00B123 and have extracted all the img files contained in update.app
5. I'm trying / hoping to flash images to recover (with bootloader unlocked) but I'm a bit confused at this step.
All the instructions I found in my research mention mostly flashing just boot.img, system.img and recovery.img but I'm missing some of those files from the update.app or I guess they could be named differently. I don't have a boot.img, just a fastboot.img which I'm sure is not the same. I also don't have a recovery.img, just recovery_ramdis, recovery_vbmeta, recovery_vendor, erecovery_ramdis, erecovery_vendo, erecovery_vbmet and erecovery_kerne.
I was able to flash system.img successfully but that didn't help.
Also tried to use the unbrick feature from Huawei Multi-Tool but here again I seem to be missing image files. Multi-Tool says it needs system.img, ramdisk.img, cust.img, ramdisk_recovery.img and userdata.img.
Of those, I think I'm missing cust.img for sure, ramdisk_recovery I might have but it's named differently (recovery_ramdis) and userdata.img I don't think I really need.
I'm attaching a txt file with a list of all the img files I do have in case it can be useful or rings a bell for someone.
Oh yeah, I also tried flashboot update update.zip but it's only giving me this warning:
archive does not contain 'android-info.txt'
error: update package 'update.zip' has no android-info.txt
So...does anyone have any advice or suggestions? Is there a better method to recover that I missed?
Any help is appreciated!
Flash the ramdisk.img to ramdisk and report back please. I have an M3 that is in the same condition as yours, but I am on an extended deployment and won't be able to test this for at least another month :/
fargonaz said:
Flash the ramdisk.img to ramdisk and report back please. I have an M3 that is in the same condition as yours, but I am on an extended deployment and won't be able to test this for at least another month :/
Click to expand...
Click to collapse
Thanks for taking the time to the reply mate, sorry to hear about your M3.
I tried fastboot flash ramdisk ramdisk.img and it said flashed successfully but the device is still not booting. Nothing else seems to have changed either.
Let me know if I misunderstood what you wanted to try or if you have any other ideas.
Cheers
etheberge said:
Hi everyone,
I have an 10.8 inch wifi only tablet imported from China, non-pro, model CMR-W09C00 which was running firmware B123.
I was playing around trying to convert it to a global firmware and tried to flash it with the same firmware 123 but for CMR-W09C432 using Huawei Firmware Finder.
Turns out this was a pretty bad idea
Now the tablet is not booting and I can't figure out how to recover. Here's what I tried:
1. eRecovery is not working, it downloads the firmware completely and tries to install but fails. It did work fully once before I tried to flash the wrong firmware.
2. Wiping cache and data partition does nothing
3. I have access to fastboot and can unlock/lock the bootloader at will.
4. I have the full-OTA zip file for the original firmware CMR-W09C00B123 and have extracted all the img files contained in update.app
5. I'm trying / hoping to flash images to recover (with bootloader unlocked) but I'm a bit confused at this step.
All the instructions I found in my research mention mostly flashing just boot.img, system.img and recovery.img but I'm missing some of those files from the update.app or I guess they could be named differently. I don't have a boot.img, just a fastboot.img which I'm sure is not the same. I also don't have a recovery.img, just recovery_ramdis, recovery_vbmeta, recovery_vendor, erecovery_ramdis, erecovery_vendo, erecovery_vbmet and erecovery_kerne.
I was able to flash system.img successfully but that didn't help.
Also tried to use the unbrick feature from Huawei Multi-Tool but here again I seem to be missing image files. Multi-Tool says it needs system.img, ramdisk.img, cust.img, ramdisk_recovery.img and userdata.img.
Of those, I think I'm missing cust.img for sure, ramdisk_recovery I might have but it's named differently (recovery_ramdis) and userdata.img I don't think I really need.
I'm attaching a txt file with a list of all the img files I do have in case it can be useful or rings a bell for someone.
Oh yeah, I also tried flashboot update update.zip but it's only giving me this warning:
archive does not contain 'android-info.txt'
error: update package 'update.zip' has no android-info.txt
So...does anyone have any advice or suggestions? Is there a better method to recover that I missed?
Any help is appreciated!
Click to expand...
Click to collapse
I think I am in a similar spot. I went from a custom ROM back to stock, but now all attempts at installing full OTAs fail. Did you ever figure this out how to fix it?
Thanks
Hi. I recently bought couple of tv boxes and decided to modify their firmware for my needs (root in progress).
All devices are Amlogic S905X based, so i found multiple TWRP builds for s905x and tried to boot from sdcard.
Obviously i failed: none of them were loaded and device just stuck at logo screen. So i decided to build my own version of TWRP based on stock recovery. As far as i'm writing this message obviously i failed again.
I'm unable to unpack stock ramdisk and kernel, looks like they were encrypted and are decrypted by second stage bootloader during boot. Though i'm experienced in cracking but i never had a deal with bootloader disassembly and analysis, so i need help unpacking this at least tell me how to disassemble bootloader correctly.
I've attached recovery and boot images.
boot - https: //yadi.sk/d/zpwSfpHhAx4QGQ
recovery = https: //yadi.sk/d/67jx76xOYUU0Mw
I can add your Moto e6 on here if you send me a copy of your recovery.img so o can port it it only takes me a few minutes now to port to new device I will be uploading more this weekend if you want one for your device send me your recovery.img and I will port it to you real fast
Thanks to A-Team Digital for all there help
This certainly works with usb mouse plugged into usb port. No touch otherwise.
I need 2 files from your device to get touch working
Let me know which ones and I will send them to you. Thanks.
Pick the 2 you need from these files
What carrier do you have what is the model number o have all the files I just need to know the model number and carrier please
I'm repacking a universal one with all the files for all models and carriers right now give me a little bit and I should have it uploaded
I have it built but can't upload it here too big of files in total it is just over 3gb but it adds something's to the system so you don't have to boot into recovery to get root and you have rw access in twrp and Android if you have a telegram let me know and I can send you the files on there if you like
If not I'm uploading them to google drive right now
I got the download size down to 1.6gb zipped and 3.3gb unziped that have to be flashed please read readme.txt
Here is the link to google drive it has 2 zip files download both and it has all the files you need to flash to device
Moto e6 - Google Drive
drive.google.com
Sorry for delay in getting back to you. First, I downloaded the zip files and the readme. Thank you. Second I have the latest version of the T-Mobile Rom, which, I believe, is very similar, if not identical to, the MetroPCS version you have. I will check out the readme file and let you know how it goes. Thanks again.
Okay. I reviewed your zip files and they are the ones from AIO. I looked at all of these files before and decided not to install them since it prohibited upgrading the firmware in the future. If these are required to have a touch-friendly TWRP recovery, then I will pass. I like my Moto E6 security updates too much. By the way, I admire the A-Team work.
They are not the same as there's I added the ability to update you just have to use magisk and go to update in settings and keep magisk after update you can get security updates for a while but moto is stoping updates on that phone next month
I just added a few lines to allow security updates because I started with there base and needed updates for my work phone
I change a few files in the recovery file but twrp will have touch but can not mount as rw or anything no back ups or nothing unless you go my route right now at least you get security updates
Thanks for the explanation. I think I will give it a try.
I tried it and I am now running my T-Mobile version fully rooted with a fully operating TWRP touch working recovery!
The system.img would not install, and that was a very good thing. It was not needed. Everything works. I have done full backups, including non-encrypted data, using the Batik-TWRP. I did update to Magisk 23 and that worked just fine as well. Thank you so much for finally giving us a way to fully root and backup this phone!
You are welcome sir Al software updates will work just remember to go in magisk manger and keep magisk after update
I have two moto e6:
1. XT2005-5 RETCA (bootloader unlocked & rooted with Magisk, but via recovery only)
2. XT2005-1PP Verizon version (Brand new state. Not even activated. But fastboot is available).
Both are with the newest stock rom for their channel (rescued by LMSA).
I followed the readme, but fastboot could not flash any image.
I got error like this:
Sending 'boot' (32768 KB) OKAY [ 1.279s]
Writing 'boot' (bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Can you make images if I upload boot, dbt, recovery?
Or can you show instruction to patch/modify images?
Also, I have tried to flash the stock ROM from RECTA onto Verizon version but failed (went into fastboot loop).
Then I tried to falsh back stock Verizon ROM, and failed, as well.
Yet, LMSA could flash the stock Verizon ROM.
Maybe we can copy patched images into LMSA Download folder (C:\ProgramData\LMSA\Download\RomFiles), over the stock ROM, and let it flash for us (probably depending on the "Preflash validation").