Related
okay, so Im new here, literally just traded my thrill for the atrix about an hour ago. Now, i see that there are people being bricked by trying to unlock their bootloader after the OTA update, it was already updated when i got it. So, my question is... what the hell can i do to unlock the bootloader and NOT brick my phone?? I would really like to unlock it. Also, if i do not unlock my bootloader, can i still install CWM and flash ROMs??
If you have an AT&T Atrix, use this (I received the phone with stock 2.3.4, 4.5.91)- http://forum.xda-developers.com/showthread.php?t=1182871 . Super easy and worked great for me.
If not, read the Noob guide on top of the General Forum.
You need to unlock the bootloader first before you can do anything.
Sent from my MB860 using XDA App
HustlinDaily said:
If you have an AT&T Atrix, use this (I received the phone with stock 2.3.4, 4.5.91)- http://forum.xda-developers.com/showthread.php?t=1182871 . Super easy and worked great for me.
If not, read the Noob guide on top of the General Forum.
Click to expand...
Click to collapse
i see a lot of people saying they are having issues but fixing it with the android recovery... how do i get into android recovery on this device?
Enzopreme said:
i see a lot of people saying they are having issues but fixing it with the android recovery... how do i get into android recovery on this device?
Click to expand...
Click to collapse
Have to either root and the install ROM Mangers from the market, or install Rom Racers via fastboot (in the dev section).
Unlocking bootloader is pretty easy. There's a stupid scrpit to do it now... see my signature for noob guide for links.
Sent from my MB860 using xda premium
okay, i followed the instructions to a "t", now my device reads
SVF:105:1:2
Failed to boot 0x1000
PwrReason: PWR_KEY_PRESS
Starting Fastboot Protocol support
PLEASE HELP!!!!
Enzopreme said:
okay, i followed the instructions to a "t", now my device reads
SVF:105:1:2
Failed to boot 0x1000
PwrReason: PWR_KEY_PRESS
Starting Fastboot Protocol support
PLEASE HELP!!!!
Click to expand...
Click to collapse
Need to enter fastboot mode and enter the command fastboot unlock or fastboot oem unlock.... or have you done that?
Sent from my MB860 using xda premium
Swiftks said:
Need to enter fastboot mode and enter the command fastboot unlock or fastboot oem unlock.... or have you done that?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Fastboot mode = turn phone off
Hold power button.and volume down
Until u see. Fastboot then press volume up to select it should read starting fastboot protocal
Plug in your USB. Cable that came with the phone open terminal and type fastboot oemunlock
Then do it again with the unique I'd. And hit enter
Sent from my MB860 using xda premium
ltdanno360 said:
Fastboot mode = turn phone off
Hold power button.and volume down
Until u see. Fastboot then press volume up to select it should read starting fastboot protocal
Plug in your USB. Cable that came with the phone open terminal and type fastboot oemunlock
Then do it again with the unique I'd. And hit enter
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Yeah, what he said
Shows you how long its been since I unlocked mine.... May, June??? First day pudding came out, whenever that was.
Sent from my MB860 using xda premium
Dear XDA Geniuses,
I have a 16gb Nexus 7 WI-Fi. I was using Nexus 7 toolkit 2.0.0 to try and flash my nexus 7 back to the the stock google rom (option 9 in the toolkit.) It seems as if it wiped out cyanogen mod 10, which i had been using, as well as clockwork recovery. My nexus 7 now boot up with the google logo and the unlocked padlock on the bootom. using the volume rocker i can select the bootloader option and get an android figure with his chest open.
this is the only option i can select. my attempts have been:
1)connect it to computer. Windows 7 and Windows 8 will not recognize it, nor let me access it from the command line.
2. Use nexus 7 toolkit, which DOES recognize it in fastboot mode, to flash a new recovery on there. it says that a command failed, and won't let it write to it.
3) install adb and android sdk tools. my tablet won't show up under devices, and I am not sure if it is still in usb debugging mode. command line will not recognize it as an adb device and will not control tablet.
when i looked at this thread it was dealing with a locked bootloader, while mine is unlocked. it also wanted command line operations from the computer, which does not seem to work for me.
i was attempting to do something like this (laptop mag blog how to hard reset a bricked nexus 7) but without my nexus 7 showing up under devices I am not sure what my options are.
TLDR: Nexus 7 16gb WIFI only boots into boot recovery. Using nexus 7 toolkit to recognize as fastboot. otherwise will not show up on computer. no recovery, no boot image.
Thank you for reading.
I went back and reread the thread on flashing and restoring nexus 7 to stock in this forum, but every command I try returns " command write failed invalid argument ". Using android sdk manager i can get it to recognize the device in fastboot mode. my drivers there seem to be working.
edit: I got all the way to flashing the bootloader, but it returned "no such device or address. "
JerryMc88 said:
I went back and reread the thread on flashing and restoring nexus 7 to stock in this forum, but every command I try returns " command write failed invalid argument ". Using android sdk manager i can get it to recognize the device in fastboot mode. my drivers there seem to be working.
edit: I got all the way to flashing the bootloader, but it returned "no such device or address. "
Click to expand...
Click to collapse
latest progress can be found at imgur slash TAikq
now it is say data transfer failure - too many links. 146.84 seconds.
it was my cable. the cable mounted it in fastboot mode, but would not allow writing. switched out the cable, and we are up and running again. thanks!
Um.... Glad we could help?
Sent from my Nexus 7 using xda app-developers app
Sticky?
Man, I would love to see this sticky posted, or at least a list of errors and fixes stickied. I have been looking for an answer to the same issue for two days. Finding out it was just a lousy cable really really really pissed me off... I'm glad someone figured it out and actually posted their solution, most of these wind up with nothing.
OMG, I've tried to flash my N7 with a new lollipop 5.1 today and got the same issue as described here http://forum.xda-developers.com/showthread.php?t=2724273 then, after 5 or 6 hours of thinking what is going on, I finally found this very old thread and guess what? Changing this sh***ty cable I was using solved the problem.
Use USB ports on the back of your computer, not the front.
I just got my Nexus 4 and installed SDK and drivers on PC. OK, so now I boots my phone into fastboot mode, I connected it to my PC, entered"fastboot devices" in command line, no problem, I can see the device with the ID.
But when I entered"fastboot oem unlock", the command line it says" FAILED <command write failed <Unknown error>>". And the phone stays in fastboot mode without any pop-up.
I use USB 2.0 ports on the backside of the computer. Also USB 2.0 on my laptop. None of them work.
I tried to factory set the phone, restart computer and phone, change to another computer, none of them worked. Maybe I should contact Google to ask for an exchange because mine can not be unlocked?
Any help is deeply appreciated.
Utahnewbie said:
I just got my Nexus 4 and installed SDK and drivers on PC. OK, so now I boots my phone into fastboot mode, I connected it to my PC, entered"fastboot devices" in command line, no problem, I can see the device with the ID.
But when I entered"fastboot oem unlock", the command line it says" FAILED <command write failed <Unknown error>>". And the phone stays in fastboot mode without any pop-up.
I use USB 2.0 ports on the backside of the computer. Also USB 2.0 on my laptop. None of them work.
I tried to factory set the phone, restart computer and phone, change to another computer, none of them worked. Maybe I should contact Google to ask for an exchange because mine can not be unlocked?
Any help is deeply appreciated.
Click to expand...
Click to collapse
Yeah, GOOGLE will be happy to replace your phone because you cannot unlock your bootloader!? Are u serious? Make sure USB debugging is enabled under developer options...
There is a app in the play store that unlocks bootloader for nexus 4.
Sent from my Nexus 4
myturbo1 said:
There is a app in the play store that unlocks bootloader for nexus 4.
Sent from my Nexus 4
Click to expand...
Click to collapse
It requires root access. Without being able to unlock bootloader, I can't root my N4
BigDig said:
Yeah, GOOGLE will be happy to replace your phone because you cannot unlock your bootloader!? Are u serious? Make sure USB debugging is enabled under developer options...
Click to expand...
Click to collapse
They probably would, actually. The ability to easily unlock the bootloader is a feature of Nexus devices.
BigDig said:
Make sure USB debugging is enabled under developer options...
Click to expand...
Click to collapse
Only applies to ADB, not fastboot
Have you got the latest SDK files? Have you got the latest bootloader?
Utahnewbie said:
I just got my Nexus 4 and installed SDK and drivers on PC. OK, so now I boots my phone into fastboot mode, I connected it to my PC, entered"fastboot devices" in command line, no problem, I can see the device with the ID.
But when I entered"fastboot oem unlock", the command line it says" FAILED <command write failed <Unknown error>>". And the phone stays in fastboot mode without any pop-up.
I use USB 2.0 ports on the backside of the computer. Also USB 2.0 on my laptop. None of them work.
I tried to factory set the phone, restart computer and phone, change to another computer, none of them worked. Maybe I should contact Google to ask for an exchange because mine can not be unlocked?
Any help is deeply appreciated.
Click to expand...
Click to collapse
Try nexus 4 toolkit
Try a different USB cable if you haven't already.
Sent from my Nexus 4 using xda premium
Hy There i finally got my nexus 4 two days ago, i tried to search Google about bootloader limitation if there is any? Im pretty freaked cause i previously used xperia S with bootloader impossible to unlock, due to a carrier lock.
So is there a metod to check if bootloader of my N4 is possible to unlock like in hidden menu *#*#4636#*#* wich i cheked but i dont know to what i should pay attention? or is there the other way to chek .
I know that unlocking and rooting should be possible in N4 but i hope u understand my concern cause i bought N4 trough carrier contract and a negative expirience with xperia s, thanx
grgana said:
Hy There i finally got my nexus 4 two days ago, i tried to search Google about bootloader limitation if there is any? Im pretty freaked cause i previously used xperia S with bootloader impossible to unlock, due to a carrier lock.
So is there a metod to check if bootloader of my N4 is possible to unlock like in hidden menu *#*#4636#*#* wich i cheked but i dont know to what i should pay attention? or is there the other way to chek .
I know that unlocking and rooting should be possible in N4 but i hope u understand my concern cause i bought N4 trough carrier contract and a negative expirience with xperia s, thanx
Click to expand...
Click to collapse
No, a Nexus device will ALWAYS have an unlockable bootloader.
I don't know if anyone has said this yet, but are you sure you're in fastboot mode when you type: fastboot oem unlock?
that command only works from the bootloader, not from inside recovery or when your system is booted up.
---------- Post added at 03:53 PM ---------- Previous post was at 03:51 PM ----------
Utahnewbie said:
It requires root access. Without being able to unlock bootloader, I can't root my N4
Click to expand...
Click to collapse
That's not entirely true with something like the motochopper method.
kbeezie said:
That's not entirely true with something like the motochopper method.
Click to expand...
Click to collapse
Does motochopper work on the nexus 4 bro? Cause id love to simply root without unlocking bootloader and such (im a noob) cause i used motochopper on my locked bootloader xperia tablet and so i understand it.
jimbohurt said:
Does motochopper work on the nexus 4 bro? Cause id love to simply root without unlocking bootloader and such (im a noob) cause i used motochopper on my locked bootloader xperia tablet and so i understand it.
Click to expand...
Click to collapse
Some google searches seem to suggest so, such as : http://forums.androidcentral.com/ne...hopper-root-without-unlocking-bootloader.html
And even this one in response to my own assumption that you can't without unlock (though he didn't exactly provide links, and not sure if was specific to the Nexus S and Nexus 7)
http://forum.xda-developers.com/showpost.php?p=42580735&postcount=10
As for me... I just unlocked it, easier.
kbeezie said:
Some google searches seem to suggest so, such as : http://forums.androidcentral.com/ne...hopper-root-without-unlocking-bootloader.html
And even this one in response to my own assumption that you can't without unlock (though he didn't exactly provide links, and not sure if was specific to the Nexus S and Nexus 7)
http://forum.xda-developers.com/showpost.php?p=42580735&postcount=10
As for me... I just unlocked it, easier.
Click to expand...
Click to collapse
Thanks for the response dude, when you unlocked did you use adb and stuff through android adk or did you use a toolkit?
jimbohurt said:
Thanks for the response dude, when you unlocked did you use adb and stuff through android adk or did you use a toolkit?
Click to expand...
Click to collapse
I just rebooted into the bootloader mode, hooked it up to my computer. Typed
fastboot oem unlock
There was a warning just after, accepted it.
then I downloaded the latest TWRP (2.5.0.0) for mako (Nexus 4)
fastboot flash recovery name-of-recovery.img
booted into recovery, made a backup of my Stock rom, wiped /system /data /cache, used the following while in recovery
adb push name-of-my-rom.zip /sdcard
adb push name-of-google-apps.zip /sdcard
then installed both via recovery and rebooted into the fresh new custom rom.
If I had not installed a custom rom, and I were to leave TWRP into a non-rooted stock:
TWRP would instead warn me that it doesn't appear to be rooted, and if I would like it to place SuperSu on it, it would do so, and I would reboot into the stock system, launch SuperSu where it will ask me if I would like it to reboot into recovery and install the su binary. Which it does automatically, so stock-wise that was the cleanest way for me to get rooted on stock (with an unlocked bootloader)
---------- Post added at 09:03 PM ---------- Previous post was at 08:57 PM ----------
By the way just as a recap.
fastboot works in the bootloader mode.
adb works in recovery and in normal system (with usb debugging enabled).
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
Evening all
Hope someone can help. I am a complete novice at anything technical regarding phones/tablets etc and this situation is driving me crazy.
My Nexus 7 (2012 model I believe) recently ran out of battery and after re-charging has been caught in what I believe to be a bootloop. I've tried to google for a straightforward answer that will solve my problem but nothing seems to work. I've done a factory re-set and unlocked the bootloader but do not have usb debugging enabled so appear to be stuck!
Is there anything I can do to solve this before the thing goes out the window?
Please please please help me!!!!
:crying:
As long as you can get to your unlocked bootloader (Power up holding the power and volume down buttons), you can send Fastboot commands to your N7 and restore an operating ROM. Follow the instructions in the second thread in this forum.
exglynco said:
As long as you can get to your unlocked bootloader (Power up holding the power and volume down buttons), you can send Fastboot commands to your N7 and restore an operating ROM. Follow the instructions in the second thread in this forum.
Click to expand...
Click to collapse
my computer doesn't seem to recognise my device when i do adb devices on the command prompt - any clues please?
Have you installed drivers for your Nexus 7 model and PC operating system?
Beccy1712 said:
my computer doesn't seem to recognise my device when i do adb devices on the command prompt - any clues please?
Click to expand...
Click to collapse
Adb devices won't list anything in fastboot mode the command you need is fastboot devices this will confirm if you have a working fastboot connection.
Then you can proceed with flashing a factory image.
Sent from my C5303 using XDA Free mobile app