Related
Hello. This is my 2nd post after here. I hope this will not bother anybody.
I have a situation. I did root my TF201 using CWM and virtuous_prime_s_9.4.2.21_v1 a month ago. Just now, I plan to sell my TF201. So, I go to the tablet setting and click at the reset data or something like that. I think it's just a normal data deletion process which is not effecting the rooted system. Unfortunately, after I reset / delete the data, the tablet is not going to boot. It just keep showing the CWM Recovery page with options to reboot the system, install zip from sdcard, wipe data, and so on. I selects to reboot the system, but nothing is happening. The tablet is turned off and turned back on with same display (CWM Recovery page).
What should i do?
titanbullet said:
Hello. This is my 2nd post after here. I hope this will not bother anybody.
I have a situation. I did root my TF201 using CWM and virtuous_prime_s_9.4.2.21_v1 a month ago. Just now, I plan to sell my TF201. So, I go to the tablet setting and click at the reset data or something like that. I think it's just a normal data deletion process which is not effecting the rooted system. Unfortunately, after I reset / delete the data, the tablet is not going to boot. It just keep showing the CWM Recovery page with options to reboot the system, install zip from sdcard, wipe data, and so on. I selects to reboot the system, but nothing is happening. The tablet is turned off and turned back on with same display (CWM Recovery page).
What should i do?
Click to expand...
Click to collapse
If you still have the virtuous prime file on there just.go to install zip and select it then reflash and youl be good to go. If not then you need to search on here for a program called knives and forks which is the easy way to install adb android debug bridge once installed download virtuous prime zip and place it in the same Rwhere you just installed adb then make sure you are in the cmw main screen and type adb push (filename) this will send the to tablet it may take up to 10 minutes and will just show a flashing cursor . Then flash.as normal. Sorry for spelling mistakes typing.g this on my phone and its being stupid
Uberjim said:
If you still have the virtuous prime file on there just.go to install zip and select it then reflash and youl be good to go. If not then you need to search on here for a program called knives and forks which is the easy way to install adb android debug bridge once installed download virtuous prime zip and place it in the same Rwhere you just installed adb then make sure you are in the cmw main screen and type adb push (filename) this will send the to tablet it may take up to 10 minutes and will just show a flashing cursor . Then flash.as normal. Sorry for spelling mistakes typing.g this on my phone and its being stupid
Click to expand...
Click to collapse
Thanks for the reply. I appreciate the info given. Will try to use the tool now since the rom file is no longer saved in the tablet.
Will update soon.
Thanks.
I'm just done installing the Knivesandforks on my win7. After that, the system automatically install the phyton. I dont know what its function, but as i follow this steps, i get error with cmd which shown as below:
Code:
c:\users\pc>adb reboot
error: device not found
i think i didn't miss any steps. Anybody here could help me with this?
Thanks in advance.
* my tablet is still in cmw main page and not showing anything even has been connected to the PC. i think that's the reason why the error occurs - device not found. anybody who could give some ideas on this will much appreciated.
You may need the fast boot drivers I wasn't sure if you would with being in cmw download those and extract them to the same folder as adb then load it up by using shift right mouse click run command and type and type adb devices if it shows up your good to go try the above steps again
titanbullet said:
Hello. This is my 2nd post after here. I hope this will not bother anybody.
I have a situation. I did root my TF201 using CWM and virtuous_prime_s_9.4.2.21_v1 a month ago. Just now, I plan to sell my TF201. So, I go to the tablet setting and click at the reset data or something like that. I think it's just a normal data deletion process which is not effecting the rooted system. Unfortunately, after I reset / delete the data, the tablet is not going to boot. It just keep showing the CWM Recovery page with options to reboot the system, install zip from sdcard, wipe data, and so on. I selects to reboot the system, but nothing is happening. The tablet is turned off and turned back on with same display (CWM Recovery page).
What should i do?
Click to expand...
Click to collapse
Recovery bootloop, see here, option 1a: http://forum.xda-developers.com/showthread.php?t=1514088
Use only Universal Naked Drivers (see related thread).
Sometimes even with proper drivers adb is a mess, then uninstall adb and search the net for a ready to use adb, there are some easy to find.
Uberjim said:
You may need the fast boot drivers I wasn't sure if you would with being in cmw download those and extract them to the same folder as adb then load it up by using shift right mouse click run command and type and type adb devices if it shows up your good to go try the above steps again
Click to expand...
Click to collapse
i did those steps again, but it seems like not helping. the script is only rebooting the tablet instead of giving me the option to flash the rom. i don't know if i did wrong. but as i know, i did as posted here.
* frust to see the cmw recovery for the whole day
Striatum_bdr said:
Recovery bootloop, see here, option 1a: http://forum.xda-developers.com/showthread.php?t=1514088
Use only Universal Naked Drivers (see related thread).
Sometimes even with proper drivers adb is a mess, then uninstall adb and search the net for a ready to use adb, there are some easy to find.
Click to expand...
Click to collapse
i did follow this tutorial
at first, install universal naked drivers - done
Now do the following:
Make sure your Prime is in Recovery mode (CWM) - YES
Open a cmd line on your pc - DONE
Type: "adb shell" - DONE
You should see a "#" now - YES
Once you have that "#", please type: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter] - Ok. This part was very difficult. I see the "#" but to type all those command, I can't. Why? Because the line in cmd instantly extended to a new line of command. I mean it just like I press the ENTER button. So, the line move to below and i can't finish typing all those command.
Now type: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 and press [Enter]
Exit the shell and reboot your Prime via CWM
It should not reboot to CWM automatically now. It either boots your ROM or is stuck at the splash screen. If it is stuck, boot to recovery and install any ROM you want.
Click to expand...
Click to collapse
titanbullet said:
i did follow this tutorial
at first, install universal naked drivers - done
Click to expand...
Click to collapse
Very strange, try to expand your command line window first. It doesn't matter if the text goes on following line, as long as you don't press Enter it's considerd as the same line. Try copy/paste instead ot typing.
Striatum_bdr said:
Very strange, try to expand your command line window first. It doesn't matter if the text goes on following line, as long as you don't press Enter it's considerd as the same line. Try copy/paste instead ot typing.
Click to expand...
Click to collapse
this is my first time, so i don't know if that was strange. ha ha. well, it's not about the command line which is extended or not. but the line itself creating a new line, as i said - just like i press the ENTER button.
i try to use copy-paste function (ctrl + c and ctrl + v). but i don't think it functions in cmd.
please help..
[Solved]
What i do?
I follow this step again
Installing the ADB again
And the most important thing is, pushing ROM into /sdcard should be like this:
Code:
adb push rom.zip /sdcard/rom.zip
And right-click copy paste function solving my strange cmd
Then i just follow the steps by installing the zipped rom thru cwm when my screen did not stuck at splash screens
Thanks for your kindness
My TF is now back to normal
THANKS!
Hello,
I have a Motorola Razr Maxx that is running the latest OS, and is rooted. I recently broke my screen and cannot get past the lock screen so I can start my VNC server (to continue using my phone without the screen). I have searched through what seems to be all posts on bypassing pattern lock and I have not been able to succeed yet due to permission denial for super user in ADB, not having sqlite3 on my phone, and not being able to flash anything onto it in recovery mode.
Does anyone have any ideas on how to bypass the lock screen without any use of the touchscreen? I have debugging mode on, and I have a access to view what is on the screen via hdmi cable or remote viewer.
Thanks in advance.
thazzle said:
Hello,
I have a Motorola Razr Maxx that is running the latest OS, and is rooted. I recently broke my screen and cannot get past the lock screen so I can start my VNC server (to continue using my phone without the screen). I have searched through what seems to be all posts on bypassing pattern lock and I have not been able to succeed yet due to permission denial for super user in ADB, not having sqlite3 on my phone, and not being able to flash anything onto it in recovery mode.
Does anyone have any ideas on how to bypass the lock screen without any use of the touchscreen? I have debugging mode on, and I have a access to view what is on the screen via hdmi cable or remote viewer.
Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2620456
Do you have the SafeStrap recovery? Root adb commands might work from there.
thazzle said:
Hello,
I have a Motorola Razr Maxx that is running the latest OS, and is rooted. I recently broke my screen and cannot get past the lock screen so I can start my VNC server (to continue using my phone without the screen). I have searched through what seems to be all posts on bypassing pattern lock and I have not been able to succeed yet due to permission denial for super user in ADB, not having sqlite3 on my phone, and not being able to flash anything onto it in recovery mode.
Does anyone have any ideas on how to bypass the lock screen without any use of the touchscreen? I have debugging mode on, and I have a access to view what is on the screen via hdmi cable or remote viewer.
Thanks in advance.
Click to expand...
Click to collapse
As long as your phone is rooted you should be able to do
Code:
adb shell su
.
If you've never given adb su priviledges before it may not work, in which case you should boot to recovery (if your rooted I'm assuming you have proper recover installed, and if you don't shame on you )
Any recover based on TWRP (SafeStrap, ClockworkMod, etc.) should give you adb access, you might need to mount the system partition though.
Tory Gaurnier said:
As long as your phone is rooted you should be able to do
Code:
adb shell su
.
If you've never given adb su priviledges before it may not work, in which case you should boot to recovery (if your rooted I'm assuming you have proper recover installed, and if you don't shame on you )
Any recover based on TWRP (SafeStrap, ClockworkMod, etc.) should give you adb access, you might need to mount the system partition though.
Click to expand...
Click to collapse
is there any way to boot to recovery without seeing whats on the screen? my hdmi doesn't recognize a connection until the phone is fully on
EDIT: I also never gave adb su priviledges, i rooted the phone shortly before breaking it.
Tory Gaurnier said:
As long as your phone is rooted you should be able to do
Code:
adb shell su
.
If you've never given adb su priviledges before it may not work, in which case you should boot to recovery (if your rooted I'm assuming you have proper recover installed, and if you don't shame on you )
Any recover based on TWRP (SafeStrap, ClockworkMod, etc.) should give you adb access, you might need to mount the system partition though.
Click to expand...
Click to collapse
Crap, I didn't think about that, if you have CWM then hold Volume up and Power, but it's going to be impossible to tell when it gets to recovery. If you have SafeStrap the touchscreen will have to work, if the touchscreen functions at all, then keep pressing the bottom left corner until you feel the vibration of the Recovery button.
Otherwise you might be out of luck.
Sent from my XT1049 using xda app-developers app
My screen and digitizer are broken on my S4. It is running the ME7 firmware (bought it that way), so I can't go back to MDK or apparently use any sideload stuff (such as CWM recovery).. At least, don't think so. I tried blindly doing it, but no luck.
I want to get app data off the phone (not just apks, but save data), was thinking adb, but when I boot into recovery, it shows unauthorized (on the PC that I rooted it with). When I plug in while it's booted, it never shows in the list of devices at all. Yes, I have the latest drivers from Samsung, yes, I have the latest adb, yes I have tried different cables. No, I cannot click or accept or navigate the phone at all through the touchscreen, nor even see what is displayed (broken!)
Is there any way to override this somehow and get access to the internal memory? I already copied everything that it shares by default through the file sharing mode (that still worked fine), but that doesn't give access to /data/data/ etc...
adb Summary:
- Recovery mode shows unauthorized. If I use the menu options (blindly), I can get it into sideload mode. I did something to get it into recovery status in adb, but I have no idea how I did that, and I wasn't able to get any data off in that mode either anyway.
- I can get it into Download mode, but flashing CWM didn't work (with heimdall), and adb shows nothing useful in that mode.
- Booted, it goes into the regular share files mode, but adb devices lists nothing.
Really hoping I won't have to either lose all my save data, or buy the docking station..
Thanks in advance!
Have exactly the same problem
Lander3 said:
My screen and digitizer are broken on my S4. It is running the ME7 firmware (bought it that way), so I can't go back to MDK or apparently use any sideload stuff (such as CWM recovery).. At least, don't think so. I tried blindly doing it, but no luck.
I want to get app data off the phone (not just apks, but save data), was thinking adb, but when I boot into recovery, it shows unauthorized (on the PC that I rooted it with). When I plug in while it's booted, it never shows in the list of devices at all. Yes, I have the latest drivers from Samsung, yes, I have the latest adb, yes I have tried different cables. No, I cannot click or accept or navigate the phone at all through the touchscreen, nor even see what is displayed (broken!)
Is there any way to override this somehow and get access to the internal memory? I already copied everything that it shares by default through the file sharing mode (that still worked fine), but that doesn't give access to /data/data/ etc...
adb Summary:
- Recovery mode shows unauthorized. If I use the menu options (blindly), I can get it into sideload mode. I did something to get it into recovery status in adb, but I have no idea how I did that, and I wasn't able to get any data off in that mode either anyway.
- I can get it into Download mode, but flashing CWM didn't work (with heimdall), and adb shows nothing useful in that mode.
- Booted, it goes into the regular share files mode, but adb devices lists nothing.
Really hoping I won't have to either lose all my save data, or buy the docking station..
Thanks in advance!
Click to expand...
Click to collapse
Did you find a fix?
So I recently pulled my G Watch back out and installed the most recent OTA 6.0.1, installed TWRP, the custom kernel, and rooted it. Obviously all of that required ADB to function correctly. It did perfectly. I installed ADB using the 15 Second ADB Installer, and used WinDroid Toolkit to flash TWRP and get into recovery and do the rest, that by default installed the ClockworkMod ADB drivers, all of this on my Windows 10 PC.
Those drivers worked perfectly. Until today.
I did a fresh install of CM13 on my Nexus 5 phone, which my watch was paired to at the time. I wiped everything and started over, so I then went into my watches settings and did the Factory Reset so I could start fresh and resync up with my new rom install on my phone.
But when I try to connect via ADB or even try to list the devices it always states "Unauthorized"...
For whatever reason, no matter what I try it wont bring up the prompt on my phone to authorize this computer.
I revoked Debug permissions on both my watch and my phone, tried different usb ports, turned off and on debugging in all its forms on both my watch and phone, plus restarted all my devices and my PC. I have tried google's adb drivers as well.
Not sure what else there is to possibly try, seems I have covered all my bases here. Just doesn't make sense that it worked and now all the sudden it doesn't...
Glad I'm not the only one having this problem! I've tried same exact methods you mentioned with no luck. Hopefully someone knows what's going on here and provide a solution
Maybe deleting the keys in the computer will fix it. If it works with another computer, then it's the solution. On Mac, they are stored in a folder called .android in the home folder, if I recall correctly. Anyway it should be easy to find online how to delete the keys in the OS you're using.
What I did was first authorise my phone to my pc's adb then I copied adb_keys from /data/misc/adb/ on my phone to my pc. I then copied that while in TWRP on my LG G watch to the same directory /data/misc/adb/ and rebooted to system and voila adb access restored!
Thanks for your suggestions guys, but I officially give up figuring this out. Tried other computers and it still says "unauthorized." Tried both Windows 10 and Ubuntu and still the same error. Some thing's definitely happened since Wear 6.0 update or maybe invisible kernel for 6.0?
@Xmaster24 I would try your TWRP way, but I never installed it as I didn't see the need for it. I don't think there's a way to install it now without ADB, is there?
xymic said:
Thanks for your suggestions guys, but I officially give up figuring this out. Tried other computers and it still says "unauthorized." Tried both Windows 10 and Ubuntu and still the same error. Some thing's definitely happened since Wear 6.0 update or maybe invisible kernel for 6.0?
@Xmaster24 I would try your TWRP way, but I never installed it as I didn't see the need for it. I don't think there's a way to install it now without ADB, is there?
Click to expand...
Click to collapse
adb is absolutely not required. seeing as you are running 6.0.1 get the custom TWRP from my root guide here and follow the instructions on flashing the recovery. Seeing as you don't have adb you will just have to power off your watch and boot it up and swipe top left to bottom right as soon as you see something
Xmaster24 said:
adb is absolutely not required. seeing as you are running 6.0.1 get the custom TWRP from my root guide here and follow the instructions on flashing the recovery. Seeing as you don't have adb you will just have to power off your watch and boot it up and swipe top left to bottom right as soon as you see something
Click to expand...
Click to collapse
Aaaaaand we're back, Houston! Thanks a lot man. Works great now.
Hello
I have the same problem as author of this thread. How can I get authorize adb? I need it to push some files to internal memory.
I suffer the same problem.
Ok, I found solove for this problem. Just what you need is back to stock for example by this method: http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863 or manually("fastboot flash" command): http://forum.xda-developers.com/g-watch/development/how-to-to-stock-rooted-6-0-t3339875 If you will have bootloop, you need to factory reset in twrp and reboot. To boot into twrp when you have bootloop you must enter to bootloader mode and write in cmd "fastboot boot YourTwrpName.img" command. I used twrp from this topic: http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512 After all you can update your watch to actual android wear version and again root/ change kernel.
Sorry for my bad english. I am not native speaker.
koszanty said:
Ok, I found solove for this problem. Just what you need is back to stock for example by this method: http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863 or manually("fastboot flash" command): http://forum.xda-developers.com/g-watch/development/how-to-to-stock-rooted-6-0-t3339875 If you will have bootloop, you need to factory reset in twrp and reboot. To boot into twrp when you have bootloop you must enter to bootloader mode and write in cmd "fastboot boot YourTwrpName.img" command. I used twrp from this topic: http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512 After all you can update your watch to actual android wear version and again root/ change kernel.
Sorry for my bad english. I am not native speaker.
Click to expand...
Click to collapse
Sorry, but, with ADB in "unauthorized" state it can't be done.
Guys, read Xmaster24's posts in first page. That's how I fixed it.
turbomann said:
Sorry, but, with ADB in "unauthorized" state it can't be done.
Click to expand...
Click to collapse
Why? Fastboot is diffrent thing than adb and it should work without 'adb authorization'. I used this method and it worked for me.
xymic said:
Guys, read Xmaster24's posts in first page. That's how I fixed it.
Click to expand...
Click to collapse
If you don't have copy of adb keys on watch sdcard, probably you cant use his fix(or am I wrong?). By the way, how can I mange files in TWRP mode without working adb? In TWRP is special option/ command for mange files by PC or something like that? If I connect watch to PC I can't see it as mass storage.
koszanty said:
Why? Fastboot is diffrent thing than adb and it should work without 'adb authorization'. I used this method and it worked for me.
If you don't have copy of adb keys on watch sdcard, probably you cant use his fix(or am I wrong?). By the way, how can I mange files in TWRP mode without working adb? In TWRP is special option/ command for mange files by PC or something like that? If I connect watch to PC I can't see it as mass storage.
Click to expand...
Click to collapse
You had flash 5.1.1 and then upgrade to 6.0.1? Are there bootloader compatible?
koszanty said:
If you don't have copy of adb keys on watch sdcard, probably you cant use his fix(or am I wrong?). By the way, how can I mange files in TWRP mode without working adb? In TWRP is special option/ command for mange files by PC or something like that? If I connect watch to PC I can't see it as mass storage.
Click to expand...
Click to collapse
You only need to have adb_keys file on the phone not the watch. In my case, I was able to use adb perfectly fine while I was in TWRP. Basically here's what I did:
1. Copy adb_keys file from your phone to computer. It is located in /data/misc/adb. If you can't see the file, you probably have to authorize your phone first with your computer.
2. Flash TWRP recovery from XMaster24's link using fastboot on your watch.
3. Boot into recovery. You don't need go into any options. While on the recovery homescreen, Just use this command to transfer adb_keys file into your watch:
Code:
adb push adb_keys /data/misc/adb
You can check using "Files" option in recovery to see if the file is transferred into the watch.
4. Reboot your watch and you should be able to access adb now.
You can do it your way as well, but using xmaster24's method saves time, I think
xymic said:
You only need to have adb_keys file on the phone not the watch. In my case, I was able to use adb perfectly fine while I was in TWRP. Basically here's what I did:
1. Copy adb_keys file from your phone to computer. It is located in /data/misc/adb. If you can't see the file, you probably have to authorize your phone first with your computer.
2. Flash TWRP recovery from XMaster24's link using fastboot on your watch.
3. Boot into recovery. You don't need go into any options. While on the recovery homescreen, Just use this command to transfer adb_keys file into your watch:
Code:
adb push adb_keys /data/misc/adb
You can check using "Files" option in recovery to see if the file is transferred into the watch.
4. Reboot your watch and you should be able to access adb now.
You can do it your way as well, but using xmaster24's method saves time, I think
Click to expand...
Click to collapse
In my case adb doesn't worked at all
turbomann said:
You had flash 5.1.1 and then upgrade to 6.0.1? Are there bootloader compatible?
Click to expand...
Click to collapse
It's compatibile but can occur bootloop. If you will have bootloop, you must do that what I write some posts earlier.
I'm realised that my phone with MM do the same bug, unauthorized, I look for adb_keys file but folder ADB is empty, then only remains flash and update on the watch.
Not sure if this is the proper place for this question; if not, please move. I picked up an Irulu Expro No. X9 Android tablet on eBay. It seems to work fine, except I can't get past the login screen. I tried many times the various key combinations to get it into recovery mode but none worked. Other suggestions had me putting it in debug mode first, but how to do that if you can't get logged in? I'm not concerned about saving any data, I would just like to be able to use it. I would appreciate any help to solve my problem. Thanx.
@jrockow
Have you ever tried to check whether the device is accessable by means of ADB?
Code:
adb devices
If it's accessable then you easily can remove the password lock. You do this by launching Android Settings via ADB as shown next:
Code:
adb devices
adb shell am start -a android.settings.SETTINGS
jwoegerbauer said:
@jrockow
Have you ever tried to check whether the device is accessable by means of ADB?
Code:
adb devices
If it's accessable then you easily can remove the password lock. You do this by launching Android Settings via ADB as shown next:
Code:
adb devices
adb shell am start -a android.settings.SETTINGS
Click to expand...
Click to collapse
Thanx for your quick reply.
adb devices doesn't list anything.
I thought you needed to enable USB debugging for ADB to work?
Don't know how to do that if I can't log in.
jrockow said:
Thanx for your quick reply.
adb devices doesn't list anything.
I thought you needed to enable USB debugging for ADB to work?
Don't know how to do that if I can't log in.
Click to expand...
Click to collapse
OK, so I'm somewhat of a rookie when it comes to ADB and FASTBOOT.
I'm not sure I have everything correct. I'm using an app called "Minimal ADB and Fastboot".
I have another tablet, same as the one I can't access, and I have turned on the developer options.
Even with that, I still can't see any devices when I run ADB.
FYI: When I look at devices in my PC it shows up as X9, which I believe is correct.
With my no password tablet, I can actually see all the directories of my Android on my PC.
If I try that with the other one don't see any directories.
jrockow said:
With my no password tablet, I can actually see all the directories of my Android on my PC.
Click to expand...
Click to collapse
Android's USB in that case is set to MTP mode, not ADB mode. MTP operates at the file level. Your Android device doesn’t expose its entire storage device to Windows computer. Instead, when you connect a device to your computer, the computer queries the device and the device responds with a list of files and directories it offers.
When Andoid's USB is in ADB mode, device can completely get controlled from Windows computer.
jrockow said:
I'm using an app called "Minimal ADB and Fastboot".
Click to expand...
Click to collapse
Serious Android device owners use the USB-driver ( AKA ADB ) as provided by device's OEM/Carrier.
jwoegerbauer said:
Android's USB in that case is set to MTP mode, not ADB mode. MTP operates at the file level. Your Android device doesn’t expose its entire storage device to Windows computer. Instead, when you connect a device to your computer, the computer queries the device and the device responds with a list of files and directories it offers.
When Andoid's USB is in ADB mode, device can completely get controlled from Windows computer.
Serious Android device owners use the USB-driver ( AKA ADB ) as provided by device's OEM/Carrier.
Click to expand...
Click to collapse
I was incorrect in my earlier post, when I said I turned on the developer mode on my "good" tablet and I still couldn't access it thru ADB.
I found out I really didn't have it turned on, and when I did I was able to execute the ADB commands.
That gets me back to my earlier post about not being able to turn on the developer mode on my "bad" tablet if I can't log in.
I would think with all the guys working on this stuff someone has come up with a way to get around a lost password?
I remind you, I tried the power+volume sequence many times, many ways, so I need a different approach; if there is one?
Thanx.
@jrockow
Because the tablet can't connect with PC via ADB then wondering why you don't contact seller of the tablet? Unlock Screen Password always can be done with Google Account Android device initially was bound to.
jwoegerbauer said:
@jrockow
Because the tablet can't connect with PC via ADB then wondering why you don't contact seller of the tablet? Unlock Screen Password always can be done with Google Account Android device initially was bound to.
Click to expand...
Click to collapse
I have already reached out to the seller. However, he knows nothing of the history of the tablet. He's just a guy who collects tons of electronics and sells them on eBay.
What really frustrates me is I can quite easily get my "good" tablet to enter recovery mode with the power+vol combination. I have tried many, many times to duplicate the same combo on the "bad" tablet and it just jumps over the recovery mode and boots to the logon screen.
Is it possible someone made some change to the tablet that won't allow it to go into recovery?
jrockow said:
I have already reached out to the seller. However, he knows nothing of the history of the tablet. He's just a guy who collects tons of electronics and sells them on eBay.
What really frustrates me is I can quite easily get my "good" tablet to enter recovery mode with the power+vol combination. I have tried many, many times to duplicate the same combo on the "bad" tablet and it just jumps over the recovery mode and boots to the logon screen.
Is it possible someone made some change to the tablet that won't allow it to go into recovery?
Click to expand...
Click to collapse
So, I've come to the conclusion that what I'm asking for just can't be done.
Can't enter reset with any key combo I've tried; can't use ADB because debugging not on; can't go to Google because I don't know who owned the phone before me.
If this were a PC device, there are multiple apps available to get around a lost password. I've done it many times.
I was really hoping there would be some Android genius out there who could help.
What a shame to realize that a perfectly good working device might as well be thrown in the trash.
jrockow said:
So, I've come to the conclusion that what I'm asking for just can't be done.
Can't enter reset with any key combo I've tried; can't use ADB because debugging not on; can't go to Google because I don't know who owned the phone before me.
If this were a PC device, there are multiple apps available to get around a lost password. I've done it many times.
I was really hoping there would be some Android genius out there who could help.
What a shame to realize that a perfectly good working device might as well be thrown in the trash.
Click to expand...
Click to collapse
If you know that the phone basically supports ADB, if the phone has a slot for external SD-card, if you can boot into Recovery Mode, if the Recovery Mode allows you to "apply update from sd-card" then you by means of an OTA can enable USB-debugging, then you can access the phone via ADB.
Currently I'm working on such an UPDATE.ZIP and will, if it's bug free, it publish here on XDA.
Personally don't own a phone what supports ADB: it's a HUAWEI Y7 2019. If you are willing to become a tester let me know it. I'll then PM you the link to the UPDATE.ZIP.
jwoegerbauer said:
If you know that the phone basically supports ADB, if the phone has a slot for external SD-card, if you can boot into Recovery Mode, if the Recovery Mode allows you to "apply update from sd-card" then you by means of an OTA can enable USB-debugging, then you can access the phone via ADB.
Currently I'm working on such an UPDATE.ZIP and will, if it's bug free, it publish here on XDA.
Personally don't own a phone what supports ADB: it's a HUAWEI Y7 2019. If you are willing to become a tester let me know it. I'll then PM you the link to the UPDATE.ZIP.
Click to expand...
Click to collapse
If I could boot into Recovery Mode my problem would be solved.