Database Develop

11a to 12b (VS980)

Pretty much when I first got my phone I rooted and put TWRP 2.6.3.2 on it. I haven't really done anything with it since - I was waiting for a stable 4.4 ROM and then just got busy and didn't have time to play with my phone.
Anyway, now i'm having radio/4g issues and I'd like to update to 12b and possibly even 24a.
My software screen now -
here
From my understanding, using xdabebb's method here, I should be good to go to 4.4.2 as long as I can find a way to upgrade TWRP 2.6.3.2 to 2.6.3.3 (any flashable zips?) otherwise I can use the .tot method and get to 12b.
Is this correct? Any pointers?
Thanks! :fingers-crossed:

sheamolt said:
Pretty much when I first got my phone I rooted and put TWRP 2.6.3.2 on it. I haven't really done anything with it since - I was waiting for a stable 4.4 ROM and then just got busy and didn't have time to play with my phone.
Anyway, now i'm having radio/4g issues and I'd like to update to 12b and possibly even 24a.
My software screen now -
here
From my understanding, using xdabebb's method here, I should be good to go to 4.4.2 as long as I can find a way to upgrade TWRP 2.6.3.2 to 2.6.3.3 (any flashable zips?) otherwise I can use the .tot method and get to 12b.
Is this correct? Any pointers?
Thanks! :fingers-crossed:
Click to expand...
Click to collapse
What's the latest version of TWRP showing up in Flashify? If it's high enough just flash it that way and you're good to proceed.

Wow! Thanks! Didn't realize it was that easy. It's been a while and didn't even know things like Flashify were out
Anyhow, worked great. I updated to 2.7.0.0, followed instructions exactly and bam i'm on 4.4.2. Thanks a bunch!

[Q] Moving from CM11 back to Stock or Otherwise

Hi all,
I have been using CM11 (http://forum.xda-developers.com/showthread.php?t=2494684) for awhile and hoping that they'd fix it so I wouldn't have to go back to stock or install a new ROM, but it seems that isn't going to happen. I guess I'm a beginner with this stuff, only because I only really dig in about twice a year and so I forget everything I learned the last time I had dealt with it.
I'm currently using a nightly from a few weeks ago (haven't bothered updating since... I don't think they're updating them) and I would like to either go back to completely stock and get OTA updates again, or move to another stable ROM. I had a backup from when I first rooted, but have since lost it. I have tried to find out what steps I need to take, but everything in these forums is all over the place and IF this THEN this, and Verizon specifically has to follow these steps, blah blah blah. Long story long, it's very confusing to me and at this point I think I have to follow 4 different guides entirely to get back to something that works (Which makes me think I'm missing something very simple). I figured I'd post and get a direct response to my specific situation.
Android version 4.4.4
Baseband version 11A
Recovery ClockworkMod 6.0.4.4
(Not sure this will help or not, but figured it's worth adding)
I did at one point have TWRP installed, but I had changed it at some point for... Some reason, no idea at this point. I think part of my frustration with trying to fix this is that some instructions tell me to have at least some specific version of TWRP (2.7?) installed, but I could never get it to work. The files for earlier versions were .img and the newer versions were .zips I think, and the process would always error out, no matter what I tried. (extracting contents, using the .img within, changing .zip to .img, maybe others, this was months ago)
Ultimately, I'd like to go to a stable ROM rather than stock, but I really don't want to have to spend hours working on this. I have already spent time looking at different threads piecing together what I need to do and I'm not at all confident that what I've come up with is the easiest or correct way for me to do this. Some people may say "the instructions are on the first post of whatever ROM you want". While that is true, when I have to be on a specific baseband or some such and directions are referenced but aren't linked, and I have to start digging, I lose confidence.
Aaaannyway, if anyone could help I would VERY MUCH APPRECIATE IT. I have been dealing with daily crashes for way too long.

Nicholo said:
Hi all,
I have been using CM11 (http://forum.xda-developers.com/showthread.php?t=2494684) for awhile and hoping that they'd fix it so I wouldn't have to go back to stock or install a new ROM, but it seems that isn't going to happen. I guess I'm a beginner with this stuff, only because I only really dig in about twice a year and so I forget everything I learned the last time I had dealt with it.
I'm currently using a nightly from a few weeks ago (haven't bothered updating since... I don't think they're updating them) and I would like to either go back to completely stock and get OTA updates again, or move to another stable ROM. I had a backup from when I first rooted, but have since lost it. I have tried to find out what steps I need to take, but everything in these forums is all over the place and IF this THEN this, and Verizon specifically has to follow these steps, blah blah blah. Long story long, it's very confusing to me and at this point I think I have to follow 4 different guides entirely to get back to something that works (Which makes me think I'm missing something very simple). I figured I'd post and get a direct response to my specific situation.
Android version 4.4.4
Baseband version 11A
Recovery ClockworkMod 6.0.4.4
(Not sure this will help or not, but figured it's worth adding)
I did at one point have TWRP installed, but I had changed it at some point for... Some reason, no idea at this point. I think part of my frustration with trying to fix this is that some instructions tell me to have at least some specific version of TWRP (2.7?) installed, but I could never get it to work. The files for earlier versions were .img and the newer versions were .zips I think, and the process would always error out, no matter what I tried. (extracting contents, using the .img within, changing .zip to .img, maybe others, this was months ago)
Ultimately, I'd like to go to a stable ROM rather than stock, but I really don't want to have to spend hours working on this. I have already spent time looking at different threads piecing together what I need to do and I'm not at all confident that what I've come up with is the easiest or correct way for me to do this. Some people may say "the instructions are on the first post of whatever ROM you want". While that is true, when I have to be on a specific baseband or some such and directions are referenced but aren't linked, and I have to start digging, I lose confidence.
Aaaannyway, if anyone could help I would VERY MUCH APPRECIATE IT. I have been dealing with daily crashes for way too long.
Click to expand...
Click to collapse
There isn't any developers for cm11 unless you go to some of the unofficials. There is no one to do the work. If your wanting a stable rom check out mahdi works great.

simple_fear85 said:
There isn't any developers for cm11 unless you go to some of the unofficials. There is no one to do the work. If your wanting a stable rom check out mahdi works great.
Click to expand...
Click to collapse
If I'm reading things correctly, in order to use Mahdi I need to...
1) Wipe everything but internal storage.
2) Flash the 11A Kitkat modem for the JB baseband. (I think that makes sense?) (Based on this post) Or maybe I'm supposed to use Cloudyfa's KK modem?
3) Flash Mahdi.
4) Flash patch.
5) Flash Gapps.
Am I close or way off? I guess the modem and baseband stuff is confusing me the most.

If you want to stick to CM11, you can upgrade your baseband to 24A and use jackpotclavin's build, it works well but it hasn't been updated past 4.4.2 I believe.

Nicholo said:
If I'm reading things correctly, in order to use Mahdi I need to...
1) Wipe everything but internal storage.
2) Flash the 11A Kitkat modem for the JB baseband. (I think that makes sense?) (Based on this post) Or maybe I'm supposed to use Cloudyfa's KK modem?
3) Flash Mahdi.
4) Flash patch.
5) Flash Gapps.
Am I close or way off? I guess the modem and baseband stuff is confusing me the most.[/QUOTE
no go to xdabbes follow his stock method then go back to twrp flash mahdi, the patch, and then gapps
All aosp roms now that are 4.4.4 are running the 24a bootstack or kitkat.
Click to expand...
Click to collapse

no go to xdabbes follow his stock method then go back to twrp flash mahdi, the patch, and then gapps
Click to expand...
Click to collapse
Okay, now this is where I run into the TWRP problem I mentioned. I can't get TWRP 6.3.3+ installed because the file is a zip, and no matter what I do with it (extracting contents and using the .img within, changing .zip to .img) I get some error. I don't actually know what it is off the top of my head, but I tried to do it more than once in the past and always ran into the same problem.

Nicholo said:
Okay, now this is where I run into the TWRP problem I mentioned. I can't get TWRP 6.3.3+ installed because the file is a zip, and no matter what I do with it (extracting contents and using the .img within, changing .zip to .img) I get some error. I don't actually know what it is off the top of my head, but I tried to do it more than once in the past and always ran into the same problem.
Click to expand...
Click to collapse
You use autorec for twrp?
Sent from my LG-VS980 using XDA Free mobile app

Nicholo said:
Okay, now this is where I run into the TWRP problem I mentioned. I can't get TWRP 6.3.3+ installed because the file is a zip, and no matter what I do with it (extracting contents and using the .img within, changing .zip to .img) I get some error. I don't actually know what it is off the top of my head, but I tried to do it more than once in the past and always ran into the same problem.
Click to expand...
Click to collapse
Do you have a custom recovery? If so, flash the 2.7.x.x zip within your current recovery, then reboot recovery. If you don't have a custom recovery, then use autorec or freedom tool to install one.
Sent from my VS980 4G using XDA Premium 4 mobile app

[Q] Flashing KK Modem

Hello,
I would really appreciate any help/information around flashing the KK modem. I'm currently on CM11 and interested in moving some other ROM's, but many of them indicate that I have to flash the KK modem. I currently have Baseband version 12B. I'm just looking for a little instruction or guidance around the process of flashing the modem.
I've had some folks say it's a fairly detailed process and others who have said just download the zip and flash from TWRP. I'm a little hesitant, and not sure what is correct.
Any help is greatly appreciated.
Thanks in advance.

liquidamber said:
Hello,
I would really appreciate any help/information around flashing the KK modem. I'm currently on CM11 and interested in moving some other ROM's, but many of them indicate that I have to flash the KK modem. I currently have Baseband version 12B. I'm just looking for a little instruction or guidance around the process of flashing the modem.
I've had some folks say it's a fairly detailed process and others who have said just download the zip and flash from TWRP. I'm a little hesitant, and not sure what is correct.
Any help is greatly appreciated.
Thanks in advance.
Click to expand...
Click to collapse
Personally I'd suggest doing the return to stock process, let it take the KK OTA then re-root it with ioroot and re-install recovery with autorec. just to ensure everything gets updated properly.

mjones73 said:
Personally I'd suggest doing the return to stock process, let it take the KK OTA then re-root it with ioroot and re-install recovery with autorec. just to ensure everything gets updated properly.
Click to expand...
Click to collapse
I have also been told that would be best, as well. And now I'm thinking that's what I'll do. I was able to root it fairly easily with ioroot and the return to stock process seems pretty straightforward, so I'll noob my way through that.
I appreciate your response.

liquidamber said:
I have also been told that would be best, as well. And now I'm thinking that's what I'll do. I was able to root it fairly easily with ioroot and the return to stock process seems pretty straightforward, so I'll noob my way through that.
I appreciate your response.
Click to expand...
Click to collapse
Use this method: http://forum.xda-developers.com/showthread.php?t=2711668
Worked great for me. Make sure to follow maladus directions

Nexus 6 Help

Hi I have a few questions for my nexus 6 that I am getting today
1) I am going to flash a the new marshmallow update, which one should I pick because for root you need a specific build but on the google factory images the latest build is not supported? I really don't know.
2) After I flash 6.0 can I just do the fastboot flash recovery twrp.img without flashing the boot.img
3) When I go to a new rom like Chroma by Zephik do I still need to change the boot.img to flash the beta super user
For now these are all my questions and I would really appreciate if you could answer it.
side note: I cannot use NRT becuase I am on a mac, if you guys have any alternatives I would really appreciate it too.

1) Flash any of them, they are all rootable. I would recommend going with the latest one. Unless I am mistaken, I believe K, N, and R each have the same radio so there effectively would be no real difference in the end result, as a custom ROM will overwrite everything else.
2) Yes, there is no need to have a modified boot image or root if you plan on flashing a custom ROM.
3) This depends on the ROM, they should have instructions in their post as to what they require. I am pretty sure Chroma comes with a custom kernel already, and I believe it comes pre-rooted as well. It could be that you have to root the ROM after you flash it if you want root though, there are some ROMs that are like that. The OP should have installation instructions.
As for your side note, I don't recommend using a toolkit of any sort. I recommend learning how to use fastboot, and doing it manually. That way if you were to need to fix something in the future, you would have a general understanding of what you did and why, and perhaps that will help you in how to fix it. Rather than clicking a couple buttons in a toolkit. Also, toolkits can fail, and not tell you why. It is often hard to figure out what went wrong when it is doing multiple steps at once, rather than one at a time like if you were to do it the manual way. It really isn't that difficult, and it is very well documented process at this point with tons of guides with pictures and even videos out there.

cupfulloflol said:
1) Flash any of them, they are all rootable. I would recommend going with the latest one. Unless I am mistaken, I believe K, N, and R each have the same radio so there effectively would be no real difference in the end result, as a custom ROM will overwrite everything else.
2) Yes, there is no need to have a modified boot image or root if you plan on flashing a custom ROM.
3) This depends on the ROM, they should have instructions in their post as to what they require. I am pretty sure Chroma comes with a custom kernel already, and I believe it comes pre-rooted as well. It could be that you have to root the ROM after you flash it if you want root though, there are some ROMs that are like that. The OP should have installation instructions.
As for your side note, I don't recommend using a toolkit of any sort. I recommend learning how to use fastboot, and doing it manually. That way if you were to need to fix something in the future, you would have a general understanding of what you did and why, and perhaps that will help you in how to fix it. Rather than clicking a couple buttons in a toolkit. Also, toolkits can fail, and not tell you why. It is often hard to figure out what went wrong when it is doing multiple steps at once, rather than one at a time like if you were to do it the manual way. It really isn't that difficult, and it is very well documented process at this point with tons of guides with pictures and even videos out there.
Click to expand...
Click to collapse
Thanks so much, I actually used adb/fastboot when I was rooting my mytouch 4g so this knowledge should come in handy, one other question if I were to root the latest factory image can I use the MRA58K.img that Chainfire posted for 6.0 or do I have to find a modified boot img that matches the latest factory image which is MRA58R, thank you so much again

Is "Copy partitions zip" still needed when prepping for roms with official firmware?

Is "Copy partitions zip" still needed when prepping for roms with official firmware?
In the following threads and others, I'm seeing the first step listed as crucial, and involving flashing this small zip file in order to populate the B slots of the phone:
https://forum.xda-developers.com/moto-x4/how-to/guide-install-android-9-0-pie-gsi-moto-t3833860
https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265
However, in more recent tutorials as well as the (awesome) videos I've seem floating around from munchy, this step is not shown. In fact, the act of "populating the B slots" now seems tied to flashing a copy of the official firmware in order to prep for custom roms.
I'm a little bit confused about wether the official firmware is now a replacement for this original "copy-partitions-payton.zip" file. Aside from a couple of OP's, I don't see anybody mentioning this file anymore. Also, when instructions are given on "populating the B slots" it seems to now refer to the official firmware flashing process.
Am I getting all of this correct? Is flashing the official firmware a replacement for the step of flashing the copy-partitions-payton.zip file?
I've already unlocked my bootloader.
I really apologize if I'm asking obvious questions, but this is my first android phone in 5 years and I really, REALLY don't want to screw this up. I've had a lot of catching up to do and have been doing a ****-ton of reading in this forum. I think I have the rest of the flashing process figured out... I just want to do the first step right. Thank you so much XDA for being the resource for people like me!!

we still need it. which video doesn't have this step? pretty sure i did mention it in all the videos. if i did not , then my bad.

Hey man thanks so much for replying! I haven't actually seen it in any of the videos - unless I'm missing something incredibly obvious.
(for context - my ultimate goal is to flash LineageOS 15.1 and get root passing SafetyNet to the point where GPay works)
I started here to get the basics:
https://www.youtube.com/watch?v=bkmczD9tvEQ
This video starts right with flashing the stock firmware:
https://www.youtube.com/watch?v=2-Kcwjyk_Ls
This video I didn't understand at first, but eventually got that you're just explaining A/B slots, not necessarily giving a tutorial:
https://www.youtube.com/watch?v=zVwYxp30dps&t=119s
None of these have that specific zip being flashed.
So if I understand correctly the correct process after buying the phone would be...
1) Unlock bootloader
2) push needed zips to phone storage
3) fastboot into TWRP
4) flash copy-partitions-payton.zip
5) reboot into recovery
6) flash stock firmware (I'll be using PAYTON_FI_8.1.0_OPWS28.46-21-8_subsidy-DEFAULT_regulatory-DEFAULT_CFC)
6) ...and basically follow the rest of your video to a T from there.

Hey I was wrong sorry - it's totally in the Android P video. So that was super helpful... and I just finished flashing everything successfully! I did not seem to have to flash the stock firmware at all - I simply flashed copy-partitions-payton.zip, did a factory reset, and moved right on to flashing LineageOS.
So does this mean that copy-partitions-payton.zip and flashing a copy of stock firmware accomplishes the same thing?
This is also missing from the official Lineage documentation, fyi:
https://wiki.lineageos.org/devices/payton/install
Thanks for your videos, they've been super helpful and so far no problems with my flash.

amirite said:
So does this mean that copy-partitions-payton.zip and flashing a copy of stock firmware accomplishes the same thing?
Click to expand...
Click to collapse
What do you mean by flashing a copy of stock firmware? Where is it asking you to flash stock firmware, the guide assumes you are on stock firmware. Also, if you have LOS already running dont bother about it too much. The original instructions explaining all this were in the LOS thread I created, which was transferred to Erfan once LOS was official. Now, the original instructions are no longer there. So, just forget about them and enjoy your custom rom :highfive:

I surely am Everything is running perfectly, except for a couple of minor crashes of the settings app. No biggie. Thanks again for the reply, I'm sure I'm mis-reading a few things pretty badly, but this is helping.
When you use the flash_all.sh script in your videos (at 4:45 in the 2nd video), is that not flashing the stock firmware? Isn't that zip directly from Motorola and flash_all.sh flashes the entire phone back to stock?
I assumed that flashing the stock firmware was a way of putting the phone in a known-good state before continuing with you guide. But then you talk about how Motorola didn't populate the B slots. So I'm just not exactly clear on what the copy-partitions-payton.zip does. I did flash that, but I didn't have to use flash_all.sh at all.

amirite said:
I surely am Everything is running perfectly, except for a couple of minor crashes of the settings app. No biggie. Thanks again for the reply, I'm sure I'm mis-reading a few things pretty badly, but this is helping.
When you use the flash_all.sh script in your videos (at 4:45 in the 2nd video), is that not flashing the stock firmware? Isn't that zip directly from Motorola and flash_all.sh flashes the entire phone back to stock?
I assumed that flashing the stock firmware was a way of putting the phone in a known-good state before continuing with you guide. But then you talk about how Motorola didn't populate the B slots. So I'm just not exactly clear on what the copy-partitions-payton.zip does. I did flash that, but I didn't have to use flash_all.sh at all.
Click to expand...
Click to collapse
What I understand is that Moto does not flash both slots by default, but flashing the flash-all does both slots with the stock firmware. If you are on the default stock setup, copy-partions will just copy your the Moto default to the other slot.

Got it. So basically the main goal with that first step is simply to populate the B slot which can be achieved by either method. Thanks guys, I just wanted to make sure I understood the full scope of what had to be done. Always an adventure catching up to the many months of hard work y'all do to get us here. Much appreciated and I'm enjoying my new setup a bunch!

amirite said:
In the following threads and others, I'm seeing the first step listed as crucial, and involving flashing this small zip file in order to populate the B slots of the phone:
https://forum.xda-developers.com/moto-x4/how-to/guide-install-android-9-0-pie-gsi-moto-t3833860
https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265
However, in more recent tutorials as well as the (awesome) videos I've seem floating around from munchy, this step is not shown. In fact, the act of "populating the B slots" now seems tied to flashing a copy of the official firmware in order to prep for custom roms.
I'm a little bit confused about wether the official firmware is now a replacement for this original "copy-partitions-payton.zip" file. Aside from a couple of OP's, I don't see anybody mentioning this file anymore. Also, when instructions are given on "populating the B slots" it seems to now refer to the official firmware flashing process.
Am I getting all of this correct? Is flashing the official firmware a replacement for the step of flashing the copy-partitions-payton.zip file?
I've already unlocked my bootloader.
I really apologize if I'm asking obvious questions, but this is my first android phone in 5 years and I really, REALLY don't want to screw this up. I've had a lot of catching up to do and have been doing a ****-ton of reading in this forum. I think I have the rest of the flashing process figured out... I just want to do the first step right. Thank you so much XDA for being the resource for people like me!!
Click to expand...
Click to collapse
Well, I did not need it. I just went from stock android 9 to LineageOS 16.