Am I Bricked?
Many people get confused on whether they are bricked or not, so I am creating this thread to help you see if you are bricked, identify your problem, and fixing it.
The term bricked means that you have "tweaked" your phones software or hardware a little to far, leaving you with a brick, or paperweight.
There are two types of bricks, Soft Brick and Hard brick. Soft Bricks are generally easy to recovery from and can result in an error in flashing kernels, modems, etc.
Soft Brick
To identify a soft brick:
1. Pull your battery.
2. Re-Inster your battery.
3. Power on your device.
If your phone is soft bricked, you will see a image like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(phone) /!\ (Computer)
Use One-Click Unbrick by AdamOutler.
Link to full thread: http://forum.xda-developers.com/showthread.php?t=1153310
Download it here
Watch the demonstration video here
As I have not been bricked in a while, I do not remember if this resets your phone to stock or if it enables download mode. If it does not reset your phone to stock, use Heimdall to do so.
After following all of theese steps, you should be running stock 2.2 froyo rooted.
TRusselo said:
More information on Soft Brick:
the soft brick screen can occasionally be used as a Download mode screen.
Chances are you received the soft brick while attempting to odin-flash something. (or heimdall)
Reboot odin (or heimdall) and phone (to soft brick screen) and re-attach cable, the first box in odin should turn yellow. If it does, flash a full rom/stock rom.
And your soft brick is gone!
Click to expand...
Click to collapse
Hard Brick
To Identify a hard brick:
1.Pull your battery
2.Re-Inster your battery
3.Plug your phone in. (into the wall, Not computer)
3A: If you do not get the battery charging animation, you may be hardbricked.
4:Hold your power button.
4A: If your phone refuses to power on at all, you are hard bricked.(if you can get to the AT&T screen, your are not technicly hard bricked, follow the following bootloop instructions)
Hardbricks are harder to recover from, and you will need a jtag or the unbrickable mod applied to your device. If you do not know how to solder, or you are completely new to it, I suggest you have it jtagged by MobileTechVideos here. If you are an expert at soldering, or have someone you can trust to solder wires to your phones board, then you can attempt the unbrickable mod here.
Bootloop
By definition, a bootloop is not a brick, but can leave your phone as useful as one. Bootloops can be caused by corrupt bootloaders, kernels, Roms, or Roms running on incompatible bootloaders.
Identify a bootloop:
1. power on your device.
2. If your phone does not get past the AT&T screen, you are in a bootloop.
If you are in a bootloop after flashing a new rom:
Try reflashing the Rom, and make sure your kernel and rom are compatible with your bootloader.
If you are in a bootloop after flashing a new kernel:
Try reflashing the kernel, and make sure your kernel and rom are compatible with your bootloader.
If you are in a bootloop after flashing a new bootloader:
Reflash the bootloader, and make sure your rom and kernel are compatible with the bootloader.
If you can not enter download mode after flashing your bootloader:
Try to wait out the bootloop, if you manage to get your phone booted (may take up to 4 hours) download terminal from the market, and use the command: Reboot download, then reflash to stock using heimdal
If you are unable to get your phone into download mode, you will need Jtag or unbrickable mod. (I had this problem, My phone booted after 2 hours from powering it on. since this happened while flashing back to stock, I was unrooted, and had to wait a total of 7 hours, through 3 reboots to get my phone rooted and into download mode.)
If I missed something, feel free to tell me .
My first post was stickied. ^.^
More information on Soft Brick:
the soft brick screen can occasionally be used as a Download mode screen.
Chances are you received the soft brick while attempting to odin-flash something. (or heimdall)
Reboot odin (or heimdall) and phone (to soft brick screen) and re-attach cable, the first box in odin should turn yellow. If it does, flash a full rom/stock rom.
And your soft brick is gone!
TRusselo said:
More information on Soft Brick:
the soft brick screen can occasionally be used as a Download mode screen.
Chances are you received the soft brick while attempting to odin-flash something. (or heimdall)
Reboot odin (or heimdall) and phone (to soft brick screen) and re-attach cable, the first box in odin should turn yellow. If it does, flash a full rom/stock rom.
And your soft brick is gone!
Click to expand...
Click to collapse
Yeah, if the phone-!-computer screen says something about hardware failure, that will also work as dl mode. For more info, hit the captivate sig link below and look for connection issues and also download mode.
TRusselo said:
More information on Soft Brick:
the soft brick screen can occasionally be used as a Download mode screen.
Chances are you received the soft brick while attempting to odin-flash something. (or heimdall)
Reboot odin (or heimdall) and phone (to soft brick screen) and re-attach cable, the first box in odin should turn yellow. If it does, flash a full rom/stock rom.
And your soft brick is gone!
Click to expand...
Click to collapse
Thanks . added to OP.
I used MobileTechVideos last month! After a flash gone wrong, my Captivate was hard bricked, ie, I couldn't even start it! No power, nada, it was dead! After reading a couple of reviews here and other places, I decided to send my phone (from Québec, Canada)!
I got it back and I can vouch for the great service! My cappy is running great! Communication was very good!
So, yeah, I highly recommend their services if you don't know how to solder and don't know what to do (like me). I could have tried but I'm pretty sure I would not have my phone anymore!
nastycrow said:
I used MobileTechVideos last month! After a flash gone wrong, my Captivate was hard bricked, ie, I couldn't even start it! No power, nada, it was dead! After reading a couple of reviews here and other places, I decided to send my phone (from Québec, Canada)!
I got it back and I can vouch for the great service! My cappy is running great! Communication was very good!
So, yeah, I highly recommend their services if you don't know how to solder and don't know what to do (like me). I could have tried but I'm pretty sure I would not have my phone anymore!
Click to expand...
Click to collapse
Just out of curiosity how long did it take from the first day you dropped your phone at the post office to the day when you got it back?
jonnyg1097 said:
Just out of curiosity how long did it take from the first day you dropped your phone at the post office to the day when you got it back?
Click to expand...
Click to collapse
I contacted them, they said it would take around 5 days. They fix and ship it out the same day they get it.
Sent from my I897
McSpammer5 said:
I contacted them, they said it would take around 5 days. They fix and ship it out the same day they get it.
Sent from my I897
Click to expand...
Click to collapse
wrong topic...
TRusselo said:
More information on Soft Brick:
the soft brick screen can occasionally be used as a Download mode screen.
Chances are you received the soft brick while attempting to odin-flash something. (or heimdall)
Reboot odin (or heimdall) and phone (to soft brick screen) and re-attach cable, the first box in odin should turn yellow. If it does, flash a full rom/stock rom.
And your soft brick is gone!
Click to expand...
Click to collapse
Thanks, followed this and it worked like a charm!
bruzski said:
wrong topic...
Click to expand...
Click to collapse
what do you mean? he asked a question, I answered him. if you mean the thread, it was moved here by one moderator and stickied by another.
Sent from my I897
McSpammer5 said:
Bootloop
By definition, a bootloop is not a brick, but can leave your phone as useful as one. Bootloops can be caused by corrupt bootloaders, kernels, Roms, or Roms running on incompatible bootloaders.
Identify a bootloop:
1. power on your device.
2. If your phone does not get past the AT&T screen, you are in a bootloop.
If you are in a bootloop after flashing a new rom:
Try reflashing the Rom, and make sure your kernel and rom are compatible with your bootloader.
If you are in a bootloop after flashing a new kernel:
Try reflashing the kernel, and make sure your kernel and rom are compatible with your bootloader.
If you are in a bootloop after flashing a new bootloader:
Reflash the bootloader, and make sure your rom and kernel are compatible with the bootloader.
If you can not enter download mode after flashing your bootloader:
Try to wait out the bootloop, if you manage to get your phone booted (may take up to 4 hours) download terminal from the market, and use the command: Reboot download, then reflash to stock using heimdal
If you are unable to get your phone into download mode, you will need Jtag or unbrickable mod. (I had this problem, My phone booted after 2 hours from powering it on. since this happened while flashing back to stock, I was unrooted, and had to wait a total of 7 hours, through 3 reboots to get my phone rooted and into download mode.)[/SIZE]
[/CENTER]
Click to expand...
Click to collapse
I'm stuck in the bootloop after going back to stock. I waited an hour or so and the phone finally started up.
How can I get the phone into download mode if I am not currently rooted?
bwandin said:
I'm stuck in the bootloop after going back to stock. I waited an hour or so and the phone finally started up.
How can I get the phone into download mode if I am not currently rooted?
Click to expand...
Click to collapse
Jig or button combo
---------- Post added at 03:52 PM ---------- Previous post was at 03:48 PM ----------
McSpammer5 said:
I contacted them, they said it would take around 5 days. They fix and ship it out the same day they get it.
Sent from my I897
Click to expand...
Click to collapse
You can't go wrong with Josh and MTV
short and good info.....had some problem learnt now...
bwandin said:
I'm stuck in the bootloop after going back to stock. I waited an hour or so and the phone finally started up.
How can I get the phone into download mode if I am not currently rooted?
Click to expand...
Click to collapse
if the button combos or a jig won't work (which in my case they did not) you will need to find a program that will auto root without the use of cwm. you will most likely have to reboot another time. after that go to the market and get terminal emulator. then use command su then command reboot download. first try the button combos.
1. hold vol up and down and plug in your USB cable to your phone and computer.
2. try vol - and power button at same time. post again if you need anymore assistance
Sent from my I897
301k jig
Is anyone try use 301k jig from dealextreme site or other else service?
I wanna buy it, cos I think I'll brick may cappy one day
darkjedi85 said:
Is anyone try use 301k jig from dealextreme site or other else service?
I wanna buy it, cos I think I'll brick may cappy one day
Click to expand...
Click to collapse
Mobile tech videos. Get your jig there
Sent from my GT-P7510 using XDA Premium HD app
According to this thread, I am hard bricked..
Whenever I try to plug my phone into the computer or wall to charge, it doesn't.
It shows the "loading" image and flickers on to the image of the battery charging animation, then flickers off.
I removed my battery, put it back in, and now it doesn't show signs of life.
The circumstances on how I got to this part are confusing, however. My phone was working properly a couple days before, but I noticed that overnight, while charging, it didn't reach 100%.
I didn't worry too much, carried on with my day and my phone died in the middle of the day. It hasn't been able to turn on/charge since. I was running an older version of MIUI, if that helps.
I'm hoping it's just a battery issue and nothing major, but it fits the description of a hardbrick.
Any ideas? Please let me know if this is the wrong place for it.
appledrank said:
According to this thread, I am hard bricked..
Whenever I try to plug my phone into the computer or wall to charge, it doesn't.
It shows the "loading" image and flickers on to the image of the battery charging animation, then flickers off.
I removed my battery, put it back in, and now it doesn't show signs of life.
The circumstances on how I got to this part are confusing, however. My phone was working properly a couple days before, but I noticed that overnight, while charging, it didn't reach 100%.
I didn't worry too much, carried on with my day and my phone died in the middle of the day. It hasn't been able to turn on/charge since. I was running an older version of MIUI, if that helps.
I'm hoping it's just a battery issue and nothing major, but it fits the description of a hardbrick.
Any ideas? Please let me know if this is the wrong place for it.
Click to expand...
Click to collapse
Your not hard bricked then
Sent from my GT-P7510 using XDA Premium HD app
I am hardbricked when flash button combo fix in gingerbeard bootloader, you don't flash anything and can't charge when stick USB so I think you may have something broken inside
McSpammer5 said:
what do you mean? he asked a question, I answered him. if you mean the thread, it was moved here by one moderator and stickied by another.
Click to expand...
Click to collapse
noo...I ment i posted in the wrong topic..
Sent from my GT-P7510 using XDA Premium HD app / CM9 kang ICS 4.0.4
Related
While I was flashing a ROM (Synergy1.3), my wife decided to move my phone to another table. When i looked at it a few minutes later,the screen was blank. Now it wont turn on at all. I had used that particular ROM before without any problems. My battery was at 90% when i started to flash. I have a terrible feeling i am bricked. Any ideas?
goralla said:
While I was flashing a ROM (Synergy1.3), my wife decided to move my phone to another table. When i looked at it a few minutes later,the screen was blank. Now it wont turn on at all. I had used that particular ROM before without any problems. My battery was at 90% when i started to flash. I have a terrible feeling i am bricked. Any ideas?
Click to expand...
Click to collapse
You take out the battery..then try it?
Dominazn said:
You take out the battery..then try it?
Click to expand...
Click to collapse
yes,also tried charging it from wall charger ans USB. I get this error when plugging into USB (QHSUSB_DLOAD)
It's hard to brick a phone. Worst case, boot into download mode and Odin up the stock image.
If you can't access Download mode, you've most likely bricked as any research I've done points to it. If you've got insurance you can pay the premium, or send it to one of the JTAG services for repair (such as MobileTechVideos).
Just don't leave or touch the phone next time when you're flashing!
With my case it's hard to hit the buttons for recovery and download. I created across to get to them. Not what you're wanting to here. But here's a tip: if you can get adb to recognize your phone but can't use buttons to get into download mode you can "adb shell" and then "reboot download". That will cause the phone to boot download/Odin mode. Hopefully that will work and you can flash back to stock.
Sent from my SCH-I535 using xda app-developers app
The phone will not power up in any way at all. I am in the 5th stage of the grieving process. Back to my Tbolt and hope Samsung honors the warranty.
goralla said:
The phone will not power up in any way at all. I am in the 5th stage of the grieving process. Back to my Tbolt and hope Samsung honors the warranty.
Click to expand...
Click to collapse
They won't honor it with a rooted phone or flash count pass 0
Sent from my Verizon Samsung Galaxy S3 4G LTE
If you cant get to download mode or get adb to recognize when properly set up you do probably have a brick. What's happening to you with the warning happened to my friend on Sprint while accidentally flashing a ROM for a different phone. What he had to do was send it in to MobileTechVideos and got it repaired for around 60$. Samsung/Verizon wont likely fix them under warranty.
My only question is if you indeed were flashing synergy, how did a system ROM brick a device. o_0 And hell even if it was another phones ROM wouldn't our locked bootloader deny overwriting?
enomele said:
If you cant get to download mode or get adb to recognize when properly set up you do probably have a brick. What's happening to you with the warning happened to my friend on Sprint while accidentally flashing a ROM for a different phone. What he had to do was send it in to MobileTechVideos and got it repaired for around 60$. Samsung/Verizon wont likely fix them under warranty.
My only question is if you indeed were flashing synergy, how did a system ROM brick a device. o_0 And hell even if it was another phones ROM wouldn't our locked bootloader deny overwriting?
Click to expand...
Click to collapse
I also accidentally flashed a rom for a different phone and am considering sending it to MobileTechVideos. Your friend had good success with them fixing his phone?
-Purk
I think this might also work for you, if the battery charging icon comes on while your charging it then this might work. When you have it connected and the charging icon comes on put it in download mode(do not unplug it until your in download mode). Then use odin to flash it back to stock. It happen to me ones and when i did this it work for me, so i don't know if this will work for you. (Sorry for my grammar)
I flashed a Jellybean touchwiz rom for Verizon GS3, and went to reboot and now nothing, zero zip nada. No charging led light, no way to get into recovery and no response.
Anything I can do?
what happens when you do vol up + home+power button?
Absolutely nothing. I tried to get back into the recovery to see if I could restore my backup and nope.
did you try leave it pluged in for 30mins ?
does it vibrate once when you try to turn it on?
No vibrating and no sign of life at all. Even when plugged into my computer, I was going to try the unbrick guide but it listed that I should be able to get into the recovery still.
NickTheMajin said:
No vibrating and no sign of life at all. Even when plugged into my computer, I was going to try the unbrick guide but it listed that I should be able to get into the recovery still.
Click to expand...
Click to collapse
leave it plugged in for a while to make sure its not drained battery
do you have a usb jig?
I don't have a USB jig but this is possibly good news. I removed the battery and SD card and plugged it into my computer and it tried to install drivers (failed but tried) and the led light comes on red.
if your gettin led now you more then likely need to let it charge
It doesn't give me the led with the battery in
Plug it into a wall charger for at least 30 or even better if you can get a battery from someone.
Sent from my sexy white Eclipsed galaxy S3
I think its gone still nothing.
red led means qualcomm download mode. sounds dead to me
Yeah, haha. I saw it and mentally prepared myself for it. Literally just got the phone today so Verizon had no qualms with just sending me a new phone. Guess I'm reactivating my Rezound in the meantime. Thanks for the help guys.
you know
I am surprised. That also happened to me the first time i flashed that very same rom (touchwiz) with twrp . I have done this so many times , i literarily can flash a rom on the way to work .
I was in shock , i still dont know how the heck can i flash a rom and brick .
I plugged mine into windows and i got the device manager driver error from hell . and my phone never came back up again
I stayed away form twrp and touchwiz and i still cant possibly comprehend how a simple rom flash can brick my phone .
Which ROM did you flash?
Sent from my SCH-I535 using xda premium
you could probably send it to get Jtag'ed for around $60 if your warranty is invalid (ie used device)
You just hard bricked it. I did the same thing. Check here - post 5 shows the same symptoms :http://forum.xda-developers.com/showthread.php?t=1770341
And here: http://forum.xda-developers.com/showthread.php?t=1791721
I was pushing a copy of root66 that I hadn't md5'd. Took a JTAG to bring me back (twice) .
Sent from my SCH-I535 using xda app-developers app
So, in the future, md5 checksum absolutely everything since I'm assuming now that that is why this happened? (Since I made doubly sure I was flashing a rom for my phone).
If you still have the file you downloaded, you can check it. That would answer that question. If it checks out fine, then we have to look elsewhere for the problem.
BTW, MobileTechVideos.com can bring you back - based on my experience with them, I highly recommend.
Sent from my SCH-I535 using xda app-developers app
Please share exactly what you did so others can benefit from your unfortunate experience.
What ROM did you flash?
Did you use ODIN or a recovery?
If recovery, which one - CWM or TWRP?
Was there any unusual condition you can think of ... low battery, USB connected to computer or to charger, etc?
I was running CM 10 and tried to flash the stock ROM. I flashed it fine (no errors in CWM, I also did clear the cache, dalvik, wiped system) after that I pressed reboot and nothing happened no Samsung just a black screen. I waited for around 10 minutes and then finally took out the battery. After that the phone wouldn't boot, recovery or download wouldn't work either. I tried everything I could and figured it's hard bricked. So if you have any suggestions on this they will be greatly appreciated. I still have my T-Mobile warranty, and the question I have is would they accept a phone that is rooted, but won't even boot so basically there is no way of finding out if it's rooted or not?
aanonymoushuman said:
I was running CM 10 and tried to flash the stock ROM. I flashed it fine (no errors in CWM, I also did clear the cache, dalvik, wiped system) after that I pressed reboot and nothing happened no Samsung just a black screen. I waited for around 10 minutes and then finally took out the battery. After that the phone wouldn't boot, recovery or download wouldn't work either. I tried everything I could and figured it's hard bricked. So if you have any suggestions on this they will be greatly appreciated. I still have my T-Mobile warranty, and the question I have is would they accept a phone that is rooted, but won't even boot so basically there is no way of finding out if it's rooted or not?
Click to expand...
Click to collapse
First error was you wiped system before reboot so there was nothing there to boot into... Leave the battery out for a bit then insert and boot into recovery.. reflash rom and this time only wipe cache and dalvik not system.. reboot.. Also how charged was the battery? maybe it is almost dead and needs charging!
Racing19969 said:
First error was you wiped system before reboot so there was nothing there to boot into... Leave the battery out for a bit then insert and boot into recovery.. reflash rom and this time only wipe cache and dalvik not system.. reboot.. Also how charged was the battery? maybe it is almost dead and needs charging!
Click to expand...
Click to collapse
I cant boot into anything at all... And the baterry was fine it was maybe at 60% when I flashed
aanonymoushuman said:
I cant boot into anything at all... And the baterry was fine it was maybe at 60% when I flashed
Click to expand...
Click to collapse
what rom were you flashing when this happened?? if it was a stock rom you should have been using odin.. unless it was one of the stock CWM flashable roms... if you can't get it going send me a pm.. I do JTAG repair
aanonymoushuman said:
I was running CM 10 and tried to flash the stock ROM. I flashed it fine (no errors in CWM, I also did clear the cache, dalvik, wiped system) after that I pressed reboot and nothing happened no Samsung just a black screen. I waited for around 10 minutes and then finally took out the battery. After that the phone wouldn't boot, recovery or download wouldn't work either. I tried everything I could and figured it's hard bricked. So if you have any suggestions on this they will be greatly appreciated. I still have my T-Mobile warranty, and the question I have is would they accept a phone that is rooted, but won't even boot so basically there is no way of finding out if it's rooted or not?
Click to expand...
Click to collapse
Wait... you wiped system after flashing stock...? That wiped the stock rom That's why nothing booted after the reboot.
I don't know why you can't get into download mode... When you plug in a usb when the battery is out does the phone vibrate? If not, try another usb cable. If that fails then you do have a hardware issue. If the phone vibrates hold vol + and vol - and power and reinsert battery-you should get download mode.
AFAIK, they (T-Mo) put the phone in download mode and check the flash counter. If it says anything other than "no" they will not accept it. Any odin flash adds to the flash counter.
anactoraaron said:
Wait... you wiped system after flashing stock...? That wiped the stock rom That's why nothing booted after the reboot.
I don't know why you can't get into download mode... When you plug in a usb when the battery is out does the phone vibrate? If not, try another usb cable. If that fails then you do have a hardware issue. If the phone vibrates hold vol + and vol - and power and reinsert battery-you should get download mode.
AFAIK, they (T-Mo) put the phone in download mode and check the flash counter. If it says anything other than "no" they will not accept it. Any odin flash adds to the flash counter.
Click to expand...
Click to collapse
As said before it's a brick, no screen, no vibration nothing. And I don't think T-Mo can even get to the phone unless they jtag it or something, which they will most likely not do as it will cause discomfort and timeloss to the customers (ME)
aanonymoushuman said:
As said before it's a brick, no screen, no vibration nothing. And I don't think T-Mo can even get to the phone unless they jtag it or something, which they will most likely not do as it will cause discomfort and timeloss to the customers (ME)
Click to expand...
Click to collapse
Well I doubt they can do that at the store (I don't have any confidence in the salespeople's tech ability there lol), so if you are under warranty just tell them that when you unplugged it this morning it was like that :laugh:
If it doesn't vibrate when plugged in and no battery installed then it sounds like a hard brick.
I think they do the manufacturer warranty as an exchange on the spot, so even if they do figure it out eventually you should be good.
But it would suck if they can get it into download mode at the store... better try numerous usb ports (even switch computers to be sure!) and cables to be sure Also wouldn't hurt to leave the battery out overnight and try again. If they get it in download mode... well two things. One they won't ever honor any warranty on the phone anymore (and they will give the phone back to you), but two... if they can get it in download mode have them leave it like that and rush back home - and then you're back in business
Kind of a win-win...
anactoraaron said:
Well I doubt they can do that at the store (I don't have any confidence in the salespeople's tech ability there lol), so if you are under warranty just tell them that when you unplugged it this morning it was like that :laugh:
If it doesn't vibrate when plugged in and no battery installed then it sounds like a hard brick.
I think they do the manufacturer warranty as an exchange on the spot, so even if they do figure it out eventually you should be good.
But it would suck if they can get it into download mode at the store... better try numerous usb ports (even switch computers to be sure!) and cables to be sure Also wouldn't hurt to leave the battery out overnight and try again. If they get it in download mode... well two things. One they won't ever honor any warranty on the phone anymore (and they will give the phone back to you), but two... if they can get it in download mode have them leave it like that and rush back home - and then you're back in business
Kind of a win-win...
Click to expand...
Click to collapse
I got a replacement going from T-Mobile, they just sent out the new phone today, but I'm confused do I send them my broken one right now? or wait till the new one comes?
They should have explained everything on the phone, they will send you a box to return it in . And if they find out that it has been rooted and modded , you could be charged the full price for the phone. Every time I sent the phone back I've always read it back to stock if yours was bricked hopefully they won't notice
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
background: rooted and was running 4.1 stock and CWM 10.0 on verizon gs3. i wanted to bump up to jelly bean 4.2 with CWM 10.1.
first i tried using Rom Manager and Rom Toolkit to flash a new rom. from Rom Manager, i rebooted into recovery and got stuck on the CWM boot screen.
After 30 minutes or so i pulled the battery and tried flashing the stock .tar.md5 using Odin and ended up with this:
"System software not authorized by verizon wireless has been found on your phone. Please turn off your phone and go to the nearest verizon wireless store for help."
now i can't boot into download or recovery. i just have this screen with the yellow exclamation point and the above message.
how screwed am i? i've tried reading everywhere and from what i can gather i didn't wipe my cache sufficiently, but all the other threads just say 'use Odin to get back to stock', but i can't get into download mode so i can't use odin.
please help.
You're bootloader wasn't unlocked. Pull the battery then hold power, volume down, and home for fifteen or twenty seconds until it boots into download mode. Odin flash a stock rom then root AND ALSO unlock your bootloader.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
You're bootloader wasn't unlocked. Pull the battery then hold power, volume down, and home for fifteen or twenty seconds until it boots into download mode. Odin flash a stock rom then root AND ALSO unlock your bootloader.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I have noticed that a lot of people have not unlocked the bootloader are posting on here that they have "bricked" their phones.
jmxc23 said:
I have noticed that a lot of people have not unlocked the bootloader posted on here that they have "bricked" their phones.
Click to expand...
Click to collapse
Ha, I agree although I think its occurred in decreasing fashion since August. Being "bricked" is used overeagerly by folks not wholly understanding their situation. You really have to try to brick this device before that word can be used correctly.
Your phone has not been bricked. You will know that you have bricked your phone when you can't turn on your phone at all. No download mode and no recovery mode also no pulling of the battery just a dead phone.
ClockworkMod
When you fix your phone, root then unlock the bootloader... You can try RM again but I believe that it is best to use ClockworkMod (or the Touch version) for flashing instead of ROM Manager - old fashion, maybe, but it works!
NOTE: Once you start flashing it becomes addictive - you have been warned
thanks for the comments. my apologies for using the term Brick incorrectly as it seems to really chap the cheeks of some people on this board (http://forum.xda-developers.com/showthread.php?t=2149210)
no luck with holding down buttons with the battery pulled. i ordered a USB Jig to try and force it back into download mode.
From there, what should my first step be? return to stock?
jondotwoz said:
thanks for the comments. my apologies for using the term Brick incorrectly as it seems to really chap the cheeks of some people on this board (http://forum.xda-developers.com/showthread.php?t=2149210)
no luck with holding down buttons with the battery pulled. i ordered a USB Jig to try and force it back into download mode.
From there, what should my first step be? return to stock?
Click to expand...
Click to collapse
youll need to put the battery back in......lol
ddurandSGS3 said:
youll need to put the battery back in......lol
Click to expand...
Click to collapse
obviously. i've tried this a million times. It shows the download screen green android robot and the text in the top left for about 4 seconds. then it goes black and the yellow triangle comes back telling me unauthorized software is on there.
check here. particularly post 2. i think thats what you want.
http://forum.xda-developers.com/showthread.php?t=1840030&highlight=odin
ddurandSGS3 said:
check here. particularly post 2. i think thats what you want.
http://forum.xda-developers.com/showthread.php?t=1840030&highlight=odin
Click to expand...
Click to collapse
thanks that's a very helpful thread. However, i still can't get into download/Odin mode. i'm guessing if/once the USB jig can force the phone into download mode, this is where i'll start.
thanks for everyone's help and patience.
Alright i got 6 hours before tmbobile store opens and i can HOPEFULLY get an exchange, but not banking on it. btw im new to rooting so i wasnt familiar with the process, but regardless i have hard bricked my NEXUS 5. Title says the problem. I followed wwjoshdew's guide to rooting on youtube, and rooted successfully. But i could'nt for the life of me figure out how to create nandroid. I ended up realizing i didnt download cmw recovery mode and downloaded it from the play store. the app took me to a button that said flash recovery and i hit it and my phone asked for permission from unknown source, i hit ok and it shut down, on 70% battery life. Not turning on please help
Try to boot the phone into bootloader mode. Just hold volume down and the power button. From there try to cycle to recovery. You use your volume down to cycle through the options and power but as select. If you can boot into recovery and have that successfully installed then you can erase your phone and try to power it on from there. If you didn't successful install the custom recovery then you'll have the standard Android recovery. You can erase everything from that too.
These phones are hard to brick and not be able to fix it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
ruben8448 said:
Try to boot the phone into bootloader mode. Just hold volume down and the power button. From there try to cycle to recovery. You use your volume down to cycle through the options and power but as select. If you can boot into recovery and have that successfully installed then you can erase your phone and try to power it on from there. If you didn't successful install the custom recovery then you'll have the standard Android recovery. You can erase everything from that too.
These phones are hard to brick and not be able to fix it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Doesn't turn on dude. No matter what. I am new to roms but i know what a hard brick is.
You should really read the guides and stickied threads at the top of these forums. The guides are very noob friendly and you wouldn't have bricked your phone. There's one to reset your device to stock as well. There's really no need for this thread and on top of that there is a sticky that says no questions in the General forums.
Sent from my Nexus 5 using Tapatalk
Determine your phone is actually off. Plug your phone into charge, if a battery sign appears in the middle of the screen then your phone is off.
If your phone is off, hold down the volume down button with the power button to start the bootloader, press volume down twice and press the power button to enter recovery.
If your screen remains black and doesn't show a battery logo, hold the volume up, volume down and power buttons at the same time for a minute, then let go and hold down the power button. Which should hopefully start your phone.
FuMMoD said:
You should really read the guides and stickied threads at the top of these forums. The guides are very noob friendly and you wouldn't have bricked your phone. There's one to reset your device to stock as well. There's really no need for this thread and on top of that there is a sticky that says no questions in the General forums.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You should have been around long enough to know that when newbies break their new toys they go nuclear and dismiss all the information around them.
BNNEBULA said:
Alright i got 6 hours before tmbobile store opens and i can HOPEFULLY get an exchange, but not banking on it. btw im new to rooting so i wasnt familiar with the process, but regardless i have hard bricked my NEXUS 5. Title says the problem. I followed wwjoshdew's guide to rooting on youtube, and rooted successfully. But i could'nt for the life of me figure out how to create nandroid. I ended up realizing i didnt download cmw recovery mode and downloaded it from the play store. the app took me to a button that said flash recovery and i hit it and my phone asked for permission from unknown source, i hit ok and it shut down, on 70% battery life. Not turning on please help
Click to expand...
Click to collapse
You bricked a Nexus?
Hold down Volume Down, Up, and Power to get into fastboot mode. Restore from Factory Image.
Normally, to root a nexus, I fastboot Team Win Recovery Project.
Anyways what you did simply could not HARD BRICK the phone.
zeekiz said:
You should have been around long enough to know that when newbies break their new toys they go nuclear and dismiss all the information around them.
Click to expand...
Click to collapse
Seriously lol. Even though the guides are right there in their faces.
Sent from my Nexus 5 using Tapatalk
HELP SOS
FuMMoD said:
You should really read the guides and stickied threads at the top of these forums. The guides are very noob friendly and you wouldn't have bricked your phone. There's one to reset your device to stock as well. There's really no need for this thread and on top of that there is a sticky that says no questions in the General forums.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
My Nexus5 doesn't flash the Led light or enter bootloader and software . I was flashing the based CM kernel and i followed the instructions nicely, while using TWRP Recovery i pressed reboot system after the flash and the phone suddenly died. I connected it to the PC and the installing drivers popup appeared and it didn't install them, problem(QHSUSB_BULK) it only appeared once. And since that, phone is dead. PLEASE HELP!!!!
Yazan Abzakh171 said:
My Nexus5 doesn't flash the Led light or enter bootloader and software . I was flashing the based CM kernel and i followed the instructions nicely, while using TWRP Recovery i pressed reboot system after the flash and the phone suddenly died. I connected it to the PC and the installing drivers popup appeared and it didn't install them, problem(QHSUSB_BULK) it only appeared once. And since that, phone is dead. PLEASE HELP!!!!
Click to expand...
Click to collapse
Do you have a link to the kernel you flashed? I think you done bricked it good.
Were you using this method?
http://www.youtube.com/watch?v=w3beFx-3Ic4
If yes,I think then all Nexus 5 users should be warned about CF's autoroot issues,because I see more and more topics related to this issue.
Simonna said:
Were you using this method?
http://www.youtube.com/watch?v=w3beFx-3Ic4
If yes,I think then all Nexus 5 users should be warned about CF's autoroot issues,because I see more and more topics related to this issue.
Click to expand...
Click to collapse
I don't believe the issues you're seeing, appears to be failed emmc, is related to chain fire's auto root. Cf is probably the most popular method to root and it's a coincidence. I've seen these failures with other root methods too.
I think the op flashed a kernel not for his device.
jd1639 said:
I don't believe the issues you're seeing, appears to be failed emmc, is related to chain fire's auto root. Cf is probably the most popular method to root and it's a coincidence. I've seen these failures with other root methods too.
I think the op flashed a kernel not for his device.
Click to expand...
Click to collapse
I am not a developer so bear with me. I'm just a guy in mpls with a completely stock N5 from Google Play that encountered similar issue as the original post. There was no damage or water issue, or other problem prior to going dead. It had about 50% battery and maybe 15 minutes after reading an email it was dead when I looked at it again. It just simply turned off while in my pocket. I could not get it to power on or enter bootloader or a recovery screen. After a week of trying to charge via USB and the original wall charger and countless attempts to hold power and volume buttons without success, I decided to pop the back off and disconnected the battery. I put it back together, but that made no difference either. Google play will send me a new phone, but I'd like to get it fired up and extract the last week or so of pics. Any ideas? Again, I am a complete noob and this 3 month old phone has not been modified in any way, other than auto updates from Google play. Thanks for any assistance or guidance.
elf1967 said:
I am not a developer so bear with me. I'm just a guy in mpls with a completely stock N5 from Google Play that encountered similar issue as the original post. There was no damage or water issue, or other problem prior to going dead. It had about 50% battery and maybe 15 minutes after reading an email it was dead when I looked at it again. It just simply turned off while in my pocket. I could not get it to power on or enter bootloader or a recovery screen. After a week of trying to charge via USB and the original wall charger and countless attempts to hold power and volume buttons without success, I decided to pop the back off and disconnected the battery. I put it back together, but that made no difference either. Google play will send me a new phone, but I'd like to get it fired up and extract the last week or so of pics. Any ideas? Again, I am a complete noob and this 3 month old phone has not been modified in any way, other than auto updates from Google play. Thanks for any assistance or guidance.
Click to expand...
Click to collapse
So, your phone doesn't turn on at all?
jd1639 said:
I don't believe the issues you're seeing, appears to be failed emmc, is related to chain fire's auto root. Cf is probably the most popular method to root and it's a coincidence. I've seen these failures with other root methods too.
I think the op flashed a kernel not for his device.
Click to expand...
Click to collapse
Correct. No symbols, no battery icon, no vibrate, etc.
elf1967 said:
Correct. No symbols, no battery icon, no vibrate, etc.
Click to expand...
Click to collapse
I'm afraid there's nothing you can do. It would have to at least get into recovery or bootloader to have a prayer.
jd1639 said:
I'm afraid there's nothing you can do. It would have to at least get into recovery or bootloader to have a prayer.
Click to expand...
Click to collapse
Thanks - was just hoping it was not a hardware failure given the posts about difficulty bricking N5. Any chance if I bought a new battery that came charged it would fire up or replacing the motherboard an option?
p.s. I am not the original poster so not sure if I ticked someone off or not, sorry if I did. Just looking for assistance
elf1967 said:
Thanks - was just hoping it was not a hardware failure given the posts about difficulty bricking N5. Any chance if I bought a new battery that came charged it would fire up or replacing the motherboard an option?
p.s. I am not the original poster so not sure if I ticked someone off or not, sorry if I did. Just looking for assistance
Click to expand...
Click to collapse
It sure sounds like a hardware failure. Doubt a different battery would help. And don't worry about being the original op. This thread is old
jd1639 said:
It sure sounds like a hardware failure. Doubt a different battery would help. And don't worry about being the original op. This thread is old
Click to expand...
Click to collapse
I get the unknown device driver when hooked up USB to computer (QHSUSB_BULK). Think it is worth waiting a few weeks prior to returning it to see if there is a way to access the flash memory via a driver download? Searches for help showed similar unknown driver problem workable on samsung and HTC last year (QHSUSB_DLOAD)
elf1967 said:
I get the unknown device driver when hooked up USB to computer (QHSUSB_BULK). Think it is worth waiting a few weeks prior to returning it to see if there is a way to access the flash memory via a driver download? Searches for help showed similar unknown driver problem workable on samsung and HTC last year (QHSUSB_DLOAD)
Click to expand...
Click to collapse
No, you won't be able to. The memory doesn't mount like a sd card would. For the future use something like drop box or Google drive too backup your photos as you take them.