Develop Bugs

[Q] S4 Mini I9190 3g firmware, help?

Hi there, I have a s4 galaxy mini GT-I9190 says baseband version: I9190ZSUAMG1. Build number: JDQ39.i9190ZSUAMG1. I believe it is a Hong Kong version? Sorry I'm a noob. I am looking for the United Kingdom firmware. Could anyone send me a link so I can download it? As I am not sure what I need.
Also is it fairly easy to do the update?
Regards,
Alan

A14n said:
Hi there, I have a s4 galaxy mini GT-I9190 says baseband version: I9190ZSUAMG1. Build number: JDQ39.i9190ZSUAMG1. I believe it is a Hong Kong version? Sorry I'm a noob. I am looking for the United Kingdom firmware. Could anyone send me a link so I can download it? As I am not sure what I need.
Also is it fairly easy to do the update?
Regards,
Alan
Click to expand...
Click to collapse
Yes you currently have either the Hong Kong (TGY) firmware or Taiwans (BRI) region.
It seems that your model doesn't have the U.K Stock firmware as of yet.
Check out: http://samsung-updates.com/device/?id=GT-I9190
I'm not sure if any other regions will work.
To note on if it's easy to update firmwares;
Some info on every step for rooting>recovery>flashing firmwares or custom roms steps
Updating/Restoring your firmware is relatively easy.
Go to the following thread to get started with rooting your device and flashing a custom recovery which is needed for flashing Firmwares and Roms: http://forum.xda-developers.com/showthread.php?t=2398143
Kies: http://www.samsung.com/uk/support/usefulsoftware/KIES/JSP
Sent from my GT-I9195 using xda app-developers app

Will there ever be any UK firmware for the I9190 non LTE? If the (i9195) has the uk version already. I'm not even sure you can buy the i9190 in the UK? As i bought this one from Ecell off ebay, Hong Kong version.
Would the i9195 rom work on the i9190? probably a stupid question... Or is there any europeon roms out there that would be better than the HK version.
I'm encountering problems, on the google play store. There's a game called asphalt 7/8. When I go to it in the store it comes up. " your device isn't compatible with this version". Is it region locked or something? It thinks im in HK so I can't get it? It's really annoying. Is there anything I can do?
Alan

The i9195 ROM will NOT work on the i9190.
You could email the developers for info regarding asphalt. If it were region locked, it wouldn't show up on your play store at all.

Frustrating...i9190 in UK
Thats the thing it does not show up in my play store. Only way I see it is by clicking a link to the game on google. Then it says" your device isn't compatible with this version".
What can I do, this is so frustrating. I am in the UK and it thinks I'm in HK. Anyway around this?... Any other firmware out there with a region that can access everything on google play without restrictions?
I don't mind rooting my phone, have done it before on an older android.

A14n said:
Thats the thing it does not show up in my play store. Only way I see it is by clicking a link to the game on google. Then it says" your device isn't compatible with this version".
What can I do, this is so frustrating. I am in the UK and it thinks I'm in HK. Anyway around this?... Any other firmware out there with a region that can access everything on google play without restrictions?
I don't mind rooting my phone, have done it before on an older android.
Click to expand...
Click to collapse
Like i said before i'm not sure if other regions will work for your device.
GT-I9195 files will most definately not work since it uses another kernel iirc.
You could ask Arco regarding suitable regions for your device other than HK for European customers or you could install CWM on your device and try some E.U firmwares out yourself.
If none of them work or you get bootloops you can always hop back to the Hong Kong firmware.
Last but not least, if none of this works and you're still eager to play asphalt you should google for the APK & SD files (.obb) which ofcourse is illigal and i cannot link you to it (sorry have to stick to xda rules).
Sent from my GT-I9195 using xda app-developers app

Thanks for your help, who is Acro do you have their contact details? I have successfully rooted the phone now. Got CWM installed.
I've tried the Market Enabler app to get asphalt 8. But that does not seem to work. Damn why didn't I get the S4 mini LTE.

A14n said:
Thanks for your help, who is Acro do you have their contact details? I have successfully rooted the phone now. Got CWM installed.
I've tried the Market Enabler app to get asphalt 8. But that does not seem to work. Damn why didn't I get the S4 mini LTE.
Click to expand...
Click to collapse
Arco68 is a developer/user here at xda , he works on CyanogenMod 10.1-Nightlies for the GT-I9195. Just check out the general S4 Mini section.
Sent from my GT-I9195 (CM10.1-Nightlies) using xda premium app-developers app

Bricked? Help
Ok I tried flashing the phone using Odin, and it failed right at the end. Now phone is stuck saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Well I tried that and Kies is not detecting anything :'(. Looks like I've broken it completely now.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9190XXUAMF7_I9190OJVAMG2_I9190XXUAMF7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> tz.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> persist.img.ext4
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

A14n said:
Ok I tried flashing the phone using Odin, and it failed right at the end. Now phone is stuck saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Well I tried that and Kies is not detecting anything :'(. Looks like I've broken it completely now.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9190XXUAMF7_I9190OJVAMG2_I9190XXUAMF7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> tz.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> persist.img.ext4
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Is that the Hong Kong firmware? Did you made a backup before you did anything? You should know that its a must if your inexperienced with this kind of stuff.
Have you tried renaming the zip file to update.zip and load it from cwm or if you have it, the backup file? maybe that will work.

Ok I managed to get the phone up and running again I reinstalled CWM. Then flashed a different firmware I9190UBUAMH1 and it passed this time. Seems way better a lot less bloatware more UK friendly.
Asphalt 8 still shows as incompatible, mystery as to why? I have seen videos on YouTube of it running on the S4 Mini. I have e-mailed gameloft, but no reply yet.

A14n said:
Ok I managed to get the phone up and running again I reinstalled CWM. Then flashed a different firmware I9190UBUAMH1 and it passed this time. Seems way better a lot less bloatware more UK friendly.
Asphalt 8 still shows as incompatible, mystery as to why? I have seen videos on YouTube of it running on the S4 Mini. I have e-mailed gameloft, but no reply yet.
Click to expand...
Click to collapse
Good that everything worked out eventueel.
Just Google the asphalt 8 apk and sd data files and save yourself the trouble (and money lolz). It worked for me with most games incl. Asphalt 7 & 8.
Sent from my GT-I9195 (CM10.1-Nightlies) using xda premium app-developers app

A14n said:
Ok I managed to get the phone up and running again I reinstalled CWM. Then flashed a different firmware I9190UBUAMH1 and it passed this time. Seems way better a lot less bloatware more UK friendly.
Asphalt 8 still shows as incompatible, mystery as to why? I have seen videos on YouTube of it running on the S4 Mini. I have e-mailed gameloft, but no reply yet.
Click to expand...
Click to collapse
Please Help Me
My Phone is I9190 .
it was running i9190xxuamf7 , then i install I9190ZSUBML3 and among installing it failed with this message " Odin : Invalid system.img.ext4 "
after that i reinstall i9190xxuamf7 then installed successfully but after boot there was No Radio such as Antena ,Bluethooth , wifi
then i install i9190xxuamf7 with a i9192 pit & Odin Failed with This Message :
" Set Waranty Bit : System
Set Waranty Bit : Cache
Set Waranty Bit : Hidden "
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9190XXUAMF7_I9190OJVAMG2_I9190XXUAMF7_HOME.tar.md 5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> tz.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> persist.img.ext4
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
PLEASE !!! SOMEONE HELP ME... I AM SO SAD & TIRED
WHAT SHOULD I DO ?

SOLVED !
bahmax said:
please help me
my phone is i9190 .
It was running i9190xxuamf7 , then i install i9190zsubml3 and among installing it failed with this message " odin : Invalid system.img.ext4 "
after that i reinstall i9190xxuamf7 then installed successfully but after boot there was no radio such as antena ,bluethooth , wifi
then i install i9190xxuamf7 with a i9192 pit & odin failed with this message :
" set waranty bit : System
set waranty bit : Cache
set waranty bit : Hidden "
<osm> enter cs for md5..
<osm> check md5.. Do not unplug the cable..
<osm> please wait..
<osm> i9190xxuamf7_i9190ojvamg2_i9190xxuamf7_home.tar.md 5 is valid.
<osm> checking md5 finished sucessfully..
<osm> leave cs..
<id:0/004> odin v.3 engine (id:4)..
<id:0/004> file analysis..
<id:0/004> setupconnection..
<id:0/004> initialzation..
<id:0/004> get pit for mapping..
<id:0/004> firmware update start..
<id:0/004> singledownload.
<id:0/004> tz.mbn
<id:0/004> nand write start!!
<id:0/004> boot.img
<id:0/004> recovery.img
<id:0/004> system.img.ext4
<id:0/004> persist.img.ext4
<id:0/004> non-hlos.bin
<id:0/004> cache.img.ext4
<id:0/004> hidden.img.ext4
<id:0/004> fail! (size)
<id:0/004>
<id:0/004> complete(write) operation failed.
<osm> all threads completed. (succeed 0 / failed 1
please !!! Someone help me... I am so sad & tired
what should i do ?
Click to expand...
Click to collapse
i solved my problem !
I found out if your last good worked rom is "z" you should instal 'z' based rom & if it was 'x' you should install 'X' based rom.
For example mine was i9190xxuamf7 & i install i9190zsubml3 then my phone crashed even when i reinstalled i9190xxuamf7 because phone did not let me downgrade so i should upgrade it to a 'x' based rom so i install i9190xxubmj7 then my phone worked correctly and my problem solved
good luck
bahman mahmoudzadeh
25-day-1392

same problem i cant flash orginal fw
I9190XXUCOC1_I9190SERCOC1_I9190XXUCOC1_HOME.tar can flash
I9190XXUCOD2_I9190OJVCOD2_I9190XXUCOD2_HOME.tar cant flash

[Q] Return to Stock Rom 4.3 After CyanogenMod

im in a bit of a pickle here.
so i had android 4.3 stock rom but then switched to cyanogemod 10.2.. today i decided i wanted to go back to stock rom so i tried using odin 3.07 and flashing I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 (i cant find 4.3 firmware anywhere). i go into download mode, put that file in PDA, and odin tells me:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
and on my phone is says SV REV Check Fail : Fused 2 > Binary 0
i was trying to find stuff out online and they said something about a bootloader and i have no clue what that means. also, cyanogenmod is no longer even going to the home screen so my phone is not functioning at all. and since it isnt loading, my computer isnt detecting a device so i cant add any files to my phone.
can someone please help me? using english please, not computer hacker language. im not that advanced in this kind of stuff.

camerondobbs said:
im in a bit of a pickle here.
so i had android 4.3 stock rom but then switched to cyanogemod 10.2.. today i decided i wanted to go back to stock rom so i tried using odin 3.07 and flashing I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 (i cant find 4.3 firmware anywhere). i go into download mode, put that file in PDA, and odin tells me:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
and on my phone is says SV REV Check Fail : Fused 2 > Binary 0
i was trying to find stuff out online and they said something about a bootloader and i have no clue what that means. also, cyanogenmod is no longer even going to the home screen so my phone is not functioning at all. and since it isnt loading, my computer isnt detecting a device so i cant add any files to my phone.
can someone please help me? using english please, not computer hacker language. im not that advanced in this kind of stuff.
Click to expand...
Click to collapse
Unfortunately my friend, Odin will not work to return back to stock. By chance did you make a nandroid backup before you switched from 4.3 to CyanogenMod? If not I'd suggest finding a TW based rom from one of the devs on here under the Android Development thread and flash it manually via CWM or TWRP. I'm looking myself for a 4.3 TW Odin tar but nothing has surfaced to my knowledge. You're trying to flash a 4.0 rom in Odin it looks like which won't work since 4.3 updates the baseband and bootloader which will cause Odin to fail every time you try flashing a rom that isn't 4.3

camerondobbs said:
im in a bit of a pickle here.
so i had android 4.3 stock rom but then switched to cyanogemod 10.2.. today i decided i wanted to go back to stock rom so i tried using odin 3.07 and flashing I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 (i cant find 4.3 firmware anywhere). i go into download mode, put that file in PDA, and odin tells me:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
and on my phone is says SV REV Check Fail : Fused 2 > Binary 0
i was trying to find stuff out online and they said something about a bootloader and i have no clue what that means. also, cyanogenmod is no longer even going to the home screen so my phone is not functioning at all. and since it isnt loading, my computer isnt detecting a device so i cant add any files to my phone.
can someone please help me? using english please, not computer hacker language. im not that advanced in this kind of stuff.
Click to expand...
Click to collapse
if you still can go into downloadmode, you can unroot your device and put it back to stock with Kies 3.
Download Kies 3 from samsung web site and download Samsung USB Drivers too
Unplug your phone from the PC
After on Kies 3 click on tools>emergency firmware update and inisialitazion.
Now they will ask for your phone model so if you are on at&t its : SGH-I747 (Rogers bell .. tis : SGH-I747M
After, Kies 3 will ask you your S/N (this can be found under your battery the sticker) so remove your battery and write it down
Know if it work they gonna tell you to put your phone into download mode
To go into download mode hold : Volume Down + Home Button + Power button
After on your phone you should see a Yellow triangle with some warning (jUst ignore that and press the volume up button)
And Kies 3 will automaticly unroot your phone, flash the new 4.3 update and flash the new bootloader too.
!!!***WATCH OUT! DO A BACK UP OF YOUR INTERNAL MEMORY BECAUSE YOU ARE GOING TO LOSE EVERYTHING***!!!
And after you just have to wait.... Kies 3 will download automaticly 4.3 Firmware and flash it on your phone.
Make shure that your battery is charged at least at 30% before doing that.
And after enjoy your phone unrooted and on stock rom and after you will be still able to update your phone for futurer update availble.
Tell me if it worked for you after!

[Q&A] [HOWTO][TAR][OUDHS] THE ODIN THREAD :: Return to stock, fix soft brick :: 5/7/

[Q&A] [HOWTO][TAR][OUDHS] THE ODIN THREAD :: Return to stock, fix soft brick :: 5/7/
Q&A for [HOWTO][TAR][OUDHS] THE ODIN THREAD :: Return to stock, fix soft brick :: 5/7/13 MDL
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [HOWTO][TAR][OUDHS] THE ODIN THREAD :: Return to stock, fix soft brick :: 5/7/13 MDL. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

i did all this to my s4 but now when i boot it, says Kernel Is Not Seandroid Enforcing, Set Warranty Bit
also when i booted the phone the wifi does not work. could you help with this problem?

Samsung Galaxy S4
Is This ''UVUAMDL Official TAR'' for Samsung Galaxy S4?

Ayaz Gill said:
Is This ''UVUAMDL Official TAR'' for Samsung Galaxy S4?
Click to expand...
Click to collapse
Yes

UPDATE: I fixed the issue while posting this, the solution is included. I am hoping by posting this it may help someone having the same problem, because I spent hours and days trying to solve the issue. Sorry the post is so long.
This is my first post.. I am in desperate need of help!
I have searched everywhere, and cannot find any answers really.
I rooted my M919 at one point, and I could not receive OTA updates.
I do not know if it was rooted when I tried to update it with Odin though.
I was in a hurry (I know BIG mistake) and I never wiped my phone or anything before trying to flash the phone.
I think the phone may not be working because I may have not used triangle away before, but I am not sure if I ever used it. I did the root a long time ago.
I have tried changing USB cords, computers, drivers, md5 files, different Odin versions, flashing PIT file, you name it, I have probably tried it
When I boot the phone the currupt recovery screen shows up. Kies will not recognize the phone.
In the left corner it says:
ODIN MODE
...SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
I can still access "downloading" mode, and it says the same as above.
Odin gives me different errors depending on the file I am attempting to flash
The reason I tried flashing the PIT file is because it would sometimes say
I am not completely sure what update I was using before this all happened, but I think it may have been this one, unrooted?:
CF-Auto-Root-jfltetmo-jfltetmo-sghm919.tar.md5
Error codes are as follows:
While flashing 4.4.4 (Odin 3.10)
M919UVUFNH7_M919TMBFNH7_M919UVUFNH7_HOME.tar.md5
JFLTE_USA_TMO_16G.pit
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUFNH7_M919TMBFNH7_M919UVUFNH7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Recovery File I found (Odin 3.09)
JFLTE_USA_TMO_16G.pit
openrecovery-twrp-2.8.0.1-jfltetmo.tar
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Recovery File I found (Odin 3.09)
JFLTE_USA_TMO_16G.pit
openrecovery-twrp-2.8.0.1-jfltetmo.tar
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
One time I tried using this and it passed!!!
This ONLY works on 3.07 to my knowledge though. It fails on every other Odin
Recovery File I found (Odin 3.07)
JFLTE_USA_TMO_16G.pit
openrecovery-twrp-2.8.0.1-jfltetmo.tar
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
The screen is now frozen on the "Samsung Galaxy S4" screen and just shuts off if trying to boot into recovery mode.
If plugged into USB while trying to boot into recovery it launches the recovery file I just flashed!
I went back into download mode, and plugged the phone back in.
I opened Odin 3.07 again, since I had success with the recovery file.
I tried flashing 4.4.4 again M919UVUFNH7_M919TMBFNH7_M919UVUFNH7_HOME.tar.md5
and it failed while only having Auto Reboot checked. I tried launching it with Auto Reboot AND F Reset Time, and it worked!! Hope this helps someone!!

Hi DarkMenace - would it be possible for you to send me signed M919 PIT file as well? Thanks

shaqto said:
Hi DarkMenace - would it be possible for you to send me signed M919 PIT file as well? Thanks
Click to expand...
Click to collapse
Replied to your email. Not sure if I still have it but I may be able to find it if you say it's not there.

alright i did a no no... I tried flashing back to stock odin when my phone was encrypted .. now its softbricked.
everytime i try to flash the stock odin, it always fails at system.img ext4. Need some help guys, its been softbricked for a week. I flashed philz touch twrp on it so I do recovery on it. any ideas?

doesnt work
Bricked my s4/but i had twrp installed to fix it

I'm getting a Fail message in Odin over and over. I've downloaded the .zip twice so I don't think it's an issue with a corrupt file... The .dll is in my Odin folder and everything. Pretty confused and today is my last day to send my phone back into T-Mobile before they charge me.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

asmth00 said:
I'm getting a Fail message in Odin over and over. I've downloaded the .zip twice so I don't think it's an issue with a corrupt file... The .dll is in my Odin folder and everything. Pretty confused and today is my last day to send my phone back into T-Mobile before they charge me.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
What version Bootloader/Modems do you have now on the phone? If the version you have now has Knox, then you can't downgrade to MDL.
If you are not sure, you can use this free app: https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en
If the version is MK2 or newer, you can't downgrade to MDL.
You can find newer firmwares either on the SamMobile.com site, or on this thread: http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Rob

<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!

In odin, it says 0:[COM4] on the top left
You have 0:[COM3] in your screenshot
Is there a problem or something?Or is it fine?

<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SGH-M919-UVUAMDB-k0nane.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
I get this when i click start
i have a gt-1905 softbricked
please help me

AziNoapte said:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SGH-M919-UVUAMDB-k0nane.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
I get this when i click start
i have a gt-1905 softbricked
please help me
Click to expand...
Click to collapse
If you have a GT-1905 (which I can't find), you shouldn't be trying to flash FIRMWARE for a T-Mobile phone (SGH-M919). That will brick your phone.
If it is an S4, you should be able to take off the back and look under the battery for the model number.
You can flash ROMs, but not firmware between different S4 models. Try finding the FIRMWARE for your phone, and flash that. Also, verify your model, because GT-1905 isn't a Samsung model number.
You can find firmwares here: http://www.sammobile.com/firmwares/
Rob

rlichtefeld said:
If you have a GT-1905 (which I can't find), you shouldn't be trying to flash FIRMWARE for a T-Mobile phone (SGH-M919). That will brick your phone.
If it is an S4, you should be able to take off the back and look under the battery for the model number.
You can flash ROMs, but not firmware between different S4 models. Try finding the FIRMWARE for your phone, and flash that. Also, verify your model, because GT-1905 isn't a Samsung model number.
You can find firmwares here: ------------To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links--------------
Rob
Click to expand...
Click to collapse
i messed up the writing cuz i was scared
I have 19505
I managed to get to 4.2.2 with konane`s guide,got the stock tar but wifi doesnt work on my S4
Can you help me fix it?
Or if it is impossible, can i upgrade to KitKat?

AziNoapte said:
i messed up the writing cuz i was scared
I have 19505
I managed to get to 4.2.2 with konane`s guide,got the stock tar but wifi doesnt work on my S4
Can you help me fix it?
Or if it is impossible, can i upgrade to KitKat?
Click to expand...
Click to collapse
Since this forum is for the T-Mobile variant of the S4, and I'm not familiar with the GT-I9505, I would suggest you try the forum for that model:
http://forum.xda-developers.com/galaxy-s4
If you flashed a T-Mobile tar to your I9505, it is probably because of the radio/modem which was designed for the T-Mo model. There should be links in that forum about no WiFi, etc.
Rob

Hello gang. Got a new circuit board installed two weeks ago. Got the phone back, started setting it up, and after about an hour the touchscreen quit working. >8\
I emailed the shop and they said "could be because you're rooted."
Smelled like bull**** to me, but giving them the benefit of the doubt I figured I'd try to flash back to stock. (Which I WAS actually stock, I had the 4.4.4 OTA update, and then rooted and de-bloated.)
Anyway, I downloaded the "Stock firmware" (SGH-M919-UVUAMDB-k0nane.tar.md5) from post 1 in the title thread and flashed it with Odin.
SEEMS to be working, but oddly enough I have a M919UVUFNH7 baseband and bootloader, but Android 4.4.2, which based on my reading, should be impossible?
Also, like several other posters, I have no wifi.
In any event, I am currently downloading the NH7 firmware from sammobile. Says 2 hours to go.
Will try to flash that with Odin and we'll see what happens. Anyone have suggestions in the meantime?

OK - follow-up. I downloaded M919UVUFNK2_M919TMBFNK2_M919UVUFNK2_HOME.tar and flashed it with Odin. Even though Odin said "Boot" and "Modem" in the flashing process, I still seem to have NH7 bootloaders and baseband.
Help?

Well, never mind. I don't care anymore. Tried to replace my glass and cracked the digitizer. Dunno if I'm down to drop another $120 on this thing now.
$300 purchase price
$100 circuit board replacement
$12 glass
Now $120 for a display? I might just call knock it off with this thing.

Reverting Note 4 Back to Stock Firmare

I've searched high, and I've search low for firmware for my phone (only to be led to sites whose download speed is atrocious).
My phone model is: SM-N910P
I've been searching for the .tar files for the firmware updates. The MD5 is either not valid by Odin's standard or something else.
Can someone point me along to a link of the latest Note 4 Stock Firmware update from a site that doesn't take all day to download from? Thanks Kindly.
P.s. Yes, I have gone through website and threads posting link to the correct firmware but all of them have not been MD5 correct or worked at all.
I'm also experiancing frequent crashes/restarts on the phone.
I got this phone from a family friend and its been acting weird in ways that are outside my comphrenension. It's rooted and they need it to factory state but all theses errors, problems, slow downloads, are making it near impossible.

Try downloading stock tar from this thread with your PC. You can and should verify the md5 before flashing in Odin when md5 is provided.
http://forum.xda-developers.com/showthread.php?p=63868221
Sent from my SM-N930P using Tapatalk

I flashed the file you linked to and this is what i got in Odin
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin engine v(ID:3.1101)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> aboot.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> sbl1.mbn
<ID:0/009> rpm.mbn
<ID:0/009> tz.mbn
<ID:0/009> sdi.mbn
<ID:0/009> NON-HLOS.bin
<ID:0/009> boot.img
<ID:0/009> recovery.img
<ID:0/009> system.img.ext4
<ID:0/009> FAIL! (Write)
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

gordonfrohman said:
I flashed the file you linked to and this is what i got in Odin
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
Checking MD5 finished Sucessfully..
Leave CS..
Odin engine v(ID:3.1101)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
aboot.mbn
NAND Write Start!!
sbl1.mbn
rpm.mbn
tz.mbn
sdi.mbn
NON-HLOS.bin
boot.img
recovery.img
system.img.ext4
FAIL! (Write)
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Questions:
Which stock tar did you flash? (see end of this post)
Does the phone frequently reboot or boot to download mode (reporting) failure to normal boot? Any eMMC failures reported?
Things to check or try if non applicable:
Factory reset in stock recovery if no OS is installed. If you can boot OS, make sure that Settings/Security/reactivation lock is disabled and enable developer mode and enable USB debugging.
Verify correct Samsung driver installed on PC or uninstall and reinstall from Samsung support for Note 4.
Use original Samsung Note 4 cable or replace. A good quality USB data cable should work but if replacing, use OEM replacement.
Run Odin in administrative mode. Try the suggested Odin version (3.10.7 or 3.10.6) or latest version from here: http://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
(Odd reported issues sometimes result in one of these reported as successful where various others weren't).
Try another USB port, cable or PC
Edit: All KIES and Smart Switch sessions should be killed prior to starting Odin session.
Do not Odin older stock tars; usable stock tars start at OG5 and up.
Sent from my SM-N930P using Tapatalk

T805 LTE Update from 5.0 to 6.0 FAIL - Stock ROM wrong?

Hi @all,
I experience an update issue recently. Have a T805 LTE with Android 5.0.2 (rootet, running with original firmware/no mods) and want to update to 6.0.1 Marshmallow. Updating regularly wasnt possible cause of root, so I´m with flashing Odin.
I got myself both official 6.0.1 stock roms for Vodafone Germany from Sammobile and tried 3 Versions of Odin, but still Odin gives me this message, which might rely to a wrong firmware version as mentioned in another forum:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T805XXU1CPH5_T805VFG1CPH1_T805XXU1CPH8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My current 5.0.2 Version is T805XXU1BOC1 / LRX22G.T805XXU1BOCC
(T805XXU1BOCC_T805OXA1BOC4_T805XXU1BOC1_HOME.tar)
and I tried the two available 6.0.1 stock roms
T805XXU1CPL1_T805VFG1CPL1_T805XXU1CPL1_HOME.tar
T805XXU1CPH5_T805VFG1CPH1_T805XXU1CPH8_HOME.tar
Before I went to download mode I did a factory reset with TWRP, and before that I did a backup with Titanium (but not sure if that went properly). I still have the original 5.0.2 firmware, if everything fails...
Would really appreciate any kind of advice what to do now, am I doing something wrong or is there maybe a special trick (like this PIT thing or something)?
*sigh* manymany thx for your knowledge