[Q] Cyanomod 9 boot loop + no recovery - Nexus S Q&A, Help & Troubleshooting

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!

Related

[Q] Triumph stuck going into bootloader

I was attempting to go into CWM recovery so I could make a backup but instead my phone went into the boot loader so I did a battery pull and restarted the phone by just pressing the power button no volume buttons and the phone still goes to the boot loader tried hooking it to the pc and ejecting it then a battery pull and then powered it up went right back to the boot loader Anyone know how to fix this??
Did you ever figure this out?
joehammer said:
I was attempting to go into CWM recovery so I could make a backup but instead my phone went into the boot loader so I did a battery pull and restarted the phone by just pressing the power button no volume buttons and the phone still goes to the boot loader tried hooking it to the pc and ejecting it then a battery pull and then powered it up went right back to the boot loader Anyone know how to fix this??
Click to expand...
Click to collapse
Sent from my MOTWX435KT using XDA App
No I didn't my phone is basically bricked I tried switching back to the stock recovery but it still does the same thing so I called Virgin and they are sending me a new one when they have them in stock again maybe 4 or 5 days the rep said. Thank goodness I was still under warranty.
Oh well that's good. I wonder what went wrong? I just want to avoid it if I can. Has anyone else had this problem?
joehammer said:
No I didn't my phone is basically bricked I tried switching back to the stock recovery but it still does the same thing so I called Virgin and they are sending me a new one when they have them in stock again maybe 4 or 5 days the rep said. Thank goodness I was still under warranty.
Click to expand...
Click to collapse
Sent from my MOTWX435KT using XDA App

Bricked/Soft Brick?

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

[Q] Possible brick? Need help fellas

So I goofed, pretty big this time.
I was running CM9 Alpha 5 and decided to take another shot at CleanRom, I read through the beginning instructions and saw it was a straight forward flash in recovery.
I however didn't see that if I was using CWM there would be some major issues.. HEEEE wasn't lying.
The phone bootloops only getting to the initial HTC screen, the loading bar doesn't even load up then power off then repeats. What's even stranger is it won't turn off unless I plug the usb cord in and fiddle with it for a few mins. I figure if I can get back into recovery all should be bueno. Just how might I do that? I've tried getting to recovery from the phone itself and tried hooking it up to a PC that will see the device, no such luck. It makes the notification on the PC that a usb has connected then makes the disconnect notification sound and cycles through that till I unplug it.
So is there any saving this thing? Or did I goof so hard its a paper weight?
tl:dr I flashed CleanRom in CWM without knowing that I shouldn't have used CWM. It's boot looping and I can't get it to enter recovery mode on adb. Am I screwed or is there something I can do?
Thanks so much guys, I can't believe I let myself think everything would be peachy when I flashed w/o reading EVERYTHING. Lesson learned.
Happened to me too. You have to relock your boot loader, download a stock RUU for your carrier and return to stock, reunlock then reroot and try it again with TWRP.
Sent from my HTC One X
danielsaenz said:
Happened to me too. You have to relock your boot loader, download a stock RUU for your carrier and return to stock, reunlock then reroot and try it again with TWRP.
Sent from my HTC One X
Click to expand...
Click to collapse
Worked like a charm man! Thanks so much!

Am i bricked...

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)

[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

Categories

Resources