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.
Related
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.
Received an ota update on 11/30/13. Installed and can no longer enable wifi. There are a few threads with similar problems but, the fixes in them don't seem to be working for me. I tried to Odin back to a pre update version. Unfortunately Odin wouldn't work. However, was able to use Odin to install TWRP. I've been reading on xda for the past 4 days. I've tried several methods mentioned in some of the posts to revert. None seem to work. Would someone please help with some step by step instructions on how to get my phone back to stock. I want to remove TWRP and re-install the stock recovery and have the latest sprint s4 stock rom.
My phones device info is showing the following:
Software Version - L720VPUEMJA
Hardware version - L720.08
Model # - SPH-L720
Baseband Version L720VPUEMJA
Kernel Version - 3.4.0-1927016
Build Number - JSS15J.L720VPUEMK2
Same issue here
Scott02 said:
Received an ota update on 11/30/13. Installed and can no longer enable wifi. There are a few threads with similar problems but, the fixes in them don't seem to be working for me. I tried to Odin back to a pre update version. Unfortunately Odin wouldn't work. However, was able to use Odin to install TWRP. I've been reading on xda for the past 4 days. I've tried several methods mentioned in some of the posts to revert. None seem to work. Would someone please help with some step by step instructions on how to get my phone back to stock. I want to remove TWRP and re-install the stock recovery and have the latest sprint s4 stock rom.
My phones device info is showing the following:
Software Version - L720VPUEMJA
Hardware version - L720.08
Model # - SPH-L720
Baseband Version L720VPUEMJA
Kernel Version - 3.4.0-1927016
Build Number - JSS15J.L720VPUEMK2
Click to expand...
Click to collapse
I too am having the same issue with Wi-Fi. I am on stock rooted rom and stock recovery. I got the OTA MK2 today and updated but Wi-Fi won't turn on since the update.
Scott02 said:
Received an ota update on 11/30/13. Installed and can no longer enable wifi. There are a few threads with similar problems but, the fixes in them don't seem to be working for me. I tried to Odin back to a pre update version. Unfortunately Odin wouldn't work. However, was able to use Odin to install TWRP. I've been reading on xda for the past 4 days. I've tried several methods mentioned in some of the posts to revert. None seem to work. Would someone please help with some step by step instructions on how to get my phone back to stock. I want to remove TWRP and re-install the stock recovery and have the latest sprint s4 stock rom.
My phones device info is showing the following:
Software Version - L720VPUEMJA
Hardware version - L720.08
Model # - SPH-L720
Baseband Version L720VPUEMJA
Kernel Version - 3.4.0-1927016
Build Number - JSS15J.L720VPUEMK2
Click to expand...
Click to collapse
How did you take the OTA. It looks like you flashed the MK2 ROM that's is in Dev section. Of you had taken the real OTA it would have updated your baseband (modem) as well.
I've heard you can use MJA tar while on MK2.
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
How did you take the OTA. It looks like you flashed the MK2 ROM that's is in Dev section. Of you had taken the real OTA it would have updated your baseband (modem) as well.
I've heard you can use MJA tar while on MK2.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Not sure about the original poster but I updated from the Sprint notification I got. Maybe I should have flashed the update from the dev section. Should I try flashing the MJA firmware again?
daniel4653 said:
How did you take the OTA. It looks like you flashed the MK2 ROM that's is in Dev section. Of you had taken the real OTA it would have updated your baseband (modem) as well.
I've heard you can use MJA tar while on MK2.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I originally took the OTA update over the air. I did try flashing the version on one of the XDA threads afterwards.
Scott02 said:
I originally took the OTA update over the air. I did try flashing the version on one of the XDA threads afterwards.
Click to expand...
Click to collapse
Just found that after the update I lost root. Maybe that's part of the issue as well.
eenglish34 said:
Just found that after the update I lost root. Maybe that's part of the issue as well.
Click to expand...
Click to collapse
I doubt it. I lost root too. I re-enabled it via Odin and the problem is still there. I'm just trying to find a way to get back to stock now so I can take it in to the sprint store.
Scott02 said:
I doubt it. I lost root too. I re-enabled it via Odin and the problem is still there. I'm just trying to find a way to get back to stock now so I can take it in to the sprint store.
Click to expand...
Click to collapse
I was able to fix mine by downloading the stock MJA rom and flashing it through Odin. Then take the OTA update and re-root (if you want root again).
eenglish34 said:
I was able to fix mine by downloading the stock MJA rom and flashing it through Odin. Then take the OTA update and re-root (if you want root again).
Click to expand...
Click to collapse
I did the same. I initially installed the update manually via stock recovery and lost wifi. ODIN back to stock MJA fixed wifi, and then repeated the manual update. Wifi works fine now. I did not do any data wipes going back and forth, and have no adverse effects so far.
Just got my I337, using with simple mobile. Managed to sim unlock via this method, and was feeling pretty good. I think I had (have?) MK2. So using the stock ROM, it kept on asking to autoupdate. Didn't know if that would screw anything up, so attempted to install a kitkat venom ROM. I now can't get out of safestrap recovery. I'm not sure if the issue was trying to install a kitkat ROM, or if I mistakenly put it in the primary ROM slot. Anyway, I'm on a linux box without any immediate access to windows, so it looks like ODIN is out of the question. Been scouring the forums, but I have a few questions:
1. What are the limitations of the locked bootloader? Not really sure what I'm sidestepping by using a custom recovery. I had read that it limited me to TW ROMS (which is fine by me actually), but I see AOSP and other ROMs posted...
2. What exactly is meant by MK2, NC1, MF3, etc? I understand that they are progressions of SOMETHING, but not sure what--guessing it's the whole AT&T update, including ROM, modem, kernel? And I can't seem to find what exactly the progression is...
3. Is there a ROM that I should try to flash to get me back up and running before I start trying to screw with something else? Like I said, I have access to safestrap 2.71, adb, and an SD card, so I feel like this shouldn't be TOO hard to fix
nola mike said:
Just got my I337, using with simple mobile. Managed to sim unlock via this method, and was feeling pretty good. I think I had (have?) MK2. So using the stock ROM, it kept on asking to autoupdate. Didn't know if that would screw anything up, so attempted to install a kitkat venom ROM. I now can't get out of safestrap recovery. I'm not sure if the issue was trying to install a kitkat ROM, or if I mistakenly put it in the primary ROM slot. Anyway, I'm on a linux box without any immediate access to windows, so it looks like ODIN is out of the question. Been scouring the forums, but I have a few questions:
1. What are the limitations of the locked bootloader? Not really sure what I'm sidestepping by using a custom recovery. I had read that it limited me to TW ROMS (which is fine by me actually), but I see AOSP and other ROMs posted...
2. What exactly is meant by MK2, NC1, MF3, etc? I understand that they are progressions of SOMETHING, but not sure what--guessing it's the whole AT&T update, including ROM, modem, kernel? And I can't seem to find what exactly the progression is...
3. Is there a ROM that I should try to flash to get me back up and running before I start trying to screw with something else? Like I said, I have access to safestrap 2.71, adb, and an SD card, so I feel like this shouldn't be TOO hard to fix
Click to expand...
Click to collapse
Well, fixed my problem, though still don't have all the answers to my questions. I couldn't find a way to unbork without odin. Luckily my mom was in town visiting, and had a windows box that I used--I think I would have been hosed otherwise. Anyway, managed to revert to MK2 stock, and then upgrade to Goldeneye kit kat ROM via this method (my baseband is now listed as xxxxxxMLD).
I guess that MLD/NC1/NB1/MK2 are just ROM/radio firmware versions (kernel too, or is that completely unchangeable)? Still don't know the exact order of release, and if anyone could enlighten me a bit as to my other questions, I'd appreciate it...
I'll probably hold off on trying to change anything else until I have reliable access to windoze, unless someone can give me the steps using linux/adb.
nola mike said:
Well, fixed my problem, though still don't have all the answers to my questions. I couldn't find a way to unbork without odin. Luckily my mom was in town visiting, and had a windows box that I used--I think I would have been hosed otherwise. Anyway, managed to revert to MK2 stock, and then upgrade to Goldeneye kit kat ROM via this method (my baseband is now listed as xxxxxxMLD).
I guess that MLD/NC1/NB1/MK2 are just ROM/radio firmware versions (kernel too, or is that completely unchangeable)? Still don't know the exact order of release, and if anyone could enlighten me a bit as to my other questions, I'd appreciate it...
I'll probably hold off on trying to change anything else until I have reliable access to windoze, unless someone can give me the steps using linux/adb.
Click to expand...
Click to collapse
The order of firmware versions with Android version - MDB(4.2.x) -> MDL(4.2.x) - > MK2(4.3)->MLD(4.4 leak)->NB1(4.4.x)->NC1(4.4.x)
The bootloader for SGH-I337 was always locked.
1. This means that the stock kernel and recovery cannot be replaced.
2, The bootloader cannot be downgraded.
But, there was a bug in the first 2 releases, that loki exploited and provided a workaround for #1.
When flashing a firmware that contains the bootloader (aboot.mbn), it does a version check. The version check is through a fuse count maintained in the bootloader. MLD and MK2 although are different Android versions, have the same bootloader version. That means you can flash one over the other (go back and forth). The same with NB1 and NC1. But, once you update to NB1, you cannot go back to MK2.
Since the kernel cannot be replaced, all the ROMs we flash have to be compatible with the kernel that we have on the phone. Hence the mention of TW only ROMS. We cannot flash CM/AOSP/AOKP/GPE (most) ROMS. The AOSP ROMS you are seeing are themed TW roms only.
jmjoyas said:
The order of firmware versions with Android version - MDB(4.2.x) -> MDL(4.2.x) - > MK2(4.3)->MLD(4.4 leak)->NB1(4.4.x)->NC1(4.4.x)
The bootloader for SGH-I337 was always locked.
1. This means that the stock kernel and recovery cannot be replaced.
2, The bootloader cannot be downgraded.
But, there was a bug in the first 2 releases, that loki exploited and provided a workaround for #1.
When flashing a firmware that contains the bootloader (aboot.mbn), it does a version check. The version check is through a fuse count maintained in the bootloader. MLD and MK2 although are different Android versions, have the same bootloader version. That means you can flash one over the other (go back and forth). The same with NB1 and NC1. But, once you update to NB1, you cannot go back to MK2.
Since the kernel cannot be replaced, all the ROMs we flash have to be compatible with the kernel that we have on the phone. Hence the mention of TW only ROMS. We cannot flash CM/AOSP/AOKP/GPE (most) ROMS. The AOSP ROMS you are seeing are themed TW roms only.
Click to expand...
Click to collapse
Thanks for that, very enlightening.
nola mike said:
Thanks for that, very enlightening.
Click to expand...
Click to collapse
Just as an update, seems there's a workaround for Odin called heimdall, which is cross platform. . Haven't tried it, but looks like it should work.
A while back I attempted to fix my issues with wireless signal strength by rooting and running roms. Eventually I learned more and figured out how to change just the baseband and attempted to put everything back where it was.
In doing this I still have the "custom" thing when the phone starts though its showing unrooted at this point and on factory software. I attempted to update to 4.4.4 and it failed. I would imagine this is due to the changes I have made before.
Is there a way for me to revert the phone in its entirety back to factory so I can use the new software?
Thanks,
Casey
1. Reflash STOCK ROM android 4.4.2 with the correct CSC.
2. Reflash android 4.4.4 and tell me how it works
Joku1981 said:
1. Reflash STOCK ROM android 4.4.2 with the correct CSC.
2. Reflash android 4.4.4 and tell me how it works
Click to expand...
Click to collapse
Sorry I am fairly ignorant on some of this.
Where would I obtain stock rom and what do I use to reflash?
Runzlikegirl said:
Sorry I am fairly ignorant on some of this.
Where would I obtain stock rom and what do I use to reflash?
Click to expand...
Click to collapse
Shameless Bump
So I had DarkLord N5 on my N9005 before, which was awesome, but it had performance issues (especially when gaming). Then i downgraded to Stock KitKat using Odin and after boot up It showed No Signal, and everything was freezing and force closing. I somehow went to settings and found that i also have issues with IMEI and Baseband version, it was all unknown. The worst part is i did not backup my EFS. Any help guys please :crying:
I also have no audio playback
Im no pro here, but as i found in my research it is hard to downgrade from lolipop to kitkat as in 5.0 new architecture has been presented which they called art. I think. So it gives lots of incompatibilities. I tried the same as you but i ended up going stock lolipop for a while.
Yesterday i flashed Ressurrection remix 6.0.1 Marshmallow based off Slim roms and CM and i admit this is so far best rom i have tested. (Unless you need all fancy spen features)
I'd try to stick to anything that is 5.1 or above since great battery life.
Sorry for not much info, but i couldn't get past your post unanswered.
oxoconstantineoxo said:
Im no pro here, but as i found in my research it is hard to downgrade from lolipop to kitkat as in 5.0 new architecture has been presented which they called art. I think. So it gives lots of incompatibilities. I tried the same as you but i ended up going stock lolipop for a while.
Yesterday i flashed Ressurrection remix 6.0.1 Marshmallow based off Slim roms and CM and i admit this is so far best rom i have tested. (Unless you need all fancy spen features)
I'd try to stick to anything that is 5.1 or above since great battery life.
Sorry for not much info, but i couldn't get past your post unanswered.
Click to expand...
Click to collapse
I had many experiences with downgrading from new version to old version with my S3 and my Note, but never had this issue. Something is causing this...
founded a old backup of CM11.. Flashed CWM and restored to CM. Works flawlessly, but still no sound and those stuff
Honix5962 said:
I had many experiences with downgrading from new version to old version with my S3 and my Note, but never had this issue. Something is causing this...
Click to expand...
Click to collapse
So i had problems with my either s2 or note 4.
But afaik if u have updated your bootloader there may be no way to get back. And lack of IMEI on reverted KitKat isn't anything new. I bet going simply to anything art. Based will do.
People here are arguing on same issues as yours. Just don't listen to these "flash with odin" guys.. This doesn't work. Even if u flash the stock one.
http://forum.xda-developers.com/gal...o-downgrade-lollipop-to-kitkat-t2990262/page2
Hope you will dig up something.
You could try this. It worked for me.
http://forum.xda-developers.com/showthread.php?t=2507403
Have you tried flashing to the latest stock rom for the phone using Odin?
audit13 said:
Have you tried flashing to the latest stock rom for the phone using Odin?
Click to expand...
Click to collapse
Nope, I downloaded the KitKat firmware from Sammobile, and I'm downloading the Lollipop one now.
deejhay14 said:
You could try this. It worked for me.
http://forum.xda-developers.com/showthread.php?t=2507403
Click to expand...
Click to collapse
I tried it, but still no use :c
I would not try any other ROMs before trying to flash the latest stock rom from sammobile.com. Hopefully, this will resolve the baseband and imei issue. Sometimes, the missing or wrong imei is caused by a mismatch between the bootloader and modem firmware.
audit13 said:
I would not try any other ROMs before trying to flash the latest stock rom from sammobile.com. Hopefully, this will resolve the baseband and imei issue. Sometimes, the missing or wrong imei is caused by a mismatch between the bootloader and modem firmware.
Click to expand...
Click to collapse
I hope so.
I have seen this sort of problem on the Samsung s3 and note 3 phones.
audit13 said:
I have seen this sort of problem on the Samsung s3 and note 3 phones.
Click to expand...
Click to collapse
I did downgrading from 5.0 (CM12) to Stock 4.4 KitKat in my S3, but never had issues like this.
Downgrading from a cm rom to a stock rom via Odin can be fine because installing a cm rom does NOT alter the phone's bootloader or modem. Trying to downgrade from stock 4.4.2 to stock 4.3 with Odin on an s3 cannot be done.
audit13 said:
Downgrading from a cm rom to a stock rom via Odin can be fine because installing a cm rom does alter the phone's bootloader or modem. Trying to downgrade from stock 4.4.2 to stock 4.3 with Odin on an s3 cannot be done.
Click to expand...
Click to collapse
Oh, never knew about this, thanks for the info
Sorry, I meant to say that installing a cm rom DOES NOT change the bootloader or modem. When you flash back to stock via Odin, you are simply writing over the existing modem and bootloader with the same bootloader and modem if you are flashing the same stock rom that was on the phone before installing cm.
I flashed between KitKat and LP official just fine.
audit13 said:
Have you tried flashing to the latest stock rom for the phone using Odin?
Click to expand...
Click to collapse
Never mind, It works. Thanks for the help.
Which method worked? Thanks.
Use gsii repair