Database Users

help with ADB and unrooting?

i downloaded toolkit and unlocked my phone , rooted it i installed chainfire 3d and now its stuck on the nexus logo
i tried to unroot it but when i connect it and open the toolkit it says that there is no adb connection so what the **** is that ?? so i relocked it and tried to root it again but its still telling me that there is no adb connection so i found out that i can fix this by going to settings/devloper/the check the bugging usb but the problem is i cant boot in this ****ty device :S
and i installed the nexus driver on pc
but really i dont know what should i do :S:S
i swear that i will never root my nexus again
please big help

Re: help again :S
If you do not know what ADB is then you really have no business rooting any android device.
ADB stands for android debugging bridge. You need to install this on your PC before f##%%*g about with your device. Google how to install Android SDK (which includes ADB). There are plenty of threads on XDA.

And the thread title should be something more descriptive than 'help again' in order that someone who actually respects this forum by searching first will find threads with the same issue.

killall said:
If you do not know what ADB is then you really have no business rooting any android device.
ADB stands for android debugging bridge. You need to install this on your PC before f##%%*g about with your device. Google how to install Android SDK (which includes ADB). There are plenty of threads on XDA.
Click to expand...
Click to collapse
hey my friend i did what u told about the SDK but when i open toolkit its says "daemon not running. starting it now on port 5037" then it says " ADB server didnt ACK " then "failed to start daemon " what should i do :S ????

Check that your usb drivers are correctly installed. Look at the FAQ in Nexus Toolkit thread.

Unlocking the Nexus 7 (2013) Bootloader

This is the same as any other Nexus device.
WARNING. As is normally the case, this WILL factory reset your device.
Install the Android SDK (and Google USB driver).
Android SDK
Google USB Driver (Windows)
Enable USB debugging on the Nexus 7.
Unlock Developer Options by going to Settings > About Tablet and clicking on the build number seven times.
Go to Settings > Developer Options and check USB debugging. Click OK on the warning.
Connect the Nexus 7 via USB and reboot the Nexus 7 into the bootloader.
Note: Users have reported failures and "Access is Denied" errors when connected via USB 3.0 ports so use USB 1.1 or 2.0 to be on the safe side.
Open a command line / terminal and navigate to your SDK platform-tools directory.
Enter
Code:
adb reboot bootloader
and hit enter.
Once the Nexus 7 boots to the bootloader, unlock it
At the command line / terminal enter
Code:
fastboot oem unlock
and press enter.
On the Nexus 7, use the volume up button to select 'Yes' on the 'Unlock bootloader?' screen.
Press the power button to save your choice and verify on the next screen that you see 'LOCK STATE - UNLOCKED' at the bottom.
Use your volume keys to select 'Start' and click the power button to factory reset and reboot.
Enjoy your unlocked bootloader!

Do you have the usb drivers installed? That happened to me ("old" n7) when I didn't have the usb drivers installed.

may need to update your drivers for it to be able to see the device.
when you try adb devices while it is on does it kick back the device id number?
i haven't tried yet as i knew the drivers out currently would be an issue.

gksmithlcw said:
Any ideas? I tried I tried the ol' fastboot oem unlock command and it just sits there with the < waiting for device > message.
Click to expand...
Click to collapse
Perhaps it needs new adb/fastboot drivers ? I'm still charging mine, so I haven't tried. Sorry. Maybe the new driver comes with the 4.3 SDK ?

gksmithlcw said:
Any ideas? I tried I tried the ol' fastboot oem unlock command and it just sits there with the < waiting for device > message.
Click to expand...
Click to collapse
First off (don't mean to be a d!ck) but this thread belongs in "General", or "Q&A", because you haven't posted a development thread.
Second, unlocking the boot loader is just as easy as the first Gen Nex7. I had mine unlocked within 5 minutes of getting it home.
As others have said, make sure your drivers are installed, or ADB won't even recognize the device.

mrancier said:
Perhaps it needs new adb/fastboot drivers ? I'm still charging mine, so I haven't tried. Sorry. Maybe the new driver comes with the 4.3 SDK ?
Click to expand...
Click to collapse
I updated my SDK when 4.3 dropped but I did have to go snag the Google USB driver and install it to get the N7 to be recognized.

ATGAdmin said:
First off (don't mean to be a d!ck) but this thread belongs in "General", or "Q&A", because you haven't posted a development thread.
Second, unlocking the boot loader is just as easy as the first Gen Nex7. I had mine unlocked within 5 minutes of getting it home.
As others have said, make sure your drivers are installed, or ADB won't even recognize the device.
Click to expand...
Click to collapse
1. You may be right (as far as my posts go) but how am I to ever make a dev post if I'm not allowed to make a first post in a dev forum?
2. This /is/ a dev-related post.
3. My feelings wouldn't be hurt if the mods felt the need to move the post.

Yeah I had to install the google usb drivers from the SDK in device manager of Windows to get the n7 recognized.

Thanx. Just got home with my new nexus 7....bootloader now unlocked :highfive:

Nevermind it literally is that as the command.
Sent from my Nexus 7 using Tapatalk 4 Beta

keynith said:
Can you update it with the commands? So people don't have to search
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
The commands are there...
Also, unlocked mine not 5 minutes after opening on Ubuntu 13.10.

no idea why my device won't be read by adb. but i manually rebooted to bootloader and fastboot oem unlock took care of that. time to wait for root/recovery

Worked great thanks!
---------- Post added at 03:32 PM ---------- Previous post was at 03:31 PM ----------
smirkis said:
no idea why my device won't be read by adb. but i manually rebooted to bootloader and fastboot oem unlock took care of that. time to wait for root/recovery
Click to expand...
Click to collapse
Make sure you update your files from the SDK Manager. It had updated USB driver which from there it would install the proper drive and then it worked form me.

The trick, as stated in the Nexus Toolkit after driver install, is that you need to change the tablets usb settings from MTP to PTP. Tablet was immediately seen using "old" nexus toolkit universal usb drivers (old = i did not download the new SDK). I choose toro 4.2.2 (because it doesn't matter for unlocking) and then told it to unlock. worked like a charm.
Now the question is ... how long does it take to reboot cause mine is taking forever!!!
OK it booted. So yeah the Nexus 7 Toolkit ver 5.0 worked just fine to at least unlock. I did not root (4.3 still too buggy) or install a custom recovery yet.

Stock recovery, pretty please?
My dumbass flashed TWRP for Grouper. Wouldn't boot, so I tried erasing the recovery in hopes it would self-restore. No dice. Can't seem to find recovery-from-boot.p either. No boot and still no custom recovery for this puppy. :crying:
Would someone be the kindest person on earth and pull & post the stock recovery...or tell me how to find and flash a back-up copy already stored on my nexus? Google hasn't even posted the img files yet. My new toy is borked and Daddy wants to play tonight!
Thank you!

My body and my 7 are ready for a recovery!
Thank you!

treoo0_1 said:
My dumbass flashed TWRP for Grouper. Wouldn't boot, so I tried erasing the recovery in hopes it would self-restore. No dice. Can't seem to find recovery-from-boot.p either. No boot and still no custom recovery for this puppy. :crying:
Would someone be the kindest person on earth and pull & post the stock recovery...or tell me how to find and flash a back-up copy already stored on my nexus? Google hasn't even posted the img files yet. My new toy is borked and Daddy wants to play tonight!
Thank you!
Click to expand...
Click to collapse
I'd be happy to, but am having a hard time finding the correct ADB command.

isnt the new N7 files called Razor instead of grouper ? or is that just what the device was called prior to launch

adb pull
jc monkeyballs said:
I'd be happy to, but am having a hard time finding the correct ADB command.
Click to expand...
Click to collapse
Can you use
Code:
adb pull %PATH TO BE PULLED FROM% %PATH TO PLACE PULLED FILE%
Example:
Code:
adb pull /system/recovery.img C:\Android\Local
Thanks for offering to help!
---------- Post added at 05:08 PM ---------- Previous post was at 05:07 PM ----------
Lpuboy87 said:
isnt the new N7 files called Razor instead of grouper ? or is that just what the device was called prior to launch
Click to expand...
Click to collapse
Yep. Razor.
Branch = Razor
codename = Asus flo
Wifi Model: ME371K

followed the first post and it worked....used this for the commands
ADB Commands
---------- Post added at 11:12 PM ---------- Previous post was at 11:10 PM ----------
treoo0_1 said:
Yep. Razor.
Click to expand...
Click to collapse
yeah thought so. :good::highfive:

[Q] Can't boot in any OS anymore (Nexus 7)

Hi guys,
I am new to this Forum and I am German so please understand that my english is not the best.
A few days ago I flashed my Nexus 7 (2012) with the newest Ubuntu Touch Version after having android before. After succesfully flashing the device with the OS it booted with no problem but UbuntuTouch didn't quite come to my expectations, so I decided to switch back to Android. I tried that by simply following the steps that are suggested on the Ubuntu webpage but that did not work out. I tried to just load the Android package to tablet in some other way but now I have the problem, that UbuntuTouch is still installed but when I try to boot it, it gets stucked in a bootloop.
I already tried to "wipe data/factory reset" in the recovery mode but it isn't working. At least bootloader and recovery mode are working fine.
I hope there is some way you can help me solve my problem, if there is anything unclear feel free to ask.
Daniel

I'd suggest asking in the Nexus 7 forum. They know what to do. We probably don't as it's different for every device and the chance that someone comes around who has a Nexus 7 as well is much higher in the Nexus 7 forum. (You know why. ^^)
Please add whether you own the 2012 or 2013 model. Then report your own post by clicking on the orange triangle on the right side of your post and in the text field describe that you want your thread to be moved (ask politely ). Then it'll be in the N7 forum and the people over there will be able to help you. Good luck.

Read this thread:
http://forum.xda-developers.com/showthread.php?t=1907796
Sent from my Nexus 7 using Tapatalk

Update Bricked Phone; Anyway to Retrieve Data?

I have a razr m that I was updating the other day to the newest official firmware. It asked me to update, and then I did. To make sure it completely successfully I plugged it into the charger to give it juice, and it then went to the Fastboot screen with the error : "Failed to hab check for boot: 0x56, Fastboot Reason: Boot Failure." Now I know that ADB was not turned on in the phone. I was curious as to if I would be able to recover my data as I did not have a memory card in it, and I recently took a trip with a lot of pictures. I have used fastboot before, but it was a while ago, and I can't recall ever having a file keep the data partition as it was. If anyone has any advice or ideas I would be so grateful as I really do not want to lose these pictures.

Koneesha said:
I have a razr m that I was updating the other day to the newest official firmware. It asked me to update, and then I did. To make sure it completely successfully I plugged it into the charger to give it juice, and it then went to the Fastboot screen with the error : "Failed to hab check for boot: 0x56, Fastboot Reason: Boot Failure." Now I know that ADB was not turned on in the phone. I was curious as to if I would be able to recover my data as I did not have a memory card in it, and I recently took a trip with a lot of pictures. I have used fastboot before, but it was a while ago, and I can't recall ever having a file keep the data partition as it was. If anyone has any advice or ideas I would be so grateful as I really do not want to lose these pictures.
Click to expand...
Click to collapse
According to this:
http://www.droidforums.net/threads/...-to-flash-cm10-1-on-xt907-please-help.246431/
You may have had a bad download.
I would:
1. Download and install the moto drivers
2. Download and install RSD lite.
3. Download the firmware for the phone.
4. Unzip the firmware and look for the .xml file.
5. Edit the .xml in Notepad and remove these sections:
Code:
<step operation="getvar" var="max-download-size" />
<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="partition" filename="gpt.bin" MD5="5B3FD782141145E4BD1C9270D954AFF1" />
<step operation="flash" partition="tz" filename="tz.mbn" MD5="8514ED883150B7A0579F9431CD872B39" />
<step operation="erase" partition="userdata" />
<step operation="oem" var="fb_mode_clear" />
6. Save the .xml.
7. Connect the phone while in fastboot mode and flash that .xml.
That should get you a clean flash and leave userdata in place.
If anyone would like to verify that would be great. I just know that this is what I edit and remove when I want to keep my data.

Similar thing happened to me. OTA update prevented phone from booting.
The answer was HouseOfMoto and selecting keep data.
http://www.droidrzr.com/index.php/topic/28162-house-of-moto-32/
Good luck.

HT123 said:
Similar thing happened to me. OTA update prevented phone from booting.
The answer was HouseOfMoto and selecting keep data.
http://www.droidrzr.com/index.php/topic/28162-house-of-moto-32/
Good luck.
Click to expand...
Click to collapse
Haha, I completely forgot about house of Moto. So use to manual flashes now.
Sent from my Nexus 7 using XDA Free mobile app

Thanks so much guys. I forgot about all these things. I get into the development, and back out of it so I need to relearn this stuff. But thank you so much I'm going to test these out tonight. House of moto I feel like I even used back in the droid x days. Maybe I'm wrong but I remember the name. Haha

House of Moto made it easy. I restored back to the pre OTA update, took the ota and then redid all the rooting stuff as my BL is unlocked.
It was easier then trying to figure out flash script modifications when i was scrambling to get kids to the right place and keep in touch with people when i had a phone that no longer worked. Plus i had the original stock KK rom already downloaded so it was easy.

Fastboot help after following guide

Following the unlock/root/flash guide, I installed android sdk and was able to get adb to work but when I tested fastboot it just stayed stuck in the bootloader waiting for me to plug in a data cable. Not sure what I'm missing since I installed google drivers from sdk, usb debugging, authorized, enabled oem unlocking. I'm running windows 10 btw.

I had to manually select the driver to get fastboot to work on Win10

truckroot said:
I had to manually select the driver to get fastboot to work on Win10
Click to expand...
Click to collapse
Thanks, I had to install universal windows adb driver and select it.

SysAdmNj said:
Following the unlock/root/flash guide, I installed android sdk and was able to get adb to work but when I tested fastboot it just stayed stuck in the bootloader waiting for me to plug in a data cable. Not sure what I'm missing since I installed google drivers from sdk, usb debugging, authorized, enabled oem unlocking. I'm running windows 10 btw.
Click to expand...
Click to collapse
You're welcome to ask these questions in my guide thread instead of creating a new one. There are quite a few people that answer questions when people have them.

Heisenberg said:
You're welcome to ask these questions in my guide thread instead of creating a new one. There are quite a few people that answer questions when people have them.
Click to expand...
Click to collapse
Sorry, didn't realize people were asking questions in there as well

SysAdmNj said:
Sorry, didn't realize people were asking questions in there as well
Click to expand...
Click to collapse
Yeah there are currently over 200 pages of questions