Power+Home+Volume down shows :
Odin Mode
Product Name: SM-N910F
Current Binary: Custom
System Status: Custom
Reactivation Lock: off
Knox Waranty VOID : 0x1(4)
Qualcomm Secureboot: Enable (CSB)
Power+Home+Volume up NO MENU
I tried to update my device with kies
- bootloop recovery booting
I tried to update my device with Odin
- N910FXXS1CPC5_N910FDTM1COI1_N910FXXS1COK1_HOME.tar
- bootloop recovery booting
What can I do ?
Related
So i follow http://forum.xda-developers.com/xperia-l/development/rom-updated-ios7-extreme-edition-t2560915 to install a ROM then I realize that is a JB rom .
Now my phone stuck at Odin mode and could not do normal boot
Detail:
Could not do normal boot.
ODIN MODE
PRODUCT NAME : SM-N9005
CURRENT BINARY :Custom
SYSTEM STATUS : CUSTOM
REACTIVATION LOCK (KK) : OFF
KNOX KERNEL LOCK : 0X0
KNOX WARRANTY VOID : 0X1
QUALCOM SECUREBOOT : ENABLE (CSB)
RP SWREV : S2,T2,R2,A3,P3
WIRTE PROTECTION : Enable
USC START
I tried restored my nanoid backup but it doesn't work , please help !
Problem solved
Solution : I use Odin to install stock firmware and everything works fine now
I tried to root my Note 3 SM-N900W8 with Odin 3.07. When ODIN showed passed, I removed the cable but the phone was stuck at keep rebooting showing:
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
It never showed Set Warranty Bit: recovery
I had to remove the battery to stop the rebooting. After I turned on the phone at the Download Mode page, it shows the following:
ODIN MODE
PRODUCT NAME: SM-N900W8
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S2, T2, R2, A3, P2
WRITE PROTECTION: Enable
UDC START
When I tested the phone with Root Checker whether it's rooted. The app said it is not rooted.
I tried to run ODIN to root the phone again and I ran into the same rebooting problem again.
I also cannot open the Recovery Mode screen (Volume up + Menu + power). The phone would show RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING but nothing happens after.
If anyone knows how to fix and root the phone, please kindly let me know.
Weird..double check if the rooting file(the 1 u downloaded frm chainfire) is for sm-n900w8 only..
Sent from my SM-N900 using XDA Premium 4 mobile app
WHEN I TRIED USING ODIN
FOR ROOTING
ODIN MODE
PRODUCT NAME:SM-900F
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEN STATUS: OFFICIAL
REACTIVATION LOCK(KK): ON
KNOX WARRENTY VOIO: 0X0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV : S1 T1 R1 A1 P1
UDC START
SECURE CHECK FAIL : RECOVERY
WHAT DO I NEED TO DO
PLS ADVICE
MY EMAIL
([email protected]):crying:
When i rooted my g900f it wasnt so long ago , i flashed twrp on odin then flashed in twrp supersu zip which can be found on chainfires web, google both , u'll find sumting
Try turning of your reactivation lock.
Reactivation lock would be my guess. It stops a lot of people until they turn it off.
Hello guys, ever since I bought my phone I sometimes have this error "sbl1 partition doesn't exist" pressing power button for 7 seconds reboots and fixes it, but problem is, I'm about to sell the phone and the owner might think I'm cheating him if it ever happens to him, so does anyone have an idea of how to fix this?
Full error:
boot recovery mode
check boot partitions. .
sbl1 partition doesn't exist
odin mode
product name: sm-g900f
current binary: custom
sytem status: custom
reactivation lock(kk): off
knox warranty void: 0x1 (0)
qualcomm secureboot: enable (csb)
rp swrev:**s1,**t1,**r1,**a1,**p1
secure download :**enable
udc start
Flash a stock ROM with ODIN
Latest G900F (United Kingdom) Lollipop ROM
Code:
https://mega.nz/#!fVhhzRBC!A79uC8Fgg1mGCZOaujQCzBxcUUN9z_ctVVkigD8ffVM
Please help me! My phone stays in download mode with the following messages appearing on screen:
Could not do a normal boot.
Odin Mode.
Product Mode: SM-G900F
Current Binary: Custom
System Status: Custom
Reactivation Lock: Off
Knox Warranty Void: 0x1(4)
Secure Boot: Enable
Ap SWREV: S1,T1,R1,A1, P1
Secure Download: Enable
UDC START
Flash a stock ROM with ODIN
If your first thought after a "brick" isn't "where did I store the tar for my phone?" you should probably read on how to use Odin to repair your phone and not flash things on it again...