Related
Hello guys,
i got a serious and frustrating problem here.
A few days ago my xoom was stuck on the M screen, so I used a thread in the forum and recovered it.
It solved myh problem back then, but since I had 3.2 before this and the solution injected me with Android 3.01 my problems started to show themselves.
the first one is that
<b> Through Fastboot, RecoveryMod, ADB </b> and any other way you can Imagine to install a new ROM or even remove or create a file,
All of them show success message but when I check them out I see no changes.
i tried fastboot and Recovery to install nearly every ROM,Recovery and bootimage in this site but so far it was wild goose chase.
so I want to ask if I'm doing anything wrong or if you need any more information here, but please help me with this
wow I cant believe it, All these masterminds here and no answer to my distress signal??
Guys I am so in trouble and this is the only place I hoped to get answered.
I can provide you with more info if you need, but please dont say I'm on my own here.
all these years this forum was the last hope for me.
i know I'll get my answer here one day
You are not being very clear about what you have done,, but I'm assuming that you reinstalled the stock image that got you back to HC 3.01. Can you see if you are able to get OTA updates to get you back to at least 3.1, or 3.2 if possible?
If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?
Mohfath said:
If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?
Click to expand...
Click to collapse
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?
okantomi said:
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?
Click to expand...
Click to collapse
That would be relief to know this could be solvable.
I will look more too.
As for your post I must say:
1. I plug the Xoom to the PC using the included cable
2. I start the xoom and start fastboot
3. on the PC system has the drivers and completely knows it
4. I start with SDK:
I. Fastboot oem unlock (Completing onscreen instructions and reboot device)
II. Fastboot mode again I use Fastboot flash boot boot.img
III. Continuing with Recovery,System
IV. Rebooting the device anything is the same.
My ROM is unchanged by the process and keeeeeeeeps giving the damn error of System process error please submit
5. And with ClockworkrecoveryMod I have the stock ROM on my sd card.
I. I choose install zip from sd card.
II.Choose the correct zip file and start flashing.
III. Choosing Wipe Data/Factory reset will take the device into a complete hang. unless I first use the mount page to mount the System/Data
IV. I reboot the device and ..... you know nothing changed.
so thats my story.
Still hope to find something about it.
Thanks...that was helpful. But now I want to know the following:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .
okantomi said:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .
Click to expand...
Click to collapse
Being rooted? -> Yes, The world is more beautiful with root!
to recover -> I followed this: http://forum.xda-developers.com/showthread.php?t=1097997 Shame it was Android 3.0
I use ClockworkRecovery 3.0.0.28 and I cant upgrade it cause of ... you know
And for your help I must say you are definitely the most caring person I know...
I'm off to check the provided link now
I was thinking of something that might be a reason.
I have this tiny problem:
When I go to CWM and choose Erase userData/Factory Reset Device Hangs
Click to expand...
Click to collapse
I was thinking of may be the userdata partition is corrupted and I gotta find a way to flash it completely.
Somehow I used Fastboot utility to do this and after saying Success, Nothing changed again.
Do you know any other way to physically do this job?
What you will need:
KingRoot V4.5.0.901 (latest version as of this posting)
Rooting your phone will void your warranty.
Terminal Emulator for Android
Replace KingUser with SuperSU
MtkDroidTools v2.5.3-updated
adbd Insecure v2.00
SP Flash Tool
I am not going to get into how to install ADB drivers, MtkDroidTools, or SP Flash Tool. If you are not experienced with rooting, flashing, etc., please do some research.
Okay, let's get started
First you will need to get your phone rooted. Download KingRoot using the link above and follow this guide.
Next you will need to replace KingUser with SuperSU.
Now that we have the phone rooted and SuperSU in place, we can use MtkDroidTools to make a backup of the phone.
This video will show you how to backup your phone with MtkDroidTools (make sure you have downloaded the version I provided, as this has updated ADB files). Also make sure you enabled adbd Insecure before you connect your phone (you don't need to check enable at boot).
Once you have a successful backup, you need to create the files for flashing (scroll down to PREPARING EXTRACTED MTK ANDROID FLASH FILES FOR FLASH TOOLS) if you need to flash back to the original firmware.
Hopefully you now have a backup of your phone. Now we can install a custom recovery. You can use either TWRP (rename to recovery.img) or PhilZ.
The easiest way to flash the custom recovery is with SP Flash Tool. Connect your phone (you don't need adbd Insecure enabled for this). Run flash_tool.exe as administrator. For scatter-loading File click on the Scatter-loading folder
and navigate to your MtkDroidTools backups folder. There should be a folder that starts with BLU-STUDIO-C. Open that folder and select MT6582_Android_scatter.txt. For the recovery file, navigate to the one you downloaded (TWRP or PhilZ) by clicking on the Location column next to RECOVERY.
Make sure RECOVERY is the only box checked before proceeding. Now you have your scatter file and custom recovery loaded. Click on the Download button. Nothing will happen at this point. Now shut down your phone (not restart). Once your phone shuts down completely, plug it in via USB and you should see it begin to flash the custom recovery. If not, then you need to make sure you have the necessary drivers installed. Once it's complete, you can close out SP Flash Tool and disconnect your phone. After your phone is disconnected, hold down the power and volume up buttons until the recovery menu appears :good:
Post your feedback, and if you encounter any problems, please be as descriptive as possible. Good Luck
Credits:
@AlexZap who was the first to help me along this crazy journey
@yuweng for all his help in backing up the phone and for PhilZ recovery
@bigrammy for porting TWRP Recovery
@rua1 for MtkDroidTools
@carliv for CarlivTouchRecovery
Thanks for this guide, it has worked for me so far (backing up with mtkdroidtools now). Can I ask, why is it neccessary to use SPFT to flash the recovery? I have used fastboot to flash the recovery without issues. I just
$ fastboot oem unlock
and then was able to
$ fastboot flash recovery recovery.img
and it worked.
html
Also, would you be able to port some custom roms for this phone?
cteeto said:
Thanks for this guide, it has worked for me so far (backing up with mtkdroidtools now). Can I ask, why is it neccessary to use SPFT to flash the recovery? I have used fastboot to flash the recovery without issues. I just
$ fastboot oem unlock
and then was able to
$ fastboot flash recovery recovery.img
and it worked.
html
Also, would you be able to port some custom roms for this phone?
Click to expand...
Click to collapse
Glad it worked out for you. Yes, fastboot is also an option (as you all ready know).
Recovery could probably be flashed with Flashify, but haven't tried it. I am not a developer, so no I can't port any ROM's, and take no credit for the custom recoveries listed here.
If someone can post Cyanogenmod for a phone that uses the same hardware, I can port that for this phone.
sandix said:
If someone can post Cyanogenmod for a phone that uses the same hardware, I can port that for this phone.
Click to expand...
Click to collapse
ABSOLUTLY.......this would just be AMAZING...if anyone could manage to make a Cyanogenmod for this phone.....:good:
Bricked Blu Studio C (D830U)
Hey,
Was wondering if you could help me out here, as I'm a TOTAL Noob when it Comes to BLU phones But not to flashing....
I've Bricked by Phone, The Computer and SP Flash Tools still recognize the phone..
I've Downloaded the proper ROM from NeedRom.com....
My Issues:
1. Can you Verify WHICH Driver I should Be Using for a FULL either Erase/Download Or a Firmware Upgrade (Not Sure Which)
2. I need a Scatter File the Contains ALL the Memory address and Supplies ALL the Check Marks for a FULL Rewrite Flash....The One with the rom is missing Preloader Android, Cache, and usrdata...
When I did JUST the Scatter file flash attempt I got the BROM_ERROR : S_DL_GET_DRAM_SETTING_FAIL ( 5054 )
I googled that and it said the Perloader wsn't right So I added the Perloader (And checked the "firmware.info file" and seen the Memory:
preloader 0x0000000000c00000 0x0000000000000000 2 /dev/misc-sd
So I tried Anyway and got the same error except this time it's 4032.
So Basically Can you tell Me Which Files In the ROM I Download Go Into Which SLOTS on SPFTools, and Which memory address' are correct the firmware file or the Scatter??
I really don't want to keep slamming the phone with "STUFF" and REALLY screw something up, I think I'm lucky it's even being recognized at this point....
Also the MTK_Allinone_DA.bin that comes with SPFTools is the right one??!?!
I'm Using Version 5.13.52.200
I'm Assuming Just a FULL Scatter file would solve the problem?!?!?
ANYHELP In this Would be VERY much Appreciated....
Thanks
Mike
EDIT:
Ok, I got it to 4001 Error, And it's saying that error is it's not connecting with the preloader, So I'm thinking (hoping) if I can get those 3 files, even if the cache is empty as long as the memory address is right, and the scatter.txt, and do a Firmware upgrade, Hope, will solve the problem, if not, On to Test Pins...
@bobl61
Could work together to enhance MTKDroid liek as
Increae number of CPU recognize by it (ex. MT67xx - just recognize it - not work with it)
Update the apk included and sued by MTKDroid (like MobileUncle/Root Explorer/SuperSU)
Upload the ROM or the link I think I know what's the problem @Miker1029
Fixed from the dead!
Swaelae113 said:
Upload the ROM or the link I think I know what's the problem @Miker1029
Click to expand...
Click to collapse
Hey Thanks, I've made some progress today, The rom is on Need Rom.com so best to just google Needrom and D830U as It's internal search doesn't work so well....
I Got a New (Cheap, Used Phone) and to my Suprise It's an MT65XX Chip set Also (ACK!!!!!)..................... NO WAY IT JUST BOOTED UP!!!!!!!!!!!!!!!!!!!!!!!!!!! TOOK FOREVER!!!!!
Ok I learned that with the Downloaded ROM from Needrom, You Need to Go to MTK Tools and Process blocks for flash, The go to the Directory you Extracted the ROM to, And It'll bring up the MD5 file click it and It'll create the Scatterfile and the "!FLASH" Directory, Then Navigate to the !FLASH (something) Directory and you'll have your scatterfile.txt, Load it up, I added ALL files (see Screen Shot) and it's booted up.... You need to use Preloader Drivers for it, And I HAD TO FORMAT AND FLASH.... And what you see in the SPFlashtool screen shot is what I flashed....
I'm not a GUIDE writer sorry, But Hopefully this will give hope to those like me (that have been bricked for ALONG TIME) Hope.....
If anyone needs info on this Ask, I'll try and answer.....
Mike
IMEI Problem
Miker1029 said:
Hey Thanks, I've made some progress today, The rom is on Need Rom.com so best to just google Needrom and D830U as It's internal search doesn't work so well....
I Got a New (Cheap, Used Phone) and to my Suprise It's an MT65XX Chip set Also (ACK!!!!!)..................... NO WAY IT JUST BOOTED UP!!!!!!!!!!!!!!!!!!!!!!!!!!! TOOK FOREVER!!!!!
Ok I learned that with the Downloaded ROM from Needrom, You Need to Go to MTK Tools and Process blocks for flash, The go to the Directory you Extracted the ROM to, And It'll bring up the MD5 file click it and It'll create the Scatterfile and the "!FLASH" Directory, Then Navigate to the !FLASH (something) Directory and you'll have your scatterfile.txt, Load it up, I added ALL files (see Screen Shot) and it's booted up.... You need to use Preloader Drivers for it, And I HAD TO FORMAT AND FLASH.... And what you see in the SPFlashtool screen shot is what I flashed....
I'm not a GUIDE writer sorry, But Hopefully this will give hope to those like me (that have been bricked for ALONG TIME) Hope.....
If anyone needs info on this Ask, I'll try and answer.....
Mike
Click to expand...
Click to collapse
Update, Just a Heads Up I'm Assuming from Googling around, that Installing the NVRAM will wipe your IMEI, Still working on this aspect, But it doesn't seem to be Hindering the phone in anyway, As I said It Took along time to boot up, So I'm not sure if Re-writing the NVRAM made it work or not, I do know I formatted + Download, and It Sat On the Splash Screen, I shut down and Flashed just the NVRAM file, and It booted.....
NOW Should I go for a Custom Recovery??? LOL.... I'll wait.... But now that I know I can Fix it......Hmmmmm
Mike
Miker1029 said:
Hey Thanks, I've made some progress today, The rom is on Need Rom.com so best to just google Needrom and D830U as It's internal search doesn't work so well....
I Got a New (Cheap, Used Phone) and to my Suprise It's an MT65XX Chip set Also (ACK!!!!!)..................... NO WAY IT JUST BOOTED UP!!!!!!!!!!!!!!!!!!!!!!!!!!! TOOK FOREVER!!!!!
Ok I learned that with the Downloaded ROM from Needrom, You Need to Go to MTK Tools and Process blocks for flash, The go to the Directory you Extracted the ROM to, And It'll bring up the MD5 file click it and It'll create the Scatterfile and the "!FLASH" Directory, Then Navigate to the !FLASH (something) Directory and you'll have your scatterfile.txt, Load it up, I added ALL files (see Screen Shot) and it's booted up.... You need to use Preloader Drivers for it, And I HAD TO FORMAT AND FLASH.... And what you see in the SPFlashtool screen shot is what I flashed....
I'm not a GUIDE writer sorry, But Hopefully this will give hope to those like me (that have been bricked for ALONG TIME) Hope.....
If anyone needs info on this Ask, I'll try and answer.....
Mike
Click to expand...
Click to collapse
You are correct. I didn't realize the video on how to backup the stock rom did not include the next step which is to create the files needed to flash with MTK. Good catch, Miker1029 :good:
bobl61 said:
You are correct. I didn't realize the video on how to backup the stock rom did not include the next step which is to create the files needed to flash with MTK. Good catch, Miker1029 :good:
Click to expand...
Click to collapse
Hey Thanks, Maybe you can redo it or whatever, I was bricked for Months (Mainly Because i didn't know the Phone Type), Check out the screenshots to see the extent I went to Googling My Butt Off trying to figure it out, But once I did, All went good, I've flashed Atleast 100 Phones, For me, Friends, Family, Never had the Kind of issues I had with the MTK Chipset...
But now that I have it, It's rooted, Flashed, Xposed Framework Installed and working, Exactly what I was "Originally" trying to do....LOL, It's good now tho...
Now Funny thing I lost My Compass on it, and Sensor detector says it's working fine, So Not sure what's Interfering With it.... Hate to Re-Flash
SOOO, If I GOTTA re-flash Been looking around for 6.0 (Marshmallow) Build for it (No Luck)
1st Pic, Just the Face.
2nd Pic, Where I Cut the Battery Connector (Casing) to the Board so I could Disconnect the Battery without taking the phone apart....
3rd Pic, I left the screws out as There's a Little spring on the Bottom-Left (Looking from the back) that Makes the speaker work, And On the Bottom-Right is the antenna connection that I can't get to "Snap" back in..... So I left the screws out to fix those minor issues, I'm trying to NOT open it anymore then I already have LOL
Mike
I want custom ROM for blu studio c 5+5
[Q
So i did this exactly as its written and now my d830u its freezing in blu logo... and im not able to enter recovery img, i used the philz link since the other one is deleted... hope any1 could help!
bertucci25 said:
So i did this exactly as its written and now my d830u its freezing in blu logo... and im not able to enter recovery img, i used the philz link since the other one is deleted... hope any1 could help!
Click to expand...
Click to collapse
Little. More details would be nice..
Did you download the rom from needrom?
Did you create the flashable files from that rom?
Did you generate and add scatter file?
Did you format and flash?
Did you check device manager to see if it's using the pre drives?
Did you remove any and alll USB / MTK drives, except the pre driver?
Disd you start the flash THEN plug on the phone? Does MTK say on the bottom PRE driver?
And finally i believe my issue was some kind of lock up as the battery isnt removable so i cut the casing to access the battery connector and basically stated the flash and attached the battery connection..
Alls i can say is i was at the exact same spot as you i flashed 3 or 4 totally incorrect roms, and had that driver issue, when i finally got the proper rom and fixed the driver issue it worked, and it did take like 20 to 30 minutes for the ohone to boot the 1st time..
Mike
---------- Post added at 11:05 AM ---------- Previous post was at 10:33 AM ----------
Also, i used the recovery that came with the rom and when it finally booted up, i flashed the custom recovery...
And if you decide to go with disconnecting the battery be careful as some months after the female connection on the board broke completely off... I hate any phone without a way to break the electrical connection think it's stupid..
Good luck,
Mike
Miker1029 said:
Little. More details would be nice..
Did you download the rom from needrom?
Did you create the flashable files from that rom?
Did you generate and add scatter file?
Did you format and flash?
Did you check device manager to see if it's using the pre drives?
Did you remove any and alll USB / MTK drives, except the pre driver?
Disd you start the flash THEN plug on the phone? Does MTK say on the bottom PRE driver?
And finally i believe my issue was some kind of lock up as the battery isnt removable so i cut the casing to access the battery connector and basically stated the flash and attached the battery connection..
Alls i can say is i was at the exact same spot as you i flashed 3 or 4 totally incorrect roms, and had that driver issue, when i finally got the proper rom and fixed the driver issue it worked, and it did take like 20 to 30 minutes for the ohone to boot the 1st time..
Mike
---------- Post added at 11:05 AM ---------- Previous post was at 10:33 AM ----------
Also, i used the recovery that came with the rom and when it finally booted up, i flashed the custom recovery...
And if you decide to go with disconnecting the battery be careful as some months after the female connection on the board broke completely off... I hate any phone without a way to break the electrical connection think it's stupid..
Good luck,
Mike
Click to expand...
Click to collapse
Ok i'm going to explain my journey from soft-to-revive history:
I was trying to install a custom recovery for my D830U (Blu) and end up in this thread. I made all the steps
-Rooted the phone with kingroot
-Removed kingroot and installed SuperSU
-Instaled insecure adbd insecure
-I made a backup of my stock rom with MtkDroidsTool(wich is the needrom provided, since i flashed my phone while ago)
-Drivers are installed (VCOM)
Everything is downloaded from the links in the post
Ok at this point i did everything exactly like the guide, great
Ok now the part were "something" failed is:
I got the scatter file in the mtkdroidstool backup folder and REPLACED the recovery to the PhilZ recovery.img in the link of the first post. And flashed normaly. Here is where things got bad
I disconnected the phone and realized it got bootloop, couldnt start the phone and can't get into recovery (when i press vol+ button it goes to black screen), because i installed a bad/not compatible philz recovery.img(AGAIN ITS FROM THE PROVIDED LINK) ok now i'm worried but no problem, i tried to reflash with original stock rom and eventually after many tries i got into a normal recovery mode and the phone boots normal..
Now my phone is at the start point. Can you tell me which version of custom recovery are you currently using? Or what procedure should i follow to get into it? Again thanks! Cheers.
Ya I'll upload the recovery i used, I'll get it here sometime today..
I'm not sure which it is, as i said, the power connection for the battery broke off the board awhile ago, so it's either philz or twrp.
Also, if I'm remembering correctly, you have to add the other drivers, not the pre driver, you can try it with the pre, and if you don't get the green check use the other ones, and when you go flash, I'd backup your recovery you have now and put it somewhere safe...
Ill also add the version of xposed i used, if i can find it.. I know i had to install the. Zip files from recovery...
Mike
I believe this is the custom recovery i flashed, i no longer have the phone to test, but i believe i removed all except the stock and custom..
As i said back up your current recovery..
Let me know so i can mark it my puter.. Thanks
Mike
Also let me add, I had a bad philz also, not sure if i got it here, or somewhere else, but i have it marked as philz doesnt work on my computer...
Ok folks, two downloads, can you provide an update?
I'm trying to help with an obscure phone..
So a report back, for the people, would be nice.
Mike
Miker1029 said:
Ok folks, two downloads, can you provide an update?
I'm trying to help with an obscure phone..
So a report back, for the people, would be nice.
Mike
Click to expand...
Click to collapse
Hey mike im going to test this today i'll update my progress in a few! wish me good luck :silly:
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