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,
Related
Hi,
First sorry for my bad English.
I'm not a dev and i don't know hot to make flashable zip's and all other stuf, but i thing it's possible to make one thing to revert back to old bootloader.
First in new roms we have two new files, one is persdata.img.ext4 and i think here is some knox app files. Other is sbl1.mbn and that file i thing is for bootloader to show knox in download mode. In previous roms we dont have sbl1.mbn, we have only sbl2 and sbl3 files.
In Es File Explorer i see that sbl1.mbn is in /firmware-mdm/image folder
First i think to delete that file and after that to test flashing BMGA rom with odin to replace other two sbl files, but i don't know if i delete that file do i have a download mode.
And if its possible some dev to make one flashable file with some script to delete that file with instalation and replacing sbl2 file in /firmware-mdm/image and sbl3.mbn with that from BMGA rom (i don't know where is placed sbl3, i don't find them in root directory.)
Odin got fail after trying to replace aboot.mbn if found any way way to flash or repace aboot.mbn in phone i think we go back to previous bootloader.
mitky82 said:
Hi,
First sorry for my bad English.
I'm not a dev and i don't know hot to make flashable zip's and all other stuf, but i thing it's possible to make one thing to revert back to old bootloader.
First in new roms we have two new files, one is persdata.img.ext4 and i think here is some knox app files. Other is sbl1.mbn and that file i thing is for bootloader to show knox in download mode. In previous roms we dont have sbl1.mbn, we have only sbl2 and sbl3 files.
In Es File Explorer i see that sbl1.mbn is in /firmware-mdm/image folder
First i think to delete that file and after that to test flashing BMGA rom with odin to replace other two sbl files, but i don't know if i delete that file do i have a download mode.
And if its possible some dev to make one flashable file with some script to delete that file with instalation and replacing sbl2 file in /firmware-mdm/image and sbl3.mbn with that from BMGA rom (i don't know where is placed sbl3, i don't find them in root directory.)
Odin got fail after trying to replace aboot.mbn if found any way way to flash or repace aboot.mbn in phone i think we go back to previous bootloader.
Click to expand...
Click to collapse
Is not posible. I tried to do this ... But the thing is that the new bootloader is eFused with the soft. Anyhow i managed yo get MF8 on my baseband and MF8 as rom . but no luck to change the bootloader
Sent from my GT-I9505 using xda app-developers app
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!
Hi guys.
Some of you have read that in Note 3 its actually possible to downgrade from Kit Kat to 4.3 stock rom without trigger the knox counter.
Well, I made this thread so we can change some experiences.
So far, I was able to flash the 4.3 XXEMJ7 firmware on a 4.4.2 phone by doing the follow:
1- Extract a 4.4.2 rom to a folder using 7Zip
2- Extract a 4.3 XXEMJ7 rom to another folder using 7Zip
3- Move system.img.ext4 hidden.img.ext4 mdem.bin NON-HLOS.bin and rpm.bin from the 4.3 folder to the 4.4.2 folder.
4- In a linux terminal: tar -cvf output.tar <File1 File2 file3 ....>
5- Flash with Odin the Output.tar.
The phone flashed till the end and power ok without bootloops. Basically I flashed a Knoxed 4.4.2 Bootloader to the phone with all it's appendices (sbl1.mbn sbl2.mbn sbl3.mbn aboot.mbn boot.mbn and recovery.img) but with a 4.3 System, Modem and Rel Power Managment (rpm.bin).
The phone powered up ok and we can see on the phone 4.3 XXEMJ7 under the Android Version and baseband I9505XXEMJ7.
BUT KNOX GET TRIGGED.
Now the challenge: Do all this without trigger the knox.
Any toughs ?
BrunoWestone said:
Hi guys.
Some of you have read that in Note 3 its actually possible to downgrade from Kit Kat to 4.3 stock rom without trigger the knox counter.
Well, I made this thread so we can change some experiences.
So far, I was able to flash the 4.3 XXEMJ7 firmware on a 4.4.2 phone by doing the follow:
1- Extract a 4.4.2 rom to a folder using 7Zip
2- Extract a 4.3 XXEMJ7 rom to another folder using 7Zip
3- Move system.img.ext4 hidden.img.ext4 mdem.bin NON-HLOS.bin and rpm.bin from the 4.3 folder to the 4.4.2 folder.
4- In a linux terminal: tar -cvf output.tar <File1 File2 file3 ....>
5- Flash with Odin the Output.tar.
The phone flashed till the end and power ok without bootloops. Basically I flashed a Knoxed 4.4.2 Bootloader to the phone with all it's appendices (sbl1.mbn sbl2.mbn sbl3.mbn aboot.mbn boot.mbn and recovery.img) but with a 4.3 System, Modem and Rel Power Managment (rpm.bin).
The phone powered up ok and we can see on the phone 4.3 XXEMJ7 under the Android Version and baseband I9505XXEMJ7.
BUT KNOX GET TRIGGED.
Now the challenge: Do all this without trigger the knox.
Any toughs ?
Click to expand...
Click to collapse
is sound working?
Dosnt work over here.. can extract and add all the files without a problem.. but flashing the tar fails every time..
tommyukuk said:
Dosnt work over here.. can extract and add all the files without a problem.. but flashing the tar fails every time..
Click to expand...
Click to collapse
Have you tar the files in linux terminal using "tar -cvf output.tar file1 fle2 file3 file4 etc.... ?
It's working for me.
Yeah exactly how you wrote, creates the file no probs but odin refuses to flash it what so ever.. never mind tho..
Sent from my GT-I9505 using xda premium
Downgrade flash
BrunoWestone said:
Hi guys.
Some of you have read that in Note 3 its actually possible to downgrade from Kit Kat to 4.3 stock rom without trigger the knox counter.
Well, I made this thread so we can change some experiences.
So far, I was able to flash the 4.3 XXEMJ7 firmware on a 4.4.2 phone by doing the follow:
1- Extract a 4.4.2 rom to a folder using 7Zip
2- Extract a 4.3 XXEMJ7 rom to another folder using 7Zip
3- Move system.img.ext4 hidden.img.ext4 mdem.bin NON-HLOS.bin and rpm.bin from the 4.3 folder to the 4.4.2 folder.
4- In a linux terminal: tar -cvf output.tar <File1 File2 file3 ....>
5- Flash with Odin the Output.tar.
The phone flashed till the end and power ok without bootloops. Basically I flashed a Knoxed 4.4.2 Bootloader to the phone with all it's appendices (sbl1.mbn sbl2.mbn sbl3.mbn aboot.mbn boot.mbn and recovery.img) but with a 4.3 System, Modem and Rel Power Managment (rpm.bin).
The phone powered up ok and we can see on the phone 4.3 XXEMJ7 under the Android Version and baseband I9505XXEMJ7.
BUT KNOX GET TRIGGED.
Now the challenge: Do all this without trigger the knox.
Any toughs ?
Click to expand...
Click to collapse
Yesterday, I made output.tar file as you write. I used 4.4.2 ROM and 4.3 ROM for my S4. I flashed output.tar to my phone via Odin and it passed OK. Bud when finished phone displays logo and then only black screen. I am not able to go to recovery. I had to go to download mode and flash original 4.4.2 ROM to phone. Then it works fine again. Twice same result...
Hi,
I did it in an other way. I removed the file aboot.mbn in the firmware-archive of the android-verion 4.3 and renamed it to I9505XXUEMKE.tar.
In odin I selected the tar file and flashed my S4. Well, it works, but I have no sound in the system. In which way can I fix this problem?
Thx so much
I'm looking forward.
Best wishes.
Look here: https://forum.xda-developers.com/galaxy-s4/help/downgrade-lollipop-to-jellybean-t3334506
hey guys
i found today galaxy s4 i9515 firmware 5.0.1 Lollipop
and i waited it alot of time
so i want to install it to my phone with Odin
but that firmware from another country (poland)
this is my phone i9515 VE version
Model GT-I9515
Model name GALAXY S4 VE
Country Saudi Arabia
Version Android 4.4.2
Changelist 928311
Build date Wed, 05 Mar 2014 12:20:18 +0000
Product code KSA
PDA I9515XXU1ANC2
CSC I9515OJV1AND1
this is lollipop version (poland)
Model GT-I9515
Model name GALAXY S4 VE
Country Poland
Version Android 5.0.1
Changelist 4421239
Build date Tue, 10 Mar 2015 11:19:37 +0000
Product code XEO
PDA I9515XXU1BOC3
CSC I9515OXA1BOC3
so i can use it for my phone or what and my data will gone if i use it ??
thnx for help
1. Backup all you internal data copying all the folders inside to your computer.
2. Create a nandroid backup with a CUSTOM RECOVERY if you wanna come back later to KIT KAT.
3. Backup your IMEI and your EFS folder: HERE.
3. Download and flash this firmware without the BOOTLOADER if you wanna come back later to KIT KAT. Lil GUIDE for remove bootloader of one firmware compressed: HERE.
4. Flash the firmware via ODIN and if you need more help go: HERE.
Joku1981 said:
1. Backup all you internal data copying all the folders inside to your computer.
2. Create a nandroid backup with a CUSTOM RECOVERY if you wanna come back later to KIT KAT.
3. Backup your IMEI and your EFS folder: HERE.
3. Download and flash this firmware without the BOOTLOADER if you wanna come back later to KIT KAT. Lil GUIDE for remove bootloader of one firmware compressed: HERE.
4. Flash the firmware via ODIN and if you need more help go: HERE.
Click to expand...
Click to collapse
the different in country will make problem ??? in calls or any thing like this
what is csc i cannot understand the important of it
and can i setup firmware without root ?
m4mo2015 said:
the different in country will make problem ??? in calls or any thing like this
what is csc i cannot understand the important of it
and can i setup firmware without root ?
Click to expand...
Click to collapse
1. Different country (CSC different) affects only to 4G and OTA updates.
2. CSC ("Country Specific Code") is basically the configuration data APN, MMS, etc ... in each country.
3. Flashing new firmware erase root access.
It worked man without root
And all my data still the same after flash without wipe xD
And no problems with wifi networks
I want my Lollipop
m4mo2015 said:
It worked man without root
And all my data still the same after flash without wipe xD
And no problems with wifi networks
Click to expand...
Click to collapse
hey congrats you got your s4 updated.... i also have a KSA version of Galaxy s4.... and there's a Poland version rolling out , does it have Arabic Language in it?, and can you send me a link which tutorial did you follow for updating your s4.
Yes you can use it. There is no problem at all. And it will not erase your data.
I'm using it.
Regards
shakeelasghar said:
Yes you can use it. There is no problem at all. And it will not erase your data.
I'm using it.
Regards
Click to expand...
Click to collapse
i'm stuck on this
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
after this it just say it fails
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
using odin 3.07
mind to help how to fix?
or can you show how you successfully fixed yours?
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