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.
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.
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.
I wanted to try and see how cm10.1 felt so i am going to install it. However i would first like to know if there are going to be any issues. Will my device get bricked? Its the XT1058 with bootloader unlocked, its in 34.B7 i think is the version which is the one of lollipop i believe (I may be wrong). I am currently in cm11 and have installed cm12.1 before as well as a flashable backup of the official brazil release. However the brazil rom wasnt the "complete" one, it was pretty much like installing cyanogenmod, i didnt have to use the rsd lite i just flashed it through twrp because it was a backup. So... thanks in advanced everyone.
Hey, I just wanted to know if it would be possible to dirty flash CM 12.1 from my current rom which is Pure Nexus Project. Would there be any problems considering CM 12.1 is based on Lollipop? Or should I flash Lollipop first then proceed with 12.1. Also I have no interest in the unofficial releases for CM 13.
Don't dirty flash....
Yea... pretty sure a dirty flash downgrade will have no hope of working...
You could always backup and try, that way you would have a restore point for when it almost certainly turns out to not work going from a MM aosp ROM to a lp cm rom via dirty flash...
I'm sure you already spent more time on this issue than actually doing a clean install would have taken.
Nowadays a clean install means a factory reset in recovery with what you keep all your files and personal data. You make a Titanum backup before flashing, and after you let Google install all your software, you just restore the data to the applications.
You basicly can't retain any system data going from one rom to another, so those setting will have to be set by hand anyway.
Sent from my Nexus 6 running cyosp using Tapatalk
Official CM13 is now out. And don't dirty flash, it probably wont even boot.
as many as are telling you not to dirty flash, i wont. but, i will tell you to make a nandroid backup in recovery first. that way when you do dirty flash, and things dont go well, you can always restore your backup.
Hi i flashed a month ago aicp to my xperia sp and now i want to install a nightly of the same rom.Do i have to do full wipe or just flash the rom?I am using cyanogen recovery.I am asking this because in my previous rom i installed a nightly update without wiping and i ended up bricking the phone.
I read everywhere that the safest way is to do a full wipe, and since you have nothing to lose it won't hurt, so i think you should.
nickos12 said:
Hi i flashed a month ago aicp to my xperia sp and now i want to install a nightly of the same rom.Do i have to do full wipe or just flash the rom?I am using cyanogen recovery.I am asking this because in my previous rom i installed a nightly update without wiping and i ended up bricking the phone.
Click to expand...
Click to collapse
yes it is practically the correct way to update a nightly.
However do bear in mind that the nature of nightly is that it might have problems after different builds, therefore having a previous build zip handy would really help you. Also backups!
In case of a problem, clean flashing sometimes aren't really your go-to method to correct stuff. Always assume it as a last resort.. In case you faced any problem do kindly share here.
so i sould install the nighlty without wiping?
TechnoSparks said:
yes it is practically the correct way to update a nightly.
However do bear in mind that the nature of nightly is that it might have problems after different builds, therefore having a previous build zip handy would really help you. Also backups!
In case of a problem, clean flashing sometimes aren't really your go-to method to correct stuff. Always assume it as a last resort.. In case you faced any problem do kindly share here.
Click to expand...
Click to collapse
so i sould install the nighlty without wiping?
nickos12 said:
so i sould install the nighlty without wiping?
Click to expand...
Click to collapse
Yes you may
Ok thanks
nickos12 some questions raised i hope you don't mind posting here to spare a new topic
TechnoSparks said:
However do bear in mind that the nature of nightly is that it might have problems after different builds, therefore having a previous build zip handy would really help you. Also backups!
Click to expand...
Click to collapse
1. So you saying that a new update might/could be worst than the previous, correct ?
2. Do we need a full wipe of everything like first time (data, system, dalvid cache, etc) before install an update of the same rom (nightly 20151214) ?
3. Should i install it via recovery or ota ?
giannisv6 said:
nickos12 some questions raised i hope you don't mind posting here to spare a new topic
1. So you saying that a new update might/could be worst than the previous, correct ?
2. Do we need a full wipe of everything like first time (data, system, dalvid cache, etc) before install an update of the same rom (nightly 20151214) ?
3. Should i install it via recovery or ota ?
Click to expand...
Click to collapse
Yes, nightly is a daily release where changes are huge in the back end.. Sometimes a simple change can make a build unbootable. Sometimes it introduces new bugs. Sometimes it is better and fixes everything. It is of course a good thing to update to the latest if possible, it is just that it is also vital to know what we're going to face when we flash a new update. So that we can make backups beforehand in case something really bad happens.
If you are installing an update to the same ROM there is no need to wipe anything. Wiping is optional.
↑ Note, if you are reverting to a previous build, you will need to wipe everything as there will be conflicts for the system data. This is why frequent/periodic app backups useful.
You can do either both of them without any problem
Thank you very much.
It's the first time i flashed a custom rom (the AICP 10 successfully :cyclops: ) and i got overwhelmed with all these endless customization options .