I'm currently running Rooted 4.4.2 with Franco and xposed. I created an nandroid and downloaded paranoid 4.41 and gapps and flashed em both, and after numerous attempts I can't get mobile data to work, no 3g or anything. I'm now back on 4.4.2... Anyone have this problem.
Mine works fine. Are you sure your APN info is correct?
Sent from my Nexus 5 using Tapatalk
Related
After flashing latest CM 10.1 nightly (20130311) my tablet booted up but I got the message " Unfortunately System UI has stopped working". Rebooted into twrp recovery and flashed CM 10.1 20130310 nightly. Everything worked fine as usual. Tried flashing CyanDelta 20130311 update file and got the same message. Flashed back to CM 10.1 20130310 nightly again and everything was fine. Has anyone experienced this problem with the CM 10.1 20130311 nightly on Xoom wifi? I have flashed CM 10.1 20130311 nightly on both my GNex and my Nex 7 and have had no problems. Has anyone heard of any bugs with the Xoom CM 10.1 nightly (wingray)? Thanks.
Sent from my Xoom using Tapatalk HD
I had the exact same issue last night. I chalked it up to user error since I had not upgraded CM from within the settings before. I am new to CM and didn't have this option on the competing ROM I used.
kevk60 said:
After flashing latest CM 10.1 nightly (20130311) my tablet booted up but I got the message " Unfortunately System UI has stopped working". Rebooted into twrp recovery and flashed CM 10.1 20130310 nightly. Everything worked fine as usual. Tried flashing CyanDelta 20130311 update file and got the same message. Flashed back to CM 10.1 20130310 nightly again and everything was fine. Has anyone experienced this problem with the CM 10.1 20130311 nightly on Xoom wifi? I have flashed CM 10.1 20130311 nightly on both my GNex and my Nex 7 and have had no problems. Has anyone heard of any bugs with the Xoom CM 10.1 nightly (wingray)? Thanks.
Sent from my Xoom using Tapatalk HD
Click to expand...
Click to collapse
Just wanted to report the same. Yesterday build did not work so I had installed 20130310 build and it is ok although I did not check all the apps.
RoryPG said:
I had the exact same issue last night. I chalked it up to user error since I had not upgraded CM from within the settings before. I am new to CM and didn't have this option on the competing ROM I used.
Click to expand...
Click to collapse
sashykanth said:
Just wanted to report the same. Yesterday build did not work so I had installed 20130310 build and it is ok although I did not check all the apps.
Click to expand...
Click to collapse
So far all my apps seem to be working with cm10.1 20130310 nightly.
Sent from my Xoom using Tapatalk HD
gapps won't flash after reflashing older nightly
kevk60 said:
After flashing latest CM 10.1 nightly (20130311) my tablet booted up but I got the message " Unfortunately System UI has stopped working". Rebooted into twrp recovery and flashed CM 10.1 20130310 nightly. Everything worked fine as usual. Tried flashing CyanDelta 20130311 update file and got the same message. Flashed back to CM 10.1 20130310 nightly again and everything was fine. Has anyone experienced this problem with the CM 10.1 20130311 nightly on Xoom wifi? I have flashed CM 10.1 20130311 nightly on both my GNex and my Nex 7 and have had no problems. Has anyone heard of any bugs with the Xoom CM 10.1 nightly (wingray)? Thanks.
Sent from my Xoom using Tapatalk HD
Click to expand...
Click to collapse
I had the same exact issue with my Xoom. I reflashed an older nightly and it's working again but now I can't get Gapps to flash properly. Every time it loads no gapps....????
I have tried reflashing the latest gapps 3 times now.
Anyone else have this issue or have Any suggestions? Running twrp if it matters but thinking of switching to CWM to try flashing gapps to see if it will take.
I use the team eos gapp pack for Xoom only. When I tried using other gapp packs my system ROM would be full and I could not update supersu. When I use the team eos for Xoom only gapps I found that I have about 30 mb left on my system ROM. My supersu was able to update then. I am using twrp 2.4.3.0 on my Xoom. Am running cm 10.1 20130310 and will stay there until a fix has been made. Do not know if this will help you, just wanted to let you know what has helped me. Are you wiping cache and dalvik before flashing gapps? I'm taking it you are flashing a previous build over the newest nightly.
Sent from my Nexus 7 using Tapatalk HD
kevk60 said:
I use the team eos gapp pack for Xoom only. When I tried using other gapp packs my system ROM would be full and I could not update supersu. When I use the team eos for Xoom only gapps I found that I have about 30 mb left on my system ROM. My supersu was able to update then. I am using twrp 2.4.3.0 on my Xoom. Am running cm 10.1 20130310 and will stay there until a fix has been made. Do not know if this will help you, just wanted to let you know what has helped me. Are you wiping cache and dalvik before flashing gapps? I'm taking it you are flashing a previous build over the newest nightly.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I did wipe both dalvik and cache before flashing gapps. I was using the gapps 20130301 so it could be that or maybe it's an older version of twrp that's causing the issue because I think I'm on 2.4.1.0.
I saw in another thread that I just read someone else was using a different gapps the gapps unified 20130220. I was thinking of giving that a try but I will try the one you recommended first as we both had the same issue above. I will also try flashing the new twrp to see if that's it as well.
Thanks I'll post back up later whether it worked or not.
If you have goo manager you could just update twrp from there.
Sent from my Xoom using Tapatalk HD
Looks like system ui bug issue has been fixed in the newest cm 10.1 nightly (20130314). Thanks to the devs.
Sent from my Xoom using Tapatalk HD
So after I flashed 10.2 I can only boot my Verizon s3 on the first initial boot. If I ever have to reboot the phone, it locks up at cyanogenmod flash screen. The only way I can get the phone to boot back up after this, is to do a battery pull and boot into twrp. Then do a full format, doing just a factory reset doesn't work. Once I complete a full format, I can restore one of my backup images and the phone will boot once, and that's it. Then I have to start the process all over again, any ideas?
Don't know if this helps but I'm currently running OSE 4.3.1, but have tried with dirty unicorn & liquid smooth.
Sent from my SCH-I535 using xda app-developers app
Well I managed to get this fixed not 100 percent sure on how, what I did was flash stock deodexed image in twrp, then started flashing from 10.1.3 and then to 10.2. I'm not sure which helped, but after this I was able to restore any of my previous roms and they boot just fine now.
Sent from my SCH-I535 using xda app-developers app
Were your backups all AOSP 4.3 as well or TW?
Sent from my SCH-I535 using Tapatalk 4
I find if I'm getting an infinite bootloop like that, flashing stock seems to sort **** out. That's the case on the LG and Motorola phones I've owned as well.
SlimSnoopOS said:
Were your backups all AOSP 4.3 as well or TW?
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
AOSP & AOKP none of them were TW.
beepea206 said:
I find if I'm getting an infinite bootloop like that, flashing stock seems to sort **** out. That's the case on the LG and Motorola phones I've owned as well.
Click to expand...
Click to collapse
Yep I guess so, still learning on all of this custom rom stuff. I tried everything prior to just flashing stock rooted rom, wasted a ton of time wish I would of thought of it sooner.
Below are some current rom's that i'm running all seem to be very stable with very little bugs.
Current Rom:[ROM][OFFICIAL][4.3] CM10.2 M1 for d2vzw so far this rom seems to be very stable have only had one random reboot since I flashed it yesterday.
Backup Up Rom's:
1. So far my all time favorite with very little issues:[ROM][4.3.1][Official][OSE Rom][d2vzw]
2. I really enjoy this rom only complaint is the cell service on it doesn't seem to be quite as stable:[ROM] [Team D.I.R.T] Dirty Unicorns 4.3.1 - d2vzw v3.9
3. Another very stable rom, only complaint is with the radio sometimes after a reboot radio doesn't work and you have to do a battery pull:[ROM][4.3][OFFICIAL] LiquidSmooth v2.10 - d2vzw - 10|6|13
sampson2269 said:
AOSP & AOKP none of them were TW.
Click to expand...
Click to collapse
I wonder if we'll see this issue pop up with the TW 4.3 OTA we're rumored to receive this month.
Sent from my SCH-I535 using Tapatalk 4
I have a Nexus 4 running on 4.4.2 update base ROM. I've unlocked and rooted my phone, with multiple root tests to be sure. I've also downloaded the Franco kernel. Though its not working, so I assume its cause its a nightly version. From the information I've found those don't always work.
Back to my question though. My devices is a Mako, which goes along with being a Nexus 4 right. So why is it when I downloaded the cyanogenmod mako latest ROM it didn't work? Came up with an error comparing device and product as being mako, and some status 7 thing. I did a restore and now I'm here.
I've tried to install it view clockwork recovery, and from the ROM manager app. Both came up with those errors. Am I doing something wrong?
Sent from my Nexus 4 using xda app-developers app
Hi. I updated to an unofficial Carbon 4.4 kitkat build. I flashed the PA gapps and rebooted.
Normally my phone would autodownload all my apps that I had installed previously, but it didn't this time.
Anyone know why?
It happens sometimes ... Wipe and reinstall again ... I usually go back to a nandroid version to re-sync Google then reinstall and all works well
Sent from my SCH-I535 using XDA Premium 4 mobile app
I saw that there are new 12.1 nightlies for the T-Mobile LG G2.
https://download.cyanogenmod.org/?device=d801
You need to have KK bootstack installed.
Also you need GApps for 12.1 if you want them.
What is the KK bootstack you are referring to exactly? Thanks in advance!
Sent from my LG-D801 using Tapatalk
btafoya said:
What is the KK bootstack you are referring to exactly? Thanks in advance!
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
I had to install a new bootstack for the stock lollipop to work here: http://forum.xda-developers.com/tmobile-g2/development/rom-tmo-g2-lollipop-30b-stock-rom-t3084687
This rom uses the old bootstack for kitkat. You can download it here if you installed the lollipop bootstack: https://www.androidfilehost.com/?fid=95916177934556125
I flashed the 20g bootstack with cm and the rom kept rebooting every few minutes. Is anyone else having this issue?
Sent from my LG-F350K using Tapatalk
I'm on cm12 right now. I never installed a kk bootstack for it to work? But when I try to flash 12.1 I get some error in twrp regarding some verification issue.
Sent from my LG-D801 using Tapatalk
tnvu1 said:
I saw that there are new 12.1 nightlies for the T-Mobile LG G2.
https://download.cyanogenmod.org/?device=d801
You need to have KK bootstack installed.
Also you need GApps for 12.1 if you want them.
Click to expand...
Click to collapse
This whole post should be deleted by mods. Bloody cancer. Having the KK boostack installed will cause reboot every time you connect to LTE you NEED 30b in order for this to work. Did you even test this OP? Or did you just put this thread out here without even knowing if it was correct or not? Because I wasted a lot of time troubleshooting this and needless to say I'm a little miffed at you for the absolutely incorrect information you posted here.
I flashed it straight from stock Lollipop and everything worked, until a few hours later when LTE and 2G stopped working. I could make calls and get on wifi but no mobile data.
What is the best current guide/method for installing a custom recovery and CM12 on the D801? Are the nightly builds stable enough?
bigj480 said:
What is the best current guide/method for installing a custom recovery and CM12 on the D801? Are the nightly builds stable enough?
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/tmo...l-one-click-freedom-tool-lp-30b-twrp-t3084474
Nightlies might be stable if I could figure out the bootstacks issue
GTR24 said:
Try this: http://forum.xda-developers.com/tmo...l-one-click-freedom-tool-lp-30b-twrp-t3084474
Nightlies might be stable if I could figure out the bootstacks issue
Click to expand...
Click to collapse
Thanks, I installed the newest nightly and had the the same issue as you. Mobile data didn't work as soon as I installed. Unfortunately I also wiped my contacts, I mistakenly though they were backed up. I did an ABD and TWRP backup, so I'll see if I can restore them.