[Q] Bootloader status locked or unlocked? (Samsung) - Galaxy S 4 Mini Q&A, Help & Troubleshooting

How can I verify if the bootloader is Locked or Unlocked on Samsung Galaxy? S4 mini GT-I9195 (Android 4.4.2 KitKat)
- I have googled after this for few days now and I can't find nothing.
As I see, some old Samsung models (like s3) have the bootloader unlocked and some carriers variants lock the bootloader.
But how about S4 Mini? All that I can find is for other phones like Sony Xperias.
On http://autoroot.chainfire.eu/ I did find this but is not explaining how to unlock or how to check the status of the bootloader:
" UNLOCK BOOTLOADERS
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !" "
On http://wiki.cyanogenmod.org/w/Install_CM_for_serranoltexx
I have found this:
" Samsung devices come with a unique boot mode called Download Mode which is very similar to Fastboot Mode on some devices with unlocked bootloaders."

Can you boot into download mode ?? Power off the phone. Then Press and hold Volume Down , Home and Power/Lock keys @ the same time till device vibrates.
You should get a screen saying "press volume up to continue" and "volume down to restart". Press Volume up and make a note of text on next screen. Come back and report.

ODIN MODE
Product name: GT-I9191
Current Binary: Samsung Official
System Status: Official
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x0
CSB-Config-LSB: 0x30
Bootloader Ap Swaev: 2
Write Protection: Enable
What dose it mean the one from above?
- Current binnary System status official => stock rom/firmware?
- Knox Kernel Lock => ?
- Knox Warranty Void: => Is valid and not trigered
- Csb-Config-Lsb => ?
Bootloader Ap Swaev => ?
Write protection enable => BOOTLOADER LOCKED?

isabelamoisin said:
ODIN MODE
Product name: GT-I9191
Current Binary: Samsung Official
System Status: Official
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x0
CSB-Config-LSB: 0x30
Bootloader Ap Swaev: 2
Write Protection: Enable
What dose it mean the one from above?
- Current binnary System status official => stock rom/firmware?
- Knox Kernel Lock => ?
- Knox Warranty Void: => Is valid and not trigered
- Csb-Config-Lsb => ?
Bootloader Ap Swaev => ?
Write protection enable => BOOTLOADER LOCKED?
Click to expand...
Click to collapse
Isabela,
Our devices Samsung (in general all Samsung devices) don't have locked bootloader. So you/we must only root our devices for flash some custom kernels/ROMs.
Good luck

This is why I am asking. For downgrading the firmware and rooting. Without briking.
>><<
I have used TowelRoot with succes, for having root on the device, but after a factory reset and some updates, TowerRoot is NOT working anymore.
>><<
So, I wish to downgrade to an older firmware/stock rom without (soft) bricking the device.
KingoRoot is also not working, and is asking me if I wish to:
""Kingo will now start to root your device by flashing custom Recovery through Odin Mode, which will
1.Definitely void your WARRANTY (I don't care)
2. Possibily BRICK your phone and lead to boot failure
(I really care as I wish to avoid bricking)"
>><<
Also on chainfire auto root I have found this statement but is not explaining how to unlock or how to check the status of the bootloader:
http://autoroot.chainfire.eu/
" UNLOCK BOOTLOADERS
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !" "
>><<
On http://wiki.cyanogenmod.org/w/Install_CM_for_serranoltexx
I have found this:
" Samsung devices come with a unique boot mode called Download Mode which is very similar to Fastboot Mode on some devices with unlocked bootloaders."
sasank360 said:
Can you boot into download mode ?? Power off the phone. Then Press and hold Volume Down , Home and Power/Lock keys @ the same time till device vibrates.
You should get a screen saying "press volume up to continue" and "volume down to restart". Press Volume up and make a note of text on next screen. Come back and report.
Click to expand...
Click to collapse
R_a_z_v_a_n said:
Isabela,
Our devices Samsung (in general all Samsung devices) don't have locked bootloader. So you/we must only root our devices for flash some custom kernels/ROMs.
Good luck
Click to expand...
Click to collapse

@isabelamoisin
You have latest knox bootloader. It is impossible to downgrade to jellybean 4.2.2
But you can root your device by kingo/towelroot even if u are on latest firmware.
Check this thread ::: http://forum.xda-developers.com/galaxy-s4-mini/general/root-4-4-2-tripping-knox-t2887705
1.) Read instructions carefully
2.) Read instructions carefully
3.) Read comments and replies
4.) Then go ahead with procedure.

Hi, a complete noob here, i have a GT-I9195 here that has been bricked, keeps on rebooting after the samsung logo appears, i have tried flashing the stock rom and got a PASS message from odin, i want to know wether or not the issue is hardware related or bootloader related, thanks in advance, here is the odin log, i'd be really grateful if you could also redirect me to a more useful thread if you think my issue isn't relevant to this one
<ID:0/003> 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/003> Odin engine v(ID:3.1101)..
<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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.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> NON-HLOS.bin
<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!!

WhiTeRaaven said:
Hi, a complete noob here, i have a GT-I9195 here that has been bricked, keeps on rebooting after the samsung logo appears, i have tried flashing the stock rom and got a PASS message from odin, i want to know wether or not the issue is hardware related or bootloader related, thanks in advance, here is the odin log, i'd be really grateful if you could also redirect me to a more useful thread if you think my issue isn't relevant to this one
<ID:0/003> 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/003> Odin engine v(ID:3.1101)..
<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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.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> NON-HLOS.bin
<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!!
Click to expand...
Click to collapse
How large is the file you were booting up with odin?

Razvan said:
Isabela,
Our devices Samsung (in general all Samsung devices) don't have locked bootloader. So you/we must only root our devices for flash some custom kernels/ROMs.
Good luck
Click to expand...
Click to collapse
Sorry to bring this up again. But if we are able to access Download mode, then is the bootloader unlocked?
EDIT: Btw, I have a Samsung Galaxy S3 Korean (SHV-E210K) (by Olleh) and I tried going into Download mode but its all in korean so I didn't understand anything.

Bootloader locked or unlock help me
I have rooted my galaxy A5 Sm-A500G with CF auto root with ODIN in my pc it means that my bootloader is unlock help me

Related

[Q] Help with SPH-L520, PLEASE!

Tried the root method here.
And got the error:
Code:
image size too large!! W:1080, H:1920
display image fail
SECURE FAIL: KERNEL
I panicked, but figured it'd be alright if I just flashed the stock firmware. I re-downloaded the unmodified stock firmware and not I am getting the error
Code:
sw rev check fail fused 3 > binary 2
Odin fails to flash stock at all. It seems to flash it if it's the modified one (the attempt to remove the bootloader) but it then doesn't boot.
If I try to boot phone after flashing stock and failing it says "Firmware upgrade encountered an issue. Please select revoery mode in kies & try again."
What can I do? I want to try re downloading/flashing the PIT file but i can't seem to find a download for that anywhere. Could anyone link me or maybe create a backup pit from their phones I could use?
I have no idea what to do...
Same Issue
I flashed Cyanogenmod and it was working smoothly until I would attempt to load certain apps like Tribal wars or if I was in Game of war, the text would lag after I type a single line of wording then it would jerk up and cause the app to crash. Also, after a few reboots I noticed it automatically uninstalled half of my total apps and I had to redownload them all. I would like to reverse what I did so I installed the stock firmware for my SPH-L520 with this method.
My phone's specs mentioned on Odin Download Mode..
PRODUCT NAME: SPH-L520
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX KERNAL LOCK: 0x0
KNOX WARRENTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
BOOTLOADER AP SWREV: 4
WRITE PROTECTION: ENABLE
I would get the following error after attempting to flash stock firmware..
What it says on Odin3 v3.07..
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L520VPUAMK2_L520SPTAMK2_L520VPUAMK2_HOME.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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
What it says on my phone...
SW REV CHECK FAIL : Fused 4 > Binary 2
Anyone mind shedding some light on this?

[Q] Rooting crashed/phone bricked and odin keeps failing/help please!

I am not new to the rooting scene, however I have a problem that I can't seem to figure out. I've been reading now for the past 2 days, tried several things and still can't get this resolved. I've never had any issues in the past with odin and rooting samsung phones before, including ones with locked bootloaders. However, I've met my match. I tried following the tutorial listed on this site for rooting the samsung note 3 from tmobile. I watched the video and followed along with the files listed here
http://forum.xda-developers.com/note-3-tmobile/#root
My problem is as follows: I tried rooting with odin, installed kies for the usb support but halfway through the root process I get the big RED FAILED! phone's progress bar stops and it hangs. I though this was strange and never encountered this before. I then tried repeating the same process and same results, however this time around I am only able to bring the phone into "odin" mode "download" and not the original stock rom.
At first I was getting the original "the firmware encountered an upgrade issue" and couldn't bypass this unless I opted for download mode. I've tried the same steps to "unbrick" via oden with stock tmobile firmware for this phone and yet it yields the same results, big exclamation failed on odin. I then tried the process with the .pit file to partition that I found online somewhere and that fails too. My note starts up now, but stuck at the samsung galaxy note 3 screen. I've tried several versions of odin, switching usb cables, usb ports and I am unable to root this phone or even get it unbricked! i've read extensively here and can't seem to find a solution to my problem. Can someone PLEASE point me in the right directions?? BTW, I am using a mac with VMWARE, i've never encountered any issues with vmware in the past while running windows 8.
Phone says the following:
Once in download mode my phone says the following:
ODIN MODE
PRODUCT NAME: SW-N900T
CURRENT BINARY: CUSTOM
SYSTEM STATUS: OFFICIAL
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X0
QUALCOM SECUREBOOT: ENAMBLE
RP SWREV: S2, T2, A2, A3 P2
WRITE PROTECTION: ENABLE
UOC START
and I get these results from ODIN:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.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> SingleDownload.
<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)
Please someone help me, I am desperate and I can't think of what to do next.
http://forum.xda-developers.com/showthread.php?t=2677032
TWEAKED N3
BACARDILIMON said:
http://forum.xda-developers.com/showthread.php?t=2677032
TWEAKED N3
Click to expand...
Click to collapse
I can't seem to do this on 2 versions of windows installed on vmware for my mac. Everytime I try odin fails! Is there a way you can help me do this with heimdall on my mac?

[Q] Messud up my I9195, don't know what to do next..

Hi Folks,
I've messed up my S4 mini. I'm going to try to remember what i have done..
First of all, I started with rooting my phone with Odin. After that I've installed Slimbean. Yesterday I thought I saw heaven in this Deodexed rooted rom: http://www.s4miniarchive.com/2014/04/deodexed-and-rooted-stock-for-galaxy-s4-mini.html But it went wrong.
I've copied that rom to my ext SD card and installed this zip with the install .zip function in the CWM Recovery interface. After installing I've rebooted. At the first screen my phone hangs.
After this I've tried to recover my phone with ODIN by using a stock rom I9195XXUBML4_I9195TNLBML1_I9195XXUBML4_HOME.tar.md5 But it hangs at the end of the proces. Below the transscript:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9195XXUBML4_I9195TNLBML1_I9195XXUBML4_HOME.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> 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> rpm.mbn
<ID:0/003> aboot.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> NON-HLOS.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Ext4)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When I'm trying to boot now I got the Annoying message stating: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Unfortunately the recoverymode in Kies doesn't see my phone.
Does anyone out here know a possible workaround?
Hope I can find help here!
Thanks a lot!
Arno (from The Netherlands)
wich firmware you where on begining?
whats your download screen looks like, does it have the word knox on it?
fburgos said:
wich firmware you where on begining?
whats your download screen looks like, does it have the word knox on it?
Click to expand...
Click to collapse
I don't know on which firmware my phone started.
My screen contains the following information:
ODIN MODE
PRODUCT NAME: GT-I9195
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
BOOTLOADER AP SWREV: 1
WRITE PROTECTION: Enable
Am I screwed?
47273 said:
I don't know on which firmware my phone started.
My screen contains the following information:
ODIN MODE
PRODUCT NAME: GT-I9195
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
BOOTLOADER AP SWREV: 1
WRITE PROTECTION: Enable
Am I screwed?
Click to expand...
Click to collapse
No you are not.
Based on your "screen" the computer should detect it . Kies is :silly:, if not try different ports of pc, or other pc. You also can try making a "samsung jig" if all fail (Google it = instructions).
Load the correct latest firmware depending on you back sticker (under the battery) with odin.
Best of luck.
vasiboss said:
No you are not.
Based on your "screen" the computer should detect it . Kies is :silly:, if not try different ports of pc, or other pc. You also can try making a "samsung jig" if all fail (Google it = instructions).
Load the correct latest firmware depending on you back sticker (under the battery) with odin.
Best of luck.
Click to expand...
Click to collapse
It worked! I am back on a offical Samsung ROM and for now thats good enough.
Thanks a lot for your help!

[Q] SGH-T999 soft-bricked in download mode only, Odin fails every time! Please help

SGH-T999 soft-bricked in download mode only, Odin fails every time! Please help me
I am new to forums and am in dire need of help. I have learned all that I know through google searches and spending at least 10 hours trying to solve this, so I need simple, easy-to-follow instructions.
I wanted to try experimenting with cyanogenmod so I tried using the one-click installer. On my wife’s galaxy s3 it failed but installed CWM and I think it removed GAAPS and booted up in stock touchwiz. After trying to get cyanogen on it and failing I decided to use Odin to get it back to factory settings and it worked!!
My Tmobile SGH-T999, however, is soft-bricked. I can't even get into simple recovery (volume up + power + home) but I can get into download mode. When I try booting it up normally, I get the message:
"firmware upgrade encountered an issue. Please select recovery mode in Kies and try again". The top left of the screen says:
Product name: GSH-T999
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: Samsung official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
Warrenty Bit: 0
BOOTLOADER AP SWREV: 1
I've tried using Odin 3.07 to put the same firmware (from sammobile) that I used on my wife's phone. I tried flashing the firmware with the proper 16gb pit file and that also failed. I'm pretty sure the PIT file I have works because I didn't get an error message (an earlier attempt with a different PIT failed with a PIT error message on the phone).
Whenever I use Odin it completes 99% of the way and give me this error message (at the end)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Successfully..
<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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<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> NON-HLOS.bin
<ID:0/003> cache.img.ext4
<ID:0/003> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
I've installed the latest samsung USB drivers, got from sammobile.com the latest firmware (for 4.3) and put it in the PDA slot, got what seems to be an accurate PIT file. I'm using a new USB cable. It worked for my wife's galaxy s3 but I have no idea how to make it pass!
I sincerely hope that you can help me.
warmly,
-Bryce J
PM me if you want to chat, text, or call me!
What did you do to yours to get it softbricked in the first place? Did you ever update to a 4.4 ROM? You are trying 4.3 and if you ever updated to 4.4 bootloaders/modem, then you can't go down to 4.3
Did you buy your phone new, or used online? A lot of used phones are some bastardized hybrid i747 and t999 parts.
sameboat
I'm having something similar. I'm just trying to get to factory reset but can't even get to recovery mode.
Simple fix. Download the stock firmware and boot into Download mode. Follow the Odin tutorial and you should be fine.

Problems with S4 mini GT-I9195 (loop, can'tacess recovery mode)

Hi guys!
i recently got my s4 mini bricked, so following some instructions on this forum i could debrick my cel phone, but I'm still with some problems.
- My cel phone stay on loop with the logo of sansung
- I can acess the download mode BUT I CAN'T ACESS THE RECOVERY MODE!
- When I plug the usb cable it apears the batery image and the cel starts without I press anything, it doesn't just stay charging.
I had download the firmware from sammobile, the correct to my country (Brazil) and did all correct following the tutorials, using odin and everything, but it don't work!
Could someone pleeeeeease help me!!!
Post odin logs
Davidich said:
Post odin logs
Click to expand...
Click to collapse
Thanks for you fast reply!
here's my odin log:
<ID:0/008> 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..
<ID:0/008> Odin engine v(ID:3.1100)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> tz.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img.ext4
<ID:0/008> NON-HLOS.bin
<ID:0/008> cache.img.ext4
<ID:0/008> hidden.img.ext4
<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)
<ID:0/008> Added!!
I don't know if it say something, but i saw an another s4 mini in download mode on the internet, and in the corner appears this:
ODIN MODE
PRODUCT NAME: GT-I9195
CURRENT BINARY: Sansung Official
SYSTEM STATUS: Official
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
And when I put mine in download mode, also appears this:
ODIN MODE
PRODUCT NAME: GT-I9195
CURRENT BINARY: Sansung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
BOOTLOADER AP SWREV: 1
WRITE PROTECTION: Enable
there's more in my than in the other, there's why this?
I didn't say but I can't acces recovery mode because the screen appear, with recovery booting write on teh corner, but the phone restart to the normal mode and stay in the loop
If you use kies try to close all kies processes in task manager...and if you have a antivirus disable it because it can close your firewall...also try to change the usb port
Davidich said:
If you use kies try to close all kies processes in task manager...and if you have a antivirus disable it because it can close your firewall...also try to change the usb port
Click to expand...
Click to collapse
I made all this and without success , here is the odin log:
<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/007> Added!!
<ID:0/007> Odin engine v(ID:3.1100)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> boot.img
<ID:0/007> cache.img.ext4
<ID:0/007> hidden.img.ext4
<ID:0/007> NON-HLOS.bin
<ID:0/007> recovery.img
<ID:0/007> rpm.mbn
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> system.img.ext4
<ID:0/007> tz.mbn
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
After the odin, the phone restart and stay in the loop.
Try another rom from sammobile
Davidich said:
Try another rom from sammobile
Click to expand...
Click to collapse
I've tried at least three of them, now I'm downloading another, but i don't know if will change something
that I said on my second post, about waht is write on the corner of the download mode, doesn't mean nothing?
The information in download mode is OK. What were you running before you bricked your phone?
RuffBuster said:
The information in download mode is OK. What were you running before you bricked your phone?
Click to expand...
Click to collapse
Practically nothing, I was talking on the whatsapp and I locked the phone and sleep, when I wake up it was bricked :/
Unfortunately there seems to be a few of these phones that just die all of a sudden. May well be a corrupt internal memory. If you weren't doing anything unusual to your phone and Stock ROM doesn't work then this may well be the case. But don't take my word for it it may be something else.
RuffBuster said:
Unfortunately there seems to be a few of these phones that just die all of a sudden. May well be a corrupt internal memory. If you weren't doing anything unusual to your phone and Stock ROM doesn't work then this may well be the case. But don't take my word for it it may be something else.
Click to expand...
Click to collapse
I hope a lot to don't be this, I will keep trying, but it's being a lot complicated!
If somebody still can help me would be awesome!
julioghigi said:
I hope a lot to don't be this, I will keep trying, but it's being a lot complicated!
If somebody still can help me would be awesome!
Click to expand...
Click to collapse
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
BOOTLOADER AP SWREV: 1
WRITE PROTECTION: Enable
On your logs from Odin it was Bootloader Version 1 , so your running JB V.4.2.2 ? And your tried to update in KitKat?
bierma32 said:
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
BOOTLOADER AP SWREV: 1
WRITE PROTECTION: Enable
On your logs from Odin it was Bootloader Version 1 , so your running JB V.4.2.2 ? And your tried to update in KitKat?
Click to expand...
Click to collapse
Yes I flashed JB V.4.2.2 with odin, and I also tried to update in kitkat, but with the same effect
I want to ask, I had some problens with the ear speaker of the phone and I broke the flat of these, so I'm doing all thiss without the ear speaker, would be this the problem? like the phone doesn't detect this and don't start?
Now I tried to update to kitkat 4.4.2 again to look de bootloader version, and it keep on version 1, should be this?
I tried to update to kitkat 4.4.2 of Russia, and appear those messages
Set warranty bit : system
Set warranty bit : cache
Set warranty bit : hidden
Secure check fail : modem
Why???
RuffBuster said:
Unfortunately there seems to be a few of these phones that just die all of a sudden. May well be a corrupt internal memory. If you weren't doing anything unusual to your phone and Stock ROM doesn't work then this may well be the case. But don't take my word for it it may be something else.
Click to expand...
Click to collapse
Hi!
If my internal memory is corrupted, there is a way to correct by sd card mode? or by JTAG? or the only way to save the phone is changing the eMMc chip?
Hi julioghigi. Did you ever manage to solve this? I am facing the same issue and I am clueless...
Similar problem here
Similar problem for me and still no solution :s
Link to thread here.
same here, any solution??
Same problem
Sertico said:
same here, any solution??
Click to expand...
Click to collapse
Hi Julio i send you inbox...
rogersc79 said:
Hi Julio i send you inbox...
Click to expand...
Click to collapse
Lucky Sertico, Christmas father came early for ya
Cheers

Categories

Resources