Related
I don't know what went wrong..
My phone stuck at dialer after i made a phone call..therefore I pulled out the battery,put it back & try to turn it on..but nothing happened.
I tried to go into recovery (volume down+power) but it still wont turn on..
Also i tried to use ADB but my phone not detected..
The phone wont turn on,nothing on the screen,LED light not blinking (even when i connect to PC or wall charger)
Please let me know if you guys got any suggestion or even better if there is a solution..
please dont tell me that my phone is bricked
far8s said:
I don't know what went wrong..
My phone stuck at dialer after i made a phone call..therefore I pulled out the battery,put it back & try to turn it on..but nothing happened.
I tried to go into recovery (volume down+power) but it still wont turn on..
Also i tried to use ADB but my phone not detected..
The phone wont turn on,nothing on the screen,LED light not blinking (even when i connect to PC or wall charger)
Please let me know if you guys got any suggestion or even better if there is a solution..
please dont tell me that my phone is bricked
Click to expand...
Click to collapse
any luck on this??? i jacked mine up trying to flash a new firmware and am stuck in the same boat with my sensation being completely unresponsive.
You could factory reset it:
From the manual:
If you can’t turn HTC Sensation 4G on or access settings, you can still perform a factory reset by using the hardware buttons on HTC Sensation 4G.
1. Remove the battery, wait for a few seconds, then reinsert the battery.
2. Press and hold the VOLUME DOWN button, and then briefly press the POWER button.
3. Wait for the screen with the three Android images to appear, and then release the VOLUME DOWN button.
4. Press VOLUME DOWN to select FACTORY RESET, and then press the POWER button."
Overlord-in-training said:
You could factory reset it:
From the manual:
If you can’t turn HTC Sensation 4G on or access settings, you can still perform a factory reset by using the hardware buttons on HTC Sensation 4G.
1. Remove the battery, wait for a few seconds, then reinsert the battery.
2. Press and hold the VOLUME DOWN button, and then briefly press the POWER button.
3. Wait for the screen with the three Android images to appear, and then release the VOLUME DOWN button.
4. Press VOLUME DOWN to select FACTORY RESET, and then press the POWER button."
Click to expand...
Click to collapse
It was stated that he can't access the bootloader, which is what is required for the "FACTORY RESET"...
There are a number of people reporting this issue. I've even experienced the issue after the device powered down due to a drained battery. Luckily I have a stand alone charger. I put the battery on the charger for about 15 minutes, put it back in the device and it was able to boot, charge, connect usb etc...
I tried for 20 minutes to get any response from the device before trying the charger.
No charging LED isn't a good sign.
There seem to be more and more people reporting with this problem these last few weeks. IT happened with mine....it was not battery drained cuz it went dead when battery was 100% charged. I've been trying to get input as to whether this is related to ROM or firmware we're flashing....but no one seem to know.
Nothing will work...ADB...battery out...etc...I've sent my phone back to HTC...waiting to see what happens.
There are at least 3-4 different post with the same problem the past few weeks.
newr said:
There seem to be more and more people reporting with this problem these last few weeks. IT happened with mine....it was not battery drained cuz it went dead when battery was 100% charged. I've been trying to get input as to whether this is related to ROM or firmware we're flashing....but no one seem to know.
Nothing will work...ADB...battery out...etc...I've sent my phone back to HTC...waiting to see what happens.
There are at least 3-4 different post with the same problem the past few weeks.
Click to expand...
Click to collapse
What rom were you running when this happened?
GROGG88 said:
It was stated that he can't access the bootloader, which is what is required for the "FACTORY RESET"...
There are a number of people reporting this issue. I've even experienced the issue after the device powered down due to a drained battery. Luckily I have a stand alone charger. I put the battery on the charger for about 15 minutes, put it back in the device and it was able to boot, charge, connect usb etc...
I tried for 20 minutes to get any response from the device before trying the charger.
Click to expand...
Click to collapse
Well what i did was that i had a brand new sensation, i got it s-offed, rooted, cwm, superCID. all that done following the guide here on XDA. i wanted to have the new elegancia ICS rom which required the 3.32 firmware with the 4ext recovery. I got the 4ext flashed and then flashed the 3.32 firmware which caused a bootloop. then i panicked and tried to put it back to stock. not realizing that it was prolly bootlooping due the stock rom not being compatible with that firmware (not positive if that caused the bootloop. just a guess) it bricked after trying to put it back to stock. nothing responds. computer doesnt recognize it. new battery doesnt to anything. no charging led. looking back on what i did. I was still able to get into the 4ext recovery when it was bootlooping. If i flashed a compatible rom while it was doing that would it have fixed the issue. can anyone confirm if the bootloop was caused due the the stock TMOUSA rom not being compatible with 3.32? Tmobile is going to send me a brand new one. I'd like that rom but dont wanna repeat the same mistake lol
Thanks
shawn0223 said:
Well what i did was that i had a brand new sensation, i got it s-offed, rooted, cwm, superCID. all that done following the guide here on XDA. i wanted to have the new elegancia ICS rom which required the 3.32 firmware with the 4ext recovery. I got the 4ext flashed and then flashed the 3.32 firmware which caused a bootloop. then i panicked and tried to put it back to stock. not realizing that it was prolly bootlooping due the stock rom not being compatible with that firmware (not positive if that caused the bootloop. just a guess) it bricked after trying to put it back to stock. nothing responds. computer doesnt recognize it. new battery doesnt to anything. no charging led. looking back on what i did. I was still able to get into the 4ext recovery when it was bootlooping. If i flashed a compatible rom while it was doing that would it have fixed the issue. can anyone confirm if the bootloop was caused due the the stock TMOUSA rom not being compatible with 3.32? Tmobile is going to send me a brand new one. I'd like that rom but dont wanna repeat the same mistake lol
Thanks
Click to expand...
Click to collapse
Yep, it was because stock was incompatible with that fw, happened to me two weeks ago when I got my sensation and I started tinkering, I flashed opensensation and I was good to go
Sent from my sensational sensation 4g
yahhboy said:
Yep, it was because stock was incompatible with that fw, happened to me two weeks ago when I got my sensation and I started tinkering, I flashed opensensation and I was good to go
Sent from my sensational sensation 4g
Click to expand...
Click to collapse
so if i do the same process and go flash the new rom right after flashing the fw. i shouldnt have a problem right?
tjamaican said:
What rom were you running when this happened?
Click to expand...
Click to collapse
I installed 6.6.2 Revolution. It booted fine after I installed the ROM...so unlike some others, the installation seems to worked fine. I was able to run Titanium and restalled all the programs....but then when I talked on the phone....it became unresponsive and shutdown and never turned on again
Having similar problem.........only thing my phone just vibrates......the led is red for couple seconds when charger is connected
dreaddie101 said:
Having similar problem.........only thing my phone just vibrates......the led is red for couple seconds when charger is connected
Click to expand...
Click to collapse
WEll..if your phone lights up or have some response.maybe you can still do something by connecting to computer. Mine was completely unresponsive...and can't be detected on computer!
Maybe it's an overclock issue? I've read on different threads that there may be a motherboard issue. The sensation is known for overheating. Maybe it's frying the motherboard.
What frequency were you guys running and was your phones randomly shutting down before it became unresponsive?
i think we guyz got the same problem :S its just turned off with a constant beep
http://forum.xda-developers.com/showthread.php?t=1624293
shawn0223 said:
so if i do the same process and go flash the new rom right after flashing the fw. i shouldnt have a problem right?
Click to expand...
Click to collapse
Yes you should be fine, just make a backup of stock in case something goes wrong when you flash your first rom
Sent from my sensational sensation 4g
yahhboy said:
Yes you should be fine, just make a backup of stock in case something goes wrong when you flash your first rom
Sent from my sensational sensation 4g
Click to expand...
Click to collapse
Awesome, I just got my new sensation yesterday. Worked like a charm.
---------- Post added at 08:29 AM ---------- Previous post was at 08:28 AM ----------
shawn0223 said:
Awesome, I just got my new sensation yesterday. Worked like a charm.
Click to expand...
Click to collapse
Oh and thanks lol
So i was running cm10 and i wanted to install a kernel. I when to install and kernel via rom manager.. When i tried to install in the screen went black and i havent been able to get the phone to turn on since,,,, i noticed when i try to put the phone into dload mode nothing happens... When i plug the phone into the wall charger the led light turns on as if it was charging but i dont have the battery in.. If i put the battery in and i push the volume down home and power nothing happens...can someone please help??? Please!!!!!!!!! I think the kernel was something like k74 something like that...
If you arent able to get into download mode, or even get a vibrate out of the phone, then sadly it may be hard bricked. I don't understand how flashing a kernel could hard brick the phone, though. At any rate, worst case scenario is you will have to send the unit in for a JTAG repair if you are unable to get it to boot in any way.
bakerboy81 said:
So i was running cm10 and i wanted to install a kernel. I when to install and kernel via rom manager.. When i tried to install in the screen went black and i havent been able to get the phone to turn on since,,,, i noticed when i try to put the phone into dload mode nothing happens... When i plug the phone into the wall charger the led light turns on as if it was charging but i dont have the battery in.. If i put the battery in and i push the volume down home and power nothing happens...can someone please help??? Please!!!!!!!!! I think the kernel was something like k74 something like that...
Click to expand...
Click to collapse
Welcome to AOKP/CM. lol Wouldn't use rom manager myself but hold on a few and Droidstyle or Annoying duck should chime in soon. I don't remember how bricked that means. Maybe able to leave battery out awhile and get it back.
apacseven said:
If you arent able to get into download mode, or even get a vibrate out of the phone, then sadly it may be hard bricked. I don't understand how flashing a kernel could hard brick the phone, though. At any rate, worst case scenario is you will have to send the unit in for a JTAG repair if you are unable to get it to boot in any way.
Click to expand...
Click to collapse
i have never heard of jtag... can you give me more info just in case
JTAG is the only way to recover from a hard brick. It is a service that is performed by only one (or maybe a few) companies in the world for the S3 (and many many other devices). Heres a link to the service, which starts at $60, and a link to the video of the S3 being unbricked.
https://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
https://www.youtube.com/watch?v=XnA8Djs55Ds&feature=player_embedded
Try leaving the device plugged into the charger for a hour or so then try to get into odin mode...if still nothing then it sounds like you flashed a kernel that was for the international s3.
bakerboy81 said:
So i was running cm10 and i wanted to install a kernel. I when to install and kernel via rom manager.. When i tried to install in the screen went black and i havent been able to get the phone to turn on since,,,, i noticed when i try to put the phone into dload mode nothing happens... When i plug the phone into the wall charger the led light turns on as if it was charging but i dont have the battery in.. If i put the battery in and i push the volume down home and power nothing happens...can someone please help??? Please!!!!!!!!! I think the kernel was something like k74 something like that...
Click to expand...
Click to collapse
Did you install the 10/14 nightly? I noticed that when I installed the 10/14 nightly and then installed leankernel over that my phone would no longer boot. A simple flash back to M2 and leankernel fixed the issue. 10/14 had a lot of kernel updates so I think that's the problem.
VolUp+Home+Power to boot back into recovery I believe.
Do all of your flashing manually in the future. ROM Manager = no.
Sent from my SCH-I535 using Tapatalk 2
Anayalata said:
Did you install the 10/14 nightly? I noticed that when I installed the 10/14 nightly and then installed leankernel over that my phone would no longer boot. A simple flash back to M2 and leankernel fixed the issue. 10/14 had a lot of kernel updates so I think that's the problem.
VolUp+Home+Power to boot back into recovery I believe.
Click to expand...
Click to collapse
Since his phone wont even power on it will be impossible to flash another ROM.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thanks
FNM
bakerboy81 said:
So i was running cm10 and i wanted to install a kernel. I when to install and kernel via rom manager.. When i tried to install in the screen went black and i havent been able to get the phone to turn on since,,,, i noticed when i try to put the phone into dload mode nothing happens... When i plug the phone into the wall charger the led light turns on as if it was charging but i dont have the battery in.. If i put the battery in and i push the volume down home and power nothing happens...can someone please help??? Please!!!!!!!!! I think the kernel was something like k74 something like that...
Click to expand...
Click to collapse
Delete please
Sent from my PC36100 using Tapatalk 2
I am so sad as I write this...:crying:
I had TWRP custom recovery and running the ARHD 9.0 rom.
I was tempted to try the other roms so I played around with Omega and ReVolt rom..they worked fine...
Then, when I tried to reflash ARHD 9.0, I could get to TWRP recovery but it just reboots even before any of the buttons appear.
So, I went into download mode and flashed HighOnAndroid custom recovery.
It seem to work fine....so I went ahead and flashed ARHD 9.0....It installed fine and completed successfully.
But when I rebooted the device...sigh...no power, not even the charging animation when I plug it into the charger...
So, if anyone has a solution on what I should do, please do tell me or I am really sad...so so sad...:crying:
Try a different charger, cable and wall outlet. Leave the n8000 there for a while. Hold the power button for a while, then let it go. Listen closely to the speakers for the little samsung sound when it turns on. Idk if the rom you installed has a boot sound tho. Anyways, if you still dont have an answer after that.. I would maybe start to think the power button is dead. Its a last ditch option but plausible i suppose lol.
Beyond that, you might have to think about sell it for parts.
Oh and i remember from my time with the Samsung vibrant that sometimes, even if nothing comes up on the screen, the device might be picked up by Odin after doing the dl mode button combo
Sent from my Nexus 4 using xda app-developers app
younix258 said:
Try a different charger, cable and wall outlet. Leave the n8000 there for a while.
Click to expand...
Click to collapse
I brought a friend's Note and charged using my usb charger/cable...it is working ok.
I would maybe start to think the power button is dead. Its a last ditch option but plausible i suppose lol.
Beyond that, you might have to think about sell it for parts.
Click to expand...
Click to collapse
My Note is about 2 months old and is still under warranty period. As a last resort, I can send it to them.
Oh and i remember from my time with the Samsung vibrant that sometimes, even if nothing comes up on the screen, the device might be picked up by Odin after doing the dl mode button combo
Click to expand...
Click to collapse
I will try and post back here.
Thanks for sharing your thoughts though.
freelancer81 said:
I brought a friend's Note and charged using my usb charger/cable...it is working ok.
My Note is about 2 months old and is still under warranty period. As a last resort, I can send it to them.
As you have root and custom rom then warranty is void .
If Samsung cannot tell that you have root and custom rom is a different matter .
Click to expand...
Click to collapse
Have you tried plugging in to your pc, see if odin recognizes it? If so try flashing stock samsung rom.
Sent from my GT-N8013 using XDA Premium App
rail205 said:
Have you tried plugging in to your pc, see if odin recognizes it? If so try flashing stock samsung rom.
Click to expand...
Click to collapse
I tried it....not detected...
It's very strange...no backlit or sound even when pressing power, power+vol up/vol down combos.
There was no error at all while flashing the ARHD 9.0.....and when I click on the finish and restart/reboot button at the end, boom..it shutdowns and dies on me...
I have googled it but no one has ever come across this kind of problem.
Since it is completely dead, there is a chance that sammy will not know it's rooted and running custom firmware.
Thanks to you and JJEgan for your concerns and suggestions.
As it sounds like a hardware issue, Samsung will likely fix it under warranty. At least that was my experience with Asus on my previous tablet.
Sent from my Vivid 4G using xda app-developers app
Do you know.if your battery was almost dead when flashing that last. Rom? I've heard that can brick ur device if it dies in flashing process. (Even tho you said flash completed) but who knows?
trevor7428 said:
Do you know.if your battery was almost dead when flashing that last. Rom? I've heard that can brick ur device if it dies in flashing process. (Even tho you said flash completed) but who knows?
Click to expand...
Click to collapse
I am not very sure about the exact battery percentage but yeah, it was low...somewhere about 10%~30%.
So, does that mean there is no way to revive it?
:crying:
freelancer81 said:
I am not very sure about the exact battery percentage but yeah, it was low...somewhere about 10%~30%.
So, does that mean there is no way to revive it?
:crying:
Click to expand...
Click to collapse
Unfortunately not without a new motherboard it seems like. If the is no sign of life, no recovery, no download mode and can't flash via oden or kies on computer with proper drivers installed. Then it sounds like a hard brick. Not recoverable unless new motherboard or JTAG. :/
Sorry man. But in future never flash if less than 30% battory. I've heard some pple say not below 50%
I don't know if your 10.1 died while flashing, but if so it could hard brick
50% is the suggested level of battery because flashing actually uses a large amount of battery. Also the tablets seem to power down things at 10%power.
Could be it shut off if the power dropped below 10%. This is why we suggest to not flash below 50%...
trevor7428 said:
Unfortunately not without a new motherboard it seems like. If the is no sign of life, no recovery, no download mode and can't flash via oden or kies on computer with proper drivers installed. Then it sounds like a hard brick. Not recoverable unless new motherboard or JTAG. :/
Sorry man. But in future never flash if less than 30% battory. I've heard some pple say not below 50%
I don't know if your 10.1 died while flashing, but if so it could hard brick
Click to expand...
Click to collapse
ultramag69 said:
50% is the suggested level of battery because flashing actually uses a large amount of battery. Also the tablets seem to power down things at 10%power.
Could be it shut off if the power dropped below 10%. This is why we suggest to not flash below 50%...
Click to expand...
Click to collapse
so sad....lesson learnt too late....the hard way :crying:
But I guess I have learnt one more way of hardbricking a device.
dude, seems like maybe a problem with your "main board"... i had the same issue at my galaxy tab 2, and i sent it to the shop ( because its passed warranty period already)...
Hi.
This phone was working perfectly and I left it to go away to another country so it must have discharged it's battery.
When I got back it would not turn on. Even after charging for a day, it will not turn on.
When I have the charging cable connected, it goes to Google Logo Screen and it loops (restarts over and over again)
There is no error message.
Picture is attached so please let me know what to do. It was a gift so no receipt to claim warranty.
Thanks for any help in advance.
joongpark said:
Hi.
This phone was working perfectly and I left it to go away to another country so it must have discharged it's battery.
When I got back it would not turn on. Even after charging for a day, it will not turn on.
When I have the charging cable connected, it goes to Google Logo Screen and it loops (restarts over and over again)
There is no error message.
Picture is attached so please let me know what to do. It was a gift so no receipt to claim warranty.
Thanks for any help in advance.
Click to expand...
Click to collapse
Try booting into stock recovery and clearing cache, reboot.
If that doesn't work then you'll have to unlock the bootloader (which wipes data) and try flashing the factory images. A guide for that can be found in the first link of my signature.
Lethargy said:
Try booting into stock recovery and clearing cache, reboot.
If that doesn't work then you'll have to unlock the bootloader (which wipes data) and try flashing the factory images. A guide for that can be found in the first link of my signature.
Click to expand...
Click to collapse
Thanks for the help...I am not sure If I am able to get into recovery more. Last time I tried, I was not able to.
Let you know once I try it.
Thanks.
Lethargy said:
Try booting into stock recovery and clearing cache, reboot.
If that doesn't work then you'll have to unlock the bootloader (which wipes data) and try flashing the factory images. A guide for that can be found in the first link of my signature.
Click to expand...
Click to collapse
I just tested and I am not able to get into recovery more...I am not sure what that mean. Should I connect Nexus to computer and see if it's recognized by computer and try to reload stock ROM?
Phone was never unlocked or flashed...it was in the same state as it was bought.
Can this be hardware problem? I saw some reports of similar thing happening with power button problem or other hardware problems.
joongpark said:
I just tested and I am not able to get into recovery more...I am not sure what that mean. Should I connect Nexus to computer and see if it's recognized by computer and try to reload stock ROM?
Phone was never unlocked or flashed...it was in the same state as it was bought.
Can this be hardware problem? I saw some reports of similar thing happening with power button problem or other hardware problems.
Click to expand...
Click to collapse
did you go into the bootloader, choose recovery, and it went to an android laying on its back?
This is the weirdest things...Spent days and days trying to bring it back to life and it would just reboot after GOOGLE logo. There was no way to get into recovery more.
I was looking around and someone said that tapping hard behind the power button with finger might bring it back and it did...so crazy. No matter what, I am a happy camper.
If you have tried everything, just try it...it behind power button and it might wake up the android that's been sleeping.
joongpark said:
This is the weirdest things...Spent days and days trying to bring it back to life and it would just reboot after GOOGLE logo. There was no way to get into recovery more.
I was looking around and someone said that tapping hard behind the power button with finger might bring it back and it did...so crazy. No matter what, I am a happy camper.
If you have tried everything, just try it...it behind power button and it might wake up the android that's been sleeping.
Click to expand...
Click to collapse
Can u explain how did u do that .what do u mean by behind the power button
I have the option to buy this device from a guy who has this problem and i have said to him to try the tips but not working. Computer does not see the device yet and thats logic since it just goes for 2-3 sec in bootloader he told me. Is this the power buttion failure or can it be fixed with nexus toolkit?
Price is €50 because of that and little damaged glass but i doubt if i can let it boot normal again.
Hi all,
Did a factory data reset with a rooted, bootloader unlocked XT925 on stock jb and now its bricked. I can't access recovery, and when I do the simulated battery pull by pressing both volume keys and power button, it shows the moto dual core screen, before going to the android with the blue bar underneath usually seen while updating for about 30 seconds before briefly flashing the android on its side with the red triangular warning sign above it, then it powers off.
Is there anything I can do to save it? I had modified the start up animation which I think may be causing it. It won't even show up when plugged into my computer.
Thanks
Hi there :
At this point, can you get your xt925 on fastboot mode by pressing volume up and power while it is off? if so, you can just go ahead and flash a 4.1.2 rom. Since your BL is unlocked you can download one from any region that suits you.
hbenz2008 said:
Hi there :
At this point, can you get your xt925 on fastboot mode by pressing volume up and power while it is off? if so, you can just go ahead and flash a 4.1.2 rom. Since your BL is unlocked you can download one from any region that suits you.
Click to expand...
Click to collapse
Can't get into fastboot
aamd11 said:
Can't get into fastboot
Click to expand...
Click to collapse
With power + volume up you can't get to fastboot?
aamd11 said:
Can't get into fastboot
Click to expand...
Click to collapse
i have seen an unusual trend of hard bricks coming from fdr's recently. i cant begin to explain it, or offer a fix for it.
unfortunately from what you have described, your phone seems to be gone.
i can only suggest that anyone having issues with there phone, that they think a fdr would fix, dont do it!! re-flash with rsd instead until we determine what is causing this.
i know its not wide spread, but i wouldnt risk it just the same.
Sad Panda said:
With power + volume up you can't get to fastboot?
Click to expand...
Click to collapse
i got same problem. but when i get on fastboot and i start flashing my backup stock rom, it fails...
what can it be?
bweN diorD said:
i have seen an unusual trend of hard bricks coming from fdr's recently. i cant begin to explain it, or offer a fix for it.
unfortunately from what you have described, your phone seems to be gone.
i can only suggest that anyone having issues with there phone, that they think a fdr would fix, dont do it!! re-flash with rsd instead until we determine what is causing this.
i know its not wide spread, but i wouldnt risk it just the same.
Click to expand...
Click to collapse
Sad Panda said:
With power + volume up you can't get to fastboot?
Click to expand...
Click to collapse
Nope fastboot is inaccessible. Oh well! Sad this happened just before I updated to the loooong awaited KK build as well. Luckily I found a Sony Xperia Z1 for a great price so off to new things (and new subsection of XDA).
Thanks for the replies everyone!
on the other hand Xperia is a good unit