I'm running Liquid Smooth v3.2 10-28 and have baseband 24a. As the title states, if I install any other ROM (have tried CM, PacMan, Dirty Unicorn) then I get boot loops. I'm doing a clean install through TWRP (which is what I've always done up until now). Even my previous backups result in a boot loop.
Does anyone have any idea why this might be happening or how to fix it? Do I need to return to stock, re-root, and go from there?
Thanks in advance :fingers-crossed:
CM, PAC, and DU are all jb based. 24a is kitkat. You'll need to flash the 12b bootstack in xdabbeb's thread to run one of those roms.
Welp, now I feel ignorant >.<
Thanks for the info.
nowetdio said:
CM, PAC, and DU are all jb based. 24a is kitkat. You'll need to flash the 12b bootstack in xdabbeb's thread to run one of those roms.
Click to expand...
Click to collapse
If you want CM with the 24A baseband.. (actually you need the 26A baseband with this one I believe)
CM11 - http://forum.xda-developers.com/showthread.php?t=2702958 26A
Related
I'm currently on the official CM11 nightlies, and I just haven't had the time to go through the entire process required to switch to the 4.4.2 OTA-based CM11 ROM. However, the random reboots and SODs are getting to me so much these days that I'm willing to try something different to quickly flash over to it. I was wondering if anyone knew if the following process would work:
Reboot into recovery
Make a backup of course
Flash TWRP 2.7 and reboot recovery
Flash the 24A OTA bootstack from XDABBEB's VS98024A ROM and reboot recovery
Wipe system, cache, dalvik
Flash JackpotClavin's OTA-based CM11 over my current install and reboot
I realize a dirty flash in this way may introduce its own set of problems, but I'm willing to take the chance if it means I can go straight from my current CM11 install to JPC's without having to wipe everything and go back to stock first.
I'm very comfortable with the command line and I have a good knowledge of how most Android devices work (bootloader, radio, recovery, kernel, cache, system, and data, and how they all tie together, all that necessary info). I just don't really know much about all the extra stuff for the G2 and I haven't had time to research it, so I've got no clue if flashing the bootstack is all I need, or if I'll also have to go hunting for a 4.4.2 radio zip to get the baseband up to date or anything else.
_b_d_ said:
I'm currently on the official CM11 nightlies, and I just haven't had the time to go through the entire process required to switch to the 4.4.2 OTA-based CM11 ROM. However, the random reboots and SODs are getting to me so much these days that I'm willing to try something different to quickly flash over to it. I was wondering if anyone knew if the following process would work:
Make a backup of course
Flash TWRP 2.7
Flash the 24A OTA bootstack from XDABBEB's VS98024A ROM
Wipe system, cache, dalvik
Flash JackpotClavin's OTA-based CM11 over my current install
I realize a dirty flash in this way may introduce its own set of problems, but I'm willing to take the chance if it means I can go straight from my current CM11 install to JPC's without having to wipe everything and go back to stock first.
I'm very comfortable with the command line and I have a good knowledge of how most Android devices work (bootloader, radio, recovery, kernel, cache, system, and data, and how they all tie together, all that necessary info). I just don't really know much about all the extra stuff for the G2 and I haven't had time to research it, so I've got no clue if flashing the bootstack is all I need, or if I'll also have to go hunting for a 4.4.2 radio zip to get the baseband up to date or anything else.
Click to expand...
Click to collapse
Follow steps 3-5 in XDABBEB's thread you posted and you should be good to install the CM11 4.4.2 based release. No harm in trying a dirty flash, worse case you need to wipe and install clean anyway.
Replying to say it worked perfectly, for anyone else in the same situation. I updated from the official CM11 4/26 nightly to JPC's 4/30 CM11 build by following the steps in my first post (and without wiping data or internal storage) and it booted right up with no issues whatsoever like a normal nightly upgrade. Huzzah!
_b_d_ said:
Replying to say it worked perfectly, for anyone else in the same situation. I updated from the official CM11 4/26 nightly to JPC's 4/30 CM11 build by following the steps in my first post (and without wiping data or internal storage) and it booted right up with no issues whatsoever like a normal nightly upgrade. Huzzah!
Click to expand...
Click to collapse
I did this same thing although my previous CM 11 worked just fine except my GPS didnt work. So after this install and upgrading my bootstack and modem to 25A that my GPS would be fixed but its still broken under this as well. Any ideas guys?
xsirxx said:
I did this same thing although my previous CM 11 worked just fine except my GPS didnt work. So after this install and upgrading my bootstack and modem to 25A that my GPS would be fixed but its still broken under this as well. Any ideas guys?
Click to expand...
Click to collapse
Did you make sure to get a GPS lock on a stock based 25A ROM by opening maps and letting it locate you? That seems to calibrate the GPS sensors.
JRJ442 said:
Did you make sure to get a GPS lock on a stock based 25A ROM by opening maps and letting it locate you? That seems to calibrate the GPS sensors.
Click to expand...
Click to collapse
up
I found that I had to go to a stock-based 25A ROM to fix this as well. Not a big deal - first back up everything in TWRP, wipe everything except internal storage, flash xdabbeb's ROM, get the GPS lock, then reflash as above (not really necessary if you're restoring but I did it anyway), then restore from backup.
I'm now on a 25B bootstack (dirty flash) and so far, so good - it's much more stable than straight CM11.
Somehow during my update to the 24A baseband, I lost my APN settings (there are no entries), and therefore have no mobile data ("Mobile Network State: Disconnected"). Where can I find the APN settings for my vzw g2? I found a site that claimed to have the correct VZW apn settings (can't post links yet, just google "buzzmobile verizon apn" and it's the top result) but for some reason, whenever I try and set the MNC to 012, the entire APN entry disappears from the menu. Entering all the other settings and leaving the MNC at its default (I think it was 004) didn't resolve my internet connection. Any ideas? I was thinking I could probably revert to stock KK using the kdz method, but since that'd be rather time consuming, if there's any way I could just flash a quick fix or something I'd prefer that.
I'm running Mahdi 6-28 build, V6 patch, 4.4.4 PA mini gapps, 24A baseband
After several hours of searching and troubleshooting I found a fix. Trying to make APN entries didn't lead anywhere, and editing the apn-conf.xml also did nothing. I had flashed 4 or 5 different 4.4.4 roms (some stock, some AOSP) and still nothing, but for whatever reason, doing a wipe and flashing XDABBEB's VS98024A v1.2.1 ROM (can't post link sorry) fixed my mobile data. I then did a system/cache/dalvik/data wipe and reinstalled Mahdi 6-28 and boom I have Mahdi with working LTE. Sorry for the spam I guess, but maybe this will help anyone having similar issues.
takethecake said:
After several hours of searching and troubleshooting I found a fix. Trying to make APN entries didn't lead anywhere, and editing the apn-conf.xml also did nothing. I had flashed 4 or 5 different 4.4.4 roms (some stock, some AOSP) and still nothing, but for whatever reason, doing a wipe and flashing XDABBEB's VS98024A v1.2.1 ROM (can't post link sorry) fixed my mobile data. I then did a system/cache/dalvik/data wipe and reinstalled Mahdi 6-28 and boom I have Mahdi with working LTE. Sorry for the spam I guess, but maybe this will help anyone having similar issues.
Click to expand...
Click to collapse
Ran into the same exact issue on a friend's phone. Going to try this out. Regardless if it works, thanks for the post!
UPDATE: It worked. The 24a bootstack includes the new modem and properly formats relevant partitions. I flashed XDABBEB's ROM just to replicate your exact procedure but this shouldn't be necessary. The bootstack is all that is needed when coming from a 12b rom.
topdawg7793 said:
Ran into the same exact issue on a friend's phone. Going to try this out. Regardless if it works, thanks for the post!
UPDATE: It worked. The 24a bootstack includes the new modem and properly formats relevant partitions. I flashed XDABBEB's ROM just to replicate your exact procedure but this shouldn't be necessary. The bootstack is all that is needed when coming from a 12b rom.
Click to expand...
Click to collapse
Having the same issue and flashing the 24a bootstack without the ROM does nothing. About to return this phone, it seems like nothing works correctly unless you are on the POS bloated stock ROM. What a shame, such potential on this device. Oh well.
remicks said:
Having the same issue and flashing the 24a bootstack without the ROM does nothing. About to return this phone, it seems like nothing works correctly unless you are on the POS bloated stock ROM. What a shame, such potential on this device. Oh well.
Click to expand...
Click to collapse
Return it to stock, let it take the KK OTA, root it, autorec for recovery, flash your 24A based rom of choice, that always works for me.
I had Carbon running fine on mine til I got bit by the black line issue. I haven't put AOSP on the replacement, probably will soon..
mjones73 said:
Return it to stock, let it take the KK OTA, root it, autorec for recovery, flash your 24A based rom of choice, that always works for me.
I had Carbon running fine on mine til I got bit by the black line issue. I haven't put AOSP on the replacement, probably will soon..
Click to expand...
Click to collapse
Trying this now, returning to 11a robbed me of my LTE for some reason though... doesn't even show up in the network info screen that shows the 3g/1x/LTE signal strength... weird...
remicks said:
Having the same issue and flashing the 24a bootstack without the ROM does nothing. About to return this phone, it seems like nothing works correctly unless you are on the POS bloated stock ROM. What a shame, such potential on this device. Oh well.
Click to expand...
Click to collapse
Haha I should have clarified. I meant that flashing the 24a bootstack and THEN flashing a 24a-based rom should do the trick. Flashing the 24a bootstack, XDABBEB's rom, and then (clean) flashing another 24a-based rom is redundant.
Thanks, doesn't matter now. Phone fell 1 foot and cracked to hell and touchscreen no longer works.
I am at a standstill installing CM11 off of the moto_msm8960 unified CM11 builds. Here's what I have accomplished so far:
Root and unlock bootloader with motochopper and motopocalypse
Install CWM Touch v.6.0.4.4 per the CM tutorial here.
Download a nightly CM11 build and remove Status 7 error per the tutorial here.
Backup stock AOSP ROM with CWM to external SD
My issue now is that I cannot install the ROM through CWM because my bootloader is not 4.4. Could someone guide me in updating the kernel to a KK based one so that I can install?
Edit:I realized while reading another thread that my problem it that the CM website has misreported the rom to use and that I have to use the moto_msm8960 jbbl branch, as the bootloader can only be upgraded if Moto releases a (the?) KK upgrade officially.
IanPPK said:
Edit:I realized while reading another thread that my problem it that the CM website has misreported the rom to use and that I have to use the moto_msm8960 jbbl branch, as the bootloader can only be upgraded if Moto releases a (the?) KK upgrade officially.
Click to expand...
Click to collapse
That's right, you can flash the jbbl branch, it works good. Use that until we recieve the KitKat upgrade.
mauchito said:
That's right, you can flash the jbbl branch, it works good. Use that until we recieve the KitKat upgrade.
Click to expand...
Click to collapse
I intend to flash nightlies. Quick question though, do I have to do a nandroid backup in CWMR, factory reset/wipe, and then flash the new nightly, or can the new nightly flash like an update.zip? I am currently doing the process I mentioned above and don't want to risk bricking, if there is any risk.
IanPPK said:
I intend to flash nightlies. Quick question though, do I have to do a nandroid backup in CWMR, factory reset/wipe, and then flash the new nightly, or can the new nightly flash like an update.zip? I am currently doing the process I mentioned above and don't want to risk bricking, if there is any risk.
Click to expand...
Click to collapse
It is optional to do a nandroid backup, I would usually do this when I am still running stock ROM but it is up to you. You can either clean flash or dirty flash, I don't believe it'll brick your device. I usually clean flash, it is just me. Good luck!
IanPPK said:
I intend to flash nightlies. Quick question though, do I have to do a nandroid backup in CWMR, factory reset/wipe, and then flash the new nightly, or can the new nightly flash like an update.zip? I am currently doing the process I mentioned above and don't want to risk bricking, if there is any risk.
Click to expand...
Click to collapse
Just a little reminder: You can OTA nightly to nightly and snapshot to snapshot without almost any risk of bricking your device, but when you change from nighty to snapshot or viceversa, you forcefully need to wipe everything. Or you'll get a nasty bootloop.
I am unable to install Cyanogenmod. I have TWRP that was installed with AutoRec. I tried flashing the Stable 10.2 CM version,and when I flashed it said "Failed", which put me into a security error boot loop. Then I tried a nightly, and it said "Success" and when I tried to start it up, it put me into another boot loop. I have the stock Kernel, and I am rooted. Is something like goo manager or rom manager better to use for this? Or what is the safest way to install a custom ROM
Zach_Deem said:
I am unable to install Cyanogenmod. I have TWRP that was installed with AutoRec. I tried flashing the Stable 10.2 CM version,and when I flashed it said "Failed", which put me into a security error boot loop. Then I tried a nightly, and it said "Success" and when I tried to start it up, it put me into another boot loop. I have the stock Kernel, and I am rooted. Is something like goo manager or rom manager better to use for this? Or what is the safest way to install a custom ROM
Click to expand...
Click to collapse
JackpotClavin's version is the only one that works on the VS980. http://forum.xda-developers.com/showthread.php?t=2702958
Sent from my XDABBEB VS98025A v2.0.0 using XDA free mobile app
What he said, the official nighties only work with the JB baseband.
So is there any other way to do this? I saw that is is extremely risky, and it will permanently brick my phone. Is there any other thing im able to do to flash this?
Zach_Deem said:
So is there any other way to do this? I saw that is is extremely risky, and it will permanently brick my phone. Is there any other thing im able to do to flash this?
Click to expand...
Click to collapse
If you want CM11 with the KK baseband(24A), use the version z3pp3lin pointed you to, otherwise most other AOSP based roms have already been upgraded to work with the KK baseband, use one of those. Just double check the notes on the rom to make sure it's KK/24A based.
Do I have to do all of those steps? You said there is a like for cyanogenmod for 24a. I don't see one though
Zach_Deem said:
Do I have to do all of those steps? You said there is a like for cyanogenmod for 24a. I don't see one though
Click to expand...
Click to collapse
All those steps are required to manually install a recovery on KK, that was pre-autorec, if you've already installed TWRP, you can skip to step 11.
mjones73 said:
All those steps are required to manually install a recovery on KK, that was pre-autorec, if you've already installed TWRP, you can skip to step 11.
Click to expand...
Click to collapse
So I can only use his roms?
Zach_Deem said:
So I can only use his roms?
Click to expand...
Click to collapse
You have the 24A KK baseband on your phone, you can only use roms that work with that baseband. If you specifically want CM11, you need to use the rom linked, otherwise any other 24A KK based rom will work. Check the notes for any rom you want to install to see what baseband it works with.
mjones73 said:
You have the 24A KK baseband on your phone, you can only use roms that work with that baseband. If you specifically want CM11, you need to use the rom linked, otherwise any other 24A KK based rom will work. Check the notes for any rom you want to install to see what baseband it works with.
Click to expand...
Click to collapse
So If I want cm, I have to use his links correct? I just want to be sure so I don't get another bootloop
Why not just use a AOSP or CM based ROM that works with the 24A baseband... CM is good, but hardly the "best" ROM out there, if there is such a thing... Try AICP 6.0, it is extremely stable and the VS980 version is excellent and very feature packed.
Zach_Deem said:
So If I want cm, I have to use his links correct? I just want to be sure so I don't get another bootloop
Click to expand...
Click to collapse
For about the 4th time, yes.
mjones73 said:
For about the 4th time, yes.
Click to expand...
Click to collapse
Im about to flash the cm version and we will see how this goes
I downloaded the rom onto my phone but I'm scared for some reason. Is it guaranteed to not brick if I'm on the right version?
Zach_Deem said:
I downloaded the rom onto my phone but I'm scared for some reason. Is it guaranteed to not brick if I'm on the right version?
Click to expand...
Click to collapse
Not too freak you out more, but no, there is no guarantee. That's why every ROM has the disclaimer in the OP. By flashing you're taking responsibility that you understand the risks involved. If you flash cm and damage your phone somehow, it's on you. So it's either stay with rooted stock where you know nothing will happen, or flashing and taking the risk. Your choice...
njstein said:
Not too freak you out more, but no, there is no guarantee. That's why every ROM has the disclaimer in the OP. By flashing you're taking responsibility that you understand the risks involved. If you flash cm and damage your phone somehow, it's on you. So it's either stay with rooted stock where you know nothing will happen, or flashing and taking the risk. Your choice...
Click to expand...
Click to collapse
Alright, but is there any way to know if a rom is successfully flashed other than it saying successful or restarting?
Zach_Deem said:
Alright, but is there any way to know if a rom is successfully flashed other than it saying successful or restarting?
Click to expand...
Click to collapse
No.
Hello everyone, I have a VS980, I was running crdroid 4.4.2 rom and in order to flash CM12, I flashed the 12b modem, everything went well with CM12, After that one I flashed a Lollipop Resurection rom, then I flashed another Lollipop based rom, Bliss to be exact.
on that last rom I flashed Render Kernel which I didn't know was Bumped (I don't know how to go about Bump! so I was trying to stay away from it). the thing is that now I'm trying to flash back to a cloudy G3 rom (Kitkat based ) and i always end up in a bootloop (the phone reboots straight to TWRP recovery on its own). I have already tried flashing the 24a bootstack from xdabbeb's thread. and also tried flashing the Kitkat modem and I still can't flash back to cloudy. Luckily I still can flash back to Bliss Lollipop Rom, which is the one I'm running right now.
Sorry for the long explanation. Could anyone please Help me?
PS: Any insight as to how does BUMP! work (or at least a FAQ about using it vs loki based zips would be great).
Hello, anyone?
Since you are on a Verizon VS980, I would recommend using the G3 rom specifically for our phones. Cloudy G3 rom doesn't work with the Stock Messaging app, along with Visual VM and several others. The radio keeps flipping to GSM WorldWide mode and roams.
I recommend this one:
http://forum.xda-developers.com/verizon-g2/development/xdabbeb-s-vs982-5-v1-0-0-t2975551
It also uses the BUMPed recovery... so you should be able to just wipe and flash with ease. Just flash the Bootstack update first, wipe, rom, celebrate.
I actually came from Cloudy G3 directly. It feels like the CloudyG3 rom except it is custom tailored for our Verizon phones specifically so everything works better.