Hi guys,
this is gonna be a long story, but I'm at end of my wits.
So my phone (HTC One M7_UL Vodafone DE) got water damaged (it was submerged in water for at least a minute). I tested it again last weekend and it seemed to work in terms of hardware. I managed to test the speakers, the charge jack, the headphones jack, wifi, gsm, both cameras, etc. it all seems to work fine, and it's not about that anyways. I kept getting a "com.htc.htcdialer" issue, saying the process had unexpectedly crashed and then a few minutes later the phone would reboot. I tried finding out what this error was and how to fix it but I couldnt find anything. Also its weird that I got a software error.
So I unlocked the bootloader (via htcdev.com), flashed the latest recovery (I tried both cwm and twrp), which was also fine. I managed to install the latest Android Revolutions HD (53.0) and thats where the problems started again: I would get to the lock screen but as soon as I would swipe up to unlock it I would the white screen with the HTC letters on it. I tried wiiping all the cache and partitions i could find and reinstalled that rom, but the problem remained the same. Tried a different recovery (twrp) repeated all the steps and still no more luck than before.
So I decided to give a different rom a try and just flashed the latest stable cyanogenmod rom on it, and that boots fine, but eventually without error message reboots as well.
Then I tried flashing the latest viper rom, but there I have the same issue as at the beginning, that I get as far as the lock screen and then it just wont let me unlock it.
And that's where Im at the end of my wits. I cant imagine its a hardware related issue, but i might be wrong.
Ideally I would love to get my hands on a nandroid backup to restore the phone to stock, a stock rom ruu, but I cant find any of those either.
I'd really appreciate your help.
Let me know if you need specific details of installations, versions, decide numbers, etc
Related
I'm pretty desperate right now as I'm trying to fix my phone for like 24 hours straight and searched the whole ****ing internet for a solution and my eyes are popping out any moment. My situation:
I have a HTC One from Vodafone Germany with LTE.
I rooted it with the HTCdev.com method described in this tutorial:
http://forum.xda-developers.com/showthread.php?t=2292729
After that I put CM10.2(Android 4.3) on my phone and for the first two days it worked quite ok but since two or three days I get no signal at all. The APN settings are definitely correct. Then I decided I try to go back to stock and that's where the next problem pops up. It seems that I can't go back to stock because when I do my phone wont react to any touches at all. It seems this is a common problem when going back from 4.3 to a lower version (as the nandroid backup of vodafone stock is 4.2.2 or 4.1.2). Because I used the method mentioned above I'm stuck with HBoot 1.54 and S-On so I can't do anything about that touch problem it seems and on 4.3 I don't get any signal at all (WiFi working, just saying). Even tried Pac-Man Rom, still no signal at all. Can someone help me in any way? No one can call me or text me for two to three days now and this is a really bad situation!
Hope I did not miss anything!
anstaendig said:
I'm pretty desperate right now as I'm trying to fix my phone for like 24 hours straight and searched the whole ****ing internet for a solution and my eyes are popping out any moment. My situation:
I have a HTC One from Vodafone Germany with LTE.
I rooted it with the HTCdev.com method described in this tutorial:
http://forum.xda-developers.com/showthread.php?t=2292729
After that I put CM10.2(Android 4.3) on my phone and for the first two days it worked quite ok but since two or three days I get no signal at all. The APN settings are definitely correct. Then I decided I try to go back to stock and that's where the next problem pops up. It seems that I can't go back to stock because when I do my phone wont react to any touches at all. It seems this is a common problem when going back from 4.3 to a lower version (as the nandroid backup of vodafone stock is 4.2.2 or 4.1.2). Because I used the method mentioned above I'm stuck with HBoot 1.54 and S-On so I can't do anything about that touch problem it seems and on 4.3 I don't get any signal at all (WiFi working, just saying). Even tried Pac-Man Rom, still no signal at all. Can someone help me in any way? No one can call me or text me for two to three days now and this is a really bad situation!
Hope I did not miss anything!
Click to expand...
Click to collapse
have you tried to flash a stock RUU? http://forum.xda-developers.com/showthread.php?p=39588860
As I already mentioned... Yes I did and then the display wont recognize any touch input
Have you tried flashing the TWRP for the newer drivers and seeing if it responds?
Sent from my Nexus 10 using Tapatalk 4
It's not the recovery where the touch is not working. Recovery is working fine. As soon as i flash the stock rom and boot, i cannot type in my pin, because it wont react to touch.
anstaendig said:
It's not the recovery where the touch is not working. Recovery is working fine. As soon as i flash the stock rom and boot, i cannot type in my pin, because it wont react to touch.
Click to expand...
Click to collapse
Wut. But have you tried an RUU: a total factory reset of everything?
Hi all, love this forum but dont post often.
Heres the problem: My HTC One m7 (international version) is acting strange:
* Sometimes when I turn on the display I have to enter my sim pin, as if it had rebooted itself, only I know it hasnt. It also happens regurarly when Im using the phone *poff* all of a sudden "enter sim pin".
* When switching from wifi to 3g/LTE it lags for minutes. It drops all connections, including regular gsm, and I have to enter sim pin maybe half the time I swith from wifi. Switching from 3g/LTE to wifi doesnt present the same issues.
* Its extremely laggy when these things happen, otherwise it works fine.
What I have tried so far:
* Old backup of Liquidsmooth 4.4. Works fine for a few days then these same problems starts occuring.
* Uninstalling apps. Thought I was onto something when I uninstalled SwiftKey and it worked perfectly for about 3 days! But then the problems came back...
* Tried other roms but I usually end up with the "unfortunately the process com.android.systemui has stopped" when the rom is up and fully booted. Its a loop that just continues (when pressing ok) so I cant do anything but reboot and try again. I tried probably 5 versions of Liquidsmooth but also Beanstalk and other aosp roms, even Lollipop versions (the liquidsmooth one worked but the same sim pin problems occurred). Havent tried any sense based roms. Also tried several versions of TWRP, official and unofficial. Still ends up with the com.android.systemui problem.
* Tried resetting permissions, wipe cache/dalvik and also wiped the entire sdcard. Used adb/flash to transfer new rom for installation.
So I'm basically out of ideas and pondering going back to stock and sending it in for repair, unless someone here has some tips since I'd rather try myself first.
Thanks for any help or input!
koolkeith said:
Hi all, love this forum but dont post often.
Heres the problem: My HTC One m7 (international version) is acting strange:
* Sometimes when I turn on the display I have to enter my sim pin, as if it had rebooted itself, only I know it hasnt. It also happens regurarly when Im using the phone *poff* all of a sudden "enter sim pin".
* When switching from wifi to 3g/LTE it lags for minutes. It drops all connections, including regular gsm, and I have to enter sim pin maybe half the time I swith from wifi. Switching from 3g/LTE to wifi doesnt present the same issues.
* Its extremely laggy when these things happen, otherwise it works fine.
What I have tried so far:
* Old backup of Liquidsmooth 4.4. Works fine for a few days then these same problems starts occuring.
* Uninstalling apps. Thought I was onto something when I uninstalled SwiftKey and it worked perfectly for about 3 days! But then the problems came back...
* Tried other roms but I usually end up with the "unfortunately the process com.android.systemui has stopped" when the rom is up and fully booted. Its a loop that just continues (when pressing ok) so I cant do anything but reboot and try again. I tried probably 5 versions of Liquidsmooth but also Beanstalk and other aosp roms, even Lollipop versions (the liquidsmooth one worked but the same sim pin problems occurred). Havent tried any sense based roms. Also tried several versions of TWRP, official and unofficial. Still ends up with the com.android.systemui problem.
* Tried resetting permissions, wipe cache/dalvik and also wiped the entire sdcard. Used adb/flash to transfer new rom for installation.
So I'm basically out of ideas and pondering going back to stock and sending it in for repair, unless someone here has some tips since I'd rather try myself first.
Thanks for any help or input!
Click to expand...
Click to collapse
maybe your sim is faulty. try to get a new one from your provider. or it just has a bad contact in your phone.
about the lagging: did you try a clean flash? is your storage full? my phone gets pretty laggy when my storage is nearly full..
Hey thanks for your reply! However I dont think its the sim card, and as I mentioned I clean flashed several times with several twrp version and also twice with wiping all data on my sdcard...
Sorry if I can't offer a concrete solution, but I had similar issues (especially the first one, but also lag when switching networks) on my HOX+. Turns out it was the sim.
Try to test another sim before returning, and at least try a sense based rom. Since you say that it works without problem for a few days with Liquidsmooth 4.4, and then it starts breaking again, it may be rom (aosp?) related. But then again, it may be just random.
Hope you figure it out soon
Thanks akpe! I ordered a new sim card, if that doesnt help I suppose its something hardware related...
Well, the new sim card didnt help. My problem seem very similar to this: http://www.androidpolice.com/2013/0...rops-on-some-nexus-4-handsets-fixes-in-sight/
Basically my whole radio disconnects and restarts itself when turning off wifi. Reading that androidpolice thread leads me to thinking about flashing an earlier firmware, from 4.2.2. I have no idea which one, or if I can use the one in that thread or not.
Any suggestions? I'd appreciate it, googling for hours and reading catlogs for days isnt getting me anywhere..
HELP!
Hmm wasn't that a Google issue which got fixed by HTC in the latest OTA? Try a ROM which has the hotfix (like latest ViperOne, 7.0.2) and see if you still get this
akpe said:
Hmm wasn't that a Google issue which got fixed by HTC in the latest OTA? Try a ROM which has the hotfix (like latest ViperOne, 7.0.2) and see if you still get this
Click to expand...
Click to collapse
Hi akpe! I took your advice and am now running ViperOne 7.0.2 and so far it WORKS! So it seems it was indeed that google bug. HUGE THANKS!
Is it possible to have the aosp lockscreen when at the same time using a pin? I can't seem to figure that out.
Thanks again!
Glad it worked
As for the lockscreen, no idea mate, I'm using the stock one :/ Ask around in the ViperOne thread, maybe someone there knows
Ok, thanks again!
Another thing I cant find is profiles? Need it to make whatsapp notification sound silent when listening to music..
Hi guys and gals.
I've been flashing roms for years and I've soft bricked my devices dozens of times and have always been able to recover, except this time.
I was running Cyanogen mod 12.1 and all the problems started happening after a nightly update. Basically, the phone got super laggy and eventually started random rebooting. I thought it was a bad flash or something was wrong with the latest update so I did a clean wipe and flashed another rom, same thing happened. Eventually I Odined back to stock and it ran fine for a few days but the problems came back. Now the phone won't even finish boot anymore. I used NAND erase all in odin and and reflashed again, it seems to be better since it wont reboot its self anymore but I can't get past the T-mobile splash screen. Last night I tried reformating the NAND using a PIT file but I kept getting "Secure check fail : PIT". I was starting to thing the problem is hardware related but it won't RR in download mode and I think its too big of a coincidence that it happened after the Cyanogen update. Any ideas?
My first and always main advice is that if you are unsure about your hardware the first step is to Odin back to stock. The reason is because it is a bit for bit rewrite back to the way the phone was intended to be run as long as you do a factory reset from Stock Android Recovery before it boots. This is how your phone was when it came out of the box and it is a great way to check if it has a hardware issue by looking for bad behavior when using the original drivers.
If you flash back to stock completely clean and your phone is still acting crazy you might have bad blocks on your NAND, you might have issues with your RAM/CPU, or it might just be a loose hardware connection from heat or impact. But you can only truly diagnose those from Touchwiz because the drivers are first-party, not reverse engineered to be compatible. If you can reinstall all your apps and use it normally for a week then your hardware is good and CM was the problem and you should try another AOSP build.
I am on the 09/09 Nightly for CM and I can tell you that I have no lag or issues on my device at the moment for what that is worth. Good luck!
Thanks. I might just send it into samsung and see what happens.
So I think I messed up my phone.
TL;DR: Messed up phone by removing stock rom, Costume roms don't work except 1 and in that one IMEI is set to zero and I can't connect to any network.
several month ago I had the stock xperia z Lolipop and made a decision to root the device. I unlocked it's bootloader and did the rooting... all as planned. about a month later my phone started acting funny, so I decided to reset it, the problem is I had installed TWRP and as noob in using the app, I accidentally wiped the entire device. I thought I had bricked the thing so I left it aside.
I had been using an older phone as replacement until last week when I thought I'd give the Z another chance. I looked around this forum, found a bunch of stuff, tried a lot of roms and after failing to make 4 roms work (Cyan nougat, Cyan MM, Costumised sony 5.1.1 and a stock one I found here) I managed to find a fifth one that worked (http://forum.xda-developers.com/xperia-z/general/android-5-1-available-yuga-pabx-t3054304). I always followed the tutorials but I may have done a lot of mistakes... for example I'm not even sure what kernel is and if I needed to change it for any of the roms or if I needed to like wipe the entire system or not before flashing ( I did all the time), and what about rooting? does the system require a previous rooted rom to install new ones? don't we simply format the entire device?.
Now the major problem of the working rom is that my phone can't connect to it's simcard network, the simcard is working since it requires pincode on start and the phone can find the networks by manual search, it simply gives an error "network XXX unavailable". I looked around and saw that my IMEI is set to all zero's in the phone about section. this could be unrelated to the network problem... but I don't have much expertise in these stuff.
So right now it seems like I can't install any other roms (they won't even start up, most get stuck during boot) and the only one I can install doesn't give me network access.
Any Ideas?
Hey guys, I've encountered a thorny problem on my wife's N910T3, and am running out of ideas about what this could be... so, could really use some help.
Some background: The phone's been working fine for over a year of ownership, mostly on the stock ROM, which gets pretty laggy at times. A few weeks ago I installed a custom ROM (the Acapolypse-X N7 port) to improve performance, and for the past few weeks it's been working perfectly fine on the custom ROM no problem.
Today, when my wife went to check Twitter, the phone crashed and started bootlooping. I had seen a similar issue on my Note 3 before (which turned out to be a specific issue with the kernel I was using), so I figured I would just go into recovery, flash a different kernel or at worst, do a clean install of the ROM.
That's when things started getting weird: The phone would crash while INSIDE recovery during ROM installation (I've never seen a phone crash inside recovery before...) After failing to successfully flash a ROM or, even in cases when it succeeds, fails to boot, I decided to do a full flash back to the latest unmodified stock ROM (since I couldn't find an ODIN-flashable image to download, I used Samsung Kies for this - typically this resolves any kind of left over from previous installations).
On the first attempt, it succeeded - the phone booted into the stock ROM and I was able to start customizing settings. Figuring the issue has been resolved, I went ahead and attempted to root by flashing TWRP through ODIN, and that's when the phone went back to rapidly bootlooping again (it reboots every 2 seconds, I can't even get into recovery when this is occuring). The only way I can return to Recovery is by flashing it again in ODIN (typically this trick will only work once; upon rebooting the phone after that it is prone to start bootlooping again).
Based on the symptoms I suspected the NAND going bad. However, I receive no emmc read/write errors during flashing - all write operations in ODIN results in success and my friend even ran a full storage check via ADB and this phone just doesn't seem to have any bad sectors (I almost wish it were since that would resolve the mystery).
Anyone have any ideas what may be the problem? I have a decent amount of experience installing custom roms on my phones and troubleshooting installation issues, but I've never seen anything like this (crashing/bootlooping directly inside recovery).
I'm sure there are several possibilities that could be software related. However, I've had this issue on a couple of my older phones and it just turned out that the power button was sticking. Just had to pull the phone apart and clean it.
If nothing else seems to work for you, it wouldn't hurt to check this.
PS: I have 4 boys who like to play on the devices with sticky fingers.