Hi,
I'm currenty using CyanogenMod 10, probably switching to CM 10.1 when SakuraDroid RC1 releases.
My current baseband version is XXMF1, I see that XXMG2 is the most recent one.
Is it good practice to always update to the most recent baseband? Or is it ROM-specific what the best baseband version is, and should I ask this question on the thread of the ROM I'm using?
How do I go about only updating the baseband version without flashing over my CM firmware?
Thanks
Yes, it's good to upgrade to the new baseband if there are changes in changelog - but there no way to upgrade it without flashing. Just go ahead and install new firmware, and next CM.
Related
Hello all!
I've got an unofficial version of a custom ROM installed on my phone and I want to migrate to an official nightly version of the ROM. Can I flash the official version over the top of the unofficial version, or do I have to do the full memory wipe process and treat it as a completely new ROM?
Hello, everyone. I have a S3 L710 (Boost Mobile) that is currently running 4.3 stock/root and I want to update to CM11 Kit Kat. I currently have philz touch 6.07.9 d2spr recovery manager and have made a nandroid backup.
When I try and flash any version of 4.4 (I've tried various nightly builds and Bean Stalk) it just gives me a status 7 error. When I remove the asserts I just get install aborted. Here is a log of my most recent attempt: http://pastebin.com/x1AJVqqM
Here is my about device information:
Model Number: SPH-L710
Android Version: 4.3
Baseband Version: L71j0vpubmk5
Kernel Version (Line 1): 3.031
Build Number: JSS15J.L710Vpubmk5
SE for android status: permissive
Hardware version: l710.14
Any ideas? Do I have an incompatable bootloader or something? If so, how do I upgrade that?
So far I've tried to get the following roms installed. They all fail with the same error that is specified in the OP.
Cyanogenmod 11 (20140116 and 20140104): http://download.cyanogenmod.org/?device=d2spr
Cyanogenmod 10.2.0-d2spr: http://download.cyanogenmod.org/?device=d2spr
Beanstalk: http://forum.xda-developers.com/showthread.php?t=2558705
EXCEPT, I did just get MOAR 7.1.0 to flash to my phone successfully: http://forum.xda-developers.com/showthread.php?t=2572102
So at least I'm on 4.3 now..
Colleagues,
I have an SGH-i317 AT&T Galaxy Note II. It is rooted, has TWRP 2.8.1.0 and SuperSU 2.46 and TitaniumBackup all of which work just fine. I used Odin 3.10. I'm about to flash custom ROMSs CM10.2 and CM11. I have a couple things I don't quite understand before I flash. Hopefully someone can help. In the past, AT&T forced OTA upgrades so I'm at runnign rooted 4.4.2. (Specifics on my firmware are below.)
1. I know Android has broken a third party app's ability to save files to the external SIM. Is this problem inherent ONLY to vendor 4.4.2 builds like AT&T's, or does CM and other custom ROMS that are based upon 4.3 and 4.4 suffer from the same dumb limitation?
2. I've read online that the boot loader software became vendor-signed-package aware and is now a "locked" bootloader. AT&T forced my perfectly good 4.1.2 to go to 4.3 and consequently to 4.4.2. Is it not possible to actually replace that bootloader? If not, why not? Is that not possible at this time?
3. I noticed that for my SGHi317 that there is no such thing a an t0lteatt anymore for CM11 since they have merged their development branches. So will the latest t0lte work for SGH-i317? Do I need to do anything special other that flash it and the correct gapps to the phone?
Thanks for the help!
Model SGH-i317
Android 4.4.2
Baseband I317UCUCNJ1
Kernal Version 3.0.31-1728680
Buil number KOT49H.I317UCUCNJ1
I have a Nexus 7 2013 WiFi (Flo) of build number LMY48G currently running 5.1.1. I would like to flash Marshmallow but after some searching I am getting the impression this isn't possible for my build number.
No 6.0.0. image is listed on the official Google images page or on this list compiled here on XDA. However on another Google site, it lists "Nexus 7 (flo/deb)" of build numbers MRA58K and MRA58N having Marshmallow compatibility.
Am I correct in understanding that I cannot flash an image made for MRA58K/MRA58N on my LMY48G because of underlying hardware differences, and that there is no image available for my build? Will this brick my device?
I appreciate the advice, this is only my second time flashing a device and I just got this tablet and dont' want to brick it
LMY48G is just a build number for one of the official lollipop firmware for Flo. There is nothing stopping you from flashing the latest Marshmallow firmware. Just make sure you flash the correct version as there is a 3G (Mobile) version as well. From what you are saying you have the WIFI version for which the latest Marshmallow build is MRA58V.
Please read thoroughly on how to flash official firmware before you do so. It seem to me you may not be very confident in doing this.
abdulhamid1978 said:
LMY48G is just a build number for one of the official lollipop firmware for Flo. There is nothing stopping you from flashing the latest Marshmallow firmware. Just make sure you flash the correct version as there is a 3G (Mobile) version as well. From what you are saying you have the WIFI version for which the latest Marshmallow build is MRA58V.
Please read thoroughly on how to flash official firmware before you do so. It seem to me you may not be very confident in doing this.
Click to expand...
Click to collapse
Thank you, yes I am using the WiFi version. And you are correct, this is only the second time I've flashed a ROM and the first time was Cyanogenmod with an automatic loader. I will definitely educate myself before proceeding...:good:
Updated SM-T705 to latest CM 12.1 Nightly available (20160529) and "No SIM Card"
I just upgraded my ROM from a older version of Android 5.1 that was like a Feb/March build of CM 12.1. I took the latest that was offered via the CM Updater; and after backing up it applied succesfully. However, even though the SIM card is installed in the tablet, the Baseband seems to be stuck on "Unknown". My device is a SM-T705 - the Exynos variant.
My question is: Does this bug mean they broke the radio support for the klimtlte builds of CM12.1? Or do I need to update the radio firmware? I'm using the lollipop radio that I was using with the previous build and it was working fine, but I wanted to update because well, updates are good right?
If push comes to shove I might just roll back to my ROM backup and continue using that.