Related
I have been rooted for a while and successfully flashed a few Roms/Kerenels using rom manager. I was flashing the newest version of Myn and one of the "warm" kernels that it offered with it. Everything was going normally the rom loaded fashed the rom and kerenel the phone was reseting then out of nowhere i got the image of the white box and android guy with an arrw as if to say "android taken out of box" I left it like that for about 5 min then took the batt out and tried to reset it. I got the same image then i tried vol. up & power it vibrated 3x and did nothing. My buddy had the same problem yesterday and he got it workin. I called him and he said all he did was pull batt/restart over and over till it booted normally. I tried that about 10x then it would not turn on again. Plugged it in, no response no led light up.
Am I bricked past the point of no return, and if not what can I do to get back in business
Stay calm, pull battery out for 5 minutes and then put it back in, then put charger in and see if LED comes on.
did that batt was out for about 20 min plugged it back in nothing
let phone charge 30 minutes
will do.. from what you know does this sound like a typical brick scenario? I feel like I didnt do anything different from all the other times I flashed roms/kerenels it just kinda flipped out on me this time?
it just happened to me, my phone wouldnt turn on or charge. Pull out battery for 1 minutre, (make sure phone isnt plugged in) out battery in, DONT PLUG IN CHARGER YET.
power phone on, once u see the white evo splashscreen, plug charger in and wait seconds and u will see LED turn on.
keep me updated
No mtter what I do or at least nothing ive tried I cannot get the Evo to respond by turning on or lighting up or doing anything
To get into bootloader, you need to press and hold vol *down* and power. Sometimes mine is finicky...be sure to firmly press those buttons, and keep them just as firmly held until you see the bootloader screen.
If that doesn't work, you might have a dead battery. Can you swap batteries with a friend?
I had this happen to me with my girls evo. Its usually related to overheating. Do you happen to have a second battery? If yu had an htc hero, they have same battery. Worked for me.
Sent from my SPH-D700 using XDA App
This happened to me while flashing the newest EViO. Don't worry, if your phone turns on a little youre most likely fine.
Sent from my Detoxed CM6.1.2 Evo 4G!
Never got it working or turned on but I took it to a Sprint tech center andt they gave me a new one... It would not power on even when they opened it up. they just replaced it.
I Really didnt even do anything. flashed cm7.0.2 few days ago
with pershoot kernel
been running fine. never overclocked etc.
just few hours ago my phone kept freezing and when i turn it back on it would show black screen, pulled battery rebooted and froze in bootscreen.
wiped dalvik cache wiped cache rebooted been working fine then froze again
same thing happened
repeated the process then forze again so i thought i would wiped the whole thing so did factory reset and it showed something like E:cant mount/recovery/cache or w/e
(i used gmethod to rooted the device.)
....i flashed miui on top of it then flashed kernel and those error popped up again
....i was scraed rebooted...htc logo
for like 10 min...pulled out the battery....now my phone wont turn on... any ideas?
i know the phone is done for real. when i plug into charger nothing comes up
when i turn it on nothing comes up
when i turn it on to hboot nothing comes up
does anyone know where i can get a new motherboard?
i voided the warranty by doing the spring mod
or new screws with void stickers.
It's possible the battery is having problems, i doubt it though, it seems as though youve hard bricked your phone.
does anyone know where i can get the motherboard or better
OEM htc g2 screws with void stickers?
eunkipark92 said:
does anyone know where i can get the motherboard or better
OEM htc g2 screws with void stickers?
Click to expand...
Click to collapse
Haha
Sent from my T-Mobile G2 using XDA Premium App
By the looks of things, any number of factors could be contributing to your Desires errors. However, it does seem like you've messed up the partitioning on the Desire Z internal memory and its giving you errors for it.
Try these steps.
1. Take the battery out and plug in your charger.
If the light doesnt come up try plugging your USB cable into your PC to charge.
If the light still doesn't come up your Desire Z is gone.
However, if the light does eventually come on, go to 2.
2. If any light comes up, then try turning it on.
If the screen turns on and you see ANYTHING besides black thats GOOD. go to 3
If the screen doesn't turn on there may be a motherboard issue.
3. Now if you can get it to turn on and not show black you should try this:
3a. Plug it into your PC then from there hold VOL DOWN and then navigate your way to Fastboot. It should say FASTBOOT USB or something like that.
3b. Flash a stable ROM onto your phone via your PC by going into recovery, mounting as storage then copying a ROM over. Then just flash the ROM onto your Desire Z and it should be fine.
If all this fails you should send it to a repair shop. There's no way you would get warranty to fix it at this point.
so ok i managed to get mini usb cable
When i conntected my phone to charger last night the orange battery light came on.
but nothing else.
when i clicked voulme down button then connected it to my computer it vibrated 5 times then green light came on.
And on my computer it showed up as Qualcom CDMA technologies MSM.
im searching everywhere to see if i can fix it. at this point any help would be appreciated.
I did notice that even though the phone wasnt turning on the phone was getting hot? (it wasnt connected to the charger obviously.)
when i did battery pull and leave it out it cools down. when i put it back in and turn it back on it gets hot after a while even though the screen and everything does not turn on.
Do this:
Pop out the battery and leave it for maybe 1 minute.
Then put the battery back in and see if the phone gets hot. If the phone does get hot skip passed 3 and 4.
Now assuming the phone doesn't get hot, plug it into your charger for about 5 minutes before turning the phone on. Try and get into Fastboot/Bootloader.
Once in your bootloader, just navigate your way to recovery and flash a new rom.
If the phone/battery gets hot it means its turned itself on as soon as the battery has gone and the phone isn't displaying anything. You should try just plugging the phone into the charger and turning it on. See if you get anything up on the screen. If you do then just jump into recovery and flash a rom.
Otherwise, if the screen always stays black regardless of what you do, send it in for repairs.
Aegishua said:
Do this:
Pop out the battery and leave it for maybe 1 minute.
Then put the battery back in and see if the phone gets hot. If the phone does get hot skip passed 3 and 4.
Now assuming the phone doesn't get hot, plug it into your charger for about 5 minutes before turning the phone on. Try and get into Fastboot/Bootloader.
Once in your bootloader, just navigate your way to recovery and flash a new rom.
If the phone/battery gets hot it means its turned itself on as soon as the battery has gone and the phone isn't displaying anything. You should try just plugging the phone into the charger and turning it on. See if you get anything up on the screen. If you do then just jump into recovery and flash a rom.
Otherwise, if the screen always stays black regardless of what you do, send it in for repairs.
Click to expand...
Click to collapse
yea it stays black no matter what i do,, but it does get hot though.
Farout.. you should really send it to a repair shop then. The reason why is because you can't do anything to the device without the screen on. You can try and hope for it to boot into HBOOT but you would have better luck sending it off on Warranty or to a phone repairs place.
Aegishua said:
Farout.. you should really send it to a repair shop then. The reason why is because you can't do anything to the device without the screen on. You can try and hope for it to boot into HBOOT but you would have better luck sending it off on Warranty or to a phone repairs place.
Click to expand...
Click to collapse
yae the replacement is already on their way
Haha thats brilliant. Don't brick this one lol.
So I'm watching tv, and I plug in my phone to charge it a bit because the GPS had gotten stuck on this morning and I burned my battery down to 40%. All of a sudden I hear it buzzing over and over again...like a reboot loop.
So I pull it out of the charger, pull the battery and let it try to boot. Gives the samsung screen for a moment, then flickers, and again to the reboot loop. Holding down power for 10 sec makes it do the same thing, I can't force it into recovery or DL mode without it bootlooping either! At one point I was able to get to the download mode screen, but just 3 seconds and the screen goes black, and back to bootlooping.
I literally did nothing to it. Only thing I did different today was the GPS got stuck (which it has done before), I rebooted the phone, then when it booted again I went ahead and just shut off the GPS. But this was like 20 minutes before this started happening.
So what can I do? Right now its plugged into my computer charging while off, seems to be the only thing it can do without bootlooping.
Running CM9.1 Nightly 9/3 with included kernel and LC8 radio (I think)
zander21510 said:
So I'm watching tv, and I plug in my phone to charge it a bit because the GPS had gotten stuck on this morning and I burned my battery down to 40%. All of a sudden I hear it buzzing over and over again...like a reboot loop.
So I pull it out of the charger, pull the battery and let it try to boot. Gives the samsung screen for a moment, then flickers, and again to the reboot loop. Holding down power for 10 sec makes it do the same thing, I can't force it into recovery or DL mode without it bootlooping either! At one point I was able to get to the download mode screen, but just 3 seconds and the screen goes black, and back to bootlooping.
I literally did nothing to it. Only thing I did different today was the GPS got stuck (which it has done before), I rebooted the phone, then when it booted again I went ahead and just shut off the GPS. But this was like 20 minutes before this started happening.
So what can I do? Right now its plugged into my computer charging while off, seems to be the only thing it can do without bootlooping.
Running CM9.1 Nightly 9/3 with included kernel and LC8 radio (I think)
Click to expand...
Click to collapse
My first guess is your battery is shot. i was gonna recommend the power button failure but if its staying off it might not be that. but id let it charge fully then try to boot up.
Thanks, oddly after a bit of messing around finally got it to boot up. Immediately backed up in CWM....seems to be acting OK now. Idk what happened...
i'll guess, the USB connector got short-circuited when you plugged in, and it caused a cascade failure that fried the SD card or something else inside the phone
there was a factory defect back then with the old SGS 1 (i9000m) model, they fixed that after the 3rd batch, everyone with an old phone from 1st and 2nd release batches, were able to exchange i for a new one.
however in your case, that's not a factory defect, but you plugged it wrong (my guess)
because it has happened to me before when i plugged it in, but the battery was still not charging even after several minutes, yet the phone was getting really really hot
then i unplug, and plug it back in and got the sound feedback "tuu tuud" and then it was actually charging after a few minutes
the first time around even though the charging icon changed, there was no feed back sound, and that was the key, it was not plugged in properly.
so after that time, i always made sure to verify to make sure the phone was plugged in properly and not just relay on he visual icon.
check back after a few minutes, to make sure the phone doesn't get very hot, and it actually increased 1%
It happened again today! After a full charge overnight and no problems for the day up to a little while ago, I opened my email app, it froze, then proceeded to start boot looping. I'm in class so I don't have my computer to try to bring it out of it...so yeah that sucks...
I do remember when I got it to charge yesterday it showed it was charging for 20-30 minutes, but after I "revived" it, I found it hadn't charged at all.
I have been using a Nokia USB cable to charge my phone since I got it, because it was longer than the cheapie Samsung cable that came with it...but it hasn't ever caused problems before. And it charged just fine last night.
How long is the warranty on these things thru tmobile? I may just swap it out while I still can.
Also on an unrelated note, I upgraded to the LG3 radio because I was meaning to anyways...
I pulled it out of it again! This time I held the power button while putting the battery in, when it vibrated I let go, it vibrated again, showed the Samsung logo, and then booted like normal
May I ask what rom are you currently on?
datrapstar said:
May I ask what rom are you currently on?
Click to expand...
Click to collapse
CM9.1 nightly 9/3 with included kernel
It did it a third time during class while it was in my pocket, the power button trick didn't work this time, I had to pull the battery after the samsung logo, plugging it back in to get it to boot...but...
near the end of the CM9 boot animation, when it vibrates and the auto brightness kicks in, it started it again! I have yet to revive it...
This is a bit upsetting because I had just got CM9 the way I liked it and I don't exactly have the time right now to mess with warranty and a new phone...I would like to fix it.
There are about 20 different threads on here on how to revert to stock...let me as a last ditch try to revert to stock and see if it keeps doing it...unless somebody has any ideas...
I was working in recovery mode, i super-wiped my phone to see if installing a ROM from scratch would help, and my phone even does it in recovery mode. Warranty time.
So whats the fastest way to restore to stock? Who knows how long I will have after reviving it before it breaks again.
zander21510 said:
I was working in recovery mode, i super-wiped my phone to see if installing a ROM from scratch would help, and my phone even does it in recovery mode. Warranty time.
So whats the fastest way to restore to stock? Who knows how long I will have after reviving it before it breaks again.
Click to expand...
Click to collapse
Here you go!!
http://forum.xda-developers.com/showthread.php?p=30832325
Sent from JMT Goodness
Well, finished playing stupid for T-Mobile, in two weeks I will have my replacement T989. Now all that's left is returning this thing to stock before it starts acting up again.
And my temporary replacement phone?
HTC Dream, aka the G1, the first Android phone! Lol what a difference...GB feels like a dinosaur...
http://forum.xda-developers.com/showthread.php?t=1513359
[HOWTO]Restore to Stock/Recover from a Bad Flash. Could try the last 3 pages on this thread. That will help you go back to stock without an issue. Hell might make you wanna keep your phone if you can get it to work again.. good luck
Sent from my SGH-T989 using xda app-developers app
datrapstar said:
http://forum.xda-developers.com/showthread.php?t=1513359
[HOWTO]Restore to Stock/Recover from a Bad Flash. Could try the last 3 pages on this thread. That will help you go back to stock without an issue. Hell might make you wanna keep your phone if you can get it to work again.. good luck
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Thanks! got it all done, back to ugly, ugly stock lol...and just when I thought maybe I would have to brick it myself it did the reboot thing again...so pulled the battery and there it sits factory reset.
After using my phone for about 2 hours I stuck it in my pocket for as I was about to go into a meeting. After the meeting I pulled my phone out and it turned on (thought it was strange because I never turned it off) and I began to use it. Stuck it back in my pocket and after a couple minutes I pulled it out again to call someone but the phone was off again! I tried turning it back on and it just keeps going to either the samsung boot logo or when its plugged in it goes to the battery logo. It only stays on either on for no more than 2 seconds. So used my friends phone to test if it was my battery that was broken on his s3. After swapping battery my phone still didn't turn on and with my battery in his phone it booted right up and even was up to 81% battery life!
My phone is rooted and its running just a stock rom from sammobile.
I have no idea what to do. Any suggestions besides calling tmobile? I do not have insurance and I bought it using my uncles contract since he didnt want another phone.
Thank you
Can you get into recovery? While the phone's off hold Volume Up+Home button+Power button and see if it goes into recovery.
Sent from my SAMSUNG-SGH-T999 using Tapatalk 2
I have a N5X, unrooted, bootloader locked, 7.1.2 stock. It happened twice in the last week, the phone used to work perfectly before that. I just pick it up as usual but it doesn't turn on anymore, I tried multiple times to boot it normally or in bootloader mode but nothing happened; then the next morning I plug it into the wall the led flashes red and it reboots normally. I thought it could only happen once but it happened again yesterday night and as usual this morning it booted up. Does anybody know what the problem may be caused by? What can I do? The phone still has warranty and if no solution is found I'll send it back to Google. Sorry for my english.
I have had the exact same problem, mine only occurs when the phone is ran down to 0% and powered off. I never let that happen but I have a 3 year old son who repeatedly does it, and every time i hold my breath, praying it will come back on. Well i am holding my breath and praying once again this morning,hoping it will power back on. Do you think it could be some kind of "protected mode"to keep the battery or something else from overheating or whatever?
alezmoroni said:
I have a N5X, unrooted, bootloader locked, 7.1.2 stock. It happened twice in the last week, the phone used to work perfectly before that. I just pick it up as usual but it doesn't turn on anymore, I tried multiple times to boot it normally or in bootloader mode but nothing happened; then the next morning I plug it into the wall the led flashes red and it reboots normally. I thought it could only happen once but it happened again yesterday night and as usual this morning it booted up. Does anybody know what the problem may be caused by? What can I do? The phone still has warranty and if no solution is found I'll send it back to Google. Sorry for my english.
Click to expand...
Click to collapse
If you need the phone and are confident, try unlocking the bootloader, reflashing stock factory image and relocking the bootloader again. You will lose all the data, though.
If you can live without a phone for a while, just send it to Google/LG. Nothing else one can do imho.
When my phone was in the last steps of dying (eventual bootloop), I could disconnect the battery and it'd get farther through the boot cycle, or even once booted. Basically, after it wouldn't react to any buttons or combos, I would disconnected and reconnected the battery. Then I could give things another shot. So I'd start it, it'd make it to the colored circles, or I could boot to the recovery menu, and try some things, but at some point it would go black. Then it would not react to anything unless I disconnected the battery. Then it would react to the buttons again and eventually one of the steps would make it go black. And then take a disconnect to get another try.
It sounds like your phone may be close to dying.
By the way, I only opened it up since I was past the warranty expiration date, and LG extending the warranty to about 18 months wasn't a known thing at the time. It is actually easy to get everything apart, but hard not to make dings in the plastic cover even using plastic tools.
I would say, back up everything you can from it and expect it is going to get worse. Redoing the OS didn't save mine.