Issue with Sony Xperia M4A4 Aqua (E2303) - General Questions and Answers

Hello guys!
Yesterday I wanted to root my phone following these instructions (sorry link can't be posted dues to I'm just a newbie here) but post was on dottech dot org.
I did everything that was necessary for preparing the phone, however I stucked at step 8.
I flashed the original .128 firmware to my phone, and when I powered it on, I was delighted. When I realized that it won't boot at all, I got an idea, simply to wait. I waited over 20 minutes, nothing happened, stuck on T-mobile logo. For the rest of the time I left it on charger, and unfortunately I am unable to power it off since it has built-in battery.... I tried to power off by long pressing power button, nothing happened. I tried again to flash it, but when it asks me to plug the phone to the usb in case to get in flashmode, it says battery has to charge, so it's discharged... I plug it to charger one more time, but as soon as it gets enough power, it tries to start itself, and I can't power it off...
It gets really hot at the back panel, and as it discharges, everything is happening again....
Please help me to get back my phone working!
Any help would be much appreciated!
Thanks
(Sorry, it's M4 Aqua actually)

pistiC said:
Hello guys!
Yesterday I wanted to root my phone following these instructions (sorry link can't be posted dues to I'm just a newbie here) but post was on dottech dot org.
I did everything that was necessary for preparing the phone, however I stucked at step 8.
I flashed the original .128 firmware to my phone, and when I powered it on, I was delighted. When I realized that it won't boot at all, I got an idea, simply to wait. I waited over 20 minutes, nothing happened, stuck on T-mobile logo. For the rest of the time I left it on charger, and unfortunately I am unable to power it off since it has built-in battery.... I tried to power off by long pressing power button, nothing happened. I tried again to flash it, but when it asks me to plug the phone to the usb in case to get in flashmode, it says battery has to charge, so it's discharged... I plug it to charger one more time, but as soon as it gets enough power, it tries to start itself, and I can't power it off...
It gets really hot at the back panel, and as it discharges, everything is happening again....
Please help me to get back my phone working!
Any help would be much appreciated!
Thanks
(Sorry, it's M4 Aqua actually)
Click to expand...
Click to collapse
EDIT: I am able to flash kernels to phone if I let it charge for about 10 minutes then enter flashmode and I keep pressing volume down + power for about 5 minutes (as it would start itself.) BUT still doesn't boot up. Freezes at the T-mobile logo. Please help.

Get your phone's box then search it's model on Google for firmwares that you can flash through fastboot etc

Related

Constant boot loop - can't even get download mode

I have a rooted stock phone that stopped working for no apparent reason (no new ROM flashed, no configuration change). It starts, shows the Samsung logo, and immediately reboots. I tried to put it in download mode, when i hold the 3 keys I see the download logo showing up, but it reboots after a few seconds anyway. after a while it will start looping through the battery charge screen (which shows the battery as empty). I tried 2 different batteries with no change. Any idea how to get something working again?
That almost sounds like some sort of power issue. Have you left it sit turned off until the battery was full?
Yes, I left it overnight and it just keeps flashing the battery screen and then resets. I also have an external charger and used it to charge the battery, so it's not an issue with the battery actually being empty.
Have you been able to get the phone into download mode previously?
Have you have dealt with a boot loop and performed an Odin recovery previously? If not, remember it can take a few tries to get download mode to pop up.
If you can't get Odin to go, you might try flashing with Kies.
I am wondering if your phone met with some kind of disaster when you weren't around (trauma or liquid).
anyone747 said:
I have a rooted stock phone that stopped working for no apparent reason (no new ROM flashed, no configuration change). It starts, shows the Samsung logo, and immediately reboots. I tried to put it in download mode, when i hold the 3 keys I see the download logo showing up, but it reboots after a few seconds anyway. after a while it will start looping through the battery charge screen (which shows the battery as empty). I tried 2 different batteries with no change. Any idea how to get something working again?
Click to expand...
Click to collapse
This sounds almost exactly like the problem I had with my Sidekick. In my case, it turned out to be a bad battery and a loose ribbon cable on the motherboard. I'd check those two things.
This happened to me as well, and the three-button method to get into download mode wasn't working. For some odd reason, for me to get into download mode all I have to do is hold down the power button + track pad, and it goes right into download mode... Maybe slightly different model?
Try that - power button + trackpad
Bootloops.
Not a guaranteed fix by any means but for troubleshooting purposes you may want to consider making a USB JIG. It will most definitely help you figure out just how serious the problem is and if it IS software related with a way to get it working again you will need the JIG anyway so its worth a shot. If nothing else you learn a new skill and you're the proud owner of an incredibly useful tool that you can say you made yourself. good luck!
I know this post is kind of old, but it just happened to me last week (same circumstance, a rooted phone, but stock). I ended up just pulling the battery out and pressing the power button a couple times to hopefully drian it and letting it sit for 15 minutes, and then I put the battery back in and it worked again. I now have another rom flashed on it, I hate stock.
I know this forum is ancient, but I'm working on an E-Bay phone with this exact issue. I found the following thread the most useful and informative on the problem:
http://forum.xda-developers.com/showthread.php?t=1996709
Hopefully this helps other.
what i did was hold the power volume and button between the menu n back with the left hand YES HOLD IT UNTILL THE PIT IS UPLOADED. then u can let go then slide in the vattery with the right.while checking off the flash bootloarders on the heimdall with it fixing my phone XD
I had this happen, I dissassembled the phone, and used an alcohol pad to clean the power button area, and manipulated the button a lot, let it dry, reassembled...it still bootlooped.
BELOW IS RISKY BUT WORKED FOR ME
So while the back cover was off (exposing the cicuit board but everything still connected) I inserted the battery and watched it boot loop...during this, I used a flathead screw driver to "short" the power button pins...this let it boot fully, and it has been fine since.
i smacked the phones power button a few times and it worked

[Q] Htc Sensation XE half-dead. Please help.

Hey guys, it's been a long time since i don't post anything here. I've recently bought a very cheap used Htc Sensation XE. But he came to me with this issues:
- It doesn't turn on.
- My notebook doesn't recognize it, when I connect it with a USB cable.
- When I connect it to the charger a orange led turned on, stood turned on for a few seconds, then turned off. Stood turned off for a few seconds the turned on again. This went on and on for a while, until the phone vibrated, then nothing else happened. If I remove the charger then put it back on, the process will repeat itself.
Has anyone been through this? I really need some help.
Thank you all for the attention!
Perfect friend, now just wait, the staff is very good here.
will.mack said:
Hey guys, it's been a long time since i don't post anything here. I've recently bought a very cheap used Htc Sensation XE. But he came to me with this issues:
- It doesn't turn on.
- My notebook doesn't recognize it, when I connect it with a USB cable.
- When I connect it to the charger a orange led turned on, stood turned on for a few seconds, then turned off. Stood turned off for a few seconds the turned on again. This went on and on for a while, until the phone vibrated, then nothing else happened. If I remove the charger then put it back on, the process will repeat itself.
Has anyone been through this? I really need some help.
Thank you all for the attention!
Click to expand...
Click to collapse
Okay. How long have you tried leaving the phone on charge?
Have you tried booting to bootlaoder?
Hold down Volume down + Power button.
If the bootloader screen is accessible, can we please know what it says?
I think he does not have access to the bootloader ...
kgs1992 said:
Okay. How long have you tried leaving the phone on charge?
Have you tried booting to bootlaoder?
Hold down Volume down + Power button.
If the bootloader screen is accessible, can we please know what it says?
Click to expand...
Click to collapse
The last time it stood 30 minutes on charge. I've tried booting into bootloader but it doesn't work. The phone won't even vibrate to indicate it is turning on
will.mack said:
The last time it stood 30 minutes on charge. I've tried booting into bootloader but it doesn't work. The phone won't even vibrate to indicate it is turning on
Click to expand...
Click to collapse
Check if that battery is a tight fit. If not, try putting in a piece of paper (like a business card) on the edge opposite to battery contacts.
Also, have you tried a different battery?
Get these drivers, install them and restart your PC.
http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
Then try connecting your phone to the PC.
Solved? But how?
In the exact same problem. Is your problem solved? In that case, how was it solved? I know it's an old thread, but seems the only hope. Someone please help!

[Q] device bricked through normal operation?

HTC One M8, S-Off, Skyfall latest on 4.4.4, stock kernel, TWRP 2.8.1.0. Have been running Skyfall latest since a few days after its release, and TWRP 2.8.1.0 similarly. No problems to report so far.
I was using my phone today as one would, browsing Facebook through the app, and my phone freezes. Screen goes black, power off. Phone was probably at 80-85% battery when this happened.
I am no stranger to freezes and hard reboots, so I expected the phone to come back up shortly after this. It did not.
Tried to reboot via ADB. Couldn't detect the device.
Tried to reboot into recovery by holding Vol Down and Power. No response.
Tried to reboot into a soft reset by holding Vol Up and Power. No response.
Tried to force a battery recalibration by plugging in the phone to a charger* and holding Vol Up, Vol Down, and Power for two minutes. No response. (*the charger was not the stock HTC charger, as I don't presently have access to that, but was rather a generic charger rated for [email protected])
Somehow, miraculously, after leaving the phone plugged in for a few minutes more and fumbling a bit with (I think) the Power and Vol Up, the phone powered on, rebooted twice, and then entered the OS normally. Was stable for what seemed like about 5 minutes. After receiving a few text messages and in the middle of responding to one, it froze and powered off as before.
Last system-level tweaking that I did was to accept the latest SuperSU upgrade a few days ago. That needed to reboot into recovery, install a zip, and reboot again. All appeared to work correctly, and phone booted back up afterwards without issue. Appeared to be stable until today. I'm not blaming the SuperSU update just yet, and it seems an unlikely culprit given that the phone booted back up without issue and was stable for several days following.
Thoughts? Would greatly appreciate any troubleshooting ideas beyond these.
Update 1: After leaving it plugged in for a few minutes, I tried the battery calibration approach again. The device powered on and showed the initial boot splash (the one with the development notice in ugly red). I then released all buttons, and after a few seconds the screen went black. Would not respond afterwards. Beginning to suspect this may be a power issue.
devmage said:
HTC One M8, S-Off, Skyfall latest on 4.4.4, stock kernel, TWRP 2.8.1.0. Have been running Skyfall latest since a few days after its release, and TWRP 2.8.1.0 similarly. No problems to report so far.
I was using my phone today as one would, browsing Facebook through the app, and my phone freezes. Screen goes black, power off. Phone was probably at 80-85% battery when this happened.
I am no stranger to freezes and hard reboots, so I expected the phone to come back up shortly after this. It did not.
Tried to reboot via ADB. Couldn't detect the device.
Tried to reboot into recovery by holding Vol Down and Power. No response.
Tried to reboot into a soft reset by holding Vol Up and Power. No response.
Tried to force a battery recalibration by plugging in the phone to a charger* and holding Vol Up, Vol Down, and Power for two minutes. No response. (*the charger was not the stock HTC charger, as I don't presently have access to that, but was rather a generic charger rated for [email protected])
Somehow, miraculously, after leaving the phone plugged in for a few minutes more and fumbling a bit with (I think) the Power and Vol Up, the phone powered on, rebooted twice, and then entered the OS normally. Was stable for what seemed like about 5 minutes. After receiving a few text messages and in the middle of responding to one, it froze and powered off as before.
Last system-level tweaking that I did was to accept the latest SuperSU upgrade a few days ago. That needed to reboot into recovery, install a zip, and reboot again. All appeared to work correctly, and phone booted back up afterwards without issue. Appeared to be stable until today. I'm not blaming the SuperSU update just yet, and it seems an unlikely culprit given that the phone booted back up without issue and was stable for several days following.
Thoughts? Would greatly appreciate any troubleshooting ideas beyond these.
Update 1: After leaving it plugged in for a few minutes, I tried the battery calibration approach again. The device powered on and showed the initial boot splash (the one with the development notice in ugly red). I then released all buttons, and after a few seconds the screen went black. Would not respond afterwards. Beginning to suspect this may be a power issue.
Click to expand...
Click to collapse
Well the good news is that you aren't bricked, if the phone gives any signs of life then you are not bricked. Have you always installed SuperSu updates through recovery? I always select I believe it says "normal" and let it do it's thing and until now (knock on wood) haven't had any issues updating binaries that way. I would go back to stock and see if your problems continue or flash the previous SuperSu and see if it still happens.
devmage said:
HTC One M8, S-Off, Skyfall latest on 4.4.4, stock kernel, TWRP 2.8.1.0. Have been running Skyfall latest since a few days after its release, and TWRP 2.8.1.0 similarly. No problems to report so far.
I was using my phone today as one would, browsing Facebook through the app, and my phone freezes. Screen goes black, power off. Phone was probably at 80-85% battery when this happened.
I am no stranger to freezes and hard reboots, so I expected the phone to come back up shortly after this. It did not.
Tried to reboot via ADB. Couldn't detect the device.
Tried to reboot into recovery by holding Vol Down and Power. No response.
Tried to reboot into a soft reset by holding Vol Up and Power. No response.
Tried to force a battery recalibration by plugging in the phone to a charger* and holding Vol Up, Vol Down, and Power for two minutes. No response. (*the charger was not the stock HTC charger, as I don't presently have access to that, but was rather a generic charger rated for [email protected])
Somehow, miraculously, after leaving the phone plugged in for a few minutes more and fumbling a bit with (I think) the Power and Vol Up, the phone powered on, rebooted twice, and then entered the OS normally. Was stable for what seemed like about 5 minutes. After receiving a few text messages and in the middle of responding to one, it froze and powered off as before.
Last system-level tweaking that I did was to accept the latest SuperSU upgrade a few days ago. That needed to reboot into recovery, install a zip, and reboot again. All appeared to work correctly, and phone booted back up afterwards without issue. Appeared to be stable until today. I'm not blaming the SuperSU update just yet, and it seems an unlikely culprit given that the phone booted back up without issue and was stable for several days following.
Thoughts? Would greatly appreciate any troubleshooting ideas beyond these.
Update 1: After leaving it plugged in for a few minutes, I tried the battery calibration approach again. The device powered on and showed the initial boot splash (the one with the development notice in ugly red). I then released all buttons, and after a few seconds the screen went black. Would not respond afterwards. Beginning to suspect this may be a power issue.
Click to expand...
Click to collapse
Make sure you aren't trying to power it on while still plugged in. The charging animation bug really rears its ugly head sometimes when trying to do that.
The Stig 04 said:
Well the good news is that you aren't bricked, if the phone gives any signs of life then you are not bricked. Have you always installed SuperSu updates through recovery? I always select I believe it says "normal" and let it do it's thing and until now (knock on wood) haven't had any issues updating binaries that way. I would go back to stock and see if your problems continue or flash the previous SuperSu and see if it still happens.
Click to expand...
Click to collapse
I would love to go back to stock if I could get the device to turn on.
This was the first SuperSU update that I can remember having installed, so yes, I've always installed through recovery. The update even prompted me that, for HTC devices, better luck is had via updates through recovery.
dottat said:
Make sure you aren't trying to power it on while still plugged in. The charging animation bug really rears its ugly head sometimes when trying to do that.
Click to expand...
Click to collapse
I'm unaware of this bug. When disconnected, the device still refuses to reboot via any of the usual reboot patterns (Power, Power + Vol Up, Power + Vol Down, Power + both Vols).
devmage said:
I'm unaware of this bug. When disconnected, the device still refuses to reboot via any of the usual reboot patterns (Power, Power + Vol Up, Power + Vol Down, Power + both Vols).
Click to expand...
Click to collapse
OK. So couple more questions....
Does the power light blink for a second and then go out when you connect power or does it stay on?
What type of device does your computer see the phone as when you connect it? Please try if you have not. Watch device manager while doing so.
dottat said:
OK. So couple more questions....
Does the power light blink for a second and then go out when you connect power or does it stay on?
What type of device does your computer see the phone as when you connect it? Please try if you have not. Watch device manager while doing so.
Click to expand...
Click to collapse
Power light does not blink at all on connection. This is true both when connecting to a USB power adapter and to the computer.
My computer does not recognize a device. ADB does not report that a device is connected. Also, I use a Mac, so System Information does not report any USB device being connected. For comparison, I tried with my wife's Samsung S5, and it reported correctly in both places, so I know the cable and computer are working correctly here too.
devmage said:
Power light does not blink at all on connection. This is true both when connecting to a USB power adapter and to the computer.
My computer does not recognize a device. ADB does not report that a device is connected. Also, I use a Mac, so System Information does not report any USB device being connected. For comparison, I tried with my wife's Samsung S5, and it reported correctly in both places, so I know the cable and computer are working correctly here too.
Click to expand...
Click to collapse
Can you check dmesg on your Mac and see if you have any qualcomm devices show up near the end of the file? . Plug the phone in right before running the command.
dottat said:
Can you check dmesg on your Mac and see if you have any qualcomm devices show up near the end of the file? . Plug the phone in right before running the command.
Click to expand...
Click to collapse
Nothing from Qualcomm, nor anything related, upon plugging in the phone.
Using
Code:
sudo watch 'dmesg | tail -n 15'
(OS X requires dmesg be accessed with sudo), I saw the following come up upon plugging in the S5 mentioned before:
Code:
USBMSC Identifier (non-unique): 0x00000000 0x4e8 0x685b 0x232, 2
With the same watch in place, I saw no output at all for the M8.
devmage said:
Nothing from Qualcomm, nor anything related, upon plugging in the phone.
Using
Code:
sudo watch 'dmesg | tail -n 15'
(OS X requires dmesg be accessed with sudo), I saw the following come up upon plugging in the S5 mentioned before:
Code:
USBMSC Identifier (non-unique): 0x00000000 0x4e8 0x685b 0x232, 2
With the same watch in place, I saw no output at all for the M8.
Click to expand...
Click to collapse
I would suggest warranty route through HTC. You have got a brick.
dottat said:
I would suggest warranty route through HTC. You have got a brick.
Click to expand...
Click to collapse
That is my fear. Thank you for your help.
dottat said:
OK. So couple more questions....
Does the power light blink for a second and then go out when you connect power or does it stay on?
What type of device does your computer see the phone as when you connect it? Please try if you have not. Watch device manager while doing so.
Click to expand...
Click to collapse
Hi,
Background: Rooted, S-Off (via Sunshine), was running CleanROM (on the 444 firmware) and tried installing Vanir 444. ROM installed no problem, Gapps installed no problem, installed SuperSU 2.40 at the end and rebooted.
I've run into the exact same situation as the OP. Tried all the button combinations/adb stuff and the phone only boots to the initial white HTC screen but then goes blank. I've tried everything to get into bootloader but nothing seems to get me there. The phone vibrates when it "turns on" after the hard reset but nothing after the white HTC screen except a black screen.
I'm responding to this post in particular because my phone was/is showing the blinking power light when it's plugged in. Hopefully this is a good sign?
TIA for any help!
Matt
sigmaxaa said:
Hi,
Background: Rooted, S-Off (via Sunshine), was running CleanROM (on the 444 firmware) and tried installing Vanir 444. ROM installed no problem, Gapps installed no problem, installed SuperSU 2.40 at the end and rebooted.
I've run into the exact same situation as the OP. Tried all the button combinations/adb stuff and the phone only boots to the initial white HTC screen but then goes blank. I've tried everything to get into bootloader but nothing seems to get me there. The phone vibrates when it "turns on" after the hard reset but nothing after the white HTC screen except a black screen.
I'm responding to this post in particular because my phone was/is showing the blinking power light when it's plugged in. Hopefully this is a good sign?
Thanks TIA for any help!
Matt
Click to expand...
Click to collapse
I'm afraid that I won't be of much help going forward. I sent in the device on a warranty claim.
I will add that, in the day or so following my posts here, I plugged the phone in again and to my surprise it began taking a charge again. I let it charge for about an hour, and tried turning it on - remarkably, it came up normally. It was stable for about an hour more, and then froze and powered off as before, refusing to once again turn on.
I left it alone for another couple of days, during which time my replacement arrived, and tried again. It began taking charge, and I left it as such for a couple hours more. This time knowing that my stable time was limited, and with a replacement phone in hand, I immediately restored the phone to RUU stock and locked it.
Your problem seems different from mine, in that my device was outright refusing to even take power or turn on. Best of luck to you, though!
Thanks for the info...I appreciate the response. I'm hoping that there's something that can be done but after 2 hours, trying every trick I could find via
Google with nothing to show for it, I'm keeping fingers crossed that it's something simple I'm missing. If I could just get into the dang bootloader!
Thanks again!
Sent from my SM-P600 using XDA Free mobile app
---------- Post added at 01:38 PM ---------- Previous post was at 01:34 PM ----------
sigmaxaa said:
Hi,
Background: Rooted, S-Off (via Sunshine), was running CleanROM (on the 444 firmware) and tried installing Vanir 444. ROM installed no problem, Gapps installed no problem, installed SuperSU 2.40 at the end and rebooted.
I've run into the exact same situation as the OP. Tried all the button combinations/adb stuff and the phone only boots to the initial white HTC screen but then goes blank. I've tried everything to get into bootloader but nothing seems to get me there. The phone vibrates when it "turns on" after the hard reset but nothing after the white HTC screen except a black screen.
I'm responding to this post in particular because my phone was/is showing the blinking power light when it's plugged in. Hopefully this is a good sign?
TIA for any help!
Matt
Click to expand...
Click to collapse
To add to this, I've let the phone sit for about an hour, untouched, and now the green light is blinking like it does when there's a SMS/email. Pushing the power button doesn't do anything.
devmage said:
I'm afraid that I won't be of much help going forward. I sent in the device on a warranty claim.
I will add that, in the day or so following my posts here, I plugged the phone in again and to my surprise it began taking a charge again. I let it charge for about an hour, and tried turning it on - remarkably, it came up normally. It was stable for about an hour more, and then froze and powered off as before, refusing to once again turn on.
I left it alone for another couple of days, during which time my replacement arrived, and tried again. It began taking charge, and I left it as such for a couple hours more. This time knowing that my stable time was limited, and with a replacement phone in hand, I immediately restored the phone to RUU stock and locked it.
Your problem seems different from mine, in that my device was outright refusing to even take power or turn on. Best of luck to you, though!
Click to expand...
Click to collapse
For what it's worth for anyone that finds this info useful...can't take credit for this as I found it over in the One M8 forum. Thanks to @mpogr
I quote his post: "The problem was that my phone's screen was going blank after the normal boot screen, so I couldn't see when it gets turned off. I was simply pressing the Vol Up + Power for too long, so it would go into full reboot. I just measured the amount of time it was taking to do this (was ~12 seconds). So I pressed Vol Up + Power for ~10 secs, then released those and pressed Vol Down. That finally brought me into Fastboot.
I could have probably gotten the same result by pressing Vol Down + Power, however, the phone screen was blank all the time, so it was difficult to understand when I should have released the Power button to let it go into Fastboot."
I held Power/Vol Up for 10 seconds (as he described) and then let go and immediately held Vol Down only...after about 3 seconds, bootloader screen came up and I was able to get into recovery and restore a backup.

No response or any indication from my Z5 after a black screen

Here is what happened. I was playing Crashlands when I noticed that my battery is at 3%. So ran to get my Quick charger to get some power fast. After connecting it, I tried to unlock the screen and it went black after a second. So I was thinking that it just shutdown because of low battery. I pressed the power button and noting happens, just the red light showing it was charging. Then I tried soft restart (power + volume up) and it vibrated 3 time and probably shutdown. From that point noting I did started the phone. Even using the off button next to the Sim tray. When I connected it to my PC is ether recognized as Unknown USB device or SOMC Flash Device. I should probably mention that the phone was hot from the game before connected it the charger.
I had the phone for one year and a bit. It is not rooted and i just recently installed the lattes update from Sony. Currently I have it put to charge, at least it looks like it is charging (gets little hot).
Is my phone bricked or something else? What should I do?
I have same problem like this.
Hope someone can help us.
QHSUSB_DLOAD device will show when Connected PC.You can use Flashtool to install the driver.
Unknown divices : because you should complete shut down the power (Disconnect the buttery ).
flash tool will find the phone ,but can't flash.
seems Z1 have a way that find the test point to recovery boot file.hope z5 have the same way.
Sorry for my Poooor English ,hope you can understand what i say and have someone Help US.

Cant shutdown to charge devic

I just purchased the 6x and I was going to root and get some stuff done before getting it setup for a relative.
However, i screwed up the twrp recovery flash and messed it up. I've found the directions to get it back on track, however I can't charge it enough to actually let the recovery run. The battery is dead and when i plug it into the charger it just keeps turning back on and sticking at the "Your Device is booting now". I've attempted holding the power button down to force it to shutoff, but it doesn't seem to have any effect.
Anyone else run into this issue and managed to get past this problem?
You can try pressing the up volume + power. Also you can try down volume + power. Also you can press all 3 buttons and keep them held down. Hopefully one of those combinations can help you. Else you will have to let the phone battery completely die (overnight) and then plug the charger in.
fc3211 said:
You can try pressing the up volume + power. Also you can try down volume + power. Also you can press all 3 buttons and keep them held down. Hopefully one of those combinations can help you. Else you will have to let the phone battery completely die (overnight) and then plug the charger in.
Click to expand...
Click to collapse
Unfortunately I've done all of these options. Letting it drain over night is what got me into this situation actually. I can get myself into fastboot to follow the instructions I have, install the boot/recovery/system images. And can even get the boot for installing update.app to start, but from what i can tell it doesn't have the juice it loses power and shuts down. then when it gets just a enough juice, it automatically turns back on and sits at the "booting now" screen.
Are you sure you held down the power button long enough? Try holding it for 5 minutes straight and dont let go no matter what
I am not sure what else to suggest to you, will wait for one of the more experienced members to chime in. You may have to physically open the phone and disconnect the battery if nothing else works. And that is not an easy job if you look on YouTube to replace the battery on this phone takes at least an intermediate level of skill with micro-electronics.
All I can tell you is to please not lose hope. I had a situation 3 or 4 days ago where I had FRP lock on and nothing I tried worked and I was ready to sell the phone on eBay for $50 and cut my losses but the older members of this forum helped me and after hours of frustration I finally have a working phone again. If worse comes to worse comes to worse than your final option will be to try to get service from Huawei, maybe lie to them and say that you accepted ota update and that the Huawei update caused all the problems. Or better story than that: Tell them you where mugged at the Mall and thief stole your phone but then 3 days later you saw the same thief again at another Starbucks and confronted the thief and took your phone back again. But it appears the thief must have tried to flash TWRP or something because now phone is messed up. Maybe they will believe that. Haar-Haarr
But that is a worst case scenario, probably it wont come to that. My phone was doing the same thing as yours, I forget what I did to interrupt it from rebooting on its own. But really all you can do is try a combination of the buttons and hope the dang phone will finally just power off. Its too bad you cannot boot into TWRP and select POWER OFF
Try booting into eRecovery. Plug your device to the charger and turn the phone on. When you're on the bootloader warning, press and hold Vol+ button until it boots. eRecovery should let you to charge your device. It also has a battery indicator.
BTW, don't forget to download your phone firmware. It may be necessary for fixing your phone if you messed up an important partition.
Panchoso4D said:
Try booting into eRecovery. Plug your device to the charger and turn the phone on. When you're on the bootloader warning, press and hold Vol+ button until it boots. eRecovery should let you to charge your device. It also has a battery indicator.
BTW, don't forget to download your phone firmware. It may be necessary for fixing your phone if you messed up an important partition.
Click to expand...
Click to collapse
I can't seem to get to recovery.
After working on it more yesterday, i'm not entirely convinced it is the battery causing me the issues. After flashing the .img files in fastboot, i can sometimes get it to start recovery (both volume buttons and power) and it will start installing the update but it stalls and reboots at 5%. Based on what i've read on the other threads, this has to do with not getting the right firmware matched from what as on there before. Problem is i jumped so quickly into unlocking the bootloader and trying to root i never paid attention to my build number in the OS to know what to flash back to. I've tried multiple TeamMt firmware search website, as well as the official one from Huawei.

Categories

Resources