Idk if im supposed to be able to do this but I can flash different roms over each other without it messing up, there's been times where a rom didn't flash until I flashed it over another rom, not sure if its a normal thing
Sent from my SM-G900P using XDA Free mobile app
rgconcept23 said:
Idk if im supposed to be able to do this but I can flash different roms over each other without it messing up, there's been times where a rom didn't flash until I flashed it over another rom, not sure if its a normal thing
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
The standard answer here would be an emphatic no.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Thank you, and would it be a benefit or a bad thing?
Sent from my SM-G900P using XDA Free mobile app
rgconcept23 said:
Thank you, and would it be a benefit or a bad thing?
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
When flashing over systems you can have very bad consequences. ..ie settings may force close and such ...
Sent from my SM-N900P using Xparent BlueTapatalk 2
I do worry about that and feel like if its not as clean as it could be but I just hope nothing catastrophic happens, I actually sometimes get some features of different roms by doing that, and ive also wondered about the modem or whatever NAB and NCD mean, like ive seen people talk about needing to update and am not sure how important that is
Sent from my SM-G900P using XDA Free mobile app
rgconcept23 said:
I do worry about that and feel like if its not as clean as it could be but I just hope nothing catastrophic happens, I actually sometimes get some features of different roms by doing that, and ive also wondered about the modem or whatever NAB and NCD mean, like ive seen people talk about needing to update and am not sure how important that is
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
If you "dirty flash," there's no problem with that, just know that if you ever encounter an error, we will be unable to help you in any way.
You're right, cross-flashing might leave remnants (features) of the previous ROM, but there's no guarantee that they'll be utilized correctly or linked correctly to the system files. As far as I know, the "worst" thing that could happen by dirty flashing is an unrelenting boot-loop. In those cases, you should just do a full system wipe and re-install the ROM.
I recommend, as Micmars does, a full system wipe prior to installing any ROM, but to each their own.
Typically, ROMs do not install different modems. As far as the MJ4 vs. NAB vs. NC5, here's a little primer on the various versions:
MJ4
This was the last Jellybean TW released for the Sprint Note 3. If you are on MJ4, you'll have to update your bootloader to NAB (or NC5) in order to update to KitKat ROMs (and you can't go back). The
NAB
This is the first KitKat TW ROM for the Sprint Note 3. Once on NAB, you can't go back down to Jellybean (yet... some people are working on it). You need to be on the NAB or NC5 bootloader in order to flash these ROMs.
NC5
This is the second KitKat TW release for the Sprint Note 3. It introduced some updates to the system and it includes WiFi calling (I've never used it, but others say it's really nice). You can flash back and forth between NAB and NC5 ROMs as much as you want, without changing anything. You need to be on the NAB or NC5 bootloader in order to flash these ROMs.
As far as updating to NC5 ROMs, just look at the changelogs between the NAB and NC5 versions of the ROM. If the added/changed features look appealing to you (or it looks more stable), then by all means update.
As far as modems go, I always stick to the newest Modem, which always tend to work best for me (I'm in a large metropolitan area). Sometimes people will report that the older modems (MJ4 or NAB) work better in their area. The Modems are completely separate from the ROMs, so flashing an older (or newer) modem should not have any affect on the stability of the ROM. It's really up to you if you want to update it.
As far as bootloaders go, if you are already on KitKat ROMs, I'd recommend updating to the NC5 Engineering Bootloader, but as long as you're on NAB, you should be fine. Just make sure to read the OP of any ROM you flash, they typically will tell you what version of the bootloader you need to be on.
Related
Okay, I have an MDK S4, rooted, cwm installed, running Cyanogenmod. I've heard the new baseband has some signal improvements, and I'm a sucker for the newest and best, but I'm leery of my typical 'flash it and see' methodology here.
I -think- I can just flash the modem in ODIN and go, but I would really appreciate hearing from someone that's already done this, first. Any cons? Can it be undone? Are there any potentially unexploded mines in this update that I should be wary of?
Sent from my SCH-I545 using xda premium
What is ME7.. please guide me briefly
I have heard this causes problems with wifi and other possible problems. Flash at your own risk.
Sent from my SCH-I545 using Tapatalk 2
zeeshanaayan07 said:
What is ME7.. please guide me briefly
Click to expand...
Click to collapse
The new baseband included in the root-killing Verizon OTA
From what I have understood you might me able to flash just the modem, though I don't know what kind of issues the lack of firmware may cause.
Sent from my Nexus 7 using xda premium
I flashed the ME7 radios through Odin using the information gleaned from this thread: http://forum.xda-developers.com/showthread.php?t=2358007
I haven't had any signal issues, so haven't felt the need to try and revert - however there is a revert image in that thread which should take you back to the original radios. I flashed the new ones a few hours after getting the phone and haven't looked back.
I'm pretty sure my phone is also a time machine...here's why, and please clear this up for me. I have tried googling this to find out how I ended up with such a special Super Galaxy S4. I got my Verizon S4 back in April last year and have been rooted ever since it was possible...so, in other words I have one of the original MDK builds. Why am I always reading about people freaking out because of 'accidentally' upgrading their firmware on these builds...hang on, let me continue. I have flashed a ROM on my phone about 131 times, and flashed maybe 2 or 3 radios...after doing so, my baseband and build numbers would change pretty regularly... to ME7, MK2, and everything in between. I have absolutely no trouble flashing whatever I want for the most part, and can always go back to MDK...why is this? I have lots of theories but they all revolve around me being awesome...and I'm sure you'd rather not hear them. Can anyone explain this?
calebcabob said:
I'm pretty sure my phone is also a time machine...here's why, and please clear this up for me. I have tried googling this to find out how I ended up with such a special Super Galaxy S4. I got my Verizon S4 back in April last year and have been rooted ever since it was possible...so, in other words I have one of the original MDK builds. Why am I always reading about people freaking out because of 'accidentally' upgrading their firmware on these builds...hang on, let me continue. I have flashed a ROM on my phone about 131 times, and flashed maybe 2 or 3 radios...after doing so, my baseband and build numbers would change pretty regularly... to ME7, MK2, and everything in between. I have absolutely no trouble flashing whatever I want for the most part, and can always go back to MDK...why is this? I have lots of theories but they all revolve around me being awesome...and I'm sure you'd rather not hear them. Can anyone explain this?
Click to expand...
Click to collapse
Well I think your referring to flashing custom ROMs that are " upgraded" past MDK. You can obviously do that without issue. You can also flash any modem you want ( baseband ).
But what people are referring to when they say do NOT update an MDK phone is either an OTA Update directly from Verizon... Or using Odin to flash stock firmware beyond MDK.
If you do that your bootloaders going to lose the Loki Exploit and bye bye custom recovery... Follow me??
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
---------- Post added at 10:46 PM ---------- Previous post was at 10:43 PM ----------
Grab this app
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Your bootloaders going to be MDK
And your radio will be whatever one you last flashed. And depending on what ROM you're running, in your about phone it MAY show you a different build other than MDK. That's just the build the Dev based the ROM off of.
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Like the poster above said, flashing Modems/Radios will change what's shown as your "baseband" in about phone, but won't affect your MDK bootloader. So your bootloader version was never upgraded/downgraded.
phew!
Ah...so it's not all about me. Thanks for the thoroughly explained answers from both of u guys. That really clears things up. And glad to know about the modem being OK to flash/upgrade. Well, I am EXTREMELY lucky- seeing how I tried an OTA update last week after having to flash a retail image to my S4 with Odin (soft brick)...because the OTA update failed! I will NEVER try that again!! Ha. Thanks for the info!
calebcabob said:
Ah...so it's not all about me. Thanks for the thoroughly explained answers from both of u guys. That really clears things up. And glad to know about the modem being OK to flash/upgrade. Well, I am EXTREMELY lucky- seeing how I tried an OTA update last week after having to flash a retail image to my S4 with Odin (soft brick)...because the OTA update failed! I will NEVER try that again!! Ha. Thanks for the info!
Click to expand...
Click to collapse
Definitely don't update via OTA or use anything in Odin other than MDK.!!!
After you root your phone use Titanium Backup and freeze "SDM " and "FWUpgrade" then make a backup in whatever recovery you're using.
Those two things being frozen ( I think SDM is good enough ) will stop any OTA possibility. Although being rooted and whatever else you may have done should be enough to stop it. No need to risk it lol
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Mistertac said:
Definitely don't update via OTA or use anything in Odin other than MDK.!!!
After you root your phone use Titanium Backup and freeze "SDM " and "FWUpgrade" then make a backup in whatever recovery you're using.
Those two things being frozen ( I think SDM is good enough ) will stop any OTA possibility. Although being rooted and whatever else you may have done should be enough to stop it. No need to risk it lol
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Hmm...I searched Titanium for SDM and anything with FW (FWUpgrade) in it, i dont see anything there. I tried just browsing too. Maybe BoneStock v2.1 (VZW, TW, 4.3) is built without those files already? I'd like to do what you're recommending though, that makes so much sense. I found "ConfigUpdater" but, that's probably not what I want, right?
calebcabob said:
Hmm...I searched Titanium for SDM and anything with FW (FWUpgrade) in it, i dont see anything there. I tried just browsing too. Maybe BoneStock v2.1 (VZW, TW, 4.3) is built without those files already? I'd like to do what you're recommending though, that makes so much sense. I found "ConfigUpdater" but, that's probably not what I want, right?
Click to expand...
Click to collapse
I would imagine @andybones removed the OTA files from his rom.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Yea I was referring to if you were on stock MDK ... The devs most certainly remove all that junk. My bad for not making myself clear.. Thanks Josh
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
calebcabob said:
I'm pretty sure my phone is also a time machine...here's why, and please clear this up for me. I have tried googling this to find out how I ended up with such a special Super Galaxy S4. I got my Verizon S4 back in April last year and have been rooted ever since it was possible...so, in other words I have one of the original MDK builds. Why am I always reading about people freaking out because of 'accidentally' upgrading their firmware on these builds...hang on, let me continue. I have flashed a ROM on my phone about 131 times, and flashed maybe 2 or 3 radios...after doing so, my baseband and build numbers would change pretty regularly... to ME7, MK2, and everything in between. I have absolutely no trouble flashing whatever I want for the most part, and can always go back to MDK...why is this? I have lots of theories but they all revolve around me being awesome...and I'm sure you'd rather not hear them. Can anyone explain this?
Click to expand...
Click to collapse
There is no way to go back but if you are looking to update to 4.4.2 before the release let me know because I just updated!!! I will send screenshots upon request.
jake.99x3 said:
There is no way to go back but if you are looking to update to 4.4.2 before the release let me know because I just updated!!! I will send screenshots upon request.
Click to expand...
Click to collapse
Did u read that post lol
Sent from my HTC6525LVW using XDA Premium 4 mobile app
re: this thread.
I'm currently running a 4.4.2 Omnirom nightly on the original DE MDK bootloader/mode/radio. I would like to flash the MK2 radio as Verizon recently lit up AWS in my area and I'd like to take advantage of that. My questions are:
1) Can I safely flash modem, radio, and boot while maintaining my current TWRP recovery/Omnirom setup? I've seen scattered reports of issues booting AOSP ROMs on the newer bootloader.
2) If something goes bad, can I just ODIN back to MDK modem/radio/boot and start over and be okay?
3) Can I use Heimdall safely or do I neeeeeed to use ODIN? I only ask because my Windows partition is kinda ****y and I don't want to boot it if I don't have to
You don't need to do all that.
Go to this thread: http://forum.xda-developers.com/showthread.php?t=2487298
Surge made all the modems flashable zips you can flash in recovery. Use the DE modem only versions, not the one with NON-HLOS
Sent from my SCH-I545 using XDA Premium 4 mobile app
The zips there don't work because I'm still on the MDK bootloader. I need to upgrade to one of the newer bootloaders to use the new modems.
ervel flick said:
The zips there don't work because I'm still on the MDK bootloader. I need to upgrade to one of the newer bootloaders to use the new modems.
Click to expand...
Click to collapse
No you don't lol modems are independent of your bootloader, it's just not recommended to also flash the nonhlos bin with it. I can assure you most of us MDK users have upgraded our modems to at least MJ7 to take advantage of the AWS bands.
Sent from my SCH-I545 using XDA Premium 4 mobile app
joshm.1219 said:
No you don't lol modems are independent of your bootloader, it's just not recommended to also flash the nonhlos bin with it. I can assure you most of us MDK users have upgraded our modems to at least MJ7 to take advantage of the AWS bands.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I must be doing something wrong then, because when I flash any of those ZIPs my baseband doesn't change.
ervel flick said:
I must be doing something wrong then, because when I flash any of those ZIPs my baseband doesn't change.
Click to expand...
Click to collapse
Probably gotta go with the three finger salute then. Sometimes flashing lower level code requires a cold boot into recovery rather than just rebooting into recovery.
Turn your phone off then boot into recovery by holding vol up + home + power. Try flashing a modem again and it should work.
Sent from my SCH-I545 using XDA Premium 4 mobile app
joshm.1219 said:
Probably gotta go with the three finger salute then. Sometimes flashing lower level code requires a cold boot into recovery rather than just rebooting into recovery.
Turn your phone off then boot into recovery by holding vol up + home + power. Try flashing a modem again and it should work.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've tried that and sadly no joy. It seems I need the newer bootloaders to use the newer modems - I just need to know if the newer bootloaders will play nice with AOSP ROMs.
ervel flick said:
I've tried that and sadly no joy. It seems I need the newer bootloaders to use the newer modems - I just need to know if the newer bootloaders will play nice with AOSP ROMs.
Click to expand...
Click to collapse
You can only run AOSP roms on an unlocked or loki'd bootloader, such as we have.
Upgrading your bootloader at all will lock it. You can use safestrap and flash tw roms only. All of the firmware after MDK is locked.
Sent from my SCH-I545 using XDA Premium 4 mobile app
joshm.1219 said:
You can only run AOSP roms on an unlocked or loki'd bootloader, such as we have.
Upgrading your bootloader at all will lock it. You can use safestrap and flash tw roms only. All of the firmware after MDK is locked.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
There are two, newer, unlocked Developer Edition bootloaders after MDK.
ervel flick said:
There are two, newer, unlocked Developer Edition bootloaders after MDK.
Click to expand...
Click to collapse
Can you flash those on an MDK phone?
Sent from my SCH-I545 using XDA Premium 4 mobile app
joshm.1219 said:
Can you flash those on an MDK phone?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah, but I saw that AOSP ROMs may have trouble booting on them. I linked to them in my OP.
ervel flick said:
Yeah, but I saw that AOSP ROMs may have trouble booting on them. I linked to them in my OP.
Click to expand...
Click to collapse
You should try PM'ing Surge to see if he can help
Sent from my SCH-I545 using XDA Premium 4 mobile app
Well I'm using the S4 DE as a backup until my insurance replacement G2 comes tomorrow. Once I get that, I'll probably just flash the MK2 stuff and report back.
Ok, so here's been my experience thus far.
1) MK2 bootloader flashed in ODIN fine, but Omnirom wouldn't boot after that. TW-based GPE ROM did, so it looks like the newer bootloader doesn't work wit AOSP ROMs.
2) MK2 radio .tar.md5 wouldn't flash in ODIN at all, failed every time. CWM-flashable ZIP version flashed without error but now calls don't work; com.android.phone crashes when I try to place or receive a call. CDMA and LTE data work fine.
3) AWS IS SO FAST OMG
addendum 5/5/14
So, heimdall works just fine flashing the above modems. I flashed the MK2 modem and NON-HLOS bins as well as the MK2 bootloader (which was already working fine from the ODIN flash but what the hell). I used heimdall in Linux, so I'm assuming my earlier flashing issues were due to my semi-hosed Windows install. CDMA seems to be working for texts now. com.android.phone still crashes on outbound and inbound calls, but at this point since SMS works my guess is that it's a ROM issue.
addendum 2, 5/5/14
Call issues were a ROM issue. Formatted /system and /data, reflashed Omnirom, and all is well.
Guys...
SOrry if this is a poor post, but I'm still new to the gs4 on verizon.
When I got the phone about a week ago, It immediately took an OTA upgrade. I'm geussing this was a mistake?
Only reason I say this, is because i'm now on NC5, and it seems that I'm limited as to what I can do as far as ROMS.
However, I'm seeing that there are people on "MDK" which I'm assuming is an older base...are able to put whatever AOSP rom posted in the forum....
DO all phones comes with MDK base?
I can call them and ask to send a replacement....what are the chances its MDK?
A little help would be appreciated....Thanks!
Doubtful vzn has any phones left with mdk (I'm assuming, it was the original base when this phone came out last summer). If it makes you feel any better you were probably on mk2 4.3 when you took the upgrade, so you didn't really lose anything.
You can root, just no custom kernels, no custom recoveries, just safestrap. I'm running a Google play edition aosp 4.4.3 on safestrap and it runs pretty well. There's a thread in the general section.
Sent from my SCH-I545 using XDA Premium 4 mobile app
docluv01 said:
Guys...
SOrry if this is a poor post, but I'm still new to the gs4 on verizon.
When I got the phone about a week ago, It immediately took an OTA upgrade. I'm geussing this was a mistake?
Only reason I say this, is because i'm now on NC5, and it seems that I'm limited as to what I can do as far as ROMS.
However, I'm seeing that there are people on "MDK" which I'm assuming is an older base...are able to put whatever AOSP rom posted in the forum....
DO all phones comes with MDK base?
I can call them and ask to send a replacement....what are the chances its MDK?
A little help would be appreciated....Thanks!
Click to expand...
Click to collapse
MDK bootloader was on the original GS4 and an exploit called loki was found that could bypass the bootloader lock so that you could root & install a custom recovery like TWRP or CWM & thereby flash both TouchWiz and AOSP roms. Thanks to Vzw /Att /Samsung, ota updates were issued that kills this exploit. All new phones are locked down. Can still root & use Safestrap recovery to flash TW based roms into a "sandbox" parallel system. Can't flash new kernels though.
Got it! Thanks
You know I looked at that ROM....considering giving it a try.,
Im on NC5 and SS, are there any issues with GPS etc?
rrrrrrredbelly said:
Doubtful vzn has any phones left with mdk (I'm assuming, it was the original base when this phone came out last summer). If it makes you feel any better you were probably on mk2 4.3 when you took the upgrade, so you didn't really lose anything.
You can root, just no custom kernels, no custom recoveries, just safestrap. I'm running a Google play edition aosp 4.4.3 on safestrap and it runs pretty well. There's a thread in the general section.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
docluv01 said:
Got it! Thanks
You know I looked at that ROM....considering giving it a try.,
Im on NC5 and SS, are there any issues with GPS etc?
Click to expand...
Click to collapse
I have flashed several ss compatible kitkat roms and used gigilies nc2 wifi fix and never had issues with wifi or bluetooth or GPS
sent by safestrap powered echo v26
Hello, not new to rooting and such but I'm a little confused. Just got this Note 2 after breaking my G2. I'm on ND7, managed to root and install safestrap. I've made a stock back up and flashed over my stock as there is no rom slot support yet. I've flashed Alliance 30 and it worked well. My question is, can I flash other Rom's like Wilson's CM12? My bootloader is still locked. Is there a safe way to unlock it? I've searched and found that if you have a locked bootloader you can't flash kernels. I think? Not trying to be annoying. Just confused. I haven't used safestrap since my old Razr days, lol. Any help would be awesome. Thanks in advance. ..
Sent from my SCH-I605 using XDA Free mobile app
I think you can flash any rom using safestrap. The only ones I tried so far are DN3 and Alliancerom. They flashed with no problems. I would like to add on to this question though, Can I flash any mods using safestrap?
Right. Or kernels for that matter? It's strange because there's some people with unlocked bootloader's, some with safe strap, and some just plain old stock rooted (which was a pain in it's self).
Sent from my SCH-I605 using XDA Free mobile app
Did a little more digging into the thread, basically if your bootloader is locked, the only Rom's that you can flash are those with the same build and kernel that you are currently on. So you were right. As far as flashing mods with safestrap, still unsure. ???
Sent from my SCH-I605 using XDA Free mobile app
No other ROMs besides the above mentioned? Seems almost worth sending it to that company to downgrade
any group pricing?
Installed Mocha DrIzzle, liking it so far except the network speed mod
If I couldnt stand to be without telelphone....
stoph8n24 said:
No other ROMs besides the above mentioned? Seems almost worth sending it to that company to downgrade
Click to expand...
Click to collapse
I'd be on the "Send it Off" wagon.
I've seen destructions for using ODIN to flash a KIES image in, and then go about fixing it that way but many many more posts saying this is impossible.
What I'd like to know, if I have to go with the same darn kernel etc, is how the everloving **** to get rid of ALL and I mean *ALL* of the crapware/verizonware/amazonware/etc and completely strip the touchwhiz down to just what I need....
This phone thing is a nasty addiction....:cyclops:
stoph8n24 said:
No other ROMs besides the above mentioned? Seems almost worth sending it to that company to downgrade
Click to expand...
Click to collapse
Anyone know if there is a list? I was just given this phone. I rooted it, but also stuck with the locked boot loader. I did install Safestrap and did a back up, and was able to create a ROM slot, but that is all I've done so far.
Since I'm "developmentally chsllenged" (I can follow instructions, but I can't do any development work or anything) I try to just go with trusted info, which has worked so far. I just came from a RAZR Maxx HD with CM12 and am not happy with the way this phone runs.
I'm in the same boat as you guys, and I believe you can only flash 4.4.2 ROMs. That's what I gathered from the Safestrap thread. However, you can (and should) backup your stock ROM in Safestrap and flash other ROMs over that.
I'm currently using Alliance, and it's decent. Nowhere near the amount of modifications as CyanideL, which is really what I want, but can't install because it's currently on Android 5.x.
Ridiculous what Samsung has done to this phone. Glad it was relatively cheap though, good lesson to avoid any manufacturer who locks the bootloader in the future.
Does anyone know if we can just flash an older version of the stock ROM? Couldn't we odin, or something, down to 4.1.x and go from there?
adobrakic said:
I'm in the same boat as you guys, and I believe you can only flash 4.4.2 ROMs. That's what I gathered from the Safestrap thread. However, you can (and should) backup your stock ROM in Safestrap and flash other ROMs over that.
I'm currently using Alliance, and it's decent. Nowhere near the amount of modifications as CyanideL, which is really what I want, but can't install because it's currently on Android 5.x.
Ridiculous what Samsung has done to this phone. Glad it was relatively cheap though, good lesson to avoid any manufacturer who locks the bootloader in the future.
Click to expand...
Click to collapse
I have SS and did a back up, but I thought I read about people running into problems and then bricking? I think they got them back after doing some stuff but since I am no where as talented with this stuff I try to be cautious. I've rooted and SS' ed a Bionic and ran several ROM's on that one until replacing it with a RAZR Maxx HD that I rooted (and was able to take advantage of the exploit before they pushed a patch and unlocked the bootloader).
If I can just flash over the stock ROM safely, then I'll get flashing right away
I read the issues with bricking as well, but I think those people were trying to flash 5.x ROMs. I agree about wanting to avoid it though. I have a HTC One S that I saved from being bricked a few times, but I don't even wanna have to go through the process of that for the Note 2. Here's the Safestrap thread, if you're a little wary and would like to read more about it.
As far as I can tell, you should be good with flashing 4.4.2 ROMs, since that's what I did and we seem to have the same config (4.4.2 Note 2, Safestrap 3.72). The only thing I wonder is what TWRP you have. I have the latest 2.7.0.x. If that's what you have, you should be just fine with flashing a 4.4.2 ROM over the stock ROM.