Hi guys. I rarely have to post anything on here as I always find the resolution to my problem. I have a Vodafone UK HTC One M9 and I was rooted with S-off, unlocked bootloader. When the Android 7.0 update was able to be downloaded ota I tried to install it and it didn't work. I assumed it was because I had TWRP recovery installed rather than the stock recovery. I flashed stock recovery back on and then it still didnt work. I can't exactly remember what happened but i ended up spending two weeks trying to recover the phone. I have now S-on and after flashing hundreds of things i've finally got it sort of working again.
The Problem.
It is now running android 7.0 BUT it constantly displays 77% for the battery level and refuses to charge. I have the charging LED but it does not charge. Now the battery has died I can only power the phone whilst it is plugged into the mains. I can get into download mode and android. As soon as I try and load recovery it turns the phone off (allthough I have reflashed recovery).
What have I cocked up? I assume I need to reflash something that controls my battery? The phone worked perfectly prior to this. Any suggestions or advice would be greatly appreciated.
You flashed a stock recovery in a rooted state. That's what you did wrong.
Considering I know nothing about what you've done to it so far I'd say to follow flippy's thread in the general section stickies and return the phone to stock state.
Beamed in by telepathy.
Related
My phone's USB port stopped working recently so I needed to unroot in order to file a warrenty claim. I flashed a rooted stock rom and performed an update to get back to completely stock (this deleted my custom recovery as well). Last night it asked me to update from 3.26 to 3.29 something and I did it. I think that it installed correctly and rebooted normally, but I'm not totally sure (it was pretty late). Now this morning I saw it was off and when I turn it on it goes straight to fastboot. There doesn't seem to be an option from here to boot into the full phone. Now I'm unrooted, no custom recovery, and can't use the USB port. (The way I was charging it, btw was through a hacked USB cord pressed right between the contacts on the battery and phone). What can I do?
Would there be anyway to flash a file called PC36DIA.img or whatever the file it looks for when you load the HBOOT that would fix this problem? Does anyone know how to make/get one that would fix it?
blakerboy777 said:
My phone's USB port stopped working recently so I needed to unroot in order to file a warrenty claim. I flashed a rooted stock rom and performed an update to get back to completely stock (this deleted my custom recovery as well). Last night it asked me to update from 3.26 to 3.29 something and I did it. I think that it installed correctly and rebooted normally, but I'm not totally sure (it was pretty late). Now this morning I saw it was off and when I turn it on it goes straight to fastboot. There doesn't seem to be an option from here to boot into the full phone. Now I'm unrooted, no custom recovery, and can't use the USB port. (The way I was charging it, btw was through a hacked USB cord pressed right between the contacts on the battery and phone). What can I do?
Would there be anyway to flash a file called PC36DIA.img or whatever the file it looks for when you load the HBOOT that would fix this problem? Does anyone know how to make/get one that would fix it?
Click to expand...
Click to collapse
I think this is what you're looking for:
http://forum.xda-developers.com/showthread.php?t=791019
And here's the thread for getting the stock 3.29 back after your phone can boot into a rom (so you can get your warranty)
http://forum.xda-developers.com/showthread.php?t=800582
I put the file on my memory card, and a blue bar goes up on the side. I'm pretty sure that I'm supposed to OK something at some point and then more bars in different colors go up in the same place, but none of that happened. After it goes up, it says something like loading file, then just goes back to the boot loader. I think the update did this more than anything else.
My question is this: I still don't have a custom recovery (this thing was supposed to flash clockworkmod recovery), can I assume that this didn't change anything on my device? I'd feel a lot more comfortable saying that an update bricked it than knowing that I might have just tainted it by rooting the phone after it got bricked.
Hey mates,
would be cool if you could help me to understand the connection between recovery and flashed rom...
This is why I'm asking: I rooted my desire a couple of weeks ago (by applying the unrevoked method). Since then I flashed a couple of custom roms. I wasnt very happy because the most roms caused my mobile phone to crash. I thought it was because a broken sd card therefore i bought a new one today. Sometimes when my phone crashed I wasnt even able to enter recovery anymore. And sometimes it did just nothing... I couldnt even enter hboot (it just didnt boot - like it was briked - only the charging led was on when i plugged the charger in). In this case I had to remove the battery a couple of times or plug in the charger. Usually I needed to do this many times. This is btw. why I'm fed up with custom roms but maybe its just my mistake. And now finally my question:
Why can I enter recovery sometimes and sometimes not? Does this depend on the rom? Why do I have to remove the battery etc. to make it run?
I know flashed back to the rom I of which I created a backup after root. But it seems that my phone is more unstable since then (even if its just my rooted stock rom)
Thank you for your answers...
What rom are you on? Maybe your recovery is a bit messed, have you tried reflashing it? Btw, s-on right?
If your not able to get to your hboot then there is something wrong with your phone. It will most likely be able to do with your hardware. You can use an ruu to restore everything back to factory default. You could then root again and see if that will help. But it does look like to be a hardware/corruption issue.
Swyped...
Your Desire maybe being one of the new PVT4 new nand would might cause this. I know that the latest version of unrevoked and Clockwork recovery can't be used to root the PVT4 new nand. I had that problem and the fix for me was to use an earlier version of unrevoked and flash Amon Ra recovery instead. There's a thread around the forums regarding this. Check first if your Desire is of the new PVT4 model. Can't post the link but there's a thread that explains how you can check if your Desire is PVT4 new nand. Would post the link but can't yet, but a quick search should take you to it.
hey guys, thank you very much for your fast answers. The desire is s-on. I'll try an official ruu. If I'm brave enough I'll root again . The strange thing is that I can enter recovery but not always. A hardware issue would be awful. I'll let you know how it went. I hope it is ok to just use ruu to update a rooted rom. It flashes a new recovey too, doesnt it?
Ok, i tried to use ruu to unroot my device. It told me that my bootloader was not compatible and canceled flashing. But it also broke my rom. I couldnt boot the system anymore and i couldnt boot into recovery. I dowloaded a ruu image (with my radio) to flash it via hboot. Everything seemed to go fine but after the first restart i'm stucking with an update sign (i guess its the recovery menu) - a mobile with green arrowrs. I think its frozen. Do i need to do anything else?
Hey, just to keep you up to date. I successfully unrooted my device by flashing a stock ruu. Now its booting (but not always) but it often freezes after a few minutes after the boot progress. I guess I'm going to send it back.
Thank you all for your help anyway.
Lovebongo said:
Hey, just to keep you up to date. I successfully unrooted my device by flashing a stock ruu. Now its booting (but not always) but it often freezes after a few minutes after the boot progress. I guess I'm going to send it back.
Thank you all for your help anyway.
Click to expand...
Click to collapse
Yeah best to send it back, it sounds more like a fault with the device
i had my phone for a year now, 2 days i ago i unlocked bootloader and rooted my phone. today i tried to flash the pacman rom. everything went well until i rebooted phone. it starts up normally, but on the setup menu my phone instantly shuts down and opens recovery mode because battery is empty though it is charged. it's been hours now and problem persists, i searched online everywhere and couldn't find answer. so did i do anything wrong? my phone is CDMA and using clockworkmod recovery v5.8.3.1
i really need help here i don't think i can afford a new phone.
by the way, i am not an expert on android so i lack a bit of terminology and also i am new here and i did search and couldn't find any answers. thank you
For some reason my phone isn't booting up all the way to the rom/OS. It gets stuck on the boot animation and goes on forever and hasn't been able to boot up since yesterday, when my powered off at 20% battery, which is something normal for my phone. I was rooted and on android 4.3/MK4, but when I put it to charge and tried booting it back up, the phone would boot up, but would get stuck on the boot animation, going on forever. It wouldn't freeze it would just continue to play the animation. I tried removing the battery, factory wiping it, and installing a new rom, which I found out was for a different baseband. When i finished installing it it still wouldn't boot up all the way through.:crying: I then tried installing the previous rom, and still no good. After all that I installed a stock firmware using odin, hoping it would work. I installed the 4.4.2 NE2 firmware, which isn't for my phone but watching zedomax's video, he said to download the latest build date, which is what I did. Well, downloaded it and flashed it through Odin with a PASS and everything going good. Although, when it was rebooting-even after a factory and cache wipe-it still wouldn't boot up. I tried installing other firmwares aswell, but still no luck. I'm just waiting for it to finally boot up, so if anyone can help me out, I WOULD GREATLY APPRECIATE IT, otherwise, anything is going to help at this point. Since I flashed the firmware, I now have a stock recovery and rom(I hope). I've been through these types of situations, but not to this point.. :crying:
It seems odds, but you may want to try a new battery. I recently went through a total disaster with my device and it ultimately was the battery. You may want to try booting with it connected to the a/c wall charger. It may give you an indication.
Have you tried the quick fix posted? My phone did the same thing when i had the stock recovery it showed error mounting efs folder. I noticed after installing clockwork that error didnt show up. It was still the same problem though. Wouldnt hurt to check it out. I got my note two from a friend who described the issue starting the same way you said happend to yours. The phone had never been rooted though. Good luck to you in trying to fix it.
Sent from my SM-T217S using XDA Free mobile app
I have the ATT sgh-i747. I was using it as normal. The battery was low and i could not charge it before it got to 0%. After it died, I connected the charger and started it back up. When the screen came on, the "no sim-emergency calls only" message was there and the touch screen did not work. Also, the time and date were off. it said 3:59 September 15th. I tried the normal reset (take battery out, replace, turn back on) several times and still the same thing. I had just replaced the sim reader a month ago, as well as the rear camera and speaker, and everything was working as normal. I opened the phone up to make sure all connections were set. Still the same message. I did a factory reset and after I turned it on, still, the touchscreen does not work and it says no sim. I find it odd that both these things would stop working at the exact same time. Also the phone is long past its warranty. Any ideas on what this could be?
Anyone?
Have you tried flashing another ROM?
I don't know how to do that, if you could point me in the right direction I'd appreciate it.
Before anyone can give you advice, we need as many details as you are able to provide.
Was your phone running a stock ATT ROM? What ROM was it running? Are you able to boot into download mode?
Stock Rom, phone is not rooted and I can boot to download
What stock ROM? It's important that anything you flash does not try to downgrade the bootloader if you were on stock 4.3 or 4.4.
I'm not 100% sure. I want to say 4.3. There was a software update for the phone that automatically downloaded about a week ago but im not sure if that is related.
Since you received an update a week ago, you may be on KK.
I suggest flashing Philz Touch recovery via Odin and see if you can boot into recovery. In recovery you can see if the digitizer responds.
Flash the latest tar version from here in Odin: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/