Well here is the issue, I bought the HTC Thunderbolt awhile ago. I then rooted my phone but left the original ROM on it since the custom roms were not stable. I noticed verizon was pushing me some update and I just ignored them. I woke up today to see my phone rebooted with the screen on an exsclamation point. And then my Thunderbolt keeps rebooting itself now. I tried going into ROM Manager to download a Custom ROM but the phone just reboots before I can do it. I just installed Liquid Gingersense v1.6 rom with the MR2 OTA Radio which said it installed just fine after installing the Liquid Gingersense rom. I went through setting up the google account fine and after it booted to the main screen now my phone boots all over again, get stuck at htc screen for a bit then loads the phone fine then boots again. I am really not sure what the heck is going on. I am new to the MR2 OTA Radio since I cam from the Droid 1. So I hope it was not the install order I did it. I Have turned off the phone booted it with still same rebooting over and over issue. If anyone has idea's please let me know. Much appreciated. Thanks
I'm in the same boat. I have wiped the SD card and done a factory reset on the phone. It is no longer rooted, as I can't install and run apps requiring root permission. The update fails every time it tries to install, I also get the exclamation point android screen when the update tries to install. I'll take the update, I don't care. I just want a reliable phone again.
I'm seeing this issue come up a lot. Some of you folks seem pretty upset by it, and reasonably so. Search through the threads and you'll find you solution.
For those who are STILL running that antique and wildly obsolete ROM that the jcase rooting process leaves you with, I'd like to set a few facts before you. First of all, that ROM wasn't provided as a long-term daily driver. It's OLD and it's not very efficient with the battery. Second, simply because it's stock doesn't mean it's inherently stable. It's probably less stable than the custom ROMs out there. Third, the only ROMs really struggling with stability were the 2.01 RUU gingerbread builds. That build is obsolete, but not nearly as obsolete as the ROM that the rooting process leaves you with. The stability issues with the second OTA had nothing to do with the ROM, but rather, the radio that came with the RUU. In short, it's foolhardy to believe that custom ROMs are somehow inherently dangerous or unstable.
I'd like to suggest to whoever might be running the rooted ancient ROM the rooting process leaves you with to abandon it at your earliest convenience. Flash an MR2 radio, and if you like stock, use the stock rooted debloated ROM based on the 1.70 RUU. If you decide not to do this, and your phone auto-accepts the update, you'll probably lose everything on the phone trying to get it working again. Save yourself that hassle. Flashing ROMs isn't hard and people do it everyday.
I recently flashed CM10 to my skyrocket, and started getting random reboots. This started happening on every rom I tried afterwards, so I flashed back to stock ics and tried to start over. Now, even stock ics will reboot when I touch it (it will stay running if I don't touch the phone, but simple things like going to the app drawer will make it freeze and crash). It also will boot loop most of the time. I'd say 1 in 5 tries I can actually get it to boot.
Is there some way to clear it back to stock "more"? It seems that it should be recoverable, since it does actually boot up sometimes, but I've tried the normal factory resets/ formatting, and flashing back to stock to clear any leftover problems, and I don't know what else to try.
Ok guys. I browsed through the forums for this but can only find my issue on custom Roms. My issue is with my wife's phone on the Stock Rom. I rooted her phone the other night and since then her phone has no wifi signal til a reboot then her wifi comes back in nice and strong.
Is this a known root issue? Her phone is on 4.0.1, which I believe is the latest firmware for this phone to date. The only thing I did after rooting was, of course, install apps necessary for root and flashed a security program. Nothing else.
I have a friends S4 here that I rooted for them a while back and installed Xposes + Wanam to make their locked bootloader device a bit more useful. It worked perfectly for many months.
Recently they come back to me to tell me their phone dies very quickly when it is not in use and does get pretty warm. Battery panel shows that Android OS is using majority of percentage and not any more detailed. I realized that it was definitely OTA updated and that Xposed stated that modules were no longer installed nor did Superuser have root. I realized I made a mistake and forgot to disable OTA services.
What I have done so far: Re-rooted by flashing old kernel, flashed back to new kernel. Reinstalled Xposed modules and things SEEM to be perfectly fine. Two days later, the same thing is still happening. Android OS is definitely still hogging the CPU doing something in a loop.
I understand that a possible factory wipe from recovery MAY fix this issue unless System files are messed up and needing to use Odin to restore BUT I figure it'd be a great idea to come here and see if there's a quick fix that may be possible that could also help other readers that have run into the issue of accidentally receiving OTA while rooted.
Thanks for reading.
stevey500 said:
I have a friends S4 here that I rooted for them a while back and installed Xposes + Wanam to make their locked bootloader device a bit more useful. It worked perfectly for many months.
Recently they come back to me to tell me their phone dies very quickly when it is not in use and does get pretty warm. Battery panel shows that Android OS is using majority of percentage and not any more detailed. I realized that it was definitely OTA updated and that Xposed stated that modules were no longer installed nor did Superuser have root. I realized I made a mistake and forgot to disable OTA services.
What I have done so far: Re-rooted by flashing old kernel, flashed back to new kernel. Reinstalled Xposed modules and things SEEM to be perfectly fine. Two days later, the same thing is still happening. Android OS is definitely still hogging the CPU doing something in a loop.
I understand that a possible factory wipe from recovery MAY fix this issue unless System files are messed up and needing to use Odin to restore BUT I figure it'd be a great idea to come here and see if there's a quick fix that may be possible that could also help other readers that have run into the issue of accidentally receiving OTA while rooted.
Thanks for reading.
Click to expand...
Click to collapse
You could downgrade back to nc5 by flashing the tar file. Nc5 tends to be more stable and battery life is decent. I tried running nk1 for awhile, running into the same issues. I went back to nc5 running echoerom v39.1
Hello all.
New poster here, been coming here for some time though for the loads of great information and generally helpful people.
I'm having an issue with my Honor 5x, and I seem to be the only one i can find on this forum having this issue.
The issue that I am having is that I lose the ability to connect to the cellular networks (I am actually running dual-sim) when I load a custom ROM after the first reboot.. The first time this happened, it even lost the IMEI numbers (WTF). I restored from the backup I made, and tried again. I got the same result, after the first reboot, it can no longer find the cellular networks, and when i try to search for network providers, it gives me an error simply saying "Error searching for networks." Restore backup again, flash resurrection rom to see if maybe CM13 is just being stupid with my phone, got no signal right off the bat, and could not find networks.
At this point, I restored the stock recovery, and let it recover my phone to stock, which is where I am at the moment, since it works. Also noteworthy, that every time I restored from backup, the phone had no problems at all connecting to the cellular networks. as well, it never had an issue through all of this with connecting to WiFi.
Relevant Information:
Phone Model: KIW-L24
Build Number: KIW-L24C567B331
Emui Version: 4.0
Android Version: 6.01
Kernel Version: 3.10.49-g472a5b3
Location: United states
Carriers: Cricket, MetroPCS
Bootloader is unlocked
I have not restored root access
I have Flashed TWRP and made a full backup (again)
I'm getting the feeling that it is due to to something that I have forgotten, but I can't seem to think of anything.
Help?
So close, but no cigar.
Still having issues, here's what Ive done so far:
Restored phone completely to stock, leaving only an unlocked bootloader.
Loaded the latest version of TWRP
Re-Rooted the phone
Made a complete backup of the phone, with no partitions left unchecked, in case of a catastrophic failure
Used TWRP to wipe Dalvik/ART, Cache, System, & Data
Loaded the latest CM13 nightly build
Loaded GApps pico version (I don't use many of the Google apps, so I prefer to download the ones that I want)
Wiped Dalvik/ART
Rebooted Phone
At this point, the phone went about its first boot business, loading stuff in the background, optimizing apps for the first use.
I skipped almost all of the first-time setup stuff, no sense in setting it all up if it didn't work this time as well, but connected to WiFi, selected the primary SIM, and activated data on that SIM. This is all normal from my other attempts as well.
Rebooted the phone, when it came back up, I had signal on my phone, and it successfully sent and received messages.
Added my Google account, rebooted again, not getting signal. checked network operator settings, and I get the message stating "Error searching for networks" for both SIM cards.
Removed Google account, changed SElinux settings to permissive, soft reboot, no change.
In the past, I did try wiping Dalvik/ART & cache once this happened, but the only thing that changed is that it caused the process com.android.phone to crash on me repeatedly.
Currently digging around on the net some more to see if maybe there's something that I missed.
Try 1 Sim? Its some bug with dual sim i guess
I will try that when I get a chance, I am currently trying to restore the phone back to stock again after another failed attempt.
Also noteworthy, I had it completely lose the sim cards on me after a restore to the working stock backup that i made earlier in the day yesterday, I had to completely revert to stock (Restore stock recovery, let it rest the phone to stock) then the SIM cards started working again.
This is starting to get rather frustrating.
I'll keep you updated, as I've kinda decided to make this a log of sorts of my experience with this.
Hellspawn119 said:
I will try that when I get a chance, I am currently trying to restore the phone back to stock again after another failed attempt.
Also noteworthy, I had it completely lose the sim cards on me after a restore to the working stock backup that i made earlier in the day yesterday, I had to completely revert to stock (Restore stock recovery, let it rest the phone to stock) then the SIM cards started working again.
This is starting to get rather frustrating.
I'll keep you updated, as I've kinda decided to make this a log of sorts of my experience with this.
Click to expand...
Click to collapse
Did u fixed it? im having the same issue, although i dont have a backup.....
Tried updating to stock marshmallow first before installing CM?
stanley08 said:
Tried updating to stock marshmallow first before installing CM?
Click to expand...
Click to collapse
I tried that, see my thread http://forum.xda-developers.com/honor-5x/help/network-help-t3445510
i dont really know what to do, could the problem be MODEM.img???
Im having the exact same Issue, All roms loose the SIM card so I loose all signal and basically everything... a restart sometimes helps it, tried installing different ROMS, going back to STOCk 5.0.1 or 6.0.1 nothing Helps... NO clue what to do.
Same issue here. Happens on every Rom.
EDIT: Using KIW-L21 (UK)
Unlocked, single sim.
Maybe the it has something to do with modem.img