Database Info

[HELP] my sensation won't turn on

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

Motorola Backflip wont boot or either charge

Hi.
I found my old Backflip yesterday and decided to use it as a bluetoot-keyboard. Since the original ROM was so out of date, I decided to flash a bootloader and flash CM. So I flashed the recovery, flashed CM. Rebooted, phone started booting, but as soon as it was showing "ANDROID" on the screen, it went off and started over. I was able to get back to the recovery, so I wiped it again and flashed CM again, same. Now it's even worse: The battery is dead, the phone can't power up by itself, only works with the wall-adapter. Even hooked up to my computer, only the light around the port flashes up.
Can someone help me pls?
Cheers!

Jukpulfer said:
Hi.
I found my old Backflip yesterday and decided to use it as a bluetoot-keyboard. Since the original ROM was so out of date, I decided to flash a bootloader and flash CM. So I flashed the recovery, flashed CM. Rebooted, phone started booting, but as soon as it was showing "ANDROID" on the screen, it went off and started over. I was able to get back to the recovery, so I wiped it again and flashed CM again, same. Now it's even worse: The battery is dead, the phone can't power up by itself, only works with the wall-adapter. Even hooked up to my computer, only the light around the port flashes up.
Can someone help me pls?
Cheers!
Click to expand...
Click to collapse
I think that the battery is faulty......
Try using the battery with another mobile

eatsleep said:
I think that the battery is faulty......
Try using the battery with another mobile
Click to expand...
Click to collapse
I agree with him it sounds like your battery has issues. Although it could be somewhere in the flashing something went wrong. (doubt it)

Constant rebooting

I have the cricket model. Sometime last night my phone started rebooting on every ROM and kernel. Nothing I do will get it to stop. It doesn't happen in TWRP and that's it. I thought maybe it was a battery issue as I haven't been able to fully charge it because of this issue but that's not helping either. I've been trying to use the upgrade tool but in this state the computer never even recognizes the phone and I can't even get that far, plus it reboots even when in download mode. I'm about to call cricket and see if they can just send me a new one since I've only had it a week but is there anything I can do? Does anyone have a boot IMG for complete stock 60450 ?!? EDIT: Got the tool to recognize phone and start process but what do ya know phone reboots even deep into download mode. It just always wants to restart to the system for some reason, except for when on twrp. UPDATE:EDIT: Turns out the reason the upgrade app wasn't working is because i didn't have enough space for the update to download on the PC . I didn't realize because the app never stated why it was restarting my phone or disconnecting so I just assumed it was related to why my phone kept restarting on all ROMs. Wow lol I feel so damn stupid for not thinking of this 2 days ago. Its installing now and hopefully this fixes my reboot issues. Thanks to everybody here for helping and answering my 1000 question's on every post. Really appreciate it.

it looks like motherboard is gone. I hope you can return it when you have custom rom installed.

DallasCZ said:
it looks like motherboard is gone. I hope you can return it when you have custom rom installed.
Click to expand...
Click to collapse
I've had the phone for one week lol. Motherboard is gone? Could something be messed up in build prop somewhere? I did try to use a DPI changer app on stock rom once or maybe xposed? I've done a lot of flashing since I got it trying to find the perfect setup. I just noticed that the USB cable it came with is crap so now that I'm using a different one I'm hoping that low discalobrated battery was the issue. Charging it up proper and gonna see what happens after. Also for some strange reason the Flyme OS ROM is the only one that doesent seem to want to restart as often. It still does but it lasts a lot longer before doing so , why idk lol.

turn off the phone, charge it fully and then run the upgrade tool to go back to stock.
Odesláno z mého 6045X pomocí Tapatalk

DallasCZ said:
turn off the phone, charge it fully and then run the upgrade tool to go back to stock.
Odesláno z mého 6045X pomocí Tapatalk
Click to expand...
Click to collapse
I wasnt previously able to corectly charge becauss when i would turn the phone off to charge it wpuld power up instead of gking to the charging acreen. I think the USB cable that came with the phone might have been faulty and I just didn't notice it somehow. Now that I've charged the phone to 50% Flyme is up and running without a reboot, although running quite hot....which could also be the issue. Maybe the metal on the USB tip got toasted. That would explain my reboots in download mode but it doesent explain why the phone never once rebooted on me while in twrp and why it would reboot even while not being charged and had like 30%. Gonna charge it up to 100 and try the tool again.

carnivalrejectq said:
I wasnt previously able to corectly charge becauss when i would turn the phone off to charge it wpuld power up instead of gking to the charging acreen. I think the USB cable that came with the phone might have been faulty and I just didn't notice it somehow. Now that I've charged the phone to 50% Flyme is up and running without a reboot, although running quite hot....which could also be the issue. Maybe the metal on the USB tip got toasted. That would explain my reboots in download mode but it doesent explain why the phone never once rebooted on me while in twrp and why it would reboot even while not being charged and had like 30%. Gonna charge it up to 100 and try the tool again.
Click to expand...
Click to collapse
if you can boot to flyme, and got no reboots in TWRP i suggest you flash from TWRP your previously mad ebackup..if you dont have any, just flash stock kernel or look here in threads, there was a thread and it contains TWRP backup of stock rom..if you find TWRP backup of your STOCK 6045O then flash it from TWRP, and if you dont observe nay reboots, it was due to the kernel. IF it still reboots send it to warranty repair.

DallasCZ said:
if you can boot to flyme, and got no reboots in TWRP i suggest you flash from TWRP your previously mad ebackup..if you dont have any, just flash stock kernel or look here in threads, there was a thread and it contains TWRP backup of stock rom..if you find TWRP backup of your STOCK 6045O then flash it from TWRP, and if you dont observe nay reboots, it was due to the kernel. IF it still reboots send it to warranty repair.
Click to expand...
Click to collapse
Well I'm back on CM now with no reboots. I guess my USB cable just sucked and my battery calibration was off so the battery was showing more than it actually had and probably causing instability. However, I still can't get the tool to work. It just reboots at around 22% exiting me out of download mode. BTW I've searched and scowled almost every thread and I can't find a stock kernel. There's the arde one but I thought that was just his custom kernel for stock. And the twrp back up I definitely can't find. I seen the thread but there was no link.

carnivalrejectq said:
Well I'm back on CM now with no reboots. I guess my USB cable just sucked and my battery calibration was off so the battery was showing more than it actually had and probably causing instability. However, I still can't get the tool to work. It just reboots at around 22% exiting me out of download mode. BTW I've searched and scowled almost every thread and I can't find a stock kernel. There's the arde one but I thought that was just his custom kernel for stock. And the twrp back up I definitely can't find. I seen the thread but there was no link.
Click to expand...
Click to collapse
If it was the USB cable why is mobile upgrade tool rebooting the device at 22%? It makes no sense. It could be the pins on the usb socket on the phone or i dont know.
You should ask someone with the 6045O device to send you the boot.img (aka kernel) of stock 6045O.

DallasCZ said:
If it was the USB cable why is mobile upgrade tool rebooting the device at 22%? It makes no sense. It could be the pins on the usb socket on the phone or i dont know.
You should ask someone with the 6045O device to send you the boot.img (aka kernel) of stock 6045O.
Click to expand...
Click to collapse
Well I first noticed my cable was funky when I loaded up Flyme it kept making an unplug sound and I thought it was just the ROM glitching out but I changed the cable and it stopped. About the tool......I have a Windows tablet that it's only USB connection is one of those mini USB to full adapters and it's a little loose. I have zero problems with it plugging my phone into it for file transfer or for adb, it's all fine there so idk why it would be causing an issue with the tool, last time I tried it k specifically made sure all connections were sturdy and didn't move the whole time and it still rebooted. I noticed somebody in one of the threads said his device did the same thing though and that's why he couldn't use the tool as well......nobody ever replied to him lol

Ahh I spoke to soon. Restored my stock, because that's what I prefer for even at OC it still doesent make the phone nearly as hot as CM ROMs and the restarts came right back even with a decent charged battery. I'm back on CM again though and its not happening. Doesent make much sense because before the restarts were happening across all ROMs. It can't be the kernel in my stock restore as I had used it a bunch of times before with no issues...... Though it is saved on my external SD..... But so is the cm build I'm using. Idk whats going on here. Just wanna return the phone to full stock and call it a day lol. Edit: spoke to soon again lol. There goes CM rebooting, although it took way longer than stock to do so.

My Mi4c only works when charging

After my phone bricked I installed latest Chinese Stable ROM in EDL mode. I chose EDL mode for two reasons (1. I suspected that the phone only works while plugged in to charge and 2. the EDL mode turns off the phone after flashing so I can plug in the charger before booting). Turns out I was right. After the flash was over I tried to boot it without charging it first and it didn't work. After I connected it to the charger it booted normally and the ROM installed successfully.
I tried it again this morning after it fully charged. Few seconds after Ii disconnected it, it turned off. When I tried to turn it back on it was just rebooting to the MI logo screen. I plugged it in the charger and it rebooted 2 times (both times it got to those three dots at the bottom of the screen) and the third time it booted normally.
I also just noticed that the phone is curved a bit (maybe less than 1mm difference between upper left edge and rest of them), maybe from wearing it in tight pockets or something like that.

I think your battery might be dead. Try checking the voltage or the quality.
Replaceable batteries are pretty cheap.
Trimis de pe al meu Mi-4c folosind Tapatalk

Might be faulty battery, might be bad kernel, might be anything. Best way to check is to try to flash latest dev china rom via fastboot, if it still doesn't work try flashing stable 5.1.1 rom, again, via fastboot. If none of the solutions above doesnt work might be bad battery or worse, the controller on mobo died.

timipisoboy said:
Might be faulty battery, might be bad kernel, might be anything. Best way to check is to try to flash latest dev china rom via fastboot, if it still doesn't work try flashing stable 5.1.1 rom, again, via fastboot. If none of the solutions above doesnt work might be bad battery or worse, the controller on mobo died.
Click to expand...
Click to collapse
Well I hope it's a battery, because I just bought one to replace it. What is that mobo controller? Is it replaceable?

I have the same issue,
Battery replacement and stock rom of android 7 didn't help
I'm afraid is another hardware issue /:

I do have a similar problem, flashed xiaomi.eu and something have been broken.
I dont know how and why but its very strange.
Unplugged from supply i can boot up the phone, can see the miui logo and boot into fastboot but NOT into recovery and not boot up os.
As soon as i plug in supply it works quit normally, can boot up everything seems to be working, booting into twrp and flashing rom. No problem at all.
If i unplug while running os it imediately shut down.
The battery bar inside twrp show strange jumps.
What happens did somehting break ? Id like to gift the phone my mother for christmas.

Danny94 said:
I do have a similar problem, flashed xiaomi.eu and something have been broken.
I dont know how and why but its very strange.
Unplugged from supply i can boot up the phone, can see the miui logo and boot into fastboot but NOT into recovery and not boot up os.
As soon as i plug in supply it works quit normally, can boot up everything seems to be working, booting into twrp and flashing rom. No problem at all.
If i unplug while running os it imediately shut down.
The battery bar inside twrp show strange jumps.
What happens did somehting break ? Id like to gift the phone my mother for christmas.
Click to expand...
Click to collapse
Hi how did you resolved this. Facing same problem. Will replacing battery solve this.

visharagp said:
Hi how did you resolved this. Facing same problem. Will replacing battery solve this.
Click to expand...
Click to collapse
I purchased a new battery and it was working normally again and still working.

Danny94 said:
I purchased a new battery and it was working normally again and still working.
Click to expand...
Click to collapse
Great then I have to purchase a new battery ss well

A51 stuck in TWRP bootloop

Today, I flashed the latest firmware onto my phone, it had a few boot issues but I managed to finish.
Then I noticed that (I KNOW I AM DUMB) forgot to backup the data in my internal storage as well...
Now I tried flashing TWRP because I noticed the internal storage shows up as ~4GB, which is about as much as I had free space left before flashing.
Problem: my phone is now stuck in a TWRP splash screen bootloop and doesn't want to reboot anywhere else.
I used the exact same TWRP ROM I had previously used on Android 11 and it worked perfectly fine (ROM: https://forum.xda-developers.com/t/...-sm-a515f-one-ui-3-0-dub1-android-11.4231543/)
Now I can't get out of TWRP anymore (not even into download mode or anything) and all my hope is pretty much lost.
Do I need to wait for the battery to fully drain? Would it still be possible to recover the data from the internal storage (since it wasn't encrypted and appears to still be there?)
Thank you in advance to anyone willing to help!

For the record; I got it out. Still pretty stuck fixing the OS, I gave up on the data since it wasnt too important anyways

The same issue

rooot_ said:
For the record; I got it out. Still pretty stuck fixing the OS, I gave up on the data since it wasnt too important anyways
Click to expand...
Click to collapse
how did you remove the bootloop?

kabelknabbelaar said:
how did you remove the bootloop?
Click to expand...
Click to collapse
Drain the battery than go to download mode with pc. Than flash it with firmware. You can find firmware on galaxyfirmware.com

kabelknabbelaar said:
how did you remove the bootloop?
Click to expand...
Click to collapse
The battery, let it drain or force restart to download mode and flash the whole firmware.

aljustiet said:
Drain the battery than go to download mode with pc. Than flash it with firmware. You can find firmware on galaxyfirmware.com
Click to expand...
Click to collapse
Yes, I let the battery fully drain - my trick to get into Download Mode was to hold Power + Volume Up once the battery drained and then connecting the charging cable connected to a computer while holding down the buttons
Then flash stock FW