[SOLVED] HTC One shutting itself down - One (M7) Q&A, Help & Troubleshooting

Hi !
I am currently encountering an issue with my HTC one, it worked well, until I connected it to my computer last night.
Since then, the phone keeps shutting himself down after 1 minute or so.
I've the latest Viper ROM, ICECAVE 5.3 and ElementalX 14.1
I've tried everything I could, I wiped the dalvick and cache partition, re-flashed the kernel, re-flashed ICECAVE, nothing helped.
I can't flash the ROM as I don't have the ZIP on my phone's memory.
What bugs me out is that everything worked fine until I connected it to my computer, it's not logical at all, I did this thousands of times before and did not flash anything new since days....

So, after searching around the internet, I found that I could use adb in Recovery, so I pushed the ROM file and flashed it with a total wipe, everything is fine now !
(I had issues regarding adb push and sideload, but it was because drivers issues, I just used an other computer and it worked well !)

Related

[Q][GT-I9001] Ivendor CM10 plus CastagnaIT Kernel (from Softreboot to Hardbrick)

Hello everyone,
I just hardbricked my SGS+ and now I'm a bit curious how this could happen.
This is what I did:
I used to run CM9 RC5 from arco68 along with the Kernel for ICS from Christopher83 and CWM 6.0.1.2.
Because my phone always lost the wifi-connection and also had some freezes I decided to try out CM10 Beta 3 from ivendor.
I backuped my phone, downloaded the zips and even verified the MD5sums. Next I flashed CWM 6.0.1.9 as recommended in the thread from ivendor.
After exporting the nandroid backup and other stuff like photos to my computer I wiped everything as mentioned in the thread, flashed the two zips and rebooted. Everything went fine and I was almost ready with setting up my phone again when I got my first softreboot.
Suddenly it showed the CM-bootlogo and after maybe 10 seconds I was back on my homescreen. I got another two or three softreboots until I decided to flash the Kernel 3.x from CastagnaIT.
I rebooted into recovery, wiped cache and dalvik cache, flashed the zip and rebooted.
Now I wanted to reboot into recovery again to fix permissions but instead I got a softreboot and my phone stuck at the CM10 bootlogo.
I waited for around 5 minutes and then I just turned the phone off and booted into the recovery mode.
Because I wanted a clean install without any problems like softreboots I decided to wipe my phone again (data, cache, system) and just reflash the zip for CM10. And at this point everything went wrong.
I flashed CM10 but when I tried to flash gapps my phone just turned off. And no, the battery was not empty. In fact the battery was at around 50-60% and my phone was also connected to my computer.
I tried to turn on my phone but now it stuck at the Samsung bootlogo.
The next thing I did was probably a horrible mistake. I tried to un-brick my phone but I did not realize that I could boot into download mode without problems so I guess my phone wasn't softbricked at all.
Well, after that I still stuck at the Samsung bootlogo and couldn't enter recovery mode. I got into download mode somehow and maybe this was my second mistake. I tried to flash the "i9001Reset.zip" via Odin. Everything went fine but when Odin said "Close serial port and wait until rebooting" my phone was completely dead. I think it was while I tried to flash the reset-file when I got a message like "MBR: read failed". So somehow I managed to destroy my master boot record.
Now I can't turn on my phone or enter download nor recovery mode. I already removed the battery for about 45 minutes but this didn't work either.
My phone is dead but at least I saved the important data and maybe I'll get a new one through warranty. Or I just buy a Nexus 4.
My questions are:
What did I do wrong especially when I tried to save my phone?
How can I prevent such things from happening?
And at which point I should have got help here in the forum or elsewhere?
I would really appreciate some tips for the future because I already flashed and used a lot of different ROMs but this is the first time something really went wrong.
Thanks for reading and thanks for your help in advance.
(Please excuse my non-perfect englisch.)
Greetings,
Mangoniter

[Q] HTC one - ARHD install crash - phone bricked

Hi Guys,
So i've been away from flashing ROMs for awhile but have been playing with my HTC one and have had no issues until today.
I downloaded the new ARHD, put it on my SD card and went to install it. Aroma played nice for once but as soon as it started installing and doing the full wipe the phone rebooted. So i tried again with the same result. In the end i passed by the full wipe option and managed to get to the final step of rebooting and then it would freeze which it did 3 times.
Now i can see the ROM but i can't mount the SD card in CWM to put anything else on there so my phone is useless. I am not really experienced with ADB having only used it briefly with my sensation a few years back.
Can anyone help?
Thanks in advance
connect phone to comp, open cmd in folder that you have rom on computer (cd/location/here/rom.zip) then do (as long as you set up adb correctly) adb push rom.zip while selecting flash rom from sideload. cwm will do the rest.
I think all that happened was Aroma crashing every time. Correct me if I'm wrong but that's what it sounds like to me.
Hi,
I cannot get the phone recognized in fastboot, if i let the phone start to boot i can see my device.
Sorry if this isn't clear
Glenn.Bre said:
Hi Guys,
So i've been away from flashing ROMs for awhile but have been playing with my HTC one and have had no issues until today.
I downloaded the new ARHD, put it on my SD card and went to install it. Aroma played nice for once but as soon as it started installing and doing the full wipe the phone rebooted. So i tried again with the same result. In the end i passed by the full wipe option and managed to get to the final step of rebooting and then it would freeze which it did 3 times.
Now i can see the ROM but i can't mount the SD card in CWM to put anything else on there so my phone is useless. I am not really experienced with ADB having only used it briefly with my sensation a few years back.
Can anyone help?
Thanks in advance
Click to expand...
Click to collapse
If it got all the way to the "Reboot Phone" stage--meaning that the phone wiped and installed the new OS--you should be fine to boot the phone up normally. I'm sure you have, but have you tried just powering it up and seeing if it'll load into Android? Reminder: First boot after a new ROM always takes a few minutes.
Hey guys,
So i ended up continuing to flash it trying various options and eventually it came up ok... The scary thing was the random reboots during install whilst aroma was trying to wipe everything...
But all sorted, thanks everyone!

[HELP] No OS and Phone Reboots when flashing

Hi All,
My phone decided to put itself into an infinite reboot loop today for no reason. It was running Android Revolution HD 31 fine before this point (S-On).
I could not get it to start so I wiped in recover and tried re-flashing, and it rebooted during flashing
I have tried uploading smaller roms to it, but it reboots during the adb sideload or adb push, so currently I am stuck, I also download the RRU but it does not detect my phone
Any help would be much appreciated!
Update it finally flashed everything is crashing will try a wipe and flash again.....
make sure it is charged before flashing, at least 30%.
never change a rom without a full wipe.

Sorta bricked my phone???

Sooo... I had a rom installed and decided for the giggles to another one. I wiped everything and it. It worked fine for about an hour, and then it rebooted randomly, i did not think much of it until i tried to unlock the phone. As soon as I entered the pattern it rebooted. I tried it a couple times and it happened every time. Thinking it was a bad rom I wiped everything and flashed my old one back on. Guess what, it kept happening. So I "figured" I must have screwed something up badly. Decided to do a full factory wipe using kdz and lgup. Once that finished I flashed the newest twrp which I believe is 3.0.2, then i flashed the old one back on. Same thing happened, worked for a bit then rebooted randomly and then kept rebooting every time I tried to unlock the phone. (Also flashing the newest gapps package each time, and I redownloaded both gapps and both roms multiple times) I just did another kdz wipe but tried flashing twrp 2.8.7.1. Will flash the old rom again and let you know how it goes in the morning. In the meantime, any ideas of why this might be happening?

Samsung Tab s2 stuck booting into TWRP

Ive been lurking on this forum for a while but ive finally hit a wall I cant find an answer to
I successfully rooted my tablet using magisk and TWRP about 4 months ago, everything was going great. about 2 months ago my tablet booted up into TWRP and would not get out, no matter what I tried. eventually I fixed it by wiping everything and reflashing stock ROM from ODIN and going through the root process again, not a big deal. cut to 2 days ago, my tablet restarts and boots into TWRP again and wont boot into system, basically seemed like the same as before, until I plugged it into my computer
For some reason, my tablet no longer connects to ODIN or my laptop at all. Ive used the same cable and different device and same usb port and it worked just fine, ODIN picked up the connection and everything. Ive updated and unistalled and reinstalled drivers for all the USB ports and I dont think that is the issue. I even deleted and reinstalled ODIN but still nothing.
I thought maybe there was some setting on the tablet that might be preventing a connection to ODIN, so I wiped the rooted ROM off the tablet (im new to this, dont know if this was a bad idea) and tried again but got nothing. now with a soft bricked tablet I got a micro SD card, put a TWRP flashable version of the ROM onto it and plugged that into the tablet and flashed this new ROM onto the tablet, and that worked from what I can tell (system folder went from like 8mb to 17000 or something) but I still cannot get the tablet to boot into system.
I can access download mode (there appears to be two versions, one where it just says downloading and another where a bunch of text appears on the top left, some of it mentioning ODIN) and all the functions of TWRP, but ODIN does not connect and I cant get it to boot into the system.
TWRP version 3.1.0.1_ashyx
link to the post where I got the stock lite version of the ROM currently flashed to my tablet:
https://forum.xda-developers.com/tab-s2/development/rom-nougat-stock-lite-v1-t3746583
any help would be greatly appreciated, sorry for the wall of text.
Wish I had something useful to add. I'm having the same issue. TWRP 3.4.0.0 and LineageOS. I've had this issue forever. I flash a clean ROM, it works for a week or two, then I come back to it and all I get is recovery.
I can access Odin however.
Usually it takes wiping and installing a ROM to get the device working again, in fact it issue takes several rounds of that. But of course, in all of that I've lost my setup and some files.
Is there an actual solution to this?
On my T810 I'm having TWRP 3.3.1-0 with this ROM https://forum.xda-developers.com/tab-s2/development/rom-aospextended-rom-v6-7-t3979381
plus Magisk and Pico Gapps.
Of course it's only Pie and not Q, but working well.
3.4.4-0 not tested yet.
Once had an issue with black screen, but at that time I was using case with a screen cover.
Since that I've switched to TPU case only covering the back.
No more issues after that, perhaps it was a problem with FlipFlap like on other devices.

Categories

Resources