Related
My computers don't recognize my Asus Zenfone 2 Ze551ml. I've installed the intel drivers, the asus drivers, the google android drivers. I've restarted, tried different USB ports, tried different computers, and tried different USB wires but to no avail.
I originally wanted to unroot so that I could apply OTA updates but I couldn't get into recovery, all the phone does is restart into bootloader again. All the solutions I read require me to use ADB or get into recovery and since I can't get into recovery or get any computer to recognize the phone I seem to be stuck.
I haven't updated the OTA since 2.18.40.12 version. Can anyone help me figure out how to update my phone or get my computer to recognize it?
Thanks,
Please see the following for hardware reset/wipe cache partition procedure:
http://www.asus.com/us/support/FAQ/1011956/
Please see the following and scroll down for manual firmware update procedure:
http://www.asus.com/us/support/FAQ/1009748/
If you have any questions or concerns with Zenfone 2 please feel free to contact me direct at [email protected].
Sincerely,
ASUS_USA
Thanks for the reply Asus_USA,
Unfortunately, both the links you sent me don't work on my phone. For the first link (hardware reset/wipe cache partition) it asks me to go into fastboot mode, which I can do no problem, it then tells me to go into recovery mode. I can scroll down with my volume keys to the 'recovery mode' option but when I hit the power key to reboot the phone into recovery mode, it just reboots back into fastboot mode.
The second link (manual firmware update) asks me to download the update from the ASUS website, which I can do with no problem and then attach the phone to the computer and transfer the zip file to the root of my internal storage, I can't do this because the computer doesn't recognize my phone and therefore doesn't allow me to copy anything into it.
Let me know if you have any other ideas!
Thanks,
Kalkin19 said:
Thanks for the reply Asus_USA,
Unfortunately, both the links you sent me don't work on my phone. For the first link (hardware reset/wipe cache partition) it asks me to go into fastboot mode, which I can do no problem, it then tells me to go into recovery mode. I can scroll down with my volume keys to the 'recovery mode' option but when I hit the power key to reboot the phone into recovery mode, it just reboots back into fastboot mode.
The second link (manual firmware update) asks me to download the update from the ASUS website, which I can do with no problem and then attach the phone to the computer and transfer the zip file to the root of my internal storage, I can't do this because the computer doesn't recognize my phone and therefore doesn't allow me to copy anything into it.
Let me know if you have any other ideas!
Thanks,
Click to expand...
Click to collapse
You can download the file directly to your phone from chrome by going to the download site on your phone. Also try setting your phone to PTP mode when it is plugged in and see if anything changes in device manager.
Or take out the sd card and copy to that, once back in phone you can then copy or move...
ultramag69 said:
Or take out the sd card and copy to that, once back in phone you can then copy or move...
Click to expand...
Click to collapse
Tried it this way and then rebooted the phone. The phone recognized that there was an update file, and when I allowed it to install it rebooted into the Fastboot screen and then did nothing. I waited a half hour before touching the phone. When I rebooted the phone it didn't update and nothing had changed.
cmendonc2 said:
You can download the file directly to your phone from chrome by going to the download site on your phone. Also try setting your phone to PTP mode when it is plugged in and see if anything changes in device manager.
Click to expand...
Click to collapse
I tried downloading the file from online and the same thing happened as with the SD Card. When I restarted the phone it recognized that there was an update file and asked me if I wanted to install it. I clicked yes, it thought for about 30 seconds and then rebooted the phone into fastboot mode. Nothing happened after that and I had to choose the 'Reboot' option to start the phone back up; nothing had changed and the update did not work.
PTP mode doesn't seem to affect anything. My computer still doesn't recognize the phone.
I should also mention that the phone *does* charge when plugged into the computer.
Maybe u r having drivers issues
Try it with diff pc
Sent from my ASUS_Z008D using XDA Free mobile app
yakub234go said:
Maybe u r having drivers issues
Try it with diff pc
Sent from my ASUS_Z008D using XDA Free mobile app
Click to expand...
Click to collapse
I have. I tried it on 2 desktops and 3 different laptops, I installed the necessary drivers on all of them and tried using different USB cables. No luck.
Kalkin19 said:
I tried downloading the file from online and the same thing happened as with the SD Card. When I restarted the phone it recognized that there was an update file and asked me if I wanted to install it. I clicked yes, it thought for about 30 seconds and then rebooted the phone into fastboot mode. Nothing happened after that and I had to choose the 'Reboot' option to start the phone back up; nothing had changed and the update did not work.
PTP mode doesn't seem to affect anything. My computer still doesn't recognize the phone.
I should also mention that the phone *does* charge when plugged into the computer.
Click to expand...
Click to collapse
Your PC won't recognize it, even in fastboot mode?
If it does you can flash a new recovery in fast boot by using the adb tools. To test attach phone in fastboot mode to pc and type in "fastboot devices".
If it detects the phone you will see your serial number come up. Then reflash the pre-rooted image. it might replace the screwed up files in your recovery.
Instead of the ADB drivers only though, use the flashtools found here - http://forum.xda-developers.com/attachment.php?attachmentid=3301263&d=1431011927 Say thankyou to Shakalaka... I was having trouble using ADB, you might need to update to the latest drivers, but the flashboot tools worked with no problem...
You need to put the pre-root.img file in the folder and after connecting phone via usb hold shift, rightclick inside flashtools folder and select "open command window here" from drop down menu.
Then try the fastboot devices command.
Afterwards you can either flash the recovery again back to stock or flash the pre-rooted image and see if that fixes it.
You can find stock recovery,droidboot.img files and boot.img files here - http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
Again, BIG thanks to Shakalaka.
ultramag69 said:
Your PC won't recognize it, even in fastboot mode?
If it does you can flash a new recovery in fast boot by using the adb tools. To test attach phone in fastboot mode to pc and type in "fastboot devices".
If it detects the phone you will see your serial number come up. Then reflash the pre-rooted image. it might replace the screwed up files in your recovery.
Instead of the ADB drivers only though, use the flashtools found here - http://forum.xda-developers.com/attachment.php?attachmentid=3301263&d=1431011927 Say thankyou to Shakalaka... I was having trouble using ADB, you might need to update to the latest drivers, but the flashboot tools worked with no problem...
You need to put the pre-root.img file in the folder and after connecting phone via usb hold shift, rightclick inside flashtools folder and select "open command window here" from drop down menu.
Then try the fastboot devices command.
Afterwards you can either flash the recovery again back to stock or flash the pre-rooted image and see if that fixes it.
You can find stock recovery,droidboot.img files and boot.img files here - http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
Again, BIG thanks to Shakalaka.
Click to expand...
Click to collapse
My computers don't recognize my phone even when it's on fastboot mode so I can't follow any of the steps
Would the solution for flashing recovery detailed in this thread help you ?
http://forum.xda-developers.com/showthread.php?t=3166701
You would need to still have root.
Sent from my ASUS_Z00AD using Tapatalk
corrsea said:
Would the solution for flashing recovery detailed in this thread help you ?
http://forum.xda-developers.com/showthread.php?t=3166701
You would need to still have root.
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
Thanks for directing me to that thread, it looks like, unfortunately, I have lost root access over the course of trying different solutions... Anyone know of a way to allow terminal to access root without superuser?
i have the same problem, computer sees my device in fastboot but i cant flash anything through recovery, everything is whiped i have no system on phone now i tried everything.
when i use adb drivers suggested in post above it says outdated server and still doesnt see my device in recovery mod.
i tried on 2 computers
i tried stock recovery matching my stock rom
i tried twrp
in general it says on my phone"you need sdb 1.0.32 or higher" but i use 1.3 version (15 secs install)
any suggestions?
thats the first phone ive ever bricked and i'm panicking right now...
Hi everyone.
And @Kalkin19 @ma.ruda,
Could you both try to follow my steps on other similar thread?
It's on http://forum.xda-developers.com/showthread.php?p=64093132
Let me know if your adb problem is solved or not.
Edit: Seems this thread is so old! Someone bumped it by posting the same issue. But, yeah, at least, give a reply. :silly:
Sent from my ASUS_Z00AD
krasCGQ said:
Hi everyone.
And @Kalkin19 @ma.ruda,
Could you both try to follow my steps on other similar thread?
It's on http://forum.xda-developers.com/showthread.php?p=64093132
Let me know if your adb problem is solved or not.
Edit: Seems this thread is so old! Someone bumped it by posting the same issue. But, yeah, at least, give a reply. :silly:
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
Sorry for such a delayed response, I haven't logged in and checked my messages in a while. This issue was fixed for me randomly. I kept plugging my phone into my computer and it eventually recognized it (after about 60 different tries). I quickly added adb, unlocked, rooted and have been having no issues since then. I appreciate your link! Hopefully it helps others in the future.
i tryed to root my phone everything was going alright, but wen i went to boot it up i got stuck on
ASUS IN SEARCH OF INCREDIBLE and a loading logo, i can not get in to my bootloader
my pc detects it but fast boot and adb do not detect it
what do i do :crying::crying::crying::crying:
FluidArc said:
i tryed to root my phone everything was going alright, but wen i went to boot it up i got stuck on
ASUS IN SEARCH OF INCREDIBLE and a loading logo, i can not get in to my bootloader
my pc detects it but fast boot and adb do not detect it
what do i do :crying::crying::crying::crying:
Click to expand...
Click to collapse
Probably you soft bricked your phone. I got into a similar situation when I applied OTA after root. Dont worry, its very easy to recover your phone. It should be able to boot in Fasboot mode. If it does, follow follow this guide:
.theandroidsoul.com/how-to-unbrick-asus-zenfone-2-works-on-ota-fail-too-82039/ (Add www at the start)
Download the latest pre-rooted system .img from here:
mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Download the stuff needed and then just follow the guide. Hopefully you recover your device. Best of luck!
EDIT: Forgot to add but did you install the adb drivers? Probably thats the reason Fastboot and adb dont detect it. Or did you go into the fastboot mode in the phone? If not, do that first. To do it, follow these steps:
1. Power your device down.
2. Press and hold the power and volume up button.
3. Release the power button when it vibrates.
4. Release the volume up button once the ASUS splashscreen appears.
5. Now the device should be in Fasboot mode.
6. Then connect your phone to your PC (dont forget to install the drivers!) using the USB Cable and go to the folder where the flashtools are.
7. Hold Shift and right click > then click open command window here
8. Type "fastboot devices". Enter the command two times. (Cause the first time it will start daemon or something like that)
If your device shows up, congrats! You are in fastboot mode and it is working.
now what do i do
i do not know what ferwere i am on and my recovery is broken how to i get it up and runing
dh_711 said:
Probably you soft bricked your phone. I got into a similar situation when I applied OTA after root. Dont worry, its very easy to recover your phone. It should be able to boot in Fasboot mode. If it does, follow follow this guide:
.theandroidsoul.com/how-to-unbrick-asus-zenfone-2-works-on-ota-fail-too-82039/ (Add www at the start)
Download the latest pre-rooted system .img from here:
mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Download the stuff needed and then just follow the guide. Hopefully you recover your device. Best of luck!
EDIT: Forgot to add but did you install the adb drivers? Probably thats the reason Fastboot and adb dont detect it. Or did you go into the fastboot mode in the phone? If not, do that first. To do it, follow these steps:
1. Power your device down.
2. Press and hold the power and volume up button.
3. Release the power button when it vibrates.
4. Release the volume up button once the ASUS splashscreen appears.
5. Now the device should be in Fasboot mode.
6. Then connect your phone to your PC (dont forget to install the drivers!) using the USB Cable and go to the folder where the flashtools are.
7. Hold Shift and right click > then click open command window here
8. Type "fastboot devices". Enter the command two times. (Cause the first time it will start daemon or something like that)
If your device shows up, congrats! You are in fastboot mode and it is working.
Click to expand...
Click to collapse
Once happened to my zf2, what i did is formatting cache from the adb then my device could be detected, thus i could enter the recovery mode
Sent from my ASUS_Z00AD using XDA Free mobile app
i can not enter recovery
dawnsleeper said:
Once happened to my zf2, what i did is formatting cache from the adb then my device could be detected, thus i could enter the recovery mode
Sent from my ASUS_Z00AD using XDA Free mobile app
Click to expand...
Click to collapse
it is fix all good guys thx
FluidArc said:
i can not enter recovery
Click to expand...
Click to collapse
Hey,
Could you please help me (or anyone for that matter).....I've soft bricked my phone and I'm a little weary about following any other steps incase I fully brick the phone.
I have a Zenfone 2 that was CN Z00A 2.20.40.63 , I tried to root because random chinese apps kept downloading on my phone and obv it soft bricked (kept looping at boot).....since then I have tried a lot of stuff without luck and my brain is fried from all the information.... I went to the recovery mode but ADP couldn't find my phone and then I loaded a recovery image on my SD calling it MOFD_SD.ZIP but that didn't work due to signature verification error. Now after reading what you wrote I can see that fastboot is recognizing my device....I would go through with the process but I'm afraid if I screw this one up it could be the end of fastboot working and therefore me being royally screwed.
Since my phone was naturally CN Z00A 2.20.40.63 I'm wondering if the pre-rooted images on the site you mentioned above will work? There is no download for CN Z00A 2.20.40.63 and I want to know whether it's safe to use CN Z00A 2.20.40.61 (or a WW image) or whether I have to try another option (if you have any suggestions).
If anyone could reply with help it would be greatly greatly appreciated.
dh_711 said:
Probably you soft bricked your phone. I got into a similar situation when I applied OTA after root. Dont worry, its very easy to recover your phone. It should be able to boot in Fasboot mode. If it does, follow follow this guide:
.theandroidsoul.com/how-to-unbrick-asus-zenfone-2-works-on-ota-fail-too-82039/ (Add www at the start)
Download the latest pre-rooted system .img from here:
mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Download the stuff needed and then just follow the guide. Hopefully you recover your device. Best of luck!
EDIT: Forgot to add but did you install the adb drivers? Probably thats the reason Fastboot and adb dont detect it. Or did you go into the fastboot mode in the phone? If not, do that first. To do it, follow these steps:
1. Power your device down.
2. Press and hold the power and volume up button.
3. Release the power button when it vibrates.
4. Release the volume up button once the ASUS splashscreen appears.
5. Now the device should be in Fasboot mode.
6. Then connect your phone to your PC (dont forget to install the drivers!) using the USB Cable and go to the folder where the flashtools are.
7. Hold Shift and right click > then click open command window here
8. Type "fastboot devices". Enter the command two times. (Cause the first time it will start daemon or something like that)
If your device shows up, congrats! You are in fastboot mode and it is working.
Click to expand...
Click to collapse
Captain_Hindsight said:
Hey,
Could you please help me (or anyone for that matter).....I've soft bricked my phone and I'm a little weary about following any other steps incase I fully brick the phone.
I have a Zenfone 2 that was CN Z00A 2.20.40.63 , I tried to root because random chinese apps kept downloading on my phone and obv it soft bricked (kept looping at boot).....since then I have tried a lot of stuff without luck and my brain is fried from all the information.... I went to the recovery mode but ADP couldn't find my phone and then I loaded a recovery image on my SD calling it MOFD_SD.ZIP but that didn't work due to signature verification error. Now after reading what you wrote I can see that fastboot is recognizing my device....I would go through with the process but I'm afraid if I screw this one up it could be the end of fastboot working and therefore me being royally screwed.
Since my phone was naturally CN Z00A 2.20.40.63 I'm wondering if the pre-rooted images on the site you mentioned above will work? There is no download for CN Z00A 2.20.40.63 and I want to know whether it's safe to use CN Z00A 2.20.40.61 (or a WW image) or whether I have to try another option (if you have any suggestions).
If anyone could reply with help it would be greatly greatly appreciated.
Click to expand...
Click to collapse
Well, I'm not sure if it'll work but check this out (Scroll down to No. 4 - Changing from CN to WW version):
forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
I'm no expert, but to be honest the state your device is in, I don't see any other options. Because when my device (it had WW firmware) got soft-bricked, I followed the guide by androidsoul and it did recover my phone. Not sure about yours since its a CN one.
If you like living on the edge and are really desperate, go ahead try this out, if not, better wait for someone with more knowledge then me.
EDIT: I forgot but since ADB isn't working, you can't use this method. So the only option I see that you have is flashing a pre-rooted rom.
Hello All,
I would like to start by saying that I am a novice when it comes to rooting phones so ANY help received here will be greatly appreciated. I have come across a few people within the various forums who have a very similar issue to the one I am having, but nothing exact. Now to the point.
Phone: Zenfone 2 (Model: ZE551ML-23-4G64GN-BK) came unlocked from amazon.com
Carrier: Metro PCS.
PC used to root: Win 7 64 bit / AV: Avast Free.
Issue: About 1 month ago I rooted my phone. Last night I received a prompt to do an OTA update, and selected install. I realized after that I shouldn't have done that, but it was too late. My phone would not load past the black and white ASUS loading screen.
I then proceeded to do some research online, and try to "unbrick" my phone myself. I figured out how to hold the power button + volume up key, select Recovery Mode with the power key, and press power + volume up again to get into the Recovery Mode. I was following some instructions online that didn't really make sense, which led me to choosing Wipe Cache Partition. This didn't work, so I had to manually reboot the phone (Hold the power key, and turn it back on). From that point forward I have been unable to get back into the Recovery Mode. Once I get to the sleeping android with the red triange I have tried holding power + volume up (which got me into recovery mode the first time), power + volume down, power + both volume up and down, I've rebooted my phone several times to make sure I was doing this as soon as the little android appeared and nothing happens. The android just pulses in and out and nothing happens. This is the first of my many problems as I have never flashed a ROM before, and I am a novice. Also my PC does not recognize my phone at all at this point. I'm using the same cable and port that I always use when transferring files. The port has been tested with a tablet and iPhone, which works. My questions are as follows:
1. Am I screwed? lol.
2. Is there a way/trick to getting into recovery mode again?
3. Can I still unbrick my phone without getting into recovery mode? Is there something I can do with my phone connected to the PC perhaps?
I would also like to mention the following:
1. I've downloaded firmware Version V2.20.40.160 from asus website. Is this the right "image" or 4 files I should be using to flash onto my phone?
2. I've also downloaded ADB, but it doesn't look like the 15 second one, and it does not detect my phone. What tools do I download in order to fix the issues I am having?
Thank you in advance!
Best regards,
Clavin0089
For anyone who may have found this thread I think I found a fix here. I will let you know after I test this if it works:
http:
//valuestuffz.blogspot.com
/2015/10/fix-zenfone-2
-stuck-in-recovery-wipe-cache-partition.html?m=1
Sorry. I had to break up the link in order to post it.
Clavin0089 said:
I would also like to mention the following:
1. I've downloaded firmware Version V2.20.40.160 from asus website. Is this the right "image" or 4 files I should be using to flash onto my phone?
2. I've also downloaded ADB, but it doesn't look like the 15 second one, and it does not detect my phone. What tools do I download in order to fix the issues I am having?
Thank you in advance!
Best regards,
Clavin0089
Click to expand...
Click to collapse
i was in same sit with a brick of sorts and used this guid to help me:
> http://www.asus-zenfone.com/2015/12/how-to-downgrade-asus-zenfone-2-firmware.html *** I used this to go from the 168/174 ( 174 didnt fix issue that 168 caused ) back to 160
> http://www.asus-zenfone.com/2015/03/zenfone-2-how-to-enter-recovery-wipe.html *** How to enter recovery if you dont know how
make sure the phone is plugged into a usb2 port and not a 3.0
what got me is when i installed adb, it put adb files in a default directory on my hdd, so i just copied the files to the folder where where i had all files at See below
i used the .160 file to restore my phone and it worked..
now if phone isnt detected yet, you may still need files. have you tried iSocUSB-Driver ?
I followed the steps outlined in the link:
http
://valuestuffz.blogspot.com/2015/10/fix-zenfone-2-stuck-in-recovery-wipe-cache-partition.html?m=1
And everything appeared to have gone smoothly, however, now my phone just loads, and will not enter the home screen. I just have that ASUS IN SEARCH OF INCREDIBLE screen now. I was able to get into the recovery mode, but it doesn't appear to have worked. I also received the "Permission denied" errors mentioned in the link. Any suggestions?
My phone is now detected by the PC for the record.
didn't know of that but it has same steps but one I linkd easier to read and doesn't have wall of text.....
did you push the 3 required files via adb on bootloader screen ?
if so did you push the rom file in recovery once you selected adb sideload from the list ?
remember you have to follow the instruct exactly and be on correct screen when you push the files....
first boot takes some time
Pu$$nBooT$ said:
didn't know of that but it has same steps but one I linkd easier to read and doesn't have wall of text.....
did you push the 3 required files via adb on bootloader screen ?
if so did you push the rom file in recovery once you selected adb sideload from the list ?
remember you have to follow the instruct exactly and be on correct screen when you push the files....
first boot takes some time
Click to expand...
Click to collapse
I did push over 3 files, but when I downloaded the .160, it only had droidboot.img,and boot.img. I tried both .168 (Which may have been totally wrong, but had all 3 files) and .160 from the asus website where you can select firmware. I did the .160 most recently. I put the recovery.img, droidboot.img, and boot.img into the adb folder, and ran the following CMDs:
Fastboot erase cache
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
I then used adb sideload CMD to load the .160, and it reached 100% and said successful. I attached a screenshot of what the "permission denied" CMD looks like.
Pu$$nBooT$ said:
didn't know of that but it has same steps but one I linkd easier to read and doesn't have wall of text.....
did you push the 3 required files via adb on bootloader screen ?
if so did you push the rom file in recovery once you selected adb sideload from the list ?
remember you have to follow the instruct exactly and be on correct screen when you push the files....
first boot takes some time
Click to expand...
Click to collapse
Tonight after work I will try the links you suggested to me once more, and let you know the results. I sincerely appreciate all of your help here! Thank you very much!
anytime...
i never seen/encountered that error message before... try adb kill-server command if you run into any issues. when you start again it will load automaticaly... have you tried different usb ports? stay on usb2.0 when connected and try original oem cable that came with the phone. if you dont have it, try different micro-usb cables ( i had issues when i had my lg g3 being on a usb3 port, so i made sure mine was plugged in a 2.0 port )
Currently i am on beanstalk, and want to go back to stock.
I flashed the stock recovery via fastboot, but when i enter into Stock Recovery mode, it gives me Error icon.
The whole process is to flash the stock zip via sideload, but i am not able to enter the stock recovery.
The stock version i am trying to flash is 2.20.40.160.
I flashed all three files, Droidboot.img, recovery.img, boot.img.
And then turned the phone off, and now it is stuck on Asus screen. Urgent Help!!
btw when u see that error icon, nothing is actually wrong.... you have to hit 2 buttons simultaniously to enter recovery.
see > http://www.asus-zenfone.com/2015/03/zenfone-2-how-to-enter-recovery-wipe.html on step 6, this is normnal.. once u do button dance, you will enter step 7 and select flash via adb.. then you flash the rom file
Pu$$nBooT$ said:
btw when u see that error icon, nothing is actually wrong.... you have to hit 2 buttons simultaniously to enter recovery.
see > http://www.asus-zenfone.com/2015/03/zenfone-2-how-to-enter-recovery-wipe.html on step 6, this is normnal.. once u do button dance, you will enter step 7 and select flash via adb.. then you flash the rom file
Click to expand...
Click to collapse
Yeah, i looked it up, power + volume up. That did it. Thanks!
np...
Hi all! It took me a lot of time to finally being able to root this tablet. It's old, slow and practically unusable, but with some tricks it can be made much, much better. I'm going to explain what you need to do to root this tablet, and in case of brick (which happened to me many, many times) how to unbrick it. I even got to a point where I could not even boot into recovery mode, and only fastboot was working, that was scary, but I managed to get out. Every single file I will use will be bundled in a ZIP you can download, and I'll try to make sure this link stays up, because there's nothing more frustrating than wanting to make these things in the future only to find out the link is dead, along with all your hopes. Before we begin, a little disclaimer:
Code:
#You, and only you are responsible for everything that you do or happens to your tablet.
#If you screw up, I have a number of backups to help you recover, but if that's not enough don't point a finger at me.
#I will not be babysitting anybody to help restore their tablet or recover lost data.
#This process WILL wipe all of your data, do a backup before beggining.
#YOU HAVE BEEN WARNED!
1. ENABLING USB DEBUGGING
This is a very basic step, but it's needed if you want to even begin to do this. You'll need to go to "Settings -> About Phone". There, look for a line that says "Compilation Number" (or something like that) and tap it multiple times. You will see a message pop up saying "You are now a developer" (I wish it was that easy). Go back to the settings screen, you will see a new option appeared called "USB Debugging". Enable it, and make sure "Developer Options" are enabled too at the very top of the screen. Now, connect the tablet to your computer. You will see a message pop up asking for permission, tap "Always allow from this computer" and press "Allow".
That's it for this step.
2. SETTING UP ADB TOOLS AND MAKING SURE THEY WORK
Now that we have USB debugging enabled, and we have allowed our PC to access the tablet, we can begin setting up ADB. The required files are attached in the zip.
Extract the "platform-tools" folder and move it somewhere nice. Then open it, hold shift and right click in a white space and select the option "Open command window here". CMD will pop up, now type:
Code:
adb devices
It will probably say something about a server followed by a list of attached devices. If you see a serial number there, then great! ADB is working as it should. If not, make sure the tablet is connected, that USB Debugging is on, and if all else fails, try with another cable.
Now for the juicy part.
3. UNLOCKING THE BOOTLOADER
We will have to unlock the bootloader if we want to do anything here. Here's what to do. Type:
Code:
adb reboot fastboot
Wait until the tablet reboots into fastboot. Once there type:
Code:
fastboot oem unlock
fastboot oem unlock confirm
This should unlock the bootloader.
NOTE: This method of unlocking is reported to not work anymore, but I listed it anyway just in case, as it doesn't hurt to try. If this is not working for you, don't panic, it's normal, use the following code instead:
Code:
fastboot oem asus-go
fastboot oem asus-go confirm
This should work, and the bootloader should be unlocked now.
4. INSTALLING THE REQUIRED FIRMWARE
Now, your tablet may or may not have the required firmware for the procedure, but just in case we will flash one that's sure to work. If you followed along, you should be in fastboot mode right now. Type:
Code:
fastboot reboot
Your tablet should boot as normal, without any changes (unless the first bootloader unlock method worked for you, in which case it probably wiped all of your data). Now we can access ADB once again, so type:
Code:
adb reboot recovery
The tablet will reboot into recovery mode and you should see an image of wasted android with an open belly (if you don't see this it doesn't matter). You should see a list of options with blue text, you must use the volume keys to navigate this menu. If you don't see any options, press any volume key and they should appear. If instead of getting into recovery mode, the tablet just turned off, then go to the "Fixing recovery" section.
In this menu, you must select "Wipe data/factory reset". This will, obviously, wipe all of your data. Once that finishes, select the "Install update through ADB" option. Once that's done, make sure the "updated_firmware.zip" file is in the same directory as the "adb.exe" file, then type:
Code:
adb sideload updated_firmware.zip
This will install the firmware, it will take about 20 mins. Once finished, reboot the device. You may think it got bricked at this point, fear not, the first boot really takes this long (about 10 mins).
Once everything is done, the device should boot up and everything should be exactly as it was when you took it out of the box, meaning, it doesn't even remember your wifi password. Do a quick (but proper) set up and enable USB Debugging again, make sure to allow the PC again (and check the "always allow" box). Also, scroll down a bit more in the developer options section and look for one that says "Verify apps installed through USB" or something of that kind. Make sure it's unchecked. Now, we gotta install root.
5. ROOTING
The all holy root, finally here. Type this into the terminal:
Code:
adb reboot fastboot
You should be familiar with this process by now. Once in fastboot mode, type:
Code:
fastboot boot root.img
Once finished, reboot. You should boot up as a rooted user, hooray! Only one final step, we gotta give ourselves some means to control this new power, that's where the SuperSU app comes into play.
6. INSTALLING SUPERSU
Apparently, not every single SuperSU apk file works... but lucky for you, I managed to scout and bundle one that does, so use that one. Make sure the apk file is in the same folder as "adb.exe" (as with all of the previous files) and type:
Code:
adb install supersu-2-82.apk
Leave it a few mins, and you should see a "success!" message when it's finished. Open the SuperSU app and it will tell you that you need to update the binaries. Say yes to that, and when asked wether to do a "Normal" update or "TWRP" update, select normal. It should be successful and prompt you to reboot, do so.
That's about it, you now have root access in the ASUS ZenPad C 7.0.
NOTE: Every single attempt I made to make the SuperSU app a system app resulted in the app crashing and I needed to reinstall it again, do as you please.
Why would you even want to do this you might ask? Well, I personally used this to make a few tweaks with Kernel Auditor and L Speed, two apps that will let you customize the performance of the machine to its maximum... sacrificing battery of course. You can search online for the best configuration for you for these apps. With the right tweaks, it transforms from **** to usable, and you need root for all of this.
As a quick note, you might notice that the SuperSU pop up that prompts you wether to grant or deny root access to an app is delayed, that's just how life is with this machine, it's slow. As a tip, when an app is trying to acquire root access, go back to the home screen and open the SuperSU app, then go back to the app you were trying to give it access to, it should appear quicked that way. Sometimes it's so slow that the app says I don't have root, only to have the pop up appear 10 seconds later. Now... to a final chapter.
7. UNBRICKING
This would be the end of the story if nothing went wrong, you have a rooted tablet and you can now do whatever you want with it, but that's not how life is. **** happens, things can go wrong, and when they do, you better have a backup plan. I don't know how to get back your ex, but I know how you can unbrick your tablet if that should happen. Follow these steps if you want to recover this machine...
Code:
#This process will wipe all data, but you shouldn't care about that since you can't access it anyway.
So, if the tablet doesn't turn on and gets stuck at the boot up screen, what can we do? Well, let it sit at the boot up screen for a few mins, and then type in the terminal:
Code:
adb devices
If it's recognized, then type:
Code:
adb reboot recovery
If it's not recognized, press the power button and the volume down key until the tablet turns off. Once that happens, press the power button and the volume down key, when the logo appears, let go of the power button and keep the volume down key pressed, that should boot the tablet into recovery mode. If you got into recovery mode, skip to 7.2
7.1 FIXING RECOVERY MODE
Sometimes, (it happened to me), recovery mode is broken.... it just doesn't appear, no matter what you do you can't get into it. To fix this, we gotta flash it again. We gotta enter fastboot mode. One option is to boot up the device until it gets stucked and wait a few mins, then adb should be able to recognize it and you type:
Code:
adb reboot fastboot
If that's not the case, turn the tablet off and press power and volume up, that should get you to fastboot. Once there type:
Code:
fastboot devices
And the tablet should appear there, if it doesn't... well it better do. I don't really know what to do if it doesn't appear there, but there shouldn't be a reason for it not to. I guess you can try to enter fastboot once again, with the tabler connected from the beggining or something like that, let's just assume it does, and if it doesn't then I'm sorry to tell you that's homework you will have to do.
Once here, we must format the cache and the data partition, for that type the following:
Code:
fastboot format cache
fastboot format userdata
Now, we need to get the recovery files, grab them from the zip I gave you. The files in question are "recovery.bin" and "vrl.bin". We will start with vrl. Once the two formats are finished, type:
Code:
fastboot flash vrl vrl.bin
Followed by:
Code:
fastboot flash recovery recovery.bin
Once that's done, press the power button and volume down keys until the tablet turns off. Then, press them again until the logo appears, and when that happens let go of the power button, that should get you (finally) into recovery.
7.2 UNBRICKING (FOR REAL THIS TIME)
Well, now that everybody is on the same page, and we could get to recovery mode, it's time to repeat some steps really... Follow the procedure from step 4 onwards (from the part that tells you to go to recovery). So, wipe data and apply that damn zip with sideload, the tablet should work now.
That's all I have to offer guys. I'm not a developer, I'm just a guy with a bunch of free time on his hands, so I was able to gather all of this information and (most importantly) files so you can root and fix this god damn tablet. Until the next one!
FINAL NOTE: In the files I included, there's a TWRP.img file. This is the TWRP custom recovery. As far as I know, this version should work with this tablet, but I was unable to flash it and make it work. IF YOU WANT TO TRY THIS DO SO AT YOUR OWN RISK, IT'S HIGHLY PROBABLE THAT THIS WILL RESULT IN BRICKING YOUR TABLET AND BREAKING THE STOCK RECOVERY, IN WICH CASE YOU WILL NEED TO FOLLOW THE STEPS STATED IN THIS GUIDE.
I couldn't upload the files as an attachment directly... sorry.
The "updated_firmware.zip" file is added as a separate download because it's a bigger file, and I prefer to let people decide if they even want it in the first place.
updated_firmware.zip
Everything else
None of the 8 drivers from Intel or Google detect the device in fastboot mode. I tried fixing this tablet years ago and had the fastboot drivers. As far as I know I have the same ones. These all loaded with no problem, but I could never get ADB Device to detect it in fastboot mode
Google: Android ADB Interface | Android Bootloader Interface | Android Composite ADB Interface
Intel: Android ADB Interface | Android Bootloader Interface | Intel AndroidADB Interface | Intel Android Bootloader Interface | Intel Android Composite ADB Interface
neghvar said:
None of the 8 drivers from Intel or Google detect the device in fastboot mode. I tried fixing this tablet years ago and had the fastboot drivers. As far as I know I have the same ones. These all loaded with no problem, but I could never get ADB Device to detect it in fastboot mode
Google: Android ADB Interface | Android Bootloader Interface | Android Composite ADB Interface
Intel: Android ADB Interface | Android Bootloader Interface | Intel AndroidADB Interface | Intel Android Bootloader Interface | Intel Android Composite ADB Interface
Click to expand...
Click to collapse
Make sure you enable usb debugging, no driver will work without that enabled.
tralph3 said:
Make sure you enable usb debugging, no driver will work without that enabled.
Click to expand...
Click to collapse
Not possible. This hangs during boot up or I can enter fast boot mode. It has been like this for years. Basically a soft brick. I tried to fix this years ago as stated above, but having seen this latest post about it, I decided to try again. But this time, I cannot find a fastboot driver that shows the device as attached when I run ADB devices
neghvar said:
Not possible. This hangs during boot up or I can enter fast boot mode. It has been like this for years. Basically a soft brick. I tried to fix this years ago as stated above, but having seen this latest post about it, I decided to try again. But this time, I cannot find a fastboot driver that shows the device as attached when I run ADB devices
Click to expand...
Click to collapse
Be aware that when in fastboot mode, adb devices never lists anything, you must use "fastboot devices"
tralph3 said:
Be aware that when in fastboot mode, adb devices never lists anything, you must use "fastboot devices"
Click to expand...
Click to collapse
Yep! That's where I was messing up. Thank you.
And the tablet is now working. Thank you very much.
One last question though. I tried to install the twrp.img file included in the pack
fastboot flash recovery TWRP.img
Here is what I got
Sending 'recovery' (26588 KB) (bootloader) Ready to receive: 0x019f7000 size of data
OKAY [ 0.741s]
Writing 'recovery' (bootloader) Flashing partition: recovery
FAILED (remote: ' Download image size is large than partition size')
fastboot: error: Command failed
How do I get around this if the image file is too large?
neghvar said:
Yep! That's where I was messing up. Thank you.
And the tablet is now working. Thank you very much.
One last question though. I tried to install the twrp.img file included in the pack
fastboot flash recovery TWRP.img
Here is what I got
Sending 'recovery' (26588 KB) (bootloader) Ready to receive: 0x019f7000 size of data
OKAY [ 0.741s]
Writing 'recovery' (bootloader) Flashing partition: recovery
FAILED (remote: ' Download image size is large than partition size')
fastboot: error: Command failed
How do I get around this if the image file is too large?
Click to expand...
Click to collapse
Yeah I never could get around it either. I never could install a custom recovery on this tablet, it just wasn't made for it. But hey, root is cool.
Work?
Still working?
jerryspring said:
Still working?
Click to expand...
Click to collapse
Why wouldn't it? This tablet ain't gonna change. Everything should work no problem.
Hi, any custom rom for this device to make it useful ?
It is in my drawer for more than 2 years and I just do not know what with it
Also how to play with settings in root mode so I can make it faster ?
Hey folks,
I recently followed this guide and a couple of issues.
First, I had expected all my data to be gone, which is fine. But it wasn't. I seemed to have gotten all the way through without it being reformatted, and this makes me suspect I never really achieved all the goals.
One thing I should note, in recovery boot, I had to use the volume button to select a source. No big deal, but it had not worked until I guessed I needed to do that.
Oh, and another thing is I had to install the driver package, and then after, once it was rebooted into fastboot, manually guide the device manager to select from list.
It seems after complete shutdown and then a fresh bootup, my SuperSU software was gone. So, is this only a tethered root boot? Is there a completely untethered?
After rebooting again, it seems my device will not complete booting, but I will give it some more time. I may have bricked it, though I have no idea how lol. All I did was enable USB debugging again and issued the reboot command.
I know this is an old guide, and probably long forgotten by most participants, but I recently got one of these tablets online, open box but new or like new, for around $20, and I would like to get it rooted because otherwise, it is extremely sluggish and the battery drains very fast. I read online it is google play services at fault, but I do not know for sure.
Anyway, if anyone has any updated info or alternative method to achieve full root access untethered, please advise. Unless this guide is that, in which case I just need to try again. Just out of curiosity, what is the TWRP.img for?
Here is some background.
I ordered an LG G7 ULM off of ebay a few days ago. When I got it, I noticed that it was an LG G7 Sprint that was converted to ULM. (Which is typical of eBay). I decided to flash the latest ULM firmware to the device by downloading the latest kdz and flashing with LGup. What I didn't realize until later is that I flashed the "Brightpoint" ULM version. Knowing this, I wanted to flash the non Brightpoint version, but when I try getting into download mode, it doesn't work. It only shows the G7 logo, then shows the battery charging symbol.
Additionally, I am in USB debugging mode and have OEM unlock on in developer options.
Things I have tried:
Holding volume up and then plugging USB
Holding volume down and plugging in USB
Holding volume up and power button
Holding volume down and power button
Reboot fastboot via adb
Also, when i try using LGup without download mode it gives and error "spc code does not match"
Does anyone know how to fix this?
https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303
If you try ti flash when phone is not in download mode you get "spc code does not match" error.
First method is correct
"Holding volume up and then plugging USB" If that doesn't work try adb reboot download (I don't think there is download option with fastboot command or not supported by LG G7)
If you have ADB installed,connect phone with USB cable
1)Check your phone is listed in with command
Adb devices
2) then run this command
adb reboot download
sampal said:
If you try ti flash when phone is not in download mode you get "spc code does not match" error.
First method is correct
"Holding volume up and then plugging USB" If that doesn't work try adb reboot download (I don't think there is download option with fastboot command or not supported by LG G7)
If you have ADB installed,connect phone with USB cable
1)Check your phone is listed in with command
Adb devices
2) then run this command
adb reboot download
Click to expand...
Click to collapse
1. Adb devices shows my device.
2. I tried the adb reboot download. It just reboots normally. Shows lg logo then my phone is booted up.
None of the fastboot commands word because I can't get into download mode.
onenite said:
1. Adb devices shows my device.
2. I tried the adb reboot download. It just reboots normally. Shows lg logo then my phone is booted up.
None of the fastboot commands word because I can't get into download mode.
Click to expand...
Click to collapse
If you have one of the models with OEM unlock inside the developer menu, you're wasting your time because it does nothing. I don't even know why it's there because the LG G7 ThinQ does not have fastboot mode baked in.
Try running a fastboot command and you will see. You have to get past the bootloader to access anyting to do a root and this is not possible on most of the phones here . Also you do not run these commands from download mode I don't believe, they would usually be done when in fastboot or recovery mode.
The only mode you're probably going to get into is download mode. It would be for manually upgrading firmware. You can go into that mode by holding power and Volume +. I tried for three days straight until I stumbled upon another Canadian who was able to root his phone but he had to use a special box and connectors.
There is no fastboot or recovery. All you can find is download mode and safe boot. I wish you the best of luck but if you have the same variant that I do and most of Canada does if it was purchased here then you will not be able to access fastboot because it does not exist. Don't take my word for it though, do your research and you will see I am speaking the truth. Or you can kill yourself and rip out your hair trying to get fastboot to to load but you will not succeed in doing anything but ending up bald. Luckily I shave my head or else I would have done that. Good luck on your research and if you should get fastboot to do anyting please post it in here for everyone to see so we can praise you and root our own phones also. Cheers my friend.
I didn't read back deeply but it sounds like you're attempting what I did, and use modded boot.img files to further gain access to what we need to root the phone. This is true as for what we need to do, but most who have flashed these images have either ruin their devices totally or had to reflash stock firmware. There were a few that got lucky and let's talk firmware fixed the issue but most phones that broke are probably in a landfill now. Please do share if you succeed in anyting we haven't already tried. I tried flashing to a firmware that does have fast boot capability but it did not work because fastboot is built into the phones and the firmware for any particular country has no effect on whether you can root your phone or not. Just before this I mentioned the boot.img method and I'm guessing the command you are running is something like fastboot flashroot_a boot.img and then typing the same command a second time but only with a letter b instead of an a. This method will not work either so please share if you discover a third method that no one else has discovered yet. I would donate money to you because you would basically be the developer of the root method that actually works.
TWiiTCH said:
If you have one of the models with OEM unlock inside the developer menu, you're wasting your time because it does nothing. I don't even know why it's there because the LG G7 ThinQ does not have fastboot mode baked in.
Try running a fastboot command and you will see. You have to get past the bootloader to access anyting to do a root and this is not possible on most of the phones here . Also you do not run these commands from download mode I don't believe, they would usually be done when in fastboot or recovery mode.
The only mode you're probably going to get into is download mode. It would be for manually upgrading firmware. You can go into that mode by holding power and Volume +. I tried for three days straight until I stumbled upon another Canadian who was able to root his phone but he had to use a special box and connectors.
There is no fastboot or recovery. All you can find is download mode and safe boot. I wish you the best of luck but if you have the same variant that I do and most of Canada does if it was purchased here then you will not be able to access fastboot because it does not exist. Don't take my word for it though, do your research and you will see I am speaking the truth. Or you can kill yourself and rip out your hair trying to get fastboot to to load but you will not succeed in doing anything but ending up bald. Luckily I shave my head or else I would have done that. Good luck on your research and if you should get fastboot to do anyting please post it in here for everyone to see so we can praise you and root our own phones also. Cheers my friend.
I didn't read back deeply but it sounds like you're attempting what I did, and use modded boot.img files to further gain access to what we need to root the phone. This is true as for what we need to do, but most who have flashed these images have either ruin their devices totally or had to reflash stock firmware. There were a few that got lucky and let's talk firmware fixed the issue but most phones that broke are probably in a landfill now. Please do share if you succeed in anyting we haven't already tried. I tried flashing to a firmware that does have fast boot capability but it did not work because fastboot is built into the phones and the firmware for any particular country has no effect on whether you can root your phone or not. Just before this I mentioned the boot.img method and I'm guessing the command you are running is something like fastboot flashroot_a boot.img and then typing the same command a second time but only with a letter b instead of an a. This method will not work either so please share if you discover a third method that no one else has discovered yet. I would donate money to you because you would basically be the developer of the root method that actually works.
Click to expand...
Click to collapse
Thanks for the reply.
I was reading into flashing the laf.img file which would fix the download mode not working, but I'm unable to gain root, so that isn't really an option.
I guess for now, I'm stuck with this firmware version. But, at least I'm on the latest pie version... Hopefully there will be a fix for it, or maybe someone will know how to fix this.
I have heard that you can buy for a service to fix this for around $30. But I don't think I would trust someone doing changes to my phone without a guarantee.
Help me
I have the same problem too, my phone is Verizon variant and I can't get to download mode
babykut said:
I have the same problem too, my phone is Verizon variant and I can't get to download mode
Click to expand...
Click to collapse
OK, I have solved it by myselft, you can use ADB (adb reboot recovery) to restart your phone and then holding volume up key to boot into download mode, hope it work for you
babykut said:
OK, I have solved it by myselft, you can use ADB (adb reboot recovery) to restart your phone and then holding volume up key to boot into download mode, hope it work for you
Click to expand...
Click to collapse
Oh my God, you are a genius. I can't thank you enough.... It worked!!!
onenite said:
Oh my God, you are a genius. I can't thank you enough.... It worked!!!
Click to expand...
Click to collapse
You are welcome
babykut said:
OK, I have solved it by myselft, you can use ADB (adb reboot recovery) to restart your phone and then holding volume up key to boot into download mode, hope it work for you
Click to expand...
Click to collapse
Thank you bro
babykut said:
OK, I have solved it by myselft, you can use ADB (adb reboot recovery) to restart your phone and then holding volume up key to boot into download mode, hope it work for you
Click to expand...
Click to collapse
When exactly do you hit the volume up button?
it doesnt seem to work for me
landonloco said:
When exactly do you hit the volume up button?
it doesnt seem to work for me
Click to expand...
Click to collapse
1) Give "adb reboot recovery" command
2) Press Enter
3) The display's phone shutting down
4) Hold the up volume down until you see the little label "download mode"
It works!
Jengirl said:
1) Give "adb reboot recovery" command
2) Press Enter
3) The display's phone shutting down
4) Hold the up volume down until you see the little label "download mode"
It works!
Click to expand...
Click to collapse
Wuh. It could work, but my question is, HOW THE HELL DID YOU GET YOUR LAPTOP/PC TO DETECT THE CELL PHONE!!!!!!
PD: I Have the same problem, plis help me
Jengirl said:
1) Give "adb reboot recovery" command
2) Press Enter
3) The display's phone shutting down
4) Hold the up volume down until you see the little label "download mode"
It works!
Click to expand...
Click to collapse
it shows no command screen