[Q] adb / fastboot issues - Nexus 7 Q&A, Help & Troubleshooting

Using a linux PC I was attempting to unlock my bootloader following the directions at http://www.geek.com/articles/mobile/how-to-unlock-and-root-the-nexus-7-2012081/.
I can execute adb reboot bootloader just fine.... however when I issue the fastboot oem unlock command nothing happens on the tablet, and I see "< waiting for device >" in the terminal window. If I CTRL-C to break out and then do a 'adb devices' I see that there are no devices listed.
The Nexus 7 is a stock 16gb, C70 running 4.1.2/JZO54K.
Probably unrelated - I noticed in the last couple of weeks that the tablet has become slugging/laggy. Available space was at about 2gb. I removed some storage hungry games and got available space back up to about 5.5 gb.... but it's still laggy and touch detection barfs on occasion.
Any help/advice would be greatly appreciated.

Being on Linux make sure hat your fastboot command either has suid-bit set and owner is set to root or you need to run the command by sudo:
sudo fastboot devices
For adb there should be no problems, but adb is not working if your device is in fastboot mode.
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
Being on Linux make sure hat your fastboot command either has suid-bit set and owner is set to root or you need to run the command by sudo:
sudo fastboot devices
For adb there should be no problems, but adb is not working if your device is in fastboot mode.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Uggg.... Years of using Odin has made me stupid and lazy.... sudo did the trick. Thanks!!

Related

HELP!! =(

tried to install TWRP using these instrucitons
http://forum.xda-developers.com/showthread.php?t=1399023
tried everything i could find but im stuck in the kindlefire flash screen and cant go back or anything...is there anyway i can force the tablet to reboot into the OS? It doesnt connect to adb or anything
u are in fastboot. open a cmd prompt in the same directory your adb is in, and run fastboot commands. since twrp isn't installed, u will need to include -i 0x1949 device code or whatever it is, sorry I'm on my device so I can't type is specifically.
Sent from my HTC Glacier using xda premium
smirkis said:
u are in fastboot. open a cmd prompt in the same directory your adb is in, and run fastboot commands. since twrp isn't installed, u will need to include -i 0x1949 device code or whatever it is, sorry I'm on my device so I can't type is specifically.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
i tried doing that..i looked for all of the fast boot commands and it always says fastboot not a valid command etc etc....i tried an adb shell but that didnt work either..i even tried doing a restore with a thread thats in the general forums
Have you verified that fastboot is in fact on your machine? It should reside in the same folder as adb. Also, have you you either A) added the adb/fastboot folder in your Path or B) CDed into the folder where adb/fastboot resides to run the commands?
yay i got it to work...all i did was put in this
fastboot -i 0x1949 oem idme bootmode 4000
then this
fastboot -i 0x1949 reboot
which i got from here
http://forum.xda-developers.com/showthread.php?t=1398728&page=3
looks like all i had to do was add fastboot to the directory i was using so thanks =)
now i just have to wait for a full charge and i can try the twrp again
I also try to install CM7, but it's dead in recovery, I can't exit recovery now. For I have changed boot mode to "idme bootmode 0x5001", How can I change to normal mode ? When I reboot now, it goes to recovery mode directly.

[Closed] ADB Sideload issue

I had a problem and my wifi tablet is now bootlooping. So I looked into using adb sideload to re-install a rom.
When I enter sideload (twrp) and do adb devices it lists my device with sideload beside it.
C:\Windows\system32>adb devices
List of devices attached
0123456789ABCDEF sideload
when I try to sideload the rom adb c:\rom.zip I get error closed.
I tried adb usb to reset the usb but getting error closed.
C:\Windows\system32>adb usb
error: closed
By the way I am running windows 8
Really stuck any ideas!
I have been able to download the stock image and use fastboot to flash so I think I have the issue sorted!
I had the same problem three days ago. Try this method. It works for me write this on command " adb sideload filename.zip" hit enter don't put quote. If this not for you, go head try
adb push filename/data/media/
If you are on 4.2.2
adb push filename/data/media/0/
Good luck
Sent from my SPH-D710 using xda premium
Sideload mode is just a subfunction of your recovery. Create a blank .zip file and push it to the device using adb push C:\pathtozip\whatever.zip to abort. You'll be kicked back to your recovery and will be able to reboot.

[Linux] Unlock bootloader and root nexus 7 from command line

I had some problems using all the toolkit around and was not able to unlock my bootloader and root my phone. (Shame on me it was already three days since I got hands on my device). I had upgraded to 4.3 some toolkits didn't support my build etc.
Some pre-reqs:
1) BACKUP ( I back uped using the helium app, but forgot to backup my internal storage, and it too got wiped)
2) Thats all
I am using the wifi only version of this tablet (grouper)
I am using debian wheezy 7.2 64 bit
Here is what I did:
1)I installed adb and fastboot using wheezy-backports repository
Code:
apt-get install android-tools*
2) I connected my phone to my laptop in usb debugging mode and ran the following commands:
Code:
adb reboot bootloader
fastboot oem unlock
3) Then I downloaded the CF-ROOT script from this link
4)Extracted the file.
5)Some more commands
Code:
cd /path/to/extracted/folder/image
fastboot boot CF-Auto-Root-grouper-nakasi-nexus7.img
thats all folks, you have an unlocked bootloader and a rooted device.
That's the normal method if you don't use a toolkit! You are able to use that for example on windows too. It's nothing new
Sent from my Nexus 4 running Android 4.3
Yeah, I figured out that later! LOL
Thanks anyways

Not able to adb to Zuk Z1 from Mac.

hi All
I had a nexus 5 earlier. I have used adb and fastboot to install custom ROMs. My adb setup is fine.
I have put Zuk in dev-mode,
The following command works, The phone reboots.
fastboot -i 0x2b4c oem unlock-go​
None of the other commands work
adb reboot bootloader​
I have even tried to put phone is bootloader mode, manually using keys, and then tried to run adb commands. Even then it didnt work.
Do you think it can data wire issue, or am I missing some settings.
Running Mac OX El Captian.
viveksharma2108 said:
hi All
I had a nexus 5 earlier. I have used adb and fastboot to install custom ROMs. My adb setup is fine.
I have put Zuk in dev-mode,
The following command works, The phone reboots.
fastboot -i 0x2b4c oem unlock-go​
None of the other commands work
adb reboot bootloader​
I have even tried to put phone is bootloader mode, manually using keys, and then tried to run adb commands. Even then it didnt work.
Do you think it can data wire issue, or am I missing some settings.
Running Mac OX El Captian.
Click to expand...
Click to collapse
you need to add ./ infront of any command on mac.
like this
Code:
./adb reboot bootloader
the same goes for fastboot commands.
like this
Code:
./adb reboot bootloader
I am doing that already.

fastboot

Hi essential phone owners, I'm hoping you are willing to help me out.. Anyway, i used adb reboot bootloader for fastboot access after I enabled OEM unlock from the developer options. The device state is LOCKED. I then typed fastboot devices and received no permissions (verify udev rules). Does that mean I'm stuck on stock?
dirtyreturn said:
Hi essential phone owners, I'm hoping you are willing to help me out.. Anyway, i used adb reboot bootloader for fastboot access after I enabled OEM unlock from the developer options. The device state is LOCKED. I then typed fastboot devices and received no permissions (verify udev rules). Does that mean I'm stuck on stock?
Click to expand...
Click to collapse
What type of computer?
Hopefully, not using cable that came with the phone. Don't use it for flashing.
What are you trying to do?
tech_head said:
What type of computer?
Hopefully, not using cable that came with the phone. Don't use it for flashing.
What are you trying to do?
Click to expand...
Click to collapse
Thanks for your questions. I am using Ubuntu 18 I believe. I have a nexus 6p also, and adb/fastboot commands worked just fine with that phone. What i would like to do successfully is to unlock the bootloader and critical partition, flash twrp, and finally be able to flash AICP/Magisk.
Edit- from computer to phone I am using the extra type C USB cable that came with the 6p. And I must note that the essential is found using command adb devices. And command adb reboot bootloader gets me to the point of fastboot.
Ubuntu ?
sudo fastboot devices
I'm using Linux Mint, so basically Ubuntu. I created a file under /etc/udev/rules.d and put this line in it:
SUBSYSTEM=="usb", ATTR{idVendor}=="2e17", MODE="0666", GROUP="plugdev"
(My login ID is in the plugdev group.)
I'm able to execute adb and fastboot without needing sudo.

Categories

Resources