Database Users

[Q] Nexus 7 Bootloop

Hi! I have Nexus 7 and I've used it for 4 months, it's on warranty. It started to lag couple of days and I rebooted it sometimes, but on the one reboot it didn't start Android and stucked on X logo, after another reboot it started a bootloop from X logo to Google logo on and on. After another reboot it stucks only on Google screen. I've tried to wipe data and cache partition, but it also stucks. I also tried Nexus 7 Toolkit, but it gets an error on unlock bootloader. I also tried to do it via Windows' cmd.exe with fastboot oem unlock, the same problem. I can't find any working method. Please, help.

You can use the toolkit to revert back to set stock rom. Download the stock .img from the toolkit and perform the flash. Make sure you boot to the bootloader to do this.
Entering the command fastboot oem unlock on a unlocked device will not do anything if the bootloader is already unlocked.
Sent from my Nexus 4 using Tapatalk 2

scream4cheese said:
You can use the toolkit to revert back to set stock rom. Download the stock .img from the toolkit and perform the flash. Make sure you boot to the bootloader to do this.
Entering the command fastboot oem unlock on a unlocked device will not do anything if the bootloader is already unlocked.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I'm having the EXACT same problem. Also had my N7 for about 4 mos. I'm going to try the above suggestion also. Please post your results and I'll do the same.
---------- Post added at 10:46 PM ---------- Previous post was at 10:42 PM ----------
scream4cheese said:
You can use the toolkit to revert back to set stock rom. Download the stock .img from the toolkit and perform the flash. Make sure you boot to the bootloader to do this.
Entering the command fastboot oem unlock on a unlocked device will not do anything if the bootloader is already unlocked.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
If I'm already unlocked (not rooted), what steps should I follow? I'm new to all this and, although I've rooted a phone once before, I barely remember what I did back then. I don't even know what you mean by "perform the flash." Can you provide some more specific directions? I have the toolkit downloaded. Thanks!
---------- Post added at 11:34 PM ---------- Previous post was at 10:46 PM ----------
Ok - figuring this out slowly. Can someone tell me where in my folders I can find my bootloader file?

ctychick said:
I'm having the EXACT same problem. Also had my N7 for about 4 mos. I'm going to try the above suggestion also. Please post your results and I'll do the same.
---------- Post added at 10:46 PM ---------- Previous post was at 10:42 PM ----------
If I'm already unlocked (not rooted), what steps should I follow? I'm new to all this and, although I've rooted a phone once before, I barely remember what I did back then. I don't even know what you mean by "perform the flash." Can you provide some more specific directions? I have the toolkit downloaded. Thanks!
---------- Post added at 11:34 PM ---------- Previous post was at 10:46 PM ----------
Ok - figuring this out slowly. Can someone tell me where in my folders I can find my bootloader file?
Click to expand...
Click to collapse
You can't find the bootloader file. It's embedded within the system. Unless you have the flashable zip then you can use that. Why do you need it anyways?

ten char .

Bad block on nand flash
Sent from my ST18i using xda app-developers app

Hi mate*
Dunno if you got things sorted but I had the same problem last week. I'd let the unit run flat and stay flat for a coupla days and bootloop is the price I paid. So, I call Asus who inform me that it's under warranty and to send it in for repair. Fair dos to them that's good service but I don't wanna be without my Nexus for 2 weeks so I have another play with it having previously had no joy resetting it using power and vol up/down etc.*
I'd managed to get some charge into it by waiting for the bootloop to turn it on and then manually turning it off. Not sure how quickly yours restarts but I had lockscreen for 10 seconds or so before restarting the cycle. That said it wasn't long enough to reset to factory settings but it was long enough to turn off wifi. Dunno why I tried this, sheer desperation probably but after a restart with wifi off and a full battery I was able to access my stuff and back it up to pc.*
I then was able to perform a factory reset and set the device up again, including wifi and apps. Since then it's been good as gold (but I won't let it drop below 20% charge!) but as there's only 4 months of warranty left Asus are gonna let me send it in to have a new motherboard anyway - might as well as its been wiped anyhow. The last thing I want if for it to [email protected]#k up a week after the warranty's ran out.*
I hope this helps you or other searching for a fix bud, let us know *

Lolpoppa said:
Hi mate*
Dunno if you got things sorted but I had the same problem last week. I'd let the unit run flat and stay flat for a coupla days and bootloop is the price I paid. So, I call Asus who inform me that it's under warranty and to send it in for repair. Fair dos to them that's good service but I don't wanna be without my Nexus for 2 weeks so I have another play with it having previously had no joy resetting it using power and vol up/down etc.*
I'd managed to get some charge into it by waiting for the bootloop to turn it on and then manually turning it off. Not sure how quickly yours restarts but I had lockscreen for 10 seconds or so before restarting the cycle. That said it wasn't long enough to reset to factory settings but it was long enough to turn off wifi. Dunno why I tried this, sheer desperation probably but after a restart with wifi off and a full battery I was able to access my stuff and back it up to pc.*
I then was able to perform a factory reset and set the device up again, including wifi and apps. Since then it's been good as gold (but I won't let it drop below 20% charge!) but as there's only 4 months of warranty left Asus are gonna let me send it in to have a new motherboard anyway - might as well as its been wiped anyhow. The last thing I want if for it to [email protected]#k up a week after the warranty's ran out.*
I hope this helps you or other searching for a fix bud, let us know *
Click to expand...
Click to collapse
I tries this but it doesnt seem to work for me, i had the same issue as you and now it seems as though it is bricked :/ i tried doing the steps you mentioned but it didnt work for me. i get to the home screen for about 10 secs till it restarts. i want to save my music/pictures and i dont know what to do (i never enabled developer options either) any ideas?

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] GS4 f'ed up build.prop lost root. Begging for help!

Please help!!! Ok, let me start by saying that I've successfully rooted, soft bricked, and unbricked my previous S2 & Note 2. I just got an S4 about a month ago and decided to root today. While I was setting it up a month ago I updated to mf3 and had completely forgotten.
I did the new root via terminal and was successful. Installed SU just fine. I gave root to xplorer and switched out my build.prop for the sprint sg4 to install google wallet (the one I could actually use nfc with). Installed fine, then got an error about not having sufficient permission inside gw. I rebooted and somehow su lost binary. I've tried everything I could look up. I can't uninstall su without root, and I can't open it without the binaries. I can't replace the build.prop, or edit it. I can pull via adb but can't push. Can't do it through adb shell either. Can't use odin (cuz mf3), can't use mobile odin, can't use goo either. I'm lost.
It hasn't caused any serious problems but I'd like to have my at&t build.prop back. (Fyi, I did back it up before I did it. So I have it, I just can't replace it.)
Can this be fixed? Am I f'ed? Do I have to live with it til someone gets around the bootloader? Or do I have to take it back to bestbuy to replace it? (And if I do, Will they replace it?)
Update: BestBuy will not replace it.

Go to a best buy that has the Samsung experience. They won't replace the phone but they can flash the mf3 firmware and get you back to like new again. You'll have to sweet talk them.

You can also try visiting an att store to have them flash mf3.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

Thanks for the posts guys. Really appreciate it! I ended up trying to do an emergency flash via Kies. After a couple of dozen times of it failing to download (too slow) my phone ended up with the yellow triangle and said the firmware upgrade failed and to connect it to Kies. Luckily that showed that I wasn't rooted so I took it to a Samsung experience kiosk and they had me up and running in 10 minutes. Needless to say I'm not rooting again til there's a recovery for MF3!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Jd1639, the girl I spoke to yesterday wouldn't reflash it for me. She could tell it wasn't stock because of the 4G signal.
I got lucky today with Kies failing! The hubs would've killed me!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

silrosriv said:
Jd1639, the girl I spoke to yesterday wouldn't reflash it for me. She could tell it wasn't stock because of the 4G signal.
I got lucky today with Kies failing! The hubs would've killed me!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I had the exact same experience with Best buy. The lady, as friendly as she was, was unhelpful in my situation. She kept saying they do not want to flash something that has been altered in any way just in case it gets bricked... it is to prevent liability on their part (which I can kind of understand). I even told her I'd be glad to sign a waiver to assume full liability if something goes wrong. She didn't go for it... Unfortunately, I'm stuck at the moment, I'm searching out ways to restore my build.prop from either adb sideload via the stock recovery or through ODIN somehow... There was a thread discussing a fix for the yellow triangle that required ODIN to flash some files (5 or so)... So, I was thinking if I can get the same type of thing setup for build.prop, I'd be in good shape... I just have 0 experience with doing this stuff, so I'm still reading/learning how it all works.

Dusty, I think if you're on MF3 nothing is going to work. You can try an emergency firmware flash through Kies. If you're at the yellow triangle and it's telling you to connect it to Kies then look at the top and see if it says that you're running Samsung official with write block enabled. If it does then take it back to the Samsung experience kiosk and tell them your PC froze during an update and that's what broke your phone.
Hope it helps. That's what worked for me.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

dustyhughes said:
I had the exact same experience with Best buy. The lady, as friendly as she was, was unhelpful in my situation. She kept saying they do not want to flash something that has been altered in any way just in case it gets bricked... it is to prevent liability on their part (which I can kind of understand). I even told her I'd be glad to sign a waiver to assume full liability if something goes wrong. She didn't go for it... Unfortunately, I'm stuck at the moment, I'm searching out ways to restore my build.prop from either adb sideload via the stock recovery or through ODIN somehow... There was a thread discussing a fix for the yellow triangle that required ODIN to flash some files (5 or so)... So, I was thinking if I can get the same type of thing setup for build.prop, I'd be in good shape... I just have 0 experience with doing this stuff, so I'm still reading/learning how it all works.
Click to expand...
Click to collapse
Wait so you lost root, too?
What exactly is your problem?
Because you can replace your build.prop with adb easily.

Exel said:
Wait so you lost root, too?
What exactly is your problem?
Because you can replace your build.prop with adb easily.
Click to expand...
Click to collapse
Sorry, I was a bit vague... I modded the build.prop to enable lockscreen rotation, which was basically adding one line to the end of the file. I realize how dumb this was, it was late and I wasn't thinking clearly :silly:....
Well, since I modded the build.prop, I cannot boot to the OS, in fact after the Samsung boot logo it doesn't even make it to the AT&T boot screen. It remains black after Samsung boot logo. The LED does turn blue after a bit, and if I have the phone plugged into the laptop the USB drivers will install, but I never make it to the OS no matter how long I leave the phone.
So I'm stuck not being able to boot to the OS. I can get to stock recovery and have the ADB sideload option, but it seems to be different that full blown ADB (from what I've gathered).
My biggest problem now is trying to take a copy of the clean build.prop and replace the one that is messed up in /system/
I can't determine exactly what I need (update script with build.prop etc) to load over sideload to get it to work.
---------- Post added at 12:07 PM ---------- Previous post was at 12:03 PM ----------
silrosriv said:
Dusty, I think if you're on MF3 nothing is going to work. You can try an emergency firmware flash through Kies. If you're at the yellow triangle and it's telling you to connect it to Kies then look at the top and see if it says that you're running Samsung official with write block enabled. If it does then take it back to the Samsung experience kiosk and tell them your PC froze during an update and that's what broke your phone.
Hope it helps. That's what worked for me.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I can get my phone to the yellow triangle, but mine actually says custom in the top left instead of official... Because of that, I couldn't convince the lady at the kiosk to flash my phone. Granted, it wasn't on the yellow triangle yesterday when i took it. I did convince her to plug it in while I had it in download mode. It recognized my phone, but I couldn't get her to proceed with flashing it.

dustyhughes said:
Sorry, I was a bit vague... I modded the build.prop to enable lockscreen rotation, which was basically adding one line to the end of the file. I realize how dumb this was, it was late and I wasn't thinking clearly :silly:....
Well, since I modded the build.prop, I cannot boot to the OS, in fact after the Samsung boot logo it doesn't even make it to the AT&T boot screen. It remains black after Samsung boot logo. The LED does turn blue after a bit, and if I have the phone plugged into the laptop the USB drivers will install, but I never make it to the OS no matter how long I leave the phone.
So I'm stuck not being able to boot to the OS. I can get to stock recovery and have the ADB sideload option, but it seems to be different that full blown ADB (from what I've gathered).
My biggest problem now is trying to take a copy of the clean build.prop and replace the one that is messed up in /system/
I can't determine exactly what I need (update script with build.prop etc) to load over sideload to get it to work.
---------- Post added at 12:07 PM ---------- Previous post was at 12:03 PM ----------
I can get my phone to the yellow triangle, but mine actually says custom in the top left instead of official... Because of that, I couldn't convince the lady at the kiosk to flash my phone. Granted, it wasn't on the yellow triangle yesterday when i took it. I did convince her to plug it in while I had it in download mode. It recognized my phone, but I couldn't get her to proceed with flashing it.
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?t=1236732
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

dustyhughes said:
Sorry, I was a bit vague... I modded the build.prop to enable lockscreen rotation, which was basically adding one line to the end of the file. I realize how dumb this was, it was late and I wasn't thinking clearly :silly:....
Well, since I modded the build.prop, I cannot boot to the OS, in fact after the Samsung boot logo it doesn't even make it to the AT&T boot screen. It remains black after Samsung boot logo. The LED does turn blue after a bit, and if I have the phone plugged into the laptop the USB drivers will install, but I never make it to the OS no matter how long I leave the phone.
So I'm stuck not being able to boot to the OS. I can get to stock recovery and have the ADB sideload option, but it seems to be different that full blown ADB (from what I've gathered).
My biggest problem now is trying to take a copy of the clean build.prop and replace the one that is messed up in /system/
I can't determine exactly what I need (update script with build.prop etc) to load over sideload to get it to work.
---------- Post added at 12:07 PM ---------- Previous post was at 12:03 PM ----------
I can get my phone to the yellow triangle, but mine actually says custom in the top left instead of official... Because of that, I couldn't convince the lady at the kiosk to flash my phone. Granted, it wasn't on the yellow triangle yesterday when i took it. I did convince her to plug it in while I had it in download mode. It recognized my phone, but I couldn't get her to proceed with flashing it.
Click to expand...
Click to collapse
Then I would try Kies. Leave your phone unplugged, then go to tools, upgrade and initialization, in all caps enter your device (mine is SGH-I337), click ok, enter your serial number, click ok, then plug in your phone in Odin mode. If that doesn't work you may have to wait for someone to figure out MF3 with Odin.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

silrosriv said:
Try this
http://forum.xda-developers.com/showthread.php?t=1236732
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Thanks much, I really appreciate the help. I have tried to push/pull files from my device without luck. The only option i have for ADB on my phone at the moment is the stock recovery "install over adb". It looks like the only commands I can run are "adb devices" (which lists my phone as "sideload") and "adb sideload"... I've used the sideload command to try and flash an OTA mf3 cfg file I found in another thread. the file was successfully pushed to the phone, and the update began but failed with an erro code of 7 (which is supposed to mean wrong device or something).
I was thinking if I could encapsulate the build.prop with a script into one of these update files to be pushed over sideload, I may be able to get my build.prop replaced and my phone running again. But i'm not sure how to build that file, or whether or not it would even have access to replace a file in the "/system" folder.
I'm still searching, and will update when/if I find an answer.

dustyhughes said:
Thanks much, I really appreciate the help. I have tried to push/pull files from my device without luck. The only option i have for ADB on my phone at the moment is the stock recovery "install over adb". It looks like the only commands I can run are "adb devices" (which lists my phone as "sideload") and "adb sideload"... I've used the sideload command to try and flash an OTA mf3 cfg file I found in another thread. the file was successfully pushed to the phone, and the update began but failed with an erro code of 7 (which is supposed to mean wrong device or something).
I was thinking if I could encapsulate the build.prop with a script into one of these update files to be pushed over sideload, I may be able to get my build.prop replaced and my phone running again. But i'm not sure how to build that file, or whether or not it would even have access to replace a file in the "/system" folder.
I'm still searching, and will update when/if I find an answer.
Click to expand...
Click to collapse
Not sure, correct me if I'm wrong, but I think you're in recovery (blue DOS looking menu list). Power button & volume up? That is how you get to sideload. To do regular adb you need to run an app for terminal emulator while the phone is actually on.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

silrosriv said:
Then I would try Kies. Leave your phone unplugged, then go to tools, upgrade and initialization, in all caps enter your device (mine is SGH-I337), click ok, enter your serial number, click ok, then plug in your phone in Odin mode. If that doesn't work you may have to wait for someone to figure out MF3 with Odin.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I'm afraid you are right... If MF3 were available through Kies (since I was unfortunate enough to get a phone with mf3) i'd be ok... but i think i may just be waiting a while.... My wife has the same phone, so if i could image hers, I could go that route... but again, out of my area of expertise.
---------- Post added at 12:29 PM ---------- Previous post was at 12:28 PM ----------
silrosriv said:
Not sure, correct me if I'm wrong, but I think you're in recovery (blue DOS looking menu list). Power button & volume up? That is how you get to sideload. To do regular adb you need to run an app for terminal emulator while the phone is actually on.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
you are correct, I cannot get to the phone's os for full blown adb...

dustyhughes said:
I'm afraid you are right... If MF3 were available through Kies (since I was unfortunate enough to get a phone with mf3) i'd be ok... but i think i may just be waiting a while.... My wife has the same phone, so if i could image hers, I could go that route... but again, out of my area of expertise.
---------- Post added at 12:29 PM ---------- Previous post was at 12:28 PM ----------
you are correct, I cannot get to the phone's os for full blown adb...
Click to expand...
Click to collapse
I kind of want to try for you..
You have TeamViewer? It's a remote access app for your PC so I can run some commands on your PC (adb)

dustyhughes said:
I'm afraid you are right... If MF3 were available through Kies (since I was unfortunate enough to get a phone with mf3) i'd be ok... but i think i may just be waiting a while.... My wife has the same phone, so if i could image hers, I could go that route... but again, out of my area of expertise.
---------- Post added at 12:29 PM ---------- Previous post was at 12:28 PM ----------
you are correct, I cannot get to the phone's os for full blown adb...
Click to expand...
Click to collapse
Have you tried to boot in safe mode? I don't think it will let you change anything though.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Exel said:
I kind of want to try for you..
You have TeamViewer? It's a remote access app for your PC so I can run some commands on your PC (adb)
Click to expand...
Click to collapse
I do not have teamviewer currently installed. I've been using LogMeIn since it was completely free and kind of just stuck with it. I've also used join.me for the one off remote assistance situations.
i would be willing to allow you to try. I currently have ADB installed and have updated the windows path environment to use ADB universally, so there's no need to be in any certain directory.
I would be willing to allow you to attempt something... I'm almost desperate at this point
Sorry for the delay, I'm still at work, and something came up.

You guys can also try Join.me totally free.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

silrosriv said:
Have you tried to boot in safe mode? I don't think it will let you change anything though.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
i'm not sure what you mean about safe mode, is there a hardware key combination required for it?
---------- Post added at 01:03 PM ---------- Previous post was at 01:02 PM ----------
silrosriv said:
You guys can also try Join.me totally free.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Yes, I love Join.me... I liked it more before it started "suggesting" you to buy it all the time though

dustyhughes said:
i'm not sure what you mean about safe mode, is there a hardware key combination required for it?
---------- Post added at 01:03 PM ---------- Previous post was at 01:02 PM ----------
Yes, I love Join.me... I liked it more before it started "suggesting" you to buy it all the time though
Click to expand...
Click to collapse
Feel free to PM me the info and whatnot and I'll see what I can do for you.

[Q]

Hey there. I have a rooted and unlocked nexus 7 WiFi (2012) and want to put it back to stock. But when in bootloader I get unknown on windows. And when I try and unroot on Ubuntu it just keeps saying waiting for devise. Is there any way of fixing this. I am using android 4.3.

Wipe your windows drivers and start fresh.
After you uninstall the driver's, use this guide..
http://forum.xda-developers.com/showthread.php?t=1907796

Will do. I'll let you know how it goes. But I was also getting the same while using Ubuntu on a different machine.

Unfortunately I know nothing of Ubuntu. Maybe if you have trouble you should ask in its thread?

No dice. Windows keeps saying that the device has malfunctioned when I do the bootloader reboot.

Well, its either a driver issue still....or Ubuntu issue....or hardware issue on the device.
I'd ask in the Ubuntu thread.
---------- Post added at 07:59 PM ---------- Previous post was at 07:59 PM ----------
Here...
http://forum.xda-developers.com/showthread.php?t=1957561

Cheers fot the help.

A quick question is there a way of installing a bootloader from storage on the nexus? The Ubuntu thread was a bust.

Problems unlocking bootloader

Hello all, hope you're all doing well. I've come across some problems when trying to unlock the bootloader on the Nexus 6P. Whenever I execute
Code:
fastboot flashing unlock
in the bootloader, my command prompt stays at
Code:
< waiting for device >
and never seems to progress after that. I have also tried
Code:
fastboot oem unlock
, but it still stays on
Code:
< waiting for device >
. I have already done some research on this problem and I have tried to troubleshoot by checking if I have the latest SDK update, and I do, but still no luck. My main purpose of doing this is to install the official 7.1.1 factory image. How can I fix this problem?

Does it say anything in cp when you type devices? Is there a serial number that returns
---------- Post added at 08:22 PM ---------- Previous post was at 08:20 PM ----------
It's either driver issue or maybe you don't have usb debugging checked. Cause it can't see your device

I know that in the beginner's guide, we are told not to use minimal adb. Unlocking bootloader is the first step. Even though my device was recognised, bootloader just simply refused to unlock. I had latest SDK tools installed and everything. So, I resorted to minimal adb and bootloader unlocked without any fuss. For everything else that followed, I used normal fast boot.
You can try this at your own risk. It worked for me. Just sharing.
Edit: if you haven't done anything to your phone, can't you just check for update and install 7.1.1 the normal way, since this is all you want?

Yeah and also if what your using is not up to date (previous adb) you can have problems with that just like that guy up there said

Thanks for reaching out and taking time to try and help out everyone.
dontbeweakvato said:
Does it say anything in cp when you type devices? Is there a serial number that returns
---------- Post added at 08:22 PM ---------- Previous post was at 08:20 PM ----------
It's either driver issue or maybe you don't have usb debugging checked. Cause it can't see your device
Click to expand...
Click to collapse
I've forgot to mention that when I run
Code:
adb devices
when the operating system is up, ADB recognizes it. However, when I'm in bootloader, like you mentioned, it doesn't see it. I've tried switching off and on the "OEM unlocking" and "USB debugging" in the "Developer options", however the problem persists.
tropical cactus said:
I know that in the beginner's guide, we are told not to use minimal adb. Unlocking bootloader is the first step. Even though my device was recognised, bootloader just simply refused to unlock. I had latest SDK tools installed and everything. So, I resorted to minimal adb and bootloader unlocked without any fuss. For everything else that followed, I used normal fast boot.
You can try this at your own risk. It worked for me. Just sharing.
Edit: if you haven't done anything to your phone, can't you just check for update and install 7.1.1 the normal way, since this is all you want?
Click to expand...
Click to collapse
Doubt minimal adb will fix this, but worth a try. I'll also try running ADB on a different computer if that might help. Also, the reason why I want the official 7.1.1 release is because my device is currently running the developer's version. In addition I tried checking for update; no use.
dontbeweakvato said:
Yeah and also if what your using is not up to date (previous adb) you can have problems with that just like that guy up there said
Click to expand...
Click to collapse
Yup. I did mention that my SDK tools are the latest release in my first post.
Edit: Never mind everyone I've found the solution! For some reason the device didn't have the Google USB drivers installed when the device is in the bootloader screen. After days of researching and trial and errors, here is the article that helped me:
http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/3/
Note: If you're experiencing this similar problem with the "< waiting for device >" message in the command line, you must acquire the Google USB driver .zip file.
Thanks to everyone that offered help!

Yep driver issues. Classic.