Related
My colleague brought his stock A500 to me in a bricked condition last week.
I need a way to restore it. If I try to do a wipe it will say bootloader error if i try the recovery the droid falls down with the red sign with the exclamation mark.
This tablet has never been rooted, my colleague is not in to such things, it's lived its life with ordinary acer otas and the occational very young human (5 year old) trial wich it has survived.
He has installed all the OTAs he ever got on the tablet and this is in Sweden so it would probably be a 4.0.3 acer stock on it now.
I'm guessing it has died during a OTA or something. if i turn it on it will sit at the acer logo indefinitly.
I Bricked my A500 during a rooting atempt resulting in me needed to flash a stock rom to get it working again, but i cant find the thread i read to un-brick my A500.
Please Help!
try this http://forum.xda-developers.com/showthread.php?t=1839313
dibb_nz wrote:
try this http://forum.xda-developers.com/showthread.php?t=1839313
Click to expand...
Click to collapse
Well that thread seems to hold all i need, although i can't do a full wipe. when i do the flipswitch wipe procedure it halts with bootloader error
Im hoping to just be able to flash the stock rom from the link you gave me. Is it entirely necessary to do the wipe prior to flash? can i wipe it afterwards?
Hogbola said:
Well that thread seems to hold all i need, although i can't do a full wipe. when i do the flipswitch wipe procedure it halts with bootloader error
Im hoping to just be able to flash the stock rom from the link you gave me. Is it entirely necessary to do the wipe prior to flash? can i wipe it afterwards?
Click to expand...
Click to collapse
we're assuming the tab is full stock and currently on ICS...
and we're assuming he never tried to 'fix' his tab by flashing one thing or another...
the bootloader error worries me...what exactly does it say...
Yes the wipes are really important!! and not being able to use the button method to do so is concerning...
what happens with the Over The Air (OTA) updates is its just that...an update...it leaves all your settings/data intact. When you OTA from one build to another, like Gingerbread 3.0 to Honeycomb 3.1/2 and then to ICS 4.0 - you drag all your apps and settings with you and of course some things that work with 3.2 will not work under ICS....fjor instance, lots of folk had trouble with wifi disconnects, once they got to ICS - or they had apps force closing and other 'glitches'. This is why everyone tells you to do the wipes - as this fixes these things! In the case of stock ICS my gmail would f/c all the time no matter how many times I wiped/formatted....So for a smooth running tab - flash a custom rom!!!!!!
But getting back to you...
From that link i gave you...download the 3.1_Full.zip....its decrypted so just extract it and get the "update.zip" from it..
This "update.zip" is not an incremental "update" but the full stock rom....
once installed you'll be on GB you will need to root it with iconia root and then use acer recovery installer to flash cwm....(get these from the playstore)
do a backup or adb devices so you can get your CPUID....this is important...if anything goes wrong at any stage this is the only thing that will get you unbricked....see the cpuid link in my sig for more on this, please take the time to read it, even if it doesnt make much sense to you, read it anyway....
AFTER you have retrieved your cpuid, you can nvflash the patched bootloader/recovery pkg which means you are able to flash ICS/JB custom roms
they cannot be flashed via cwm like normal...you must use nvFlash to do it....
OR
take the OTA route to ICS...this takes a bit of time...I did it last week and it was a good 6-7 hours to go from GB to ICS
there are pre-rooted stock roms if you wanna stay stock see civato's stock rom thread for that here http://forum.xda-developers.com/showthread.php?t=1633907
official stock rom list by blackthund3r are here http://forum.xda-developers.com/showthread.php?t=1816560
civs guide to flashing the unlocked bootloader here http://forum.xda-developers.com/showthread.php?t=1622425
I am in a similar situation. Push the power button and it goes to a screen with white acer on black and stays there. Totally stock ICS, no root. I tried the update.zip thing and after automatically rebooting it says "Boot verified failed...". I don't have my cpuid, or have installed previously CWM or anything like that. I can get into APX mode. This guy here: http://forum.xda-developers.com/showthread.php?t=1751978 could only get into APX with no cpuid as well, but i don't understand all of the ubuntuu and command line stuff. I would love for someone to be able to walk a dummy like me through this mess. Thanks for any help.
if u got boot verified fail error you need nvFlash to repair that....as u know, with nvflash you need yr cpuid....wot about usbdeview? if you've never plugged yr tab into yr PC - then it won't work and the ONLY other way is Linux....
might be best to start yr own thread with a descriptive title, not just a help I'm bricked no uid, thread there are hundreds of those....the more effort u put into the title the more likely you will attract the attention of someone who can actually help...and remember you just don't need a bit of help but a blow by blow description of what to do and how....this will be very time consuming....at the very least get ubuntu installed, maybe just try a few things, anything to show you are capable of at least giving it a go yourself..
there are others who would like 2 know how to do this as well...having a specific thread of its own would be great
good luck
dibb
Sent from my GT-I9300 using Tapatalk 2
Actually, I have connected it to my PC before. Only for transferring media though. If I've done that, is the some way to retrieve my cpuid from the PC?
yup...usbdeview.zip see the bottom of the OP in the cpuid guide in my sig
Thanks alot for your help. I used usbdeview and got my cpuid. Now I should use nvflash? Know where a good step by step is for that one?
you could try the one in my sig??
dibb_nz said:
you could try the one in my sig??
Click to expand...
Click to collapse
Right. Sorry, I didn't notice that before. Thanks again for your direction.
"To install one of these roms you will need a custom recovery and to get that you must flash the patched bootloader FIRSt - once its patched you can install a recovery any old way you like"
Looking at that guide, would you please tell me what a custom recovery is and how to get one? Btw, I don't plan to do a custom ROM yet, I just want to get the damn thing working first. Was thinking of using the HC EUUs from the firmware files list. However there are two files, a .rar and a .exe listed. Which do i use?
NvigR8 said:
Right. Sorry, I didn't notice that before. Thanks again for your direction.
"To install one of these roms you will need a custom recovery and to get that you must flash the patched bootloader FIRSt - once its patched you can install a recovery any old way you like"
Looking at that guide, would you please tell me what a custom recovery is and how to get one? Btw, I don't plan to do a custom ROM yet, I just want to get the damn thing working first. Was thinking of using the HC EUUs from the firmware files list. However there are two files, a .rar and a .exe listed. Which do i use?
Click to expand...
Click to collapse
The .rar EUU is for an A500, the .exe is for the A501, which do you have?
I've got the a500. However, I decided to go with a custom ICS rom after all. I managed to put a new bootloader and custom recovery on using the a500apx flash tool. That part went fine. I flashed this rom:
Acer_AV041_A500_1.054.00_WW_GEN1-FULL-ROOT (original odex)
and that appeared to go well according to twrp, but after rebooting, it just shows the bootloader again and stops there. Not sure what i did wrong.
I renamed the rom update.zip. Should i not have done that?
well congrats for getting thru the flash process with no probs!!!
as far as renaming to update.zip that was not such a good move...hopefully things havent been screwed up too much
just go back into recovery and do a FULL wipe/format
then to flash use the option "install from zip file" not sure where that is in TWRP but it will have one
Okay. I will reflash the rom after completely wiping again. Thanks.
On a different note, why do roms require particular bootloaders?
Also different, how do you like your SGS3? If i can manage to fix this thing, perhaps I'll root my phone...
NvigR8 said:
Okay. I will reflash the rom after completely wiping again. Thanks.
On a different note, why do roms require particular bootloaders?
Click to expand...
Click to collapse
The stock ICS BL is encrypted - more or less - the only way to 'flash' a recovery or rom is to have the "key" that "unlocks" - it more or less - if you dont use the right key then the OS will not boot - the 'key' is based on your cpuid which is why everyone is forever telling you to save it somewhere safe....
Also different, how do you like your SGS3? If i can manage to fix this thing, perhaps I'll root my phone...
Click to expand...
Click to collapse
I enjoy the big screen, took awhile to get used to it in my hand, kept dropping it....then I ran it over with my 44tonne truck after 3 days and munted it!!!!
I have a case for it now, and its gr8 - I havent installed a rom on it yet...the forums over there are jampacked and I have no idea what I'm doing, lol - its the first android device I've had that I've left stock for so long...but it does what I want...the camera is awesome -burst mode is the bomb - BUT do I think it was worth the money???? Still on the fence about that one.....
Ouch. Sorry to read about running over your phone. That would kill me. I really like my SGS3. I think I'll look into rooting it just to be able to back it up and get rid of the bloatware. I did that on my Captivate and prior to today, thats all I've ever done modding wise to an android device.
So, I managed to get my tab up and running again. Yay! I reflashed the rom w/out changing the name and worked like a charm. Now If only I knew why this happened in the first place... Thanks for all your help.
NvigR8 said:
Ouch. Sorry to read about running over your phone. That would kill me. I really like my SGS3. I think I'll look into rooting it just to be able to back it up and get rid of the bloatware. I did that on my Captivate and prior to today, thats all I've ever done modding wise to an android device.
So, I managed to get my tab up and running again. Yay! I reflashed the rom w/out changing the name and worked like a charm. Now If only I knew why this happened in the first place... Thanks for all your help.
Click to expand...
Click to collapse
yeh sometimes happens with the tab for some reason - thank your lucky stars it didn't get stuck in apx mode...if that happens its normally a hardware fault so theres not alot u can do...I'm just pleased you got sorted without too much drama and it was as easy as reflashing the zip....so now you have the v8 BL - you're gold!!!
dibb_nz said:
we're assuming the tab is full stock and currently on ICS...
and we're assuming he never tried to 'fix' his tab by flashing one thing or another...
the bootloader error worries me...what exactly does it say...
Yes the wipes are really important!! and not being able to use the button method to do so is concerning...
what happens with the Over The Air (OTA) updates is its just that...an update...it leaves all your settings/data intact. When you OTA from one build to another, like Gingerbread 3.0 to Honeycomb 3.1/2 and then to ICS 4.0 - you drag all your apps and settings with you and of course some things that work with 3.2 will not work under ICS....fjor instance, lots of folk had trouble with wifi disconnects, once they got to ICS - or they had apps force closing and other 'glitches'. This is why everyone tells you to do the wipes - as this fixes these things! In the case of stock ICS my gmail would f/c all the time no matter how many times I wiped/formatted....So for a smooth running tab - flash a custom rom!!!!!!
But getting back to you...
From that link i gave you...download the 3.1_Full.zip....its decrypted so just extract it and get the "update.zip" from it..
This "update.zip" is not an incremental "update" but the full stock rom....
once installed you'll be on GB you will need to root it with iconia root and then use acer recovery installer to flash cwm....(get these from the playstore)
do a backup or adb devices so you can get your CPUID....this is important...if anything goes wrong at any stage this is the only thing that will get you unbricked....see the cpuid link in my sig for more on this, please take the time to read it, even if it doesnt make much sense to you, read it anyway....
AFTER you have retrieved your cpuid, you can nvflash the patched bootloader/recovery pkg which means you are able to flash ICS/JB custom roms
they cannot be flashed via cwm like normal...you must use nvFlash to do it....
OR
take the OTA route to ICS...this takes a bit of time...I did it last week and it was a good 6-7 hours to go from GB to ICS
there are pre-rooted stock roms if you wanna stay stock see civato's stock rom thread for that here http://forum.xda-developers.com/showthread.php?t=1633907
official stock rom list by blackthund3r are here http://forum.xda-developers.com/showthread.php?t=1816560
civs guide to flashing the unlocked bootloader here http://forum.xda-developers.com/showthread.php?t=1622425
Click to expand...
Click to collapse
When i do the wipe it says
Code:
Erasing userdata...
Code:
Unrecoverable bootloader error (0x19000008)
Unrecoverable bootloader error (0x19000008)
Hogbola said:
When i do the wipe it says
Code:
Erasing userdata...
Code:
Click to expand...
Click to collapse
I googled your error - the consensus from what I read is a corrupt OS due to running OTA updates...
Some had luck with rebooting. Others had to send it to Acer.
Did you run the update.zip? so what happens when you run the update.zip
Are you able to get into "apx mode"? If you can, hook up to your PC and see if your tab is recognised as an "apx device" - check "Hardware, Printers in win7"
Thats all I can suggest atm - if your tab does get into apx mode OK then you can find your cpuid by running Linux -
Maybe ask the guy if he's ever had the tab hooked up to his PC like to transfer files and stuff - get him to download "USBdeview" to his PC -
this will show every single device thats ever been connected to the PC and it will show the "cpuid"...
Even if we do get the uid theres no guarantee it will fix the bootloader error - but we may as well explore all the options we can....
dibb_nz said:
USBDeview will only work when you have previously plugged your tab into the PC WHILE you were running HC Rom and BL
1. If you haven't plugged your tab into this pc before, do so now, before you run the program. HC ROM/BL ONLY
1a. Run the exe and you will be presented with a window of all the USB devices you have ever plugged into your computer.
2. Click on "VendorID" column along the top to sort them
3. Look for the number "0502" under Vendor ID AND "3325" Product ID
4. In the serial number column will be a 15-digit number this is your device ID.
5. Write the number down and put a 0 in front of it and now you have your CPU ID!!!
Click to expand...
Click to collapse
< include generic disclaimer here >
TL;DR
Since update 3.1, Nvidia can force updates (such as the one that bricks your tablet) to be downloaded and installed silently. No guarantees, but:
If you're on stock, delete TegraOTA (/system/app/TegraOTA or /system/priv-app/TegraOTA if you're on 5.0 or newer, or /system/app/TegraOTA.apk if you're still on 4.4) before booting into Android (the attached ZIP file does this for you, but please check with the file manager in recovery before rebooting and let me know if it didn't work), then reboot
Note: you also will need to delete TegraOTA again if you ever install an OTA from Nvidia or a recovery image
If you're not on stock, you're probably safe
EDIT: The urgent OTA is currently not getting sent out to any devices anymore, not even to those who have been getting it before.
EDIT 2: The urgent OTA is now being delivered again, this time named "ST - yy"!
What if my tablet is already deactivated?
Unless you can still boot into fastboot mode (in which case your tablet isn't really deactivated yet), your tablet is probably gone for good. The only way to fix this would be through nvflash, and using it requires the SBK that is unique to each device and that only Nvidia knows, so it's pretty unlikely that we'll ever be able to fix these deactivated tablets.
What/why/how?
In the last OTA (Update 3.1), Nvidia has made some changes to their TegraOTA application. The most important/interesting/suspicious of which is the ability for them to mark OTAs as "urgent". What this means is that these updates will be downloaded without ever notifying the user, and they will be installed without asking the user for permission first. If this is how the kill switch is delivered, all users will see is the tablet randomly rebooting and installing an update, then the tablet would never boot again. As some of you might notice, this would match what has been happening to a few users already, both here and on reddit.
But that's not all. I've been connecting to the OTA servers using various serial numbers (both found and provided to me by a few people) in hopes of actually finding the update that bricks the device. The first serial number I've tried that wasn't mine was the serial number from the screenshot on the recall page. It revealed an interesting "urgent" OTA, named "SHIELD Tablet xx - LTE", which does nothing but flash a blob (which, among other things, contains the bootloader). Many more questions appear now, but the main one is: if this is nothing but a routine bootloader update, why is it marked urgent? And why is it not attached to any Android update? But this by itself is not enough to prove anything, as I could only obtain it with one serial number, so as far as I could have known, it might had just been an internal update or something similar. (update is linked and analysed in the second post below)
Today, however, one of the serial numbers I've been given by some of the people here (thanks for the help guys!) turned out to have the same update waiting for it the next time it connected to the Internet. This rules out the possibility of an internal update, so the next somewhat obvious possibility is that this is the kill switch. Mind you, I still have no direct way of proving this without flashing the ZIP to see what happens (which I'm not planning to do myself), but I will keep checking on the other serial numbers I've gotten to see if this update turns up for them too.
The same person who has given me this serial number has also tested running the old tablet on the latest stock Android version but with TegraOTA removed, and, as expected, the tablet is still working perfectly fine now. Your mileage may vary.
How can I know if the kill switch has been triggered for my tablet?
Go to http://shield.bogdacutu.me/ and enter the full serial number of your old tablet. If the next OTA returned is "SHIELD Tablet xx" "ST - yy", the kill switch has been triggered for your tablet.
Warning: the serial number from the box of the tablet and the one etched on the side of the tablet are not complete, as they only contain the first 13 characters of the full (20 characters) serial number. You can get the full serial number from Android (Settings -> About -> Status), from the bootloader (it will be on the screen when you boot into bootloader mode), or from your computer if the tablet is or (in some cases) if it was previously connected, using various tools such as USBDeview. Example: 0413714803249000a4cf (you can try this on the page and it will return that the kill switch is activated).
Why would I want to also do the fix on my new tablet too?
The update is signed by Nvidia, and communication with the OTA server does not use HTTPS, so, for example, a malicious WiFi network could MITM your connection and cause this update (as well as any other signed update) to be flashed to your new tablet without your permission, thus permanently disabling it too. If you have the stock recovery, only updates signed by Nvidia can run. The story might be slightly different if your recovery doesn't enforce signature verification (such as TWRP and CWM by default).
Can I still get updates from Nvidia after doing this?
Not directly, but people will post OTA download links here on xda when new updates get released. I'd personally recommend that you wait before flashing though until someone here checks the new update to confirm that there's no new way for Nvidia to kill your tablet.
Many hours of work have gone into investigating this. Even if it doesn't help your specific scenario, consider hitting that Thanks button, so that I can at least know it wasn't for nothing.
I'd also like to thank the people who have given me their serial numbers to use for testing again, this wouldn't have been possible without their help: @Beauenheim, @Jackill, and @runandhide05 (who has even volunteered to test removing TegraOTA with the latest update on his old tablet :highfive
Fragments of code from TegraOTA.apk
< screenshots temporarily removed >
Also, from what I've seen so far, the update isn't delivered instantly after activating the new tablet. I don't know exactly what the rule is, but out of the 4 serial numbers that I have, only 2 have this update waiting for them.
EDIT: One more serial number from the ones I have has gotten the xx update. Only one left...
EDIT 2: All the serial numbers I have have the urgent OTA waiting for them now.
"SHIELD Tablet xx" - Update Analysis
OTA URL: http://ota.nvidia.com/ota/data/post...wf-full_ota-32256_554.0168.20150624152335.zip
yy OTA URL: http://ota.nvidia.com/ota/data/posted-roms/uploaded/st---yy--092704233775---7294.20150819152732.zip (if you don't know what you're doing, DO NOT DOWNLOAD THIS, it's very likely that this will permanently brick your device upon flashing it!!!) - also attached to this post in case this link becomes invalid
updater-script is the first file we check:
Code:
getprop("ro.product.device") == "shieldtablet" || abort("This package is for \"shieldtablet\" devices; this is a \"" + getprop("ro.product.device") + "\".");
nv_copy_blob_file("blob", "/staging");
reboot_now("/dev/block/platform/sdhci-tegra.3/by-name/MSC", "");
Suspiciously enough, this only flashes a blob to the staging partition. But what exactly does this blob do, you might ask? Well, the blob actually contains data for 9 partitions, which are automatically replaced during the next boot (before the bootloader does anything else at all, so once you've rebooted, there's no going back) with the contents present in this blob. The 9 partitions are as follows (also detailing comparison with files from update 3.1):
BCT (Boot Configuration Table) - stores some information that is needed for the device to find the bootloader stored on the other partitions, initialize the RAM and some other stuff
Status after update: probably corrupted - the previous OTAs have binary BCTs, but this update replaces it with a text file (which, while it does contain somewhat relevant information, is likely not a valid format). If this is corrupted, it's enough for the device not to be able to boot anymore.
BMP (boot logo) - intact
DTB - intact
EBT (part of the bootloader) - has a zeroed out region
NVC (part of the bootloader) - intact
RBL (part of the bootloader) - has a zeroed out region
RP4 (landscape boot logo) - intact
TOS (Trusted OS - probably part of the bootloader too) - has a zeroed out region
WB0 (related to the boot process, source file is named "nvbootwb0.bin") - has a zeroed out region
The update also contains a few other files, but those are not used at all (probably leftovers from the 5.1 AOSP update template that they are using).
DO NOT DOWNLOAD THE ATTACHMENT IF YOU DON'T KNOW WHAT YOU'RE DOING. THIS IS THE XX OTA, NOT THE ZIP THAT REMOVES TEGRAOTA!
Just as I suspected!!
Thanks a lot this is great. So the silent updater can force updating even with a custom recovery like cwm?
How to install the provided zip?
Thanks again.
tecnoworld said:
Thanks a lot this is great. So the silent updater can force updating even with a custom recovery like cwm?
How to install the provided zip?
Thanks again.
Click to expand...
Click to collapse
CWM and TWRP are both compatible with OTAs, so yes, it can. If you completely erase the recovery (fastboot erase recovery), the update can't get flashed, but the tablet will still reboot (which is at least annoying).
You can flash the provided ZIP through CWM or TWRP (but please check through the file manager if /system/app/TegraOTA still exists after installing it, the ZIP hasn't gone through a lot of testing so it might not work properly in all cases)
tecnoworld said:
Thanks a lot this is great. So the silent updater can force updating even with a custom recovery like cwm?
How to install the provided zip?
Thanks again.
Click to expand...
Click to collapse
This was to be my question too... Normal ota updates will not flash if you have a custom recovery, so how would this silent ota update?
bluegizmo83 said:
This was to be my question too... Normal ota updates will not flash if you have a custom recovery, so how would this silent ota update?
Click to expand...
Click to collapse
Normal OTAs don't work through custom recoveries because they do various checks that usually fail when you have a custom recovery (such as if the system partition is modified, by rooting for example), this urgent OTA has none of those checks
Bogdacutu said:
Normal OTAs don't work through custom recoveries because they do various checks that usually fail when you have a custom recovery (such as if the system partition is modified, by rooting for example), this urgent OTA has none of those checks
Click to expand...
Click to collapse
Oh ok! Great explaination. Thanks for all your hard work on this! I'm flashing the zip now, i'll report back if it removes the file
Edit: Ok I flashed the zip, and TegraOTA is gone. Now I will finally turn on my new tablet and set it up!
So out of interest, what do you think the chances are that thisll work?
How did you find out if the update is waiting? FYI I flashed the ZIP... All is good and it booted fine on LTE 32Gb...
Plus the deleting of the TegraOTA File has gone through... So you really think the TegraOTA removal has stopped it?
How do i check if i have downloaded randomly that update?
Great post. Hopefully that's as far as Nvidia is going to go. I flashed a custom rom on my old tablet. I'm keeping my new one stock but deleting the system app per your post. Just in case Nvidia is spiteful when I don't return the old tablet. I don't want to leave them any option of nuking the new one.
fkofilee said:
So out of interest, what do you think the chances are that thisll work?
How did you find out if the update is waiting? FYI I flashed the ZIP... All is good and it booted fine on LTE 32Gb...
Click to expand...
Click to collapse
Decompiled the OTA application. Using information from there I can connect to the OTA server directly from my PC, and request updates for any given serial number and Android version combination.
I wouldn't have posted this if I weren't relatively confident in my findings
Bogdacutu said:
Decompiled the OTA application. Using information from there I can connect to the OTA server directly from my PC, and request updates for any given serial number and Android version combination.
I wouldn't have posted this if I weren't relatively confident in my findings
Click to expand...
Click to collapse
I know fella I appreciate it. Could you check my second point? 2 x Nvidia Shields would be awesome! One for Work, One For Home
fkofilee said:
Plus the deleting of the TegraOTA File has gone through... So you really think the TegraOTA removal has stopped it?
How do i check if i have downloaded randomly that update?
Click to expand...
Click to collapse
Yes, I think it did. If that update was downloaded on your device, it would have been too late (as it reboots instantly after the update is downloaded), so I wouldn't worry about that.
Bogdacutu said:
Yes, I think it did. If that update was downloaded on your device, it would have been too late (as it reboots instantly after the update is downloaded), so I wouldn't worry about that.
Click to expand...
Click to collapse
So heres an interesting one for you, using a logical mindset, if you receive your new tablet, activate it, the next time that the old one connects to the network, it downloads this update and bricks it? But it wont technically do this until the new tablet is turned on?
fkofilee said:
So heres an interesting one for you, using a logical mindset, if you receive your new tablet, activate it, the next time that the old one connects to the network, it downloads this update and bricks it? But it wont technically do this until the new tablet is turned on?
Click to expand...
Click to collapse
As mentioned in the OP, the update doesn't get delivered immediately after you activate the new tablet. But yes, the old tablet shouldn't get the update before the new one is activated.
Bogdacutu said:
As mentioned in the first post, the update doesn't get delivered immediately after you activate the new tablet. But yes, the old tablet shouldn't get the update before the new one is activated.
Click to expand...
Click to collapse
Sorry fella missed that part, I will be donating some funds when i get paid later this month Mucho Gracias!
Totally not related to this thread, but I just went to setup my new tablet and it's not letting me restore apps & settings from my old Shield Tablet... It doesn't show my old tablet as a restore option. I doubt checked and the old tablet is setup to backup all settings and apps though. Anyone else have this issue when setting up they're new tablet?
bluegizmo83 said:
Totally not related to this thread, but I just went to setup my new tablet and it's not letting me restore apps & settings from my old Shield Tablet... It doesn't show my old tablet as a restore option. I doubt checked and the old tablet is setup to backup all settings and apps though. Anyone else have this issue when setting up they're new tablet?
Click to expand...
Click to collapse
Upgrade to 5.1 on the new tablet without restoring any data, then do a factory reset and you should get the option to restore
Bogdacutu said:
Upgrade to 5.1 on the new tablet without restoring any data, then do a factory reset and you should get the option to restore
Click to expand...
Click to collapse
AWESOME man, thank you!!
Preamble
Hello, all.
Soooo I've never posted on this forum before. I've mainly leeched the invaluable info for my personal gain. I'm sure many a googler has come here trying to figure out how to root their phone. And I'm sure many a "swimmer" in Schitz Creek has come here via Google to figure out how to save their device from what had been perceived as an upgrade. I'm speaking, of course, of trying to root/unlock a phone and finding said phone "bricked".
Well, it’s time to give back.
Because yesterday, I was neck deep in Schitz Creek. After a series of dumb decisions and a lack of knowledge, I bricked the phone I’d bought for my wife’s birthday. I was just trying to be able to delete the Asus bloatware and install titanium backup and greenify. By the way, since when did Facebook become a system app? How is this a thing? Anyways, my wife deserves better battery life. And it’s fun to feel like Cyber MacGuyver by rooting a phone. But the situation went awry. My wife kept telling me that everything was going to be alright, but I know the limitations of my knowledge.
Brief aside: I'm decently computer/phone savvy, but I would, in no way, consider myself an advanced user. Sure, to my family, I'm a computer wizard. But that doesn't mean a whole lot. To them, opening up a command prompt in Windows is seen as an act of magic. And I haven't had my planeswalker spark yet. However, I have successfully rooted, and in most cases unlocked the bootloader, for several phones (HTC desire, Galaxy S3 [three different models over three years], Asus Zenfone 5, LG G4 [once pre-motherboard-death and once post (after a downgrade)], and now the ZE552KL). So I know how to at least fumble my way around adb, fastboot, odin, and various recoveries. As long as you’re at this level, or willing to learn, then you should be able to follow these instructions. End aside.
Mistakes not to make
Let’s get down to brass tacks. I made two big mistakes that you shouldn’t make. Both mistakes stemmed from the basic mistake of using a root method other than this one: https://forum.xda-developers.com/zenfone-3/help/guide-how-to-root-zenfone-3-ze552kl-t3471524
The problem with not using this EXACT method is that some of the files/programs which you need to use have specific versions which will ensure an easypeasy root. Honestly, if you properly follow the instructions in the above post, you will most likely not run into any problems. The only addition I can make is that instead of steps 6 and 7, you might find it easier to install SuperSU.zip through TWRP instead of pushing and sideloading.
Mistake 1: Not using the proper TWRP file and SuperSU file
For some reason, there are multiple versions of these files. Your SuperSU file should be 4.8MB. Using the wrong SuperSU will break the dm-verity. Your TWRP should NOT be the latest experimental version. It should be the one from November or earlier of 2016. Using the wrong TWRP will leave you unable to use the touchscreen. Trust me. I know from experience.
Mistake 2: KEEP TWRP READ ONLY
Disabling read only has no current benefits. It will just break the dm-verity. Your device will still be able to be written to if you keep TWRP read only. I have no idea why it’s called “read only”.
How to unbrick the phone
I’m sure some of you skipped straight to here. While I can’t blame you, please at least read the above paragraph. It will help you.
First I will describe the situation the phone was in, and then I will explain how I saved it. Before I continue, I want to give a big shout out to Niemer. Without their helpful post, I would’ve had no idea what to do. Thanks!
Situation the phone was in
--TWRP could not be used because the touchscreen wasn’t working.
--The dm-verity was messed up (i.e. “not started in enforcing mode").
Before you look at the solutions, make sure that your phone shows up in the windows device manager as an ADB device/ASUS ADB device/ADB composite device/etc. no matter which step you’re in. Google it to figure out how if you don’t already know.
The solution
Part 1 - Create and flash a system image which will restore your dm-verity
step 1. download the latest system “update” from the asus drivers website. I have a WW version of the phone, so I downloaded “WW_V13.20.10.152”. It’s a 1.76GB file, so be patient. I haven’t tested this method with other versions of the phone, but they should work in theory.
step 2. go into the updater script file (META_INF → com → google → android → updater-script). Open it with notepad ++.
step 3. delete from the beginning of the file up until the line “ui_print("Target: asus/WW_Phone/ASUS_Z012D:6.0.1/MMB29P/13.20.10.152-20161222:user/release-keys");”
The code that you are deleting checks to make sure that your phone is the proper model. But there is a good chance that it will mistakenly identify your phone as a phony. So we need to get rid of this code.
step 4. save the updater-script file
step 5. create a copy of the modified system update zip file. You should now have two 1.76GB files (or maybe slightly different if your phone is a CN, JP, or other model. Once again, I have a WW version of the phone). Name one of the files “realupdate.zip” and name the other “dmsaver.zip”. The names aren’t actually important.
step 6. enter dmsaver.zip. delete these four files: file_contexts, system.new.dat, system.patch.dat, and system.transfer.list. Exit out of the file. It should now be about 60MB.
step 7. turn on your ZE552KL and enter fastboot mode
step 8. in a cmd screen from your main folder (i.e. the one with adb, fastboot, and all the other files, including the ones you just created), type in the command “fastboot flash system dmsaver.zip”
step 9. if successful, you have just restored the dm-verity. You should now no longer get that sinister red text which has been ruining all your fun.
Part 2 - Install a proper version of TWRP
(This is only important if your version of TWRP won’t let you do anything because you can’t use your touch screen)
Download the version of TWRP that is included in the how-to-root post I linked to above. Also, you can download the oldest version (NOT the newest) from a sharing website which is linked to in a post on the ASUS website. It’s not in english though. Flash it to your phone in fastboot mode using the “fastboot flash recovery” command. Make sure you turn your phone off before turning it back on, or your recovery might not activate correctly.
Part 3 - Install a new version of your system.
Go into TWRP and install the zip file “realupdate.zip” that you created in Part 1 - step 5.
Part 4 - Root your phone
Follow the instructions in the link I posted earlier. It comes from this website, so you know it’s good. This time, though, you probably don’t need to unlock the bootloader
Part 5 - Breathe a sigh of relief
Parting words
I really hope this guide can be of assistance to you. The full procedure for fixing “my” phone wasn’t really recorded anywhere (although once again, big shout out to Niemer for their post). I went through hundreds of iterations of seemingly random fastboot, recovery, and adb actions before everything worked out. Because of this, I feel quite fortunate to have saved the phone, and I really wanted to give back. This community has been super helpful to me over the last seven years, and this is my chance to reciprocate. I sincerely hope that this post will help you.
I hope I didn’t forget anything. I have a sneaking suspicion that I did. In any event, if you have any questions, please post them, and I’ll try to be of assistance. Happy rooting!
thank you man but i start Part1 step8 "fastboot flash system dmsaver.zip" it's successful then i go into TWRP and install the zip file “realupdate.zip” dm-verity show again.
Thank again.
Raw firmware
I have the same issue. My phone was branded "tim italy". When i bought it, I flashed the WW version via asus flash tool, and I'm currently able to update till the last M version, which is the ......152.
If i try to update to Android N, my phone will not boot, giving me the corruption message and shutting down after 10 seconds. I also tried to perform the dm restore procedure; the dm error disappeared but the system is stuck on the Asus boot screen
I believe that the only solution is to flash a Nougat RAW firmware via asus Flash tool. Does Anyone have a download link for the N version ?
thank you, you helped me, now im on N
I guess the version matters then. So be careful with which firmware you download/install. If anyone has success with other versions, please share how you did it
I am stuck on Step 8. i put the 2 zips in where my adb and fastboot is located, and then proceed to type 'fastboot flash system...' and then it wont let me flash, any help?
Device Locked
When I flash the dmsaver.zip, receive the error "FAILED (remote: not allowed in locked state)". Apparently this with the bootloader locked, but I already unlocked before. Someone can help me unlock the bootloader again?
Further hyperlinks & solution ideas
Check out my solution and Ideas in those in links I posted in this thread at 4th of septembre 2017:
https://forum.xda-developers.com/ze...-zenfone-3-zoom-ze553kl-t3657239#post73661437
The hyperlinks in my post might also be useful, I hope.
Would be glad about your feedback, if it helped! :good:
how do you update the script file ..can u just post the file that u made somehow or email it or attach it to a message?
cant get it to work followed the instructions still getinf error code 7 trying to install lineage os
If you have lineage OS version not is a zip file but all the images (boot.img, system.img, ...) then you could try to flash the images through ADB...
if someone have the no verity issue, can you try a method for me please?
it consists on:
re-flash the rom kernel via fastboot
and run:
Code:
fastboot oem reset-dm-verity
Followed all the steps and twrp still has no touch function.
Tried all different twrp versions.
OS Version is a key
Hi everybody that has the same issue, I hope you read that so you can fix your problem.
So what I did was downloading old version of OS that autor mentioned "WW-13.20.10.152". It is necessary to download this version even if there are more newer versions. Then follow tutorial and you should be fine.
So again, thanks OP for posting this. You helped me a lot!
Went to update "YB1-X90L_170420" and as I have been normally doing I removed root, ran the update, and all was well. It installed fine and worked no problem.
I was then prompted for update "YB1-X90F_USR_S000408_1704201342_WW06_BP_ROW_TO_YB1_X90F_USR_S000426_1705080316_WW06_BP_ROW" So I started the download and when the device reboots it then fails with this string, note the error about the "build fingerprint"
Supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Package expects build fingerprint of Lenovo/yeti_10_row_wifi/yeti:6.0.1/MMB29M/LenovoYB1-X90F_S000408_170420:user/release-keys or Lenovo/yeti_10_row_wifi/yeti:6.0.1/MMB29M/LenovoYB1-X90F_S000426_170508:user/release-keys; this device has Lenovo/yeti_10_row
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
I foolishly after some googling and not finding enough info opened a chat with Lenovo. The rep asked what the error was and once I showed it said that was just related to my fingerprint scanner .... really?!?!? I knew the chat was a dead spot at this point but tried to state this device has no fingerprint reader, etc.. and so on. Hope they could really tell me what the error was. Anyway the rep told me to 'ignore' the update and just carry on since my device is actually working. They then went on to state they are hardware only on the chat session, which the Lenovo site says nothing about that. They then also told me to take this up with Google as they make Android not Lenovo. So much for warranty helping anything but possibly replacing a physically broken device. Their techs are useless, seriously.
So anywho, as you see in the error the update is trying to apply but looks for "Lenovo/yeti_10_row_wifi" and is finding somewhere (in the update or my device?) "Lenovo/yeti_10_row", notice the missing "wifi" on the end of that. My 'build.prop' and other system files are untouched. I even tried resetting the device. Which after the reset I was able to once again install the "YB1-X90L_170420" update but this next update "YB1-X90F_USR_S000408_1704201342_WW06_BP_ROW_TO_YB1_X90F_USR_S000426_1705080316_WW06_BP_ROW" fails again on that same fingerprint mismatch.
Any clue what I should be looking for here? Has anyone else installed that update successfully?
Will anyone here supply me with the original (or as close as original) clean stock ROM without paying for it? I know I should have backed up with TWRP before I started doing updates, and this may well be my issue, but I didn't and not I can only restore back to an already rooted backup. Though I assume doing a reset of that rooted restore is considered clean (no root or 3rd party anything)?
thanks for any help or ideas!
MarkAllen said:
Went to update "YB1-X90L_170420" and as I have been normally doing I removed root, ran the update, and all was well. It installed fine and worked no problem.
I was then prompted for update "YB1-X90F_USR_S000408_1704201342_WW06_BP_ROW_TO_YB1_X90F_USR_S000426_1705080316_WW06_BP_ROW" So I started the download and it the device reboots then fails with this string, note the error about the "build fingerprint"
Supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Package expects build fingerprint of Lenovo/yeti_10_row_wifi/yeti:6.0.1/MMB29M/LenovoYB1-X90F_S000408_170420:user/release-keys or Lenovo/yeti_10_row_wifi/yeti:6.0.1/MMB29M/LenovoYB1-X90F_S000426_170508:user/release-keys; this device has Lenovo/yeti_10_row
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
I foolishly after some googling and not finding enough info opened a chat with Lenovo. The rep asked what the error was and once I showed it said that was just related to my fingerprint scanner .... really?!?!? I knew the chat was a dead spot at this point but tried to state this device has no fingerprint reader, etc.. and so on. Hope they could really tell me what the error was. Anyway the rep told me to 'ignore' the update and just carry on since my device is actually working. They then went on to state they are hardware only on the chat session, which the Lenovo site says nothing about that. They then also told me to take this up with Google as they make Android not Lenovo. So much for warranty helping anything but possibly replacing a physically broken device. Their techs are useless, seriously.
So anywho, as you see in the error the update is trying to apply but looks for "Lenovo/yeti_10_row_wifi" and is finding somewhere (in the update or my device?) "Lenovo/yeti_10_row", notice the missing "wifi" on the end of that. My 'build.prop' and other system files are untouched. I even tried resetting the device. Which after the reset I was able to once again install the "YB1-X90L_170420" update but this next update "YB1-X90F_USR_S000408_1704201342_WW06_BP_ROW_TO_YB1_X90F_USR_S000426_1705080316_WW06_BP_ROW" fails again on that same fingerprint mismatch.
Any clue what I should be looking for here? Has anyone else installed that update successfully?
Will anyone here supply me with the original (or as close as original) clean stock ROM without paying for it? I know I should have backed up with TWRP before I started doing updates, and this may well be my issue, but I didn't and not I can only restore back to an already rooted backup. Though I assume doing a reset of that rooted restore is considered clean (no root or 3rd party anything)?
thanks for any help or ideas!
Click to expand...
Click to collapse
From what i recall the fingerprint is what is shown in the buildprop. You could try editing this but i would tread carefully if its just a minor update as it may justmess up your system if there are other mismatches during the update process.
Lenovo technical support is a complete joke, you get much better help here. Lol
Sent from my F5121 using Tapatalk
Nope every line of my build.prop, where listed, has the proper "Lenovo/yeti_10_row_wifi" that the update claims is wrong. I personally think it is this update itself but no confirmation from other users if the update
"YB1-X90F_USR_S000408_1704201342_WW06_BP_ROW_TO_YB1_X90 F_USR_S000426_1705080316_WW06_BP_ROW"
has installed for them yet.
And I certainly knew how far I was *not* going to get with Lenovo but figured it couldn't hurt. I was really trying to get a stock ROM download from them or anywhere. I would love to just revert this to how it was out of the box and start over.
Well for reference I think I finally realize what is causing this (unconfirmed, but sounds feasible).
I did at one time try the "YB1-X90L_USR_S000155_1609272258_WW06_BP_ROW" noted in another thread here from Easy firmware. I figured since it was a free download and others have done it, what could it hurt? lol (I think I know now). Anyway I forget what it was at the time but something with that rom just wasn't right for me and I decided to restore back to my TWRP backup I had made. I'm assuming my backup doesn't overwrite something that "L" version rom did and leaves some residue that reports itself as the "L" model now?
Anyway that is the only thing to me that makes sense to me that could be happening. Of course I have no original stock rom with IMG files to flash again to fix this. :/
Can anyone here confirm Easy Firmware is safe to use? Can anyone confirm their YB1-X90F rom is really that models rom?
MarkAllen said:
Well for reference I think I finally realize what is causing this (unconfirmed, but sounds feasible).
I did at one time try the "YB1-X90L_USR_S000155_1609272258_WW06_BP_ROW" noted in another thread here from Easy firmware. I figured since it was a free download and others have done it, what could it hurt? lol (I think I know now). Anyway I forget what it was at the time but something with that rom just wasn't right for me and I decided to restore back to my TWRP backup I had made. I'm assuming my backup doesn't overwrite something that "L" version rom did and leaves some residue that reports itself as the "L" model now?
Anyway that is the only thing to me that makes sense to me that could be happening. Of course I have no original stock rom with IMG files to flash again to fix this. :/
Can anyone here confirm Easy Firmware is safe to use? Can anyone confirm their YB1-X90F rom is really that models rom?
Click to expand...
Click to collapse
Hi,
I registered for the free account. Had to email there support team to get it activate as there were problems their end. The 90F firmwares were not in the free tier so I paid the $15 through paypal to be safe, and got the 90F firmware fine. It was old and I had to run a lot of updates to get it up to date. But it got everything back to how it should be.
I blame Lenovo that we have to jump through theese hoops, but the files are legit.
Broomfundel said:
Hi,
I registered for the free account. Had to email there support team to get it activate as there were problems their end. The 90F firmwares were not in the free tier so I paid the $15 through paypal to be safe, and got the 90F firmware fine. It was old and I had to run a lot of updates to get it up to date. But it got everything back to how it should be.
I blame Lenovo that we have to jump through theese hoops, but the files are legit.
Click to expand...
Click to collapse
Thanks for that confirmation! I did end up getting a registered account ($15) used Paypal and all looked good. I ended up downloading two versions of firmware. Initially I thought I would start with the oldest knowing many updates awaited but really wanted to be sure in erasing all my previous steps just in case it didn't work or the same thing happened again.
Used "YB1-X90F_USR_S000036_1607280616_WW6_BP_ROW-flashfiles.zip" from Easy Firmware. I opted to follow the included "installer.cmd" but did not do the "unlock" or "lock" as I already was unlocked of course and did not want to lock it again. When it completed I first noted my Halo keyboard not working and things were in Chinese here and there. This post resolved both items (thanks vimalbhimani!). Pretty sure that was because I formatted all the various partitions including "country", duh. Sadly however this version was showing no further OTA updates were available at all. Maybe Lenovo has deleted some of the really old OTA downloads and they are no longer available? Not sure.
I then installed the most recent rom "YB1-X90F_USR_S000196_1611040312_WW06_BP_ROW-flashfiles.zip". This time I did not format and only flashed this newer roms boot, bootloader, factory, recovery, and system images. After the system was backup everything was in great shape and updates were available. I made a TWRP backup straight away. Then I let the first and second updates listed below download and install via OTA and had no issues. The final two I opted to save time and installed using the standard recovery from my SD card after I downloaded them from my PC. Here are direct links to those if anyone wants them and they are in order of install (descending) based on already having "YB1-X90F_USR_S000196_161104"
http://tabdl.ota.lenovomm.com/dls/v...S000239_1612091428_WW06_BP_ROW_WCAC703BC6.zip
http://tabdl.ota.lenovomm.com/dls/v...S000340_1702251540_WW06_BP_ROW_WC365253B3.zip
http://tabdl.ota.lenovomm.com/dls/v6/YB1-X90F_170420_WC76FD00EF.zip
http://tabdl.ota.lenovomm.com/dls/v...S000426_1705080316_WW06_BP_ROW_WC80C2A0F2.zip (this is the failed update that incited this thread)
All updates went great and all is well at this point. Made another TWRP backup and I plan to root again now and see if any upcoming updates later have some issue?
I just wanted to report back here if anyone was interested that I unrooted, updated the June OTA update, and was able to root again without issue.
i got the same error message and now i'm stuck. I cant install any updates and so i bought a account from easy-firmware to get the firmware ... the firmware: YB1-X90F_USR_S000036_1607280616_WW6_BP_ROW-flashfiles.zip
doesnt not work with twrp or the stock recovery... it tells me "zip file is corupt"
@MarkAllen: Can you provide a guide how you got back to the stock rom? just flashing the zips doesnt work....
i really need help...
FreddeHamm said:
i got the same error message and now i'm stuck. I cant install any updates and so i bought a account from easy-firmware to get the firmware ... the firmware: YB1-X90F_USR_S000036_1607280616_WW6_BP_ROW-flashfiles.zip
doesnt not work with twrp or the stock recovery... it tells me "zip file is corupt"
@MarkAllen: Can you provide a guide how you got back to the stock rom? just flashing the zips doesnt work....
i really need help...
Click to expand...
Click to collapse
You cannot flash the ZIP file with TWRP or stock recovery. You have to unzip the file and then flash each IMG file that you need manually while in fastboot mode (there are seven of them).
**** IF YOU FOLLOW THESE DIRECTIONS IT IS NO ONES FAULT BUT YOUR OWN IF IT SCREWS UP SOMETHING!!! ****
**** WILL TRY TO HELP PROVIDE INFO IF I CAN BUT CANNOT GUARANTEE ANYTHING. ALSO THIS ERASE ALL YOUR DATA ****
First be aware as noted in the previous post above that I tried using "YB1-X90F_USR_S000036_1607280616_WW6_BP_ROW-flashfiles.zip" intially and it worked fine to get me back up and running but once I was done no new OTA updates were showing at all. No clue why so I ended up doing it again but used the ROM named "YB1-X90F_USR_S000196_1611040312_WW06_BP_ROW-flashfiles.zip". Also note I had erased my "country" partition and flashed "country.img" which requires the info posted by vimalbhimani again linked above in my previous post. It has to be used to correct for your country, no biggie at all and worked fine for myself.
1) Unzip the ROM you downloaded to a folder on your PC
2) From command prompt go to that folder
3) Make sure from the command prompt that ADB and fastboot commands are working properly
4) Put your tablet in fastboot mode ("adb reboot bootloader")
(these next commands are directly from the "install.cmd" included with the ROM from EasyFW, I just opted to run them manually one at a time in order and I omitted the unlock and lock commands)
fastboot flash gpt gpt.bin
fastboot erase misc
fastboot erase persistent
fastboot erase frp
fastboot erase metadata
fastboot format config
fastboot format country
fastboot format cache
fastboot format data
fastboot format factory
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash config config.img
fastboot flash country country.img
fastboot flash system system.img
fastboot flash bootloader bootloader
fastboot flash oemvars bootloader_policy-oemvars.txt
fastboot continue
That's it. Minus the Intel error code 03 for being unlocked, it should be a normal out of the box setup when it boots back up into Android.
good luck!
People that are looking for the YB1-X90F_USR_S000196_1611040312_WW06_BP_ROW-flashfiles.zip may want to take a look at this post.
In contrast to my experiences with devices made by other OEMs, it seems like the files can directly be used for downgrading the Yoga Book if you're currently using a newer version.
Moved...
Hi everyone,
I just updated my Asus Zenpad 10 (Z300M) via OTA.
The tablet booted and I saw the Lock screen. But after a couple of second it reboot.
I've tried a factory reset. BU it's the same probleme: It boot up to the "first start" prompt, and after a couple of second reboot.
I tried to install a custom recovery to flash a new rom with SP-Flash Tool (following this post nstalling TWRP and rooting Asus Zenpad 10 (Z300m))
But I got an error when I readBack.
And even if I flash the recovery, I can't access it on the tablet. I got a message "Your device has failed verification and may not work properly" when I try to go to recovery
Can you help me with this ?
Thank you
Same problem. When WiFi is ON.
When I put WiFi OFF - the tablet works fine.
Last firmware doesn't help, reset too. I think there is no solution at this moment, except maybe to flash an old firmware with Android 6.
I'll replace it in store. No idea about Asus control quality of their firmware... but this problem is pretty common.
???
Belnadifia said:
Hi everyone,
I just updated my Asus Zenpad 10 (Z300M) via OTA.
The tablet booted and I saw the Lock screen. But after a couple of second it reboot.
I've tried a factory reset. BU it's the same probleme: It boot up to the "first start" prompt, and after a couple of second reboot.
I tried to install a custom recovery to flash a new rom with SP-Flash Tool (following this post nstalling TWRP and rooting Asus Zenpad 10 (Z300m))
But I got an error when I readBack.
And even if I flash the recovery, I can't access it on the tablet. I got a message "Your device has failed verification and may not work properly" when I try to go to recovery
Can you help me with this ?
Thank you
Click to expand...
Click to collapse
What I do not understand! Purchased this tablet due to the thread you mention on here for TWRP using the SP Flash Tool 5.132, right? I just went ahead and used the SP Flash Tool version been using and got that individual error right at the end so did NOT try flashing the recovery! He was very talkative B4 getting this tablet but now after speaking of errors, no responses.....? The version SPFL he says is the only one that works, its option.ini file DOES NOT have the READBACK part in it for changing from false to true...... the very next versions of SPFT after do.....
any ideas????
zach
coolbeans2016 said:
What I do not understand! Purchased this tablet due to the thread you mention on here for TWRP using the SP Flash Tool 5.132, right? I just went ahead and used the SP Flash Tool version been using and got that individual error right at the end so did NOT try flashing the recovery! He was very talkative B4 getting this tablet but now after speaking of errors, no responses.....? The version SPFL he says is the only one that works, its option.ini file DOES NOT have the READBACK part in it for changing from false to true...... the very next versions of SPFT after do.....
any ideas????
zach
Click to expand...
Click to collapse
Bro, are you serious? I don't reply to your messages for a few hours so you call that whole recovery/rooting thread some kind of a scam or conspiracy? (This is not my day job btw.) The error messages you are talking about are a result of you rushing into this thing and not doing your homework, skimming the directions and/or failing to use common sense. Of course SPFT 5.1532 does not have the read-by-partition option. That's why we use a later version for that. Exactly as it says in the OP. And if you were to do your homework, you would find out that the "..failed verification.." and/or "...different operating system.." messages are expected because of verified boot process built into the bootloader.
I'll give you that
diplomatic said:
Bro, are you serious? I don't reply to your messages for a few hours so you call that whole recovery/rooting thread some kind of a scam or conspiracy? (This is not my day job btw.) The error messages you are talking about are a result of you rushing into this thing and not doing your homework, skimming the directions and/or failing to use common sense. Of course SPFT 5.1532 does not have the read-by-partition option. That's why we use a later version for that. Exactly as it says in the OP. And if you were to do your homework, you would find out that the "..failed verification.." and/or "...different operating system.." messages are expected because of verified boot process built into the bootloader.
Click to expand...
Click to collapse
The link on the Z380M is what threw a flag for me because that Asus tab isnt rootable. If this is some combo of slipups between tools & devices that lines up just right to get TWRP on its not described very well in the OP. Using the 5.132 (?) you can not readback with that option.ini file.... so what am I missing? The bootloader unlock app isn't written for this tablet is it? written for the zenphone 2 (3)?
Wow, I'm not sure if you're trolling at this point or what. If your ASUS ZenPad 10 Z300M tablet is not rootable, then you are the first one to report such a device on XDA. You still keep saying you can't readback with SPFT "5.132". I hate to sound pedantic, but I think it's better if I make my reply in list form.
There is no 5.132. The recommended version is 5.1532.
SP Flash Tool version 5.1532 does not have the "ShowByScatter" feature at all, as I've told you at least twice.
You can read back any part of the flash ROM by specifying the range manually in 5.1532 or other versions.
You can read back by partitions specified in the scatter file by enabling "ShowByScatter" with SPFT 5.1548 or higher only.
You can flash to this device by using SPFT 5.1532 only (and a couple of older versions).
As for the guide not being clear
I did not write that guide. That is @justshaun's post. I only wrote one section of it and made some corrections to other parts.
Yes, you might encounter some stumbling blocks when blindly following the steps without knowing why you are doing them. But this is a good thing, to be honest. Because if you don't understand even a little bit about what you're doing, and are not able to solve those types of problems, then you have not crossed the pretty low bar for safely modifying your device. In that case, I think you're better off not bothering with this whole recovery/root thing. It's for your device's safety.
All of the problems that you're having have probably been discussed in one thread or the other.
As for the bootloader unlocker
I have never used the unlock tool.
It does not work sometimes, maybe even most of the time.
ASUS has removed the link to it from their download page
Take it up with ASUS if you want to make it work.
Just want to mention for anyone else struggling with this issue, what fixed it for me:
I found the reboot would only happen when wifi was turned on, and even more weird, it would only happen when connected to specific wifi networks. After doing a factory reset I was able to set it up again by tethering to the wifi on my phone. I then found that I actually was able to connect to the problematic wifi network but only by setting a static IP! This has completely resolved the issue for me.
Thaniks
diplomatic said:
Wow, I'm not sure if you're trolling at this point or what. If your ASUS ZenPad 10 Z300M tablet is not rootable, then you are the first one to report such a device on XDA. You still keep saying you can't readback with SPFT "5.132". I hate to sound pedantic, but I think it's better if I make my reply in list form.
There is no 5.132. The recommended version is 5.1532.
SP Flash Tool version 5.1532 does not have the "ShowByScatter" feature at all, as I've told you at least twice.
You can read back any part of the flash ROM by specifying the range manually in 5.1532 or other versions.
You can read back by partitions specified in the scatter file by enabling "ShowByScatter" with SPFT 5.1548 or higher only.
You can flash to this device by using SPFT 5.1532 only (and a couple of older versions).
As for the guide not being clear
I did not write that guide. That is @justshaun's post. I only wrote one section of it and made some corrections to other parts.
Yes, you might encounter some stumbling blocks when blindly following the steps without knowing why you are doing them. But this is a good thing, to be honest. Because if you don't understand even a little bit about what you're doing, and are not able to solve those types of problems, then you have not crossed the pretty low bar for safely modifying your device. In that case, I think you're better off not bothering with this whole recovery/root thing. It's for your device's safety.
All of the problems that you're having have probably been discussed in one thread or the other.
As for the bootloader unlocker
I have never used the unlock tool.
It does not work sometimes, maybe even most of the time.
ASUS has removed the link to it from their download page
Take it up with ASUS if you want to make it work.
Click to expand...
Click to collapse
I have downloaded everything in the OP again and will attempt to get twrp on tablet again. I did notice one item that was causing my problem that you could call a newbie f/u... I'm using a new browser that has adblock builtin & on by default and it was causing the "loop" when trying to download the recommended SP Flash tools. I got the ones from the link downloaded and they have more internal components like the newer SP Flash Tool versions....... My bad.
Will go through the steps again hopefully later today, my apologies man.
zls
coolbeans2016 said:
I have downloaded everything in the OP again and will attempt to get twrp on tablet again. I did notice one item that was causing my problem that you could call a newbie f/u... I'm using a new browser that has adblock builtin & on by default and it was causing the "loop" when trying to download the recommended SP Flash tools. I got the ones from the link downloaded and they have more internal components like the newer SP Flash Tool versions....... My bad.
Will go through the steps again hopefully later today, my apologies man.
zls
Click to expand...
Click to collapse
Ohhh... ok. No problem man. Just please get your facts straight before posting next time. Good luck. BTW, I'm not sure if you saw this post on the TWRP thread from 2 weeks ago. You didn't reply.
diplomatic said:
What is the error that you got when trying to flash it? Can you post a screenshot of the Download tab along with the Help/About dialog box?
Click to expand...
Click to collapse