Related
Hey guys, first time on here and im kinda a noob when it comes to the rooting stuff (ive done a few things but nothing hardcore) and i need some help getting onto this (IMM76K) update (and not sure if this is the right thread to put this in). A few weeks ago i unlocked my bootloader and (after some of the same issues im having now) temp booted into CWM and installed the 4.0.4 IMM30B update. Now with this new update, i wanted to get it installed or flash back to get the OTA (not sure if i can get the OTA on the leak update)
But, everytime i try to boot into CWM again (using this toolkit: http://forum.xda-developers.com/show....php?t=1614827) i constantly get fail messages. And it happens if i try to boot into CWM or try to flash the factory 4.0.2 update.
With the phone on and trying to use these (http://www.droid-life.com/2011/12/16...factory-state/) instructions, i constantly get the error "sending 'bootloader'... FAILED (remote: Invalid Command)". Im already in the fastboot bootloader.
With the toolkit, it wont start the factory img flash if the phone is on, and if im in the fastboot bootloader, it says it "fails" to boot into the bootloader (which, again, im already in) and fails to install all the img files and then just boots back into the older 4.0.4 leak.
I havent rooted my phone (but i tried that to get past this problem but i get the same error messages), only unlocked the bootloader. Sorry for the long post and if it seems like a block of text. This is just starting to really frustrate me. Thanks
Do you have ADB installed on your computer? It's hard to troubleshoot your problem if you don't.
Yea, i do. Im in school for programming and have installed all the android SDK stuff and eclipse since i want to make android apps/games (hopefully). I downloaded the fastboot.exe file and have it in the platform-tools folder with the adb.exe file
Go here (https://developers.google.com/android/nexus/images) and download mysid for Gnex.
It's gzipped so you will need to extract those files using 3rd party software (winzip works nicely).
Boot your phone normally. Connect to your computer and open a command prompt.
Type 'adb devices' and note the result.
Type 'adb reboot bootloader' and wait for the phone to enter the bootloader.
Once there type 'fastboot devices'.
If you don't get a response you have a driver problem. You need to DL the samsung driver.
If you do, flash each zip file in that package you DL'ed from google.
Start with 'fastboot flash bootloader <location of bootloader zip>'
Then, 'fastboot flash radio <file>'
ect. until you've flashed all the zip files. (Exactly like the instructions in your link but replace the files they gave you with the ones from google.)
Post here if you get an error message.
Ok, everything is fine until i get to flashing the bootloader, heres what i get (sorry it isnt an image)
D:\Android\android-sdk\platform-tools>adb devices
List of devices attached
0146A5B30300B014 device
D:\Android\android-sdk\platform-tools>adb reboot bootloader
D:\Android\android-sdk\platform-tools>fastboot devices
0146A5B30300B014 fastboot
D:\Android\android-sdk\platform-tools>fastboot flash bootloader bootloader-toro-
primekk15.img
sending 'bootloader' (2308 KB)... FAILED (remote: Invalid Command)
finished. total time: 0.001s
D:\Android\android-sdk\platform-tools>
This is what happens even when i use a toolkit to do it for me. Ive used the toolkit to reinstall the drivers a bunch of times and it still happens
Did you relock the bootloader? Type 'fastboot oem unlock'
---------- Post added at 09:07 AM ---------- Previous post was at 08:57 AM ----------
If that's not it then it's a driver issue.
Uninstall the ones you have (Control Panel -> Device Manager) and go to http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW? and install the samsung ones.
If you have problems with that I can walk you though it.
The only thing i was able to do from the toolkits was lock/unlock the bootloader (tried that last night using the toolkit to see if it fixed any problems). ill try installing the drivers and see what happens, thanks
edit: *I locked the bootloader last night and unlocked it again right after
blipp said:
The only thing i was able to do from the toolkits was lock/unlock the bootloader (tried that last night using the toolkit to see if it fixed any problems). ill try installing the drivers and see what happens, thanks
edit: *I locked the bootloader last night and unlocked it again right after
Click to expand...
Click to collapse
1) Throw away the toolkit;
2) Uninstall all drivers;
3) Install these drivers;
4) Make sure your bootloader is unlocked;
5) Open a command prompt in the directory where your both your fastboot file and CWM are located;
6) Reboot your device into fastboot mode (vol+ & vol- & power), and plug into your PC;
7) Make sure your device is recognized by your PC: fastboot devices
8) Flash or boot CWM
a) Flash by typing: fastboot flash recovery cwm.img
b) Boot by typing: fastboot boot cwm.img
sorry for being a noob at this, but where do i put the Universal Naked Driver stuff? Do i have to extract them to a specific folder? Im trying to install the drivers from the samsung website first though
Im not using the toolkits anymore and am trying to follow your instructions for the command prompt
blipp said:
sorry for being a noob at this, but where do i put the Universal Naked Driver stuff? Do i have to extract them to a specific folder? Im trying to install the drivers from the samsung website first though
Im not using the toolkits anymore and am trying to follow your instructions for the command prompt
Click to expand...
Click to collapse
Extract the zip to a directory. Plug your device in fastboot mode to your PC. Open device manager and find the phone. Right-click on it and select update driver. Select install yourself or whatever the option is, and navigate to the folder where you extracted the zip. I've found that those drivers are better than the Samsung-packaged drivers.
Also, do one or the other, but not both. Make sure you remove the old driver before you start the new.
In windows 7 you're gonna want to go to (install Universal Naked Driver)...
Control Panel -> Hardware and Sound -> Device Manager
In the list click the driver for your phone. It will either be in the USB list or listed as some kind of phone. Right-click and uninstall the driver. Reboot. Go back to device manager. Plug in device. Click update driver software when your device shows up. Then 'Browse my computer'. Then 'Let me pick from a list'. Then 'Have Disk'. Find the .inf files and windows will install the driver.
ok, i extracted the Universal zip into its own folder on the desktop, after i uninstalled the drivers and rebooted my PC, i plugged in the phone, waited for it to show up, and went to update the drivers. I got to the "Have Disk" and selected both of the .inf files that were in the extracted folder. Both of them caused a popup that said that folder didnt contain the drivers for my device.
When im in the fastboot bootloader the phone doesnt show up in my Device Manager. Is that a problem?
Thanks for helping me through this, my last phone was a Droid X and all i ever had to do was hold vol down and power and it got me to a recovery screen like CWM and i could install an update.zip.
blipp said:
ok, i extracted the Universal zip into its own folder on the desktop, after i uninstalled the drivers and rebooted my PC, i plugged in the phone, waited for it to show up, and went to update the drivers. I got to the "Have Disk" and selected both of the .inf files that were in the extracted folder. Both of them caused a popup that said that folder didnt contain the drivers for my device.
When im in the fastboot bootloader the phone doesnt show up in my Device Manager. Is that a problem?
Thanks for helping me through this, my last phone was a Droid X and all i ever had to do was hold vol down and power and it got me to a recovery screen like CWM and i could install an update.zip.
Click to expand...
Click to collapse
What OS are you running on your PC?
Windows 7
blipp said:
Windows 7
Click to expand...
Click to collapse
Ok, try this: go into the directory where you unzipped the drivers. Right-click on android_winusb.inf and select install.
Get an error popup - "The INF file you selected does not support this method of installation"
blipp said:
Get an error popup - "The INF file you selected does not support this method of installation"
Click to expand...
Click to collapse
Hmm. Not sure what is going on.
Let's try this step-by-step:
Boot your device into fastboot mode, plug into your PC, and open up device manager. Does your PC recognize your device? What does it show in task manager?
Nothing Shows up in device manager. The "imaging devices" section is opened by default. In the "devices and printers" window, however, there is an "unspecified" device, Android 1.0. Usually the galaxy nexus shows up in the "portable devices" section in device manager. Coins "scan for hardware changes" doesn't cause it to appear either
Sent from my Transformer using XDA
blipp said:
Nothing Shows up in device manager. The "imaging devices" section is opened by default. In the "devices and printers" window, however, there is an "unspecified" device, Android 1.0. Usually the galaxy nexus shows up in the "portable devices" section in device manager. Coins "scan for hardware changes" doesn't cause it to appear either
Sent from my Transformer using XDA
Click to expand...
Click to collapse
Ok, good. Now right click on the Android 1.0 and select "update driver software". Then click on "browse my computer for driver software", then click on the "Browse" button and make sure "include subfolders" has a check.
Now navigate to where you unzipped the drivers and click ok.
Its not giving me that option. Its not in device manager, its only showing in control panel->hardware and sound->devices and printers. Right clicking only gives me Eject, Create shortcut, troubleshoot, and properties. Properties only has General and Hardware. I even went into device manager and checked "show hidden devices" and its still not there. It only shows up now when its actually booted into android
Sent from my Transformer using XDA
I have a C6506 that is unlocked, have checked via the service code. Not just unlockable but unlocked. Certain.
I've used both older flashtool64 that worked before (0.9.11.0) on a Surface Pro (windows 10) and newer (0.9.19.10) on a desktop (Windows 10 also).
In both cases I can flash 10.7.a.0.222 for C6506. I also can flash 10.3.a.0.423 on the Surface (did not try on others). It boots, it works, no issues.
I can get in fastboot mode on the phone (blue light), but on the surface with the older Flashtools (and associated drivers) I cannot access the phone at all, just waiting for device.
On the newer flash tools with drivers installed (turned off signing verification) I can get into fastboot and do things like a "getvar version", but I cannot do more complex things like get the unlock status, nor can I flash a boot image (in this case from CM 12.1). It says "Command not allowed" in the write phase. Yes, the phone is unlocked, really, at least it says it is, and I did do an unlock code with legitimate Sony provided codes. And previously rooted using it as unlocked.
I've also tried getting root with a pre-rooted 10.7.a.0.222 -- I can get an older version rooted, put recovery on it, I can do the install of the zip and it completes -- then boot loop. This is using Beta-SuperSU-V2.52.zip and zl-lockeddualrecovery2.8.23-release.combined.zip with PRFCreator. (The recovery is also what I used to do the install). Boot loop. Can't get out of it without a new flash despite power off, resets, etc. Can't get back into recovery either at that point.
I do have the phone working with a non-rooted stock Sony 10.7.A.0.222. As mentioned, flashes fine. I just can't seem to get CM running (can't fastboot the boot image), nor can I get root on the stock sony (boot loop).
I've also tried the fastboot program on the current SDK as well as the one in Flashtools without any difference, still can't flash a boot.img from cm12.1.
I feel like I'm missing something fundamental, like maybe some aspect of running Windows 10 that is interfering (I have no older version currently). I'd suspect CM12.1 but it also is failing with the typical root technique for 5.1.1 stock (i.e. root older version first).
While I am not an active developer, this is not my first round of flashing or updating the phone, though it is my first round in a year or more, certainly since Windows 10.
I realize this is a lot like "nothing is working what could be wrong" and not a very specific question, but wondering if anyone has any suggestions as to whether there might be a common cause here.
I do have one more interesting piece of information that I do not understand.
I downloaded Emma and tried to use it to flash stock just to make sure the image I had was good for stock.
Emma says "this phone is locked". So thinking my last flash re-locked it, I went into flash tools and did this:
U:\AndroidSDK\platform-tools>fastboot oem unlock 0xkey-from-sony
...
OKAY [ 2.969s]
finished. total time: 2.969s
After doing so, Emma STILL says it is locked.
Flash tool however allows me to flash it.
Any clue why Emma would say "locked" when I just finished unlocking it?
In service, configuration it says "Yes" to unlocked, not "no/yes" or any other combination, just "yes".
focus on getting the sdk tools to work, like fastboot. What do you mean it just does not flash( show console output of your fastboot flash boot boot.img), Is fastboot not recognized in the device manager, It is odd you can use it to 'oem unlock'... I had to change driver files when I switched from windows 7 to windows 10. if you can 'fastboot devices' and 'adb devices' you should be good to go as far as flashing, maybe you have bad images not made for the phone? I am no pro take my information with a grain of salt.
ham5 said:
focus on getting the sdk tools to work, like fastboot. What do you mean it just does not flash( show console output of your fastboot flash boot boot.img), Is fastboot not recognized in the device manager, It is odd you can use it to 'oem unlock'... I had to change driver files when I switched from windows 7 to windows 10. if you can 'fastboot devices' and 'adb devices' you should be good to go as far as flashing, maybe you have bad images not made for the phone? I am no pro take my information with a grain of salt.
Click to expand...
Click to collapse
I will try again tomorrow (need the phone tonight and it takes a while to get stock back up and configured).
Concentrating on fastbook and on my more-working desktop (the tablet definitely has some issue, I think driver related).
I installed the newest Flashtools, and also installed the fastboot and s1 drivers from it (I think that's what they are called). I configured Windows to permit them unsigned and they installed without error.
When I try to do CM12.1, what I did was download their distribution zip, and unzip it and pull out the boot.img file. I then put the phone in fastboot mode, and it worked and was recognized (e.g. "fastboot getvar version" responds).
Going by the instructions for CM12.1, I then tried to do "fastboot flash boot c:\pathwhereitwas\boot.img"
This does a send of the file, which works, and then does a write and says "command not allowed". So it appears to transmit the file but can't commit it to flash. I cannot post the log as didn't save it but if you think relevant can post tomorrow.
As to the locked issue -- after trying this the first time, I thought "maybe the phone has been locked again". So I did the #*#*service*#*# and see it says "yes" for unlocked. But just to be safe, I dug out my 2 year old email from Sony and did another unlock. As to why I did it with the "oem unlock" that's how CM12.1 suggests (https://wiki.cyanogenmod.org/w/Install_CM_for_odin). The first time I typed it, it failed, the second time it said "OK". Tried the flash boot again, same "command not allowed error".
The phone goes into fastboot mode easily (blue light, plus response to things like getvar). It goes into flash mode fine also, and indeed, after I gave up (each of several times) I flashed stock back on the phone and it came up with 5.1.1 stock.
I wanted to run CM12.1 as I really don't like that stock has not patched stagefright, plus I hate not having root.
Any suggestions what I may be doing wrong, that fastboot commands sometimes work, but I can't flash the boot file?
Am I flashing the RIGHT boot file? Should I be flashing the CM12.1 recovery image they have on their download page instead? (But the instructions are pretty clear).
I should note that the phone does not appear to have a recovery on it -- booting after flashing stock, and toggling all the volume buttons in any combination is just ignored.
I think your really digging way to deep into this...
The phone goes into fastboot mode easily (blue light, plus response to things like getvar). It goes into flash mode fine also, and indeed, after I gave up (each of several times) I flashed stock back on the phone and it came up with 5.1.1 stock.
Click to expand...
Click to collapse
what is the difference between fastboot and flash mode? Ive never heard of this flash mode....
This does a send of the file, which works, and then does a write and says "command not allowed". So it appears to transmit the file but can't commit it to flash. I cannot post the log as didn't save it but if you think relevant can post tomorrow.
Click to expand...
Click to collapse
I don't believe it sends a file at all, it is flashed/written to the boot partition right away.. or is supposed to - I would consider this your chief complaint... "command not allowed" when trying to fastboot flash a boot.img -- I get a lot of hits googling that.. driver problems/bootloader locked
ham5 said:
I think your really digging way to deep into this...
Click to expand...
Click to collapse
I'd welcome a shorter, simpler path.
ham5 said:
what is the difference between fastboot and flash mode? Ive never heard of this flash mode....
Click to expand...
Click to collapse
Perhaps it is purely a sony thing. If, with the phone powered off, you plug it in holding the volume up button you end up in fastboot mode; if you plug it in with the volume down you end up in flash mode.
Flashmode is used by Emma and by Flashtools. Fastboot is used by the Fastboot utility. I'm unclear what happens under the cover, but they are not interchangeable.
ham5 said:
I don't believe it sends a file at all, it is flashed/written to the boot partition right away.. or is supposed to - I would consider this your chief complaint... "command not allowed" when trying to fastboot flash a boot.img -- I get a lot of hits googling that.. driver problems/bootloader locked
Click to expand...
Click to collapse
As I said, I do not know what happens under the covers, but in fastboot mode when you do the "flash boot" it first says it transmitted a file (shows bytes sent, etc) then it does a "write" command itself and it is that write command that fails.
And therein lies my issue trying to flash the boot image -- the write command fails, and I cannot figure out why.
Drivers: I've tried the latest flashtool, and installed the drivers from there. They do install (with signing verification off), and they do connect and see the phone. Some commands work, but this one does not. Could it be the drivers? Certainly, but I do not know what to try to fix them.
Emma: I hate to keep coming back to this, but I do not understand why Emma says my phone is locked, when it clearly appears not to be. I've both re-unlocked it, confirmed it is unlocked with the service menu. But that it thinks it is locked, and the "write" command failure, makes me wonder if there is an issue either in the phone or windows or drivers that makes it act that way. incidentally I've also tried all this with antivirus/firewalls off with no effect.
Locked: just to confirm, in the service menu it says "Root Status" and "unlockable" as "yes". Not "Yes/no". That means it is currently unlocked, correct?
To your first point, I may be over-complicating it. I would welcome some suggestion of other simpler steps. I've done the same google, and don't see real solutions other than "try better drivers", but most threads seem to point to the flashtools drivers, and I've tried those, as well as installing Emma which (presumably) either used those or loaded its own.
Incidentally if this is more appropriate to the Q&A forum, and a moderator is handy, I would appreciate it moving. I placed it here because this relates mostly to the Flashtools drivers and the process of using fastboot.
I cant say for sure .. CM's dialer does not work with service menu... but you defiantly not worried about root... your looking for the bootloader to be unlocked, not unlockable..
ham5 said:
I cant say for sure .. CM's dialer does not work with service menu... but you defiantly not worried about root... your looking for the bootloader to be unlocked, not unlockable..
Click to expand...
Click to collapse
I've never gotten to CM on this phone so that's moot. I'm doing the service menu from the stock phone. And so far as I can tell the bootloader is unlocked.
I went back to a much older version of Flashtools (0.9.11) that dates from about the time I got the phone, but those drivers do not seem to install on Windows 10 at all.
But I'm not clear whether it is a driver problem, since some fastboot commands work fine.
Just read using emma with lollipop can screw your phone up... in fastboot mode can you 'fastboot getvar version' ?
here is the CM wiki - https://wiki.cyanogenmod.org/w/Install_CM_for_odin - good luck I don't think I can be of any help.
ham5 said:
Just read using emma with lollipop can screw your phone up... in fastboot mode can you 'fastboot getvar version' ?
here is the CM wiki - https://wiki.cyanogenmod.org/w/Install_CM_for_odin - good luck I don't think I can be of any help.
Click to expand...
Click to collapse
Yes, in fastboot mode I can do the getvar version. It says 0.5.
I had read the wiki; as mentioned that is why I was trying to flash boot.img.
As requested here is a fastboot session log:
Code:
U:\AndroidSDK\platform-tools>fastboot getvar version
version: 0.5
finished. total time: 0.002s
U:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (10668 KB)...
OKAY [ 0.340s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.340s
U:\AndroidSDK\platform-tools>fastboot flashing get_unlock_ability
...
^C
U:\AndroidSDK\platform-tools>fastboot devices -l
EPxxxxx47K fastboot
U:\AndroidSDK\platform-tools>fastboot devices
EPxxxxx47K fastboot
U:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (10668 KB)...
OKAY [ 0.340s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.354s
U:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (10668 KB)...
OKAY [ 0.340s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.353s
As you can see some commands work, some do not. Not sure the get_unlock_ability is even supposed to work as it looks like a late comer to fastboot and the phone is old.
Most articles I find posted about "command not allowed" do not seem to get as far as being able to use fastboot at all, but even if it is a driver issue, not sure what I can do about it, these are the latest drivers.
Ok, I've managed to get this to work. I can tell you what I did, but not why, but in case it helped someone else.
The bootloader showed unlocked, but I ran the flashtool option to unlock it again, then WITHOUT REBOOTING I did the fastboot option to flash the boot.img.
It appears that if you reboot (to stock) in between, it does something that at least makes it appear the bootloader is locked (the service menu shows it NOT locked still).
There's another thread here that implies you need to do it multiple times, but I think the issue is not a need to do it more than once, but a need to make sure that (at least a late version stock) does not get a chance to run, as it appears to do something.
I'm now happily on 12.1. Well, sort of happy, I finally noticed it says it doesn't support the 6506 (as opposed to the 6503) so I might not stay long, but at least I worked out what was wrong. Thanks to those who encouraged me to keep looking.
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
After trying to flash Pie my G7 stuck in fastboot mode. Download mode is unavailable so I not can reset the stock ROM.
After it reboots it boots into only to fastboot mode and is stuck in a loop now.
An even bigger problem is that now the bootloader is locked and the unlock.bin file can not unlock the bootloader.
ADB mode is not working!
DOWNLOAD mode is not working!
SYSTEM mod does not work!
There is only FASTBOOT mode that is in the loop
Does anyone have any suggestions?
Prosjak said:
After trying to flash Pie my G7 stuck in fastboot mode. Download mode is unavailable so I not can reset the stock ROM.
After it reboots it boots into only to fastboot mode and is stuck in a loop now.
An even bigger problem is that now the bootloader is locked and the unlock.bin file can not unlock the bootloader.
ADB mode is not working!
DOWNLOAD mode is not working!
SYSTEM mod does not work!
There is only FASTBOOT mode that is in the loop
Does anyone have any suggestions?
Click to expand...
Click to collapse
Try to get into lgup to flash a kdz, if you cant do that you might be SOL
LGUP does not detect phone, download mode is not working
hi
Prosjak said:
LGUP does not detect phone, download mode is not working
Click to expand...
Click to collapse
Please contact me, I can help you recover the device
PjLyTam said:
Please contact me, I can help you recover the device
Click to expand...
Click to collapse
How to contact you and how you can help me.
If you want to help write this here to help this benefit to anyone who has this or similar problem
Thank you
Prosjak said:
After trying to flash Pie my G7 stuck in fastboot mode. Download mode is unavailable so I not can reset the stock ROM.
After it reboots it boots into only to fastboot mode and is stuck in a loop now.
An even bigger problem is that now the bootloader is locked and the unlock.bin file can not unlock the bootloader.
ADB mode is not working!
DOWNLOAD mode is not working!
SYSTEM mod does not work!
There is only FASTBOOT mode that is in the loop
Does anyone have any suggestions?
Click to expand...
Click to collapse
Fastboot --set-active=a
LameMonster82 said:
Fastboot --set-active=a
Click to expand...
Click to collapse
Thank you for your reply
The problem is that the bootloader is locked
C:\ADB>Fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote: Slot Change is not allowed in Lock State)
finished. total time: 0.003s
Problem solved
Octoplus/Octopus LG 2.9.3
Reset FRP Lock
1. Attach testpoint, and connect phone with Micro USB cable (don´t use USB hubs!).
2. Check PC Device Manager, a new device should appear "Qualcomm HS-USB QDLoader 9008" or "Unknown Device" if you hadn´t installed a driver.
3. Release testpoint and press "Reset FRP Lock" button.
Emergency mode
To enter emergency mode, disconnect cable, disconnect battery, press and hold "Vol+" button and connect USB cable.
My lucky day
What version of G7 use?
Sent from my LM-G710 using Tapatalk
PjLyTam said:
Please contact me, I can help you recover the device
Click to expand...
Click to collapse
i got this problem too.. please help with that
Prosjak said:
Octoplus/Octopus LG 2.9.3
Reset FRP Lock
1. Attach testpoint, and connect phone with Micro USB cable (don´t use USB hubs!).
2. Check PC Device Manager, a new device should appear "Qualcomm HS-USB QDLoader 9008" or "Unknown Device" if you hadn´t installed a driver.
3. Release testpoint and press "Reset FRP Lock" button.
Emergency mode
To enter emergency mode, disconnect cable, disconnect battery, press and hold "Vol+" button and connect USB cable.
My lucky day
Click to expand...
Click to collapse
how i can do this?
My G710EM has a problem with my lockback BL. I can't boot the system and it will prompt "Your device has failed a routine safety check and will not boot. This may be a temporary problem. If this message occurs repeatedly, visit this link on Another device and refer to the red case:g.co/ABH Your device will power off automatically after a while.” With LGup brush kdz brush does not go in, fastboot “fastboot flash unlock unlock.bin” prompt is invalid
* Target reported max download size of 536870912 bytes
Sending 'unlock' (1 KB)...
OKAY [ 0.004s]
Writing 'unlock'...
FAILED (remote: Flashing Unlock is not allowed
)
Finished. total time: 0.011s
I don't know what to do.
I had the very same problem as OP. I tried to install pie with LGUP (G710EM20b_00_OPEN_EU_OP_0508.kdz) but ended in fastboot loop.
After whole night of trying different things (being a noob means less sleep) I managed to run the phone in download mode. Starting from there I was able to install my previous rom. Both failed update and rescue operations were done on Win 10.
What I tried and didn't work:
- Fastboot --set-active=a
Code:
C:\ADB>Fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote: Slot Change is not allowed in Lock State)
finished. total time: 0.003s
- Unlocking with unlock.bin. Didn't save the msg but saw it somewhere in another thread. I needed to install/point drivers first because the device was not recognized in Win.
- Solutions for G6 for going into download mode. The download mode icon was displayed for a second and then going to fastboot again.
- LG Flash Tool 2014 - I just followed a guide for older phones but it didn't work. Didn't try again.
What did work:
1. I found this post on reddit (remove spaces or PM me, I'm not allowed to post links):
Code:
https:// www .reddit. com/r/LGG3/comments/2qe5sr/in_need_of_serious_help_stuck_in_fastbootno/cn5f2qr/?utm_source=share&utm_medium=web2x
Quoting the post
At first, you'll need a working fastboot environment, you'll find out how to set it up on your own. Then you'll need the laf.img, I can upload mine if you want or I could help you extracting one out of a kdz file. Put the laf.img in the same folder like your fastboot.exe, then hold shift and right click, then click on "open command panel here" or however it's called in English. Type "fastboot flash laf laf.img" (Edit: It would probably better to use "fastboot boot laf.img" instead because of the bootloader lock). If that works, you at least have a working download mode.
Click to expand...
Click to collapse
2. I used LG_Firmware_Extract_v1.2.6.1 and extracted dz file from aforementioned pie file. The I extracted two laf files for the kz file. In my case they were: laf.img_180534 and laf.img_81990.
3. I took one of these files (sry, don't remember which one, but they have the same size - didn't check if they're the same) renamed it to laf.img and put a folder where fastboot.exe is.
4. I did
Code:
fastboot boot laf.img
and voila: the phone was in download mode!
5. After that LGUP the previous rom and the phone is working again. Here I needed few tries. At first the were some problems, then I tried different combinations (1.14, 1.15, w/ and w/o uppercut). I think LGUP 1.15 (1.14 with patch) did the work. I was able to "refurbish" the phone.
Hope it's useful for others. If anyone could prepare a guide from this description or/and tell why it worked - please feel free to do so.
I think I will wait some time before trying pie again
Garlikus said:
I had the very same problem as OP. I tried to install pie with LGUP (G710EM20b_00_OPEN_EU_OP_0508.kdz) but ended in fastboot loop.
After whole night of trying different things (being a noob means less sleep) I managed to run the phone in download mode. Starting from there I was able to install my previous rom. Both failed update and rescue operations were done on Win 10.
What I tried and didn't work:
- Fastboot --set-active=a
Code:
C:\ADB>Fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote: Slot Change is not allowed in Lock State)
finished. total time: 0.003s
- Unlocking with unlock.bin. Didn't save the msg but saw it somewhere in another thread. I needed to install/point drivers first because the device was not recognized in Win.
- Solutions for G6 for going into download mode. The download mode icon was displayed for a second and then going to fastboot again.
- LG Flash Tool 2014 - I just followed a guide for older phones but it didn't work. Didn't try again.
What did work:
1. I found this post on reddit (remove spaces or PM me, I'm not allowed to post links):
Code:
https:// www .reddit. com/r/LGG3/comments/2qe5sr/in_need_of_serious_help_stuck_in_fastbootno/cn5f2qr/?utm_source=share&utm_medium=web2x
Quoting the post
2. I used LG_Firmware_Extract_v1.2.6.1 and extracted dz file from aforementioned pie file. The I extracted two laf files for the kz file. In my case they were: laf.img_180534 and laf.img_81990.
3. I took one of these files (sry, don't remember which one, but they have the same size - didn't check if they're the same) renamed it to laf.img and put a folder where fastboot.exe is.
4. I did
Code:
fastboot boot laf.img
and voila: the phone was in download mode!
5. After that LGUP the previous rom and the phone is working again. Here I needed few tries. At first the were some problems, then I tried different combinations (1.14, 1.15, w/ and w/o uppercut). I think LGUP 1.15 (1.14 with patch) did the work. I was able to "refurbish" the phone.
Hope it's useful for others. If anyone could prepare a guide from this description or/and tell why it worked - please feel free to do so.
I think I will wait some time before trying pie again
Click to expand...
Click to collapse
Thanks for you guide.. I follow it but unfortunatly after "fastboot boot laf.img" I get this message from my LG:
"Your device has failed a routine safety check.... it will reboot after a while.."
davinik84 said:
Thanks for you guide.. I follow it but unfortunatly after "fastboot boot laf.img" I get this message from my LG:
"Your device has failed a routine safety check.... it will reboot after a while.."
Click to expand...
Click to collapse
I recall I also had some error msg, it could've been the same. Now I don't remember what I exactly did next as most my actions were more or less random. Either I tried the same command but with other laf.img file (from the rom I used before), or I tried to restart the phone into download mode (vol- and power together and then vol+ after screen goes black) or tried the same file again.
Hope it helps.
davinik84 said:
Thanks for you guide.. I follow it but unfortunatly after "fastboot boot laf.img" I get this message from my LG:
"Your device has failed a routine safety check.... it will reboot after a while.."
Click to expand...
Click to collapse
I have the same problem as well. I follow the guide but I received the same error message
domenico.dalpiaz said:
I have the same problem as well. I follow the guide but I received the same error message
Click to expand...
Click to collapse
Check if the phone is recognized in LG Bridge. If so, then choose update error recovery from software update tab. Again, I don't remember if it worked immediately or did I need to reinstall drivers and/or choose a proper driver in device manager (generic ADB vs LG...) and/or restart the phone.
domenico.dalpiaz said:
I have the same problem as well. I follow the guide but I received the same error message
Click to expand...
Click to collapse
I have same error too ...
DenisVelev said:
I have same error too ...
Click to expand...
Click to collapse
Based on other threads, e.g. https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903 and https://www.reddit.com/r/lgg6/comments/axd17d/lg_g6_eu_glh870_bricked_after_update_your_device/
try:
install the LG Bridge updater software on a computer, go to updates, click the "correct update errors" button. Then plug in your turned-off phone while holding down the volume up button. It should switch to download mode and reinstall all software from the PC. Yes, this will erase all data but it should unbrick your phone (unless the hardware's broken I guess)
Click to expand...
Click to collapse
Garlikus said:
Based on other threads, e.g. https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903 and https://www.reddit.com/r/lgg6/comments/axd17d/lg_g6_eu_glh870_bricked_after_update_your_device/
try:
Click to expand...
Click to collapse
Cannot put in download mode. Only Fastboot. For a secound show download mode after that show fastboot mode.
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?