Bricked/Soft Brick? - General Questions and Answers

Hi, my Atrix seems to be stuck in a boot loop although I don't think it's totally bricked.
My phone was unlocked, rooted, and running CM7 fine for several months and then the other day while charging it via USB, several apps kept started to force close so I thought I would try rebooting the phone. Upon reboot the got to the CM7 splash screen and automatically rebooted then it would only load up the Motorola symbol then reboot again and every time after it would reboot after the moto symbol. I thought no problem I would just flash back to stock via .sbf
I plugged in the phone and RSD Lite detected it. I loaded the 2.3.4 ATT SBF file (used it before 2 or 3 times safely) then started the flashing process and waited. I got to where it said reboot phone manually, so I did. After restarting the phone, it showed the Motorola creen then the ATT screen so I had thought I fixed it. While on the ATT screen it froze for a few minutes then it entered the boot loop process again getting to ATT screen each time.
I thought maybe it was a bad flash so I tried flashing the SBF again (in hindsight, probably not a good idea). It got to same place it did before and asked me too reboot and the boot loop process started again. I tried to manually restart it by holding volume down and power, but I would get the RSD Protocol Support message.
Is my phone recoverable or is bricked? If bricked, what are my options regarding obtaining a new phone since I am out of warranty, no insurance and cant upgrade till September and don't exactly have $500 for a new smartphone?

i think your phone is recoverable soft bricked

Yes soft bricked, hey you ride a 450?
Sent from my HTC Wildfire S using xda premium

Yes, soft bricked. If you can get into download mode just flash back to stock and try again. If not, use a jig. You can also buy a jig from ebay for less then $4 buy it now , free shipping.
There might be other ways but I cannot think of any atm. Its almost 4am here lol.
Sent from my Serendipity 6.4 flashed Captivate using xda premium

soft bricked...majorly due to kernal problem..reflash the kernal

Thanks all and no I don't "ride a 450" sorry (I'm assuming by that you mean motorcycle or ATV with a 450cc engine)

oh sorry I meant to ask that question to dirtbikerr450, but yes a 450cc engine

Android311 said:
oh sorry I meant to ask that question to dirtbikerr450, but yes a 450cc engine
Click to expand...
Click to collapse
No i dont sadly i ride a 125

I was finally able to get into Android Recovery by unplugging the battery then plugging in the usb then simultaneously holding volume down and plugging in the battery, I wiped the data and cache then rebooted, to my suprise it booted back up but, only to where I could make emergency calls. Tried to reflash stock with RSD Lite again this time it said passed though but I can still only make emergency calls. Any suggestions?

dirtbikerr450 said:
No i dont sadly i ride a 125
Click to expand...
Click to collapse
125s are great, I ride a crf450 great bike
Sent from my HTC Wildfire S using xda premium

whenemusattack said:
I was finally able to get into Android Recovery by unplugging the battery then plugging in the usb then simultaneously holding volume down and plugging in the battery, I wiped the data and cache then rebooted, to my suprise it booted back up but, only to where I could make emergency calls. Tried to reflash stock with RSD Lite again this time it said passed though but I can still only make emergency calls. Any suggestions?
Click to expand...
Click to collapse
Nice man! Why don't you flash cm7?
Sent from my HTC Wildfire S using xda premium

I took out the sim card and wiped it and then reinserted it and the phone booted. I don't know if I want to unlock and root again, at least probably not until ICS is here. How is CM9, stable enough for everyday use?

Im not sure, but most cm9 here are still nightlys (I think) which would be stable for everyday use, so maybe next month you will start to see stable versions out
Sent from my HTC_A510c using XDA

Related

Phone wont boot after root

So i used my xtc clip to s off an inspire and tried installing clockwork and SU but clockwork gave me an SU error. So i loaded the acehack and tried that, then i ended up getting the soft brick, so i flashed the ruu and it seemed to flash fine but now the phone wont turn on it just charges.
Out of nowhere it just turned on and started vibrating while connected to charger. It wont turn on still when i try.
xboxhaxorz said:
Out of nowhere it just turned on and started vibrating while connected to charger. It wont turn on still when i try.
Click to expand...
Click to collapse
Have you started with the easiest fix by pulling out the battery & waiting a minute & putting it back in, then try to power on the phone.
Sent from my Inspire4G using xda premium
yes left it out for 5 mins
Can you get into bootloader or fastboot
Sent from my Inspire 4G using XDA App
left battery out overnight and tried turning on again no go
no fastboot or bootloader
removed all cards and still will not power on
phone was left unplugged with battery inserted, just this moment it is now showing the htc logo and continuously vibrating
thats very weird, i dont think its bricked i think its faulty
turning it off does not work, i have to remove the battery
Does it allow you to get into the bootloader by pressing power and - volume at all?
xboxhaxorz said:
phone was left unplugged with battery inserted, just this moment it is now showing the htc logo and continuously vibrating
thats very weird, i dont think its bricked i think its faulty
turning it off does not work, i have to remove the battery
Click to expand...
Click to collapse
Sounds like you have a corrupt hboot (or ENG hboot on a late model Inspire). You need to get the stock hboot on it and it's not trivial. Try jumping into our irc channel and hopefully we can get you straightened out:
http://webchat.freenode.net/?channels=#liberatedAria
I had a similar situation happen to me. I was able to get into hboot after running hack kit but when it goes to reboot it takes about 10 minutes to finally come back on and does the same as described above. it comes on by itself finally while vibrating for about 2 minutes. after that it will come back up. i have even been able to flash custom roms to it with the only hitch that i can't reboot normally. i still just have to wait til it comes back up on its own. Very inconvenient, but still works. any ideas?
ctsfinishes said:
I had a similar situation happen to me. I was able to get into hboot after running hack kit but when it goes to reboot it takes about 10 minutes to finally come back on and does the same as described above. it comes on by itself finally while vibrating for about 2 minutes. after that it will come back up. i have even been able to flash custom roms to it with the only hitch that i can't reboot normally. i still just have to wait til it comes back up on its own. Very inconvenient, but still works. any ideas?
Click to expand...
Click to collapse
Make a nandroid of your current rom(if it's what you llike/want to use), run the RUU to restore factory config and dl the newest version of the hack kit and reroot it. Once done, restore your nandroid that you made earlier.
ATTN1 made a version of the HK w/ ENG-HBOOT that was discovered to cause very slow boots an pulled it down, the latest version should boot normally upon completion.
thank you for the info. i'll post back when i try to reroot and install ruu
i ended up warranty exchanging my phone, attn was helping me but i think mine was too fubared

[Q] Cyanomod 9 boot loop + no recovery

Hey guys. Last night my phone was completely dead, so I plugged it in to charge it. It restarted itself 3 times before fully starting up. Then it keep restarting so I just let it do that hoping it would charge it self. Now it is boot looping and I can access recovery because it freezes and won't let me pick an option in fast boot. Is there any way to restore my phone? Also my power button does not work :/
Correct me if I'm wrong but I think you might be able to wipe the data and flash a new rom via adb in bootloader mode?
Hm not sure. Is bootloader the same as fast boot screen? If so it doesn't work.
I would suggest returning your phone to stock and send it in for repair if still under warranty otherwise you'll probably just have to buy a new phone
Sent from my Nexus S 4G using Tapatalk 2
Yeah that's what I did yesterday. Sprint's retarded and has to back order it which will take a week.... Thanks anyway!

Solid amber light with no/long boot

I know this title comes up a lot but I can't seem to find my problem.
I wanted to go back to the stock rom and I used the proper RUU but totally forgot to use the S-ON tool before hand. It installed successfully but now I get a solid amber light and so far I got my inspire to boot once only to get stuck on the splash screen with it vibrating non-stop.
And now it just vibrated once, went to a black screen and then shut off. I really don't know what to do since I can't even get to HBOOT nor will the computer recognize it.
I've done numerous batter/sim card pulls as well as clean them out.
Any help would be greatly appreciated
Have you tried booting into the bootloader and doing a factory reset?
Sent from my Inspire 4G using XDA
I think he was referring to the bootloader as HBOOT. I had this problem while rooting my sisters Inspire. Might be a corrupted bootloader.
Sent from my Inspire 4G using xda premium
lay012 said:
I think he was referring to the bootloader as HBOOT. I had this problem while rooting my sisters Inspire. Might be a corrupted bootloader.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Last I remember my bootloader was TWRP which I guess I had accidentally installed somehow. If you think its a corrupted bootloader how would I go about solving this, if there is a solution?
moutansos said:
Have you tried booting into the bootloader and doing a factory reset?
Sent from my Inspire 4G using XDA
Click to expand...
Click to collapse
Never do a factory reset on a S-OFF device....it will jam u up.
greggyt79 said:
Last I remember my bootloader was TWRP which I guess I had accidentally installed somehow. If you think its a corrupted bootloader how would I go about solving this, if there is a solution?
Click to expand...
Click to collapse
It seems that the RUU you flashed was a Froyo one and your phone was running GB so you messed the bootloader. Hit the Hack Kit IRC channel (is in the OP thread) and we will lend u a hand to fix that....
Alright so I went to the IRC and they told me they couldn't help because it did not deal with the hack kit, fair enough.
I have been able to get the phone to boot after waiting for about 10 minutes but I cannot get to the bootloader. I tried rooting the phone again this way I can turn s-on then flash the stock rom again but the phone ends up not being detected half way through the process.
I really don't know what else to do...
Forgot to mention, now my inspire boots but then fades to a greyed out screen. My computer recognizes the phone as something occupying the usb port but is not accessible. Wish the phone had a physical reset button somewhere that i can poke with a paperclip...
Sent from my SAMSUNG-SGH-I897 using XDA
greggyt79 said:
Alright so I went to the IRC and they told me they couldn't help because it did not deal with the hack kit, fair enough.
I have been able to get the phone to boot after waiting for about 10 minutes but I cannot get to the bootloader. I tried rooting the phone again this way I can turn s-on then flash the stock rom again but the phone ends up not being detected half way through the process.
I really don't know what else to do...
Forgot to mention, now my inspire boots but then fades to a greyed out screen. My computer recognizes the phone as something occupying the usb port but is not accessible. Wish the phone had a physical reset button somewhere that i can poke with a paperclip...
Sent from my SAMSUNG-SGH-I897 using XDA
Click to expand...
Click to collapse
Greggyt, Hit the IRC Channel again,.....it was a rough day and we were a bit pissed. I just connected after you were gone....=0) just hit the channel again....
glevitan said:
Greggyt, Hit the IRC Channel again,.....it was a rough day and we were a bit pissed. I just connected after you were gone....=0) just hit the channel again....
Click to expand...
Click to collapse
I will get back on the IRC this evening when I get home from work thanks again!!!
Does it say anything about QHUSB_DLOAD USB device being connected?
I ran into a similar problem not too long ago, immediate vibrating followed by a solid amber light and no phone activity (nothing on the screen at all). I knew I had a backup in Recovery, but I couldn't even get into recovery.
In order to work around this, I did the following steps.
1. Deleted the PD98IMG file from my SD card (so I could get to recovery once I made it to the bootloader).
2. Take out the battery, then put it back in.
3. Plug in the phone, and let it sit for a few minutes.
4. Start into bootloader (hold power + Volume Down)
Now, in my case I was just trying to get back into recovery. if you don't have a working recovery, or no ROM to flash, you'll want to grab a few RUU 's to try from the bootloader. Try stock GB first, then try a stock Froyo just for the heck of it.
Hope this helps! Good luck to anyone else that's stumbled into this problem.
side note: I've also heard of this "power problem" occurring to other people without bootloops or screwed up bootloaders: which is solved by doing steps 2 and 3, then it'll boot up normally.
help
im having same issue i have gb stock and i accidtly did froyo ruu phones power bottun does nothing i have to plug it into computer and it will get solid amber light then eventually it either brings up battery charge icon and then if i press power button or unplug it. it just shuts off the i plug it back in and wait sometimes white htc screen comes up and it vibrates for a while then boots ad works like nothing is wrong but i cant flash gb ruu when i try to do that or re root and go to recovery to reistall ics that is on my sd as soon as phone restarts during process it doesnt reboot then i have to go threw whole procss of trying to get it to boot back up
glevitan said:
Never do a factory reset on a S-OFF device....it will jam u up.
It seems that the RUU you flashed was a Froyo one and your phone was running GB so you messed the bootloader. Hit the Hack Kit IRC channel (is in the OP thread) and we will lend u a hand to fix that....
Click to expand...
Click to collapse
im new to this site but i did exactly what you said in your post and now my inspire wont reboot unless i go threw a few hour process of plugin my phone in and i get solid amber light for like 5 min then a battery charge screen comes up then i have to unplug my phone and plug it back in the last time i did this it took about 8 hours of tryin until it finally got amber light for like 5 min then started vibrating for a min or 2 then it booted up and its bin workin fine for like a week now ive tried to reflash gingerbread ruu ive tried doin upgrade from my phone and tried reroot but as soon as it shuts down to start upgrade my phone is off and wont reboot

[Q] Bricked Phone, and T-Mobile Replacement policy

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

Phone wont start after restoring boot partition through TWRP

Guys,
Have been running MIUI V5 on my d2vzw (ported from d2spr) for a couple of days now. Noticed today that the videos were playing reversed (probably due to the ROM running on sprint kernel, correct me if i am wrong). So i flashed one of the kernels for vzw and had a bootloop.
So, in a moment of inspiration :crying:, i restored the boot partition from my MIUI v4 backup in TWRP (thinking that must be the kernel part) and the phone wont boot. No Download mode, no vibration, get the red indicator on for some seconds but thats it. I get QHSUSB_DLOAD error when connected to my computer.
Guess this is a hard brick. Would i be able to get into download mode with USB JIG (i would need to make one, if there is no chance i will not try it). Is JTAG my only option? I have no warranty between since i am using this phone in India.
Guys,
Any Help??
I doubt it, have you trying taking out the battery holding vol up, power, and home for about 3 seconds and letting go to get into recovery to wipe the miuiv4 boot
They are different versions so flashing different rom boots won't boot the rom.
Sent from my SCH-I535 using Tapatalk 2
Addiso said:
I doubt it, have you trying taking out the battery holding vol up, power, and home for about 3 seconds and letting go to get into recovery to wipe the miuiv4 boot
They are different versions so flashing different rom boots won't boot the rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Well, my thinking was since both were 4.1.2, it should not be a problem. I was proved wrong anyway. The phone has no life at all. Is JTAG my only option??
killmastern3 said:
Well, my thinking was since both were 4.1.2, it should not be a problem. I was proved wrong anyway. The phone has no life at all. Is JTAG my only option??
Click to expand...
Click to collapse
I believe so if nothing comes up but it's weird it was just the boot that you messed with. And you still get at least a red light. If it's hard bricked I believe there is no light whatsoever.
Sent from my SCH-I535 using Tapatalk 2
What is the reality of this thought anyone have the truth?, ThanksQ
Is this statement TRUE for certain? Quote: "I believe so if nothing comes up but it's weird it was just the boot that you messed with. And you still get at least a red light. If it's hard bricked I believe there is no light whatsoever."
Thanks in advance! moi
killmastern3 said:
Well, my thinking was since both were 4.1.2, it should not be a problem. I was proved wrong anyway. The phone has no life at all. Is JTAG my only option??
Click to expand...
Click to collapse
Pull battery and let sit an hour so everything discharges and try again. If still blacked out most likely J-Tag. QHSUSB_DLOAD error is a bad sign.

Categories

Resources