Related
As noted Here, and following on, I managed to get updated through to the OTA ICS, and attempted an upgrade to the 3.1 FlexRom.
After some attempts at fixing things, I'm at the point right now, where the issue seems to be in the boot-up sequence.
I have the following variables in play:
* I have fastboot access, but no ADB.
* The tab is now stuck in a continuous loop of the ANDROID boot loader screen.
(previously, it was the FlexRom bootloader)
* The USB at first was trying to install the A500 drivers, and now fails on "MTP USB Device" installation. It fails, but because it's unlocked, I have the first point available.
* CWM no longer loads, nor can I access any recovery functions.
(When CWM was loading, I used it to flash back to the stock OTA rom, rather than attempt another upgrade)
Attempted:
*using fastboot to update the rom via the update command. FAIL.
*using fastboot to run the OEM unlocker. The computer side says "OKAY" but nothing changed on the screen.
*fastboot WILL reboot the tab if given the command, so I know something is getting through, even with the failure of the USB cord to "work"
Have not attempted:
* Hard reset via the little hole. (I honestly don't think it will work)
* Methods I'm not aware of.
So to sum up, I'm stuck in a boot loop and can't get out.
Ideas?
Did you remove bootloader.blob and the recovery folder,from that stock OTA that you flash trough CWM?
I think you are not.That's why you're in this situation.Your bootloader is locked again, and you have the stock recovery (or may be broken recovery).
Try to do hard reset (the real hard reset) with the lock screen button+volume and power (search this forum or google it).It may help you .
Did you try other fastboot commands like: 'fastboot flash recovery recovey.img' or 'fastboot flash boot boot.img' (boot.img and recovery.img must be in the same folder with fastboot to do it this way) what they return?
If above doesn't help you still has a chance with nvflash but you must read this thread after post #48
Hope this is helpful enough!
sending 'recovery' (6144 KB)... FAILED (remote: (00000002))
(for 'fastboot flash recovery recovery.img')
Now it did reboot, and it seems I may be locked again.
This error popped up:
Fastboot: Not support the command in Lock mode
Failed to process command download: hexidecimal error code
No errors on a proper 'hard' reboot, it erased userdata and cache, and is letting me into the setup, so that's probably a good thing.
and indeed it is. I'm back into the OS, and it booted up normally.
I thought I had tried it before, but apparently, it didn't take.
Thanks!
Hi there,
I have a problem that my LG will not boot the device is stuck at the logo, I've also done a hardware reset but the process also depends on the logo proof and 10min not happened.
In the download mode, I'm not coming.
About the fastboot mode I try to start TWRP, but it appears the TWRP logo and nothing else happens.
How did you manage to get it to this point? What did you do before it didn't boot anymore?
Also, if you manage to get adb access somehow you can just reflash the recovery again
I ran a SuperSU update and then he appeared dialog that I should restart the system and since I have the problem.
How can I flash the recovery again?
If I want to flash TWRP on the fastboot mode, only the TWRP logo and then nothing happens appears.
So you cant enter download mode or recovery? And you cant turn on phone?
No download mode is not only possible fastboot mode. If I we want to install Recovery in fastboot mode, shown below
Command: fastboot flash recovery recovery .img
Error on LG G3:
Error: Command never completed
Error: Auto CM012 error
Error: Command completed with errors
Error: Command timeout error
Errror:Command completed with errors
Failed to send stop command
Failed Writing block @1
SourceCoder said:
No download mode is not only possible fastboot mode./QUOTE]
Could you please explain this.
Is comma missing somewhere?
Click to expand...
Click to collapse
The following screen appears:
lgg3root.com/wp-content/uploads/2014/08/howto-unroot-unbrick-lgg3-2-690x492.jpg
And then immediately this screen:
android-hilfe.de/attachments/root-custom-roms-modding-fuer-lg-g3/345262d1415303724-lg-g3-kein-download-modus-mehr-img_20141106_093950.jpg
This screen does not appear:
androidheadlines.com/wp-content/uploads/2014/07/LG-G3-Download-Mode-AH-1.jpg
SourceCoder said:
I ran a SuperSU update and then he appeared dialog that I should restart the system and since I have the problem.
How can I flash the recovery again?
If I want to flash TWRP on the fastboot mode, only the TWRP logo and then nothing happens appears.
Click to expand...
Click to collapse
Something does not compute in this at all. SuperSU should not have caused your phone to brick like that.
Is there something else you are not telling us about how your phone was set up? Were you doing anything before you updated SuperSU? This looks like a case of where you flashed the wrong image on your phone, if you ask me.
SuperSU is not phone specific, so I'm having a hard time believing SuperSU did this.
Something else must have happened that you are not telling us. You need to lay out in order, everything you did to your phone up to the point of updating SuperSU.
Also, SuperSU asks how to update: normal or via recovery. Which way did you choose? Either one shouldn't matter, but it's a start.
I had the ROM KNVIRUS V11, since I got the message that an update to SuperSU are available. The update I installed then I get the message that the device must be restarted for the update to be finished and since I have the problem.
I wanted to start the download mode just in fastboot mode, unfortunately without success.
command to start the download mode: fastboot boot laf.img
Result: fs2.directupload.net/images/141219/p68gn6y5.jpg
What I do not understand whatever I command in fastboot mode I enter I get these error messages:
Error: Command never completed
Error: Car CM012 error
Error: Command completed with errors
Error: Command timeout error
Errror: Command completed with errors
Failed to send stop command
Failed writing block @ 1
SourceCoder said:
I had the ROM KNVIRUS V11, since I got the message that an update to SuperSU are available. The update I installed then I get the message that the device must be restarted for the update to be finished and since I have the problem.
I wanted to start the download mode just in fastboot mode, unfortunately without success.
command to start the download mode: fastboot boot laf.img
Result: fs2.directupload.net/images/141219/p68gn6y5.jpg
What I do not understand whatever I command in fastboot mode I enter I get these error messages:
Error: Command never completed
Error: Car CM012 error
Error: Command completed with errors
Error: Command timeout error
Errror: Command completed with errors
Failed to send stop command
Failed writing block @ 1
Click to expand...
Click to collapse
Did you flash the correct laf.img file for your model of phone? If not, that could be part of it. What model of the G3 are you using and where exactly did you obtain the laf.img file from?
SuperSU update should I install because the PlayStore has shown that there is an update.
laf.img I downloaded here: http://forum.xda-developers.com/showthread.php?t=2766437
I found a thread has to ängliches problem: http://forum.xda-developers.com/lg-g3/general/guide-how-to-restore-download-mode-t2897257
SourceCoder said:
SuperSU update should I install because the PlayStore has shown that there is an update.
laf.img I downloaded here: http://forum.xda-developers.com/showthread.php?t=2766437
I found a thread has to ängliches problem: http://forum.xda-developers.com/lg-g3/general/guide-how-to-restore-download-mode-t2897257
Click to expand...
Click to collapse
Well, there you go. I have NO idea for what version of the G3 that thread was for. The guy never states which version it is. You do not, repeat, do NOT flash anything to system, boot, etc for this phone unless you know for sure it's for YOUR model of the G3. There are various models of the G3. For example, mine is the Verizon model (VZ985). There is an AT&T model (DS855), and numerous others, especially for those overseas. I would not and should not flash the DS855 boot image to my VS985 boot image. It will brick the phone as you have found out the hard way from what I can tell.
You just flashed something you have NO idea which version it was for. You may have completely bricked your phone. I'm not entirely sure, but you need to find the correct stock images for your phone and flash them back.
You need to go here and figure out which model of G3 you have:
http://forum.xda-developers.com/showthread.php?t=2791269
After that, you need to go and find the correct stock image files and flash those back onto your phone. Since this are NOT img files, you cannot fastboot flash them. You muse use either KDZ or TOT files depending on which ones are available for your model of phone:
http://lg-firmware-rom.com/
or
http://storagecow.eu/index.php?dir=Xda/LG+G3/Stock/
Then, you have to use the correct tool to flash these files depending on if they are KDZ or TOT file:
http://forum.xda-developers.com/showthread.php?t=2785089
Hopefully, flashing back to the correct stock image will fix you up. However, you better make darned sure which model of phone you have BEFORE you even attempt it. Once you figure out which model of G3 you have, post here and ask. Otherwise, you could bork your phone up even worse to where it may not be recoverable. Hopefully, it's not at that state right now.
I have LG G3 16GB EU version.
As I have written on the first page, I get nothing into download mode so I can not flash it.
What I can not understand why no command in fastboot mode works no matter what I type, I always get the error message: FAILED (remote: flash write failure)
SourceCoder said:
I have LG G3 16GB EU version.
As I have written on the first page, I get nothing into download mode so I can not flash it.
What I can not understand why no command in fastboot mode works no matter what I type, I always get the error message: FAILED (remote: flash write failure)
Click to expand...
Click to collapse
Again, did you verify with the link you posted for the image file that it was indeed for YOUR model of your phone? If not, you probably have bricked it.
You need to go and follow the links I posted which tell you how to flash back to stock.
There was no reason to go into fastboot mode for SuperSU. I don't know why you felt you had to do that.
Also, the second link you posted has the thread pretty much deleted. The OP said he was incorrect in what he posted (whatever it was I don't know since he deleted it), so it was removed due to it not working as stated.
Go back to the links I posted to flash back to stock on your model. If what you say you have is the European model, then this would be the KDZ file you want:
http://storagecow.eu/Xda/LG G3/Stock/Europe Common 16G D85510A_00.kdz
I would verify for sure that is what your phone is before continuing or else, you'll bork your phone up even worse than it is already.
The boot image you flashed is probably for the Korean version of the phone and that's why everything is messed up.
If you are not sure on how to do this, then you might want to find someone near you who does.
Just remember, just because a post says it's for the G3 doesn't mean it's specifically for YOUR model of the G3. You need to verify for sure that it is. Most have the model number in the thread's title.
LG G3 Fastboot
well i have the same problem for a week every command was giving error, but then used this command "fastboot boot twrp.img" i was able to get into the recovery from there i wiped everything and then rebooted but nothing happened but then somehow (I DO NOT KNOW HOW) i was able to get into the download mode so i flashed the stock firmware of my lg g3 D855 and everything was going good and i was just setting up my phone and then suddenly it turned off and again booted into the fastboot mode, WTF , i was just installing some apps from playstore man, and now when i try to boot into twrp it is just stuck on twrp image on the whole screen
[1700] fastboot mode started
razaaliarain said:
well i have the same problem for a week every command was giving error, but then used this command "fastboot boot twrp.img" i was able to get into the recovery from there i wiped everything and then rebooted but nothing happened but then somehow (I DO NOT KNOW HOW) i was able to get into the download mode so i flashed the stock firmware of my lg g3 D855 and everything was going good and i was just setting up my phone and then suddenly it turned off and again booted into the fastboot mode, WTF , i was just installing some apps from playstore man, and now when i try to boot into twrp it is just stuck on twrp image on the whole screen
Click to expand...
Click to collapse
i was facing the same problem and "fastboot boot twrp.img" worked. it took me to twrp where i flashed my ROM. i had freaked out that my G3 was bricked.
_narisha_ said:
i was facing the same problem and "fastboot boot twrp.img" worked. it took me to twrp where i flashed my ROM. i had freaked out that my G3 was bricked.
Click to expand...
Click to collapse
But now i am stuck again on fastboot mode and this time i was not rooted and did not had twrp installed so now when i try to use the "fastboot boot twrp.img " my device will reboot and then will be stuck on twrp logo on the screen
I have the same problem...
I ran stock OTA update 20f, since a couple of weeks ago. While I had my phone on the table and it was runing voice recorder soft it restarted once and then after a couple of minutes again. This time it never booted but stuck at the LG screen.
Never rooted, never installed anything other than the OTA 20e and 20f updates. I have not flashed anything to the phone other than the official OTA.
Doesn't boot to anything other than fastboot. Recovery starts but after confirming twice it reboots and stuck still.
If I boot to Download Mode it goes to fastboot, if I wait long enough on regular boot that only shows the LG logo it will eventually go to fastboot.
Running "fastboot.exe boot openrecovery-twrp-2.8.4.0-d855.img" gives me the same error messages, stuck at the TWRP logo screen. I found the ADB port is connected but when running "adb devices" it says "LGD855..... offline". I didn't enable ADB before the device crashed and I can't enable it in TWRP because it doesn't start properly.
I have the 32GB D855 European unlocked. I belive this is hardware problem and will send it for repairs.
SourceCoder said:
I have LG G3 16GB EU version.
As I have written on the first page, I get nothing into download mode so I can not flash it.
What I can not understand why no command in fastboot mode works no matter what I type, I always get the error message: FAILED (remote: flash write failure)
Click to expand...
Click to collapse
Oeps, `flash write failure` brings back memory`s of the emmc failure with Samsung devices where the sdcard is no longer readable and can not be written on. Send it in for repair, there is no other way and they`ll probably replace the motherboard.
gee2012 said:
Oeps, `flash write failure` brings back memory`s of the emmc failure with Samsung devices where the sdcard is no longer readable and can not be written on. Send it in for repair, there is no other way and they`ll probably replace the motherboard.
Click to expand...
Click to collapse
That's right. I tested to boot Philz recovery and it freezes at the text.
Mine says actually:
Error: Command never completed
Error: Auto CMD12 error
Error: Command never completed
Error: Command timeout error
Failed to send stop command
Failed reading block @ 1
mmc read failure misc 2048
The CMD12 is according to emmc spec a "Stop command".
So this is a hardware fault and not a software one.
I've searched this and other forums, and tried virtually everything that has been suggested or that I can think of.
I have a Zenfone 2 Laser ZE551ML rooted. Phone has worked like a dream. Installed TWRP 3.0, made and saved several backups in several different places, internally and externally.
Two days ago, flashed a TWRP recovery (I was looking to get back some data I had deleted inadvertently), seemed to go well until it booted, and could not get past the screen that says "Fastboot Mode!!!". Connected to a PC and was able to execute fastboot commands; supposedly can flash various recoveries, and seemingly does so, with everything looking right on the PC, and the phone actually rebooting. But always stops at the same screen.
ADB, on the other hand, shows no devices listed. Every command results in "Error: Missing Device."
I have done everything I can think of...uninstalled and reinstalled the ADB drivers, used different ADB drivers, removed the external SD card, removed the battery (which is the ONLY way the phone will shut off...pressing the on/off button for 10 seconds just results in it booting up to the same screen. Have tried the fastboot wipe command, again it seems to do so, but always comes back to the same screen. Fastboot flashing a recovery.img appears to successfully write a recovery, then goes to same screen upon reboot.
Any ideas? I've only had this phone a couple of weeks, and really like it. But flashing what was apparently a bad TWRP backup seems to have destroyed it.
Thanks so much for any suggestions!
i have the same problem.. please help!
i have the exact same problem you had.. please tell me how you restored it
As i have a similar problem i cannot help you on the technical side.
But isn't the laser 551 KL instead of ML. Maybe you flashed the wrong files trying to restore the phone
BeachNYC said:
I've searched this and other forums, and tried virtually everything that has been suggested or that I can think of.
I have a Zenfone 2 Laser ZE551ML rooted. Phone has worked like a dream. Installed TWRP 3.0, made and saved several backups in several different places, internally and externally.
Two days ago, flashed a TWRP recovery (I was looking to get back some data I had deleted inadvertently), seemed to go well until it booted, and could not get past the screen that says "Fastboot Mode!!!". Connected to a PC and was able to execute fastboot commands; supposedly can flash various recoveries, and seemingly does so, with everything looking right on the PC, and the phone actually rebooting. But always stops at the same screen.
ADB, on the other hand, shows no devices listed. Every command results in "Error: Missing Device."
I have done everything I can think of...uninstalled and reinstalled the ADB drivers, used different ADB drivers, removed the external SD card, removed the battery (which is the ONLY way the phone will shut off...pressing the on/off button for 10 seconds just results in it booting up to the same screen. Have tried the fastboot wipe command, again it seems to do so, but always comes back to the same screen. Fastboot flashing a recovery.img appears to successfully write a recovery, then goes to same screen upon reboot.
Any ideas? I've only had this phone a couple of weeks, and really like it. But flashing what was apparently a bad TWRP backup seems to have destroyed it.
Thanks so much for any suggestions!
Click to expand...
Click to collapse
fastboot --cmdline "lge.kcal=0|0|0|x" boot twrp.img
where TWRP.img is the directory of twrp
then you should get back to TWRP
flash TWRP image again in TWRP itself because the method on line 1 only temporary flashes TWRP and will auto discard TWRP after a reboot
I've been trying to install TWRP and Magisk to the Razer phone for upwards of 3 days now. I cannot get anything to flash through fastboot to the phone no matter what I try. At one point I even said screw it and tried flashing the stock boot image back over to re-lock my bootloader, but no luck, still won't flash.
I was originally following this tutorial here but during the flashing of the boot image it kept failing. Then I tried following the "foolproof" guide found here
I either ended up with the error of "no such file or directory" or "too many links" or "unable to identify current slot". Did a ton of Googling but ultimately came up with no solutions.
I have Android SDK and development studio installed. I have the google drivers installed. I have the Razer phone drivers installed and I have ADB and Fastboot installed.
I have all the files I need on the SD card, and when I'm flashing everything I have the files I need placed in the same folder as the ADB\Fastboot files.
I have my bootloader unlocked, developer mode on and USB debugging enabled. I am using a USB Type A to Type C cable as recommended (made by Anker if it matters). I've tried all 3 USB ports on my laptop. I've even disabled Antivirus.
I have flashed many Android devices in the past and none have given me such a headache as this one. I'm even more ticked off that I can't even get the factory boot image back over to re-lock the bootloader after now realizing that I can't install Netflix anymore because they wen't and blocked installations for Rooted android users (for whatever ridiculous reason).
I will say that for whatever reason that when I go to open command prompt by using the shift+right click I only get the option to use Windows Powershell, not Command Prompt. I also have to put a .\ in front of every command I send. I'm unsure why, but I found no work around for it.
I'd like to try to get the TWRP and Magisk installed. I'm sure I can force Netflix to install over to the phone using another method.
Open to any suggestions!
FireGuy0723 said:
I've been trying to install TWRP and Magisk to the Razer phone for upwards of 3 days now.
Click to expand...
Click to collapse
I feel for you as when things don't work, like someone says they do, it's frustrating. I personally wouldn't be doing everything through power shell but would instead press Windows Key+R to bring up the "Run" dialog box then type "cmd" for command prompt. Trying to restore "command prompt here" to Windows 10 seems stupidly hidden. I'm just not sure if using powershell is messing with your progress.
Second thought is that your Razer phone drivers may not be installed correctly. For me I spent days/hours with my main PC, I then tried another PC and got my phone flashed in minutes. What would happen is that I could send "adb" commands without issue but some of the "fastboot" commands were not working. So at the critical times when it's trying to flash the different portions of our phone, some of them were successful while the others were giving little errors here and there.
I spent a lot of time updating my adb and fastboot commands to newer ones because it seems every time you download someones resources you get a different version. Also the more phones you have owned the more times you have installed specific USB drivers for those phones and they are now hanging around messing things up. There are programs such as USBDeview that will allow you to uninstall those old drivers. For me I had HP drivers from an old tablet, OnePlus drivers, LG drivers, etc.
Munk0 said:
I feel for you as when things don't work, like someone says they do, it's frustrating. I personally wouldn't be doing everything through power shell but would instead press Windows Key+R to bring up the "Run" dialog box then type "cmd" for command prompt. Trying to restore "command prompt here" to Windows 10 seems stupidly hidden. I'm just not sure if using powershell is messing with your progress.
Second thought is that your Razer phone drivers may not be installed correctly. For me I spent days/hours with my main PC, I then tried another PC and got my phone flashed in minutes. What would happen is that I could send "adb" commands without issue but some of the "fastboot" commands were not working. So at the critical times when it's trying to flash the different portions of our phone, some of them were successful while the others were giving little errors here and there.
I spent a lot of time updating my adb and fastboot commands to newer ones because it seems every time you download someones resources you get a different version. Also the more phones you have owned the more times you have installed specific USB drivers for those phones and they are now hanging around messing things up. There are programs such as USBDeview that will allow you to uninstall those old drivers. For me I had HP drivers from an old tablet, OnePlus drivers, LG drivers, etc.
Click to expand...
Click to collapse
I've been messing with it today a bunch. I am back to following the "foolproof" guide and this time I have completely uninstalled all my old drivers for anything android or USB or ADB related and reinstalled everything.
All commands work, I am using command prompt now.
What I am getting hung up on now is even after pushing all three files to the SD card, I run the command "fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot" and it bounces back with " Failed: Write to device failed (no such file or directory)"
I've double checked the file names numerous times. I have no idea what I am doing wrong now. I have tried the command "fastboot boot twrp-3.2.1-0-cheryl.img" as stated in the other tutorial and it bounces back with "failed to identify current slot".
So I'm making progress at least. I'm trying to follow the first set of instructions listed in the fool proof guide but still no luck. I also tried the "clean method" listed below on that guide and that one doesn't work either. Apparently the Fool Proof guide thinks I'm a fool!
FireGuy0723 said:
What I am getting hung up on now is even after pushing all three files to the SD card, I run the command "fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot" and it bounces back with " Failed: Write to device failed (no such file or directory)"
Click to expand...
Click to collapse
I believe that when you run "fastboot flash boot twrp-3.2.1-0-cheryl.img" you are pushing the file called "twrp-3.2.1-0-cheryl.img" that is sitting on your PC's C: or whichever drive you are currently sitting in to the Razer Phone. So make sure the file is in the same directory as where you are running that command. This will then transfer it to the Razer and will reboot into TWRP.
But after you reboot into TWRP you will want to flash the version you have sitting within your SD card to the "recovery" partition. That way it is permanent.
Munk0 said:
I believe that when you run "fastboot flash boot twrp-3.2.1-0-cheryl.img" you are pushing the file called "twrp-3.2.1-0-cheryl.img" that is sitting on your PC's C: or whichever drive you are currently sitting in to the Razer Phone. So make sure the file is in the same directory as where you are running that command. This will then transfer it to the Razer and will reboot into TWRP.
But after you reboot into TWRP you will want to flash the version you have sitting within your SD card to the "recovery" partition. That way it is permanent.
Click to expand...
Click to collapse
I was finally able to get the phone to accept a flash! I ended up saying screw it and dug a old laptop out, fresh install of windows and installed all the proper drivers onto it.
It worked almost flawlessly. It was able to correctly send the twrp.img file and the phone was able to boot into twrp which is about as far as I got. As it was attempting to load twrp it would "crash" the screen would flash twice and try rebooting back to TWRP.
What ended up happening was it got stuck in a boot loop trying to boot into TWRP. (I haven't even installed TWRP.zip yet, just tried booting the .img file).
I couldn't get the phone to boot to the system anymore. I thought I had a nice $600 paperweight on my hands.
I finally got the phone to go back into the boot loader and flashed all the factory stuff back on and relocked the bootloader. So right now I'm 100% back to stock.
I'm not sure what went wrong in the boot up of the twrp.img file. I'd like to try again but I'm kinda getting sick of wiping the phone Everytime something goes wrong.
Sent from my Phone using Tapatalk
I'm wanting to get TWRP / Magisk on my Razer too, but see too many bootloop stories after attempting to flash TWRP.... making me nervous ha ha.
Sorry, not much help, but hope you get it sorted...
Peace
chris5s said:
I'm wanting to get TWRP / Magisk on my Razer too, but see too many bootloop stories after attempting to flash TWRP.... making me nervous ha ha.
Sorry, not much help, but hope you get it sorted...
Peace
Click to expand...
Click to collapse
I had mine in boot loop, I was able to get it out pretty easily. If your able to get the phone into the bootloader (I did using a fastboot command while it was in a boot loop) you can just execute the script provided by Razer and it does the rest. Took about 10 minutes and I had factory everything back on the phone. Relocked the bootloader after and done, phone fixed.
Sent from my Phone using Tapatalk
FireGuy0723 said:
I had mine in boot loop, I was able to get it out pretty easily. If your able to get the phone into the bootloader (I did using a fastboot command while it was in a boot loop) you can just execute the script provided by Razer and it does the rest. Took about 10 minutes and I had factory everything back on the phone. Relocked the bootloader after and done, phone fixed.
Sent from my Phone using Tapatalk
Click to expand...
Click to collapse
In my case I actually had to flash the stock boot.img from the May 2018 stock OS. Then I was able to use Razers guide to flash stock again. I haven't locked my bootloader since I still want to give it a try again. But I want to find a reliable way of rooting and then unrooting in case I want to do so in the feature.
So far I haven't found said documentation.
Installed Magisk v17.1 via TWRP loaded in fastboot boot (not fastboot flash boot ie not permanently installed) and so far all seems well. No boot loops when restarting...
Peace
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?