Database Users

[Guide]Modify stock rom and delete bootloader with Knox for Galaxy S4

Hi,
Like, I'll send my phone to the SAV, because cracked glass, I don't want that they make the update, I'm with Android 4.2.2, I prefer to put a custom 4.3 or 4.4 with the old bootloader. I would like to put an official touchwizz 4.3 but without new bootloader, so they won't update it if they see that it is version 4.3 official.
Do you think that's possible? - It's possible, but does it work?
Or do you know how I could remove the new bootloader of the rom installing via ODIN? - Method below.
Is there an official 4.3 rom flashable via ODIN? - I made one but no tested!!!
Is there a risk to remove the bootloader of the rom? - I don't think but we are never sure of anything.
Because at worst, if they saw it, I could say that I did the normal update and it had to go wrong!
Here, a mate explain how make it!
explication of the Android structure:
sbl1.mbn - part of new bootloader , safe to delete
sbl2.mbn - part of new bootloader , safe to delete
sbl3.mbn - part of new bootloader , safe to delete
aboot.mbn - New Knox bootloader , DELETE
rpm.mbn - Resource power Management link
tz.mbn - Trusted zone ( Wifi won`t work if u don`t flash it together with new Modem )
boot.img - Kernel
recovery.img - Recovery/Download mode
system.img.ext4 - your apps/framework/android
NON-HLOS.bin - modem
cache.img.ext4 - CSC / APN settins / What bloat is to be installed depending on zone / carrier
hidden.img.ext4 - Another "system" part of apps that are too big for /system ( for now almost empty ) on S2 was full of apps
I've successful to make the modification with ubuntu, but I've a doubt, I wonder why he has not put the modem.bin file to inside. Reason in the post below.
Is someone can inform me if it is reliable or not?

I know why I believed he removed the file modem.bin, there isn't to modem.bin file on the S4 mini.
Edited: I misunderstood his answer!

so did you try it?

No, I don't know if I must do it, SAV sometimes make updates without thinking, so I do not think it's worth trying. But I think it should work, there is no reason!

Cant obtain root for MJE

Hey everyone. Hoping someone can help. I asked questions in the URDLV thread but got my hand slapped because that thread isn't in the official Verizon forums.
No idea what Im doing wrong. Here are the details.. I got my CSC. I downloaded N900VVRUBMJE_N900VVZWMJE.
I have cygwin installed. I have Universal-RDLV_v05 on my desktop. I open cygwin and cd to that folder. I then run ./URDLV.sh full (Path To My MJE tar.md5) inside of cygwin.
When I do this it extracts the firmware, says its hooking system image, verifies system hook, finds system hook and then creates an odin flash able tar. The creation pieces takes about 15 seconds and a new tar is in my output folder. I then put the phone into download mode and use odin to AP that tar.md5 file. Odin gets all the way to the end and then it fails. If I reboot the phone its corrupt and I have to odin the regular MJE to get back up and running.
What am I doing wrong? I don't get any errors that indicate that Im having issues when it is creating the tar. And the regular tar I have before going through this mess is fine as I can Odin it ok before running the script. Verizon Note 3.
I want to add that I have followed the steps in post 1127 of that thread exactly, using the firmware for my phone, and it still failed at the end.
http://forum.xda-developers.com/show...postcount=1127
Not sure where I am going wrong on this.

To expand on my last post - I decided to redownload the tar file from sammobile and start the whole process over again. I still get the fail when pushing the created tar file in Odin so I started following GalaxHE's post again.
This time I get all the way to this part:
ComputerName /cygdrive/c/temp/MK2_stock
$ tar -H ustar -c boot.img modem.bin rpm.mbn system.img.ext4 cache.img.ext4 NON-HLOS.bin sbl1.mbn tz.mbn hidden.img.ext4 recovery.img sdi.mbn > MK2VEGA.tar
In my case, I named the files MJE_stock. I run the above script in cygwin and get this error:
/cygdrive/c/temp/MJE_stock
$ tar -H ustar -c boot.img modem.bin rpm.mbn system.img.ext4 cache.img.ext4 NON-HLOS.bin sbl1.mbn tz.mbn hidden.img.ext4 recovery.img sdi.mbn > MJEVEGA.tar
tar: hidden.img.ext4: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
This file does NOT exist on my MJE_stock folder. I never touched it in any way. I just went back to the original MJE file I downloaded from sammobile, extracted it down again, and there is no hidden.img.ext4 file anywhere to be seen.
What is this file and how important is it? the MJE from sammobile restores my phone fine, even though that file isnt in it.
I packaged the file by taking the piece regarding that hidden file out. Worse case I figured I repackage and start from there. Went through the remaining steps and pushed the file with Odin and once again it fails. Same place each time.
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Someone, PLEASE HELP.

Hello sir,
First step. Relax. I'll take care of ya. '/cygdrive/c/temp/MK2_stock' it looks like you might have downloaded the wrong package.
Here is stock MJE
Download that. Next, you'll want to get Kingo root here
Ignore all the hubub about it, it's fine. Go ahead and get that.
System.img is giving a fail auth error either because it's for the S4, or it's because the file is not 'signed' meaning it's not authorized by Verizon/Samsung, since it's not official, or it wasn't made for your specific model. PM me if you need any further assistance.
For further reference, you can find all VZW firmware and modems in this thread here

ryanbg said:
Hello sir,
First step. Relax. I'll take care of ya. '/cygdrive/c/temp/MK2_stock' it looks like you might have downloaded the wrong package.
Here is stock MJE
Download that. Next, you'll want to get Kingo root here
Ignore all the hubub about it, it's fine. Go ahead and get that.
System.img is giving a fail auth error either because it's for the S4, or it's because the file is not 'signed' meaning it's not authorized by Verizon/Samsung, since it's not official, or it wasn't made for your specific model. PM me if you need any further assistance.
For further reference, you can find all VZW firmware and modems in this thread here
Click to expand...
Click to collapse
Hello. Thanks for the reply.
Despite mentioning MK2, I did use MJE. As I mentioned, I can flash the MJE file before modifying it with URDLV fine. I obtained my CSC and used that to determine that MJE was the right file for me.
Based on the name of the file you linked me to, thats the same file I used. Its like somehow when using URDLV the system.img is becoming corrupted.
I wouldn't think Verizon would use the same MJE file for the S4 as it does for the note? Wouldn't it be completely different?
I was really trying to avoid using Kingo since it seems like no one knows exactly what all its doing yet.

GaresTaylan said:
Hello. Thanks for the reply.
Despite mentioning MK2, I did use MJE. As I mentioned, I can flash the MJE file before modifying it with URDLV fine. I obtained my CSC and used that to determine that MJE was the right file for me.
Based on the name of the file you linked me to, thats the same file I used. Its like somehow when using URDLV the system.img is becoming corrupted.
I wouldn't think Verizon would use the same MJE file for the S4 as it does for the note? Wouldn't it be completely different?
I was really trying to avoid using Kingo since it seems like no one knows exactly what all its doing yet.
Click to expand...
Click to collapse
The URDLV program you are running modifies MJE. You are correct. The problem is that when you modify that file, you break the digital signature on that file, meaning it is no longer the original file and is not authorized to be flashed. It appears that program is for people without signature verification enabled aka 'unlocked bootloader' if you will. The Verizon Note 3 does not have such luxury. I wouldn't worry about Kingo. It's a closed source exploit because they don't want it patched, which might make some people uncomfortable, and rightfully so, but I've yet to see any implications from it and I've used it multiple times on multiple devices. Vroot was the sketchy one sending IMEIs to China.

Need Bootloader package for G900FDXUANG1

I have a Singapore variant of the 900F, which has the latest firmware package of G900FDXUANG1 (but modem is still XXUANE2). I'm hoping to use the mobile odin/everoot method of rooting this phone, but I realize that this will require separate modem and bootloader files, in addition to the actual firmware file.
Does anyone have the bootloader package for DXU1ANG1? Or can anyone help me with extracting it from the stock firmware file?
Thanks!

You didn't explain or elaborate about the method that you referred to.. so it isn't clear what you are trying to do.
Normally, a bootloader is only updated if it is part of a full firmware image. We don't often see separate bootloader files. If you really need that, you can try doing a comprehensive search. But more than likely you'd need to format the bootloader files yourself.
From memory, extract the following files from the full firmware image, then package them together in a .tar.md5 volume. These are the files that constitute the bootloader. You should do a forum search to confirm the file names since I am writing them out from memory.
aboot.mbn
sbl1.mbn
rpm.mbn
tz.mbn
sdi.mbn
You'd then flash the .tar.md5 with Odin, specifying the .tar.md5 file name on the BL Odin line. Realize that flashing the bootloader is hazardous and should anything go wrong, you will have a bricked device that won't be easy to recover.
.

fffft said:
You didn't explain or elaborate about the method that you referred to.. so it isn't clear what you are trying to do.
Normally, a bootloader is only updated if it is part of a full firmware image. We don't often see separate bootloader files. If you really need that, you can try doing a comprehensive search. But more than likely you'd need to format the bootloader files yourself.
From memory, extract the following files from the full firmware image, then package them together in a .tar.md5 volume. These are the files that constitute the bootloader. You should do a forum search to confirm the file names since I am writing them out from memory.
aboot.mbn
sbl1.mbn
rpm.mbn
tz.mbn
sdi.mbn
You'd then flash the .tar.md5 with Odin, specifying the .tar.md5 file name on the BL Odin line. Realize that flashing the bootloader is hazardous and should anything go wrong, you will have a bricked device that won't be easy to recover.
.
Click to expand...
Click to collapse
Hey, thanks for that. The 'method' I'm hoping to use is detailed in the thread here. It basically involves downgrading to a firmware that's rootable by towelroot, then upgrading using Mobile Odin and everoot. The bootloader files and modem files need to be flashed separately via Odin PC using this method, as the mobile version doesn't seem to do it. I have the modem file for my phone, but not the bootloader. Have dug through the forums, but have unfortunately not found anyone who's posted the bootloader for the DXU1ANG1 firmware yet.

If a pre June 3rd version of the full firmware is available for your phone.. and it most likely is.. then you should be able to revert by using the full firmware image. And thereafter should be amenable to the Towel root exploit.
Then if you still wish to upgrade to ANG1, use Mobile Odin Pro to do so.. and you should retain root.
The above seems a lot easier and more to the point, less risky than the approach that you seeking to do. But it's your phone.. so whichever you prefer.
.

fffft said:
If a pre June 3rd version of the full firmware is available for your phone.. and it most likely is.. then you should be able to revert by using the full firmware image. And thereafter should be amenable to the Towel root exploit.
Then if you still wish to upgrade to ANG1, use Mobile Odin Pro to do so.. and you should retain root.
The above seems a lot easier and more to the point, less risky than the approach that you seeking to do. But it's your phone.. so whichever you prefer.
.
Click to expand...
Click to collapse
Yup, that was my plan. however in the thread i mentioned, the OP who's actually tried it mentions that he needed to flash the bootloader and modem separately via pc.odin, as the mobile odin pro did not flash the bootloader or modem for.some reason. hence why i'm trying to get my hands on the bootloader for ANG1.

[Q] Flashing Fido Img via Odin

I have AT&t S4 I337 , I downloaded the stock firmware , Im able to unpack and pack the img , then flash Via ODin , So I downloaded the Stock Firmware for the I337M fido , I unpacked it then took the System.img.ext4 and placed it in my AT&t folder with the AT&t stock cache,sbl1 sbl2 etc , I packed and created a flashable Md5.tar but when flashing reaches the System.img.ext4 file I get a Fail (auth) !! and If Iput back the AT&T system.img.ext4 and pack it , Im able to flash?? . the reason why I want the Fido System.img.ext4 is because , Wifi hotspot is enabled , and sending emoji as regular sms not mms is enabled , I have searched various threads on how to compile Odin flashable firmware , every way I try it works only if I use the AT-T system.img.ext4 , which I dont want , I was also able to unpack the System.img.ext4 for both at&t and Fido and compare them , what I want to do is keep the AT&T kernal and use all Fido img , but my problem is once I have the Folder complete with all the files and folders I need, how do I compile that whole folder into a System.img.ext4 ?? any help would be greatly apreciated!!:good:

mannyvr6 said:
I have AT&t S4 I337 , I downloaded the stock firmware , Im able to unpack and pack the img , then flash Via ODin , So I downloaded the Stock Firmware for the I337M fido , I unpacked it then took the System.img.ext4 and placed it in my AT&t folder with the AT&t stock cache,sbl1 sbl2 etc , I packed and created a flashable Md5.tar but when flashing reaches the System.img.ext4 file I get a Fail (auth) !! and If Iput back the AT&T system.img.ext4 and pack it , Im able to flash?? . the reason why I want the Fido System.img.ext4 is because , Wifi hotspot is enabled , and sending emoji as regular sms not mms is enabled , I have searched various threads on how to compile Odin flashable firmware , every way I try it works only if I use the AT-T system.img.ext4 , which I dont want , I was also able to unpack the System.img.ext4 for both at&t and Fido and compare them , what I want to do is keep the AT&T kernal and use all Fido img , but my problem is once I have the Folder complete with all the files and folders I need, how do I compile that whole folder into a System.img.ext4 ?? any help would be greatly apreciated!!:good:
Click to expand...
Click to collapse
It's not going to work as it only takes the signed AT&T packages. You'd have to pull out what you need manually. A better option is to flash a ROM with tethering enabled and use an SMS app that allows emojis.

DeadlySin9 said:
It's not going to work as it only takes the signed AT&T packages. You'd have to pull out what you need manually. A better option is to flash a ROM with tethering enabled and use an SMS app that allows emojis.
Click to expand...
Click to collapse
I already modded the AT&T sms app , moded a smali file to enable emoji through sms not mms , Cant find any guides on how to mod tethering.apk that work , so far I have tried 2 guides , I tried Golden Eye , Nice rom , but I still prefer stock rooted,

[Q] how to create ODIN package with Modem and Bootloader from Stock rom?

Hello,
I am on Cyanogenmod 13. and I have outdated Modem and Bootloader. which effect my network signal
I have downloaded the latest stock firmware which is for my specific device .
from reading all over XDA this is what i understand is the procedure:
1. getting the right stock rom <- done
2. extracting the required files <- my main question
3. create 2 tar packages for Modem and for Bootloader
4. creating MD5 checksum of both file.
5. flashing using ODIN while placing modem file to CR slot and Bootloader to BL slot. (flashing it twice before boot as it might be reset)
now i know how to do all this steps but my problem is to understand which files are required to Modem tar and Bootloader tar.
the available flash-able files made by the community are not consistent. for example some of the modem tar file people made contain modem.bin and NON-HLOS.bin while others only modem.bin.
this are the files in the original stock rom:
aboot.mbn
sbl1.mbn
rpm.mbn
tz.mbn
sdi.mbn
NON-HLOS.bin
boot.img
recovery.img
system.img.ext4
modem.bin
cache.img.ext4
hidden.img.ext4
which of them i need to place in the Bootloader tar (BL) and which in the Modem tar (CP)?

I've also searched around hoping to find answer to this question. I've also compared a lot of bootloader & modem tarballs and each was different. If you found a solution please post it here. Otherwise the safest way is to flash stock firmware and then reflash it with desired custom one ...

allidea said:
I've also searched around hoping to find answer to this question
Click to expand...
Click to collapse
Which one? About Odin's slot? Use AP slot for everything.

bbsc said:
Which one? About Odin's slot? Use AP slot for everything.
Click to expand...
Click to collapse
I'd like to know which files to extract from stock FW. I don't want to end up in boot loop or something worse.
From what I've seen my stock ROM has following files as shown on 1st attachment and most custom modem + bootloader tarballs have files (below files are from PhoeniX ROM v13.6) as shown on 2nd attachment.
There is one particular file named sdi.mbn which can be found in custom modem+bootloader tarballs and which is not present in stock rom.

Ok, I don't know if it's correct or no, but I used for bootloader/modem/kernel update on SM-G900V such a file as shown on the picture.
The original (HOME) .tar.md5 was renamed to .tar.
The next files from it were deleted:
- cache.img.ext4;
- system.img.ext4.
Pit-file was added.
The resulting file was flashed via Odin's AP slot.
Result:
- bootloader, recovery, kernel and modem updated;
- Binary: Official; System: Official;
- all data on /data remain untouched.

allidea said:
I've also searched around hoping to find answer to this question. I've also compared a lot of bootloader & modem tarballs and each was different. If you found a solution please post it here. Otherwise the safest way is to flash stock firmware and then reflash it with desired custom one ...
Click to expand...
Click to collapse
All described here: https://jdrch.wordpress.com/2017/01...ions-without-breaking-custom-rom-or-recovery/

Thanks to both of you. @Hawaiihemd - As I already mentioned I am bothered by mysterious file named sdi.mbn which is not present in stock ROM (also mentioned by others who asked around about it too) but everyone mentioned it should be there ... funny ...

allidea said:
Thanks to both of you. @Hawaiihemd - As I already mentioned I am bothered by mysterious file named sdi.mbn which is not present in stock ROM (also mentioned by others who asked around about it too) but everyone mentioned it should be there ... funny ...
Click to expand...
Click to collapse
Are you still trying to figure this out??

bobbylo said:
Are you still trying to figure this out??
Click to expand...
Click to collapse
Nope. I don't know if I figured it out, but I've extracted all files from stock ROM as shown on second attachment in Post #4 above except sdi.mbn, created a .tar and flashed via ODIN ... Everything is working fine and new modem is displayed in device info.

allidea said:
Nope. I don't know if I figured it out, but I've extracted all files from stock ROM as shown on second attachment in Post #4 above except sdi.mbn, created a .tar and flashed via ODIN ... Everything is working fine and new modem is displayed in device info.
Click to expand...
Click to collapse
ok,so you created a .tar?Not a .tar.md5? why did'nt you need the sdi.mbn?

bobbylo said:
ok,so you created a .tar?Not a .tar.md5?
Click to expand...
Click to collapse
No just .tar as ODIN will accept it as well. I'm no expert but my guess .md5 is just a hash to verify .tar.
I used a tool named Odin Tar Converter v1.0 I think I found it on xda somewhere, but you can use any compression tool which is able to make .tar archives ie. 7-Zip.
Afterwards I just followed instructions for flashing bootloader and modem from PhoenixROM so I added .tar archive I've created to AP (newer ODIN) / PDA (older ODIN) and flashed it.
I've came across following instructions:
For the bootloader select BL and browse to your bootloader file.
For the modem select CP and browse to your modem file.
Click to expand...
Click to collapse
But since I created .tar regarding PhoenixROM bootloader and modem .tar structure it made more sense to follow PhoenixROM instructions.
why did'nt you need the sdi.mbn?
Click to expand...
Click to collapse
Maybe I needed it, but no matter how many stock ROMs I got my hands on none of them had this file. According to this article it seems sdi.mbn contains contains transmission band info although I don't think author himself was clear what it actually is used for. Anyway I decided to try and flash modem without it.

allidea said:
No just .tar as ODIN will accept it as well. I'm no expert but my guess .md5 is just a hash to verify .tar.
I used a tool named Odin Tar Converter v1.0 I think I found it on xda somewhere, but you can use any compression tool which is able to make .tar archives ie. 7-Zip.
Afterwards I just followed instructions for flashing bootloader and modem from PhoenixROM so I added .tar archive I've created to AP (newer ODIN) / PDA (older ODIN) and flashed it.
I've came across following instructions:
But since I created .tar regarding PhoenixROM bootloader and modem .tar structure it made more sense to follow PhoenixROM instructions.
Maybe I needed it, but no matter how many stock ROMs I got my hands on none of them had this file. According to this article it seems sdi.mbn contains contains transmission band info although I don't think author himself was clear what it actually is used for. Anyway I decided to try and flash modem without it.
Click to expand...
Click to collapse
Ok,was just wondering...I have an xda page where i created bootloaders and modems for the S5 G900T t-mobile.I use a program called cygwin64 to create the .tar.md5 files.It involves some command line input..Maybe yours is easier....Anyway,don't think i'll need to make any more,as i think there done with updates for the G900T,and maybe all the S5's