Related
Hi everyone,
Well I'm in that freak out stage.... where I am sure some of you have been.
Heres my issue...
I have a transformer prime that;
I just unrooted using Vipermod
Then did a factory reset
Now I am stuck in CWM recovery
I attempted to do a restore but after it gets done it brings me back into the recovery
I attempted to ADB but the command prompt opens and closes right away ( I assume from not being in USB debugging, which I cant get into without a rom)
I have no rom's currently downloaded into the prime as I just wiped everything in there as well.
Please i'll gladly pay $5 to anyone who can fix this without it breaking more (hard bricking if I havent already done so)
AHHH please guys help, I'm afraid it will run out of battery soon then I'll be royally screwedddd
anyone?
are you on windows 7?
yes windows 7 professional sp 1 32bit . to reiterate I am stuck in Clockwork mod Recovery without root, and with no roms on the internal SD. I have access to one restore that works but after it completes it reboots back in recovery.
birchnick10 said:
yes windows 7 professional sp 1 32bit . to reiterate I am stuck in Clockwork mod Recovery without root, and with no roms on the internal SD. I have access to one restore that works but after it completes it reboots back in recovery.
Click to expand...
Click to collapse
Turn on your tablet, let it boot into CWM.
Open cmd, cd to the directory with adb (for example cd C:\android), then copy this line of text below and right click > paste in the command prompt window.
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13
Click to expand...
Click to collapse
That should get you out of CWM into Android, assuming your restore works fine.
Attempted and got error device not found.
I have uninstalled the transformer drivers and also installed the universal drivers as said in other threads.
I assume to use ADB i need usb debugging on for it to read??
My issue is I cant get into any rom so turning on usb debugging is a no go.
can i fastboot push a rom to the internal sd card or better yet can i install a rom from the external SD card via Clockwork mod recovery?
birchnick10 said:
Attempted and got error device not found.
I have uninstalled the transformer drivers and also installed the universal drivers as said in other threads.
I assume to use ADB i need usb debugging on for it to read??
My issue is I cant get into any rom so turning on usb debugging is a no go.
Click to expand...
Click to collapse
Navigate to %android sdk folder%\extras\google\usb_driver, open android_winusb.inf and copy the following in the sections
"Google.NTx86" and "Google.NTamd64"
; TF201
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4D01&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4D03&MI_02
;
; Fastboot for all projects
%SingleBootLoaderInterface% = USB_Install, USB\VID_0B05&PID_4DAF
Click to expand...
Click to collapse
Save the file and then try running the adb command I gave again.
Says error device not found. I appreciate the help keep it coming it's keeping my hope alive. I really hope this isnt truly hard bricked.
I cant get ADB to read the transformer prime. When I type adb devices nothing shows up . it starts the daemon successfully but then doesn't show the tfp.
Thank you again for helping. I am honestly going to pay who ever finds the true fix. This stress sucks
birchnick10 said:
Says error device not found. I appreciate the help keep it coming it's keeping my hope alive. I really hope this isnt truly hard bricked.
I cant get ADB to read the transformer prime. When I type adb devices nothing shows up . it starts the daemon successfully but then doesn't show the tfp.
Thank you again for helping. I am honestly going to pay who ever finds the true fix. This stress sucks
Click to expand...
Click to collapse
Try the instructions here. Try using this only as a last-ditch resort.
it wont shut off either... i tried both of the above mentions and cant get adb to recognize the prime
Attempted both and stuck at recovery loop without root. any more ideas? is it possible to flash rom from external sd? or is there a recovery I could fastboot rhat has this feature?
Attempted both and neither work. I need to somehow get usb debugging enabled while in clockwork mod. Or figure out a way to install a rom via external SD card while in CWM. Any more help is appreciated!
birchnick10 said:
Attempted and got error device not found.
I have uninstalled the transformer drivers and also installed the universal drivers as said in other threads.
I assume to use ADB i need usb debugging on for it to read??
My issue is I cant get into any rom so turning on usb debugging is a no go.
Click to expand...
Click to collapse
No adb debugging is needed in cwm. Even without any ROM installed. Recovery is different from Android.
Try to long press power (at least ten seconds) to hard reboot, and see if it changes something in device detection.
Did a hard reset and it boots me back into Recovery.
I was able to get a new rom into the internal SD via the emergency/backup.zip method but after it completes and I do a reboot it just boots right back into recovery again.
Any help please is apprecaited.
$5 bounty for a fix via paypal
Oh joy. This one is a spaghetti western in the making.
Okay. Question first : Does Windows 7 RECOGNISE the device in any way shape or form. To find out if this can be done, you need to power up the device and hold the power and volume down buttons, DO NOT press volume up when it suggests a kernel image. If you get three icons, hit vol down once and up once, then plug the USB cable into the PC and the tablet.
If it sees "Something", you've a chance. Download the naked universal USB driver from the dev forum, install it and have your device pick it up on the windows computer. I'm assuming from your comments that you've GOT a working fastboot and adb so I'm going to skip the instructions on that.
If you do have a something, and it's recognised, hit fastboot -i 0x0b05 reboot, if it reboots of it's own accord at this point, you can confirm you have working ADB and Fastboot access. From there you've a few choices. My personal preference would be to ADB push a rom down -after- doing a rebuild of the recovery image via fastboot (I really recommend TWRP for this bit).
http://forum.xda-developers.com/showthread.php?p=26093546#post26093546 - This post here which I wrote will explain how to flash TWRP from fastboot access, presuming you can get it. Once that step is done, wipe EVERYTHING from TWRP, and I mean the whole nine yards, including /system. Raze the memory down to only things it can't actually nuke. Once that's done, reboot to fastboot protocol, get a ROM pushed via ADB and install from inside TWRP.
That -should- get you back in business. Though judging by the tangle you're in, I make no promises.
ADB wont recognize the device. I have installed and uninstalled the drivers about 5 times.
It wont boot into fastboot - just goes directly into Clockwork Mod recovery. Even while holding power and volume down text comes up that says looking for asus recovery. then says clockwork recovery and boots directly into that.
The only way I can get anything into the internal SD card is with MasterZen88's Emergency script tool that puts any 1 file into the internal SD card as backup.zip
It was unrooted prior to all of this as well.
*cringe*
If ADB isn't working -at all- and it's not using the naked USB drivers to get you any kind of workable access. You're starting to smell very much like a hard brick scenario. I'm honestly not sure if there's a way out of that. A lot of the solutions for unbricking absolutely require that the device is able to talk to the outside world, if it's not and the ADB shell is essentially telling you it's talking to dead air, you're in a world of pain.
It's a long shot but it may be worth speaking to ASUS to see if they are willing to, for a fee, restore your tablet to factory settings. Though I can't imagine that will be cheap or simple. If you are able to get an RMA or a means of getting ASUS to poke it, make sure to take photos. Their techies appear to have the worst case of butterfingers in the world.
Go over Pandaball's suggestion, because that's really the last step I can think of before contacting ASUS
My bootloader is locked and I am rooted.
I have been on the official jelly bean release for some time. On ICS I had done quite a few build.prop modifications without any issues. I swapped in the build.prop for US JB from the development forum and ever since I am stuck at a black screen.
I have done multiple factory resets from recovery and I have let the device discharge all the way down, but the same issue persists. When at the black screen I can see the MPT device listed in my device manager but I am not sure it is reaching a state I could even establish a ADB connection.
Does anyone have any advice? Since I am locked I may be able to send it in to asus if it comes to that, but I don't know if they will be able to determine that it was rooted and void the warranty.
If I can get into the stock bootloader / recovery, should I be able to push files to the internal SD?
adb rights
HockeyZ39 said:
My bootloader is locked and I am rooted.
I have been on the official jelly bean release for some time. On ICS I had done quite a few build.prop modifications without any issues. I swapped in the build.prop for US JB from the development forum and ever since I am stuck at a black screen.
I have done multiple factory resets from recovery and I have let the device discharge all the way down, but the same issue persists. When at the black screen I can see the MPT device listed in my device manager but I am not sure it is reaching a state I could even establish a ADB connection.
Does anyone have any advice? Since I am locked I may be able to send it in to asus if it comes to that, but I don't know if they will be able to determine that it was rooted and void the warranty.
Click to expand...
Click to collapse
if you can excces it through adb try setting the rights to 644 or 6755. it is usual a right problem.
leipy said:
if you can excces it through adb try setting the rights to 644 or 6755. it is usual a right problem.
Click to expand...
Click to collapse
I am wondering if I should be able to access ADB? I can get into bootloader/recovery and connect to the phone via fastboot/apx. But when ever I just let it sit with the blackscreen I only see a "Android MTP Device." I have used the universal naked drivers and get the same thing.
HockeyZ39 said:
I am wondering if I should be able to access ADB? I can get into bootloader/recovery and connect to the phone via fastboot/apx. But when ever I just let it sit with the blackscreen I only see a "Android MTP Device." I have used the universal naked drivers and get the same thing.
Click to expand...
Click to collapse
open a cmdbox in windows, type adb shell then su.
you should have #prompt then you can chmod 644 /system/build.prop
leipy said:
open a cmdbox in windows, type adb shell then su.
you should have #prompt then you can chmod 644 /system/build.prop
Click to expand...
Click to collapse
when I do adb devices nothing is listed (when sitting at the black screen). the MTP device always shows the error triangle in device manager regardless if I use the official drivers or naked ones.
HockeyZ39 said:
when I do adb devices nothing is listed (when sitting at the black screen). the MTP device always shows the error triangle in device manager regardless if I use the official drivers or naked ones.
Click to expand...
Click to collapse
did you try to unistall official driver and reinstall naked driver? the will conflict.
leipy said:
did you try to unistall official driver and reinstall naked driver? the will conflict.
Click to expand...
Click to collapse
Just to be "that prick," are you certain that the Naked Drivers were installed as thought, and you aren't still running the official set? You should have no problem accessing through ADB when in Recovery Mode if you're running the Naked Drivers.
Hello, this is the issue I'm having right now. Did anyone found a solution on this? Tried using naked drivers but still mtp device error when in recovery mode.
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
osikiri said:
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
Click to expand...
Click to collapse
My watch is now bricked because I have no way to get out of "adb sideload" mode...how did you get out of that mode? please tell me.
TjPhysicist said:
My watch is now bricked because I have no way to get out of "adb sideload" mode...how did you get out of that mode? please tell me.
Click to expand...
Click to collapse
I pushed the reset button on the back(the silver one right above the charging connectors) with a pen for about 10 seconds, and it rebooted.
osikiri said:
I pushed the reset button on the back(the silver one right above the charging connectors) with a pen for about 10 seconds, and it rebooted.
Click to expand...
Click to collapse
Wow ok, that's a LOT longer than I'm used to with other devices...THANK GOD I thought I had bricked it completely.
Anyway, now i have to figure out a way to get adb to work in sideload,...i mean CLEARLY it's possible lots of others doing it..
---------- Post added at 08:26 AM ---------- Previous post was at 07:41 AM ----------
TjPhysicist said:
Wow ok, that's a LOT longer than I'm used to with other devices...THANK GOD I thought I had bricked it completely.
Anyway, now i have to figure out a way to get adb to work in sideload,...i mean CLEARLY it's possible lots of others doing it..
Click to expand...
Click to collapse
Ok, does anyone know how to get my computer to recognise my watch in recovery mode? It's not about 'driver' the computer plain doesn't recognise that anything is plugged in at all.
I know the post is quite old already, but I experience exactly the same phenomenon...
I tried multiple PCs Linux and Windows,but non of them recognized the watch (neither on 4.4W1 nor on 4.2W2).
Anyone any idea?
Wikiwix said:
I know the post is quite old already, but I experience exactly the same phenomenon...
I tried multiple PCs Linux and Windows,but non of them recognized the watch (neither on 4.4W1 nor on 4.2W2).
Anyone any idea?
Click to expand...
Click to collapse
I believe u need to update the drivers.....I always go-to device manager...update driver..hit select from list..and choose android adb....
Sent from my LGLS990 using XDA Free mobile app
mrkrabs said:
I believe u need to update the drivers.....I always go-to device manager...update driver..hit select from list..and choose android adb....
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
The problem, as @osikiri stated, is that the device does not get recognized at all (no unknown devices in devicemanager and the sound that comes on plugging in a device does not come as well). Furthermore, afaik Linux does not even need any drivers
Had the same issue today... and the only way out way battery death and recharge
JaceAlvejetti said:
Had the same issue today... and the only way out way battery death and recharge
Click to expand...
Click to collapse
If this really helps (seems weird): I guess the exact setting could be necassary:
You simply ran out of battery while the watch was running(not recovery or fastboot) and then plugged it in and went directly (or not?) to the recovery?
Thanks in advance, would be really great to fix this!
Anyone ever find a fix to this? I'm trying to manually install the 5.0 update and I'm having the same issue. Every post I find with search tells me to update drivers but I'm on a Mac that doesn't even use ADB drivers. I've updated the SDK.
MSigler said:
Anyone ever find a fix to this? I'm trying to manually install the 5.0 update and I'm having the same issue. Every post I find with search tells me to update drivers but I'm on a Mac that doesn't even use ADB drivers. I've updated the SDK.
Click to expand...
Click to collapse
I'm doing the same thing and having the same issues!
Yeah, same issue for me as described.
Windows (Win7 x64 for me) doesn't even realise that the device is connected when it is in recovery mode. Although it will connected properly when booted normally.
+1 Any ideas?
Same issue for me. I've tried removing and replacing it on the cradle, killing and restarting the adb server, entering recovery by the touchscreen or by the adb/fastboot commands, clearing debugging keys, etc... Anybody have any other ideas?
---------- Post added at 07:25 PM ---------- Previous post was at 06:46 PM ----------
Ok, so it appears that the recovery img on 4.4w2 broke adb support or something. There are a few threads that suggest you can root and flash it or just wait for the OTA. We'll see whether I get the OTA before I have time to try this out.
Lollipop OTA Update: Download and How-To (Root Required)
I made a script that roots and updates your watch to 5.0.1 in a click.
[UTILITY][RESTORE][UNLOCK][ROOT] LG G Watch Tool
My way of doing it
osikiri said:
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
Click to expand...
Click to collapse
I've similar problem, and I've spent almost 3 hours to find the solution. I found that following solution work for me:
http://forum.xda-developers.com/g-watch-r/development/manual-ota-update-root-t2969845
I've changed the step slightly according to the comments inside the thread:
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot boot recovery.img)
// Do Not Flash 5.0.2 stock recovery
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
//you might have to reinstall the ADB drivers, just follow the simple step to install ADB driver
Done.
fi thought it was finally the solution, but fastboot oem unlock bricked my sony smartwatch3. I see tomorrow if with my windows pc i can fix with sony companion, otherwise i'll have to use the warranty
willisc said:
I've similar problem, and I've spent almost 3 hours to find the solution. I found that following solution work for me:
http://forum.xda-developers.com/g-watch-r/development/manual-ota-update-root-t2969845
I've changed the step slightly according to the comments inside the thread:
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot boot recovery.img)
// Do Not Flash 5.0.2 stock recovery
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
//you might have to reinstall the ADB drivers, just follow the simple step to install ADB driver
Done.
Click to expand...
Click to collapse
I attempted to install the custom OS, Asteroid, to my Zenwatch 2 (Sparrow) I followed the directions and now the watch will not boot, it is stuck at the Asus screen in a loop. I downloaded the recovery image, but I can not flash it do to Windows not recognizing the watch is connected. ADB gives me the error Device '(null)' not found. I have checked the device manager and there is nothing showing as an error (yellow !). Is there anyway I can recover from this?
jnelsoninjax said:
I attempted to install the custom OS, Asteroid, to my Zenwatch 2 (Sparrow) I followed the directions and now the watch will not boot, it is stuck at the Asus screen in a loop. I downloaded the recovery image, but I can not flash it do to Windows not recognizing the watch is connected. ADB gives me the error Device '(null)' not found. I have checked the device manager and there is nothing showing as an error (yellow !). Is there anyway I can recover from this?
Click to expand...
Click to collapse
go into fastboot mode and reflash your system.
dont work with fastboot / adb / root when you have no idea what youre doing!
matze19999 said:
go into fastboot mode and reflash your system.
dont work with fastboot / adb / root when you have no idea what youre doing!
Click to expand...
Click to collapse
The problem is that the watch is not being detected by Windows, therefore I am unable to reflash it, I clearly stated this in my original post.
jnelsoninjax said:
The problem is that the watch is not being detected by Windows, therefore I am unable to reflash it, I clearly stated this in my original post.
Click to expand...
Click to collapse
You said windows can't detect the watch in adb mode? What about the fastboot mode?
matze19999 said:
You said windows can't detect the watch in adb mode? What about the fastboot mode?
Click to expand...
Click to collapse
No, issuing the command: Fastboot devices shows nothing connected at all(the same goes for adb). It also does not show up in the windows device manager.
jnelsoninjax said:
No, issuing the command: Fastboot devices shows nothing connected at all(the same goes for adb). It also does not show up in the windows device manager.
Click to expand...
Click to collapse
Did you enter the fastboot mode?
matze19999 said:
Did you enter the fastboot mode?
Click to expand...
Click to collapse
The watch is showing CSC Fastboot Mode! So I would assume that it is in Fastboot mode
Were you able to get this fixed?
No, I have but been able to resolve this issue. It is not being recognized by Windows, therefore I can't flash the original os back to it.
Did you have TWRP installed prior to the failed flash?
CVertigo1 said:
Did you have TWRP installed prior to the failed flash?
Click to expand...
Click to collapse
No
I may have a way to get it working. I've had issues where Windows would not recognize a device, until I installed a cocktail of random drivers that eventually worked. What version of Windows are you running?
CVertigo1 said:
I may have a way to get it working. I've had issues where Windows would not recognize a device, until I installed a cocktail of random drivers that eventually worked. What version of Windows are you running?
Click to expand...
Click to collapse
I am running Windows 10 X64 build 1803
If you have the space, follow this: https://docs.microsoft.com/en-us/windows/wsl/install-win10
It allows you to run non-graphical Ubuntu on top of Windows. I've found sometimes my Windows 10 PC won't recognize things with adb or fastboot, but it works great in Ubuntu Bash. If you're familiar with Ubuntu at all, then it'll be a breeze to figure it out. If not, it's a pretty straight forward learning curve. It's also child's play to get adb and fastboot working right in Ubuntu, whereas it can be finicky in Windows.
Another alternative is to make a Linux Live CD using a USB drive, but that is a much more temporary solution.
---------- Post added at 10:17 AM ---------- Previous post was at 10:16 AM ----------
If none of those sound appealing, then I'd suggest deleting all drivers having to do with adb or fastboot, and start fresh by installing everything with this https://forum.xda-developers.com/showthread.php?t=2588979
CVertigo1 said:
If you have the space, follow this: https://docs.microsoft.com/en-us/windows/wsl/install-win10
It allows you to run non-graphical Ubuntu on top of Windows. I've found sometimes my Windows 10 PC won't recognize things with adb or fastboot, but it works great in Ubuntu Bash. If you're familiar with Ubuntu at all, then it'll be a breeze to figure it out. If not, it's a pretty straight forward learning curve. It's also child's play to get adb and fastboot working right in Ubuntu, whereas it can be finicky in Windows.
Another alternative is to make a Linux Live CD using a USB drive, but that is a much more temporary solution.
---------- Post added at 10:17 AM ---------- Previous post was at 10:16 AM ----------
If none of those sound appealing, then I'd suggest deleting all drivers having to do with adb or fastboot, and start fresh by installing everything with this https://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
OK, I will mess around and see what happens! I will have to do it tomorrow, but I will play around and see what happens!
Let me know how it goes and I'll walk you through it some more.
Any luck?
Sorry for the long time to reply. I installed ubuntu in window and installed the appropriate packages, however both ADB and Fastboot show nothing connected, even though the device is in CSC Recovery mode. Is there anything else I can try?
I actually tried playing with a few things on one of my computers the other day to try tracking this down. I was running into an issue where adb worked normally when the watch booted, but it would not work in recovery, and fastboot did not work either. Here is how I fixed it. Open up device manager in Windows and delete any driver pertaining to Android phones or adb. In my example, an Asus driver was causing the problem. I deleted that and reinstalled the generic Google drivers using the 15 second adb/fastboot installer that I posted in this thread. After restarting the computer, adb works perfect in Android and recovery, and fastboot works perfect as well.
TL/DR Delete all Android adb drivers in Windows, then run the 15 second adb installer that I posted in this thread, restart, and get your watch back to normal.
Assuming your bootloader is unlocked, you can flash everything I have posted here to get it running. https://forum.xda-developers.com/zenwatch-2/development/sparrow7-1-1debloat-rom-t3800067 If the bootloader is not unlocked, fastboot oem unlock will do it.
CVertigo1 said:
I actually tried playing with a few things on one of my computers the other day to try tracking this down. I was running into an issue where adb worked normally when the watch booted, but it would not work in recovery, and fastboot did not work either. Here is how I fixed it. Open up device manager in Windows and delete any driver pertaining to Android phones or adb. In my example, an Asus driver was causing the problem. I deleted that and reinstalled the generic Google drivers using the 15 second adb/fastboot installer that I posted in this thread. After restarting the computer, adb works perfect in Android and recovery, and fastboot works perfect as well.
TL/DR Delete all Android adb drivers in Windows, then run the 15 second adb installer that I posted in this thread, restart, and get your watch back to normal.
Assuming your bootloader is unlocked, you can flash everything I have posted here to get it running. https://forum.xda-developers.com/zenwatch-2/development/sparrow7-1-1debloat-rom-t3800067 If the bootloader is not unlocked, fastboot oem unlock will do it.
Click to expand...
Click to collapse
OK, I got windows to see the watch via fastboot and I downloaded the image that you posted (bloat free) now the watch started to boot, but so far it is just showing spinning dots, and has been for ~5 minutes or so, is this normal?
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.