Hi team
I recently purchased an ex Demo HTC One M9 as a cheap replacement to my broken Galaxy S7 Edge, as soon as I received it I decided to flash TWRP and a new ROM on it. I was able to unlock the bootloader via HTCDEV.com easily enough and I was able to flash TWRP onto it without issue but when it came to the ROM's I ran into many problems.
Any version of Android that is Nougat or lower would not boot, the phone would go straight to the white bootloader screen every time. Oreo and Pie ROMs were able to boot but I ran into separate issues with them, I could not make or receive phone calls as the whole phone would freeze and there was no audio in from the speaker. I was also unable to play any videos in Facebook, YouTube, Snapchat etc.
I tried every single ROM available here on XDA and ran into these issues. I stupidly also did not make a TWRP backup of my system so it was quite hard to revert back to what it came from factory, I managed to get a stock Marshmellow running thanks to a User here posting a TWRP backup so thanks.
Is anyone able to help me with upgrading to Nougat? I would really like to get the Viper ROM working if possible, is it a known issue getting stuck in the bootloader menu every time?
I've tried just updating through the OTA process in the menu but it says there is no update file available.
Cheers
Related
Gonna try my best to give as much information as I can to make it easier for anyone good enough to try and help me with this. So I have an HTC One M9, from Sprint right here in the good old US of A, and it was working fine until I got the OTA Marshmallow update. At that point, apps started crashing like crazy (even after all were updated) and the status bar at the top of the screen and navigation buttons at the bottom would randomly disappear for several seconds after pressing the volume buttons, even after wiping the cache for both the system as well as the individual apps in question.
"No problem," I thought, "I'll just root it and install a custom ROM like I have with all my Android phones in the past." So I did that and tried Android Revolution, ICE, and ViperOne (all the latest versions), and every one of them had the same issues with programs crashing, the volume buttons messing up the screen, and so on. Actually, I couldn't even get through the setup wizards for any of them because those kept crashing too, and I had to use TWRP to rename the HTCSetupWizard.apk just to get to the home screen. Once there, my home button was inoperable, and no notifications or usual buttons like WiFi, Bluetooth, etc appeared when I pulled down on the status bar (which I discovered is what Android does if you don't complete the setup wizard).
At this point, I thought, "Well, maybe it's just a problem where my phone doesn't like Marshmallow for some reason. Let me try downgrading to Lollipop and see what happens." So I got the latest Lollipop versions for each of the aforementioned Custom ROMs, and they all ran smooth as silk, which tells me it's not an issue with faulty or damaged hardware. Only problem was that mobile data wouldn't work, on either LTE or CDMA settings.
I tried changing network modes, popping my SIM card in and out and rebooting in various combinations, but none of it worked. I couldn't even get into APN settings since the phone couldn't seem to detect my SIM card and had the APN menu greyed out. I thought I might have somehow damaged the SIM card with all the time I spent screwing around with the phone, but just to see what happened, I flashed a Marshmallow ROM back onto the phone and, sure enough, LTE service was right back.
I did some more research and saw that the issue may lay in the fact that the firmware (which is currently OS version 3.41.651.4) is not usable for Lollipop OS versions, and since my phone is S-ON (and I'm really not interested in spending $25 to S-OFF it), I'm not able to downgrade the firmware or, I assume, the radio firmware (if that's something you can even do separately from the "regular" firmware. Currently version [email protected]).
At this point, I'm really not sure what to do, and could use some guidance. I feel like my options basically boil down to the following:
1)Find a way to make Marshmallow ROMs more stable, possibly by reinstalling the firmware or some other method someone here might know that I don't,
2)S-OFF my phone, downgrade my firmware to something Lollipop can work with, and try a Lollipop-era ROM (not ideal), or
3)Go back to stock and hope Sprint pushes down an update my phone can use.
After going through all that, does anyone reading this have a recommendation for which of these options would be best (and how to go about them), or possibly offer other ideas I haven't come up with during the week and a half I've been researching and trying to fix it myself? I'm not hellbent on any particular option, I just want my phone to work (all of it) without constant crashes and glitches. Thank you to anyone who read all that and is still moved to offer help!
If you can run lollipop based roms you'd be on Lollipop firmware.
If you're going to mess around with aftermarket software you need s-off. If you don't s-off then you are risking unrecoverable bricks.
Sent from my HTC One M9 using Tapatalk
Okay, so if I'm on Lollipop firmware, would it stand to reason that that's why I'm having trouble running Marshmallow ROMs, including the stock ROM from Sprint? If so, what's the best (and safest) way to update it?
New to the world of Custom ROMs. A week ago I installed CM 13 which took great courage on my part and wanted to share my experience, issues and discuss possible solutions.
My phone had the latest lollipop on it. And McCafee locked. The steps that worked for me where
1) Did a factory reset and bumped into mccafee.
2) Tried download mode but kill switch was enabled.
3) Rebooted the phone to face mccafee, tried 123465 pin which worked.
4) Disengaged McCafee but not before transferring ownership to my email.
5) Tried rooting didnt work with any method.
6) Rolled back to d software version stock lollipop.
7) Rooted with PurpleDrake
8) Replaced with CM recovery didnt work.
9) Replaced with TWRP and rebooted directly to recovery
10) Installed CM and gapps mini. Worked fine. Voila!
Issues:
1) No Custom recovery sticks, whenever I flash with a custom recovery like TWRP or Clockwork. I have to reboot into recovery immediately or the custom recovery is replaced by stock. It happens on every second reboot.
My concern is here if I get stuck into bootloop and dont have a custom recovery I might not have any other option than the stock ROM which does a full reset. How can make TWRP stick forever?
2) After installation of Custom ROM there have been random reboots, I suspect there is something here with phone app or voice. So far the reboots have been when I try to call using fb messenger, appear.in and phone app itself.
Is there a guide that tells me how to track this down?
Can I install a newer Nightly and hope this get fixed?
How can I retain my apps and data when installing a newer nightly? since all guides ask to wipe everything :S
I have a backup of system and data partitions, can I use that with other ROMs.
What ROMs have a better chance of fixing this issue?
Coudnt find Stock M for D850. Why arent those available?
Should an Official ROM be more reliable than CM for this?
3) Bad signal reception so far. It may be a generic g3 issue.
Can I hope that this issue be fixed with a different ROM or updates from Cynogen?
Someone said you may have to flash the radio partition. My question is where can I get a brief understanding of what partitions there are in android and which are risky. Which ones can be replaced, backedup and replaced back.
4) Whenever the phone reboots, it gets stuck into bootloop unless I remove the SIM card. Then I power off and install SIM Card and reboot and it boots fine.
I am already tracking CM changelog for something important. Cant post urls as of now :S
So I have a T-Mobile LG G4 that like every other G4 had the bootloop problem when I got it. I sent it to LG and they promptly fixed the issue. My current issue has nothing to do with the bootloop I believe.
Because the G4 wasn't getting the Android N update fast enough and also because I wanted to play around with Android's full potential, I decided to root the phone a little over two weeks ago. The process worked and I decided to install a custom ROM. That also worked. I have installed four or five custom ROMs built on Android 7.1 without issue, or at least without any major issue.
However last night I decided to flash Genysis ROM on Android 6.0 because I wanted to play with Xposed. I made a full Nandroid backup of the CRdroid ROM it had been running and then wiped and flashed it using TWRP. When I installed the ROM it didn't work for whatever reason, freezing up and frequently becoming unresponsive. Over about 30 minutes I managed to enable USB debugging and reboot it to recovery (why I didn't shut factory wipe it from bios I'm not sure).
Now any ROM I try to install doesn't boot up. It never gets past the OS loading screen with the ROM logo. On 6.0 ROMs it says it has optimized the apps but gets stuck on starting them. The Nandroid backup I made does the same thing, even ones I made early that day and one from several days ago.
The backups had that one app installed that shows the logcat while booting up and while I'm no expert it seems to get a loop loading the audio drivers. I don't know if that's the cause or if it's just coincidental, as I've never heard of audio drivers preventing a boot, albeit my experience is with Windows PCs.
If it would help I can attempt to take a picture of the screen while stuck, although the text moves very fast. I can access the TWRP recovery just fine but don't know how to/if you can dump logs.
Any help would be much appreciated! I can attempt to supply an information that may be needed as well.
merger3 said:
So I have a T-Mobile LG G4 that like every other G4 had the bootloop problem when I got it. I sent it to LG and they promptly fixed the issue. My current issue has nothing to do with the bootloop I believe.
Because the G4 wasn't getting the Android N update fast enough and also because I wanted to play around with Android's full potential, I decided to root the phone a little over two weeks ago. The process worked and I decided to install a custom ROM. That also worked. I have installed four or five custom ROMs built on Android 7.1 without issue, or at least without any major issue.
However last night I decided to flash Genysis ROM on Android 6.0 because I wanted to play with Xposed. I made a full Nandroid backup of the CRdroid ROM it had been running and then wiped and flashed it using TWRP. When I installed the ROM it didn't work for whatever reason, freezing up and frequently becoming unresponsive. Over about 30 minutes I managed to enable USB debugging and reboot it to recovery (why I didn't shut factory wipe it from bios I'm not sure).
Now any ROM I try to install doesn't boot up. It never gets past the OS loading screen with the ROM logo. On 6.0 ROMs it says it has optimized the apps but gets stuck on starting them. The Nandroid backup I made does the same thing, even ones I made early that day and one from several days ago.
The backups had that one app installed that shows the logcat while booting up and while I'm no expert it seems to get a loop loading the audio drivers. I don't know if that's the cause or if it's just coincidental, as I've never heard of audio drivers preventing a boot, albeit my experience is with Windows PCs.
If it would help I can attempt to take a picture of the screen while stuck, although the text moves very fast. I can access the TWRP recovery just fine but don't know how to/if you can dump logs.
Any help would be much appreciated! I can attempt to supply an information that may be needed as well.
Click to expand...
Click to collapse
why not start from 0 and flash latest KDZ with LGUP.
https://forum.xda-developers.com/tmobile-g4/development/h811-kdz-file-t3607807
For sure I'll try that. I'll let you know if it works, thanks!
Follow up- I eventually found the free time to work on this and flashing the kdz worked! I actually had to use LG Bridge as LGUP only found my device as unknown.
Thanks for the help! Back to flashing ROMs for me.
I had the latest 6.0.1 samsung rom (CPK2) which was giving me problems with freezing. So I am trying to upgrade to an 7.x.x rom, either RR, AIPC, or Lineage. But none of these roms allow the T800 boot to get beyond the initial splash logo screen. I am using latest TWRP, 3.1.1 to wipe and install rom. I am not getting any install errors. Boot loader is confirmed as CPK2.
FYI, I am able to get back to the samsung rom by reflashing it with Odin.
Update 1: In the final attempt of upgrading I installed the official 6.0.1 fw which boots fine unlike the aforementioned alternatives (very strange). However, lock ups and now screen blanking more frequent. This time wiped everything including storage. It looks more like a hardware issue but I wonder if this could be malware even after wiping everything. I will have to take this in for repair but have little hope of solving this problem.
mach281 said:
I had the latest 6.0.1 samsung rom (CPK2) which was giving me problems with freezing. So I am trying to upgrade to an 7.x.x rom, either RR, AIPC, or Lineage.
Update 1: In the final attempt of upgrading I installed the official 6.0.1 fw which boots fine unlike the aforementioned alternatives (very strange). However, lock ups and now screen blanking more frequent. This time wiped everything including storage. It looks more like a hardware issue but I wonder if this could be malware even after wiping everything. I will have to take this in for repair but have little hope of solving this problem.
Click to expand...
Click to collapse
My wife has the US Cellular 10.5 variant (T807R4). It was freezing so frequently it had become almost unusable for anything but watching videos. Rooting and disabling most of the Samsung apps did not fix the problem. I wiped the system with TWRP only to discover that none of the custom ROMs would work on this model. I downloaded and flashed the stock Samsung MM firmware (and it sat on the opening splash screen for at least 15 minutes before it finally booted up) and for the hour I used it after setting it up, I had no problems. I had previously cleared the cache with Titanium Backup and that also seemed to be a temporary fix. My conclusion is that something is happening when the cache fills up that causes the freezes but I'll need more data to say that for sure.
Just an update: I was going to have the hardware looked at so I wiped everything including the storage. But when I took it to the shop and was asked to demonstrate the freezing the tablet wouldn't. So I took it back and it was running OK until a couple weeks later when the same problems reared there heads.
Somehow I managed to get a 7.1.2 installed and the T800 is running great...so far. I'll post back if the freezing starts again.
mach281 said:
Just an update: I was going to have the hardware looked at so I wiped everything including the storage. But when I took it to the shop and was asked to demonstrate the freezing the tablet wouldn't. So I took it back and it was running OK until a couple weeks later when the same problems reared there heads.
Somehow I managed to get a 7.1.2 installed and the T800 is running great...so far. I'll post back if the freezing starts again.
Click to expand...
Click to collapse
Please explain the steps to install 7.1.2 (and which ROM you used) and update on the freezing issue. Most of the freezing issues I have read about seem to be on LTE variants (SM-T807x) so I was about to buy a wifi only (T800) tablet, thinking that would be a solution to the problem. If that's not the case, then I shouldn't waste my money.
The instructions for installing a non-stock ROM are on the dev's host page in Tab s forums. I first tried Resurrection Remix and now am on LineageOS. It was only after I wiped the internal storage area that I was able to get past the 7.x.x boot screens.
I found the stock rom 6.0.1 freezing issue persistent. I believe the problems started for me with XAR H4 and really picked up with K2 (roms supplied by sammobile). The tablet would frequently just freeze while working in an app: the screen and hardware buttons would not respond at all. Never had that problem with Android 5. The only thing I was able to do to unfreeze it was to reboot into download mode then restart the OS from there. I sometimes found that if I left it frozen overnight it would unfreeze itself by morning.
Ever since the MM update, my wife's SM-T807R4 (US Cellular version) freezes frequently when browsing and using any app which requires touchscreen input. It's almost unusable unless one doesn't mind closing and opening the case every 2 or 3 minutes (or hitting the power button twice.) I have recently rooted it and disabled many of the Samsung apps as well as some Google apps we don't use. It hasn't helped. I have not yet flashed TWRP but I have instructions on how to do so.
I don't know if the MM update caused the problem or there's a hardware issue that just didn't seem to arise until after that update. In any case, I'd like to return to Lollipop and see if that improves things. Once TWRP is available, can I just wipe everything and flash the Lollipop ROM with TWRP or do I have to flash it with Odin? Anything else I need to do to prepare?