Disclaimer:
I'm not liable to any demage to your device, including Knox. The information here is as good as I know, there is no guarantee.
(If you like to provide extra information or have a correction, I'll add it to the OP)
>>I'm searching for more full repair firmwares (Containing, PIT, Bootloader, etc. seperated), if anyone could send me the files for I9195 and I9192 etc. i'd upload them too, please help and help others.<<
There are several types of a brick:
Bootloop (usually possible to unbrick)
Stuck at splash screen (a bit harder but still usually possible)
Hardbrick (black screen and nothing works) (there is also a possible solution but it could also mean the end)
Full brick (black screen, nothing works, even the hardbrick method doesn't work. solution could be using a JTAG)
How to unbrick a bootloop and stuck at splash screen brick
Download one of the repair firmwares from here
I9195 Here
Thanks a lot for providing the I9195 files to: @b0g
PIT file:
https://drive.google.com/file/d/0Bx2R0nz6jh17bllKenctWnVsWkE/edit?usp=sharing
Other files:
https://drive.google.com/file/d/0Bx2R0nz6jh17aEVHMHkwLVRjWVE/edit?usp=sharing
###########################################################################################
- Unzip/unrar the files
- Install usb drivers and use the Odin program
- Put the files like the following:
(file names starting with: )
Bootloader (BL) > BOOTLOADER...
PDA (AP) > CODE...
PHONE (CP) > MODEM...
CSC > CSC...
PIT > CSB...
- Make sure your device has enough charge 40% is recommended
- Enter download mode (press volume down + home + power button in the booting process for around 20 seconds)
- connect your device (Odin should say "Added")
- Click start (do NOT disconnect your device or restart your computer in the flashing process, this could make things worse)
- Wait until the phone has fully reset and enter the recovery
- Do a "Factory reset" and "Wipe cache"
- Reboot
- Done
How to unbrick a Hardbricked phone
- Buy a USB-JIG online
- Make sure that the devices battery has charged (even if it doesn't show charging animation)
- Remove your battery
- Plug the USB-JIG inside your phone
- Wait 3 minutes and put the battery back inside
- Wait 40 seconds and the "download mode" screen should appear
- Follow the steps like in the "Bootloop and stuck at splashscreen guide" as above (note: you don't have to enter download mode because using the JIG it should enter it automatically)
Credits:
Me
@b0g
reserved
edited
I9195 mirror at Google drive added
Huge thanks go to @b0g for providing the files for I9195! :good:
hi.
i search a solution repair my s4 mini for hours. tried many ways on this forum and others, but nothing works. so i found this and use the data follow the steps above to ressurrect my phone of bootloop and stuck.
odin flashs correctly i think, but after the reset the phone stucks in "recovery booting..."
i checked autoreboot and re partitition, unchecked f reset time. the odin log says everthing ok:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_OXA_I9195OXABML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> persist.img.ext4
<ID:0/003> persdata.img.ext4
<ID:0/003> NON-HLOS.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
what can i do, please help?
skortax said:
hi.
i search a solution repair my s4 mini for hours. tried many ways on this forum and others, but nothing works. so i found this and use the data follow the steps above to ressurrect my phone of bootloop and stuck.
odin flashs correctly i think, but after the reset the phone stucks in "recovery booting..."
i checked autoreboot and re partitition, unchecked f reset time. the odin log says everthing ok:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_OXA_I9195OXABML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> persist.img.ext4
<ID:0/003> persdata.img.ext4
<ID:0/003> NON-HLOS.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
what can i do, please help?
Click to expand...
Click to collapse
try flashing twrp recovery and wipe all then (despite external sd)
also try flashing with f reset time enabled...
thanks for the quick help. flashed twrp and it boots in recovery, but full wipe doesnt run, so i wiped manually - unfortunately i get bluescreen and i am again at the beginning.
every method i tried ends with the same result: bluescreen, blackscreen, greenscreen and every other existing screen, in every possible loop or odin stuck during the flash process
i think the problem lies deeper and can only be solved with jtag, if it is not an hardware error. what do you think?
Hi I'm having a similar issue with my i9195 getting stuck on boot screen. I think mine has something todo with the new battery i got for it, as the new one only has 3 pins and the old has 4?
one way i found of being able to boot my phone was to take out the battery plug the charger in then put the battery back in once the green battery icon shows that it is charging hold the power until it vibrates and it should (it does for me) start up, i was also able to get into recovery using the above method by holding the home and volume up as normal.
Thanks for this, I will probably use it in near future.
Please someone has the i9192???
Aronuser said:
....
I9195 Here
Thanks a lot for providing the I9195 files to: @b0g
PIT file:
https://drive.google.com/file/d/0Bx2R0nz6jh17bllKenctWnVsWkE/edit?usp=sharing
Other files:
https://drive.google.com/file/d/0Bx2R0nz6jh17aEVHMHkwLVRjWVE/edit?usp=sharing
###########################################################################################
- Unzip/unrar the files
- Install usb drivers and use the Odin program
- Put the files like the following:
(file names starting with: )
Bootloader (BL) > BOOTLOADER...
PDA (AP) > CODE...
PHONE (CP) > MODEM...
CSC > CSC...
PIT > CSB...
- Make sure your device has enough charge 40% is recommended
- Enter download mode (press volume down + home + power button in the booting process for around 20 seconds)
- connect your device (Odin should say "Added")
- Click start (do NOT disconnect your device or restart your computer in the flashing process, this could make things worse)
- Wait until the phone has fully reset and enter the recovery
- Do a "Factory reset" and "Wipe cache"
- Reboot
- Done
.....
Click to expand...
Click to collapse
hi !
can i use this part for to try to downgrade a KK firmware to JB ???!!!
have to check "re-partition" ???
Loulou-13 said:
hi !
can i use this part for to try to downgrade a KK firmware to JB ???!!!
have to check "re-partition" ???
Click to expand...
Click to collapse
yes check re partition, ah and it's not sure yet if it's possible to downgrade from KK i wanna know myself please tell me the result if you know it
yes ,i think i will try it , but i'm "nervious" with re-partition and pit ! i'm a little afraid ...
i would have prefered an advise to a person"spécialist" who know Samsung very well ...... before testing with this flash .
but i know "re-partition" and Odin (I have already had olds Samsungs )
it's principaly the **** of **** of ****** of HELL "Knox" who scares me ...
The pit here is REALLY the good ???
There are devises who have good(s) method(s) for to downgrade , there are other that it's really impossible ..... but for the S4-mini ,nobody have done expérimenations about ,no tutorials ...etc ...
everybody flash as one file .tar now ...
EDIT !
maybe the master @arco68 can answer to this problem ???!!!
... no idea ?!
Hello, can you please help me? I have problems with random restarting of my i9195 S4 Mini (Vodafone). I tried to flash another official ROM, but this problem remains. When I try flash back original stock ROM (or any other ROM - with root or without root), the results are still same - FAIL message in ODIN after aboot.mbn file.
I tried this guide, but again, everything was ended with fail message (check the attached log).
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_OXA_I9195OXABML4_2340422_REV01_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can you please help me and tell me what I can do if I want to put back any stock ROM? I am going crazy with the fail message which shows me in every try. Checked with Odin 3.09, 3.07, 1.83 and still no success.
jerrry said:
Hello, can you please help me? I have problems with random restarting of my i9195 S4 Mini (Vodafone). I tried to flash another official ROM, but this problem remains. When I try flash back original stock ROM (or any other ROM - with root or without root), the results are still same - FAIL message in ODIN after aboot.mbn file.
Can you please help me and tell me what I can do if I want to put back any stock ROM? I am going crazy with the fail message which shows me in every try. Checked with Odin 3.09, 3.07, 1.83 and still no success.
Click to expand...
Click to collapse
Can you tell what is the text in download mode screen? If the last 2 lines say BOOTLOADER SW REV : 2, then you have latest bootloader and IT IS IMPOSSIBLE TO DOWNGRADE.
sasank360 said:
Can you tell what is the text in download mode screen? If the last 2 lines say BOOTLOADER SW REV : 2, then you have latest bootloader and IT IS IMPOSSIBLE TO DOWNGRADE.
Click to expand...
Click to collapse
Thank you for reply. Yes, I have Bootloader AP SWREV: 2. But what can I do if I want to change actual ROM which is flashed in device? I would like to get back original Vodafone ROM (stock), but I can't do anything (flash same ROM which is now in device, flash Vodafone ROM, flash custom ROM).
jerrry said:
Hello, can you please help me? I have problems with random restarting of my i9195 S4 Mini (Vodafone). I tried to flash another official ROM, but this problem remains. When I try flash back original stock ROM (or any other ROM - with root or without root), the results are still same - FAIL message in ODIN after aboot.mbn file.
I tried this guide, but again, everything was ended with fail message (check the attached log).
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_OXA_I9195OXABML4_2340422_REV01_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can you please help me and tell me what I can do if I want to put back any stock ROM? I am going crazy with the fail message which shows me in every try. Checked with Odin 3.09, 3.07, 1.83 and still no success.
Click to expand...
Click to collapse
I had the same issue (aboot.mbn failing and finally I managed to fix it by flashing I9195XXUCNE6_I9195OXACNE6_DBT with Odin 3.09. Downloaded the firmware from sammobile (http://www.sammobile.com/firmwares/3/?confirm=31540). Had to wipe data/cache after flashing the ROM. Not the ROM I wanted, but at least now I have a working S4 mini again.
jerrry said:
Thank you for reply. Yes, I have Bootloader AP SWREV: 2. But what can I do if I want to change actual ROM which is flashed in device? I would like to get back original Vodafone ROM (stock), but I can't do anything (flash same ROM which is now in device, flash Vodafone ROM, flash custom ROM).
Click to expand...
Click to collapse
skip the modem file and the bootloader file at flashing and you should be fine
Aronuser said:
skip the modem file and the bootloader file at flashing and you should be fine
Click to expand...
Click to collapse
How can I skip these files? Because in ODIN I am selecting just only one file.
Related
Now I can’t install firmware or go into recovery mode but I can still get to download screen.
okizen said:
Now I can’t install firmware or go into recovery mode but I can still get to download screen.
Click to expand...
Click to collapse
Cant you go to the download screen and set ODIN away again?
Thats how I did it.
trubster said:
Cant you go to the download screen and set ODIN away again?
Thats how I did it.
Click to expand...
Click to collapse
Hi trubster, I've reset odin and my phone into download mode several times. The odin update process starts off ok but always fails when it reaches 'SYSTEM'.
okizen said:
Hi trubster, I've reset odin and my phone into download mode several times. The odin update process starts off ok but always fails when it reaches 'SYSTEM'.
Click to expand...
Click to collapse
What message is ODIN giving in the white text box?
have you tried re-downloading the ROM? I used the MEGA link and it worked fine.
N9005XXUENA6_N9005OXXENA5_XEO.zip is the one you need if it is for the N9005, you need the stock 4.4.2 FW before you can put CFW on
trubster said:
What message is ODIN giving in the white text box?
have you tried re-downloading the ROM? I used the MEGA link and it worked fine.
N9005XXUENA6_N9005OXXENA5_XEO.zip is the one you need if it is for the N9005, you need the stock 4.4.2 FW before you can put CFW on
Click to expand...
Click to collapse
These are the messages I get from odin (from the beginning).
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
I should also mention that I has tripped my Knox to 0x1as I've always got on without one but I doubt if that would be the cause.
That file seems to be different, are you using a N9005?
https://mega.co.nz/#!jZYkyY5a!HfiJlXRgp_ZGWoQncFNWeEn5FnY_0i9iFb23EGfg2Nk
Thats the file I used first, put it in the PDA or AP box on odin and click start.
Should have no problems with it as it is an "Official" Sammy Rom
If you have a Hong Kong note you need to have a read around, If not, grab XEO firmware flash via odin 1.85 or 3.07
trubster said:
That file seems to be different, are you using a N9005?
https://mega.co.nz/#!jZYkyY5a!HfiJlXRgp_ZGWoQncFNWeEn5FnY_0i9iFb23EGfg2Nk
Thats the file I used first, put it in the PDA or AP box on odin and click start.
Should have no problems with it as it is an "Official" Sammy Rom
Click to expand...
Click to collapse
Sorry trubster, I missed out a part of the message in odin.
This is the FULL message in it's entirety.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
I've also tried the firmware from your link but unfortunately the results were the same.
I didn't experience this on my N9005 while updating, but I experienced this before on my S3, it was due to corrupted firmware file.
Please help me!!! Please!!!
okizen said:
sorry trubster, i missed out a part of the message in odin.
This is the full message in it's entirety.
<osm> enter cs for md5..
<osm> check md5.. Do not unplug the cable..
<osm> please wait..
<osm> n9005xxuena6_n9005oxxena5_n9005xxuena2_home.tar.md5 is valid.
<osm> checking md5 finished sucessfully..
<osm> leave cs..
<id:0/003> added!!
<id:0/003> odin v.3 engine (id:3)..
<id:0/003> file analysis..
<id:0/003> setupconnection..
<id:0/003> initialzation..
<id:0/003> get pit for mapping..
<id:0/003> firmware update start..
<id:0/003> aboot.mbn
<id:0/003> nand write start!!
<id:0/003> sbl1.mbn
<id:0/003> rpm.mbn
<id:0/003> tz.mbn
<id:0/003> sdi.mbn
<id:0/003> non-hlos.bin
<id:0/003> boot.img
<id:0/003> recovery.img
<id:0/003> system.img.ext4
<id:0/003> complete(write) operation failed.
<osm> all threads completed. (succeed 0 / failed 1)
<id:0/003> removed!!
<id:0/003> added!!
<id:0/003> removed!!
I've also tried the firmware from your link but unfortunately the results were the same.
Click to expand...
Click to collapse
i am also having this problem
it seems i cant flash other firmware other than poland fw...
I want ro revert back to ksa firmware or anygood fw since poland svoice isnt working fine<< sorry for bag english
please help me
i have flash my fw with kk italy, and spain but to luck,,, still having the same result... Failed!!!
Please please
u have to download hungry firmwar from sammobiles.com..it will b ok.and tick update boot loader must
clowrid1128 said:
i am also having this problem
it seems i cant flash other firmware other than poland fw...
Click to expand...
Click to collapse
I had the same problem... Just try to flash with this version of ODIN:
https://mega.co.nz/#!RVVXSYiY!6lynzTh-II8o8rvfYkdZzrYa_7m2F-CKgtItMZA66v4
I had the same problem today.The solution is here http://www.cultofandroid.com/53963/save-galaxy-note-3-failed-kitkat-update-odin-tip/
Now i am with german kit kat (DBT) and everything is ok !!!!!! :good::good::good:
Help me (SAM SM-N900S)
<ID:0/023> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N900SKSU0GPI1_CL9178490_QB10835717_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_N900SKSU0GPI1_CL9178490_QB10835717_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_SKT_N900SSKT0GPI1_CL9178490_QB10835717_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N900SKSU0GPI1_CL9178490_QB10835717_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/023> Removed!!
<ID:0/028> Added!!
<ID:0/028> Odin engine v(ID:3.1005)..
<ID:0/028> File analysis..
<ID:0/028> SetupConnection..
<ID:0/028> Initialzation..
<ID:0/028> Set PIT file..
<ID:0/028> DO NOT TURN OFF TARGET!!
<ID:0/028> FAIL!
<ID:0/028>
<ID:0/028> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/028> Removed!!
<ID:0/028> Added!!
<ID:0/028> Odin engine v(ID:3.1005)..
<ID:0/028> File analysis..
<ID:0/028> SetupConnection..
<ID:0/028> Initialzation..
<ID:0/028> Set PIT file..
<ID:0/028> DO NOT TURN OFF TARGET!!
<ID:0/028> FAIL!
<ID:0/028>
<ID:0/028> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/028> Removed!!
:crying:
Why are you flashing Kitkat ??
What phone have you got and what have you done before .
PIT showing as no partition fail .
I recently flashed my phone with odin, but now when i try to turn it on, it just turns a brighter grey colour and stays like that.
Is there a way to stop this?
Edit: I think i flashed the wrong firmware, Does anyone know any advice on how to get my phone to work?
Can you go Download Mode? if not try switching new batteries, mostly deadboot problems 'cause by battery
I can go into download mode but when i try to do another odin flash it says this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_S5360_XXMI1.tar.md5 is valid.
<OSM> MODEM_S5360_XXMG1.tar.md5 is valid.
<OSM> CSC_S5360_XEUMI1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
try downloading another firmware your region's and make sure the USB cord is fine
when you've extracted the firmware package...
CSC_S5360_XEUMI1.tar.md5 is different from others...
I've recently tried to flash a 5.0 stock rom via Odin and it failed, and I now have a bricked phone that has this warning:
PHONE-----YELLOW TRIANGLE----- COMPUTER
'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
I tried to flash the latest KNOX bootloader roms via ODIN to boot up the phone, however....
ODIN keeps hanging on the "system" flashing command and goes to a red "fail". It won't start flashing "system.img.ext4.... etc"
I've tried all versions of ODIN and all version of 5.0
Do you guys know why ODIN keeps failing at flashing 'system.img.ext4' ?
Any advice would be greatly appreciated, thanks!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin engine v(ID:3.1100)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Set PIT file..
<ID:0/012> DO NOT TURN OFF TARGET!!
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> SingleDownload.
<ID:0/012> aboot.mbn
<ID:0/012> NAND Write Start!!
<ID:0/012> sbl1.mbn
<ID:0/012> rpm.mbn
<ID:0/012> tz.mbn
<ID:0/012> hyp.mbn
<ID:0/012> NON-HLOS.bin
<ID:0/012> sec.dat
<ID:0/012> boot.img
<ID:0/012> persdata.img.ext4
<ID:0/012> persist.img.ext4
<ID:0/012> recovery.img
<ID:0/012> system.img.ext4
<ID:0/012> FAIL! (Erase)
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/012> Removed!!
What is your phones model? Did you try a different country firmware? Which Android is your phone completely on?
Corrupted EMMC I guess
Hi,
i'm trying to help a friend about his phone that got into bootloop.
i asked him if he tried to do something, but he say no.
i didn't ask my fried what android version he has because i'm not sure that he know what is this, but i ask him if this can help.
this the state, it's display the pic/logo and reboot:
http://oi64.tinypic.com/k538s8.jpg
- i tried to flash stock firmware with odin and download every firmware file from here:
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930V/
(yes, downloaded them all!) non of them was working; this whats i see on phone in download mode:
http://oi66.tinypic.com/1z1u2i1.jpg
this is the odin version 3.13 output:
<ID:0/004> 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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 5238 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> emmc_appsboot.mbn
<ID:0/004> lksecapp.mbn
<ID:0/004> xbl.elf
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
Click to expand...
Click to collapse
- i entered into Maintenance Boot Mode and tried 'factory mode' or any Debug mode or 'safe mode' and nothing, phone just reset and going back to bootloop.
http://oi67.tinypic.com/2lmxf09.jpg
- other thing i tried was to use Verizon Wireless Software Upgrade Assistant software;
looks very promising; phone was detected and firmware was downloaded:
AP_G930VVRS8CRK2_CL14274519_QB20800341_REV02_user_low_ship_MULTI_CERT_meta.tar.md5
BL_G930VVRS8CRK2_CL14274519_QB20800341_REV02_user_low_ship_MULTI_CERT.tar.md5
CP_G930VVRS8CRK2_CP11296771_CL14274519_QB20800341_REV02_user_low_ship_MULTI_CERT.tar.md5
CSC_VZW_G930VVZW8CRK2_CL14274519_QB20800341_REV02_user_low_ship_MULTI_CERT.tar.md5
HOME_CSC_VZW_G930VVZW8CRK2_CL14274519_QB20800341_REV02_user_low_ship_MULTI_CERT.tar.md5
but it didn't flash, it's failed, so i copied the files and tried with odin and it was the same - failed.
- i tried with older versions of odin, but they display "unsupported dev" error on the phone.
- i tried with different cable and computer, one at work and other at home - no luck.
i don't know what else to try, after trying to flash 27 firmwares maybe i missing something?
i stayed up all night for this.
any help will be welcomed.
same issue
i can get the newest firmware to flash with odin 3.14 but same issue. only description difference is it seems to freeze then reboot. i have seen it progress a little further with reboots (over time) all the way to the setup screen then freeze and reboot or freeze altogether. been at this for like a week now. driving me nuts please help!! i think im going to try the s7 edge firmware see what that does.
Same exact issue. Hope someone has a solution.
Just have to say. Know the frustration. I have done the same thing with a dozen firmwares. Not as many as you and can not find the answer. If I do i will let you know.
One thing
So I finally got this file to work and pass G930VVRS9CSB1_G930VVZW9CSB1_VZW in odin 3.13. It's still rebooting though. Argh.
Hi all,
after a long wait Samsung released the first update to Pie for Tab S3 SM-T825 on december 2019 (ITV-T825XXU3CSK2-20191226114137); I hoped it would fix most issues I experienced since I had upgraded from Oreo, but it's still sluggish, battery life is much worse and I don't find anything better than Oreo in this release... the worst Android build I've ever seen!
I finally decided to downgrade, so I downloaded the latest Oreo version available for my region (ITV-T825XXU3BSD1-20190510143544) and Odin v3.13.3.
AFAIK everything should work fine because the bootloader for both ROMs is the same version (XXU3); I followed the standard instructions available on Sammobile: launched Odin, selected BL, AP, CP, CSC and hit Start.
The flashing process starts without problems but it fails after a few minutes while the device is downloading system.img. Tried several times but to no avail.
The device had usb debug on, in download mode I see FRP lock on, OEM lock on.
Can anyone please help? Below you can find the Odin log.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/005> Added!!
<ID:0/005> Odin engine v(ID:3.1303)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 5116 M
<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> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> emmc_appsboot.mbn
<ID:0/005> lksecapp.mbn
<ID:0/005> xbl.elf
<ID:0/005> tz.mbn
<ID:0/005> hyp.mbn
<ID:0/005> devcfg.mbn
<ID:0/005> pmic.elf
<ID:0/005> rpm.mbn
<ID:0/005> cmnlib.mbn
<ID:0/005> keymaster.mbn
<ID:0/005> apdp.mbn
<ID:0/005> msadp.mbn
<ID:0/005> cmnlib64.mbn
<ID:0/005> sec.dat
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Never mind, it finally worked!
I put the device in recovery mode, wiped cache and user data, then repeated the flash process with Odin and everything went fine.
Hello , can you please share the firmware , it will be a a good will as it takes ages to download from sam firmware.com , you can give me a google drive link , god bless !