[UNBRICK Guide][for Bootloader v1 jb only][I9195]How to unbrick your device

sasank360

Senior Member
Feb 27, 2012
692
329
0
Hyderabad
I tried your downgrade thread and it didn't work
I tried flashing all of the files at once, it didn't work. I tried flashing the files one by one and the only fail on ODIN was caused by the PDA (AP) file. I am guessing it is because you can't just downgrade from 4.4.2 to 4.2.2; after that my phone bricked but I unbricked it by flashing the original 4.4.2 again .

Well, the error I got when trying to flash your files was:
Fused 2 > Binary 1 (or something like that).

Any help?
Thanks!
YOU CANNOT DOWNGRADE TO STOCK JELLYBEAN FROM STOCK KITKAT.
""fused 2 > binary 1"" means you have knox bootloader 2 and you are trying to replace that with knox bootloader 1. Which is impossible.
The only alternative is to flash stock jellybean firmware that has knox 2 bootloader. This link gives one such firmware for I9195. I am not sure about I9190 or I9192.
http://www.sammobile.com/firmwares/download/30561/I9195UBUBNE2_I9195ZTOBNE2_ZTO.zip/ This link gives you the only jellybean firmware that has knox 2 bootloader.
If jellybean is what you need... flash that. Good luck. :)

---------- Post added at 06:30 AM ---------- Previous post was at 06:27 AM ----------

Hi All!

I have installed I9195XXUCNK1 (maybe the latest ROM) to my phone and after that install the KNOX started to count!
I only would like to know, can I go back to 4.2.2 with this 4.4.2 ROM without brick my phone?
Or at first, Do I have to folow this thread of #1 post to avoid the trouble? (flashing this file)

My final purpose is to unlock my sim, but I don't know yet, is it possible on flashed KitKat ROM by Odin? (I9195XXUCNK1) :eek:
You cannot go back to stock jellybean now. But I believe you can unlock your sim even while on kitkat. Ask around and search for the method to unlock sim.
By the way... WARNING :: DO NOT USE THIS METHOD TO DOWNGRADE FROM STOCK 4.4.2 TO STOCK 4.2.2. IT WILL NOT WORK. IT HARD BRICKS YOUR PHONE.
 
  • Like
Reactions: csicsa

caraneday

Member
Oct 12, 2014
14
1
0
YOU CANNOT DOWNGRADE TO STOCK JELLYBEAN FROM STOCK KITKAT.
""fused 2 > binary 1"" means you have knox bootloader 2 and you are trying to replace that with knox bootloader 1. Which is impossible.
The only alternative is to flash stock jellybean firmware that has knox 2 bootloader. This link gives one such firmware for I9195. I am not sure about I9190 or I9192.
http://www.sammobile.com/firmwares/download/30561/I9195UBUBNE2_I9195ZTOBNE2_ZTO.zip/ This link gives you the only jellybean firmware that has knox 2 bootloader.
If jellybean is what you need... flash that. Good luck. :)


Just flash? No tricks?

Thanks.
-C
 

caraneday

Member
Oct 12, 2014
14
1
0
Yes. The brazil jellybean firmware i linked must be flashed as PDA / AP using odin.
In options check auto reboot and force reset time. And leave every other thing unchecked.
NO NEED FOR PIT FILE. DO NOT USE PIT FILE. Good luck.
Ok, I'll try! Is there any option to "downgrade" the bootloader from 2 to 1?

Thanks.
-C
 

frogger13

New member
May 15, 2010
2
0
0
hi guys...

i have a bricked i9195. i've tryd so many goolge links, and now im finally here.

the problem is, that my phone isnt starting. no bootscreen. when i connect it to my computer, there is a new divice in the device manager -> QHSUSB_DLOAD. ive already found a windows driver for this -> Qualcomm HS-USB QDLoader 9008

to try all these tips with flashing new firmware need to see the device with odin. but this is my problem. no matter what i do, odin have no connection to my phone.

any ideas ?
krgds
reiner
 

Pante90

New member
Feb 9, 2015
1
0
0
hi guys...

i have a bricked i9195. i've tryd so many goolge links, and now im finally here.

the problem is, that my phone isnt starting. no bootscreen. when i connect it to my computer, there is a new divice in the device manager -> QHSUSB_DLOAD. ive already found a windows driver for this -> Qualcomm HS-USB QDLoader 9008

to try all these tips with flashing new firmware need to see the device with odin. but this is my problem. no matter what i do, odin have no connection to my phone.

any ideas ?
krgds
reiner

hi, I'm new to the forum. I also encountered the problem of frogger13. the same conditions, I would understand if you explain someone knows how to retrieve the cell. I with a program called QPST can not see the phone connected via COM. But I do not know how to use the program. Thanks to availability.
 

benjieoral

Member
Mar 23, 2015
8
0
0
24
cebu
somebody can give me dbrick.img i9190 plzzxzz

Help me sir somebody can give brick.IMG i9190 my phone hard brick plzZ help me
almost 1 year my phone was hardbrick:(
 

Adiman423

Member
Aug 9, 2013
8
1
0
London
www.adistechsite.co.uk
Tried to unbrick using this method but no luck so far

Hi Everyone. A bit of backstory:
I have the Galaxy S4 Mini GT-I9195.

I rooted my phone to install Cyanogenmod 10.1.3 and then upgraded to 10.2.1.3 from within the settings menu. Fast forward to last week, I was browsing the web and the phone's screen went black. Thankfully someone that I know had a battery that would fit my phone.

At this point in time I can get into recovery mode (which is CWM recovery), but when I wipe cache or wipe data, the phone just goes back to the reboot loop.

Now, I put my GT-I9195 into download mode and follow the instructions in the first post. After flashing in download mode with the instructions the recovery boots and still shows CWM recovery instead of samsung recovery and when I reboot it's still stuck in the reboot loop with the cyanogenmod boot logo. Here's what my ODIN log showed when I flashed the files:
<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> MODEM_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sbl1.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sbl2.mbn
<ID:0/008> sbl3.mbn
<ID:0/008> aboot.mbn
<ID:0/008> rpm.mbn
<ID:0/008> tz.mbn
<ID:0/008> sbl1.mbn
<ID:0/008> sbl2.mbn
<ID:0/008> sbl3.mbn
<ID:0/008> aboot.mbn
<ID:0/008> rpm.mbn
<ID:0/008> tz.mbn
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img.ext4
<ID:0/008> persist.img.ext4
<ID:0/008> persdata.img.ext4
<ID:0/008> NON-HLOS.bin
<ID:0/008> Transmission Complete..
<ID:0/008> Now Writing.. Please wait about 2 minutes
<ID:0/008> Receive Response from boot-loader
<ID:0/008> NON-HLOS.bin
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Removed!!
<ID:0/008> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

Anyone got a solution?

please reply soon.
 

2010radams

Senior Member
Jan 29, 2013
474
197
73
Workington, Cumbria
yes it should work, make sure to stick to the guide and skip flashing the bootloader file :highfive:
Hello, thanks for the thread. The problem i have is that i am on kitkat with v2 bootloader and the information here is titled v1 bootloader only. Can i use any of the information in the op on a phone with v2 bootloader that is bricked. I have looked everywhere and cant find a guide as detailed as yours but for the v2 bootloader. Thanks in advance for any help
 
Last edited:

xqee

Member
May 7, 2015
8
0
0
Auth

Hello!

I have problem with GT-I9195.
It was hardbricked. I unbricked it with SDcard and debrick.img. Now I have bootloop problem. I put phone to download mode and flash with stock ROM but it has bootloop again and there is No command in Recovery Mode. I tried to install Custom Recovery and still same No Command.

I tried this method:
(file names starting with: )
Bootloader (BL) > BOOTLOADER...
PDA (AP) > CODE...
PHONE (CP) > MODEM...
CSC > CSC...
PIT > CSB...

I get this error:
<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> 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..
<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..
<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> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This is Status in Download mode:
ODIN MODE
PRODUCT NAME: GT-I9195
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
BOOTLOADER AP SWREV: 2
WRITE PROTECTION: Enable

And on FAIL! (Auth) Error
SW REV CHECK FAIL: Fused 2 > Binary 1


Can anyone help me?
 

Aronuser

Senior Member
Mar 1, 2014
1,049
442
0
Berlin
Hello!

I have problem with GT-I9195.
It was hardbricked. I unbricked it with SDcard and debrick.img. Now I have bootloop problem. I put phone to download mode and flash with stock ROM but it has bootloop again and there is No command in Recovery Mode. I tried to install Custom Recovery and still same No Command.

I tried this method:
(file names starting with: )
Bootloader (BL) > BOOTLOADER...
PDA (AP) > CODE...
PHONE (CP) > MODEM...
CSC > CSC...
PIT > CSB...

I get this error:


This is Status in Download mode:
ODIN MODE
PRODUCT NAME: GT-I9195
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
BOOTLOADER AP SWREV: 2
WRITE PROTECTION: Enable

And on FAIL! (Auth) Error
SW REV CHECK FAIL: Fused 2 > Binary 1


Can anyone help me?
For bootloader v1 only jb
 

xqee

Member
May 7, 2015
8
0
0
Where can I get files for Bootloader V2?

And why I have No command in Recovery mode with stock ROM?
 
Last edited:

absmo

New member
May 12, 2015
1
0
0
hi guys...

i have a bricked i9195. i've tryd so many goolge links, and now im finally here.

the problem is, that my phone isnt starting. no bootscreen. when i connect it to my computer, there is a new divice in the device manager -> QHSUSB_DLOAD. ive already found a windows driver for this -> Qualcomm HS-USB QDLoader 9008

to try all these tips with flashing new firmware need to see the device with odin. but this is my problem. no matter what i do, odin have no connection to my phone.

any ideas ?
krgds
reiner
I have exactly the same problem . Did u finally found a good fix for odin to connect to the phone? If so please me know. Thanks!
 

xqee

Member
May 7, 2015
8
0
0
I had same problem. Black screen and that Driver.
Used debrick.img and SDCard. Now I can turn it on but I stuck on bootloop...
You have full guide on this forum.