Related
Earlier today I used the Nexus Root Tool Kit to flash stock and flash the factory image for 5.0.
At erasing User Data it seemed to get stuck, it was there for over 40 minutes. While looking at the device I accidentally knocked the USB cable out and it said failed. Upon rebooting the device I got the Google logo and the bootloader unlocked icon and then the bugdroid with the gear like it's doing an update (THIS: http://scottiestech.info/wp-content/uploads/2013/03/Android_Update_Screen.jpg[1] ). It stayed like this for another 40 minutes. I forced it to shut down and tried to get into the bootloader but holding down vol up+vol down+power for almost 60 seconds did nothing.
I then booted it up normally again to the gear bugdroid and left it like that before I went out for almost 6 hours. When coming home it was the same and still stuck on that.
I rebooted again and held down to boot into the bootloader but again it did not boot in over 60 seconds.
So am I hard bricked and should toss this out with the trash tonight or can this be restored somehow.
Are you able to connect to your device using fastboot?
Assuming you have fastboot installed and the drivers installed, open a command prompt and from the directory where your SDK files are (unless you added the directory to your system PATH), type "fastboot devices" without the quotes. What do you get back? If you get back a serial#, you should be able to flash the individual files manually
(Download the factory image from google's site, and extract the files into a folder, and run the flash-all.bat This will wipe all your data out, and assumes your bootloader is already unlocked)
Edit: follow the instructions here - http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
These are for Nexus 5, but the same steps apply for Nexus 7 as well. Just make sure you download the right factory image for your Nexus 7. Use Method 1
jj14 said:
Are you able to connect to your device using fastboot?
Assuming you have fastboot installed and the drivers installed, open a command prompt and from the directory where your SDK files are (unless you added the directory to your system PATH), type "fastboot devices" without the quotes. What do you get back? If you get back a serial#, you should be able to flash the individual files manually
(Download the factory image from google's site, and extract the files into a folder, and run the flash-all.bat This will wipe all your data out, and assumes your bootloader is already unlocked)
Edit: follow the instructions here - http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
These are for Nexus 5, but the same steps apply for Nexus 7 as well. Just make sure you download the right factory image for your Nexus 7. Use Method 1
Click to expand...
Click to collapse
Well I can get it into fastboot but I'm getting errors when it tries to flash the bootloader or boot.
what's the error message?
jj14 said:
what's the error message?
Click to expand...
Click to collapse
originally there was none, it just said failed and completed. now i'm getting invalid arguments.
I'm still in fastboot mode but literally nothing will flash.
*edit* just tried to use tookit again and
writing 'bootloader'
FAILED <remote: flash write failure>
finished.
Seeing a couple people mention that they fixed errors like this just from using a different usb port or cable. going to try that.
Why didn't you use adb to flash factory image from the get-go? It's the safest way to flash. I would be so mad on your place if device would render useless. But that might be just me since i'm poor. I really hope you manage to fix it.
neo5468 said:
Why didn't you use adb to flash factory image from the get-go? It's the safest way to flash. I would be so mad on your place if device would render useless. But that might be just me since i'm poor. I really hope you manage to fix it.
Click to expand...
Click to collapse
I knew of that way but the Nexus Tool Kit has always been perfect and I've never had any issues with it so I figured I'd just do it that way to make it easier and well, it didn't happen.
I'm hoping because I can get into fastboot that it's not actually bricked yet but if so then oh well i guess.
You could have been frustrated with all the features that’s supposed to be in your New Huawei Watch is nowhere to be found. Like Wi-Fi, Bluetooth and Language Selection are all hidden in the China Stable Rom of the Huawei Watch.
I have talked to the CSR of Huawei in China, they honestly told me that the Wi-Fi certificate for the watch is not yet certified that’s why they cannot unleash it yet but it is embedded inside the watch should future updates allows the Wi-Fi to be used. Regarding the language selection, local China release is locked to Simplified Chinese, whether you like it or not.
If you happen to buy from China or received a gift with a China local release Huawei Watch, here is the guide on how to flash with an English Rom which I have already tested mine on.
Here is the complete guide:
Step 1: Put the Watch to Fastboot Mode
1) Hold down the power button
2) The screen will go black for about 2 seconds and then boot into the Huawei logo. Keep holding down the power button.
3) Wait for the first vibration, release the power button and then immediately give the power button one short press.
Note: If you feel the second vibration, you waited too long to do the release and press. Start over again with Step 1.
Another alternative for Step 1:
1.) Install ADB SETUP V1.3
https://drive.google.com/file/d/0B_1zjuazXSqbQ0p6NWtvRk9OMzA/edit
2.) Enable ADB and connect to computer
How to Enable ADB:
- Go to About
- Click 5 times on Build Number to access Developer Mode
- Go to Developer Options
- Enable ADB Debugging
3.) Go into command prompt mode
4.) Reboot watch into Fastboot mode using this code:
adb reboot-bootloader
Step 2: Unlock the Bootloader
1.) On command prompt mode, type this command: Fastboot Oem Unlock
2.) accept the prompt on the watch.
Note: If successful, command prompt will say your bootloader is already unlocked.
Step 3: Flashing
Download first the three files before proceeding:
Boot Img: https://mega.nz/#!rgRQHRrb!lgQCvqH-qkuqitPRRXfCad29MdmJ6ynaUHJDr0hjeLM
Recovery Img: https://mega.nz/#!ahgjxA4R!y8Hb0CBVBRwUr0tA3HeFrrqh0ALAiMyqJu0pLsBsAD8
System Img: https://mega.nz/#!2pYVBDpA!wQJT8LDcffk7uxEmrsqna6MKWIODD-FqBO_k4Poml7g
After downloading the three files, lets proceed:
1.) While on Fastboot mode, type this on the command prompt one at a time:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
2.) and then go to recovery and do a wipe data / factory reset.
Congrats! Your done!
Further Reading if you are stuck on flashing System.img
There are some reason beyond my explanation why the system.img cannot be flashed to the watch, here is the workaround:
1.) First of all download the TWRP and fastboot boot it:
TWRP download: http://forum.xda-developers.com/attachment.php?attachmentid=3505656&d=1444766757
Code:
fastboot boot TWRP2.8.7.0-Sturgeon.img
2.) Now your watch is in TWRP and you can no longer use ADB commands, go to your watch and select Advanced, then select ADB Side Load
3.) Going back to command prompt, push the system.img in the sdcard so:
Code:
adb push system.img /sdcard/
4.) Now flash it:
Code:
adb shell dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system
5.) Reboot.
Now you may encounter bootloop after flashing which I did, go back to Step 1 Fastboot mode and select Reboot Recovery, then wipe data and then clear cache, then you are good to go!
This is the most complete guide I can come up with based on my own explorations. Hope this helps.
Where can i find the drivers for this watch.
When i plug this watch into my computer Windows doesn't detect the drivers. I've tried looking on the HuaWei website but there are no downloadable drivers. Any help?
coolcaty said:
Where can i find the drivers for this watch.
When i plug this watch into my computer Windows doesn't detect the drivers. I've tried looking on the HuaWei website but there are no downloadable drivers. Any help?
Click to expand...
Click to collapse
Look here : https://m.reddit.com/r/hwatch/comments/3n9ckp/how_to_get_adb_access_over_usb/
"Fastboot Oem Unlock" should be "fastboot oem unlock" otherwise it won't work. Also make sure to have ADB 1.0.32 at least for watches!
hello!
i do all step and complete flash with twrp mode . but when reboot and will go to reboot recovery the watch restart and restart!
sry for weak english!
j.spectator said:
hello!
i do all step and complete flash with twrp mode . but when reboot and will go to reboot recovery the watch restart and restart!
sry for weak english!
Click to expand...
Click to collapse
5.) Reboot.
Now you may encounter bootloop after flashing which I did, go back to Step 1 Fastboot mode and select Reboot Recovery, then wipe data and then clear cache, then you are good to go!
Hi, first of all thanks for this awesome guide.
This is the first thing I am looking for after bought a Chinese watch from China.
Manage to go through ONLY I tried key in "fastboot oem unlock' all in small letters.
Then follow the guide instruction to goto recovery to wipe data after successfully go through the other flashing steps smoothly.
This is where I got stuck in infinite looping in Android lying and screen flashing every few seconds. I got panicked after trying multiple times failed to recover from this symptoms for a while.
Until finally manage to pull back to fastboot menu by keep press holding onto the power button. The steps of holding till first vibration then do a quick short press doesnt work.
I am glad that now I am back to normal with the English screen.
Next I will proceed to flash the TWRP and 1.4 update.
Hopefully everything goes smoothly.
Thank you for the guide once again and wish everyone success in updating and Enjoy!
Update: (9:29am)
Did a system update. Before was something like LBC49A, after system update it becomes LBC43B. I suppose this is 1.4 update as the name is the same.
Hence decided not to flash the TWRP recovery for the time being if it can continue auto system update.
Update (9/3/2016):
Sorry, nvr read through all the posts. Was thinking that (LBC43B) was the latest update.
So proceed to flash TWRP recovery then try to update to MEC23L (latest update) but failed to run "adb sideload update.zip"
Every time once enter into Recovery mode, the connection dropped. Then tried to do OTA update by factory reset as suggested but failed (confirmed my location can OTA as one use from same location didi it.)
This morning went back to PC flash back the original Stock Recovery from here.
Restart the watch and goto System Update, receive message "Charge the watch to update to MEC23L"
My thot - OTA only allow with Stock Recovery?
Update done but still cannot sms. ??
Btw, for LBC43B, many functions cannot work properly like sms, call and no sound at all. Thx n Enjoy.
P.S. Using Minimal ADB and Fastboot, PDAnet driver(for watch USB driver), running on Win7, connect via watch USB charge docking station.
help me please
No OS installed! Are you sure you wish to reboot?
This is my problem, I can´t install it-
I send you a private message Richboy234, can you help me please?
richboy324 said:
You could have been frustrated with all the features that’s supposed to be in your New Huawei Watch is nowhere to be found. Like Wi-Fi, Bluetooth and Language Selection are all hidden in the China Stable Rom of the Huawei Watch.
I have talked to the CSR of Huawei in China, they honestly told me that the Wi-Fi certificate for the watch is not yet certified that’s why they cannot unleash it yet but it is embedded inside the watch should future updates allows the Wi-Fi to be used. Regarding the language selection, local China release is locked to Simplified Chinese, whether you like it or not.
If you happen to buy from China or received a gift with a China local release Huawei Watch, here is the guide on how to flash with an English Rom which I have already tested mine on.
Here is the complete guide:
Step 1: Put the Watch to Fastboot Mode
1) Hold down the power button
2) The screen will go black for about 2 seconds and then boot into the Huawei logo. Keep holding down the power button.
3) Wait for the first vibration, release the power button and then immediately give the power button one short press.
Note: If you feel the second vibration, you waited too long to do the release and press. Start over again with Step 1.
Another alternative for Step 1:
1.) Install ADB SETUP V1.3
https://drive.google.com/file/d/0B_1zjuazXSqbQ0p6NWtvRk9OMzA/edit
2.) Enable ADB and connect to computer
How to Enable ADB:
- Go to About
- Click 5 times on Build Number to access Developer Mode
- Go to Developer Options
- Enable ADB Debugging
3.) Go into command prompt mode
4.) Reboot watch into Fastboot mode using this code:
adb reboot-bootloader
Step 2: Unlock the Bootloader
1.) On command prompt mode, type this command: Fastboot Oem Unlock
2.) accept the prompt on the watch.
Note: If successful, command prompt will say your bootloader is already unlocked.
Step 3: Flashing
Download first the three files before proceeding:
Boot Img: https://mega.nz/#!rgRQHRrb!lgQCvqH-qkuqitPRRXfCad29MdmJ6ynaUHJDr0hjeLM
Recovery Img: https://mega.nz/#!ahgjxA4R!y8Hb0CBVBRwUr0tA3HeFrrqh0ALAiMyqJu0pLsBsAD8
System Img: https://mega.nz/#!2pYVBDpA!wQJT8LDcffk7uxEmrsqna6MKWIODD-FqBO_k4Poml7g
After downloading the three files, lets proceed:
1.) While on Fastboot mode, type this on the command prompt one at a time:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
2.) and then go to recovery and do a wipe data / factory reset.
Congrats! Your done!
Further Reading if you are stuck on flashing System.img
There are some reason beyond my explanation why the system.img cannot be flashed to the watch, here is the workaround:
1.) First of all download the TWRP and fastboot boot it:
TWRP download: http://forum.xda-developers.com/attachment.php?attachmentid=3505656&d=1444766757
Code:
fastboot boot TWRP2.8.7.0-Sturgeon.img
2.) Now your watch is in TWRP and you can no longer use ADB commands, go to your watch and select Advanced, then select ADB Side Load
3.) Going back to command prompt, push the system.img in the sdcard so:
Code:
adb push system.img /sdcard/
4.) Now flash it:
Code:
adb shell dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system
5.) Reboot.
Now you may encounter bootloop after flashing which I did, go back to Step 1 Fastboot mode and select Reboot Recovery, then wipe data and then clear cache, then you are good to go!
This is the most complete guide I can come up with based on my own explorations. Hope this helps.
Click to expand...
Click to collapse
Hi, I have a problem, when I do this :
"select Advanced, then select ADB Side Load" after 4 or 5 minutes processing it saids "failed"
and then I can do this step "adb push system.img /sdcard/"
but not this "adb shell dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system"
Any idea please, thank you.
jbctiong said:
Hi, first of all thanks for this awesome guide.
This is the first thing I am looking for after bought a Chinese watch from China.
Manage to go through ONLY I tried key in "fastboot oem unlock' all in small letters.
Then follow the guide instruction to goto recovery to wipe data after successfully go through the other flashing steps smoothly.
This is where I got stuck in infinite looping in Android lying and screen flashing every few seconds. I got panicked after trying multiple times failed to recover from this symptoms for a while.
Until finally manage to pull back to fastboot menu by keep press holding onto the power button. The steps of holding till first vibration then do a quick short press doesnt work.
I am glad that now I am back to normal with the English screen.
Next I will proceed to flash the TWRP and 1.4 update.
Hopefully everything goes smoothly.
Thank you for the guide once again and wish everyone success in updating and Enjoy!
Update: (9:29am)
Did a system update. Before was something like LBC49A, after system update it becomes LBC43B. I suppose this is 1.4 update as the name is the same.
Hence decided not to flash the TWRP recovery for the time being if it can continue auto system update.
Update (9/3/2016):
Sorry, nvr read through all the posts. Was thinking that (LBC43B) was the latest update.
So proceed to flash TWRP recovery then try to update to MEC23L (latest update) but failed to run "adb sideload update.zip"
Every time once enter into Recovery mode, the connection dropped. Then tried to do OTA update by factory reset as suggested but failed (confirmed my location can OTA as one use from same location didi it.)
This morning went back to PC flash back the original Stock Recovery from here.
Restart the watch and goto System Update, receive message "Charge the watch to update to MEC23L"
My thot - OTA only allow with Stock Recovery?
Update done but still cannot sms. ??
Btw, for LBC43B, many functions cannot work properly like sms, call and no sound at all. Thx n Enjoy.
P.S. Using Minimal ADB and Fastboot, PDAnet driver(for watch USB driver), running on Win7, connect via watch USB charge docking station.
Click to expand...
Click to collapse
Hi there
All i know is you can flash the stock rom then update via OTA
mine is running marshmallow already now MEC23L
This is the safer way coz i never tried to flash in the MEC23L
Cheers!
alesramosfj said:
Hi, I have a problem, when I do this :
"select Advanced, then select ADB Side Load" after 4 or 5 minutes processing it saids "failed"
and then I can do this step "adb push system.img /sdcard/"
but not this "adb shell dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system"
Any idea please, thank you.
Click to expand...
Click to collapse
I did not encounter this error
did you try the first method before doing the TWRP?
A Problem
Hi. I have a problem. I complete step3. I code command: fastboot oem reboot-recovery . Its Failed. I seclected recovery on watch. But when selecting this plan is faulty. Only flashing screen icon Android. I tried again, but still the same. Can you help me?
h**ps://drive.google.com/file/d/0B0F7_Vdg_eg3Nms3M2oyVmZ1RjA/view?usp=sharing
begioxx said:
Hi. I have a problem. I complete step3. I code command: fastboot oem reboot-recovery . Its Failed. I seclected recovery on watch. But when selecting this plan is faulty. Only flashing screen icon Android. I tried again, but still the same. Can you help me?
Click to expand...
Click to collapse
hi there
i think you need to do a further reading on the one after step three
there are chances that you will get stuck in flashing the system image file
there is a workaround.
try it again
hope it helps.
richboy324 said:
I did not encounter this error
did you try the first method before doing the TWRP?
Click to expand...
Click to collapse
Hello,
I'm also encountering this error. I did try the first method, and I'm getting stuck on activating ADB Side Load. Any tips?
Hi, there's a problem and i can't mount partition /data and /cache
plz help
Thanks a lot man you are a gem
I in hurry formatted system from twrp and was without OS. very detailed tutorial for beginners with adb. I am back with watch booting fine now
Just a note. I tried doing this while in China without vpn access for my phone. This made it so I couldn't sync up or pair because it kept trying to access google which was blocked. Once I got back to Canada I was able to do everything and update to newest OTA. If you leave it on chinese rom you can use in china and pair with the Android Wear China version app.
alesramosfj said:
No OS installed! Are you sure you wish to reboot?
This is my problem, I can´t install it-
I send you a private message Richboy234, can you help me please?
Click to expand...
Click to collapse
Hey, did he ever get back to you? I've got the same thing going on right now.
alesramosfj said:
No OS installed! Are you sure you wish to reboot?
This is my problem, I can´t install it-
I send you a private message Richboy234, can you help me please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/hua...ock-huawei-watch-t3219596/page11#post66771952
Not sure if he got back to you. I had the same problem, and it involved the system.img that I downloaded from the link above. It wasn't complete for some reason. On this thread attached, it has a zip that has it all. My watch works fine now. I want to thank the OP here for showing me the steps to take. You all ROCK!
Stock watch, never turned on debugging. Have tried to do the steps in Skin1980 post (return to stock... load boot, recovery and system (got the error on System). Tried the ADB steps (but noob on ADB with no luck). Am I toast? Attached are screen shot showing fastboot recognizes devices. Also here is device screenshot. Any help would be appreciated... Love this watch but for now it's a paperweight.
Also when I try and write .img files (boot, recovery, system) I get the FAILED (remote: device locked).. I am in fast boot screen on watch.
Can u see the device if it is connected n u enter 'adb devices' in the command prompt?
If not then have to confirm does your driver install correctly.
The device must be connected to PC before you can do anything to it. My understanding.
In fastboot screen on your watch doesnt mean it is connected to PC.
You have to unlock bootloader to be able to use fastboot flash.
While in bootloader, use "fastboot oem unlock" command.
Note, that this automatically wipes all user data on the watch.
What is the error you are getting on System?
A lot of people are reporting errors but in reality they are not.
Can you screenshot the error like you did the fastboot command?
Any progress so far???
It has been a while; have you succeeded to recover the Huawei watch pass the Google animation?
I have read no thread who has solved the problem. Any feedback is appriciated.
Update: After so many days I managed to flash... My watch is working again; still no news from Huawei!!!
For newbies like I am, you have to know is you don't need to enable anything before you are stuck to google logos.
I just downloaded "adb-setup-1.4.3" and "Minimal ADB and Fastboot". Whenever the windows didn't recognize the watch I ran adb-setup which at the end asks for installing drivers and when I disconnect and connect the device, it worked.
After getting connected check if the watch is getting fastboot command by c:\fastboot devices. If you can see any letters and fastboot at the right you're ok to go.
You need to c:\Fastboot Oem Unlock which unlocks the watch and you're out of warranty. Just accept it.
Then follow the steps of skin1980 (thanks it was really great)) http://forum.xda-developers.com/huawei-watch/general/guide-return-to-stock-huawei-watch-t3219596
If you need "twrp" not written; just "swipe right" and follow the instructions of skin1980.
Boot Stuck Problem is over.
The watch is getting the updates right now but I guess I'll learn more and get to stock by the experts' help...
Thanks to you all...
hi
i managed to get mine working as well ! (Thanks to abhanli, pkt_lnt and skin180)
make sure you are in fastboot menu on your watch (holding the power button till switches off and the pressing again after vibrates)
most important thing next is to press shift and right click anywhere in the adb folder on your computer, and then run command prompt from there, otherwise adb will not load up and you will think that you have just run a dodgy script !
unlock your bootloader (typing "Fastboot Oem Unlock" in the command prompt in adb folder)
then you can use steps of skin180 (link above)
OR
https://developer.android.com/wear/preview/downloads.html
scroll down to huawei watch and choose second download option (non preview image for after testing) (thanks pkt_lnt)
extract into your adb folder (located in c:\)
then using the command prompt in adb folder, navigate to that extracted folder (using dos commands)
then if you are on windows, type "flash-all.bat"
hey presto - will work !
when it reboots, you may think "darn it still has spinning dots !" but if you wait about 5-10 mins it progresses past that stage and comes up with welcome screen !
My watch is working again !
HUAWEI customer services are a pile of POO. Their repair centre in UK is waste of time. They never answer the phone and never reply to messages.
If the Huawei watch wasnt so beautiful, i'd never bother with them !
Good luck and thanks all.
This worked great for me thanks. BUUTTTT, I now have this issue:
error: cannot load 'bootloader-sturgeon-mec23l.img'
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.010s
W/ (58966): Unable to open 'image-sturgeon-mec23l.zip': No such file or directory
error: failed to open zip file 'image-sturgeon-mec23l.zip': I/O Error
STEPHENs-Mac-Pro:~ HomePC$ fastboot devices
FFS7N15B06002296 fastboot
All 3 files are in the PATH sdk/platform-tools folder: bootloader img, flash shell, and image zip.
Can anyone please help me..
I got my Huawei watch today.. And u was doing the flash system and it didn't work so I did a reboot recovery from the watch.. Then it's not working.. After boot loading the Android logo appears for 2 sec then it's blank then the logo.. Etc.
It isn't recognized by my PS so I can't use any command prompt.. What can I do?
Please help
I tried to flash the 2.0 image on my Huawei watch and as I launched the "flash all" command, it failed with the message "data package too big". Watch rebooted and remained stuck on the huawei logo. I can enter recovery , I can enter bootloader, but even if I wipe all data and factory reset, the reboot still stops at that screen. Any ideas? Is it bricked?
Sent from my SM-G935F using XDA-Developers mobile app
I had this issue last week.
I resolved it by reflashing 1.4, booting it up, and eventually having the courage to retry 2.0.
I got the latest ADB, but in my case, for the various flashing attempts, the .bat's did not work, so I had to manually flash each file. Apparently, the first time I flashed 2.0 I must have missed a file, because on my second attempt, everything worked perfectly.
As long as you can access fastboot, everything is fine (i.e any damage you do is resolvable).
hi
i managed to get mine working as well ! (Thanks to abhanli, pkt_lnt and skin180)
make sure you are in fastboot menu on your watch (holding the power button till switches off and the pressing again after vibrates)
most important thing next is to press shift and right click anywhere in the adb folder on your computer, and then run command prompt from there, otherwise adb will not load up and you will think that you have just run a dodgy script !
unlock your bootloader (typing "Fastboot Oem Unlock" in the command prompt in adb folder)
then you can use steps of skin180 (link above)
OR
https://developer.android.com/wear/preview/downloads.html
scroll down to huawei watch and choose second download option (non preview image for after testing) (thanks pkt_lnt)
extract into your adb folder (located in c:\)
then using the command prompt in adb folder, navigate to that extracted folder (using dos commands)
then if you are on windows, type "flash-all.bat"
hey presto - will work !
when it reboots, you may think "darn it still has spinning dots !" but if you wait about 5-10 mins it progresses past that stage and comes up with welcome screen !
My watch is working again !
HUAWEI customer services are a pile of POO. Their repair centre in UK is waste of time. They never answer the phone and never reply to messages.
If the Huawei watch wasnt so beautiful, i'd never bother with them !
Good luck and thanks all.
can you please give me a more detailed steps
i only want to get back to 1.4
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?