Database Users

New phone, MDB and rooted, should try to upgrade?

I just purchased a new AT&T Galaxy S4 via Amazon. Came with MDB software installed. I used the CASUAL root procedure and was successful. That left me with rooted MDB + TWRP recovery.
I am intending to stay with a stock ROM, not a complete custom ROM.
My question is: Should I try to update to a newer version of software? I believe right now I am two releases behind (MDB -> MDL -> MF3?)
I haven't been able to find much talking about the MDL version, so I don't know if there is anything useful in it (perhaps radio updates?). I did see some references to a performance enhancement which is always good.
I'm assuming I want to stay away from MF3 as there seems to be a lot of rapidly changing/conflicting information at this point about if and how one can get to that release (and keep root).
If I wanted to go to the MDL version, how would I go about it? I found two threads here:
http://forum.xda-developers.com/showthread.php?t=2348859&highlight=mdl
http://forum.xda-developers.com/showthread.php?t=2307157&highlight=mdl
Preferably, this would be done just as an update instead of wiping what I have now. But neither of those threads indicate if a wipe is necessary or if they can simply be installed on top of the stock MDB.
Appreciate any feedback!

cabadam said:
I just purchased a new AT&T Galaxy S4 via Amazon. Came with MDB software installed. I used the CASUAL root procedure and was successful. That left me with rooted MDB + TWRP recovery.
I am intending to stay with a stock ROM, not a complete custom ROM.
My question is: Should I try to update to a newer version of software? I believe right now I am two releases behind (MDB -> MDL -> MF3?)
I haven't been able to find much talking about the MDL version, so I don't know if there is anything useful in it (perhaps radio updates?). I did see some references to a performance enhancement which is always good.
I'm assuming I want to stay away from MF3 as there seems to be a lot of rapidly changing/conflicting information at this point about if and how one can get to that release (and keep root).
If I wanted to go to the MDL version, how would I go about it? I found two threads here:
http://forum.xda-developers.com/showthread.php?t=2348859&highlight=mdl
http://forum.xda-developers.com/showthread.php?t=2307157&highlight=mdl
Preferably, this would be done just as an update instead of wiping what I have now. But neither of those threads indicate if a wipe is necessary or if they can simply be installed on top of the stock MDB.
Appreciate any feedback!
Click to expand...
Click to collapse
You cannot OTA update to MF3 without ODINing back to stock - your custom recovery will prevent the update from working.
If you want to update to MDL, you can ODIN the stock MDL package and redo the CASUAL script.
I would suggest you stay on MDL until MF3 has not only root, but also custom recovery. At this point it's still too early to take the risk, even with a root access exploit now available.
If you want the updates, there are several ROMs available that incorporate updates...there's one that is almost completely stock MF3 without the bootloader (which is the main problem with it)...there's multiple based off of stock MF3 with some optimizations...and even some based on the latest Galaxy S4 International firmware which is several updates ahead of MF3.
Of course all that requires your willingness to install a custom ROM.

+1

I think you confirmed most of what I gathered - thanks for the clarifications.
jeffreii said:
If you want to update to MDL, you can ODIN the stock MDL package and redo the CASUAL script.
Click to expand...
Click to collapse
I did this, and it didn't do quite what I expected (although maybe it is better than I expected). I downloaded the MDL firmware from:
http://galaxys4root.com/galaxy-s4-stock-firmware/
AT&T Galaxy S4 SGH-I337 UCUAMDL (Android 4.2.2)
After flashing it with Odin, and my phone rebooted, I was surprised to note that it didn't actually WIPE my device. Everything was still in place, except now the device reports that it is in fact updated to MDL.
Is that right? I was expecting it to basically be in factory-new state after flashing.

cabadam said:
I think you confirmed most of what I gathered - thanks for the clarifications.
I did this, and it didn't do quite what I expected (although maybe it is better than I expected). I downloaded the MDL firmware from:
http://galaxys4root.com/galaxy-s4-stock-firmware/
AT&T Galaxy S4 SGH-I337 UCUAMDL (Android 4.2.2)
After flashing it with Odin, and my phone rebooted, I was surprised to note that it didn't actually WIPE my device. Everything was still in place, except now the device reports that it is in fact updated to MDL.
Is that right? I was expecting it to basically be in factory-new state after flashing.
Click to expand...
Click to collapse
Yes that's normal. It doesn't wipe your internal or external sd card. The parts you store info on

jd1639 said:
Yes that's normal. It doesn't wipe your internal or external sd card. The parts you store info on
Click to expand...
Click to collapse
Too easy, that basically gave me exactly what I wanted. I think I'm squared away until MF3 settles down.
Thanks for your time!

cabadam said:
Too easy, that basically gave me exactly what I wanted. I think I'm squared away until MF3 settles down.
Thanks for your time!
Click to expand...
Click to collapse
When you ODIN an upgrade to the same firmware, you don't get a wipe. It's nice to keep your settings in those situations!
Now just make sure you root/recovery so you can avoid the OTA...otherwise make sure you freeze the OTA apps.

jeffreii said:
When you ODIN an upgrade to the same firmware, you don't get a wipe. It's nice to keep your settings in those situations!
Now just make sure you root/recovery so you can avoid the OTA...otherwise make sure you freeze the OTA apps.
Click to expand...
Click to collapse
Haha yeah, I had spent some time backing up some settings via TB, nice to know I don't have to deal with that (at least for now )
Already re-applied the CASUAL root process. I froze the "AT&T Software Update" app. Is there anything other than that?

cabadam said:
Haha yeah, I had spent some time backing up some settings via TB, nice to know I don't have to deal with that (at least for now )
Already re-applied the CASUAL root process. I froze the "AT&T Software Update" app. Is there anything other than that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=44022554&postcount=74

Hmm, so I went and also froze LocalFOTA, but I dont have anything called FW Upgrade
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Good post.
I'm also on MDB. Do you think it's actually worth it to install the MDL update?
I'm currently running Kangabean with 4.3, if it matters.

Do not update ota may bypass mdl and go to mf3
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

deron37129 said:
Do not update ota may bypass mdl and go to mf3
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Nope. Would flash the MDL through Odin and immediately run Motochopper. Just trying to figure out if it's even worth it.

trunzoc said:
Nope. Would flash the MDL through Odin and immediately run Motochopper. Just trying to figure out if it's even worth it.
Click to expand...
Click to collapse
Definitely worth it. MDL irons out the issued that the S4 had upon release.
Sent from my SGH-I337 using Tapatalk 4

sd_N said:
Definitely worth it. MDL irons out the issued that the S4 had upon release.
Sent from my SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
Thanks!.
Here goes nothing
***EDIT***
Flashed the MDL image. I pulled the SIM to avoid any kind of OTA crap and booted. Got stuck at the AT&T logo though.
I had to go into stock recovery and do a factory reset. Did that and it booted up. Ran Motochopper fine and was able to boot into TWRP.
I restored by backup, but wouldn't boot past the Samsung Logo. Did another factory reset, but still wouldn't boot. Restored a backup I had of rooted stock. That worked.
Reset again and reinstalled Kangabean from scratch. That worked. Went back to recovery again and just restored my data partition. that worked too. yay
Pain in the arse, but let's see if MDL has any noticeable differences.

Thank you ALL!! I am also on MDB firmware and was wondering about all of this.
I do have some questions if you don't mind. (sorry for the thread hijack)
On MDB firmware, can you install a stock modded rom w/o updating the firmware?(such as MDOB and Goldeneye)
Is the MDB modem compatible with these roms or will I have to flash to a newer firmware to use them?
Knowing its working perfectly now, I'd like to stick with my current setup, but Id like the ability to use a stock modded TW rom, as I have a Samsung smart TV and use most of the Samsung bloatware.
Is there really any reason to go to MDL over MDB?

custommx3 said:
Thank you ALL!! I am also on MDB firmware and was wondering about all of this.
I do have some questions if you don't mind. (sorry for the thread hijack)
On MDB firmware, can you install a stock modded rom w/o updating the firmware?(such as MDOB and Goldeneye)
Is the MDB modem compatible with these roms or will I have to flash to a newer firmware to use them?
Knowing its working perfectly now, I'd like to stick with my current setup, but Id like the ability to use a stock modded TW rom, as I have a Samsung smart TV and use most of the Samsung bloatware.
Is there really any reason to go to MDL over MDB?
Click to expand...
Click to collapse
Check the roms you want to use. Most of them require mdl firmware.

4.3 update

Newbie here. I rooted the S4 a couple of months ago. Now that 4.3 is out, can experts post some step-by-step guide on how to upgrade it on rooted devices? Thanks.

Are you sure you want to update? Why not just flash a 4.3.1 rom to your device instead and stock to AMDL firmware.
However if it hasn't manually updated to MF3 you can go into your settings and search for updates, or it should automatically update on it's own. The only thing that would prevent it would be if you've flashed a non TW based ROM, changed the framework + kernel, or froze there processes needed to update. Just a stand alone root won't prevent it.
Sent from my SGH-I337 using XDA Premium 4 mobile app

I am not on MF3. I tried to install the AT&T minor update before, but it failed twice. I did freeze some stock apps. If I unfreeze those apps, the automatic update should work then? That's very good to know. Thanks!
Br4nd3n said:
Are you sure you want to update? Why not just flash a 4.3.1 rom to your device instead and stock to AMDL firmware.
However if it hasn't manually updated to MF3 you can go into your settings and search for updates, or it should automatically update on it's own. The only thing that would prevent it would be if you've flashed a non TW based ROM, changed the framework + kernel, or froze there processes needed to update. Just a stand alone root won't prevent it.
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse

Just to be clear you never got/took the OTA update to mf3?
If you still have the mdl bootloader then you will be able to update to a new rom that is based off the new att firmware MJ6 soon. I would wait until a good rom is out to flash rather than getting any OTA update. Once you go to mf3 firmware you cannot go back to a previous firmware and you are limited on what can be flashed to your phone. If you take the new OTA (whenever att actually releases it) you will be stuck on that firmware and not able to go back to a previous firmware.
So like in my situation I have the mdb or mdl bootloader still, rooted, and I can flash any rom I want whether it is a mdl/mf3/ international firmware/ or when available the MJ6 firmware. All of this is harder/not able to do if you ever get OTA updates.
Sent From My Spiderman Themed I337

I never got the MF3 update. As I mentioned, I did try it twice, but the update failed, either because I froze some apps, or because I installed the CWM custom recovery. It's good to hear that it is actually a good thing. I noticed that the 4.3 firmware is out (the general forum), should I just install that one? How should I start? Thanks.
RockRatt said:
Just to be clear you never got/took the OTA update to mf3?
If you still have the mdl bootloader then you will be able to update to a new rom that is based off the new att firmware MJ6 soon. I would wait until a good rom is out to flash rather than getting any OTA update. Once you go to mf3 firmware you cannot go back to a previous firmware and you are limited on what can be flashed to your phone. If you take the new OTA (whenever att actually releases it) you will be stuck on that firmware and not able to go back to a previous firmware.
So like in my situation I have the mdb or mdl bootloader still, rooted, and I can flash any rom I want whether it is a mdl/mf3/ international firmware/ or when available the MJ6 firmware. All of this is harder/not able to do if you ever get OTA updates.
Sent From My Spiderman Themed I337
Click to expand...
Click to collapse

wxiao said:
I never got the MF3 update. As I mentioned, I did try it twice, but the update failed, either because I froze some apps, or because I installed the CWM custom recovery. It's good to hear that it is actually a good thing. I noticed that the 4.3 firmware is out (the general forum), should I just install that one? How should I start? Thanks.
Click to expand...
Click to collapse
What until one of the devs creates a flashable zip that you can flash in cwm. It'll probably be only a couple of days now that the leak is out.

Downgrade to 4.2.2?

(I couldn't find a recent post or topic regarding this)
I upgraded to 4.3 last night. I greatly dislike it, and want to downgrade back to 4.2.2
I tried running my phone in Odin mode and installing an older version of 4.2.2 (from May, I believe), but every time I run it, the FAIL box appears. Is there a another way of downgrading, or I am doing it wrong?
Thanks for any and all help!

At this point you are stuck on 4.3 ( I'm guessing Mj6 leak) until there is an odin flashable rom for mj9 the Mj6 update contained knox security among other things that prevents the downgrade (blown qfuse and such) hope that answers your question
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

No you cannot downgrade from 4.3 back to 4.2.2
"I drive a Dodge Stratus!!"
sent from my smokin ATT S4A dripping AWESOMENESS

drakenjin said:
At this point you are stuck on 4.3 ( I'm guessing Mj6 leak) until there is an odin flashable rom for mj9 the Mj6 update contained knox security among other things that prevents the downgrade (blown qfuse and such) hope that answers your question
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I believe he took the OTA update that AT&T pushed overnight. But yes, your correct that he will be unable to downgrade for the foreseeable feature due to Knox and what will likely be another incremental qFuse. I'm staying on 4.2.2 with SafeStrap on MF3 for a few more weeks to see what developments take place due to the release of 4.3 finally.

We need to be more specific when stating limitations. We can assume MJ9 incremented the qfuse based on past updates. So what that means is you cannot revert aboot/BLs to a prior version. It remains unclear as to whether MJ9 BL's will boot prior kernels. I havent had a chance to look at the MJ9 files yet.

What about taking his phone to Best Buy to have them flash MF3 on it?
Could be they still have it in the computer maybe.

CZ Eddie said:
What about taking his phone to Best Buy to have them flash MF3 on it?
Could be they still have it in the computer maybe.
Click to expand...
Click to collapse
The blowing of a q-fuse means it is literally impossible to downgrade, even for Best Buy. Once you're on it, that's it. All they can do is take the new 4.3 build and flash it.

I received the OTA update.
Anyways, thanks for all the quick replies. Is there a way to re-add the "Mobile Data" toggle? I don't like how they removed that, and limited the toggle tray to 10 (instead of being able to scroll through all the toggles).
EDIT:
Is there a way to re-hide the apps in the App-Drawer? (I liked being able to display only the ones I wanted)

awsomeness!!!!!!!!!!!!
ThDrkKnight said:
(I couldn't find a recent post or topic regarding this)
I upgraded to 4.3 last night. I greatly dislike it, and want to downgrade back to 4.2.2
I tried running my phone in Odin mode and installing an older version of 4.2.2 (from May, I believe), but every time I run it, the FAIL box appears. Is there a another way of downgrading, or I am doing it wrong?
Thanks for any and all help!
Click to expand...
Click to collapse
NighthawkXL said:
I believe he took the OTA update that AT&T pushed overnight. But yes, your correct that he will be unable to downgrade for the foreseeable feature due to Knox and what will likely be another incremental qFuse. I'm staying on 4.2.2 with SafeStrap on MF3 for a few more weeks to see what developments take place due to the release of 4.3 finally.
Click to expand...
Click to collapse
hey guys just thought id inform you just in case you haven't seen it yet but this genius just made my day and it worked for me to downgrade partial via heimdal flash ( used terminal on my mac ) then adb upgrade using another awesome benefactors copy of .cfg update he captured just for the community just follow the steps in this thread by gtj0

Follow steps in what thread. Link?
Sent from my SGH-I337 using Xparent Skyblue Tapatalk 2

mattwheat said:
Follow steps in what thread. Link?
Sent from my SGH-I337 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
I believe he's talking about the Partial downgrade from MJ6 to MF3 so that you can upgrade to MJ9....thats the only thing i've seen.

Samsung S4 i337 frame upgrade encounter an issue please select recovery mode in kies
Today i have just want to downgrade to 4.2.2 via Odien of Stock File MF3 TARs, but may be i m make a mistake or may be somthing else happen my Samsung S4 AT&T-i337 failed to do this and then give me "frame upgrade encounter an issue please select recovery mode in kies"
So do it in Kies but i dont have Serial number of my Device as my battery and back sticker of phones are change here in Pakistan, now my phone is only give me "frame upgrade encounter an issue please select recovery mode in kies" this,
Please any one Help, will be appreciate

salimdawar said:
Today i have just want to downgrade to 4.2.2 via Odien of Stock File MF3 TARs, but may be i m make a mistake or may be somthing else happen my Samsung S4 AT&T-i337 failed to do this and then give me "frame upgrade encounter an issue please select recovery mode in kies"
So do it in Kies but i dont have Serial number of my Device as my battery and back sticker of phones are change here in Pakistan, now my phone is only give me "frame upgrade encounter an issue please select recovery mode in kies" this,
Please any one Help, will be appreciate
Click to expand...
Click to collapse
You can not downgrade the firmware. Just flash the firmware you were on before you tried to downgrade on Odin
Sent from my Nexus 5

jd1639 said:
You can not downgrade the firmware. Just flash the firmware you were on before you tried to downgrade on Odin
Sent from my Nexus 5
Click to expand...
Click to collapse
Ok i m downloading I337UCUFNB1 1.41 GB lets c it can flash it or not, before i were have this update in only 440 MB and installed from SD card directly in Recovery mode, but now my phone not going in recovery mode only can able to in Downloading mode
any How Thanks

salimdawar said:
Ok i m downloading I337UCUFNB1 1.41 GB lets c it can flash it or not, before i were have this update in only 440 MB and installed from SD card directly in Recovery mode, but now my phone not going in recovery mode only can able to in Downloading mode
any How Thanks
Click to expand...
Click to collapse
Boot into download mode then flash the stock firmware in Odin.
Sent from my Nexus 5

My i337 AT&T is back in action
salimdawar said:
Ok i m downloading I337UCUFNB1 1.41 GB lets c it can flash it or not, before i were have this update in only 440 MB and installed from SD card directly in Recovery mode, but now my phone not going in recovery mode only can able to in Downloading mode
any How Thanks
Click to expand...
Click to collapse
Good news, my phone back in to life and here the site from where i download KitKat
https://mega.co.nz/#!88MSyQoJ!8zxUFpiXhteaLDNemgqRbBSzy6gZJHRCPRW2YndIO4g
MD5: 5BFE6BE67AA86DF8C0ED041342DFD9FF
Thanks:laugh:

[Q] New User. I Need Help.

I need help. I got a Samsung Galaxy S4 (SGH - I337) Rooted from AT&T. I got two problems.
First I cannot update my version from JellyBean 4.2 to 4.3. Every time I had downloaded the update when the device restarts and it reaches 21% on the update it said's "Update Fail". What can I do?!
NOTE - (Someone told me that because I rooted the phone I cannot update my phone through AT&T servers)
Secondly my device from time to time restarts it self.
And sometimes the wifi stars connecting and disconnecting every few seconds.
Can anyone help me?
Thanks

Having root can stop the install.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

Do a factory reset and see if that helps, do a backup before you start.....good luck.,...

Ok. So theres no manual update? No way I can update my phone to Jellybean 4.3?

tonydamiani said:
I need help. I got a Samsung Galaxy S4 (SGH - I337) Rooted from AT&T. I got two problems.
First I cannot update my version from JellyBean 4.2 to 4.3. Every time I had downloaded the update when the device restarts and it reaches 21% on the update it said's "Update Fail". What can I do?!
NOTE - (Someone told me that because I rooted the phone I cannot update my phone through AT&T servers)
Secondly my device from time to time restarts it self.
And sometimes the wifi stars connecting and disconnecting every few seconds.
Can anyone help me?
Thanks
Click to expand...
Click to collapse
Follow my thread. .... http://forum.xda-developers.com/showthread.php?t=2573080 PLEASE READ SO U GET THE PICTURE ON HOW TO DO IT. .......... ...... If I were u : flash to stock using MF3.tar files from Original Post (OP) or first post Via ODIN....... Download MF3>MK2 update.zip ...... and then go to second post on guide how to update. ......hope this will get u start it. ....PM me if you have anymore question or need more help. ..... GOODLUCK. ...:thumbup:
Swyped from MK2 Deadly Venom SS

tonydamiani said:
I need help. I got a Samsung Galaxy S4 (SGH - I337) Rooted from AT&T. I got two problems.
First I cannot update my version from JellyBean 4.2 to 4.3. Every time I had downloaded the update when the device restarts and it reaches 21% on the update it said's "Update Fail". What can I do?!
NOTE - (Someone told me that because I rooted the phone I cannot update my phone through AT&T servers)
Secondly my device from time to time restarts it self.
And sometimes the wifi stars connecting and disconnecting every few seconds.
Can anyone help me?
Thanks
Click to expand...
Click to collapse
The ATT updates can fail due to the device being rooted as stated by others here. Just as it has been recommended do a back up and a factory reset to see if it helps with your rebooting issues and wifi. Check your baseband under settings/about and if it ends with MDL i would recommend that you DO NOT update. The reason for this is that since you are rooted you can install ANY custom ROM on your phone, you can even install the latest google edition ROM 4.4.2. If you do the ATT updates and your baseband changes to MF3 or MK2 then you will be stuck with just limited ROMS and you will also be stuck with all the ATT/TW bloatware. Trust me 4.4.2 is soooo much better your phone will run alot faster and you will have the latest google version on your phone. I was on MDL and all the ATT updates failed on me and i just decided to install the google edition ROM and man oh man I LOVE IT!

audiowikid said:
The ATT updates can fail due to the device being rooted as stated by others here. Just as it has been recommended do a back up and a factory reset to see if it helps with your rebooting issues and wifi. Check your baseband under settings/about and if it ends with MDL i would recommend that you DO NOT update. The reason for this is that since you are rooted you can install ANY custom ROM on your phone, you can even install the latest google edition ROM 4.4.2. If you do the ATT updates and your baseband changes to MF3 or MK2 then you will be stuck with just limited ROMS and you will also be stuck with all the ATT/TW bloatware. Trust me 4.4.2 is soooo much better your phone will run alot faster and you will have the latest google version on your phone. I was on MDL and all the ATT updates failed on me and i just decided to install the google edition ROM and man oh man I LOVE IT!
Click to expand...
Click to collapse
Nice where can I get a Google Play Edition ROM?
Question: Having the google play edition on my phone can I keep updating it until I have kikkat?
Thanks

What's your baseband first???

rugmankc said:
what's your baseband first???
Click to expand...
Click to collapse
baseband: I337ucuamf3

You may not be able to flash 4.3 roms and above with no issues. Your bootloader is locked down and no custom kernel flashing either. Also, only TW roms. That said there is newer beta Safestrap 3.7.1? that is letting 4.3 TW roms flash. I think!
I am on an original phone and not up on Safestrap. Read all you can here about it. Threads will be in General and Q&A.

tonydamiani said:
baseband: I337ucuamf3
Click to expand...
Click to collapse
On MF3, your only option for a recovery is Safestrap 3.65 and you can only flash other 4.2.2 ROMS. Trying to use the updater in the GPE 4.2.2 ROM will possibly brick your phone. If you update to MK2 then you can have 4.3 ROMS but the 4.3 GPE ROM uses a different kernel and so you won't be able to use it.

DeadlySin9 said:
On MF3, your only option for a recovery is Safestrap 3.65 and you can only flash other 4.2.2 ROMS. Trying to use the updater in the GPE 4.2.2 ROM will possibly brick your phone. If you update to MK2 then you can have 4.3 ROMS but the 4.3 GPE ROM uses a different kernel and so you won't be able to use it.
Click to expand...
Click to collapse
Just FYI for me in future on helping out--is it SS 3.7.? for MK2--

rugmankc said:
Just FYI for me in future on helping out--is it SS 3.7.? for MK2--
Click to expand...
Click to collapse
Yes, but if anyone is asking for the record it's still in beta, only on Hashcode's goo.im, and if they're still on MF3 they should stay if they want GPE and check which ROMs are compatible in the Safestrap thread before going to MK2.

DeadlySin9 said:
Yes, but if anyone is asking for the record it's still in beta, only on Hashcode's goo.im, and if they're still on MF3 they should stay if they want GPE and check which ROMs are compatible in the Safestrap thread before going to MK2.
Click to expand...
Click to collapse
Appreciate the info--I did know about the beta. Too much to keep up on with this phone--

Suspected Mismatched Kernel and ROM Causing issues

I have a GT-i9505 that I've been running the stock Jellybean Touchwiz 4.2.2 ROM on since forever (I9505XXUAMDD). I recently discovered compatibility issues with some updated apps and decided to give the latest Touchwiz a spin. Since my phone is rooted i couldn't get the update via OTA so I downloaded the latest Touchwiz ROM (I9505XXUHOL2) and flashed it manually. It went well but I didn't really like it and I didn't have the time to set everything up again so I restored my original setup using a nandroid backup but now things are all wonky. I can't mount my SD card and wifi won't turn on. I suspect this is because the kernel is still the one from the 5.0.1 flash while the ROM is back to the 4.2.2 one. Under the about device menu the android version shows 4.2.2 and the build number is the original I9505XXUAMDD but the baseband version shows I9505XXUHOL2 and the kernel version shows 3.4.0-431985. In addition when booting up the phone it shows the "SEAndroid...kernel" message in the top left corner; not sure what this is.
Is there a way to remedy this or am I SOL and forced to use a later version of Android? Thanks in advance!
Edit: So further research suggests it's actually the Baseband version that is causing the problem so flashing the correct modem should fix it. Could someone please show me which modem is correct for I9505XXUAMDD? Also, will this fix the kernel message I keep getting? Thanks!

You can't downgrade from lollipop that easily
There's threads in general relating to downgrading

Could be a mismatch between the phone bootloader and baseband. What bootloader version and baseband is on the phone? If they match, it could just be that the bootloader and modem are too new for the rom.

DSA said:
You can't downgrade from lollipop that easily
There's threads in general relating to downgrading
Click to expand...
Click to collapse
Yeah, I realize that now. I put too much faith in the nandroid restore. I had tried out the JFLTE-GPE ROM once before and a nandroid restore reverted the device without issue so I just assumed it would do the same in this situation. I will look into the downgrade process.
audit13 said:
Could be a mismatch between the phone bootloader and baseband. What bootloader version and baseband is on the phone? If they match, it could just be that the bootloader and modem are too new for the rom.
Click to expand...
Click to collapse
I was under the impression that a nandroid restore would flash the bootloader as well but my faith in nandroid backups isn't what it used to be
Guess I'll have to look for the appropriate bootloader and modem for the ROM.

You can install the Samsung Phone Info app from the Play store to confirm your bootloader and modem.

audit13 said:
You can install the Samsung Phone Info app from the Play store to confirm your bootloader and modem.
Click to expand...
Click to collapse
Wifi is out so I don't have access to the play store
I used the terminal emulator to check the bootloader version and it's indeed still on I9505XXUHOL2. I've read somewhere that once a newer version of the knox bootloader has been installed, attempting to flash back to the 4.2.2 bootloader will brick the phone. Is this true?
Thanks again!

I don't know about the 9505 but you can't downgrade on the s3, i337, and note 2.
Personally, I would flash back to stock to make sure everything still works.

audit13 said:
I don't know about the 9505 but you can't downgrade on the s3, i337, and note 2.
Personally, I would flash back to stock to make sure everything still works.
Click to expand...
Click to collapse
Will do. I'll pull up the I9505XXUAMDD from sammobile and give that flash when I get home this evening. Thanks again!

So I flashed to stock I9505XXUAMDD but the wifi and sd card issue remains and the bootloader still shows up as I9505XXUHOL2. Not sure how to proceed.
I'm starting to get the feeling that 4.2.2 is a lost cause...I guess downgrade on GT-i9505 is not possible.
Edit: Baseband version is now I9505XXUAMDD and wifi is still not working.
Update: Flashed to I9505XXUHOF2 and everything seems to be all peachy keen for now. Will update again once I restore all my apps and data.

aznpos531 said:
So I flashed to stock I9505XXUAMDD but the wifi and sd card issue remains and the bootloader still shows up as I9505XXUHOL2. Not sure how to proceed.
I'm starting to get the feeling that 4.2.2 is a lost cause...I guess downgrade on GT-i9505 is not possible.
Edit: Baseband version is now I9505XXUAMDD and wifi is still not working.
Update: Flashed to I9505XXUHOF2 and everything seems to be all peachy keen for now. Will update again once I restore all my apps and data.
Click to expand...
Click to collapse
No it's not. It's not possible because you cannot downgrade the bootloader.
Perhaps you can still go back with 4.2.2. custom rom but in my opinion it's really not worth it. It's not worth to stay on an outdated version with all the security vulnerabilities. I would recommend anyone to use CM because then you can run the latest software on your phone.

Lennyz1988 said:
No it's not. It's not possible because you cannot downgrade the bootloader.
Perhaps you can still go back with 4.2.2. custom rom but in my opinion it's really not worth it. It's not worth to stay on an outdated version with all the security vulnerabilities. I would recommend anyone to use CM because then you can run the latest software on your phone.
Click to expand...
Click to collapse
Thanks for confirming and thanks for your input :good:
I really did enjoy the Jellybean experience on the S4; going to Jellybean from ICS felt like an upgrade. I feel like that was the best match for the phone and it just went downhill from there (as far as the S4 is concerned). I suppose it's time to move on.
Update: All apps and data fully restored and it seems stable save for some small quirks. Not liking Lollipop though.