Pretty sure i'm bricked... - Nexus One General

I've been searching around and I can't find an answer
So I trying doing the OTA update for gingerbread and everything failed.
Long story short, I can only get access to the bootloader (stock recovery?) Nothing else.
Furthest I've gotten is using the method of FRG33 as a PASSIMG.ZIP , which worked maybe 20% of the time, because it never actually loaded Android and stayed on
EDIT: I'm NOT bricked. I can only access bootloader, I am primarily having an issue flashing a custom recovery
Any ideas?
I don't know if this is helpful, this is the top of my bootloader:
Code:
*** UNLOCKED ***
NEXUSONE PVT SHIP S-ON
HBOOT-0.35.0017
MICROP-0B15
TOUCH PANEL-SYNT0103
RADIO-5.08.00.04
JUN 14 2010,12:02:27

You are not bricked.
If PASSIMG method does not work for you, unlock your bootloader and flash via fastboot the system and boot images and erase the userdata image.

If you can get to bootloader, you're not bricked.

georgemv said:
You are not bricked.
If PASSIMG method does not work for you, unlock your bootloader and flash via fastboot the system and boot images and erase the userdata image.
Click to expand...
Click to collapse
This may be a noob question, so please excuse me. If my bootloader says "UNLOCKED" at the top, it already is, right?
So "flash via fastboot", is that process where you go through adb correct?

Yes, you're already unlocked... you don't use ADB, you use fastboot:
fastboot flash recovery nameofrecovery.img

zeavott said:
I've been searching around and I can't find an answer
So I trying doing the OTA update for gingerbread and everything failed.
Long story short, I can only get access to the bootloader (stock recovery?) Nothing else.
Furthest I've gotten is using the method of FRG33 as a PASSIMG.ZIP , which worked maybe 20% of the time, because it never actually loaded Android and stayed on.
Any ideas?
I don't know if this is helpful, this is the top of my bootloader:
Code:
*** UNLOCKED ***
NEXUSONE PVT SHIP S-ON
HBOOT-0.35.0017
MICROP-0B15
TOUCH PANEL-SYNT0103
RADIO-5.08.00.04
JUN 14 2010,12:02:27
Click to expand...
Click to collapse
According to this info, you arnt unlocked, type in fastboot (C:/Sdkfolder/tools) fastboot oem unlock and it should say on the device
Code:
NEXUSONE PVT SHIP S-OFF
Sent from my T-Mobile myTouch 3G Slide using XDA App

Rusty! said:
Yes, you're already unlocked... you don't use ADB, you use fastboot:
fastboot flash recovery nameofrecovery.img
Click to expand...
Click to collapse
Very helpful! Thanks man. If I may further inquire, will this command work?
Code:
fastboot oem unlock
After I finish that, where would I find a recovery.img that would work? Once bootloader is unlocked, Can I simply install a custom recovery system? Also- do I run fastboot from the bootloader screen or from recovery?
OK- I read up more, looks like I have to be in the fastboot screen on the phone.
I see "FASTBOOT USB" in red at the top, I am going through the computer and when I type 'fastboot devices' , nothing shows up underneath. Drivers are properly installed.

The big UNLOCKED but in your first post means that someone had already done the "fastboot oem unlock" on your device...
Sent from my Nexus One using XDA App

I can only get access to the bootloader
Click to expand...
Click to collapse
Sounds like you don't know what the term "bricked" means, because if your device still freaking turns on, it isn't bricked.
Scratch that. It is bricked, and worthless. I'll give you $50 for it.

danger-rat said:
The big UNLOCKED but in your first post means that someone had already done the "fastboot oem unlock" on your device...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
That's what I was thinking too...
Any suggestions for 'fastboot devices' not detecting the phone?

zeavott said:
That's what I was thinking too...
Any suggestions for 'fastboot devices' not detecting the phone?
Click to expand...
Click to collapse
I would say it's either a driver issue, or your usb cable. If you can, remove your existing driver, then reconnect the phone in fastboot mode. Hopefully, that will force the correct driver install...
Sent from my Nexus One using XDA App

Tried that method. Looks the same. I will try on another computer.

GldRush98 said:
Sounds like you don't know what the term "bricked" means, because if your device still freaking turns on, it isn't bricked.
Scratch that. It is bricked, and worthless. I'll give you $50 for it.
Click to expand...
Click to collapse
Helpful...

mellowgato said:
Helpful...
Click to expand...
Click to collapse
Humor serves many purposes... xD
Sent from my Nexus One using XDA App

Related

Cannot boot into recovery---or phone!

Hi,
I mangled my clockwork recovery and stupidly didnt update to a working one. now my G1 is stuck at the boot up screen and i cant do anything. I need to get into recovery to reflash a rom!
what can i do?
Some more infos would be helpful, e.g. phone version, radio, SPL ...
For example if you have an "european" G1, you could do this:
a) If you have a fastboot enabled SPL (e.g. 1.33.2003, 1.33.2005, ...) -> go into fastboot mode, flash recovery, boot into that recovery and flash ROM
b) If you don't have a fastboot enabled SPL, make a Goldcard, flash e.g. orange-xxx.nbh -> now you have a fastboot enabled SPL, flash recovery, radio, SPL as needed, then continue with a)
i have a Uk G1.
I have 1.33.2005.
When I go into fastboot mode but i dont see "flash recovery" anywhere..
Fastboot ist a command you use from you PC while having connected your phone by USB.
In this thread you can have an overview of adb / fastboot / ... and how to set up. If you are on Winxx, probably you would like to have a look at this thread.
Nevertheless if you have set up the fastboot environment, typing
fastboot flash recovery <recovery.img>
on your local console window, having <recovery.img> in the current working directory on your PC will flash the recovery image on your phone.
im at work so cant install any of those....theres nothing i can do from my phone direct?
Unfortunately not ... how would you like to do it, when your phone neither boots recovery nor the ROM?
i see your point ! lol
I thought since i can get into the hboot screen (CAMERA and on buttons together) maybe something can be done....but obviously not!
AndDiSa said:
Fastboot ist a command you use from you PC while having connected your phone by USB.
In this thread you can have an overview of adb / fastboot / ... and how to set up. If you are on Winxx, probably you would like to have a look at this thread.
Nevertheless if you have set up the fastboot environment, typing
fastboot flash recovery <recovery.img>
on your local console window, having <recovery.img> in the current working directory on your PC will flash the recovery image on your phone.
Click to expand...
Click to collapse
Will not getting past the boot screen hinder any of this process...? especially as i keep seeing "select USB debugging mode" in these guides?
Press back+power to start phone in fastboot mode. Connect it to your PC using USB. (Probably you need to select fastboot on your phone later on, I do not remember at the moment.) After your phone was recognized by your PC (check by typing "fastboot devices") you can flash your recovery again.
There should be not G1 screen visible when starting your phone.
Sent from my Gingerbread on Dream using XDA App
As long as you can get in the HBoot... lucky you it isn't hard bricked like mine
I think I just bricked my US Tmobile G1! I was messing up trying to reflash the SPL and now the phone won't even turn on. Is there anything I can do to rescue my G1? I love the little phone.
Sent from my LG-P999 using XDA Premium App
jtag, riffbox... i never used them but i heard many people say it un bricked they're G1's lol not sure if this helps either but look into making a gold card..? or something like that.. lol or mabe the orange thing... im sorry i forget what its called..
ldrifta said:
jtag, riffbox... i never used them but i heard many people say it un bricked they're G1's lol not sure if this helps either but look into making a gold card..? or something like that.. lol or mabe the orange thing... im sorry i forget what its called..
Click to expand...
Click to collapse
Gold Card doesn't work and it is cheaper to get a new phone than to get Jtag. Thanks for your ideas anyways!
Sent from my LG-P999 using xda premium

[Q] OTA bootloader issue????

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

[Help] During pudding bad stuff happened, and don't know how to fix.

<<<<Problem resolved.>>>>
I have read around 25 forums about this, and still can't fix what they say can be fixed. During RSD my atrix failed and gave a screen with:
SVF message: 105:1:2 failed to boot
No OS detected, going to rsd mode in 5seconds press a key to stop count down available modes are:
1)rsd
2)fastboot
3)NvFlash
4)Bp HW Bypass rsd
5)BP HW bypass QC Dload
6)BP HW diag & Boot AP
7)BP HW Bypass BP only
8)BP SW Bypass RSD
9)Android recovery
10)boot android (no BP)
11)Device UID
12)console=tty50,115200n8
13 Early USB enumeration
14)BP tools"
I am a noob, and followed a sticky-ed xda guide, tried a lot, and don't know what do. Please break down any help given into something i understand, steps are great. I don't know how to program, or write script(which some forum posts suggested). Each time i select as the command fastboot, it says "starting fastboot protocol support" then does nothing. Forums posted a file to fix this, but megauploader is no longer with us.
Try to get into fastboot mode, and do the fastboot oem unlock command.
I'm on my phone so it's hard to find stuff, but i know there's a few copies of moto fastboot laying around the dev section, just search for them.
Sent from my MB860 using xda premium
Alcapone263 said:
Try to get into fastboot mode, and do the fastboot oem unlock command.
I'm on my phone so it's hard to find stuff, but i know there's a few copies of moto fastboot laying around the dev section, just search for them.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
I went with first option on accident and then it started to run RSD again, but it goes all the way to "starting fastboot protocol" and nothing happens, i have a fastboot.exe, but when i try to run it a black box with text pops up for a millisecond.
"Failed flashing process. Failed flashing process. Phone[0000]: Error switching phone to BP pass through mode (0x70BE0); phone connected." is the RSD error.
Squalcloud said:
I went with first option on accident and then it started to run RSD again, but it goes all the way to "starting fastboot protocol" and nothing happens, i have a fastboot.exe, but when i try to run it a black box with text pops up for a millisecond.
Click to expand...
Click to collapse
do you know how to you use fastboot? you need to execute it in the command line.
honestly you say you read 25 forums but i think you need to re-read the entire pudding unlock thread word-by-word, familiarize yourself with the command line and also use search. this error has happened and has been posted on many many many times before on this forum.
you need to unlock your bootloader (if it isn't already), and flash a fruitcake ROM. as of right now you have no OS, so you need to flash a fruitcake in order to put an OS back on your phone.
Tgishappened to me2 days ago when a repacemenf atrix came in. The flash is succesful(rsd. Part).... turn ur phone on, waitress till u get the 0x1002 error...then let the boot up start, and when is says fastboot protocol then ur good to go. Go to your cmd fast boot dir. Then do the fastboot OEM unlock. Now this is the part that scared me. When I did the fastboot OEM unlock #### I kept getting error. THIS PART IS CASE SENSITIVE. I was putting in fe and when I put in FE as it showed it worked. Once u unlock just flash romracer recovery and flash a rom and u are good to go. Msg me with any questions. This just happened to me literally 2 days ago.
Sent from my MB860 using xda premium
ahjdmarchi said:
Tgishappened to me2 days ago when a repacemenf atrix came in. The flash is succesful(rsd. Part).... turn ur phone on, waitress till u get the 0x1002 error...then let the boot up start, and when is says fastboot protocol then ur good to go. Go to your cmd fast boot dir. Then do the fastboot OEM unlock. Now this is the part that scared me. When I did the fastboot OEM unlock #### I kept getting error. THIS PART IS CASE SENSITIVE. I was putting in fe and when I put in FE as it showed it worked. Once u unlock just flash romracer recovery and flash a rom and u are good to go. Msg me with any questions. This just happened to me literally 2 days ago.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Just did this, and typo's in cmd killed me so much on the inside.
Did u get it. Sorry I'm on my phone laying in bed. Why I'm not more in depth... too much to write on this screen lol
Sent from my MB860 using xda premium
Got it, unlocked now. But my titanium back up didn't work for some reason, no biggie. most i lost was progress in some games.

[Q] Stuck in safe mode

Hi everybody.
I don't know how it happened (I just wanted to do a reboot in the recovery mode), but now I've got the blue led when normally turn my phone on. I can't even access to the fastboot (blue led too).
The only thing I can do, is boot in the safe mode, by booting my phone (connected to the charger) after removing the battery... I tried "reboot to bootloader", without success...
I think it's because of the recovery, because I had some problems during the installation of my last ROM, a few months ago. So I'd think I must flash a new recovery.
ow can I get out???? ADB? Special "trick"? Factory reset from the ROM? Flashing a new recovery (I don't know how...)?
Thank you, Roumaru
I tried to flash a new recovery with ADB, and then reboot to the bootloader, but it didn't work.... I'm really stuck!
Try RUU method if you are able to acces bootloader mode ,or try to search the forum or look into FAQ,for the answer of your problem.
Sent from my HTC Magic using xda app-developers app
george.wgx said:
Try RUU method if you are able to acces bootloader mode ,or try to search the forum or look into FAQ,for the answer of your problem.
Sent from my HTC Magic using xda app-developers app
Click to expand...
Click to collapse
I can't access to the bootloader... I can just access to the safe mode! It's really strange. I'll search in other forums, but I haven't found any answer yet
Roumaru said:
I can't access to the bootloader... I can just access to the safe mode! It's really strange. I'll search in other forums, but I haven't found any answer yet
Click to expand...
Click to collapse
Install mumilover's Fastboot Commander. Connect it to your PC with a USB cable, turn it on, and run Fastboot Commander. It will display a bunch of information about your phone that will help us diagnose the problem.
Just cut and paste the info it gives you. If it doesn't work, just tell us what information you see on the phone's screen.
You should see something like:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.0007 (SAPP10000)
CPLD-10
RADIO-6.35.07.29
Aug 4 2009, 19:43:30
Later.
DasBub, he cannot acces bootloader,so he 's not able to see that info
george.wgx said:
DasBub, he cannot acces bootloader,so he 's not able to see that info
Click to expand...
Click to collapse
Yes, I understand that he can't get into HBOOT, FASTBOOT, or Recovery using physical buttons. But there are other possibilities we can check. I don't know his skill level, knowledge about the device, or the complete state of his device, so I'm trying to build a clearer picture.
If fastboot reports nothing, what about adb? If adb reports nothing, check device manager to see if it's even noticed by the PC.
When I said "just tell us what information you see on the screen" what I meant was "tell us what the screen is showing, even if it is nothing at all and the blue LED is on". My fault.
I'm curious about the whole "safe mode" business. Is it truly booting into safe mode, where you can see the words "safe mode" on the screen, or is it something else?
DasBub said:
Yes, I understand that he can't get into HBOOT, FASTBOOT, or Recovery using physical buttons. But there are other possibilities we can check. I don't know his skill level, knowledge about the device, or the complete state of his device, so I'm trying to build a clearer picture.
If fastboot reports nothing, what about adb? If adb reports nothing, check device manager to see if it's even noticed by the PC.
When I said "just tell us what information you see on the screen" what I meant was "tell us what the screen is showing, even if it is nothing at all and the blue LED is on". My fault.
I'm curious about the whole "safe mode" business. Is it truly booting into safe mode, where you can see the words "safe mode" on the screen, or is it something else?
Click to expand...
Click to collapse
I took a look at "fastboot commander", but naturally I need to be in the fastboot to make it work, and I can't access fastboot...
I can NOT boot in HBOOT, FASTBOOT, and Recovery, but when I remove the battery, put it in the phone, plug my charger, and then press the power button, the phone boot normally, except he's in the "safe mode" (can't access some applications, no network). I can control my phone with ADB, but when I tried "adb reboot bootloader", the blue led was here again...
I also tried the RUU method, but the RUU doesn't recognize my phone.
I think it would be good if I could do a "total reset" of my phone, like flashing it or something that can reset the bootloader.
Thank you for your interest
Yeah dude there is fix for you its named JTAG Google it and you will find out what is it.
In my country its cost me 40 Euro to fix i hope in your is cheaper or even better - you can make your own
Roumaru said:
I took a look at "fastboot commander", but naturally I need to be in the fastboot to make it work, and I can't access fastboot...
I can NOT boot in HBOOT, FASTBOOT, and Recovery, but when I remove the battery, put it in the phone, plug my charger, and then press the power button, the phone boot normally, except he's in the "safe mode" (can't access some applications, no network). I can control my phone with ADB, but when I tried "adb reboot bootloader", the blue led was here again...
I also tried the RUU method, but the RUU doesn't recognize my phone.
I think it would be good if I could do a "total reset" of my phone, like flashing it or something that can reset the bootloader.
Thank you for your interest
Click to expand...
Click to collapse
Could you try something? Make sure your phone is accessible using adb, then do this:
adb -s [serial number for phone, without brackets] reboot oem-78
The serial number can be found using "adb devices".
That should reboot you into RUU mode. If it doesn't work, safe mode should still be accessible.
Please don't post Q&A in the development section.
Thread Moved
Moderating from my One Xl
DasBub said:
Could you try something? Make sure your phone is accessible using adb, then do this:
adb -s [serial number for phone, without brackets] reboot oem-78
The serial number can be found using "adb devices".
That should reboot you into RUU mode. If it doesn't work, safe mode should still be accessible.
Click to expand...
Click to collapse
Doesn't work, the blue led is coming again...
Another idea, except Jtag? Because I don't want to spend money on my Magic, and I don't think I've got the material to do the Jtag...
However, thank you everybody!
Roumaru said:
Doesn't work, the blue led is coming again...
Another idea, except Jtag? Because I don't want to spend money on my Magic, and I don't think I've got the material to do the Jtag...
However, thank you everybody!
Click to expand...
Click to collapse
Hey, we're not giving up yet
You can access ADB, so it may be possible to push a recovery image onto the device and flash it.
For the original instructions, click this link and focus on Step 9.
Here's a shortened version:
Download roottools and unzip it somewhere on your PC.
With your phone in Safe Mode and connected to your PC, open a command prompt.
If you know which radio you were on (3.X or less, or 6.X), cd to that directory in roottools and push the recovery image.
Example: If you have 6.X, you would
cd c:\roottools\6.35Radio\​adb push Recovery-RA-hero-v1.6.2.img /sdcard​
Next:
cd to the "App" directory of roottools, then
adb push flash_image /data/local/tmp
adb shell
su
cd /data/local/tmp
chmod 777 flash_image (you might have to use /data/local/tmp/flash_image or ./flash_image)
flash_image recovery /sdcard/Recovery-RA-hero-v1.6.2.img​
If you get through that with no errors, we should be good. If it throws an error at "su" then you should try using SuperOneClick to get temporary root.
If it flashes without errors, you can try "adb reboot recovery" and see what happens.
Resolved
A few days ago, the "safe mode" logo disappeared. Really didn't understand why, but now my problem is solved!
Thank you for all, Roumaru
Roumaru said:
A few days ago, the "safe mode" logo disappeared. Really didn't understand why, but now my problem is solved!
Thank you for all, Roumaru
Click to expand...
Click to collapse
That's great news! Everything works normally now?
I have heard that a stuck button or trackball is a possible cause. Maybe that was the problem with your phone, but it became unstuck?
Cheers!

stock nexus 7 stuck in boot loop

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

Categories

Resources