Related
I have attempted everything, I don't remember my B version which doesn't help. I know I was on 5.0.2 and I'm located in the UK.
I'm stuck in infinite boot loop which is happening because I deleted the OS by Accident.
I have attempted to Flash a B330 Version but boot loop. I grabbed the official Update for V5.0.2 Extracted the SYS and the other necessary files to "Unbrick" using the Honor 7 Multi-tool.
When I'm supposed to go to eRecovery I can't go to it. I have removed the cable, HOLDing both Volume Buttons and Power, when the Honor Logo pops up I remove the Power Button and it doesn't go to eRec, it just restarts due to Boot loop.
Does anyone have any suggestions what to do?
Give a shot for "Honor 7 Multi-Tool" that can be found on this Forum, that contain "Unbrick" task what you can use to unbrick your device. And that contains simple tutuorial how to do it.
Give a shot for B180 package with your country, that is FULL patch for 5.0.2 version. When that is done you can upgrade your phone to the B330.
And also for ERecovery, try hold all 3 buttons so long that you reach the recovery menu, you dont need release those buttons until you are on recovery.
kenkae said:
Give a shot for "Honor 7 Multi-Tool" that can be found on this Forum, that contain "Unbrick" task what you can use to unbrick your device. And that contains simple tutuorial how to do it.
Give a shot for B180 package with your country, that is FULL patch for 5.0.2 version. When that is done you can upgrade your phone to the B330.
And also for ERecovery, try hold all 3 buttons so long that you reach the recovery menu, you dont need release those buttons until you are on recovery.
Click to expand...
Click to collapse
thanks for your help,
I have already attempted the unbrick function on H7 Multi-Too but I can't get through to Recovery for some reason after MT is finished with transferring the files to the phone. I'v been holding the 3 buttons for 5 minutes and it just Boot-Loops, I must be doing something wrong.
Regarding how I "Deleted" the system and got into this mess, I used the Advance Wipe function in TWRP and wiped the system by accident. This might be affecting eRecovery?
I'm not sure If I used the B180 Pack or one below. So I'll re-do it and see how it goes.
Galio094 said:
thanks for your help,
I have already attempted the unbrick function on H7 Multi-Too but I can't get through to Recovery for some reason after MT is finished with transferring the files to the phone. I'v been holding the 3 buttons for 5 minutes and it just Boot-Loops, I must be doing something wrong.
Regarding how I "Deleted" the system and got into this mess, I used the Advance Wipe function in TWRP and wiped the system by accident. This might be affecting eRecovery?
I'm not sure If I used the B180 Pack or one below. So I'll re-do it and see how it goes.
Click to expand...
Click to collapse
No that wont effect anything ifyou wipe whole device, because you flash Boot/System/Recovery and other sectors with Multi Tool. So that install's a fresh install there.
Give a shot for that B180 package with correct country for you, flash all sectors with MultiTool and then reboot to recovery. That should work, if not then something goes wrong with flashing.
Heres my Thread from this forum, i think i have done that situation what you have going now.
http://forum.xda-developers.com/honor-7/general/honor-7-premium-stock-images-plk-l01-t3369369
Couldn't find B180, Only B130.
Used Huawei Updater to Extract Files.
and used multi tool's unbrick, Attempted to go to eRecovery no success.
Tried Multi-TOols Reboot to eRecovery no success as it needs USB Debugging.
I'm stuck :'(. Also lost Ability to go back to TWRP
Here is B180 for your Device (United Kingdom): http://www.hihonor.com/uk/support/details/?DOC_ID=77725
Boot your phone to the Fastboot, then flash new TWRP to your device. Shut it down and try boot to the Recovery.
When you have successfully rebooted to the TWRP, create folder what is named to dload inside your SDCard, then put that B180 "Update.app" file inside that folder.
When that step is done, start UpdateExtractor, and take Unbrick files out from that .app file.
Next step will be unbricking with MultiTool, when its done just try reboot your phone first normally to the system, if that works just go: Settings->Update->Local Packet from SDCard.
And your device start updating that B180 packet completely.
After you have updated your phone to B180, download C432B330 packet and just replace that "Update.app" file on your SDCard with that B330 file and repeat previous steps.
The problem was B130 and B180. Before deleting my OS I attempted a ROM Flash from B330 when being on a B180 System (which tells you not to do). So my System froze at B330 I guess. WHen I attempted to Unbrick on B330 it worked, didn't work on B130 or B180.
Though the process itself was correct, was just the package . Thanks
Hey guys,
I've had a total of 4 android smartphones during the last years, and I did root all of them and even install diferent ROM's, but on this phone (Honor 7) was kinda diferent.
The root process is way more complex than all the other androids I did root (simply flash a .zip file...) so I've been post-poning this task over and over..
Finally yesterday I gained courage to try out rooting my phone, and while attempting to root my Honor 7, after flashing SuperSU from TWRP, my phone no longer booted.
Stressed as I was, I just told to myself "f*ck it" and formatted the system and I didn't care much if there was a fix without needing to format the system. (but then I realised that I could not find any .img ROM files to flash from TWRP recovery, so basically I did my actions wrong once again)
I followed the tutorial from guidebeats.com which talks about rooting EMUI 4.0 Android 6.0 (I cant post links)
Basically this is the story:
While unlocking the bootloader, even though, the tutorial said the phone would reboot itself after typing "flashboot oem unlock 1234934829" I did a hard reboot (or reset?) holding (VOL+) + Power button and I have the feeling that the bootloader unlock was not 100% done, even if it said it was unlocked. (Phone was working perfectly fine there)
Then I flashed SuperSU, and I could no longer boot. After powering up my phone, after the first splashscreen, the screen would only turn black.
What (I think) I need to now is remove the TWRP recovery, and use the stock one and attempt to install an "update" using (Vol+) + (Vol-) + Power. (please correct me if I'm wrong)
But now there's some issues I got that I'd like some help with:
1- How can I get back to the stock recovery? (NOTE: I currently got no OS installed on my Honor 7, since I formated it)
2- Will I need to lock and unlock my bootloader again (if I want to 'fix' the bootloader unlock?)
3- Where can I get official Honor 7 stock ROM? (would be awesome if there was already the Android 6 stock rom for a clean install)
4- What are the steps on this tool (Honor 7 Multi-Tool) to root my phone?
I need my Honor 7 asap
Sorry for the long post, It's my first time doing a more advanced root and I have all these questions.
Thank you very much for any kind help!
joaomPT said:
Hey guys,
I've had a total of 4 android smartphones during the last years, and I did root all of them and even install diferent ROM's, but on this phone (Honor 7) was kinda diferent.
The root process is way more complex than all the other androids I did root (simply flash a .zip file...) so I've been post-poning this task over and over..
Finally yesterday I gained courage to try out rooting my phone, and while attempting to root my Honor 7, after flashing SuperSU from TWRP, my phone no longer booted.
Stressed as I was, I just told to myself "f*ck it" and formatted the system and I didn't care much if there was a fix without needing to format the system. (but then I realised that I could not find any .img ROM files to flash from TWRP recovery, so basically I did my actions wrong once again)
I followed the tutorial from guidebeats.com which talks about rooting EMUI 4.0 Android 6.0 (I cant post links)
Basically this is the story:
While unlocking the bootloader, even though, the tutorial said the phone would reboot itself after typing "flashboot oem unlock 1234934829" I did a hard reboot (or reset?) holding (VOL+) + Power button and I have the feeling that the bootloader unlock was not 100% done, even if it said it was unlocked. (Phone was working perfectly fine there)
Then I flashed SuperSU, and I could no longer boot. After powering up my phone, after the first splashscreen, the screen would only turn black.
What (I think) I need to now is remove the TWRP recovery, and use the stock one and attempt to install an "update" using (Vol+) + (Vol-) + Power. (please correct me if I'm wrong)
But now there's some issues I got that I'd like some help with:
1- How can I get back to the stock recovery? (NOTE: I currently got no OS installed on my Honor 7, since I formated it)
2- Will I need to lock and unlock my bootloader again (if I want to 'fix' the bootloader unlock?)
3- Where can I get official Honor 7 stock ROM? (would be awesome if there was already the Android 6 stock rom for a clean install)
4- What are the steps on this tool (Honor 7 Multi-Tool) to root my phone?
I need my Honor 7 asap
Sorry for the long post, It's my first time doing a more advanced root and I have all these questions.
Thank you very much for any kind help!
Click to expand...
Click to collapse
As you are already familiar with adb and other stuff so will write a short post for you.
To download latest firmware, head to
http://forum.xda-developers.com/hon...tock-firmware-packages-honor-7-t3448747/page1
Google, download and install Huawei update extractor and open UPDATE.APP in it (obtained after extracting firmware).
You can see all the images. Just extract recovery and boot to platform-tools folder.
Meantime, do the unlocking command again, with
Fastboot OEM unlock xxxxxxxxxxxxxxxx
Followed by fastboot reboot
And press and hold the vol down button again until you reboot in bootloader.
Flash the recovery and boot you extracted using
Fastboot flash recovery recovery.img
Fastboot flash boot boot.img
(I got a habit of extracting and flashing system and Cust using
Fastboot flash system system.img
Fastboot flash Cust Cust.img
But they are not necessary)
Now you are set to try a 3 button update (sometimes it gets stuck so if it's stuck for 15 minutes, try 3 button again).
Please do report back if it comes to life.
To root, just flash twrp and then use SuperSU 2.62 (no other version) and update it later using play store.
Sent from my PLK-L01 using XDA Labs
Hey!
Thank you alot for your reply.
From the link you sent about the firmwares, there are alot of Builds for the L01 (EU) model. Can I simply use the latest from the list or I gotta install 1 by 1 (from older to newer)?
Also, the bootloader unlock thing, is it ok if I wait to do it until I install the stock ROM again? Because I think I don't have the code anymore (Also don't know about IMEI)
Other thing, yesterday before bricking my phone, I tried to re-unlock the bootloader as you said above, but it didnt let me because "it was already unlocked".
I really have no idea if it's 100% unlocked or not.
important thing!
With those ROM's, I still have the right to receive official OTA updates from the HiCare app right?
Thank you again
joaomPT said:
Hey!
Thank you alot for your reply.
From the link you sent about the firmwares, there are alot of Builds for the L01 (EU) model. Can I simply use the latest from the list or I gotta install 1 by 1 (from older to newer)?
Also, the bootloader unlock thing, is it ok if I wait to do it until I install the stock ROM again? Because I think I don't have the code anymore (Also don't know about IMEI)
Other thing, yesterday before bricking my phone, I tried to re-unlock the bootloader as you said above, but it didnt let me because "it was already unlocked".
I really have no idea if it's 100% unlocked or not.
important thing!
With those ROM's, I still have the right to receive official OTA updates from the HiCare app right?
Thank you again
Click to expand...
Click to collapse
Just use B380 as it's the latest full firmware available there.
Unlocking bootloader again was just a precautionary measure (proceed without it and if it is not 100% unlocked and if something goes wrong, we can troubleshoot later, which imo, won't happen)
And yep, if you keep the firmware as it is, but if you flash twrp and root, you will still see the update available in Hicare but will have to install stock recovery again before upgrading. (Nothing else is needed as SuperSU 2.62 gives a systemless root so you only need to flash back stock recovery for an update)
I am not against honor-tool bit it's best to do things manually as it makes you learn stuff and is easy to troubleshoot if something is amiss.
Sent from my PLK-L01 using XDA Labs
muradulislam said:
Just use B380 as it's the latest full firmware available there.
Unlocking bootloader again was just a precautionary measure (proceed without it and if it is not 100% unlocked and if something goes wrong, we can troubleshoot later, which imo, won't happen)
And yep, if you keep the firmware as it is, but if you flash twrp and root, you will still see the update available in Hicare but will have to install stock recovery again before upgrading. (Nothing else is needed as SuperSU 2.62 gives a systemless root so you only need to flash back stock recovery for an update)
I am not against honor-tool bit it's best to do things manually as it makes you learn stuff and is easy to troubleshoot if something is amiss.
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
Alright, btw, about the thing you said
"Now you are set to try a 3 button update (sometimes it gets stuck so if it's stuck for 15 minutes, try 3 button again)."
I gotta do that myself with an "update.app" file or what?
Sorry, I missed that part
Cheers!
joaomPT said:
Alright, btw, about the thing you said
"Now you are set to try a 3 button update (sometimes it gets stuck so if it's stuck for 15 minutes, try 3 button again)."
I gotta do that myself with an "update.app" file or what?
Sorry, I missed that part
Cheers!
Click to expand...
Click to collapse
You have to make a dload folder in SD card and copy UPDATE.APP to that folder.
Then just turn off the phone, press and hold power + vol up + vol down until phone boots.
Let go of power but keep others two pressed for 5, 6 sec more. Your phone will boot into recovery and start installing UPDATE.APP
It likes to get stuck at 5% (most reports) but sometimes, somewhere else. If its stuck for 15 minutes on a particular percentage, just press and hold the above three buttons again using the same process.
Multiple tries make it work...
Sent from my PLK-L01 using XDA Labs
muradulislam said:
You have to make a dload folder in SD card and copy UPDATE.APP to that folder.
Then just turn off the phone, press and hold power + vol up + vol down until phone boots.
Let go of power but keep others two pressed for 5, 6 sec more. Your phone will boot into recovery and start installing UPDATE.APP
It likes to get stuck at 5% (most reports) but sometimes, somewhere else. If its stuck for 15 minutes on a particular percentage, just press and hold the above three buttons again using the same process.
Multiple tries make it work...
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
Hey man!
Good news, my phone is alive and root is done.
The problem was on the SuperSU that I flashed, it was version 2.71, instead of the one you said » version 2.62 «
I cant thank you enough!! Can I pay you a coffee?
Thank you!
joaomPT said:
Hey man!
Good news, my phone is alive and root is done.
The problem was on the SuperSU that I flashed, it was version 2.71, instead of the one you said �?�» version 2.62 �?�«
I cant thank you enough!! Can I pay you a coffee?
Thank you!
Click to expand...
Click to collapse
That's great... Enjoy your phone and as for coffee, well, let's say, you owe me one and we will leave it at that
Better yet, you can search DigiGoon and pay him for the coffee, he taught me what I told you.
You can find him somewhere in this thread
http://forum.xda-developers.com/honor-5x/help/honor-5x-kiw-ul00-boot-loop-t3449554/page1
Decision is yours
muradulislam said:
That's great... Enjoy your phone and as for coffee, well, let's say, you owe me one and we will leave it at that
Better yet, you can search DigiGoon and pay him for the coffee, he taught me what I told you.
Whichever you like...
Click to expand...
Click to collapse
Alright man, cheers
joaomPT said:
Alright man, cheers
Click to expand...
Click to collapse
Hello
How did you format your phone?
I'm still struggling with going back to Android 5 and EMUI 3.1 since there is no rollback file available. (PLK-AL10, B396) Maybe formatting and installing the old rom could be a solution, like in your case?
tgergo said:
Hello
How did you format your phone?
I'm still struggling with going back to Android 5 and EMUI 3.1 since there is no rollback file available. (PLK-AL10, B396) Maybe formatting and installing the old rom could be a solution, like in your case?
Click to expand...
Click to collapse
Hello.
Do you have unlocked bootloader and TWRP recovery? You can format your phone from TWRP recovery.
I think the only option for you is to get the old ROM img and flash it (starting from 0)
You can dirty-flash (Flash a different ROM with same android version as yours, e.g: flashing custom android 5 ROM over your stock android 5 ROM without factory resetting your phone) but I dont think you can do that from Android 6 to 5.
joaomPT said:
Hello.
Do you have unlocked bootloader and TWRP recovery? You can format your phone from TWRP recovery.
I think the only option for you is to get the old ROM img and flash it (starting from 0)
You can dirty-flash (Flash a different ROM with same android version as yours, e.g: flashing custom android 5 ROM over your stock android 5 ROM without factory resetting your phone) but I dont think you can do that from Android 6 to 5.
Click to expand...
Click to collapse
Yes I have unlocked bootloader and currently not twrp but I can flash it at any time.
The last two paragraphs you wrote are different solutions or the last one is a more detailed explanation of the previous?
I have android 6 so the later method won't work as you said.
But formatting it and flashing a stock android 5 rom - is it that simple? Nobody here suggested this before, however I have been asking for months.
All the phones are empty when they leave the assembly line.
How did you flash the new rom to your formatted phone? Extracted update.app and flashed each file with fastboot? Any issues you faced?
tgergo said:
Yes I have unlocked bootloader and currently not twrp but I can flash it at any time.
The last two paragraphs you wrote are different solutions or the last one is a more detailed explanation of the previous?
I have android 6 so the later method won't work as you said.
But formatting it and flashing a stock android 5 rom - is it that simple? Nobody here suggested this before, however I have been asking for months.
All the phones are empty when they leave the assembly line.
How did you flash the new rom to your formatted phone? Extracted update.app and flashed each file with fastboot? Any issues you faced?
Click to expand...
Click to collapse
From my last 2 paragraphs, the first was a solution, the second was an impossible alternative that I thought it would work.
My issue was that I had a custom recovery but I had no ROM installed, so I had to install the stock recovery and boot (extracting from update.app) and flashing it via fastboot, to afterwards force the update with 3-button method.
-----
What you'll need to do is:
- Flash TWRP
- Wype system, data, cache.. (so that you completely delete your current ROM)
- Extract recovery.img and boot.img from an update.app of an Android 5 ROM you'd like to have (Official ROM for your device model)
- Flash them via fastboot (You'll go back to stock recovery again)
- Shutdown your device
- Create a folder named "dload" on your sdcard and put UPDATE.APP file in it.
- Reboot
- Do the 3-Button update ([Vol+] + [Vol-] + Power)
- If it works, it will auto install
(- If it gets stuck on 5% for over 5/10min, force reboot pressing [Vol+] + Power) and try again the installation
- After installing it will boot normally (first boot takes a while)
NOTE: I'd recommend creading the dload folder before wiping the ROM, because usb didnt work for me afterwards. (It would still work if I was on recovery tho)
>> Remember to make a full system backup before wiping aswell, dont be stupid like me xD (thats why I had to full wipe my system after soft-brick)
Im answering based on what I did and was explained here to me
joaomPT said:
From my last 2 paragraphs, the first was a solution, the second was an impossible alternative that I thought it would work.
My issue was that I had a custom recovery but I had no ROM installed, so I had to install the stock recovery and boot (extracting from update.app) and flashing it via fastboot, to afterwards force the update with 3-button method.
-----
What you'll need to do is:
- Flash TWRP
- Wype system, data, cache.. (so that you completely delete your current ROM)
- Extract recovery.img and boot.img from an update.app of an Android 5 ROM you'd like to have (Official ROM for your device model)
- Flash them via fastboot (You'll go back to stock recovery again)
- Shutdown your device
- Create a folder named "dload" on your sdcard and put UPDATE.APP file in it.
- Reboot
- Do the 3-Button update ([Vol+] + [Vol-] + Power)
- If it works, it will auto install
(- If it gets stuck on 5% for over 5/10min, force reboot pressing [Vol+] + Power) and try again the installation
- After installing it will boot normally (first boot takes a while)
NOTE: I'd recommend creading the dload folder before wiping the ROM, because usb didnt work for me afterwards. (It would still work if I was on recovery tho)
>> Remember to make a full system backup before wiping aswell, dont be stupid like me xD (thats why I had to full wipe my system after soft-brick)
Im answering based on what I did and was explained here to me
Click to expand...
Click to collapse
I'll try... But seems too simple to be true...
joaomPT said:
From my last 2 paragraphs, the first was a solution, the second was an impossible alternative that I thought it would work.
My issue was that I had a custom recovery but I had no ROM installed, so I had to install the stock recovery and boot (extracting from update.app) and flashing it via fastboot, to afterwards force the update with 3-button method.
-----
What you'll need to do is:
- Flash TWRP
- Wype system, data, cache.. (so that you completely delete your current ROM)
- Extract recovery.img and boot.img from an update.app of an Android 5 ROM you'd like to have (Official ROM for your device model)
- Flash them via fastboot (You'll go back to stock recovery again)
- Shutdown your device
- Create a folder named "dload" on your sdcard and put UPDATE.APP file in it.
- Reboot
- Do the 3-Button update ([Vol+] + [Vol-] + Power)
- If it works, it will auto install
(- If it gets stuck on 5% for over 5/10min, force reboot pressing [Vol+] + Power) and try again the installation
- After installing it will boot normally (first boot takes a while)
NOTE: I'd recommend creading the dload folder before wiping the ROM, because usb didnt work for me afterwards. (It would still work if I was on recovery tho)
>> Remember to make a full system backup before wiping aswell, dont be stupid like me xD (thats why I had to full wipe my system after soft-brick)
Im answering based on what I did and was explained here to me
Click to expand...
Click to collapse
Hi again,
I'm doing this OS installation now. It starts fine but stucks at 90%, (I'm trying to install the latest stock ROM which can be downloaded from Huawei site, B220 or221). Did you have the same issue? I waited more than half an hour at 90% but did not go on.
tgergo said:
Hello
How did you format your phone?
I'm still struggling with going back to Android 5 and EMUI 3.1 since there is no rollback file available. (PLK-AL10, B396) Maybe formatting and installing the old rom could be a solution, like in your case?
Click to expand...
Click to collapse
Maybe formatting, Flash stock Android 5 recovery using Honor multitool , and then Flash a Android 5 firmware
Not sure it Will Work without rollback..
Finally, after 2 months of struggling I managed to get back to Android 5 and EMUI 3.1 without a rollback file.
Here is what I did:
0. Download a full ROM you want to install
1. Backup of the current system with Hisuite (everything. Apps, media, contacts, call log, etc.)
2. Flash TWRP recovery with fastboot (start phone in fastboot mode)
3. Wipe (and format!) everything you can with TWRP
4. Extract boot.img and recovery.img from update.app of the new ROM with Huawei Update Extractor
5. Flash boot.img and recovery.img with fastboot.
6. Copy update app to dload folder on SD card, insert into the phone.
7. Restart phone with [VOL+] + [VOL-] + [Power] buttons to force update.
8. The system will be installed from SD card. I had no issues with the installation. First I did not format the phone (just wiped) and it did not work.
9. Restore data from backup.
The only strange thing is that the native app icons look different than my previous lollipop system. Don't know why. They are less colorful. I installed C00B220 for PLK-AL10.
tgergo said:
Finally, after 2 months of struggling I managed to get back to Android 5 and EMUI 3.1 without a rollback file.
Here is what I did:
0. Download a full ROM you want to install
1. Backup of the current system with Hisuite (everything. Apps, media, contacts, call log, etc.)
2. Flash TWRP recovery with fastboot (start phone in fastboot mode)
3. Wipe (and format!) everything you can with TWRP
4. Extract boot.img and recovery.img from update.app of the new ROM with Huawei Update Extractor
5. Flash boot.img and recovery.img with fastboot.
6. Copy update app to dload folder on SD card, insert into the phone.
7. Restart phone with [VOL+] + [VOL-] + [Power] buttons to force update.
8. The system will be installed from SD card. I had no issues with the installation. First I did not format the phone (just wiped) and it did not work.
9. Restore data from backup.
The only strange thing is that the native app icons look different than my previous lollipop system. Don't know why. They are less colorful. I installed C00B220 for PLK-AL10.
Click to expand...
Click to collapse
Is this really work? i cant rollback to any version.
Yuaru said:
Is this really work? i cant rollback to any version.
Click to expand...
Click to collapse
Yes it does. (It did for me.) Technically this is not a rollback but installing a brand new system on an empty phone. That's why it is important to do a backup upfront.
tgergo said:
Yes it does. (It did for me.) Technically this is not a rollback but installing a brand new system on an empty phone. That's why it is important to do a backup upfront.
Click to expand...
Click to collapse
Thanks for the answer. Im gonna try this method. I can't reflash any region rom.
My attempt to root my H930 went very wrong... So I started by unlocking the bootloader and flashing TWRP. After that I didn't manage to get in to TWRP. Instead it started to boot, but froze eventually. Now I can't get it to boot (It gets stuck on initial LG V30 screen), and I can't power it off. I can get into stock recovery (apparently it got far enough to replace TWRP) and download mode with hardware button combinations. But the download mode seems to be different from fastboot mode (looks different on phone, and fastboot can't find it) so I can't try to flash TWRP again. I also managed to get it into a check IMEI + S/N mode by holding all buttons at once...
I've tried flashing H93010f_00_OPEN_EU_OP_0925.kdz with LG UP/Uppercut (since I can get to download mode). It went fine but the situation is the same - no boot, no way to power off.
A factory reset from stock recovery doesn't help either.
Please advice..
Alright, I acually got in to fastboot mode even though I'm not quite sure how.. I basically first went in to download mode, and then pressed vol down + power to reboot, and ended up in fastboot mode. From there I flashed twrp again. And this time I managed to get in to TWRP. Since I didn't have a working ROM I went ahead and wiped all but external sdcard and tried flashing Boombox. It resulted in an "Error: 1"..
So I tried flashing H93010f_00_OPEN_EU_OP_0925.kdz from LGUP again, and now I'm back to a device that doesn't boot again.
Which root are you trying to flash? TWRP also is in alpha at the very best at this point. Can you extract the KDZ and use fastboot to flash the .img files inside, assuming they have .img files inside of the KDZ?
jcsww said:
Which root are you trying to flash? TWRP also is in alpha at the very best at this point. Can you extract the KDZ and use fastboot to flash the .img files inside, assuming they have .img files inside of the KDZ?
Click to expand...
Click to collapse
I'm not trying to flash any root. I was planning on flashing Magisk but never got that far. At this point I'm just trying to get a working phone. I read about extracing img files from kdz but the tool didn't work in my virtual WinXP machine so I'm trying to fire up a Win10 machine now (I'm on mac).
Meanwhile I tried flashing boot and system from "LGH930GAT-00-V10c-222-01-OCT-12-2017+0.zip" but that resulted in the phone automatically booting into TWRP... That can't be good.
egendomligt said:
I'm not trying to flash any root. I was planning on flashing Magisk but never got that far. At this point I'm just trying to get a working phone. I read about extracing img files from kdz but the tool didn't work in my virtual WinXP machine so I'm trying to fire up a Win10 machine now (I'm on mac).
Meanwhile I tried flashing boot and system from "LGH930GAT-00-V10c-222-01-OCT-12-2017+0.zip" but that resulted in the phone automatically booting into TWRP... That can't be good.
Click to expand...
Click to collapse
With some other phones, like Nexus devices. Flashing older boot images can cause bootloops. I don't know if this is the case with your device but it might be something to consider. Have you tried flashing the complete latest factory image to see if that solves the bootloop?
jcsww said:
With some other phones, like Nexus devices. Flashing older boot images can cause bootloops. I don't know if this is the case with your device but it might be something to consider. Have you tried flashing the complete latest factory image to see if that solves the bootloop?
Click to expand...
Click to collapse
Unfortunately I haven't been able to get able to get a hold of a KDZ other than for 10f. I'd like to try 10v.
I got the extraction tool working in a Win10 box now, and I'm trying to extract boot and system images from the 10f KDZ...
egendomligt said:
Unfortunately I haven't been able to get able to get a hold of a KDZ other than for 10f. I'd like to try 10v.
I got the extraction tool working in a Win10 box now, and I'm trying to extract boot and system images from the 10f KDZ...
Click to expand...
Click to collapse
Best of luck!
Nope, that didn't work either. fastboot threw an error telling me the system image was too big for the partition.. At least the system image from the 10c dump fit properly..
So I guess my best bets right now are to either get a hold of a 10v KDZ, or wait for something flashable through TWRP.. :/
Is there like a lastlog for system boot that would be reachable from TWRP/adb..? It would sure be nice to see whats going wrong...
egendomligt said:
Nope, that didn't work either. fastboot threw an error telling me the system image was too big for the partition.. At least the system image from the 10c dump fit properly..
So I guess my best bets right now are to either get a hold of a 10v KDZ, or wait for something flashable through TWRP.. :/
Is there like a lastlog for system boot that would be reachable from TWRP/adb..? It would sure be nice to see whats going wrong...
Click to expand...
Click to collapse
No clue!
Ok, I got it to boot again!
* I formatted data (not wiped) inTWRP - Not sure if this step was relevant
* Flashed stock recovery/boot/system from a KDZ dump called "LGH930GAT-00-V10c-222-01-OCT-12-2017+0" - found the link in some other thread here
* Rebooted and watched it boot - went in to "Android is upgrading..."-screen - rebooted - then booted normally.
Thanks for the help and a special thanks to @Perkash who helped me out through PM.
Hi all,
I went ahead and rooted my Mate 10 Pro today - I unlocked my bootloader, installed TWRP and got it running pretty sweet. Then, like a tool - tried installing xposed framework and got myself into a boot loop.
I can get to fastboot, I can get into twrp - but for the life of me don't know how to get a system wipe and fresh format! I've tried flashing LineageOS - but that's stuck on a loading screen and then boot loops after about 10minutes.
What happens is I turn my phone on - see the bootloader message - if I do nothing there's a 50/50 changes Huawei's eRecovery window opens (where if i connect it to the wifi, it fails and gives me the option of reboot or shutdown) or LineageOS boot animation loops for about 10minutes before shutting down.
At this stage, I don't mind what rom i get working - i just want something working and I'm really regretting xposed (I should of googled!).
I really don't want to pay $40 usd - and am happy tinkering around, but would appreciate some solid advice on how I can use TWRP to wipe everything and start again!
I'm also a little confused as to why eRecovery is coming up at all - and why it can't download anything!!!!!
Can someone help me get a phone back?
Thanks!
Yeah, I bootlooped going with xposed too, but I have the Mate 10 (regular) and no TWRP. Can you get to TWRP and simply flash a clean ROM? If not, which I presume is the case, can you get to Fastboot? To try, when you get to the eRecovery window, use the option to shut down your phone. Then press the power button and, while holding it, plus in your USB cable (the other end which should already be attached to your computer). Then go to Mankindtw's thread for flashing ROMs (Mate 10 Flash Oreo one). Basically, you download three zip files from a russian language page with all the latest Huawei ROMs, repackage them within his utility, and then flash them from within his utility. Worked for me.
download update.zip (for your firmware) from http://pro-teammt.ru/firmware-database
Extract update.app from update.zip
Download Huawei Update Extractor (open it and go to settings and disable header check)
Open update.app in Huawei Update Extractor
Extract SYSTEM from update.app using Huawei Update Extractor.
(Not sure if Xposed modifies vendor too, so you might have to extract that as well)
Fastboot flash system system.img
See if it boots now. If not you could try extracting recovery_ramdisk and flash recovery_ramdisk.img to the recovery_ramdisk partition then factory reset from stock recovery.
If it does modify vendor you'd have to flash vendor as well.
Or you could try flashing lineage os system, flash recovery_ramdisk and factory reset from stock recovery (factory reset is needed to get aosp roms running)
If it still fails, use mankindtws HWOTA as described by rogerinnyc above. (link: https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814)
Stock rom seems to be installing. TY for your help
Toldorn said:
The problem I'm having now is, on my win7 and win10 pc's - when I enter fastboot, neither PC will accept drivers for it and therefore, I can't fastboot flash anything.
I just get '<waiting for device>' even when plugged in (and windows 'driver no successful' message)
Is there a way to transfer the files via twrp adb sideload?
Click to expand...
Click to collapse
Sadly no, this corresponds to reflashing the whole phone, block by block.
have you tried to find matching drivers ? (it should be pretty easy on windows 10 normally...)
Toldorn said:
The problem I'm having now is, on my win7 and win10 pc's - when I enter fastboot, neither PC will accept drivers for it and therefore, I can't fastboot flash anything.
I just get '<waiting for device>' even when plugged in (and windows 'driver no successful' message)
Is there a way to transfer the files via twrp adb sideload?
Click to expand...
Click to collapse
ChriKn said:
Sadly no, this corresponds to reflashing the whole phone, block by block.
have you tried to find matching drivers ? (it should be pretty easy on windows 10 normally...)
Click to expand...
Click to collapse
Install this regfix https://www.dc-unlocker.com/huawei-mate-10-fastboot-usb-device-not-recognised-fix
However, you would probably have had problems before too when flashing twrp.
But worth a shot I guess.
Didn't see it said you tried on win 7 too.
And if it worked before on Win 10 it should work without it.
I guess you could push system.img to /data/system.img then tap Install and selectInternal storage, tap on (go up one level) in browser, now you'll be at /. Tap on /data and then on system.img. Flash to 'System Image'.
Edit: I've tested with recovery and that flashes fine from /data/.
please see below;
Hi all. My SDCARD was encrypted in TWRP, so I googled and saw I should run this command;
recovery --wipe_data --set_filesystem_encryption=off
Which I did on TWRP terminal - and now im boot looping again. I tried fastboot system.img and it's still bootloading. I see there's supposed to be a 'boot.img' in my update.app, but there isn't.
Any ideas?
Toldorn said:
Hi all. My SDCARD was encrypted in TWRP, so I googled and saw I should run this command;
recovery --wipe_data --set_filesystem_encryption=off
Which I did on TWRP terminal - and now im boot looping again. I tried fastboot system.img and it's still bootloading. I see there's supposed to be a 'boot.img' in my update.app, but there isn't.
Any ideas?
Click to expand...
Click to collapse
Boot.img is for Nougat. Oreo uses ramdisk.
Try wiping data in TWRP (Wipe - Format Data).
You can't turn off encryption in TWRP. It's controlled by /vendor/etc/*.fstab (* = kirin970 in this case). (You can temporarily turn off encryption but it re-encrypts after booting if fstab is untouched)
But removing encryption won't fix you bootlooping, and that command you used is for Full disk encryption, we use file based encryption.
You could also try flashing back stock recovery and do factory reset from there.
Edit: Oh, you're the guy who PM'd me
I've reflashed my 'system.img' as before - but im having trouble getting into factory reset menu.
all it ever does is go into e'Recovery instead, which is useless.
Also, my booting image is still a green page of pixels - rather than a huawei logo.
Hi. I have a bla-a09 and need help. can boot into twrp but will not boot.
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 ?????