Hello,
This is will be my first XDA post ever since I always fix the most "brickiest" problems with all the Android based devices I have ever owned but not this time.
My Galaxy S4 has been updated to the latest MJA OTA (with successful CF root) and I have attempted to re-mod the hotspot service but this caused the annoying knox message to show. When attempting to restore the JAR and ODEX files, I think I have either overwritten the files in the incorrect order (ODEX -> JAR) and the phone rebooted as FX was trying to do that. So services.odex got corrupted and it was time for my to ODIN flash the MDC full stock rom as that USED to be my solution until Samsung's brand new knox protected bootloader. ODIN is not an option for me now, since the bootloader will prevent me flashing things like the pit, aboot and probably most of the other files inside the tarball. I can flash custom recovery and the MDC kernel successfully and that's about it. With custom recovery I have flashed rooted MF8 for the base operating system, and they applied the rooted MJA rom on top. The phone shows the S4 branding but then it reboots; It cannot boot into the operating system. I do not know the condition of the flash counter atm since I cannot check that in TriangleAway but it will stay "Official" under download mode, I think. I also do not know the versions of the firmware installed either in case something from MDC tar had an succession in replace some of the partitions. I am pretty sure the kernel however is still at MDC while I managed to install the system image of the MJA stock rom.
So my question is, what can I do bring back the working MJA stock rom image (/system and kernel) using TWRP recovery? Else I will have to go to Sprint and saying that the update from OTA has bricked my phone and that I have no idea how phones work.
Thank you.
45553543 450
Sorry, I forgot to add that I know that once you have MJA flashed, you cannot downgrade back unless of course someone figured out how to disable all the bootloader security but I really do not see that happening.
Fixed my own problem. Downloaded the official MJA stock tar.md5 rom from sammobile and flashed it, and managed to restore all my data using Titanium backup. This thread can be now closed.
Related
Help needed!
Tried to root my Sprint SPH-L720 MDL version (really need to be able to use it as HotSpot like I was using my previous phone) and having issues with getting root access as Sprint has added a SetUID restriction on the kernel with the latest update.
But most important, Good Enterprise stopped working as it detected that phone is rooted or partially rooted (as Titanium Backup gives me a message that it was able to acquire Root Privs – but its UI never opens up). Not having Good Enterprise is not an option for me.
So, decided to go back to Original as seen posts with instructions (these were key for me to move forward with rooting) that it is easy to do, however only know realized that all these ports are using MDC version of Firmware and I could not find Official Firmware for MDL version. Only MDC version available. Ouch!
Question #1: Anyone knows if MDL version of Original Firmware even exists and if yes where to download it? Or should I just use MDC version? Would it work?
If recovery is not available, I could pass this phone to one of my kids but I will need to fix root. To fix root I need to flash new MDL kernel using ODIN & CWM recovery. I have Fixed MDL Kernel, but I could not find instructions on how to flash it.
Question #2: Anyone could point me to the instructions on how to flash Kernel using ODIN and CWM Recovery?
Thank you In advance!
only way right now is to flash mdc and then take the ota.
for some reason Samsung has not released the mdl yet.
kernels you flash in recovery like a rom just read the install instruction in any kernel thread.
there is also an unroot script posted in dev you might try.
for rooting did you odin cf auto root? pretty hard not to root that way.
Hi,
I have OUDHS-Recovery-jfltespr-1.0.3.3 and CF-Auto-Root-jfltespr-jfltespr-sphl720 flashed on my SPH-L720, on what was stock 4.2.2
My question is, do I HAVE to nuke & pave (factory reset) to get this to 4.3 and then re-root it?
If so, why? I thought one of the big advantages to rooting an Android was the ease with which you could un-root and return to stock.. I remember having to do factory resets to update iPhones before re-jailbreaking them, what a joy! I was hoping to avoid that here, especially as I'm behind a restrictive data cap for internet (~10GB/mo, which is about 300MB/day, combined up & down).
So... any ideas?
0x6A7232 said:
Hi,
I have OUDHS-Recovery-jfltespr-1.0.3.3 and CF-Auto-Root-jfltespr-jfltespr-sphl720 flashed on my SPH-L720, on what was stock 4.2.2
My question is, do I HAVE to nuke & pave (factory reset) to get this to 4.3 and then re-root it?
If so, why? I thought one of the big advantages to rooting an Android was the ease with which you could un-root and return to stock.. I remember having to do factory resets to update iPhones before re-jailbreaking them, what a joy! I was hoping to avoid that here, especially as I'm behind a restrictive data cap for internet (~10GB/mo, which is about 300MB/day, combined up & down).
So... any ideas?
Click to expand...
Click to collapse
You have to be on a totally stock firmware to apply these firmware updates.So you can be rooted and update, as long as you have no mods applied, like the hotspot mod, etc.
Seems the easiest path if you do have any mods applied (which would be most rooted users, I'm sure) is do a full nandroid backup and TiBu or Helium backup. Also backup anything else from internal memory that might be lost, like Nova settings, etc. Then load the MF9 stock tar via Odin. To do that, follow the directions in the following thread in the section labled "Reverting to Unmodified Stock MDL to update to Stock MF9". Just use the MF9 tar instead of the MDL one:
http://forum.xda-developers.com/showthread.php?t=2277480
Use triangle away to clear your "custom" settings on the Download screen. May even have to do a 2nd factory reset to get there.
Then root using CF Auto Root and let TiBu restore all your apps. Then use the stock recovery to load the 4.3 update. If all goes well, that should give you 4.3 on a rooted phone w/o tripping the knox bit.
oops
Ironically, I had just rooted the day before 4.3 came out. The only 'mod' I have is the CWM custom recovery.. I'm guessing that's what's tripping it up?
When I try to apply the update .zip in CWM, it says,
Code:
-- Installing: /sdcard/0/Download/update_SPH-L720_MDL_CSB_user_RP_to_MF9_CSB_user_RP.zip
Finding update package...
Opening update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check(" /system/app/AllSharePlay15.apk", "dae9b84dd3cb4810371f2a6136a0536cac926af5", "37b87ff87a955c98258cef2145b4b7b913eb0752")
E:Error in /sdcard/0/Download/update_SPH-L720_MDL_CSB_user_RP_to_MF9_CSB_user_RP.zip
(Status 7)
Installation aborted.
Aaaaand, I found the problem. MF9 is 4.2.2, yes? I've already got that, I need to be trying to flash MJA/4.3 :silly: For some reason I thought MF9 was 4.3, until I realized I had it already and I'm on 4.2.2. Sorry for the confusion. Now to find the 4.3/MJA download... :cyclops:
You have to be on a totally stock firmware to apply these firmware updates.So you can be rooted and update, as long as you have no mods applied, like the hotspot mod, etc.
Seems the easiest path if you do have any mods applied (which would be most rooted users, I'm sure) is do a full nandroid backup and TiBu ='Titanium Backup', I'm assuming?or Helium backup. Also backup anything else from internal memory that might be lost, like Nova settings, etc. Then load the MF9 stock tar via Odin. To do that, follow the directions in the following thread in the section labled "Reverting to Unmodified Stock MDL to update to Stock MF9". Just use the MF9 tar instead of the MDL one:
http://forum.xda-developers.com/show....php?t=2277480
Use triangle away to clear your "custom" settings on the Download screen. May even have to do a 2nd factory reset to get there.
Then root using CF Auto Root and let TiBu restore all your apps. Then use the stock recovery to load the 4.3 update. If all goes well, that should give you 4.3 on a rooted phone w/o tripping the knox bit.
Click to expand...
Click to collapse
You will need to install the stock recovery, the MJA update will not install with a custom recovery.
Sent from my GT-N5110 using Tapatalk 4
cruise350 said:
You will need to install the stock recovery, the MJA update will not install with a custom recovery.
Click to expand...
Click to collapse
Correct. And you can get the MF9 one here:
http://forum.xda-developers.com/showthread.php?t=2357471
Camera MJA firmware manual update - possible?
jejb said:
You have to be on a totally stock firmware to apply these firmware updates.So you can be rooted and update, as long as you have no mods applied, like the hotspot mod, etc.
Seems the easiest path if you do have any mods applied (which would be most rooted users, I'm sure) is do a full nandroid backup and TiBu or Helium backup. Also backup anything else from internal memory that might be lost, like Nova settings, etc. Then load the MF9 stock tar via Odin. To do that, follow the directions in the following thread in the section labled "Reverting to Unmodified Stock MDL to update to Stock MF9". Just use the MF9 tar instead of the MDL one:
http://forum.xda-developers.com/showthread.php?t=2277480
Use triangle away to clear your "custom" settings on the Download screen. May even have to do a 2nd factory reset to get there.
Then root using CF Auto Root and let TiBu restore all your apps. Then use the stock recovery to load the 4.3 update. If all goes well, that should give you 4.3 on a rooted phone w/o tripping the knox bit.
Click to expand...
Click to collapse
cruise350 said:
You will need to install the stock recovery, the MJA update will not install with a custom recovery.
Sent from my GT-N5110 using Tapatalk 4
Click to expand...
Click to collapse
jejb said:
Correct. And you can get the MF9 one here:
http://forum.xda-developers.com/showthread.php?t=2357471
Click to expand...
Click to collapse
Thanks guys. I ended up installing SAC's 4.1 (based on Android 4.3), after manually flashing the MJA modem firmware.
(Because even after flashing stock recovery, I was getting error 7 or something like that, no clue why, I tried searching a few days, but no dice. The recommendation was to flash non-destructive MF9 stock update over first and then update, so I just downloaded Sac's while I had 4G on the way back from work).
NEW QUESTION: How do I get the updated camera firmware, as Sac's modded stock camera seems not to have it. (although, maybe Sac's camera is in error and the firmware is already updated it just doesn't realize).
I can get a patched camera to not do the popup, but I want the firmware. Any way to extract it from the stock MJA OTA file and flash just that?
0x6A7232 said:
Thanks guys. I ended up installing SAC's 4.1 (based on Android 4.3), after manually flashing the MJA modem firmware.
(Because even after flashing stock recovery, I was getting error 7 or something like that, no clue why, I tried searching a few days, but no dice. The recommendation was to flash non-destructive MF9 stock update over first and then update, so I just downloaded Sac's while I had 4G on the way back from work).
NEW QUESTION: How do I get the updated camera firmware, as Sac's modded stock camera seems not to have it. (although, maybe Sac's camera is in error and the firmware is already updated it just doesn't realize).
I can get a patched camera to not do the popup, but I want the firmware. Any way to extract it from the stock MJA OTA file and flash just that?
Click to expand...
Click to collapse
Error 7 is normally when your recovery pics up that you are rooted. Or when there is a problem with the updater script in the zip file.
If sacs used the MJA camera as a base for his nodded camera then he should have the latest camera firmware.
If you worry this much about Tue camera you can download a stock rooted MJA ROM and go into system/apps with a root explorer and extract the camera apk. Then go to where the camera apk is extracted to and move it to your internal memory under system apps. Then set permissions and reboot.
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
Error 7 is normally when your recovery pics up that you are rooted. Or when there is a problem with the updater script in the zip file.
If sacs used the MJA camera as a base for his nodded camera then he should have the latest camera firmware.
If you worry this much about Tue camera you can download a stock rooted MJA ROM and go into system/apps with a root explorer and extract the camera apk. Then go to where the camera apk is extracted to and move it to your internal memory under system apps. Then set permissions and reboot.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
The camera supposedly had some improvements, that's why I'm trying to find out. I'd ask in Sac's thread, but I don't have enough posts yet. And, I used SuperSU's uninstall to unroot the phone before trying the MJA OTA... although I did put stock recovery first, IIRC. Perhaps the root uninstall needed custom recovery to work? Anyways.
Under cce8d8a155a0602c83356e00311a1695e9a9383f.USER_L720_SPT_MF9_CSB_user_RP_to_MJA_CSB_user_RP_Update_FWD.zip\patch\system\cameradata\ there are a few items:
secimaging\PIP\rear_polaroid.png.p
RS_M10MO_OS.bin.p
RS_M10MO_SL.bin.p
RS_M10MO_SS.bin.p
I'll have to find someone who is knowledgeable about this and pick their brain if they'll let me.
i was having reception problems, thought maybe if i flashed the modem file and NON-HLOS file it would fix it. but now i got no sound, also made a backup, restored backup no change. So what i did was flash to stock 4.3 touchwiz got sound. then i realized i could not root this. so what i did was did some research and follow this. so now im back on GE 4.2.2 and still i have no sound!!!!!!! but i had with 4.2.2 touchwiz help please help please.
Last night i flashed back to stock 4.2.2 and reset my flash counter to get the bell update to 4.3.
All went well with the update. Untill i started playing.... Removed too many bloats... Wanted to start again...
FORGETTING that ATT users and others have been unable to flash back to 4.2.2 after installing 4.3
Trying to ODIN back to 4.2.2 was a mistake, it flashes the bootloaders, then fails at the kernel...
Phone stuck without the 4.3 odin file.... (not posted on sammobile or samsung-updates yet)
Long story short, we are able to flash back to 4.2.2 by flashing I337MUMUAMI1_I337MUWAAMI1_CDR from the domnican republic, then rooting by cfautoroot, installing recovery thru rom manager, then flashing a custom rom/restoring backup.
KNOX warning at bootscreen!!!!
Waiting for odin flashable file of bell 4.3 to be proper again.
Link to Dominican republic 4.2.2 http://samsung-updates.com/device/?i...axy_S_4_Canada
WARNING!!!! Microphone and wifi no longer work without proper modems.
fixed it, seems like all you have to do is download the old modem files.
Naruto101 said:
fixed it, seems like all you have to do is download the old modem files.
Click to expand...
Click to collapse
can u do a picture tutorial if u have the att i337 i have no sound but in my case i dint flash the moden i just flashed the NON-HLOS and i have no sound please help me out with a better explanation
Knox
That was said for a while now, you'll have trouble doing down by the knox
Hello, so even though I'm fairly new to the world of custom ROM's I feel as though this website has provided me with more than sufficient information for me to keep on flashing. I've flashed a few ROM's in the past but I'm currently stuck as for what I should do next. I currently have an S4 ATT MF3 which I would like to upgrade to MK2 so that I can put a 4.4.2. ROM via Safestrap using the Deadly Venom method.
Based on the guide (http://forum.xda-developers.com/showthread.php?t=2573080) I need to boot into the stock recovery and flash stock MF3 then MK2 which I can then root and safestrap. When I added my first ROM on this device I replaced the stock ROM (I have a hatred for TouchWiz) and replaced with a GPE ROM.
My phone can no longer boot into the stock Samsung recovery, it merely just bootloops instead, but I can still flash via Safestrap. So what should I do? Can I get the stock recovery back? Would I have any issues if I flash the MK2 update via Safestrap instead of the stock recovery? Will flashing the MF3 stock tar via Odin be all that I need to do? Any advice would be appreciated!
DarthVayda said:
Hello, so even though I'm fairly new to the world of custom ROM's I feel as though this website has provided me with more than sufficient information for me to keep on flashing. I've flashed a few ROM's in the past but I'm currently stuck as for what I should do next. I currently have an S4 ATT MF3 which I would like to upgrade to MK2 so that I can put a 4.4.2. ROM via Safestrap using the Deadly Venom method.
Based on the guide (http://forum.xda-developers.com/showthread.php?t=2573080) I need to boot into the stock recovery and flash stock MF3 then MK2 which I can then root and safestrap. When I added my first ROM on this device I replaced the stock ROM (I have a hatred for TouchWiz) and replaced with a GPE ROM.
My phone can no longer boot into the stock Samsung recovery, it merely just bootloops instead, but I can still flash via Safestrap. So what should I do? Can I get the stock recovery back? Would I have any issues if I flash the MK2 update via Safestrap instead of the stock recovery? Will flashing the MF3 stock tar via Odin be all that I need to do? Any advice would be appreciated!
Click to expand...
Click to collapse
If you don't mind losing your user data (back up anything you want from internal storage) just flash the MK2 full ODIN. Otherwise, there is a thread somewhere with just the MF3 recovery image and if you have root you could use an app to manually flash that (don't remember the app).
DeadlySin9 said:
If you don't mind losing your user data (back up anything you want from internal storage) just flash the MK2 full ODIN. Otherwise, there is a thread somewhere with just the MF3 recovery image and if you have root you could use an app to manually flash that (don't remember the app).
Click to expand...
Click to collapse
The app is flashify
Sent from my Nexus 5 using XDA Free mobile app
Possible to restore stock recovery?
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
pravus87 said:
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
Click to expand...
Click to collapse
I would flash in Odin the stock mf3 tar file, but out will wipe the device. All his apps and data. If you can find the mf3 recovery image file you could try to flash that in flashify, if you're rooted
Edit, found this. I didn't download the file but I'm guessing it's a .img file. You could flash that in flashify or use the dd command
Sent from my Nexus 5 using XDA Free mobile app
pravus87 said:
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
Click to expand...
Click to collapse
In addition to the above post from jd, the CM installer will not work on our device as our bootloader is locked. There is no way to run any AOSP based ROM once your phone is on MF3 firmware or higher.
DarthVayda said:
Hello, so even though I'm fairly new to the world of custom ROM's I feel as though this website has provided me with more than sufficient information for me to keep on flashing. I've flashed a few ROM's in the past but I'm currently stuck as for what I should do next. I currently have an S4 ATT MF3 which I would like to upgrade to MK2 so that I can put a 4.4.2. ROM via Safestrap using the Deadly Venom method.
Based on the guide (http://forum.xda-developers.com/showthread.php?t=2573080) I need to boot into the stock recovery and flash stock MF3 then MK2 which I can then root and safestrap. When I added my first ROM on this device I replaced the stock ROM (I have a hatred for TouchWiz) and replaced with a GPE ROM.
My phone can no longer boot into the stock Samsung recovery, it merely just bootloops instead, but I can still flash via Safestrap. So what should I do? Can I get the stock recovery back? Would I have any issues if I flash the MK2 update via Safestrap instead of the stock recovery? Will flashing the MF3 stock tar via Odin be all that I need to do? Any advice would be appreciated!
Click to expand...
Click to collapse
pravus87 said:
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
Click to expand...
Click to collapse
Here is the MF3 stock recovery, flash in PDA slot in Odin(AP in Odin v3.09+): https://mega.co.nz/#!klcz1B4J!BVAno0CcaJ7aXc9tHgUtpQ0vy_NF5ceh7RogLR6JBTU
muniz_ri said:
Here is the MF3 stock recovery, flash in PDA slot in Odin(AP in Odin v3.09+): https://mega.co.nz/#!klcz1B4J!BVAno0CcaJ7aXc9tHgUtpQ0vy_NF5ceh7RogLR6JBTU
Click to expand...
Click to collapse
Thanks to everyone for all the information, and thank you especially for sharing the link. I am staying with my parents short-term in a very rural area with awful internet and I was dreading downloading the 2+GB stock firmware file just to get recovery back. This is perfect. Thanks again!
My S4 is the i9505 (i think I got that right) M919 T-Mobile Version. It is currently running on CyanogenMod 11 M10 (latest stable release). I saved the latest 4.4.4 firmware (from SamMobile) and extracted the Modem.bin and NON-HOLS.bin (hindsight, should have just flashed the Modem.bin). And now my sound doesn't work. (Note: I flashed two kernels afterwards, not realizing the problem, but I reverted with a nandroid backup and in the about phone, it is the stock kernel of Cyanogenmod, so I don't think that had an effect)
So now that my sound doesn't work, I searched and realized that the NON-HOLS requires the same version Bootloader to work, so I first tried flashing the bootloader from the file mentioned above (aboot,rpm,sbl1 - sbl3). But I go and check my bootloader afterwards and it says that it was still the old one even through the flash passed. Next, I tried the NON-HOLS that matched the version of my bootloader, but again, still nothing.
So now I think it is something with my S4 that is not letting me flash. My phone's bootloader is unlocked (T-Mobile), and I don't have the Knox counter (probably because I switch to CyanogenMod before the 4.3 update from Carrier). I don't know what I should do now.
Brinith said:
My S4 is the i9505 (i think I got that right) M919 T-Mobile Version. It is currently running on CyanogenMod 11 M10 (latest stable release). I saved the latest 4.4.4 firmware (from SamMobile) and extracted the Modem.bin and NON-HOLS.bin (hindsight, should have just flashed the Modem.bin). And now my sound doesn't work. (Note: I flashed two kernels afterwards, not realizing the problem, but I reverted with a nandroid backup and in the about phone, it is the stock kernel of Cyanogenmod, so I don't think that had an effect)
So now that my sound doesn't work, I searched and realized that the NON-HOLS requires the same version Bootloader to work, so I first tried flashing the bootloader from the file mentioned above (aboot,rpm,sbl1 - sbl3). But I go and check my bootloader afterwards and it says that it was still the old one even through the flash passed. Next, I tried the NON-HOLS that matched the version of my bootloader, but again, still nothing.
So now I think it is something with my S4 that is not letting me flash. My phone's bootloader is unlocked (T-Mobile), and I don't have the Knox counter (probably because I switch to CyanogenMod before the 4.3 update from Carrier). I don't know what I should do now.
Click to expand...
Click to collapse
I would flash the full stock 4.2.2 .tar file in Odin from SamMobile. You should still be able to do that because you never upgraded to 4.3 with the knox protections.
That should restore your bootloader and modem back to exactly what it was when you bought the phone, overwriting the mismosh blend of 4.2 bootlaoder with 4.4 firmware parts.
You MAY have to flash it twice in Odin to get it to stick. Sometimes that's an issue when you try to use Odin to overwrite non stock firmware.
Once you get it flashed boot it and make sure it works properly in TouchWiz.
If it does, then go right back to Odin and flash whatever recovery you want to use and from there you should be able to flash whatever you want in recovery like normal.
You should NOT have to extract and push any audio files to make CM11 work like you said started this problem. That should not be a thing. I've still got the 4.2 bootloader and I'm running the latest CarbonROM (an offshoot of CM) and everything works fine. So something else must have been screwy to start.
Skipjacks said:
I would flash the full stock 4.2.2 .tar file in Odin from SamMobile. You should still be able to do that because you never upgraded to 4.3 with the knox protections.
That should restore your bootloader and modem back to exactly what it was when you bought the phone, overwriting the mismosh blend of 4.2 bootlaoder with 4.4 firmware parts.
You MAY have to flash it twice in Odin to get it to stick. Sometimes that's an issue when you try to use Odin to overwrite non stock firmware.
Once you get it flashed boot it and make sure it works properly in TouchWiz.
If it does, then go right back to Odin and flash whatever recovery you want to use and from there you should be able to flash whatever you want in recovery like normal.
You should NOT have to extract and push any audio files to make CM11 work like you said started this problem. That should not be a thing. I've still got the 4.2 bootloader and I'm running the latest CarbonROM (an offshoot of CM) and everything works fine. So something else must have been screwy to start.
Click to expand...
Click to collapse
Would a nandroid backup save the bootloader. I was thinking of installing the stock rom and then using the backup to revert to CyanogenMod.
Damn I flashed the stock ROM (pre 4.3) and I still got KNOX. Now it says "System software not authorized by Samsung has been found on your phone"
What should I do?
EDIT: I flashed the latest 4.4.4 Stock ROM since I already got KNOX (T_T, oh well warranty already over)
But what is the deal with the warning (shown above) and is there any way to prevent it from happening again other than reverting to stock everytime I want to flash something?
Brinith said:
Would a nandroid backup save the bootloader. I was thinking of installing the stock rom and then using the backup to revert to CyanogenMod.
Click to expand...
Click to collapse
No. The bootloader is not packaged with a nandroid.
And you do not need to mess with the bootloader. Just get it working and leave your bootloader alone forever.
---------- Post added at 03:56 PM ---------- Previous post was at 03:54 PM ----------
Brinith said:
Damn I flashed the stock ROM (pre 4.3) and I still got KNOX. Now it says "System software not authorized by Samsung has been found on your phone"
What should I do?
EDIT: I flashed the latest 4.4.4 Stock ROM since I already got KNOX (T_T, oh well warranty already over)
But what is the deal with the warning (shown above) and is there any way to prevent it from happening again other than reverting to stock everytime I want to flash something?
Click to expand...
Click to collapse
Are you sure its knox? Knox doesnt say that. Knox says 00x01 in the download screen.
Where are you seeing that message?
Skipjacks said:
No. The bootloader is not packago$h a nandroid.
And you do not need to mess with the bootloader. Just get it working and leave your bootloader alone forever.
---------- Post added at 03:56 PM ---------- Previous post was at 03:54 PM ----------
Are you sure its knox? Knox doesnt say that. Knox says 00x01 in the download screen.
Where are you seeing that message?
Click to expand...
Click to collapse
Im not sure if its Knox,but Knox is definitely now installed onto my phone. (KNOX warrenty void 0x1). Oh well my warranty is over so i don't really mind. But still, i want to know what that error (in above post) was as it didn't let me boot or go into recovery and only worked again once I reflashed.
And the reason why i flashed was that people say that updating the modem.bin and NON-HLOS would improve cell reception, and such. Which so far seems to be true, getting better signal in general (for wifi, uped by 10db than before so pretty significant), since i just flashed 4.4.4 for updated bootloader and modem since i already have Knox now.
i need help for my s4 gt-i9505