i read that it can be fixed by unlocking and rooting. problem is it is a friends and he doesn't know what version of android is on it. also can't put it in usb debugging.
Install this using Fastboot which does not require USB debugging. Simply download the factory images package then extract into the ADB folder. Typing "flash-all.bat" will flash all stock images including the boot, recovery, system and data.
thank you that worked
waiting for device
Username invalid said:
using Fastboot which does not require USB debugging. Simply download the factory images package then extract into the ADB folder. Typing "flash-all.bat" will flash all stock images including the boot, recovery, system and data.
Click to expand...
Click to collapse
I tried doing this and looked pretty promising because I have the same exact problem, but the terminal just says that it is waiting for device and does not budge. I have tried rebooting both computer and device. Neither work. Any other suggestions?
I tried again and now it says erasing 'boot'... and hangs there..
Is there any way to enable USB debugging or ADB through the command line fastboot?
curioux said:
I tried doing this and looked pretty promising because I have the same exact problem, but the terminal just says that it is waiting for device and does not budge. I have tried rebooting both computer and device. Neither work. Any other suggestions?
I tried again and now it says erasing 'boot'... and hangs there..
Is there any way to enable USB debugging or ADB through the command line fastboot?
Click to expand...
Click to collapse
Is your bootloader unlocked? If not boot into fastboot mode and type the command fastboot OEM unlock follow the prompt on the tablet and it will reboot now try the flashall.bat again. There is no way to enable USB debugging without selecting it from the menu that's a question that has been asked many times before
Sent from my C5303 using xda app-developers app
No. Sorry I forgot to mention that. My bootloader is not unlocked. And when I tried to do the fastboot OEM unlock, that is the only time the screen changes and gives me the option to unlock. When I scroll to yes and push the power button, the terminal says erasing user data and then it just gets stuck there.
I suspect that there is some kind of reading or writing problem.
Sent from my SGH-T889 using Tapatalk
curioux said:
No. Sorry I forgot to mention that. My bootloader is not unlocked. And when I tried to do the fastboot OEM unlock, that is the only time the screen changes and gives me the option to unlock. When I scroll to yes and push the power button, the terminal says erasing user data and then it just gets stuck there.
I suspect that there is some kind of reading or writing problem.
Sent from my SGH-T889 using Tapatalk
Click to expand...
Click to collapse
OK if the bootloader won't unlock that sounds like a corrupted nand partition which would mean the internal memory is unwritable. One more suggestion try downloading wugfresh NRT use the unroot back to stock option tick soft bricked and force write. I'm not sure it will work with a locked bootloader.
Sent from my C5303 using xda app-developers app
Captain Sweatpants said:
OK if the bootloader won't unlock that sounds like a corrupted nand partition which would mean the internal memory is unwritable. One more suggestion try downloading wugfresh NRT use the unroot back to stock option tick soft bricked and force write. I'm not sure it will work with a locked bootloader.
Sent from my C5303 using xda app-developers app
Click to expand...
Click to collapse
I have attached a screen shot of what I got when I tried the NRT unroot. It appears as though you were right, and that it is not going to work with a locked bootloader.
curioux said:
I have attached a screen shot of what I got when I tried the NRT unroot. It appears as though you were right, and that it is not going to work with a locked bootloader.
Click to expand...
Click to collapse
OK well it looks like you are at the new motherboard stage then. Fastboot OEM unlock failing is a pretty sure sign that the internal memory of your nexus has become corrupted and it is no longer possible to read from or write to the tablet. If you have warranty now would be a good time to use it. If not eBay is a relatively cheap place to get a replacement motherboard. Sorry I can't be of more help than that
Sent from my C5303 using xda app-developers app
Related
I went to back up and reset and selected factory reset data. it doesnt appear to be unrooted as right when i boot it up the google screen shows an unlock symbol. is there an easy way to unroot it?
biotin5000 said:
I went to back up and reset and selected factory reset data. it doesnt appear to be unrooted as right when i boot it up the google screen shows an unlock symbol. is there an easy way to unroot it?
Click to expand...
Click to collapse
If you just want the lock icon gone the command is: fastboot OEM lock
Executed via the USB cable and fastboot.exe
Here is info on how to get back to stock if not already:
http://forum.xda-developers.com/showpost.php?p=38995903&postcount=2
bigmatty said:
If you just want the lock icon gone the command is: fastboot OEM lock
Executed via the USB cable and fastboot.exe
Here is info on how to get back to stock if not already:
http://forum.xda-developers.com/showpost.php?p=38995903&postcount=2
Click to expand...
Click to collapse
when i use the root checker program to check it says that i am not rooted, but i still have that unlock on start up. i did the factory restore like i said in the op. I have never used fastboot can i use the nexus. i just used a program called nexus root toolkit to do it for me automatically. should i be good?
biotin5000 said:
when i use the root checker program to check it says that i am not rooted, but i still have that unlock on start up. i did the factory restore like i said in the op. I have never used fastboot can i use the nexus. i just used a program called nexus root toolkit to do it for me automatically. should i be good?
Click to expand...
Click to collapse
The unlock icon does not mean that the tablet is rooted, it means your boot loader is unlocked. See a couple posts back for a easy way to re lock it or use of the money tool kits...
Sent from my Nexus 10 using Tapatalk HD
Yes, my guess is the toolkit actually originally executed 'fastboot oem unlock' behind the scenes
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).
Hi guys,
first of all my problem:
After I recovered my build.prop to the original one I'd backuped and the next reboot my nexus 10 won't start anymore.
There had to be an error when copying or something I don't know but that's not the point!
The Nexus is starting until the google logo and then there's only a lightened up black display.....
starting in fastboot is possible and also the toolkit is noticing it.
The recovery mode is not possible to open (after the lying droid with the "!" i press power+volume up but only lightened up black...)
The biggest problem I have is that the USB debugging mode is deactivated
So i couldn't find out how to flsh the factory image on the device or "reanimate" it in any way.
Every trys with the toolkit end up in questions about the debugging mode.....
So I hope there's anyone out there who can help me with my problem
Thanks, dermokles
You don't need debugging on to use fastboot. Download the factory image from Google and extract the file until you see the images.
Boot into the bootloader and connect the N10 to your PC. Then run the flash-all script. It will flash all the images in sequence. You should be good to go after that.
Sent from my Nexus 10 using xda premium
El Daddy said:
You don't need debugging on to use fastboot. Download the factory image from Google and extract the file until you see the images.
Boot into the bootloader and connect the N10 to your PC. Then run the flash-all script. It will flash all the images in sequence. You should be good to go after that.
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
Don't work for me here..
The Terminal does not accept the fastboot command...
Make sure your drivers are installed correctly
Sent from my Nexus 10 using Tapatalk 4 Beta
El Daddy said:
Make sure your drivers are installed correctly
Sent from my Nexus 10 using Tapatalk 4 Beta
Click to expand...
Click to collapse
As far as I can say it they are installed propperly but i'm almost new to android and so perhaps you could give me a really short "tutorial"
would be really thankful for that
Got it.....
Just had to rename the fastboot-windows.exe into fastboot.exe and then run "fastboot oem unlock"
Dropped my nexus 4 yesterday and it fell right on the edge of the screen shattering it. First time I've broken a phone, and this one seems like a particularly bad one to have broken - no reasonable price screen replacement with the screen attached to the digitizer.
Anyway the phone boots up and charges fine, but I can't unlock it, which means my computer isn't connecting to it. Is there any way I can save all of my photos and other files?
Is USB debugging enabled?
Sent using xda-developers app
Chromium_ said:
Is USB debugging enabled?
Sent using xda-developers app
Click to expand...
Click to collapse
I believe so. But I have no way to check.
foofiebeast said:
I believe so. But I have no way to check.
Click to expand...
Click to collapse
To be clear, I can't check because I can't get past the lock screen. I also have no way of turning the phone off, I just have to wait until the battery runs out and then I have one chance to turn it on. I'm wondering if there is anything I can do in recovery mode that might help?
foofiebeast said:
To be clear, I can't check because I can't get past the lock screen. I also have no way of turning the phone off, I just have to wait until the battery runs out and then I have one chance to turn it on. I'm wondering if there is anything I can do in recovery mode that might help?
Click to expand...
Click to collapse
Setup adb http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Plug the phone in while its at the lockscreen, and run "adb devices". If the command returns the serial number of the phone let me know and I'll give you further guidance. If it doesn't it'll take a bit more work but we should still be able to get it done.
Sent using xda-developers app
Chromium_ said:
Setup adb http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Plug the phone in while its at the lockscreen, and run "adb devices". If the command returns the serial number of the phone let me know and I'll give you further guidance. If it doesn't it'll take a bit more work but we should still be able to get it done.
Sent using xda-developers app
Click to expand...
Click to collapse
Thanks mucho, I will try to get that set up now.
Set it up, but no devices listed
It's frustrating because it's so tantalizingly close. I have a pretty good idea that when I send it in to LG they are probably just going to send a different refurb back. I find it hard to believe that they do a 1 to 1 repair job on each phone that comes in.
foofiebeast said:
Set it up, but no devices listed
Click to expand...
Click to collapse
Alright. This is what you'll need to do: unlock the bootloader, flash cwm recovery, boot into cwm, use adb to copy the contents of your SD card to your PC.
Read this guide http://forum.xda-developers.com/showthread.php?t=2266654 . only follow the parts to unlock the boot loader and flash clockworkmod custom recovery. Make sure that you flash the recovery right after unlocking (without rebooting in between) otherwise data will get wiped. )
After that boot into your newly flashed recovery and use "adb pull /data/media/" . this should copy everything on the internal sdcard of the phone.
Sent using xda-developers app
Search for how to unlock the bootloader without wiping all your data. Would be moot otherwise...
Of course if all that's been done in the past and you already have cwm/twrp, just boot to that and you'll be able to adb in.
Also, you can hold onto the power button for 10s to force it to power down.
EDIT: restarted and tried again, making some progress now.
foofiebeast said:
Doesn't work because I can't enable usb debugging.
Click to expand...
Click to collapse
Again, that's why we go into cwm/twrp. Insecure debugging is enabled there.
Awesome, it appears to be copying everything over now!
Can't thank you enough! Just saved a years worth of pictures and videos, that pretty much chronicle the start of my current relationship up to the present.
Of course right now it is just pulling all of the EA real racing data, but I assume it will eventually get to the pictures, haha.
Chromium_ said:
Alright. This is what you'll need to do: unlock the bootloader, flash cwm recovery, boot into cwm, use adb to copy the contents of your SD card to your PC.
Read this guide http://forum.xda-developers.com/showthread.php?t=2266654 . only follow the parts to unlock the boot loader and flash clockworkmod custom recovery. Make sure that you flash the recovery right after unlocking (without rebooting in between) otherwise data will get wiped. )
After that boot into your newly flashed recovery and use "adb pull /data/media/" . this should copy everything on the internal sdcard of the phone.
Sent using xda-developers app
Click to expand...
Click to collapse
hey umm is there a way to get my contacts from the phone as well my phone is in the same situation thank you in advance
likidd said:
hey umm is there a way to get my contacts from the phone as well my phone is in the same situation thank you in advance
Click to expand...
Click to collapse
Make a nandroid backup in cwm, copy the backup to pc, then to another rooted phone, and use Nandroid Manager app to restore contacts
Sent from my Nexus 4 using Tapatalk 4
hackergnome said:
Make a nandroid backup in cwm, copy the backup to pc, then to another rooted phone, and use Nandroid Manager app to restore contacts
Sent from my Nexus 4 using Tapatalk 4
thank you but how exactly do you do that
Click to expand...
Click to collapse
likidd said:
hey umm is there a way to get my contacts from the phone as well my phone is in the same situation thank you in advance
Click to expand...
Click to collapse
you don't save as google contacts?
Hi guys, sorry to hijack a thread but i have followed the instructions above as have same issue; broken screen, no usb debugging, completely stock nexus 4. Have managed to install adb, got it working in cmd. I ran bootloader, unlocked it, DIDN'T REBOOT, just flashed my custome recovery CWM 6.0.3.6 and booted it. So now i am inside the recovery but i can't pull my media???
Any help would be greatly appreciated
Thanks
TMc1908
TMc1908 said:
Hi guys, sorry to hijack a thread but i have followed the instructions above as have same issue; broken screen, no usb debugging, completely stock nexus 4. Have managed to install adb, got it working in cmd. I ran bootloader, unlocked it, DIDN'T REBOOT, just flashed my custome recovery CWM 6.0.3.6 and booted it. So now i am inside the recovery but i can't pull my media???
Any help would be greatly appreciated
Thanks
TMc1908
Click to expand...
Click to collapse
You need to be more specific for us to help you. What do you mean by "i can't pull my media" ?
Chromium_ said:
You need to be more specific for us to help you. What do you mean by "i can't pull my media" ?
Click to expand...
Click to collapse
Apologies, i was a bit rushed. So i'm trying to get all my pics/data off my phone as my screen is smashed and i had a pattern lock on. My phone did not have usb debugging enabled. So i unlocked the bootloader, didn't do a reboot, flashed a custom recovery and then entered the recovery. However, my device isn't recognised in windows once i enter recovery and as such when i run "adb devices" no device is listed.
In the original instructions, it says:
After that boot into your newly flashed recovery and use "adb pull /data/media/" . this should copy everything on the internal sdcard of the phone
So how come once I load my recovery, when in cmd prompt, "adb pull /data/media" doesn't seem to work?
I'll be honest, i'm a little lost at this point and just really don't want to lose all my pics and thought i could get them this way before sending my phone for repair/replacement (it is insured)
Thanks for your help
TMc1908
TMc1908 said:
Apologies, i was a bit rushed. So i'm trying to get all my pics/data off my phone as my screen is smashed and i had a pattern lock on. My phone did not have usb debugging enabled. So i unlocked the bootloader, didn't do a reboot, flashed a custom recovery and then entered the recovery. However, my device isn't recognised in windows once i enter recovery and as such when i run "adb devices" no device is listed.
In the original instructions, it says:
After that boot into your newly flashed recovery and use "adb pull /data/media/" . this should copy everything on the internal sdcard of the phone
So how come once I load my recovery, when in cmd prompt, "adb pull /data/media" doesn't seem to work?
I'll be honest, i'm a little lost at this point and just really don't want to lose all my pics and thought i could get them this way before sending my phone for repair/replacement (it is insured)
Thanks for your help
TMc1908
Click to expand...
Click to collapse
Before you can run the adb pull command, you'll need to get your phone recognized by "adb devices". Try installing Koush's adb driver.
I have the afore mentioned Nexus 7. Have all the toolkits and proficient in adb. Get to the unlock prompt for the bootloader and press power over the yes option. It comes back up in bootloader locked every time.
I am in an endless loop otherwise. I can load to safe mode also.
Have the 4.23 bootloader and was trying to take the ota to 4.4.3.
Used two different aio toolboxes both with no luck. Tried to force load a stock rom. No luck. It just keeps booting back to how the tablet was before the update then reboots before you can do anything.
Sent from my SGH-M919 using Tapatalk
rigel1326 said:
I have the afore mentioned Nexus 7. Have all the toolkits and proficient in adb. Get to the unlock prompt for the bootloader and press power over the yes option. It comes back up in bootloader locked every time.
I am in an endless loop otherwise. I can load to safe mode also.
Have the 4.23 bootloader and was trying to take the ota to 4.4.3.
Used two different aio toolboxes both with no luck. Tried to force load a stock rom. No luck. It just keeps booting back to how the tablet was before the update then reboots before you can do anything.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
If you are proficient in adb like you state,then drop the toolkits.
What commands are you using? Does adb recognize your device?
Toolkits or cmd prompt the result is the same. Bootloader acts like it is going to unlock but doesn't.
Sent from my SGH-M919 using Tapatalk
dareino said:
If you are proficient in adb like you state,then drop the toolkits.
What commands are you using? Does adb recognize your device?
Click to expand...
Click to collapse
I too have this same issue.....
Once I get the unlock screen (using tool kit) and select yes.... it goes to reboot, but the tablet never comes back on...
Once I turn it back on, I never get passed the "Google" screen....
The tool kit ADB see's the tablet and runs through the "unlock" yet it never takes....
I assume that USB debugging is not turned on... but I can't get the tablet to start it up to turn it on...
Been trying SKIPSOFT ANDROID TOOLKIT.
Can anyone help?
Try the other toolkit.
Sent from my Nexus 4 using XDA Free mobile app
@rigel1326 , @Legobricke: Have you tried to unlock and flash stock images with fastboot? Just follow this guide: http://forum.xda-developers.com/showthread.php?t=1907796
Erovia said:
@rigel1326 , @Legobricke: Have you tried to unlock and flash stock images with fastboot? Just follow this guide: http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
Yes... I have attempted to unlock the device 3 times...
I have used 2 different tool kits and adb fast boot....
They attempt to unlock the device.... but as the unit goes to unlock, it goes to reboot and the unit doesn't come back on... If I manually turn it on, it still shows the unit as locked...
When using abd, the unit does try and unlock and then when it reboots it shows that it unlocked the device yet the device still shows locked..
I'm at a loss right now as to what I should do....
That's a problem. (Not being able to unlock with fastboot can be a sign of corrupted bootloader/partition/emmc)
Have you tried to factory reset your N7?
Erovia said:
That's a problem. (Not being able to unlock with fastboot can be a sign of corrupted bootloader/partition/emmc)
Have you tried to factory reset your N7?
Click to expand...
Click to collapse
Yes... I tried a factory reset..... but, as of now, I can't get to that option... If I try to get into recovery, it just goes to an image of the android with a red "!".......
In that case, it's most likely a hardware failure.
Legobricke said:
Yes... I tried a factory reset..... but, as of now, I can't get to that option... If I try to get into recovery, it just goes to an image of the android with a red "!".......
Click to expand...
Click to collapse
That's normal
I got the Same thing when I try to boot to stock recovery