I love Cyanogenmod, very much so. I downloaded the stable 10.1 build for my phone and it was mostly rock solid. When 10.2.1 come around I was pumped. I downloaded it and immediately encountered force closes out the bum. I switched back and a month later tried again. It was a slightly better experience as I realized I forgot to flash the 4.3 Gapps with my original attempt, but force closes cluttered my screen daily. I want to be able to upgrade, but the ROM just seems completely unstable for my phone. Has anyone experienced these things on their phone? Has anyone fixed these problems? Can anyone recommend the most stable and most up-to-date ROM even though stable and up-to-date rarely go hand in hand.
stjake said:
I love Cyanogenmod, very much so. I downloaded the stable 10.1 build for my phone and it was mostly rock solid. When 10.2.1 come around I was pumped. I downloaded it and immediately encountered force closes out the bum. I switched back and a month later tried again. It was a slightly better experience as I realized I forgot to flash the 4.3 Gapps with my original attempt, but force closes cluttered my screen daily. I want to be able to upgrade, but the ROM just seems completely unstable for my phone. Has anyone experienced these things on their phone? Has anyone fixed these problems? Can anyone recommend the most stable and most up-to-date ROM even though stable and up-to-date rarely go hand in hand.
Click to expand...
Click to collapse
Look in the CM11 thread, the nightlies are pretty stable for the most part and most us using it use it as a daily driver. You MUST perform a full wipe when installing a ROM, even when moving between point releases. If not, you'll encounter problems. GApps must also be flashed after the ROM has been flashed (assuming you want to use Google)
CWGSM3VO said:
Look in the CM11 thread, the nightlies are pretty stable for the most part and most us using it use it as a daily driver. You MUST perform a full wipe when installing a ROM, even when moving between point releases. If not, you'll encounter problems. GApps must also be flashed after the ROM has been flashed (assuming you want to use Google)
Click to expand...
Click to collapse
Yeah I figured that I need to wipe everything and install the proper GApps after my first attempt at 10.2 which to my credit I did do on my second try. Is there a particular nightly release that seems more stable than the rest? To put this in more context, I travel alone from college to various other places often a bit and my college is situated in almost a black hole of service for Verizon so I tend to take reliability over cutting edge even though I very badly want the newest and greatest. I'm on spring break so I'll try the newest nightly and back up my phone. Luckily I have a ton of space on my phone so I can always have a stable back up ready to be flashed on the fly.
stjake said:
Yeah I figured that I need to wipe everything and install the proper GApps after my first attempt at 10.2 which to my credit I did do on my second try. Is there a particular nightly release that seems more stable than the rest? To put this in more context, I travel alone from college to various other places often a bit and my college is situated in almost a black hole of service for Verizon so I tend to take reliability over cutting edge even though I very badly want the newest and greatest. I'm on spring break so I'll try the newest nightly and back up my phone. Luckily I have a ton of space on my phone so I can always have a stable back up ready to be flashed on the fly.
Click to expand...
Click to collapse
By their very nature, Nightlies are not considered stable in the strictest sense of the word. For most of us, they have been. But if you need reliability over cutting-edge, I'd stick with 10.2 or one of the CM11 Milestone builds (however, the RAZR HD only has one that I know of, CM11-M2).
My personal take is that given you're in an area with poor reception, choosing CM11 over CM10.2 (for example) wouldn't give you any better results over the other. Signal is signal.
My suggestion, given your circumstances and criteria, would be to stick with 10.2 but do a FULL backup via Recovery of your stock ROM (or whatever you're using instead of CyanognMod) and then do a FULL wipe of the following (and only these):
- user data
- /system partition
- /cache partition
- dalvik cache (usually found under Advanced in CWM recoveries)
Your phone will be in an unusable state after this. From here, still in Recovery, flash CM10.2 and then the appropriate GApps (make sure you choose the right one; a 4.4.2 GApps isn't suitable for a 4.3 OS) and reboot. If memory serves, CM10.2 is Android 4.3.1
If you're still having problems, you can restore your backup in Recovery or worst case, RSDLite the appropriate SBF for your phone to return to the carrier-stock ROM. But be aware if you chose the RSDLite path, you will lose everything. Basically it'll be like day-1 when you got the phone
Unroot help!!!
Hi I am trying to figure out how to unroot my Droid Razr HD...I bought it used from my buddy who upgraded and before we met up to make the deal I didn't know till after; that he rooted it and won't tell me how to unroot. I have only ever rooted one phone with his help and that was my thunderbolt. This phone is running CM 11-20140218-NIGHTLY-xt926. I want to bring it back to stock rom but have yet to find anyway to do that...it would be awesome if you guys could help me!!
Lanevox said:
Hi I am trying to figure out how to unroot my Droid Razr HD...I bought it used from my buddy who upgraded and before we met up to make the deal I didn't know till after; that he rooted it and won't tell me how to unroot. I have only ever rooted one phone with his help and that was my thunderbolt. This phone is running CM 11-20140218-NIGHTLY-xt926. I want to bring it back to stock rom but have yet to find anyway to do that...it would be awesome if you guys could help me!!
Click to expand...
Click to collapse
Find the FXZ you want to flash and use RSD or House of Moto to flash it.
Related
So I've been using Revolver for a few months...
And I saw these new ROMs and I was wondering if they are worthy to switch from Revolver...
(IF anybody tried these ROMs PLEASE post your opinion)
These are the ROMs:
[ROM] CM9 with Cornerstone
[ROM][Nightly][ICS] Team Eos Transformer Nightlies (tf101)
[ROM][ICS] Codename Android v1.5.0
Plus.. I want "Cornerstone" and Revolver doesn't have it!
Thanks in advance...
If you haven't updated to the new revolver 4 then you are still on honeycomb.
And cornerstone is a gimmick right now, it breaks a lot of features and apps don't always run correctly in the cornerstone windows..I will be surprised at this point if cornerstone survives onto android 5.0, google and Onskreen seem to be at odds over it's usefulness and how to implement it into ROMs without breaking market access to keep users from leaving negative feedback for 'broken apps' that don't work simply because they have cornerstone installed. I have a feeling cornerstone is either about to die, or be neutered beyond usability, they have already removed features and hinting at removing more to make it compliant to Google's standards. In other words, enjoy cornerstone, but I wouldn't get dependent on it, it may not be around (at least in the same form it is now) for very long.
luna_c666 said:
If you haven't updated to the new revolver 4 then you are still on honeycomb.
And cornerstone is a gimmick right now, it breaks a lot of features and apps don't always run correctly in the cornerstone windows..I will be surprised at this point if cornerstone survives onto android 5.0, google and Onskreen seem to be at odds over it's usefulness and how to implement it into ROMs without breaking market access to keep users from leaving negative feedback for 'broken apps' that don't work simply because they have cornerstone installed. I have a feeling cornerstone is either about to die, or be neutered beyond usability, they have already removed features and hinting at removing more to make it compliant to Google's standards. In other words, enjoy cornerstone, but I wouldn't get dependent on it, it may not be around (at least in the same form it is now) for very long.
Click to expand...
Click to collapse
No, I'm using Revolver 4
Good to know about that!
I wanted to try those ROMs for myself but it's really troublesome wiping everything then restoring again! which I did twice to get ICS to work! and I still have random shutdowns!
So I wanted to ask if anyone tried them... and how are they compared to the Revolver!
Do a backup of your apps and data, then do a nandroid backup through recovery. If you are currently on HC and then you upgrade to ICS, you will need to make sure that you can go back to your previous HC rom if need be by having a nandroid backup and a way to flash the corresponding HC kernel. The safest way to do this is to perform the nandroid restore through recovery, do not reboot, after restore, then reflash your HC rom's zip file. If you do not have a TF that has sbk1 and can use the nvflash utility, then you run a risk of hard bricking your tf when u try to go back to HC. So the safest bet is to stick with ICS once u upgrade.
Do a full wipe and download and try every rom you are interested in and try them out yourself. Perform the above recovery steps if you want to go back.
cavsoldier19d said:
Do a backup of your apps and data, then do a nandroid backup through recovery. If you are currently on HC and then you upgrade to ICS, you will need to make sure that you can go back to your previous HC rom if need be by having a nandroid backup and a way to flash the corresponding HC kernel. The safest way to do this is to perform the nandroid restore through recovery, do not reboot, after restore, then reflash your HC rom's zip file. If you do not have a TF that has sbk1 and can use the nvflash utility, then you run a risk of hard bricking your tf when u try to go back to HC. So the safest bet is to stick with ICS once u upgrade.
Do a full wipe and download and try every rom you are interested in and try them out yourself. Perform the above recovery steps if you want to go back.
Click to expand...
Click to collapse
I'm on ICS!
I've already backed up everything from TB but It does take a very long time to restore! (250+ Apps)
And to test the ROM properly I have to restore my data and use the ROM for couple of days!
BUT If somebody already tried one of those ROMs then I don't have to do all of that...
Hi,
I am also have a problem with Asus Base ROM as well.
So I change from Revolution HD to EOS nighlies with Cornerstone version 4.
Overall is great, it's very fast. However, I still have some problem of random not-wake up and battery drain after restart.
It may be my individual problems but just for your consideration.
ROM to use
There is always going to be some sort of wok when you are trying out different ROMs.... Somewhat nature of the beast.
I have run revolution HD and codename 1.5 so far and prefer codename at this point. Codename is still being upgraded quite often... So maybe more work than revolution.
According to other threads, these random reboots will probably be in every tf101 ICS rom as they are due to old nvidia drivers delivered by asus.
I know what you mean i have a 12kb/s internet connection and downloading roms to try is a pain. I was on revolver 3 and very happy stable fast and reliable. Upgraded to revolver 4 and had to many small problems and it all seemed a little tired and slow. Tried cornerstone and thought nah! Whats the big deal, cant change window position and half the apps dont work. I am now on codename 1.5 and although their are a few little problems it hasn't reebooted got stuck in a loop or slowed to a crawl. Loads of extra settings and the inbuilt launcher is great. So far impressed and will be sticking with it.
Ok thanks to everyone!
I guess I'm gonna be testing out "Codname" later...
Although I'm still waiting for the Official CM9 to come out!
+1 for codename android
there is the best 3d power for me.
Sent from my Xperia X8
Hello, all.
I have a T-Mobile Blaze 4G with rooted stock ROM (Gingerbread), flashed radio version T989UVMC6, manually debloated and dewizzed. I'm running Halo launcher and Busybox Free version 9.6.
Since almost the first day I've had this phone, it would occasionally force close the phone process, usually when hanging up the phone with the Bluetooth radio on and paired with an earpiece. It happened bone stock, rooted, after I changed the modem, whenever. It seemed to happen less often after I changed the modem. The process always starts back up, but the Bluetooth device connection and system sound controls are wonky (unusable) until the phone is rebooted.
The only thing that seems to stop it is running Zepplinrox's V6 Supercharger script. That, however, occasionally freezes the entire system when trying to open certain apps, requiring a reboot. I've run earch after search on this subject, and nobody else seems to have this problem. The only thing I haven't tried is wiping the whole thing and flashing a custom ICS or JB ROM. I tried Dark Knight ver. 8 and hated it pretty much instantly.
I have two questions. Number one; Will flashing a custom ROM fix this situation? I figure that this must be a problem with the crappy stock Samsung ROM. Number two; Which ROM is fully functional and stable? I'd really like to keep this phone dependable. I don't care about the latest and greatest funky cool features that are hit-or-miss at best. I just need dependable, fast and functional.
Since you have been having issues for a while, I would suggest starting fresh. With a few runs of black hole wipe from cwm. Add a run of the gremlin remover for extra cleanliness. Then a flash of the latest ICS rooted stock rom and kernel, for reliability.
Black hole wipe. http://forum.xda-developers.com/showthread.php?t=1721057
Gremlin remover, FSC http://forum.xda-developers.com/showthread.php?t=2218713
Uvmb1 ics ROM http://forum.xda-developers.com/showthread.php?t=2329081
Romman0 said:
Since you have been having issues for a while, I would suggest starting fresh. With a few runs of black hole wipe from cwm. Add a run of the gremlin remover for extra cleanliness. Then a flash of the latest ICS rooted stock rom and kernel, for reliability.
Black hole wipe. http://forum.xda-developers.com/showthread.php?t=1721057
Gremlin remover, FSC http://forum.xda-developers.com/showthread.php?t=2218713
Uvmb1 ics ROM http://forum.xda-developers.com/showthread.php?t=2329081
Click to expand...
Click to collapse
I'll definitely go for the rooted version! Does it matter what order in which the ROM and the kernel are flashed? Also, I take it from the name of the download link that I'll have to go through the process of de-bloating this thing again. S'okay, I actually enjoy that part, but I don't want to screw it up since I've not messed with anything newer than GB. Is there a good guide somewhere on the forum for apps that can be dumped safely? I know there was one for GB stock root.
Thanks for the response.
ionizd said:
I'll definitely go for the rooted version! Does it matter what order in which the ROM and the kernel are flashed? Also, I take it from the name of the download link that I'll have to go through the process of de-bloating this thing again. S'okay, I actually enjoy that part, but I don't want to screw it up since I've not messed with anything newer than GB. Is there a good guide somewhere on the forum for apps that can be dumped safely? I know there was one for GB stock root.
Thanks for the response.
Click to expand...
Click to collapse
Flash the ROM then the kernel, rewipe cache and davlik, then profit.
The most recent ICS debloating thread. http://forum.xda-developers.com/showthread.php?t=2183726&highlight=debloat
Romman0 said:
Flash the ROM then the kernel, rewipe cache and davlik, then profit.
The most recent ICS debloating thread. http://forum.xda-developers.com/showthread.php?t=2183726&highlight=debloat
Click to expand...
Click to collapse
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
ionizd said:
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
Click to expand...
Click to collapse
All the AOSP ROMs for the Blaze needs GAPPs. And yes. The latest CM10 nightly is stable. And you said CM10 ICS? CM9 is ICS and CM10 is Jellybean.
ionizd said:
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
Click to expand...
Click to collapse
The stock roms don't require gapps, but like Wolf said the cm10 jb variants do.
If your willing to use cm10 it is very stable. Just use the latest CM10 nightly and not the old stable version.
Here http://forum.xda-developers.com/showthread.php?t=1922935
The jb gapps 20121011 http://goo.im/gapps/gapps-jb-20121011-signed.zip
xWolf13 said:
All the AOSP ROMs for the Blaze needs GAPPs. And yes. The latest CM10 nightly is stable. And you said CM10 ICS? CM9 is ICS and CM10 is Jellybean.
Click to expand...
Click to collapse
Of course. I get a bit confused ever since people started talking about 10.1.
Okay, I went ahead and installed the stock rooted ROM with the stock kernel. Went through the debloating process (mostly, there are some apps that I'm not sure I can do without so they stay for now), and did some customizing. I'm seeing a bit more battery drain. Is this an issue with ICS or do I need to try another kernel or supercharge the phone? I also have this crazy issue with ROM Manager ver. 5.5.3.0. It tells me that there is an updated version of Clockworkmod Recovery, but it freezes when I try to flash from ROM Manager. Also, ROM Manager freezes when I try to reboot into Clockworkmod Recovery. Maybe I need to test a bit more before I mess with it any more.
**EDIT** Well, it looks as if my CWM recovery installation is corrupted. Can I reflash it without messing up my current ROM?
ionizd said:
Okay, I went ahead and installed the stock rooted ROM with the stock kernel. Went through the debloating process (mostly, there are some apps that I'm not sure I can do without so they stay for now), and did some customizing. I'm seeing a bit more battery drain. Is this an issue with ICS or do I need to try another kernel or supercharge the phone? I also have this crazy issue with ROM Manager ver. 5.5.3.0. It tells me that there is an updated version of Clockworkmod Recovery, but it freezes when I try to flash from ROM Manager. Also, ROM Manager freezes when I try to reboot into Clockworkmod Recovery. Maybe I need to test a bit more before I mess with it any more.
**EDIT** Well, it looks as if my CWM recovery installation is corrupted. Can I reflash it without messing up my current ROM?
Click to expand...
Click to collapse
Yes, with Odin, in the Dev forum
BTW, stay away from ROM Manager with our device. I've softbricked so many times because of it, it's ridiculous
jparnell8839 said:
Yes, with Odin, in the Dev forum
BTW, stay away from ROM Manager with our device. I've softbricked so many times because of it, it's ridiculous
Click to expand...
Click to collapse
Used this method http://forum.xda-developers.com/showthread.php?t=2011585, it worked well. Still have the battery drain issue, though. : /
ionizd said:
Used this method http://forum.xda-developers.com/showthread.php?t=2011585, it worked well. Still have the battery drain issue, though. : /
Click to expand...
Click to collapse
Since you have it setup, except for battery life. I would make a backup, then try a mod one at a time and see if any help. Also check the battery stats to see if anything of is seen. ICS will use more juice than GB, generally.
I would suggest Nos/direct injection, supercharger, or cross breeder. I would use one and see, then restore and try another.
http://forum.xda-developers.com/forumdisplay.php?f=565
Some time later...
I've been using the stock rooted ICS ROM since my last post, debloated and dewizzed of course, with Holo Launcher and T989UVMC6 baseband version flashed. Just over a month has passed, and I have good news!
I FREAKING LOVE THIS PHONE!!!
All of the force close and freezing issues have vanished, the phone's battery lasts almost as long as it did on GB, it's WAY more user friendly, and the phone is as fast as it ever was.
The bad news is that my wife got a GS4 and I lust after it now. : /
Thanks to everyone for their help!
I dont know if its my phone or what but I haven't had any luck with AOSP ROMS on this phone. It seems like there's always some sort of bug that just kills it. I flashed a CM10.2 rom that felt like speed of lightning but was bugging out. I tried ecilpse and some others but all were to buggy for me. I recently tried to flash liquid cause I wanted to run something else other than touchwiz but it ruined my phone and now I cant flash custom ROMS(i have a help thread up..feel free).. Anyone else having bad luck on these AOSP ROMS
Not what you want to hear, but I'm having no issues with flashing new ROMs. I'm only using LiquidSmooth and waiting/hoping for a 'complete' 4.3 version, but again, no problems with flashing to a new ROM. I have been running LS2.9 (4.2.2) for several weeks and on Sunday flashed up to LS2.10 (4.3) but went back to 2.9 because when I mirror my phone on my AppRadio3, it doesn't auto-rotate my screen to landscape, so I have a portrait orientation of my phone on the radio display, which makes it so small as to be unusable.
I don't recall what method I used to root my phone, but I'm using TWRP 2.6.3 to perform a) a clean wipe every time (Factory Reset + System), then b) install the new ROM, and c) a final reboot back in to recovery and flash the latest gapps image. Does it take a little longer to follow this process? Sure, but it's a reliable process that means I don't have issues afterwards to mess with, so the extra time spent on the front end is worth it to me.
I've had moderate success with the AOSP ROMS. Each one seems to have it's own small bugs, but the AOSP ROMs that I've tried didn't have anything that ruined functionality. Been running Dirty Unicorn ROM for the past couple days and it is really solid. Haven't noticed any issues at all with it yet.
It's got to be your downloads or install process. Do you check MD5? If no then start. Remember just wipe data for each install. Updater-script in ROM zip wipes system for you. Cache resides in data. Do NOT restore system data using TiBu. Other than that I don't know what else to tell ya bud :/
Sent from my SCH-I535 using Tapatalk
Haven;t had any trouble with AOSP flashes, but many of the ROMs or maybe most have some bugs. All the so called AOSP ROMs are built off the same base, CM10. None of them support all the hardware and software features that Tocuhwiz supports. I find the custom TW ROMs far superior in features and as good or better in speed as well.
Make sure you are flashing a compatible Kernel when you switch between CM based ROMs and TW based
So after doing a wipe to my phone (was becoming slow) my phone randomly restarts itself for no reason as if it just crashes. I am running the latest version of the beanstalk rom. http://forum.xda-developers.com/showthread.php?t=2091900 I don't have the greatest understanding of flashing, roms, blah blah blah, but managed to get kit kat working for the last year or so, I don't understand why this is happening now, did I choose a bad rom or something? Everything else on the phone works but obviously constant restarts get to be very annoying.
Any help would be appreciated,
thank you!
Infused4life said:
So after doing a wipe to my phone (was becoming slow) my phone randomly restarts itself for no reason as if it just crashes. I am running the latest version of the beanstalk rom. http://forum.xda-developers.com/showthread.php?t=2091900 I don't have the greatest understanding of flashing, roms, blah blah blah, but managed to get kit kat working for the last year or so, I don't understand why this is happening now, did I choose a bad rom or something? Everything else on the phone works but obviously constant restarts get to be very annoying.
Any help would be appreciated,
thank you!
Click to expand...
Click to collapse
Try leaving it turned on in recovery mode (CWM). If it still reboots, then you have a hardware issue. If it stays stable, I would blame the ROM and try a different version or a different distro.
Sent from my MyTouch 4G Slide
joel.maxuel said:
Try leaving it turned on in recovery mode (CWM). If it still reboots, then you have a hardware issue. If it stays stable, I would blame the ROM and try a different version or a different distro.
Sent from my MyTouch 4G Slide
Click to expand...
Click to collapse
Thanks for the reply,
I don't think it is a hardware issue as it never did this when I had Jelly Bean or even the last time I had Kit Kat, never know though! Also, I will try to leave it in recovery and see if it does it but a few questions:
-What is "distro" (does it has to do with the OS of the phone?)
-Is there some ROM you could recommend to me for this phone that is stable.. When I install the beanstalk ROM there are like 10 to choose from, I'm guessing they are all older/newer versions!?
-Finally something I was wondering for the longest time but wasn't sure of is can I go back to say, Jelly Bean? Or is it "irreversible"?
Thanks again, glad there's people out there who can help the noobs like me!
Infused4life said:
Thanks for the reply,
I don't think it is a hardware issue as it never did this when I had Jelly Bean or even the last time I had Kit Kat, never know though! Also, I will try to leave it in recovery and see if it does it but a few questions:
-What is "distro" (does it has to do with the OS of the phone?)
-Is there some ROM you could recommend to me for this phone that is stable.. When I install the beanstalk ROM there are like 10 to choose from, I'm guessing they are all older/newer versions!?
-Finally something I was wondering for the longest time but wasn't sure of is can I go back to say, Jelly Bean? Or is it "irreversible"?
Thanks again, glad there's people out there who can help the noobs like me!
Click to expand...
Click to collapse
Methinks it is the specific ROM. I call the different types of OM out there distributions (or "distros" - in light of what is commonly used in the Linux world), but there may be a better term. It could be the version of Beanstalk you are using, it could be any version of BeanStalk with your phone. Hard to say.
In light of above, I would try CarbonROM. I tried it out briefly, and haven;t had a problem with it (and have heard no issues form the guy I sold the phone to with it installed).
But if you want to go back to JellyBean, there is still a version of 4.2 kicking around (CM 10.1) in the development threads. You can downgrade, at worst you may have to ODIN back to stock. But try to flash in CWM first. I was quite satisfied with that version. My biggest gripe is that the mobile data quick setting didn't work fully (but the long way around did). There is CM 10.2 as well, but I could never get that one installed on my phone (installer would break). Between the two, I would try 10.1 (and if you cannot find a copy, I can dropbox it to you).
5529
joel.maxuel said:
Methinks it is the specific ROM. I call the different types of OM out there distributions (or "distros" - in light of what is commonly used in the Linux world), but there may be a better term. It could be the version of Beanstalk you are using, it could be any version of BeanStalk with your phone. Hard to say.
In light of above, I would try CarbonROM. I tried it out briefly, and haven;t had a problem with it (and have heard no issues form the guy I sold the phone to with it installed).
But if you want to go back to JellyBean, there is still a version of 4.2 kicking around (CM 10.1) in the development threads. You can downgrade, at worst you may have to ODIN back to stock. But try to flash in CWM first. I was quite satisfied with that version. My biggest gripe is that the mobile data quick setting didn't work fully (but the long way around did). There is CM 10.2 as well, but I could never get that one installed on my phone (installer would break). Between the two, I would try 10.1 (and if you cannot find a copy, I can dropbox it to you).
Click to expand...
Click to collapse
YES!
So, after I left the phone in CWM for 25 minutes or so and it being fine I decided to get Carbon as I seen in your "signature" that you had that ROM on your Infuse, it has been good for 2 hours+, looking good! I guess it was the Beanstalk ROM after all.
Thanks for the downgrading information as well, wasn't sure if you could downgrade or what would happen!
Finally, what is flashing? (I could google it but since your here, could you give me a noob friendly definition!?)
Thanks for all your help
Infused4life said:
YES!
So, after I left the phone in CWM for 25 minutes or so and it being fine I decided to get Carbon as I seen in your "signature" that you had that ROM on your Infuse, it has been good for 2 hours+, looking good! I guess it was the Beanstalk ROM after all.
Thanks for the downgrading information as well, wasn't sure if you could downgrade or what would happen!
Finally, what is flashing? (I could google it but since your here, could you give me a noob friendly definition!?)
Thanks for all your help
Click to expand...
Click to collapse
Went to reply about the camera issue and notice it was no longer in the post. Glad you got it sorted.
So flashing, as I understand it, is just another term for installing something via recovery. Not sure of the origin, maybe have something to do with installing to flash memory.
joel.maxuel said:
Went to reply about the camera issue and notice it was no longer in the post. Glad you got it sorted.
So flashing, as I understand it, is just another term for installing something via recovery. Not sure of the origin, maybe have something to do with installing to flash memory.
Click to expand...
Click to collapse
Ah ok, so it's essentially as I thought it was. I thought I was doing something wrong in terms of "flashing" but guess not! Sounds like it should just be called "Installing custom ROM".. !
Yeah, in terms of the camera thing, I'm an idiot and had USB storage turned on *facepalm*, So it wouldn't let me open the camera app!
Infused4life said:
Ah ok, so it's essentially as I thought it was. I thought I was doing something wrong in terms of "flashing" but guess not! Sounds like it should just be called "Installing custom ROM".. !
Yeah, in terms of the camera thing, I'm an idiot and had USB storage turned on *facepalm*, So it wouldn't let me open the camera app!
Click to expand...
Click to collapse
I am not sure if you are still facing the same issue but if you are facing reboots, then considering doing a fresh install after cleaning your internal storage as well since the remnants of the apps from previous installs have caused me problems. Ever since I started doing a fresh install (Factory reset, wiping the cache, wiping the dalvik cache and even the cache partition along with the wiping of the internal storage), there have been no reboot issues.
I need some assistance please! I am truly baffled by what I am experiencing and would like to know why and hopefully how to fix it. Here's the details:
CARRIER: Verizon
MODEL: HTC One M8
S-OFF: Yes (Sunshine)
ROOT: Yes
HBOOT: 3.19
RADIO: 1.09.20.0926
OpenDSP: 46.2.2
OS: 3.28.605.4
First off, sorry for the book, but I figured more details would be better at this point to figure out what is up, so I appreciate any assistance in advance! PS: I bolded the key items to the story for those that like to skim.
Prior to S-Off and Root, I was on OTA version 4.4.4 waiting in anticipation for 5.0 to come to my device. Was unsure about spending $25 for Sunshine's method, but finally decided to take the plunge. At first things seemed great and very smooth. Following all instructions from Sunshine I was finally with S-Off status. I then used WeakSauce2 to gain temp root of the Stock ROM so that I could install Flashify and TWRP. Rebooted and loaded up TWRP Recovery and completed the first Nandroid. SUCCESS! Next up was Titanium Backup and such and copied everything off to my computer for safe keeping. So far so good and then loaded up a few ROM files and whatnot to the External SD Card so I could start flashing a new ROM. Feeling good up to this point, but here's where the troubles begin...
I have had great success with CyanogenMod in the past on previous devices and always very pleased. I read CM12 for others was great and stable and performed well, so I decided to grab the latest CM12 Nightly and the GApps package. Did the normal Wipe / System Wipe for initial flash of a new ROM and then installed both ZIPs no problem. The ROM boots up and everything seems okay, only I do not have LTE at all, only 3G. I also tried the GPE rom by Digitalhigh and experienced the same thing! Restoring from Nandroid also did not fix LTE, so at this point I got worried I broke my phone somehow.
To make a long story short after lots of testing I found a fix for getting LTE back on my original ROM. I found the 4.4.4 RUU and placed the 1.7 GB zip file (0P6BIMG.zip) on the root of my external SD Card, booted into HBOOT and ran the update. It did it's thing and booted up into the Stock ROM. Still no LTE! So then I found a comment somewhere about once that is done, do a Factory Reset from HBOOT using the Stock Recovery and it is supposed to reset the NV Radio Partition, so I did this and when it booted back up, SUCCESS! I have LTE back.
Once that was done I can now flash GPE, (but unusable because SMS is not working for some reason... I am using Google Voice BTW), so I am back to my original 4.4.4 TWRP Recovered ROM. I tried just for kicks to see if after the "fix" if I could make CM12 work, but again will bring it down to an unworking LTE status. Rinse and repeat the "fix" and got LTE back and did Nandroid Recovery. I paid the money to get S-Off and Root access so I could enjoy the Custom ROM's, but now I feel I am stuck...
All that being said... Can someone please explain to me what is going on?? And is there any way I can fix this so I can use CM12 and have LTE, and even then some other ROMs? I will post in Digitalhigh's forum for resolution to the SMS issue, but I have never had this much trouble with a device before and do not know enough about the different partitions and how they work and such. Any assistance and advice is MUCH appreciated!
Thank you!
Nobody has any advise or explanation?
I don't know the version numbers you posted from you bootloader off the top of my head but did you update your firmware to one of the unofficial ones around before flashing one of the lollipop roms? Is so, are you sure it took completely as sometimes you have to flash it twice.
Alternatively you could wait for our official firmware to drop any minute now and have pretty good odds of working for you.
cntryby429 said:
I don't know the version numbers you posted from you bootloader off the top of my head but did you update your firmware to one of the unofficial ones around before flashing one of the lollipop roms? Is so, are you sure it took completely as sometimes you have to flash it twice.
Alternatively you could wait for our official firmware to drop any minute now and have pretty good odds of working for you.
Click to expand...
Click to collapse
Yes I did use official firmware, and flashed twice per recommendations. I have it working with GPE, but every time I flash CM12 it breaks LTE. I have seen articles and posts of others running CM12 on their M8's with VZW and stating "zero issues"... Lack of LTE sounds like an issue to me. So my big question at hand is, why does CM12 break LTE, and is there a fix? Everything else seemed to work great otherwise.
kjparenteau said:
So my big question at hand is, why does CM12 break LTE, and is there a fix? Everything else seemed to work great otherwise.
Click to expand...
Click to collapse
I was reading the CM12 m8 thread earlier this week and many reported that LTE did not work on builds from late Feb. early March. CM12 is in no way stable and results will vary from phone to phone. Even the speaker issues have not been fully resolved. Bummer, because I'd really like it to be more stable.
http://forum.xda-developers.com/htc...genmod-12-0-nightlies-htc-one-t2998070/page75
Thank you for your reply. Definitely wanting CM since I used to run that regularly on my older devices with no troubles at all. The speed and simplicity are what I am going for. Sense is okay, but the difference of less than 300 megs with CM compared to over a gig for stock is unreal. WAY less overhead.