hello, fellow ROMers
My galaxy s4 (jfltevzw, sch-i545) was rooted when I received it. not knowing about the MDK cutoff, i tried to install a custom rom. I can occasionally get Download mode to work AND when I do, I get this :
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SCH-I545
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
CSB-OEM_CONFIG_LSB: 0X30
WRITE PROTECTION: Enable
And when i try to flash recovery, in red it says: START [224, 1440]
And in green: SECURE CHECK FAIL : recovery
trying to boot into recovery, in red,
SECURE FAIL : KERNEL
Followed by the yellow triangle and the message about taking it to a Verizon store
Last I was able to check i am on PL1.
cannot get to boot. tried flashing stock firmware and kernel
tried kies....won't take my model name
tried Verizon tool and it did not recognize the device
tried unroot.zip and rebranded it as unroot.zip.tar, so I could try to flash with odin (3.07, 3.09, 3.10.1, 3.12, 3.14, 3.14.4, etc) basic boot attempt with power key results in same message as trying to boot recovery
when download mode won't load I get : SECURE FAIL : KERNEL followed by UNKNOWN UPLOAD UPLOAD MODE
Any guidance would be gangbusters...
Did you try a factory reset in recovery?
Related
so i was trying to go back to andriod from cyanogenmod and i accidently turned the device off while in download mode. now i am on the "firmware upgrade encountered an issure. please select recovery in Kies & try again."
upper left corner reads the following
ODIN MODE
Product name: SGH-m919
Current Binary: Custom
System Status: Offical
Knox Kernal Lock: 0x0
Knox Warrenty Void: 0x1
CSB-CONFIG-LSB: 0x30
Write Protection: Enabled
eMMC Burst Mode enabled
START [224,1440]
SW EV, Check Fail : fused: 4 binary: 1
Do you have a recovery like CWM Recovery installed ?
Try flashing cyanogen mod again and then use odin to go back to stock rom.
Hi there guys,
I recently bought an Samsung Galaxy S5 SM-900F that came already rooted with Cyanogen CM12.1 (cm-12.1-20150806-NIGHTLY-klte), using CWM Recovery Philz_touch.
When i was trying to make the updates through OTA, i was never able to update the firmware it was always displaying the old one on the informations of the phone. So i updated the firmware throught CWM Recovery Philz Touch manually, everything was ok, after that i thought to change the Recovery method to the TWRP latest version, it seemed ok that i suceeded.
However when i try to enter recovery mode i can't i'm always stuck with the ODIN mode saying Custom Rom and Knox 0x1 and does not let me to enter into recovery staying always in "Download Mode" .
Could Not Boot
Odin Mode
Product Name: SM-G900F
Current Binary: Custom
System Status: Custom
Know Warranty Void: 0x1 (2)
qualcomm secure boot: enable (csb)
AP SWREV: S1, T1, R1, A1 and P1
UDC START
Down there is information of the firmware and kernel installed on the device at the moment.
Galaxy S5
SM-G900F
Android 5.1.1
G900FXXU1ANJ1
Verson CyanogenMod = 12.1-20150806-NIGHTLY-klte
kerner version = 3.4.0-cyanogenmod-g0e5afc9 [email protected] #1 Thu Aug 6 00:38:38 PDT 2015
build number = cm_klte-userdebug 5.1.1 LMY48G b33df4b0c1 test-keys
LinuxSE State = Forcing
I also done throught ODIN the installation on CF-Auto-Root-klte-kltexx-smg900f to be able to enter to recovery but when i enter it appears in red when entered on the recovery:
Adroid System Recovery <3e>
KOT49H.G900FXXU1ANCE ->
But the information of my version base band on the Phone Information is:
G900FXXU1ANJ1
If i try to install any of the recovery modes TWRP or CWM through ODIN i will the get always stuck in DOWNLOAD MODE and i neet to install again through ODIN CF-Auto-Root-klte-kltexx-smg900f so i can enter to recovery :
Could Not Boot
Odin Mode
Product Name: SM-G900F
Current Binary: Custom
System Status: Custom
Know Warranty Void: 0x1 (2)
qualcomm secure boot: enable (csb)
AP SWREV: S1, T1, R1, A1 and P1
UDC START
Can you please advise me what can i do to overcome this and install a custom recovery to update firmware in the future?
Best Regards,
Let me start off by saying I have already scoured this forum and other sources for a solution to this problem. I should add that I am somewhat bound by the confines of my experience, also.
Like many others here, my Samsung S4 mini GT-I9195 is stuck in a boot loop, unable to get into recovery mode. It can get to download mode, but is not recognized by my PC.
Things I've done so far:
1. tried to boot in recovery mode - doesn't work, says "Recovery starting..." then restarts into boot loop
2. checked battery - not it
3. dissasembled phone and checked power button - works fine
4. tried Samsung Kies - "Device is not responding. To resolve the issue, reboot the device." - no can do (note that I only just installed Samsung Kies on my PC for the first time after the boot loop started)
5. flashed firmware using Odin - PASS! - still in bootloop w/no recovery mode
6. flashed firmware again using Odin w/Auto-Reboot unchecked - PASS! - then attempted to reboot into recovery - no go, still in bootloop w/no recovery mode
The firmware I successfully flashed was Poland/T-Mobile version 4.4.2 downloaded from sammobile.
The one thing I have NOT tried is to repartition the pit file. Would this possibly make any difference? If it's worth a try, can I do this using the tar.md5 package above, or do I need a separate .pit file and if so, how do I know I have the right one???
After doing a little reading, I downloaded CSB_signed_SERRANOLTE_ONEPIT_OPEN_130523.pit, which was included in a 'repair firmware' .zip file that also included separate bootloader, code, csc and modem files. I actually did try flashing those files (except for the pit file) and that failed (of course) with error "Device 2, Binary 1", so I flashed the firmware above again and it passed again.
What else?
- Phone is not rooted
- I have no idea if USB debugging is turned on or not
- I was doing nothing with the phone when it first died. I figured the battery might have somehow rapidly drained to zero even though it should have been around 70%. I had last touched the phone about an hour earlier, to shut off my alarm. I tried plugging in to wall charger but phone would not turn on even after an hour or more of charging. I really don't remember exactly how or when the bootloop started.
ODIN MODE
PRODUCT NAME: GT-I9195
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB:0x30
BOOTLOADER AP SWREV: 2
WRITE PROTECTION: Enable
Anyone out there feel like helping out a noob today?
i have same problem
Actually , only one diferrent
KNOX WARRANTY VOID: 0x1
exactly same ,but i tried with pit 2 pit files and 2 diferent roms , and no result. Pleace help us!!!
G935P failed to root, shows "Custom binary blocked by SECURE BOOT (modem.bin)", help!
I have Samsung S7 Edge (G935P) that I wanted to unlock, is in android version 7.0, so I downloaded root file from https://download.chainfire.eu/1087/...to-Root-hero2qltespr-hero2qltespr-smg935p.zip and flash the phone with it but the root flashing did not complete, then the phone started writing that I flashed the phone with unsupported unlock file, then I download stock rom from https://www.sammobile.com/ and flash the phone complete and it started writing on top of the screen in red color this below;
Custom binary blocked by SECURE BOOT (modem.bin)
And also showing on the screen this on the link below;
https://lionfinger.com/gsmerrors/s7edge_error1.jpg
This are also how the download mode and recovery mode shows;
Download mode => https://lionfinger.com/gsmerrors/s7edge_error2.jpg
Recovery mode => https://lionfinger.com/gsmerrors/s7edge_error3.jpg
Please someone help me on how to revive the phone to boot completely.
Thanks!
Hi , try with this one :
https://updato.com/firmware-archive-select-model?record=E6BB0C3642A611E99F15FA163EE8F90B
or this one :
https://updato.com/firmware-archive-select-model?record=E8FFA23642A611E99F15FA163EE8F90B
Teddy Lo said:
Hi , try with this one :
https://updato.com/firmware-archive-select-model?record=E6BB0C3642A611E99F15FA163EE8F90B
or this one :
https://updato.com/firmware-archive-select-model?record=E8FFA23642A611E99F15FA163EE8F90B
Click to expand...
Click to collapse
Thanks.
Both of them are the same file.
If I flashed this file, will it make it to come on completely?
Thanks
Hi,
I can't use my tablet anymore tried Odin to re-install the origin firmware "SM-T825Y_1_20180122165040_zf84f94qoe_fac.zip" (new android 8 stock ROM) but it fails, Odin shows the transfer has PASSED but I still get this message in the screen:-
"Security Error: This device has been flashed with unathorised software & is locked.
Call your mobile operator for additional support. "
I wasn't planning flashing a custom ROM the only thing I did is put OEM Lock on, not sure why I did that.
When I put in Download Mode it shows this in the screen:-
ODIN MODE [High Speed]
PRODUCT NAME: SM-T825Y
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
FAP LOCK: ON
OEM LOCK: ON
DID: 03EA1E00AE16
WARRANTY VOID: 0x1 (Ox20C)
QUALCOM SECUREBOOT: ENABLE
AP SWREV: B3 (1, 1, 1, 1, 1) K2 S2
SECURE DOWNLOAD: ENABLE
CCIC: S2 MM005 HW: 4
BOOT: 6 MAIN: DS
Regards,
Sal.
1. It's FRP not FAP ya perv.
2. Reflash firmware with odin, do not go into download mode afterwards before 3.
3. The rest watch this video carefully, and next time you want to leave your device stock, leave it stock, if you want to install a custom rom or twrp, do not have auto reboot ticked.
4. here is link ---> https://www.youtube.com/watch?v=o0T-CR-KpfM
I did reflash with odin but I still get this message "Security Error: This device has been flashed with unathorised software & is locked.
Call your mobile operator for additional support. " There is another small message on top , "Custom binary blocked by FRP. (boot.img)"
Odin tells me its PASSED but the Tablet still says its locked FRP and OEM locked .
In download mode I am getting same info.
I just went to the Samsung Shop and they fixed it for free, they said they just put a new firmware not sure how they did it but I tried it myself with latest firmware but I couldn't get rid of the lock, I am missing something? like software? or just not enough info about about getting rid of locks?
I had the same issue after i installed a Xposed module. Had to reflash Pie Bootloader and Rom via odin. Now it boots, but i can't flash twrp anymore... It always fails.