Need help with unbricking/resetting acer liquid Z330 - Android Q&A, Help & Troubleshooting

I've downloaded the stock ROM from the acer site, put it on my SD card and went into recovery to apply the update from the sdcard. When trying to update I got the following error:
e: footer is wrong
e: signature verification failed
Installation aborted.
Now, I've searched everywhere and tried at least 20 different things without anything working. I've unlocked the bootloader and flashed the boot.img which was inside the update file I downloaded from the acer site, I've tried flashing certain files seperatly etc. Another problem is, there is no system.img or recovery.img or any other img file in the stock rom from acer which doesn't allow me to flash it via the fastboot. So either I need to find those img files, or I need a fix for the error above.
Any suggestions?
(One more thing, I really can't try using a custom recovery to disable signature verification because the Liquid Z330 is such an unsupported phone, there is no cwm or twrp recovery for it. I also don't wanna risk trying another phone's cwm or twrp on the Z330 because I don't have the stock recovery.img file in case it doesn't work.)
UPDATE: I found an older version of twrp for the phone and I was able to disable signature verification but when trying to install the zip I get this error log:
Updating partition details...
*in red* E: Unable to mount '/system'
...done
Full SELinux support is present.
MTP Enabled
Installing '/sdcard/update.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip '/sdcard/update.zip'
Any new suggestions as to what might be the problem?
Update2:
So after Ysfzone posted this tutorial:
http://forum.xda-developers.com/general/general/acer-liquid-z330-unbrick-unlock-t3520952
I was able to restore my acer liquid z330.
I did actually run into some trouble with Ysfzone's instructions, and found a way around it, it should be the second comment on the post.
My only problem now is that the system is restored it's booting into demo mode. When I try to update it downloads the update and reboots into TWRP and when I then reboot to the system it says that the install failed. I think it would automatically install the update with the stock recovery but because I have TWRP installed I have to find the downloaded update file and install it manually.
So I have two options:
Either someone tells me where the update download folder is, or someone provides me with the stock recovery.
Any help?

Exactly same issues
Hey there!
I have the exact same issues. I have been trying to unbrick my phone, but nothing has actually worked. My phone is still stuck on the white screen with the acer logo.
Did you make any progress?
Were you able to find out anything that works??
Any help will be appreciated.
Thanks
MK

markendeyk said:
Hey there!
I have the exact same issues. I have been trying to unbrick my phone, but nothing has actually worked. My phone is still stuck on the white screen with the acer logo.
Did you make any progress?
Were you able to find out anything that works??
Any help will be appreciated.
Thanks
MK
Click to expand...
Click to collapse
(If you don't want to read the story, read the last sentence.)
I actually was able to get rid of the MD5 check error by creating a MD5 file myself. You basically have to download an application that gets you the MD5 sum. I used this: http://www.fast-files.com/getfile.aspx?file=127067 (just reuploaded it because I forgot where I got it from). Using the exe file in there I generated the MD5 file in this format: d2a862b7c1a8f66b6d1be32f400dc73e *update.zip. After that I tried installing the zip again, this time I got the same error except with the MD5 error missing. After contacting Acer support, I was basically told that I needed to send my info back so I could get contacted for a repair. But since I flashed the recovery it probably wouldn't fall under warranty.
So basically try emailing Acer support and try and get them to repair it. I havent found a way to fix it myself.

One more thing. It wasn't my phone to begin with, I just tried to fix it for someone. That person already has a new phone and I won't be trying anything anymore to fix the phone since I don't have it anymore.

Hello everyone,
I've been in the same situation as you until few hours.
I've also tried a lot of things which doesn't work at all ( like extracting system.img from the Acer update.zip ).
I've seen that every time I tried to install an update.zip package I get the same error:
E: footer is wrong.
E: signature verification failed
And I solved it by unzipping and zipping it again.
Then when I was able to flash it and get my phone back.
if it still doesn't work with the stock recovery, you may try with a custom recovery ( like twrp, you can easily find it on google )
If you have any questions about it, I can try to answer them.
Hope it'll help !

pxie said:
Hello everyone,
I've been in the same situation as you until few hours.
I've also tried a lot of things which doesn't work at all ( like extracting system.img from the Acer update.zip ).
I've seen that every time I tried to install an update.zip package I get the same error:
E: footer is wrong.
E: signature verification failed
And I solved it by unzipping and zipping it again.
Then when I was able to flash it and get my phone back.
if it still doesn't work with the stock recovery, you may try with a custom recovery ( like twrp, you can easily find it on google )
If you have any questions about it, I can try to answer them.
Hope it'll help !
Click to expand...
Click to collapse
Thanks for the suggestion. Just out of curiousity I guess I'll ask the phone back and try it.

I've tried it again, but the problem isn't because the signature verification fails, its something else. Idk what.

Hello Mounir9912,
Have you try to re-download the file from acer website, or/and to check the zip file with winzip or winrar ?
I've read that you created a md5 file, for my part I just disable md5 verification from TWRP.
It seems like you've got a system mount error, do you still get it if you wipe all partition on your phone (system, cache, data, dalvik cache) ?
Finally, I don't know if it can be useful, but I have a TWRP backup of my z330
I'll stay available if you still have trouble.

pxie said:
Hello Mounir9912,
Have you try to re-download the file from acer website, or/and to check the zip file with winzip or winrar ?
I've read that you created a md5 file, for my part I just disable md5 verification from TWRP.
It seems like you've got a system mount error, do you still get it if you wipe all partition on your phone (system, cache, data, dalvik cache) ?
Finally, I don't know if it can be useful, but I have a TWRP backup of my z330
I'll stay available if you still have trouble.
Click to expand...
Click to collapse
You might just be the godsend I needed. I've already tried everything you said including wiping and disabling the verification. Could you upload the twrp backup somewhere? It might be the only thing that can save this phone aside from paying way too much money to acer because of a voided warrantee.

Hello Mounir9912,
Here the link to download the twrp backup of my z330:
mega.nz/#!idICgLAZ!uJo_EvbMHAyVju9qo_uWY7d7aVLkpqxmZAWSd8jtmkk
Hope it'll help.
I'll stay available if you still need help.

pxie said:
Hello Mounir9912,
Here the link to download the twrp backup of my z330:
mega.nz/#!idICgLAZ!uJo_EvbMHAyVju9qo_uWY7d7aVLkpqxmZAWSd8jtmkk
Hope it'll help.
I'll stay available if you still need help.
Click to expand...
Click to collapse
Thanks, I'll try it when I get home (in a few hours)

damn, mega is being an asshole. I downloaded it but while downloading I accidentally unplugged the power cable from my laptop and it shut down so I had to redownload. When I downloaded again it cut me off at like 90% because of exceeding the bandwidth quota of 5GB. Now I have to either pay a monthly fee or wait 5 hours...

Hey pixie,
I've actually restored it via twrp, but it still isn't booting past the logo. Could you maybe make a backup of all the partitions except the boot, system and data partitions? The problem is probably in one of those partitions since restoring the boot or system didn't fix it.

more specifically, the ones I could backup are:
Modem, Aboot, pad, modemst1, modemst2, misc, splash, fsg, persist, cache, devinfo, oem

Hi, i'm in the same problem can you give me the link of official rom ? Plz

Ysfzone said:
Hi, i'm in the same problem can you give me the link of official rom ? Plz
Click to expand...
Click to collapse
https://www.acer.com/ac/en/GB/content/support-product/6358?b=1
Its under "OS"
Or direct download link:
http://global-download.acer.com/GDF...30&Step3=Z330&OS=ALL&LC=en&BC=ACER&SC=EMEA_27

Done Done Done !!!!!!
i fixed this problem wooow !!!!!!

This is how to unbrick Acer Liquid Z330
1- Download Official Rom from here : https://www.acer.com/ac/en/GB/content/support-product/6358?b=1
2- Download this tool from : http://www.stupdroid.com/2016/10/tool-systemnewdat-into-flashable-img.html
3- Download python (required for tool in step 2) : https://www.python.org/downloads/
4- Download Drivers the link on step 1
5- Download and install Fastboot (Search for it)
6- Create new Folder and put into all files on tool (step2) and file_contexts + system.new.dat + system.patch.dat + system.transfer.list from the Official rom
7- now launch "system.new.dat 2 flashable img converter" and tap any key and wait... after you got 2 files.. you need just the file called system.new.img
8- move system.new.img to fastboot/adb folder and rename it to system.img
9- enter phone to fastboot mode and type this command :
fastboot -w
fastboot flash system system.img
10- now just wait and don't worry about messages from fastboot...
11- after you finishing type: fastboot reboot
and wait between 5/10 mins for phone booting..
and DONE !!
Sorry for my bad english

Now my phone stuck on demo mode.. i want the stock recovery.img

hello,
first sorry for the delay.
As far as i remember, I've checked all when I backup the phone. But all that things you list are not unknown, I've seen them when the phone was still bricked. By the way, I even made a backup at this moment, so if you think that it can be useful..
Ysfzone, have you try to use qfil to get you're stock recovery ?

Related

[Q] Unable to find partition size

I am caught in a bootloop with my TF300T and am desperate for help or to know for sure if I bricked or if there is a way out. I have successfully rooted my TF300T a month or two ago by following the thread at http://forum.xda-developers.com/showthread.php?t=2187982. I kept the latest Asus ROM that I had before the root – I believe it was 4.2.1 but have no way to verify this now.
After rooting, I installed Super SU Pro and used “Root App Delete” and periodically “safe delete” (with undelete) bloatware, tested the tablet for a while, then safe deleted something else that seemed to be bloatware. Apparently I have deleted one to many essential components and am caught in a bootloop. I can’t tell which app deletion did me into this situation.
When booting to recovery using pwr + vol. down, I get the three icons (RCK, android, and wipe data) and am able to go into TWRP when selecting the RCK option. I was also able to flash an update to TWRP from my PC and upgraded from TWRP 2.5.0.0 to 2.6.3.0 in hope that the new version will be able to fix what my previous version didn’t. You may find it important that at the top of the Fastboot screen – the one with the three icons, it reads:
Key driver not found.. Booting OS
Android cardhu user bootloade <1.00 a> released by “US_epad-10.6.1.27.1-20130711” A03
Starting FastbootUSB download protocol
From TWRP I tried to wipe Dalvik and cash as some threads suggested, and to clear permissions. Clear permissions ran for 2-3 hours and didn’t complete. Those attempts produced the following message:
E: Unable to find partition size for ‘/recovery’
E: Unable to find partition size for ‘/boot’
Updating partition details…
Simulating actions…
…Followed by a “Failed” message
I also have a backup from shortly after the root and when attempting a restore it from TWRP, I get the same “Unable to find partition” message.
What I was trying to get to is to flash the latest Asus provided firmware for the TF300T (10.6.1.27.5, 508 MB) by putting the once unzipped zip file on a Micro SD card, and renaming the zip like the above referenced blog suggests, and then attempting to install it from the TWRP Install utility. This too failed resulting in the same “Unable to find partition…” messages above.
What does it really mean “Unable to find partition”? Why can't I restore my backup? Am I supposed to be able to flush a new ROM OS from TWRP Install utility? Any idea on a new direction will be appreciated. Please be patient with me – I am of the generation of printed manuals and am learning this new way.
I just installed SuperSU after unlocking...
When I boot into recovery, it says Unable to find the partition size for recovery and boot.
I then decided to factory reset to get ready to install a new ROM, and it kinda works... Then I try to install the ROM and it fails.
I reboot the system and it just boots into recovery. :/
I checked my downloads, and I downloaded the correct version(-4.2 blob) for my device(tf300t). I followed instructions but still ended up in this boot loop. Any suggestions?
Edit: Found a more updated version of TWRP(I had 2.6.x, found a 2.7)
Everything was smooth sailing from there.

Can't Flash Recovery

I recently updated to freedom os rom on my one plus 3 to see how it works and made a nandroid backup for my older rom in twrp recovery but after i flashed the rom my recovery somehow got deleted
Then i looked at few tutorials and tried to flash the twrp recovery via fastboot but it always shows an error cannot load recovery.img
i changed the name few time like twrp.img or just twrp but nothing is working
I need help fast
Suryanshd10 said:
I recently updated to freedom os rom on my one plus 3 to see how it works and made a nandroid backup for my older rom in twrp recovery but after i flashed the rom my recovery somehow got deleted
Then i looked at few tutorials and tried to flash the twrp recovery via fastboot but it always shows an error cannot load recovery.img
i changed the name few time like twrp.img or just twrp but nothing is working
I need help fast
Click to expand...
Click to collapse
What is the exact error message it gives you when you try and flash with fastboot?
SOLVED!!
The problem has been solved
I just had to download another version and put the file in the same folders as platform tools
I am new to this so I didn't know
But thanks for replying
Urgent Help Needed with OP3 running Freedom OS v1.7-C.E
Suryanshd10 said:
I recently updated to freedom os rom on my one plus 3 to see how it works and made a nandroid backup for my older rom in twrp recovery but after i flashed the rom my recovery somehow got deleted
Then i looked at few tutorials and tried to flash the twrp recovery via fastboot but it always shows an error cannot load recovery.img
i changed the name few time like twrp.img or just twrp but nothing is working
I need help fast
Click to expand...
Click to collapse
In my case I am unable to access recovery mode and factory data reset has no use and it is the only way to access the options menu. Even the power off - restart - screen shot menu area not access able.
Please help fast.
Even in fastboot mode the PC recognizes my device but not as OnePlus3.
I cannot access some apps like b612, injustice etc.
Even the OnePlus Launcher is not working.
Some apps like B612 ,Injustice ,Godfire ,WhatsApp and Hike just load the previous screen and cannot be opened. They are all present in the apps list and app drawer.
TeenNewbie1347 said:
In my case I am unable to access recovery mode and factory data reset has no use and it is the only way to access the options menu. Even the power off - restart - screen shot menu area not access able.
Please help fast.
Even in fastboot mode the PC recognizes my device but not as OnePlus3.
I cannot access some apps like b612, injustice etc.
Even the OnePlus Launcher is not working.
Some apps like B612 ,Injustice ,Godfire ,WhatsApp and Hike just load the previous screen and cannot be opened. They are all present in the apps list and app drawer.
Click to expand...
Click to collapse
I would recommend backing up the data you want to save and then flashing the stock firmware for your OnePlus3 which I would recommend taking a look at this guide here. If you have any questions please let me know I'll be happy to help you out !
shimp208 said:
I would recommend backing up the data you want to save and then flashing the stock firmware for your OnePlus3 which I would recommend. If you have any questions please let me know I'll be happy to help you out !
Click to expand...
Click to collapse
But I cannot access recovery mode, which couldnot be accessed after flashing Freedom OS.
I have already backed up all the apps and other files.
shimp208 said:
I would recommend backing up the data you want to save and then flashing the stock firmware for your OnePlus3 which I would recommend taking a look at this guide here. If you have any questions please let me know I'll be happy to help you out !
Click to expand...
Click to collapse
Hi there, like the guide i followed the steps , but now i cannot access the recovery mode (but i can access the bootloader). when i try to access recovery mode a page appears that has its its first line as follows
start do md5 checksum
then the below lines appear in red
cache : failed
boot : failed
boot_aging : failed
system : failed
md5 checksum failed
when i try to upload oneplus stock rom through command window it says
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
And one more thing ,I think i reached this glorious stage during a supersu unroot.WILL his lead to any more complications?
Please help. Being like this feels like forever. I am living in India so the chance of someone else knowing anything about this are very slim.
Thanks in advance

[TWRP][RECOVERY] Asus ZenPad 10 Z300M, Z301M & Z301MF (locked bootloader ok)

This is basically a copy of my Z380M TWRP thread adopted for the ZenPad 10. I decided to start a new one since the OP of justshaun's original recovery/rooting thread has gone stale, even as I had posted several new releases of TWRP over the months. Its instructions are also a little outdated. I've also compiled a version for the new Z301M(F) models and needed a place to post it. This is where I will be posting TWRP updates from now on.
In addition to this thread, referring to the Z380M TWRP thread and the original Z300M thread (links above) may be helpful. These models share the same hardware and software base, so most things that apply to one tablet also apply to the others.
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 or Linux PC
SP Flash Tool version 5.1532 (only this version will bypass security checks)
MediaTek VCOM drivers (available through Windows Update)
ZenPad 10 scatter file for SPFT, attached (choose the one for your tablet)
Recovery image, attached (choose the one for your tablet)
ZenPad Z300M, Z301M or Z301MF tablet upgraded to Android N
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 10.
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 for your device (twrp-3.2.1-0-z30*m.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-z30*m.img
Once inside TWRP, flash twrp-3.2.1-0-z30*m.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". On the Z301M/Z301MF, that option is labeled Factory Reset. 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.
WARNING 2: Make sure you use the correct scatter file for your device (i.e. don't mix up the Z300 and Z301 files). For the initial flash, there is no check for scatter file correctness. If you use the wrong one, SP Flash Tool will alter and lock your GPT to that scatter file layout, possibly bricking your device. It will not be easy to restore it. Flashing with the correct scatter file later on will not work because Flash Tool will not allow you to use a different file than the one you used initially.
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
SP Flash Tool v5.1532
Z300M Scatter file for all storage sizes (right click, Save link as...) -- do not use for other models
Z300M TWRP 3.2.1-0 image -- updated March 15, 2018
Z301M(F) series Scatter file for all storage sizes (right click, Save link as...) -- do not use for Z300M or other devices
Z301M TWRP 3.2.1-0 image -- updated March 13, 2018
Z301MF TWRP 3.2.3-0 image -- updated August 29, 2018
Development and experimental files
Source code
P.S. The thanks button doesn't bite.
Heya, thanks for the new thread..
Stupid question(coming from Samsung flashing)
Ive got Zenpad S3 10 P027, is this TRWP not ideal for this?
Currently, have some su (root) issues. Recovery shows Android icon chest with ! and says "No Command"
When running su in Terminal ADB via PC, says command not recognized.
Looks like I need to reflash recovery. When in TRWP (launched via fastboot boot twrp on PC) I flashed stock recovery but had system mounted read only. Could that be the problem?
Bro, I think you need to do some more homework on root, su, dm-verity, mods, etc. and read the instructions more carefully before applying these hacks. You are making a lot of simple mistakes and ending up shooting yourself in the foot for it. I don't think there's anything wrong with the Z500 TWRP. It can handle installing the stock firmware just fine. The problem is elsewhere. The unlock tool also works fine in TWRP as well in my testing.
The No Command screen is normal. That's been answered many times... you need to hold power+vol. up (or down) to get to the menu. There is no way the stock recovery image can be broken and still boot up.
The su thing, IDK what the problem is, but I'm sure if you install Magisk Manager and make your own patched image from your currently installed firmware, and fastboot-boot with it, you will have su functionality. Just like what it says in the unlock tool instructions.
Lastly and most important, never mount system in read-write mode, as I've repeated several times and exactly as it says in the directions:
7. At the TWRP welcome screen, do not select to modify the system partition and touch Keep System Read-only instead. Doing otherwise will render your tablet unbootable.
8. Mount system in TWRP (in read-only mode)
Click to expand...
Click to collapse
The only time you can mount it in read-write mode is when you are absolutely sure you have disabled dm-verity in your boot image.
I've successfully installed TWRP on Z301M using the instructions from the first post, but then I somehow managed to lose the system. Yes, I should have backed up like the OP suggests.
I thought I should be able to reinstall the original firmware downloaded from Asus (e.g. UL-ASUS_P028_1-WW-3.3.12.0-user.zip) but both the 'adb sideload' method and the TWRP failed to install that firmware zip. My device looks bricked. The only thing I can do is to boot into TWRP (I actually need to select Factory Reset on the bootloader screen to get into TWRP). The folder 'system' is empty.
Can anyone suggest what I am doing wrong when trying to restore the Asus firmware?
When I try to sideload the zip, setting TWRP in the sideload mode, the computer begins uploading but after a few seconds gives the message "Total xfer: 0.01x" and stops, while Android errors with "set boot part fail. can not open misc-sd".
When I install the firmware zip from TWRP it also starts installing fine but shortly gives the same error "set boot part fail. can not open misc-sd".
Thanks
@ahacker, first of all, thank you for the feedback on the Z301M platform. You are literally the first person to have said anything about that version of TWRP.
To see the files on system, you first have to mount the system partition. Did you do that? If not, I suggest mounting it read-only. If there was any corruption on it, then reinstalling the firmware should have fixed it. The "misc-sd" errors are normal. Pretty sure they happen on stock recovery too. The stock firmware does not have dm-verity enabled, so letting TWRP modify system to prevent overwriting recovery should not have caused any problems.
At which point did it stop booting? Also, did you use the scatter file from first post? And can you tell me if the touch screen works fine in TWRP on your tablet?
I'm not sure what the deal is with adb sideload. I don't think I've ever actually tried it....
diplomatic, thanks for replying!
diplomatic said:
[MENTION=4776997]
To see the files on system, you first have to mount the system partition. Did you do that?
Click to expand...
Click to collapse
I do mount the system partition. It appears empty. When I reboot into system TWRP says that the OS is not installed.
I don't remember the details of how I lost the system partition. First time I entered into TWRP it asked for a password, probably to mount some partition. I pressed cancel or something. Then I might have cleaned the caches. But I am sure I haven't wiped system. I might have pressed Factory Reset somewhere, because I don't have any data yet on the new tablet.
I would indeed try to mount the system read only. This is not the first Android system I rooted (maybe fifth), and I was always able to restore the system either from sideload or recovery. But here it seems Asus is making us jump extra hoops to do that.
diplomatic said:
[MENTION=4776997]
Reinstalling the firmware should have fixed it.
Click to expand...
Click to collapse
That seems to be my main problem now. I cannot reinstall the Asus firmware. It may look like I might be installing a wrong version, but I am positive that I have Z301M tablet. This is what I bought and what the boot-loader says. I download Z301M firmware from the Asus website (e.g.). So it must be a correct firmware.
diplomatic said:
[MENTION=4776997]
The "misc-sd" errors are normal. Pretty sure they happen on stock recovery too. The stock firmware does not have dm-verity enabled, so letting TWRP modify system to prevent overwriting recovery should not have caused any problems.
Click to expand...
Click to collapse
Thank you for the information.
diplomatic said:
[MENTION=4776997]
Also, did you use the scatter file from first post? Does the touch screen work fine in TWRP on that tablet?
Click to expand...
Click to collapse
Yes. I found that to be the only scatter file that worked. I tried scatter.txt from the firmware zip, but the Flash Tool refuses tio pick it up. TWRP seems to be working fine with touches working as expected.
diplomatic said:
[MENTION=4776997]
I'm not sure what the deal is with adb sideload. I don't think I've ever actually tried it....
Click to expand...
Click to collapse
This is the unbricking method described here. It probably does the same thing as the "Install Zip" from recovery, because the errors that both methods give are the same.
---------- Post added at 01:19 AM ---------- Previous post was at 12:57 AM ----------
Now system refuses to mount
ahacker said:
I don't remember the details of how I lost the system partition. First time I entered into TWRP it asked for a password, probably to mount some partition. I pressed cancel or something. Then I might have cleaned the caches. But I am sure I haven't wiped system. I might have pressed Factory Reset somewhere, because I don't have any data yet on the new tablet.
Click to expand...
Click to collapse
Er, the password should have been for decrypting your userdata. If you didn't have one set up, there might be something wrong there.... Or possibly just unformatted.
ahacker said:
That seems to be my main problem now. I cannot reinstall the Asus firmware. It may look like I might be installing a wrong version, but I am positive that I have Z301M tablet. This is what I bought and what the boot-loader says. I download Z301M firmware from the Asus website (e.g.). So it must be a correct firmware.
Click to expand...
Click to collapse
Yeah, that has to be the right one. The installation script has to match the model name reported by the recovery. Otherwise it would simply abort.
ahacker said:
Yes. I found that to be the only scatter file that worked. I tried scatter.txt from the firmware zip, but the Flash Tool refuses tio pick it up. TWRP seems to be working fine with touches working as expected.
Click to expand...
Click to collapse
Great! Guess my kernel patch was on the dot and the partition layout has not changed from the Z300.
ahacker said:
This is the unbricking method described here. It probably does the same thing as the "Install Zip" from recovery, because the errors that both methods give are the same.
Click to expand...
Click to collapse
When you installed the zip, did you unmount system completely? BTW, when you mentioned the errors, the installation does keep going for like 5 to 10 minutes afterwards, right?
If you still can't resurrect it, please post or send me the recovery & kernel log that has your installation attempt.
diplomatic said:
When you installed the zip, did you unmount system completely? BTW, when you mentioned the errors, the installation does keep going for like 5 to 10 minutes afterwards, right?
Click to expand...
Click to collapse
I've tried both ways, with and without system mounted, a few times. The installation would fail after something like 5 seconds.
diplomatic said:
If you still can't resurrect it, please post or send me the recovery & kernel log that has your installation attempt.
Click to expand...
Click to collapse
I think I am giving up on this cheap tablet. I cannot even format it in the Flash Tool: it says "To format code area is forbidden on this phone". Asus is forbidding too much for me to ever buy it again. Attached the logs.
Thanks, diplomatic
OK, found the problem. Check your PMs, ahacker.
diplomatic said:
OK, found the problem. Check your PMs, ahacker.
Click to expand...
Click to collapse
I have replied (twice), but the reply does not appear in my Sent Items. I hope it has reached you. If not, I'll paste the reply here, if you don't mind.
i not understand... i have Asus ZenPad 10 LTE Z301MFL.. a root method has been released ???
@diplomatic
Would this be compatible with Z0310M ? can't find anything for this damn model...
Hi, NeBouse,
Are you sure you have the correct information? It looks like just a misspelling of Z301M, aka P028....
I have z301m.
One thing that was a surprise for me is that the TWRP recovery flashed with the method described in the original post does not stick. You have to flash it each time you use it. If you are like me this information is important, because the original recovery plainly wipes your data without asking or warning.
After you have flashed TWRP on the device, to go to the recovery mode you have to chose "Factory Reset" in the bootloader. Then it will complain about wrong OS, which is the sign that flashing TWRP worked; choose 'yes'. The first thing you should do in TWRP is a ful nandroid backup. (Not listening the OP's advice about backing up when Installing TWRP with a wrong scatter file almost cost me the device. Thankfully diplomatic managed to remotely fix my problem, probably spending a lot of his personal time. The scatter file in the original post is a correct one now.)
Creating a nandroid backup in TWRP takes unusually long time, I even once decided that it hanged. Taking long time, like 10-30 minutes, for a full backup is normal.
Asus Z300M , Magisk 16.3 (beta) and FW 5.3.19 WW now works!
z301m, WW-3.3.12.0 firmware
For rooting I've installed in TWRP Magisk v15.3 (diplomatic warned against 16.x, someone else against 15.4) - link.
Installed in TWRP xPosed framework 88.2 - link, and xPosed Installer apk from within Android - link.
So far, so good.
What I've found is that TWRP seems to have problems with external sd cards (lots of fs corruption). I found it safer to unmount by hand by unticking the sd card checkbox in "Mount". Not very conclusive about this though.
Thanks, ahacker. Good feedback. Although to be fair, I didn't say to avoid Magisk 16.x. I said 16.0. I'm pretty sure whatever bug it had is already fixed in the latest version.
Now that you've installed root, TWRP will stick around on the emmc. The stock recovery only gets installed if you have the original unpatched boot image on it. I mean, this is not unique to these devices. That's been standard Android functionality since some 4.x or 5.x version. And this is essentially what's in the warning on the OP.
The backup I'm talking about in the installation method is done with the SP Flash Tool readback function. That will pull the partition tables and your device's "metadata" that's unique to your unit. I don't think nandroid covers that...
Oh, and what is this SD corruption you're talking about? What file system is it formatted in? Have you checked your card for errors in Windows?
Asus releases so many difference Z301M model, so I am curious if this also works on Z301MF model?
Notice Z300MF has the MTK8163BA (or MTK8163A?) CPU model while Z301M uses : 8163B
Anyone tested that already? Thanks.
my zenpad 10 has frp lock. it this a solution to remove the frp lock?
Pls help how i flash original software via fastboot ?????

Huawei mate 10 pro wont boot at all. Please help.!!

Hello,
I was wondering if some could help me please. I wanted to flash RR Rom 6.0 on my BLA-L09(I think that what's it is) phone.
I was able to unlock my boot loader, and flash TWRP my device but my dumb s*** flashed TWRP to my file system use FLASH SYSTEM instead of FLASH RECOVERY. Now, I can't fix it ?. I know I can use sideload so I'm not panicking just yet however I know I messed up the file system.
Could someone tell me what file system system I should be using (fat, exfat, ext4, etc...) and what to do to get this think to boot backup.?
I've tried and side loading "update_full_BLA-L29_hw_la.zip" stock ROM but no luck... I keep getting this error message:
"check_write_data_to_partition,write data error
Update_huawei_pkg_from_ota_zip: update package from zip failed
Updated process ended with error: 9"
HELP.!!!
me too..... following searching for a solution
Shandroid_94 said:
me too..... following searching for a solution
Click to expand...
Click to collapse
If you find anything, let me know.!
Just boot to fastboot, flash RR to system and TWRP to recovery_ramdisk?

Ulefone Armor 6E - only stock recovery after flashing TWRP

I tried to flash TWRP using this guide: https://unofficialtwrp.com/twrp-3-3-1-root-ulefone-armor-6e/
I do everything step by step, but every time after rebooting to recovery there is not TWRP but only stock recovery. I have unlocked bootloader. The device is active using the "fastboot devices" command. USB debugging mode is ON. Please help me solve this problem
install Magisk then official twrp app and flash twrp from the app to recovery
PanRyba said:
I tried to flash TWRP using this guide: https://unofficialtwrp.com/twrp-3-3-1-root-ulefone-armor-6e/
I do everything step by step, but every time after rebooting to recovery there is not TWRP but only stock recovery. I have unlocked bootloader. The device is active using the "fastboot devices" command. USB debugging mode is ON. Please help me solve this problem
Click to expand...
Click to collapse
The only way it worked for me was to install official twrp app, and flash twrp-3.3.1-0-Armor_6.img from the app to recovery, then click on reboot to rrcovery also in the app.
Twrp will only be available one time after the reboot (so it is not really flashed)
(Adb flash recovery doesn't work for me)
In order to use official twrp app, i rooted with magisk
U welcome
I'm confused now. How did you root with magisk without TWRP. The Magisk installation was basically the only reason for me to flash TWRP
PanRyba said:
I'm confused now. How did you root with magisk without TWRP. The Magisk installation was basically the only reason for me to flash TWRP
Click to expand...
Click to collapse
Same as twrp
Install magisk app and do it from there:
Go to github website and download MagiskManager-v7.3.4.apk
https://github.com/topjohnwu/Magisk/releases
From the apk you will be able to flash your boot partition with magisk (it will save a boot image flashed with magisk on your phone)
The second step is simply to transfer that .img on your computer, install platform tools (in order to use adb command line)
Launch cmd.exe in platform tools folder
Connect your phone to computer via a usb cable and usb debug enabled
Type the command "adb devices" to check if your device is recognised (if a window appear on your phone to enable connection click ok)
Then type "adb reboot bootloader" (you are now in fastboot mode)
Then type "fastboot flash boot (then the name of your flashed with magisk boot image.img that you previously put in platforms tool folder in order to not search for the path)"
Then type "fastboot reboot"
Then from magisk manager app update magisk
That's it
No need for a recovery in the first place to root with magisk
finally works. thanks you dude. I really appreciate your help
PanRyba said:
finally works. thanks you dude. I really appreciate your help
Click to expand...
Click to collapse
You're welcome
Glad to help
PanRyba said:
I tried to flash TWRP using this guide: https://unofficialtwrp.com/twrp-3-3-1-root-ulefone-armor-6e/
Click to expand...
Click to collapse
I also used that guide and couldn't get TWRP or Magisk to install on my new Armor 6E. I was able to use "Method 2" and SP Tool to flash TWRP 3.3.1-0, then I was able to flash Magisk using TWRP recovery.
I flashed Magisk-v20. 0(20000).zip
MD5 checksum: 56f82549e9f3c659a11f1f459e56489f
Now I seem to be stuck with the "Orange State" message at boot.
When I attempt to use TWRP to flash "no-verity-opt-encrypt-6.0.zip" I get the following :
-----
Installing zip file '[file path]'
Checking for Digest file...
Verifying zip signature...
Zip signature verified successfully.
##dm-verity and forced encryption disabler by jcadduono version 6.0##
Unpacking the installer...
Updater process ended with ERROR: 1
Error installing zip file' no-verity-opt-encrypt-6.0.zip'
Updating partition details...
... done
-----
The file has this MD5 checksum:
caea927e96c755f3568e85dbded88923
When I attempt to use TWRP to flash "orange_state_disabler_MTK Only.zip" I get the following:
-----
Installing zip file '[pathname]'
Checking for Digest file...
Verifying zip signature...
Zip signature verification failed!
Error installing zip file 'orange_state_disabler_MTK Only.zip'
Updating partition details...
... done
-----
That file has this MD5 hash:
30b01bb314d26643b6cc1dfce1d81cf5
I get nearly the same result when I attempt to install "ROMProvider.COM_orange_state_disabler 0.3.zip"
(Zip signature verification failed!)
That file also has the same MD5 hash:
30b01bb314d26643b6cc1dfce1d81cf5
TWRP asks for a password when I first boot into recovery. I also tried to contact them at the unofficialtwrp.com website (where I downloaded the zip files), but their contact page seems to loop back on itself.
Has anyone else run into this (and stuck with Orange State warning at boot)?
ndt44 said:
Now I seem to be stuck with the "Orange State" message at boot.
Click to expand...
Click to collapse
I was finally able to use TWRP 3.3.1 Install to flash file "ROMProvider.COM_orange_state_disabler_v0.3.zip" this morning and rid myself of the Orange State warning every single boot. NOTE: I had to UNCHECK zip file verification in TWRP Install in order to get it to work this time!!
This was my output:
-------------------------------
Installing zip file '[pathname]'
Checking for Digest file...
--- 'Orange State' disabler v0.3 - - -
##### Created by XopmoH97 #####
Current zip - > 'ROMProvider.COM_orange_state_disabler_v0.3.zip'.
Unzipping binaries to '/tmp'...
Success!
Set execute flag to 'tmp/sed-arm'.
Set execute flag to 'tmp/xxd-arm'.
Checking CPU architecture...
CPU architecture 'arm64-v8a' is supported!
Searching 'lk' block in GPT...
Success! 'lk' block = '/dev/block/mmcblk0p27'
Saving '/dev/block/mmcblk0p27' to '/tmp/lk.img'...
Testing NEW algorithm...
NEW algorithm is available!!!
Patching '/tmp/lk.img'...
Success!
Writing '/tmp/lk.img' to '/dev/block/mmcblk0p27'...
Success!!! Please reboot your device!
Updating partition details...
... done
-----------
Unfortunately, the no-verity.ZIP still will not flash!
ndt44 said:
I was finally able to use TWRP 3.3.1 Install to flash file "ROMProvider.COM_orange_state_disabler_v0.3.zip" this morning and rid myself of the Orange State warning every single boot. NOTE: I had to UNCHECK zip file verification in TWRP Install in order to get it to work this time!!
This was my output:
-------------------------------
Installing zip file '[pathname]'
Checking for Digest file...
--- 'Orange State' disabler v0.3 - - -
##### Created by XopmoH97 #####
Current zip - > 'ROMProvider.COM_orange_state_disabler_v0.3.zip'.
Unzipping binaries to '/tmp'...
Success!
Set execute flag to 'tmp/sed-arm'.
Set execute flag to 'tmp/xxd-arm'.
Checking CPU architecture...
CPU architecture 'arm64-v8a' is supported!
Searching 'lk' block in GPT...
Success! 'lk' block = '/dev/block/mmcblk0p27'
Saving '/dev/block/mmcblk0p27' to '/tmp/lk.img'...
Testing NEW algorithm...
NEW algorithm is available!!!
Patching '/tmp/lk.img'...
Success!
Writing '/tmp/lk.img' to '/dev/block/mmcblk0p27'...
Success!!! Please reboot your device!
Updating partition details...
... done
-----------
Unfortunately, the no-verity.ZIP still will not flash!
Click to expand...
Click to collapse
The Orange State disabler zip is news to me, and it sounds worthwhile to flash.
I successfully flashed the DM-Verity zip from an OTG USB drive after using TWRP to format the system and data partitions to EXT4. No success with ROMs yet.
Pergmen said:
The Orange State disabler zip is news to me, and it sounds worthwhile to flash.
I successfully flashed the DM-Verity zip from an OTG USB drive after using TWRP to format the system and data partitions to EXT4. No success with ROMs yet.
Click to expand...
Click to collapse
mvyrmnd said:
The 6 and 6E are very similar devices. The TWRP listed here works on the 6E. Magisk also works as described.
I cannot confirm for the 6 (but is likely), but the 6E works with all phh-based GSI ROMs.
These phones use A/B images.
Click to expand...
Click to collapse
Can't post links even when quoting so you just have to google "treble project github"
I have gotten roms to work (use A/B even if treble check says its only A for somereason).
I wasn't able to get liniageOS to work (from the pie roms, i think everyting else seems to work) and android Q ones even thou it should be able to from what i have gathered.
IMPORTANT! It seems like every rom is missing basic features like gestures, i dont know if it has to do with the kernel maybe? Im nubie.
VERY IMPOTANT!! Lost my IMEI number from messing around with the phone so be careful! Im not responsible.
Pergmen said:
The Orange State disabler zip is news to me, and it sounds worthwhile to flash.
I successfully flashed the DM-Verity zip from an OTG USB drive after using TWRP to format the system and data partitions to EXT4. No success with ROMs yet.
Click to expand...
Click to collapse
Would it be possible to get an MD5 checksum and filename which worked for you so that I might compare them? Did you get that file from the unofficial twrp page linked above then? Also were the "system and data EXT4 partitions" on the phone Internal Storage or the USB OTG?
ndt44 said:
I was finally able to use TWRP 3.3.1 Install to flash file "ROMProvider.COM_orange_state_disabler_v0.3.zip" this morning and rid myself of the Orange State warning every single boot. NOTE: I had to UNCHECK zip file verification in TWRP Install in order to get it to work this time!!
Click to expand...
Click to collapse
I obtained this file here:
https://www.google.com/amp/s/rompro...ange-state-fixer-fix-orange-state/amp/?espv=1
I just ordered this armor 6e phone. I will be able to answer my own question next week, I suppose. Bit, in the armor 6 thread it is mentioned few times that there twrp works on 6e, now I found this thread, which says twrp will not stay flashed to phone.
Which one is correct?
If the armor 6 twrp does work, does it work to flash gapps? Because the y is not pie, and as such is not system-as-root, which from other devices, I know that makes recovery see the phone file structure different
Ie : /system_root/system not just /system
This difference needs different build of twrp.
I will give it a try when I receive it I suppose.
mrmazak said:
I just ordered this armor 6e phone. I will be able to answer my own question next week, I suppose. Bit, in the armor 6 thread it is mentioned few times that there twrp works on 6e, now I found this thread, which says twrp will not stay flashed to phone.
Which one is correct?
If the armor 6 twrp does work, does it work to flash gapps? Because the y is not pie, and as such is not system-as-root, which from other devices, I know that makes recovery see the phone file structure different
Ie : /system_root/system not just /system
This difference needs different build of twrp.
I will give it a try when I receive it I suppose.
Click to expand...
Click to collapse
I have found a TWRP that stays on. And i have seen some that dont stay. Im able to flash gapps with it to my 6e.
poohju said:
I have found a TWRP that stays on. And i have seen some that dont stay. Im able to flash gapps with it to my 6e.
Click to expand...
Click to collapse
Thanks. Do you have links?
mrmazak said:
Thanks. Do you have links?
Click to expand...
Click to collapse
First maybe try out the unofficial TWRP (https://unofficialtwrp.com/twrp-3-3-1-root-ulefone-armor-6e/) maybe it works. I think i didnt get it to stick but its worth a shot ig and you can also try with the TWRP app (havent tried the app way). Sadly i dont remember where i got the file that sticks for me. If unofficial dosent work i can upload it to somewhere. I used ADB tools to download TWRPs. If you use SP tools to flash it while like doing a fresh install. It will go to RED state. You can use SP tools if you first install stock then unlock bootloader and flashing then only installing the recovery. You can install gapps mostly but u cant use dm veryeti disabler it messes with the IMEI at least for me. Im not that savy to know how to fix it. Its my first phone ever messing with. MAGISK works.
poohju said:
First maybe try out the unofficial TWRP (https://unofficialtwrp.com/twrp-3-3-1-root-ulefone-armor-6e/) maybe it works. I think i didnt get it to stick but its worth a shot ig and you can also try with the TWRP app (havent tried the app way). Sadly i dont remember where i got the file that sticks for me. If unofficial dosent work i can upload it to somewhere. I used ADB tools to download TWRPs. If you use SP tools to flash it while like doing a fresh install. It will go to RED state. You can use SP tools if you first install stock then unlock bootloader and flashing then only installing the recovery. You can install gapps mostly but u cant use dm veryeti disabler it messes with the IMEI at least for me. Im not that savy to know how to fix it. Its my first phone ever messing with. MAGISK works.
Click to expand...
Click to collapse
Thanks. I looked at unofficial, and unpacked there image. It is set to terrible enabled = no, and is not setup for system-as-root.
Also the prop file says it is for armor 6 not 6e, so I will just build fresh one and use that.
mrmazak said:
Thanks. I looked at unofficial, and unpacked there image. It is set to terrible enabled = no, and is not setup for system-as-root.
Also the prop file says it is for armor 6 not 6e, so I will just build fresh one and use that.
Click to expand...
Click to collapse
Good luck to you maybe you can share it when your done
poohju said:
Good luck to you maybe you can share it when your done
Click to expand...
Click to collapse
My phone is still not delivered. But I did compile twrp from source, using the September update files from ulefone site.
I started with the device tree from the armor 6, and made few changes that I have found to work for treble devices and system as root on other recent mtk phones I have.
But I can't confirm the build works. If you want to beta test it, let me know.

Categories

Resources