this assumes you already have adb/fastboot installed. Some sites seem to think these tools cannot be used with a U11 and a Mac.
Hogwash!
Get yourself to developer mode .
settings/about/software/more/tap build number 7 times rapidly.
badda bing.!
You'll now see Developer Options just about About in Settings.
Set USB debugging.
Connect to Mac via USB.
In Terminal on your Mac, type adb devices.
If you've installed adb/fastboot correctly, in a few secs a few lines will scroll with your devices serial.
Next, in Terminal, type adb reboot bootloader.
After 10 secs or so you'll get your bootloader screen with some info that might be handy if your gonna dig in.
Next type fastboot getvar all into Terminal. You'll get even more info about your phone that you may need.
Highlight it all and c&p into a Text Edit doc for future reference.
To get out of bootloader, press the volume up/down buttons untill you see what you want to do.
Then press the Power button to select.
Related
How to unbrick soft bricked Atrix, I installed http://www.youtube.com/watch?v=wQvrEH74dgI and when I installed Gapps, it didn't started and when I tryed system restore it did so but when it started it got stucked at "M" screen and nothing else is happning.
knotabs loca
manyelski said:
How to unbrick soft bricked Atrix, I installed http://www.youtube.com/watch?v=wQvrEH74dgI and when I installed Gapps, it didn't started and when I tryed system restore it did so but when it started it got stucked at "M" screen and nothing else is happning.
Click to expand...
Click to collapse
I'm in a similar situation. I was asked to use latest CWM. I happened to use Tenfar's CWM that came with the boot loader unlock.
I haven't tried it yet. Will give a shot this weekend
Hi!
I'd suggest the following:
1. Install ADB from the Android SDK.
2. Turn on Settings -> Applications -> Development -> USB Debugging.
3. Connect your phone to a computer. (If you do not have a cable, have it connect to the same local network.)
4. Select 'Motorola Phone Portal' as connection method.
5. Reboot while holding Vol. Down.
6. When you see 'Fastboot', tap Vol. Down until 'Early USB Enumeration' appears.
7. Press Vol. Up.
8. Go to a command line where your ADB executable is.
8a. If you have connected by network, find out your device's IP address and type adb connect <IP>
9. Type adb wait-for-device
10. Type adb logcat
Now, Android's system log should appear. Scroll up and carefully look for error messages - the cause for this could be widely different, I had the same problem with 'Error: ID mismatch' or something along those lines. It is likely that the application itself is the problem, and that uninstalling it will fix things. If you come to that conclusion from the log:
11. Terminate logcat (Ctrl+C, usually)
12. Type adb shell
13. Type cd /data/app
14. Type ls *gapps* (If that fails, type ls and look manually)
15. Take the file name for Gapps' .apk and type rm <filename>
16. Reboot
17. Rejoice
Sincerely,
V
PS: Will I always have to enter a captcha when posting, or is this just for noobs? I HATE captchas.
Intelensprotient said:
Hi!
I'd suggest the following:
1. Install ADB from the Android SDK.
2. Turn on Settings -> Applications -> Development -> USB Debugging.
3. Connect your phone to a computer. (If you do not have a cable, have it connect to the same local network.)
4. Select 'Motorola Phone Portal' as connection method.
5. Reboot while holding Vol. Down.
6. When you see 'Fastboot', tap Vol. Down until 'Early USB Enumeration' appears.
7. Press Vol. Up.
8. Go to a command line where your ADB executable is.
8a. If you have connected by network, find out your device's IP address and type adb connect <IP>
9. Type adb wait-for-device
10. Type adb logcat
Now, Android's system log should appear. Scroll up and carefully look for error messages - the cause for this could be widely different, I had the same problem with 'Error: ID mismatch' or something along those lines. It is likely that the application itself is the problem, and that uninstalling it will fix things. If you come to that conclusion from the log:
11. Terminate logcat (Ctrl+C, usually)
12. Type adb shell
13. Type cd /data/app
14. Type ls *gapps* (If that fails, type ls and look manually)
15. Take the file name for Gapps' .apk and type rm <filename>
16. Reboot
17. Rejoice
Sincerely,
V
PS: Will I always have to enter a captcha when posting, or is this just for noobs? I HATE captchas.
Click to expand...
Click to collapse
I can't turn on my phone, or DO ANYTHING with it, the only thing is that I get "M" screnn taht's all, if i want to turn it down I hae to do a battery poll.
Excactly, that's what Early Enumeration is for Usually, USB is loaded when the OS is up, I suppose - at least you can't normally connect with ADB during boot. However, with Early Enumeration set, you can connect while the phone is still booting and access every capability ADB or the shell is able to provide. (Granted, uninstalling the .apk in question with adb uninstall did not work for me, that's why I posted the manual approach, but that may have been an error on my side.)
I wonder if my issue is the same. Mine is stuck in a 'dual core' reboot over and over.. I can't get into recovery mode or anything. Sometimes I hate phones.
JeRrYFaR said:
I wonder if my issue is the same. Mine is stuck in a 'dual core' reboot over and over.. I can't get into recovery mode or anything. Sometimes I hate phones.
Click to expand...
Click to collapse
Mine is tha same
Stuck in mortorola unlocked boot screen
Intelensprotient said:
Hi!
I'd suggest the following:
1. Install ADB from the Android SDK.
2. Turn on Settings -> Applications -> Development -> USB Debugging.
3. Connect your phone to a computer. (If you do not have a cable, have it connect to the same local network.)
4. Select 'Motorola Phone Portal' as connection method.
5. Reboot while holding Vol. Down.
6. When you see 'Fastboot', tap Vol. Down until 'Early USB Enumeration' appears.
7. Press Vol. Up.
8. Go to a command line where your ADB executable is.
8a. If you have connected by network, find out your device's IP address and type adb connect <IP>
9. Type adb wait-for-device
10. Type adb logcat
Now, Android's system log should appear. Scroll up and carefully look for error messages - the cause for this could be widely different, I had the same problem with 'Error: ID mismatch' or something along those lines. It is likely that the application itself is the problem, and that uninstalling it will fix things. If you come to that conclusion from the log:
11. Terminate logcat (Ctrl+C, usually)
12. Type adb shell
13. Type cd /data/app
14. Type ls *gapps* (If that fails, type ls and look manually)
15. Take the file name for Gapps' .apk and type rm <filename>
16. Reboot
17. Rejoice
Sincerely,
V
PS: Will I always have to enter a captcha when posting, or is this just for noobs? I HATE captchas.
Click to expand...
Click to collapse
How do you find the device's IP address?
Hi All,
After seeming that I'm locked out of my own device for 72 hours, I managed to scour the net and use parts of other tutorials to successfully bypass the "you're device was reset, please log in" loop.
So I should point out I was running a Pure Nexus rom running 6.0 with a custom recovery, you're results may differ but you've got nothing to loose.
Pre Requisite
ADB and Fastboot - You don't need to spend an hour installing the whole kit, just visit http://developer.android.com/sdk/index.html and scroll right down to the section where it says "SDK Tools Only" and click on "installer_r24.4.1-windows.exe"
Once installed the SDK manager will open, now make sure the top 3 are checked which are:
Android SDK Tools
Android SDK Platform-tools
Android SDK Build-tools
And also scroll down in the list to find Google USB Driver
Once all of that is done download the latest Google USB drivers (although the SDK installs USB drivers it still shown an exclamation mark in device manager") http://developer.android.com/sdk/win-usb.html
To install those USB drivers just go into device manager and if you se Nexus 6 under "Other Devices" just right click and click update driver software and then click browse my computer and get it to scan the Google USB driver folder you downloaded.
restart your phone into recovery (Volume Down and Power button)
now again in device manager make sure the Nexus 6 doesn't have a yellow icon identifying there's a problem with drivers or that the nexus 6 is listed in other devices. If either of those are present right click and update drivers > browse from computer and select the Google USB drivers you downloaded previously.
Bypass FRP
With all that confirmed restart your Nexus and leave it on the Welcome screen.
Now, you need to get into platform tools which is located:
C:\Users\YOURUSERNAME\AppData\Local\Android\android-sdk\platform-tools
if you can't see AppData you need to enable hidden files and folders
once in platform tools hold SHIFT and right click any blank space and click "Open command window here"
then type "adb devices" and it should list your nexus under devices, if it doesn't open device manager and check your drivers.
If it does show your nexus execute this command which edited from another source:
"adb shell am start -n com.android.settings/.Settings"
Your nexus will now open the settings menu =] in settings go to "Backup & reset" then click "Factory data reset" (although it says it wipes user data, mine was untouched, I can't say the same for so you may lose some data if you proceed)
your phone will reboot and in my case it opened my custom recovery and executed a script, the phone will restart again and go to boot, hold the power button to force shut down the nexus and boot into recovery mode. In recovery mode flash a ROM, if you don't have a ROM download one on your PC and then connect your Nexus to your PC via USB and copy it over.
Once the ROM is installed you won't get the "you're device was reset" screen.
"
You left out some key details which are covered in the guide I wrote up a few days ago. Here's the link.
http://forum.xda-developers.com/showthread.php?t=3261846
Sent from my Nexus 6 using Tapatalk
this does not work, because in order to adb devices to populate anything you would of had to enable usb debugging from within the phone, and if you're locked our from FRP, you cant access the settings to turn on the usb debugging
Bootloader LOCKED .. and asking for gmail ID ??
Hi,
I recently rooted my Samsung Galaxy Tab A thanks to the wonderful folks of this forum. However, now that it's rooted I can't seem to connect to it via adb. For example, I see the device listed when I run "adb devices", but it is listed as "unauthorized". I no longer received the prompt to allow USB debugging. More precisely, I can still access the developer options and see that "USB debugging" is enabled, I just don't receive the pop-up prompt to "Allow USB debugging?" that list my local computer's RSA fingerprint/etc after I plug in the usb... the device just remains unauthorized and never asks me to click ok to allow usb debugging.
As suggested elsewhere, I tried removing the adbkey and adbkey.pub in the .android directory on my local computer and the killing/starting the adb server to generate new keys on the local machine, but that also doesn't seem to help...
Additionally, I noted that there is also no longer a button under developer option to "Revoke USB authorizaiton" (maybe because there are now no longer any keys in /data/misc/adb/adb_keys ?)
Any idea how to get adb shell to work again? Or maybe it not possible after rooting?
Thanks!
__adam_ said:
Hi,
I recently rooted my Samsung Galaxy Tab A thanks to the wonderful folks of this forum. However, now that it's rooted I can't seem to connect to it via adb. For example, I see the device listed when I run "adb devices", but it is listed as "unauthorized". I no longer received the prompt to allow USB debugging. More precisely, I can still access the developer options and see that "USB debugging" is enabled, I just don't receive the pop-up prompt to "Allow USB debugging?" that list my local computer's RSA fingerprint/etc after I plug in the usb... the device just remains unauthorized and never asks me to click ok to allow usb debugging.
As suggested elsewhere, I tried removing the adbkey and adbkey.pub in the .android directory on my local computer and the killing/starting the adb server to generate new keys on the local machine, but that also doesn't seem to help...
Additionally, I noted that there is also no longer a button under developer option to "Revoke USB authorizaiton" (maybe because there are now no longer any keys in /data/misc/adb/adb_keys ?)
Any idea how to get adb shell to work again? Or maybe it not possible after rooting?
Thanks!
Click to expand...
Click to collapse
I finally solved this problem.... I don't think it was particular to the Galaxy Tab A.
In order to get adb working again I had to put the device into recovery mode (power down, then power up while holding power, up-volume, home button). I then went to the terminal application of the Team Win Recovery. In terminal I issues "stop adbd" then "start adbd". At this point the device now shows up on the local host PC when I run "adb devices" (it shows up as "recovery" rather than unauthorized). I can adb root/shell to the device now. This is really all I need to do. I expect this will solve my problem in non-recovery mode as well. Or, at this point I can push my PC pub key to the device and it should be fine.
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Same issue - following
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Sunil_511 said:
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Click to expand...
Click to collapse
Hi, Sunil_511...
Bit speculative this, and I can't say for certain if the following solution would work, because I've never had this problem myself. It also requires that your Nexus 7 be in a fully bootable state.
Go to your Nexus 7 Developer Options in the devices settings and tap on 'Revoke USB debugging authorisations'. Tap on OK to confirm. See attached screenshot.
This, theoretically, should wipe the slate clean.
Reboot both your N7 and your PC/laptop and when you next reconnect your N7 to your PC/laptop, you'll be asked to authorise this new USB connection when you perform some action that requires it.
Well, that's the plan anyway.
Good luck?.
Rgrds,
Ged.
Nope, in my case my tab is not booting to recovery or system. The only option is adb and it is showing unauthorized. My last option what i think off is to change the motherboard.
Following
I have the same error and like to follow
Sunil_511 said:
I have the same error and like to follow
Click to expand...
Click to collapse
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
thanks buddy, i have tried pushing the adb keys but no luck. I will try tge second option. Will let you know after trying.
No difference still the same
BxG4ever said:
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Click to expand...
Click to collapse
tnsmani said:
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
Click to expand...
Click to collapse
Tried your suggestion.. Which i might have tried eventually from googling.. Doesn't make any difference.
Fixed
After doing all the researches, i had to buy a new motherboard and then replace it. Installed new rom and now using it. Spared about 1400INR for a 32 gig version.
Y cant i get fastboot drivers to read in Windows 10. I have updated the software to the latest update. Developer options are turned on. USB configuration is set to file transfer. In a regular state Windows 10 readds the phone and I can access the contents of the phone. I opened a power shell (regular and as admin) I typed "adb devices" it reads. (I have enabled advanced reboot.) I use the command "adb reboot-bootloader" in boots to fastboot. Now it loses connection. I Open the Run dialog box by pressing Windows Key+R. Type “devmgmt.msc” besides Android is a yellow triangle, then click Update Driver.A new window will pop up. Select the ‘Browse my computer for driver software’ option. I copied the drivers from the OnePlus 5 folder. Try to install but nothing. This is where in stuck. Please help. Thanks
trulane said:
Y cant i get fastboot drivers to read in Windows 10. I have updated the software to the latest update. Developer options are turned on. USB configuration is set to file transfer. In a regular state Windows 10 readds the phone and I can access the contents of the phone. I opened a power shell (regular and as admin) I typed "adb devices" it reads. (I have enabled advanced reboot.) I use the command "adb reboot-bootloader" in boots to fastboot. Now it loses connection. I Open the Run dialog box by pressing Windows Key+R. Type “devmgmt.msc” besides Android is a yellow triangle, then click Update Driver.A new window will pop up. Select the ‘Browse my computer for driver software’ option. I copied the drivers from the OnePlus 5 folder. Try to install but nothing. This is where in stuck. Please help. Thanks
Click to expand...
Click to collapse
Hello, please use the drivers provided here if not tried yet https://forum.xda-developers.com/on...k-bootloader-flash-twrp-t3624877/post72748916
Thanks that's the guide I used 2 flash, n install magisk. I jus used one of the options that was listed on the computer, I was a random Google drivers. Then it lit up. Thanks 4 the guide, it was very helpful
Done