Database Users

Pretty sure i'm bricked...

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

broke something again

I didn't think that I'd ever brick my phone and NOT be able to recover it. I've got a real brick now. I don't have a dev cable another battery or an external charger. I wanted to unlock the bootloader. I made some kind of error and now I have SVF:105:1:2
Failed to boot 0x1000
no OS detected, going to RSD mode.
Battery too low to flash.
If i try for android recovery I get Magic Value mismatch in red letters followed by
Reading ODM fuse: 1
any way around this until I can figure out how to get the battery charged up?

How did you get this error?
Sent from my MB860 using XDA Premium App

Did you get it flashing pudding? If so all you need to to is type the fastboot commands and then fastboot reboot
Sent from my MB860 using XDA App

jruweaver said:
How did you get this error?
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
flashing zomgunlock-lite sbf. I just now have the unlocked bl 4.5.91 sbf that was posted in the forums. I have the full screen menu. I tried to use fastboot oem unlock but, it was not unlocking. will the phone charge without being turned on? I normally always use a wall usb charger or usb cable to computer to charge the phone turned on. I have rsd lite 5.3.1

Are you familiar with fastboot?
Sent from my MB860 using XDA Premium App

As far as i know, thats the code or hard bricking. Meaning "kaput"

I just unlock my bootloader with my battery at 30%. N now i have Ninja!!
Sent from my MB860 using XDA App

If you got it while flashing "pudding" and can still get into fastboot, then the fastboot OEM unlock should fix it.
Sent from my MB860 using XDA Premium App

jruweaver said:
If you got it while flashing "pudding" and can still get into fastboot, then the fastboot OEM unlock should fix it.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
I got the SBF and now I'm waiting on an external battery charger to arrive. once thats here I'll be able to RSD the sbf. At least I haven't tried to downgrade the system. I'm seeing threads everywhere of hard bricks. This same error but without any of the options to fix anything, no menu options.

This happened to me. Borrow a charged battery..and choose option 2 for fastboot and type in the fastboot commands.
Sent from my MB860 using XDA App

defnow said:
This happened to me. Borrow a charged battery..and choose option 2 for fastboot and type in the fastboot commands.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
which fastboot commands? the fastboot oem unlock? was it that or something else?

1. Charge the battery to full with an external charger
2. Turn off phone (of course is off )
3. Press vol down while you turn on
4. Wait until "fastboot" tag show up
5. Press vol up to select fastboot
6. Now you phone is in fastboot mode
7. Connect USB to pc
8. Now run fastboot commands as follow:
fastboot OEM unlock
It will show up your unique id #
re type
fastboot OEM unlock "your unique id#"
And then
fastboot reboot
By the way you must have fastboot command files
Easy way download my script AUTOMATIC_UNLOCKV3.3 and unzip to your hard disk and just run the file "fix.bat"
I hope it help
powerlifter450 said:
which fastboot commands? the fastboot oem unlock? was it that or something else?
Click to expand...
Click to collapse
Sent from my MB860 using XDA App

[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]Brick ?

Hey , i havent touched my N7 forquit a while .. today i tryed to turn it on and found out it is out off power soi plugged it into my charger but when i tried to turn it up i passed the google logo and was stuck at the blackbean logo (when its connected to the charger it show the charging ani but turns off after 5 sec then i need to click the power bottom to see the charging ani again) and when i try to get into fastboot i cant . it just shows me the place where i can select between "start" , "recovery" and "fastboot" but it get stuc on that screen . i cant move anything or just hit "start" cuz it doesnt work either .
So am i bricked ? what can i do ?
i dont understand how that happened since i didnt touch it all week long .. (oh yea and the battery never charges it stays forever on the lowest point of the ani)

Leave it charge for a while without messing with it.
secondly it is not bricked, if it turns on any bit and if it shows anything on the screen it is not bricked.
I don't know why people keep using that word incorrectly, brick means that your device is basically a brick, a paperweight.
And that screen that says recovery etc IS where you fastboot from, that's the bootloader screen.
Sent from my Nexus 7 using xda premium

nodstuff said:
Leave it charge for a while without messing with it.
secondly it is not bricked, if it turns on any bit and if it shows anything on the screen it is not bricked.
I don't know why people keep using that word incorrectly, brick means that your device is basically a brick, a paperweight.
And that screen that says recovery etc IS where you fastboot from, that's the bootloader screen.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
OK , thank you .
still , l cant get to the fastoot and into the rom itself or recovery meaning i cant do nothing . how screwed am I ?

rkiller51 said:
OK , thank you .
still , l cant get to the fastoot and into the rom itself or recovery meaning i cant do nothing . how screwed am I ?
Click to expand...
Click to collapse
If you get to the menu that says "recovery" "start" "reboot bootloader" then you are in fastboot mode/bootloader.
Leave it charge a while and see if it works and if not you can flash a factory image or better yet, reflash your recovery and flash a ROM zip
Sent from my Nexus 7 using xda premium

nodstuff said:
If you get to the menu that says "recovery" "start" "reboot bootloader" then you are in fastboot mode/bootloader.
Leave it charge a while and see if it works and if not you can flash a factory image or better yet, reflash your recovery and flash a ROM zip
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I cant . its in that mode but still stuck , flashing doesnt work and so is any kind of flashing .
what can i do ?

What error do you get when you try flash something by fastboot?
Sent from my Nexus 7 using xda premium

When you are 'stuck' in fastboot, you have a couple ways to go about it... one option and that is to run the N7 toolkit to get the N7 into recovery. From there you can restore your stuff, drop stuff onto your N7 to flash a new rom, etc...
http://forum.xda-developers.com/showthread.php?t=1809195
Basically you run the toolkit like you are going to root it. Then when you get past installing the USB drivers and such, IIRC there was an option to get into recovery.

Ughh, toolkits.
Sent from my Nexus 7 using xda premium

nodstuff said:
What error do you get when you try flash something by fastboot?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
kpjimmy said:
When you are 'stuck' in fastboot, you have a couple ways to go about it... one option and that is to run the N7 toolkit to get the N7 into recovery. From there you can restore your stuff, drop stuff onto your N7 to flash a new rom, etc...
http://forum.xda-developers.com/showthread.php?t=1809195
Basically you run the toolkit like you are going to root it. Then when you get past installing the USB drivers and such, IIRC there was an option to get into recovery.
Click to expand...
Click to collapse
nodstuff said:
Ughh, toolkits.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
DOESNT wrok . i am stuck at "waiting forr device" .. annoying .
now that i charged all night i can move in bootloader screen ! but when i get into recovery it is stucked in google logo and hen i plug it to the PC / charger it just get stucked and i cant move it anymore or use any tool kit . its like the device is dead !
any ideas ?

Sounds like you need to fastboot the factory image to the device. Try multiple versions of fastboot. People have been reporting problems and switching to a new version of fastboot has helped.
Sent from my Nexus 7 using XDA Premium HD app

kkl0wn said:
Sounds like you need to fastboot the factory image to the device. Try multiple versions of fastboot. People have been reporting problems and switching to a new version of fastboot has helped.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
How can i do that ?
- no recovery
- no fastboot (freez on plug)
- no boot
=nothing ?
or am i missing somthing ? i can think of a way to solve this . plz help !!

Try a new version of fastboot... possibly from one of the rootkits then follow these instructions....
http://forums.androidcentral.com/ne...ide-factory-image-restore-your-nexus-7-a.html
Sounds like you're in fastboot mode and the above should work. Possibly make a YouTube video to show us the problems.
http://forum.xda-developers.com/showthread.php?t=1929617 ( Here's a thread that shows what I mean. Some people have problems with certain fastboot versions.)
Sent from my Nexus 7 using XDA Premium HD app

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