I downloaded this Rom several days ago and ran it with no issues, until last night I went on line to search a topic on Google and the phone started looping.It would boot back to my wallpaper and then start over at the HTC screen. After several attempts to restart and battery pulls , i finally got to recovery and was able to restore back to my previous rom. Phone was wiped prior to installation as instructed and all steps were followed as listed by the developer. No apps were installed other than what was on the phone and restored with Titanium. I really like this rom and hoped it would work, If anyone else has seen this let me know what fixed it for ya.
Thanks.
Related
My Desire has intermittent freezing issues. I thought it might have been due to a poor rom installation so I wiped the Dalkvik cache and factory wipe before I re-flashed LeeDroid 2.2a. I've kept the phone clean and not installed any apps so I can rule out and problems caused by them.
It was working fine yesterday until I was showing a friend how to wipe battery stats, when I went to reboot the phone from ClockworkMod it then froze at the lock screen. I had to pull the battery twice before it actually started up correctly.
It's fine now but I'm just waiting on it happening again.
Has anyone else had these issues?
It was a t-mobile uk handset and I would need to restore to their rom before returning, so if that is the likely solution, can someone pass a link so I can put their rom back on the phone.
Any help or advice appreciated.
I've just got my Desire back from repair (after 6 weeks of grief with HTC, but that's another story on another thread!) and it's doing exactly the same as yours....will appear to work fine, then randomly freeze. This could happen after 10 minutes or sometimes even during boot.
I've rooted it, but it's still got the stock T-Mobile (UK) ROM. I'm wondering if the problem might be caused by rooting, but have downloaded the 2 stock ROMs on the relevant thread on here, but neither will install.
Have you had any joy with your issue?
I'll email you as well.
Cheers,
Rich
Hey, guys!
I am in a desperate need of help. Here's my situation:
I've got an HTC Desire (obviously), which reboots every time the ROM starts. It all began after I decided to move back to a Sense ROM after having been testing ICS for the past couple of weeks. So, I flashed RCmix S - a ROM I knew to be stable and working snappily on my phone. Everything went well, I restored my apps with Titanium and then decided to remove some of the junk stock apps. When this was done, I restarted the phone, only to be faced with a series of reboots every time I got glimpse of the Sense UI (i.e. seconds after unlocking the SIM card).
I thought this might be a ROM-related issue, so I tried another one - Supernova. Same thing. Tried flashing it several times after full wipe always. No luck.
During the whole process I switched HBOOTs a few times - from stock, to Fatsys (IN2SD), back to stock. Tried several recoveries (AmonRA, 4Ext touch).
Even flashed official RUUs at least 3 times in order to get the phone back to its factory state. Once the stock ROM worked fine. Then I went on to root it and tried flashing one of the customs ROMs again, which, predictably, began rebooting just after SIM unlock.
I thought this might be connected to problems with the SD card, so I reformatted it completely - 6,8 GB FAT32 + 1 GB Ext4, using GParted. All by the book.
No I've got a clean SD (removed all the previous folders), but it doesn't seem to solve the problems.
Can anyone, please, think of something that I could do in order to get my phone back?
P.S. I forgot to mention, that my phone is S-Off. It struck me as strange, though, that it stayed S-Off even after flashing the RUUs.
New development: this morning, after successfully creating a Gold Card, I went on to try and flash a 2.2 RUU again. This time, however, the installer announced it was unable to access certain files and thus the flash process had failed. Meanwhile, the phone itself displayed a triangle and an exclamation mark on the 4 corners of the screen. I no long can access Recovery or the Bootloader. Help me, please!
Never mind, I managed it myself.
Hey guys, its my first post on here and I was hoping to get some help with my device. (Yes, I've searched extensively over the internets. No, I can't find anything related to this issue for the One X)
So let me start from scratch. About a month or so ago, my phone started rebooting randomly, I have been using ViperX 2.7.1 by Team Venom since day one of getting my phone and only started experiencing these issues after upgrading my hboot to 1.31, switching to MaXimus and returning back to ViperX. If it was the occasional reboot, I wouldn't be half as annoyed as I am this very moment. Unfortunately, my phone does not ring when I get a call. Does not ring, screen doesn't even turn on, does not notify, nothing. I called it from another number, did not ring, tried turning the screen on, did not turn on, just rebooted. This does not happen all the time, but has been happening a lot recently. So far, I have fresh installed ViperX numerous times, (wiped cache, factory reset, wiped dalvik cache and full wiped from the ViperX aroma installer) thought maybe an app was misbehaving so fresh installed from the play store instead of Titanium Backup. Even tried switching ROMS but I can't for some reason. Tried installing CM10 the other day, didn't go past the white screen. The good people on androidforums.com told me that I need a different boot.img for newer hboots so I got that, but the CM ring at startup freezes followed by a reboot. Switched to ViperX 3.2 (JB) couple days back hoping this issue wouldn't follow me here as well, but alas, it still has. Then yesterday, I thought upgrading my hboot and wiping my phone the way up'ing the firmware does might fix it, so I up'ed my hboot to 1.39. (strangely though, I still have my files on my sdcard) I followed this guide: http://forum.xda-developers.com/showthread.php?t=1920060 Only step I couldn't follow was the adb reboot oem-78, I got some strange error (did not happen when I up'ed to 1.31) After getting 1.39, I flashed ViperX 3.2 again but I still have this error.
I'm completely out of ideas and am really close to giving up and selling my phone. Any help/advice on what I could do would be greatly appreciated!
Original post: http://androidforums.com/international-tegra-3-one-x-all-things-root/667919-random-reboots.html
Disable AOSP lockscreen in tweaks.
stifler05 said:
Disable AOSP lockscreen in tweaks.
Click to expand...
Click to collapse
Woah, no way. Is that it? It worked perfectly fine before I up'ed my hboot to 1.31 (always used the AOSP lockscreen). Have you encountered a similar issue? I'm trying this out now, will keep you posted.
I went through from 4.1.1 to 4.1.2, no problems, phone ran fine after update. Then went to 4.3, same thing. The phone was running fine so I booted back into recovery and removed Knox as well as manually rerooted by flashing SuperSU. Rebooted after that and still no problems, phone was running great. I then make a backup so I have a restore point of stock 4.3, rooted, and without Knox. I then go on and try to flash Dandroid and get a status 7 error and the phone was acting up after I rebooted.
At this point I go back to my backup and simply restore it and reboot again. The phone boots up, so that's a good thing. The problem is the GApps will not run and it continuously has a pop-up notification. The phone is rendered unusable like this. I got lucky once and was able to try and launch ROM Manager to see if fixing permissions would work, but it also closed. I tried flashing a 4.3 GApps package with no success and even tried reflashing the 4.3 update but got a status 6 error.
I'm at a loss here, does anyone have any ideas on this?
Not sure if this will help much, but even when plugged in via USB my computer will not recognize the device. The S3 states that it is connected and it does show up in Device Manager, it just won't show up as any kind of readable memory.
Trying to ADB sideload a rooted stock 4.3 ROM now. Any advice at all would be a help.
EDIT: I took a video (https://www.youtube.com/watch?v=tJ-eaQ_9mVI) of the problem so everyone can see what I'm talking about and I also found a fix.
I'm not sure what was causing it, but after a solid day of researching it online the closest thing I got was resetting app preferences and also trying to clear any data of Google apps. This seemed to sometimes slow the popups down for me or create a longer gap before they just came right back in full force. So, going off that small success I had managed to navigate my way over to Settings -> Accounts -> Backup and reset -> Factory data reset and ran that. The first boot after that took a very long time, I'd say a solid twenty minutes but it did work. No more error and everything has been going smooth for me since. A restore of apps with Titanium Backup also did not bring the problem back up again, so the device seems to be good as new again.
I apologize if any of these is out of line, I just thought I would follow up with a solution in case anyone else has this problem and can't seem to fix it. Maybe this will help them.
Hello everyone. Since the Title has character limit im gonna have to explain myself here better.
Ive had my HTC One M8 for 4 years now. Pretty much since it came out in 2013. I installed ARHD back in 2014 and its been working just fine ever since. A couple of months ago i decided to go back to 45.0. Everything went smooth and everything works just fine.
But a week ago the phone decided to just go woopdido and it wouldnt open up any apps in Playstore although i could still see them. So i tried to restart it and when i did it got stuck at the HTC Logo. I tried to restart it a few times but it kept getting stuck. I was super confused due to the reason that i havent really done anything with my phone besides since the day i installed ARHD 45.0. I got desperate so i reinstalled it but this time with 53.1 and that went fine too except for one fishy thing and that was that i remember before when installing ARHD, when it got 30% it wouldnt take 2-3 minutes for it to finally start installing the ROM. It would take a couple of seconds for it to start right away and be done.
After installing 53.1 phone worked just as fine except for the fact that it was slower than it has ever been before. Which was also weird. Either way. After a couple of hours of it working, setting up every app i needed i restarted it and again it was stuck at the HTC Logo. Welp i guess..
So after that crap i went back to 45.0 again. It went good and all except it keeps getting stuck at 30% for a while but whatever. Going back to 45.0 though didnt help. Keeps repeating the same crap after a while. After a restart when having the phone doing nothing for hours gets it stuck at HTC Logo again. I literally cannot do anything with it atm and i have no clue how to go further from here as i have not had this before.
I did another reinstall of 45.0 just now and this time i also wiped the System, Data all that which ive never done before hoping that it actually helps.
The HTC One M8 is rooted. S-Off everything you really need. The current TWRP version i have is 3.1.1.0.
Update: Apparently after reinstalling any version of ARHD and then updating SuperSU breaks the phone. Any ideas?
sp3tan said:
Update: Apparently after reinstalling any version of ARHD and then updating SuperSU breaks the phone. Any ideas?
Click to expand...
Click to collapse
I responded in the other thread you created. I also asked the mods to close one, to avoid any more confusion.
Thread closed.
Per the forum rules, please do not create duplicate threads or posts here on the site.
Cheers,
Magnum_Enforcer
FSM