Problem with Bootloader Linux - Nexus 7 Q&A, Help & Troubleshooting

Hi guys
Got my Nexus today and I am wanting to unlock the boot loader and root. Im running into issues. ADB sees the device as a number. e.g. 127372445 and I can get it to reboot into boot loader but when I try to fast boot oem unlock command in the terminal I get "waiting for device" for ever lol
OS: Ubuntu 12.04
SO yea any help would be grateful as i cant proceed until i get around this?
Also I can not access my Internal Memory on the device through Ubuntu
Thanks

Rueben_ said:
Hi guys
Got my Nexus today and I am wanting to unlock the boot loader and root. Im running into issues. ADB sees the device as a number. e.g. 127372445 and I can get it to reboot into boot loader but when I try to fast boot oem unlock command in the terminal I get "waiting for device" for ever lol
OS: Ubuntu 12.04
SO yea any help would be grateful as i cant proceed until i get around this?
Also I can not access my Internal Memory on the device through Ubuntu
Thanks
Click to expand...
Click to collapse
Are you running fastboot as root? Sometimes fastboot does weird things if it's not running as root

moved thread to QA where it belongs......surprised this was in Dev tbh......

Related

[Q]Bricked ?

This is what happens :
1. When I normally turn my N7 on , it goes throught the google logo and gets stuck on the ROM logo .
2. I can get into the bootloader when the USB is plugged off , but i cant get into recovery it just gets stuck on the google logo .
3.If I plug my USB in while in the bootloader the bootloader gets stucked and i cant move around in it or flash anything , but my PC recognize that an android device is connected . (if i get into the bootloader when the USB is allready connected it gets in the bootloader main screen but i cant move) .
So i cant flash , get into the rom or return to stock .
ANY IDEAS ?? please help me :crying::crying:
Bump
Definitely not bricked since of powers on. Fastboot flash the stock image and you should be good as new.
Sent from my Nexus 7 using Tapatalk 2
Strange, it shouldn't make a difference whether your USB is plugged or not when trying to get to the recovery.
If you get into the fast boot menu or "boot loader main screen" and you press the volume down button a few times you get no response? Sometimes it takes a few seconds for mine to switch to recovery,etc.
Also, what caused your tablet to get stuck in that state?
brGabriel said:
Strange, it shouldn't make a difference whether your USB is plugged or not when trying to get to the recovery.
If you get into the fast boot menu or "boot loader main screen" and you press the volume down button a few times you get no response? Sometimes it takes a few seconds for mine to switch to recovery,etc.
Also, what caused your tablet to get stuck in that state?
Click to expand...
Click to collapse
If I press the volum dowm bottom while on fast boot menu I can move around the menu if the usb is plugged off , but I can only shutdown or restart the fastboot since the start and recovery options just gets stuck on the google/rom logo if it is plugged in I just gets stuck in the menu and I cant even scroll . yea I waited about half an hour on the google logo trying to get to my recovery and nothing happened .
I JUST DONT KNOW WHAT I DID ! I really dont ! I am an experienced flahser and had been so for almost 2 years now ! I just left my N7 on the table and didnt touch it at all for a week and when I tried to turn it on after that I just got that prob . but I did nothing related to flashing or so - it just happened by staying at the table !
any help ?? PLEASE
I CANT RETURN TO STOCK , if i plugg in the usb fastboot gets stuck .
have you tried charging it on the wall charger to make sure the battery has got a full charge, don't know, just throwing out options
Hmmm, well at least you're able to boot the tablet and get to fastboot menu so its not a hard brick. Sounds like a corrupted partition of sorts if you can't get into ROM or recovery. Someone with more expertise might have a possible solution. I wouldn't lose hope yet.
yes , i did charged it to full batt .
i can get into fastboot but not rom or recovery and when i plugg in usb i have no fastboot , doesnt that mean i wont ever be able to flash ?
if i will make a vid of the prob it will help ?
Get to boot loader and do
fastboot flash recovery C:\File path to recovery on computer
Once you have a recovery installed you can push a ROM to your Nexus via adb.
Sent from my Nexus 7
Or you can always use wugfreshs toolkit and click flash back to stock option and check device won't boot, the same thing happened to me awhile ago and the bootloader problem is cause you have the old bootloader the knew 4.13 bootloader fixed that
Sent from my Nexus 7 using Tapatalk HD
i've had good luck with mskip's toolkit in a similar situation
veeman said:
Get to boot loader and do
fastboot flash recovery C:\File path to recovery on computer
Once you have a recovery installed you can push a ROM to your Nexus via adb.
Sent from my Nexus 7
Click to expand...
Click to collapse
xfrancis14 said:
Or you can always use wugfreshs toolkit and click flash back to stock option and check device won't boot, the same thing happened to me awhile ago and the bootloader problem is cause you have the old bootloader the knew 4.13 bootloader fixed that
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Guys , I told you that my bootloader gets stuck when I connect the usb - so how can I possibly flash anything ? please read the whole post
rkiller51 said:
Guys , I told you that my bootloader gets stuck when I connect the usb - so how can I possibly flash anything ? please read the whole post
Click to expand...
Click to collapse
It says you can get to the boot loader with the cable unplugged. So get to the boot loader and then plug in the USB.
Sent from my Nexus 7
Stop... MUFFIN TIME!!!
veeman said:
It says you can get to the boot loader with the cable unplugged. So get to the boot loader and then plug in the USB.
Sent from my Nexus 7
Stop... MUFFIN TIME!!!
Click to expand...
Click to collapse
Are you kidding ? "3.If I plug my USB in while in the bootloader the bootloader gets stucked and i cant move around in it or flash anything , but my PC recognize that an android device is connected ."
I really appreciate any kind of help, but why even write and answer when you didnt even fully read the question ?
rkiller51 said:
Are you kidding ? "3.If I plug my USB in while in the bootloader the bootloader gets stucked and i cant move around in it or flash anything , but my PC recognize that an android device is connected ."
I really appreciate any kind of help, but why even write and answer when you didnt even fully read the question ?
Click to expand...
Click to collapse
Lol just calm down man we're all just trying to help you!
Now, you need to get your N7 into the bootloader, it does not matter if you can't navigate the bootloader on your N7. Once in the bootloader, connect the N7 to your computer with the USB cable.
Once you're connected, make sure you've downloaded the Android SDK and open a command prompt. Navigate your command prompt (make sure you ran that command prompt as administrator) to the "platform-tools" directory.
Once in the platform-tools directory run the following command without quotes:
"fastboot devices"
It should return the serial number for your device, indicating that fastboot sees your N7 and can work with it.
After that type
"fastboot flash recovery *.img"
You'll need to head to clockworkmod.com to download the N7 recovery image. Place the downloaded image in the platform-tools directory and replace "*.img" with the filename of the recovery image you downloaded.
That's it! Unplug your N7 and go into recovery, and sideload whatever ROM you want!
Let us know how it goes!
PS: If fastboot devices shows nothing, we have a bigger problem...
TMan459 said:
Lol just calm down man we're all just trying to help you!
Now, you need to get your N7 into the bootloader, it does not matter if you can't navigate the bootloader on your N7. Once in the bootloader, connect the N7 to your computer with the USB cable.
Once you're connected, make sure you've downloaded the Android SDK and open a command prompt. Navigate your command prompt (make sure you ran that command prompt as administrator) to the "platform-tools" directory.
Once in the platform-tools directory run the following command without quotes:
"fastboot devices"
It should return the serial number for your device, indicating that fastboot sees your N7 and can work with it.
After that type
"fastboot flash recovery *.img"
You'll need to head to clockworkmod.com to download the N7 recovery image. Place the downloaded image in the platform-tools directory and replace "*.img" with the filename of the recovery image you downloaded.
That's it! Unplug your N7 and go into recovery, and sideload whatever ROM you want!
Let us know how it goes!
PS: If fastboot devices shows nothing, we have a bigger problem...
Click to expand...
Click to collapse
Its hard to be calm then you new N7 is dying :/
somthing like this ? (pic attached)
If i did everything like you said it means i do have the bigger prob help me!
OK. Next thing is to ensure your N7 is properly detected in Windows.
Just head to the device manager. You should see Original Android Interface or something along those lines.
Report back with a screenshot, those are very helpful!
TMan459 said:
OK. Next thing is to ensure your N7 is properly detected in Windows.
Just head to the device manager. You should see Original Android Interface or something along those lines.
Report back with a screenshot, those are very helpful!
Click to expand...
Click to collapse
Here you go (attached) ! you have everything you need mate ?
I really appreciate the help ! :good::good:
I had similar issues and was able to get back to stock using WugFresh's Nexus Root Toolkit. Highly recommended!
From the same command Window, in the same platform - tools directory, does adb devices show your device?
I'm not the lowest of the low, but I am the slowest of the slow.

Nexus 7 4.2.1 update crashed

Hi techies,
Last night i have tried to update the latest update of android 4.2.1 (11mb of size) through update manager.
It hang for some time and crashed.. now no display on my nexus 7.
anybody knows how i can recover/flash it... of reset it... pls help...:crying: :crying:
i have tried 30 sec hold the start button but it doesn't help... any other ideas or anyway to HARD RESET... #HELP
remin13 said:
Hi techies,
Last night i have tried to update the latest update of android 4.2.1 (11mb of size) through update manager.
It hang for some time and crashed.. now no display on my nexus 7.
anybody knows how i can recover/flash it... of reset it... pls help...:crying: :crying:
i have tried 30 sec hold the start button but it doesn't help... any other ideas or anyway to HARD RESET... #HELP
Click to expand...
Click to collapse
This is to reset your nexus to complete stock like the day you bought it, so yes you will loose all data!
First follow the YouTube guide to install android sdk, adb, fastboot on computer.
https://www.youtube.com/watch?v=oaNM...e_gdata_player
Then follow this guide to reset your nexus.
Note the bootloader needs to be unlocked which once adb is set up as in guide below the first comand needs to be
Fastboot oem unlock
The guide doesn't mention this.
http://forums.androidcentral.com/nex...e-restore.html
When you have finished
Fastboot oem lock. Will lock your bootloader again.
nexus 7 crashed
Thanks for your update...
I hav already tried this but it shows my nexus 7 does not detect on my computer.
already tried on my Ubuntu and WinXP, all shows the bellow message...
fastboot oem unlock
< waiting for device >
Is any drivers should i install to solve this???
remin13 said:
Thanks for your update...
I hav already tried this but it shows my nexus 7 does not detect on my computer.
already tried on my Ubuntu and WinXP, all shows the bellow message...
fastboot oem unlock
< waiting for device >
Is any drivers should i install to solve this???
Click to expand...
Click to collapse
Did you follow the YouTube video fully? I had to add some paths to windows too.
You can leave the "fastboot oem unlock" command until just before you flash the operating system back on, if you forget and try to flash the operating system it doesn't matter it will just tell you the bootloader needs to be unlocked, this is the part where a small amount of poo came out of me because I had followed the guide past where you use all the erase commands and then though **** how do I unlock my bootloader now everything is wiped! Turns out the fastboot command still works.
Nexus 7 Tapatalk 2
WasherUK said:
Did you follow the YouTube video fully? I had to add some paths to windows too.
You can leave the "fastboot oem unlock" command until just before you flash the operating system back on, if you forget and try to flash the operating system it doesn't matter it will just tell you the bootloader needs to be unlocked, this is the part where a small amount of poo came out of me because I had followed the guide past where you use all the erase commands and then though **** how do I unlock my bootloader now everything is wiped! Turns out the fastboot command still works.
Nexus 7 Tapatalk 2
Click to expand...
Click to collapse
No way... i think its not detect on my Windows nor on Ubuntu. Better i think, gave it to authorized service centers.
remin13 said:
No way... i think its not detect on my Windows nor on Ubuntu. Better i think, gave it to authorized service centers.
Click to expand...
Click to collapse
Oh dear
Nexus 7 Tapatalk 2

[Q] Stuck at Google Logo - Cant Access Recovery - Cant Turn On USB Debugging

Hello all,
I poked around and saw some similar issues, but nothing quite like what I am facing and was hoping you all could help me.
I woke up this morning to find my nexus 7 2013 32 gig wifi only on the "Google" logo loading screen. The tablet will not boot up into android.
I read up a little bit and found that I can factory reset using adb and fastboot...but here is my problem...USB Debugging is not enabled on my tablet, and I cannot access android to turn it on. Therefore, adb is not recognizing my device. If I try to enter recovery from the bootloader screen I get the same "Google" logo.
My bootloader is locked.
Really hoping someone who knows more than I about how these things work can help.
Thanks in advance for any assistance you can provide.
This is the 2012 forum you need the Nexus 7 2013 forum
Sent from my C5303 using xda app-developers app
woebtz said:
Hello all,
I poked around and saw some similar issues, but nothing quite like what I am facing and was hoping you all could help me.
I woke up this morning to find my nexus 7 2013 32 gig wifi only on the "Google" logo loading screen. The tablet will not boot up into android.
I read up a little bit and found that I can factory reset using adb and fastboot...but here is my problem...USB Debugging is not enabled on my tablet, and I cannot access android to turn it on. Therefore, adb is not recognizing my device. If I try to enter recovery from the bootloader screen I get the same "Google" logo.
My bootloader is locked.
Really hoping someone who knows more than I about how these things work can help.
Thanks in advance for any assistance you can provide.
Click to expand...
Click to collapse
You will have to do it with fastboot commands, since adb isn't available when you can't get into recovery or Android.OS. Send the fastboot oem unlock command to unlock your bootloader, and follow the sticky fastboot thread directions.
exglynco said:
You will have to do it with fastboot commands, since adb isn't available when you can't get into recovery or Android.OS. Send the fastboot oem unlock command to unlock your bootloader, and follow the sticky fastboot thread directions.
Click to expand...
Click to collapse
Thanks. I appreciate the insight. However, when I run that command it gets to erasing the user data and then just hangs. It never moves on. I assumed this was because debugging is turned off, but I could definitely be wrong.
Any ideas on how to get past this step?
woebtz said:
Thanks. I appreciate the insight. However, when I run that command it gets to erasing the user data and then just hangs. It never moves on. I assumed this was because debugging is turned off, but I could definitely be wrong.
Any ideas on how to get past this step?
Click to expand...
Click to collapse
Its not because of usb debugging but its also not good. It may be corrupted nand (internal memory unwritable). Unexplained failure to boot followed by fastboot commands failing or hanging are typical hallmarks of this. Do you still have a warranty?
Sent from my C5303 using xda app-developers app
Unfortunately, Captain Sweatpants is probably correct. I'm also guessing corrupted NAND or a corrupted bootloader.
Sent from my Nexus 7 using Tapatalk

2012 N7 stuck in bootloop/bricked. Unlocked but can't recover/flash images

The title says most of my situation. I've had this since 2012 and some time early last year it just up and stopped booting into android. I have no idea what happened because my girlfriend was using it at the time and she swears she didn't change anything.
Anyways, the bootloader is locked and I have tried to go to recovery and factory reset with no luck. Wiped cache and did nothing as well. I am seeing that windows 7 is sort of recognizing the device. It shows up under device manager as "Android Bootloader Interface"
I've updated the USB drivers and installed ADB as well. When checking the command prompt for ADB Devices, it shows nothing.
I installed Wugs toolkit and it won't even find the nexus either. There has to be SOMETHING that can be done in this situation right?
:EDIT: I was able to unlock it using fastboot but I still can't get it to be found by anything else.
I can get it recognized using the fastboot command prompt, but I can't execute any commands in it. Everything like "fastboot flash boot boot.img" just returns a FAILED message with either invalid argument or no such address or device.
What I am trying to do is just recover it and start using it again. Of course I want to put Android 5.0 on it, but I would be okay with anything as long as it boots, really.
:EDIT: I was actually able to get it to work. I have no idea what specifically had fixed it, but I uninstalled and reinstalled the drivers a few times and ran fastboot and was able to wipe it and install Android 5.0! It was running great!

[Q] Permanent problem with Unlocking Bootloader Nexus S

Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!
alpheus said:
Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!
Click to expand...
Click to collapse
It looks like your device is not recognized in Fastboot mode...
Have you turned on USB Debugging while connecting PC and Allow in Device when Prompt some message ..
Go to fastboot mode and write this command... fastboot devices
If it will give you a message like this
List of devices
1235456785164
Then your devices is successfully recognized...:good:
It is not recognized by adb devices, but:
fastboot devices - gives the following output:
ERROR: could not get pipe properties
3331E6EBCA6000EC fastboot
Click to expand...
Click to collapse
fastboot oem unlock - gives the following:
ERROR: could not get pipe properties
...
FAILED (remote: Erase Fail)
finished. total time: 4.753s
Click to expand...
Click to collapse
alpheus said:
It is not recognized by adb devices, but:
fastboot devices - gives the following output:
fastboot oem unlock - gives the following:
Click to expand...
Click to collapse
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
Thanks, I tried 3 different cables on 3 different operating systems, with the same problem unlocking the fastboot. When I send fastboot oem unlock the device opens a prompt with Yes or No choice, but after choosing Yes, it stays Locked
Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too
demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
demkantor said:
Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too
Click to expand...
Click to collapse
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!
alpheus said:
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!
Click to expand...
Click to collapse
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..
UPDATE (resolved)
Here is an update. Hope this would help others with similar issue, as I've read many threads and folks complaining that they weren't able to unlock fastboot and further root their Nexus S, and who can't boot the phone, which stacked with Google Logo (soft loop). This was the case with my device and finally I got it resolved. I've read some guy tried to hit the phone and after that he was able to boot phone normally. It related to some hardware electrical circle issue. Anyways, I tried to hit my phone by placing it under the direct sun in balcony for some time until the phone got hot and then power it on. And ooops, my phone started booting passed by that Google Logo which was the good sign. Once the phone booted up, I went ahead and activated USB debugging and restarted the phone into the Fastboot mode. while the phone was still hot and in Fastboot mode I run "fastboot oem unlock" and hey, fastboot is Unlocked! Again, this was done while the phone was hot, any previous attempts (read above) weren't successful. From that point, I went ahead and rooted my Nexus S by Nexus Root Toolkit, available on wugfresh.com/nrt, without a slightest problem. Now my phone is fully rooted, bootable and working fine. I thank all who replied to my thread and tried to help and hope this info would help someone with the similar issue.
Rushabh22 said:
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..
Click to expand...
Click to collapse
Thank you for your help and suggestions.
Q Mobile X 32
bootloader oem unlock problem
plz help
Q-mobile said:
Q Mobile X 32
bootloader oem unlock problem
plz help
Click to expand...
Click to collapse
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923
Setting.Out said:
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923
Click to expand...
Click to collapse
can you help me in rooting Qmobile x32
Q-mobile said:
can you help me in rooting Qmobile x32
Click to expand...
Click to collapse
That thread didn't help?
Here's what the guide says...

Categories

Resources