Database Users

Seem to have bricked my phone following DJembey's root method

Hi everyone, I'm desperate here.
I was following DJembey's root method TO THE WORD/LETTER. Everything was fine up until the last bit in changing the 'custom' status to official. The triangle away method didn't work, so I downloaded the 'OFFICIAL_STATUS_MOD' and used odin to try and flash the PDA, but it came up as 'FAIL' and now my phone is stuck on boot mode with 'FIRMWARE UPGRADE ENCOUNTERED AN ISSUE'. I've tried using odin to flash back to the stock rom, but it keeps coming up with 'FAIL'. Rally need help
DJembey's root method:
http://forum.xda-developers.com/showthread.php?t=2255190

jesus1987 said:
Hi everyone, I'm desperate here.
I was following DJembey's root method TO THE WORD/LETTER. Everything was fine up until the last bit in changing the 'custom' status to official. The triangle away method didn't work, so I downloaded the 'OFFICIAL_STATUS_MOD' and used odin to try and flash the PDA, but it came up as 'FAIL' and now my phone is stuck on boot mode with 'FIRMWARE UPGRADE ENCOUNTERED AN ISSUE'. I've tried using odin to flash back to the stock rom, but it keeps coming up with 'FAIL'. Rally need help
DJembey's root method:
http://forum.xda-developers.com/showthread.php?t=2255190
Click to expand...
Click to collapse
what firmware you are trying to root, and what stock firmware you tried to flash?

Here's what it says, this is the firmware I am trying to flash, but just before I did the root guide, I applied all of the official updates through settings >about phone > update, etc. It was still on 4.2.2 and I think it was october edition of the latest firmware (in UK)

samersh72 said:
what firmware you are trying to root, and what stock firmware you tried to flash?
Click to expand...
Click to collapse
So maybe I am trying to flash to an older firmware, is this not allowed?? Also, it says that the PIT partition is missing on ODIN (as seen on the attached picture)

jesus1987 said:
So maybe I am trying to flash to an older firmware, is this not allowed?? Also, it says that the PIT partition is missing on ODIN (as seen on the attached picture)
Click to expand...
Click to collapse
i think you have the secured bootloader (check if you have Knox void 0x0 or something in download mode) if yes, you can not go back to MDM or an old firmware, you can flash new "knoxed" firmware.
note that Triangle away and other stuffs to reset counter or status, wont work on new firmware.

samersh72 said:
i think you have the secured bootloader (check if you have Knox void 0x0 or something in download mode) if yes, you can not go back to MDM or an old firmware, you can flash new "knoxed" firmware.
note that Triangle away and other stuffs to reset counter or status, wont work on new firmware.
Click to expand...
Click to collapse
So, when I go into 'proper' download mode (pressing Vol. Down + Home + power) I have:
ODIN MODE
PRODUCT NAME:GT-I9505
CURRENT BINARY:Samsung Official
SYSTEM STATUS: CUSTOM
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID:0x1(or t?)
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION:Enable
And for the 'Firmware upgrade encountered an issue...' screen, I have:
ODIN MODE
PRODUCT NAME:GT-I9505
CURRENT BINARY:Samsung Official
SYSTEM STATUS: CUSTOM
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID:0x1(or t?)
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION:Enable
Hope this helps

jesus1987 said:
So, when I go into 'proper' download mode (pressing Vol. Down + Home + power) I have:
ODIN MODE
PRODUCT NAME:GT-I9505
CURRENT BINARY:Samsung Official
SYSTEM STATUS: CUSTOM
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID:0x1(or t?)
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION:Enable
And for the 'Firmware upgrade encountered an issue...' screen, I have:
ODIN MODE
PRODUCT NAME:GT-I9505
CURRENT BINARY:Samsung Official
SYSTEM STATUS: CUSTOM
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID:0x1(or t?)
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION:Enable
Hope this helps
Click to expand...
Click to collapse
it seems you have the secured bootloder, dont use triangle away or somthing else to reset counter and status.
you can flash firmware that begin only with I9505XXUD or I9505XXUE

samersh72 said:
it seems you have the secured bootloder, dont use triangle away or somthing else to reset counter and status.
you can flash firmware that begin only with I9505XXUD or I9505XXUE
Click to expand...
Click to collapse
At the moment I'm downloading "I9505XXUDMI1-PRE-ROOTED-ODEX-FULL.rar", will this work do you think when I try and flash using ODIN? Hope so!!!

Right, I've tried that firmware, and it's still failing on odin any ideas?
samersh72 said:
it seems you have the secured bootloder, dont use triangle away or somthing else to reset counter and status.
you can flash firmware that begin only with I9505XXUD or I9505XXUE
Click to expand...
Click to collapse

Seems this one doesn't work either...
I've noticed something weird though, I've tried running it a few times, and each time it seems to get a little further in the flash process (it gets to just past modem) then fails.

Hello,
what USB cable are you using?
I have encountered an issue with the original Samsung cable, ("fail" in Odin all the time), but when I switched to another usb cable everything worked from that moment on
Try it, you might have luck.

Zeitraffer said:
Hello,
what USB cable are you using?
I have encountered an issue with the original Samsung cable, ("fail" in Odin all the time), but when I switched to another usb cable everything worked from that moment on
Try it, you might have luck.
Click to expand...
Click to collapse
Funny you should say that...
I restarted my PC, and tried a few USB ports, and cables, and it was still failing. But I stuck at it, and literally doing the same procedure over and over seems to have worked, as it randomly decided to flash fine! This was using the XXUE firmware

Do you still have KNOX WARRANTY 0X1 in download mode?
Sent from my GT-I9505 using XDA Premium HD app

Obagleyfreer said:
Do you still have KNOX WARRANTY 0X1 in download mode?
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah, it still says KNOX WARRANTY VOID 0x1 but it also says the binary and system status are official. Is there a way to unvoid?

[Q] Seandroid encorcing

Hi guys!
Some weeks ago, I unrooted my i9505. This saturday I wanted to root again, because of the Kitkat roms from jamal and janjan.
When I'm booting my phone there is a message in the top corner:
"KERNEL IS NOT SEANDROID
Set Warranty Bit : kernel"
I read on some different websites that this message isn't cursing any problems, but it would be nice if I could fix it anyways.
Also when i enter download-mode this is what it says:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY:Custom
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMc BURST MODE enabled
Is there any way to fix this?
Before rooting this saturday i had a stock firmware installed, which i found here: http://www.sammobile.com/firmwares/2/
Rooted my phone with this guide: http://forum.xda-developers.com/showthread.php?t=2219803
I've had some random reboots on both roms (jamal and janjan) since then - i don't know whether that is caused by the "enforcing"-error or by the ROM..
Hope you can give me some anwers
Thanks guys

This message appears coz maybe u tried to change the STOCK KERNEL for other different or maybe the ROM u installed have custom KERNEL. I recommend u make WIPE in recovery and install STOCK ROM for let ur system clean. U will can root it and install custom recovery then

So this is what i should do:
1. Boot into TWRP
2. Wipe everything
3. Flash Stock Firmware from ODIN
4. Try to boot, and then the message should be gone
- Or did i misunderstand something?

So this is what i should do:
1. Boot into TWRP
2. Wipe everything
3. Flash Stock Firmware from ODIN
4. Try to boot, and then the message should be gone
- Or did I misunderstand something?

velein said:
So this is what i should do:
1. Boot into TWRP
2. Wipe everything
3. Flash Stock Firmware from ODIN
4. Try to boot, and then the message should be gone
- Or did I misunderstand something?
Click to expand...
Click to collapse
Thanks in advance

Didn't work

velein said:
Didn't work
Click to expand...
Click to collapse
What stock ROM u are flashing?

random reboot is known bug with GE kit kat roms as of now.. wait a month or more, i'm pretty it'll be fixed..

Nothing can change
only CURRENT BINARY:Custom and SYSTEM STATUS: Custom to Official
KNOX WARRANTY VOID: 0x1 you can not change

akadxda said:
Nothing can change
only CURRENT BINARY:Custom and SYSTEM STATUS: Custom to Official
KNOX WARRANTY VOID: 0x1 you can not change
Click to expand...
Click to collapse
But this will not have any effect on my daily use of my phone?
just to be sure.
thanks in advance

velein said:
But this will not have any effect on my daily use of my phone?
just to be sure.
thanks in advance
Click to expand...
Click to collapse
No, you will not have problems
Knox will not work when 0x1
If you install the correct official firmware and this message - "KERNEL IS NOT SEANDROID* Set Warranty Bit: kernel "should be removed

[Q] Tried to install < Echoe v16 > on GT-I9505 and stuck on first boot

Hi all,
Hopefully someone can help?
The stock firmware for my S4 was XXUEMK9. I followed a combination of this guide:
http://forum.xda-developers.com/showthread.php?p=47227598#post47227598
and also this guide for v16:
http://forum.xda-developers.com/showthread.php?t=2372286
After rooting (CF-AutoRoot) I booted fine, then after installing these two I booted fine:
1. ODIN Flash the New Bootloader (the NAD bootloader will do)
2. ODIN Flash the I9505XXUNB8 Modem
Then I continued with the final stage of installing using Philz/Aroma, rebooted and just get stuck on
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit : kernel
Samsung
GALAXY S4
GT-I9505
Left for half hour and no change. Also tried repeating the final wipe/install several times, no change.
Please, is someone able to help?
Further to this I can reboot into Recovery or Download, the latter shows:
ODIN MODE
Produce Name: GT-I9505
Current Binary: Custom
System Status: Custom
KNOX Kernel Lock: 0x0
KNOX Warranty Void: 0x1
CSB-Config-LSB: 0x30
Write Protection: Enable
eMMC Burst Mode: enabled

Cant u repeat the process again or either flash stock firmware

aayushkhajuria2842 said:
Cant u repeat the process again or either flash stock firmware
Click to expand...
Click to collapse
Well I decided to try v15 instead, that went on first time? Unfortunately wifi was disabled so spend another two hours trying to get the right modem (AP + CP) installed, but finally successful.
I wonder why v16 wont go on? How odd... Anyone else had this issue?

nrps1 said:
Well I decided to try v15 instead, that went on first time? Unfortunately wifi was disabled so spend another two hours trying to get the right modem (AP + CP) installed, but finally successful.
I wonder why v16 wont go on? How odd... Anyone else had this issue?
Click to expand...
Click to collapse
Anyone had experience of this or advice?
The v15 Echoe is crashing and rebooting the phone constantly now, sometimes when it is left alone too, so will have to try something else.

Knox Warranty Void: 0x1

I saw this on my bricked GS4 4.3.1(cyanogenmod 10.2) when I powered it on.
Any way to fix this?
It pops up on recovery mode and when I boot it up.
I really just want to get my S4 working again.
Can I just take it into some place like Best Buy or something and they'd help me?
Product Name: SGH-M919
Current Binary: Custom
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
CSB-CONFIG-LSB: 0x30
Write Protection: Enabled
eMMC BURST MODE enabled

oohrekt said:
I saw this on my bricked GS4 4.3.1(cyanogenmod 10.2) when I powered it on.
Any way to fix this?
It pops up on recovery mode and when I boot it up.
I really just want to get my S4 working again.
Can I just take it into some place like Best Buy or something and they'd help me?
Product Name: SGH-M919
Current Binary: Custom
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
CSB-CONFIG-LSB: 0x30
Write Protection: Enabled
eMMC BURST MODE enabled
Click to expand...
Click to collapse
Please tell me there is hope for me.

oohrekt said:
I saw this on my bricked GS4 4.3.1(cyanogenmod 10.2) when I powered it on.
Any way to fix this?
It pops up on recovery mode and when I boot it up.
I really just want to get my S4 working again.
Can I just take it into some place like Best Buy or something and they'd help me?
Product Name: SGH-M919
Current Binary: Custom
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
CSB-CONFIG-LSB: 0x30
Write Protection: Enabled
eMMC BURST MODE enabled
Click to expand...
Click to collapse
If you can boot to recovery, then I wouldn't say it's "bricked."
As for a place like Best Buy helping you, well I don't know their processes but anyone who checks for a warranty claim can't help you in its current state.
Why not just flash a new ROM?

oohrekt said:
I saw this on my bricked GS4 4.3.1(cyanogenmod 10.2) when I powered it on.
Any way to fix this?
It pops up on recovery mode and when I boot it up.
I really just want to get my S4 working again.
Can I just take it into some place like Best Buy or something and they'd help me?
Product Name: SGH-M919
Current Binary: Custom
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
CSB-CONFIG-LSB: 0x30
Write Protection: Enabled
eMMC BURST MODE enabled
Click to expand...
Click to collapse
If your phone is "bricked" than your phone has the same exact functionality as a brick. If your phone can turn on and tell you which version of android your on, well... a brick cant do that.

Well I can't get into recovery mode. Being the idiot I tried to flash 4.2.2 over not thinking what I have done. Well, even before I couldn't get into recovery mode. I can get into download mode however. Is it possible I can flash official 4.3 or some other 4.3.1 rom over?

If you still having the problem..
oohrekt said:
Well I can't get into recovery mode. Being the idiot I tried to flash 4.2.2 over not thinking what I have done. Well, even before I couldn't get into recovery mode. I can get into download mode however. Is it possible I can flash official 4.3 or some other 4.3.1 rom over?
Click to expand...
Click to collapse
Well friend,
don't panic.. as I know all your loses is that you lost your warranty but not your device..
You can install the stock original rom jelly bean 4.3
If you are interested go to www sammoblie com then (firmwares) then search for your device model (I9500) or (I9505) or (I9505G) or (I9506) then download the firmware for your country and carrier and follow their installing instructions

If you can boot to recovery, then I wouldn't say it's "bricked."
As for a place like Best Buy helping you, well I don't know their processes but anyone who checks for a warranty claim can't help you in its current state.
Why not just flash a new ROM?

DUBU said:
If you can boot to recovery, then I wouldn't say it's "bricked."
As for a place like Best Buy helping you, well I don't know their processes but anyone who checks for a warranty claim can't help you in its current state.
Why not just flash a new ROM?
Click to expand...
Click to collapse
bro cant you read that he cant boot into recovery
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
oohrekt said:
Well I can't get into recovery mode. Being the idiot I tried to flash 4.2.2 over not thinking what I have done. Well, even before I couldn't get into recovery mode. I can get into download mode however. Is it possible I can flash official 4.3 or some other 4.3.1 rom over?
Click to expand...
Click to collapse
did you ever fix it , i got the exact same problem , i got a metropcs s4 and i wanted kit kat insane rom and tried to flash a stock tmobile rom because some people said they did and it was fine,. well not for me. i would like to knowif you ever got it fixed, i tried to flash the stock metropcs 4.2.2 that i was on before this happened and odin still fails.
its fixed now , i had to move the stock tar to the same folder as odin, go figure

Haha mate you havent "bricked" your phone.
If your phone enters the recovery, it would be booting into the download mode too.
Try getting the official firmware of your specific phone model nom and just flash it via odin.
Dont worry.
Sent from my GT-I9500 using XDA Free mobile app

DeepankarS said:
Haha mate you havent "bricked" your phone.
If your phone enters the recovery, it would be booting into the download mode too.
Try getting the official firmware of your specific phone model nom and just flash it via odin.
Dont worry.
Sent from my GT-I9500 using XDA Free mobile app
Click to expand...
Click to collapse
I get a message about use kies recovery because firmware upgrade had issues when I try to boot into recovery, and I when I boot download mode flashing the stock rom fails every time.

revized said:
I get a message about use kies recovery because firmware upgrade had issues when I try to boot into recovery, and I when I boot download mode flashing the stock rom fails every time.
Click to expand...
Click to collapse
Yeah that is because you upgraded to 4.3 which has KNOX bootloader.
It wont let you flash 4.2.2 anymore. Like a downgrade is not possible once a knix enavled bootloader is flashed.
Download 4.3 or 4.4.2 and flash. It wont fail.
Thanks if i helped.
Sent from my GT-I9500 using XDA Free mobile app

DeepankarS said:
Yeah that is because you upgraded to 4.3 which has KNOX bootloader.
It wont let you flash 4.2.2 anymore. Like a downgrade is not possible once a knix enavled bootloader is flashed.
Download 4.3 or 4.4.2 and flash. It wont fail.
Thanks if i helped.
Sent from my GT-I9500 using XDA Free mobile app
Click to expand...
Click to collapse
Sounds nice and all although I tried to flash the official 4.3 from Samsmobile and it's fails.
4.4 is not available for mrtropcs customers because the company don't care about it's customers in this regard. LOL
Just for inquiry purposes only, I found a link to a Guy saying he used lunix to delete know bootloader from a tar filehttps://www.google.com/url?sa=t&source=web&rct=j&ei=8PDgU7DSOZTdoATTkIKYDA&url=http://m.youtube.com/watch%3Fv%3D75DKAGNstbM&cd=1&ved=0CB4QtwIwAA&usg=AFQjCNE7yajeB0317RtOmlFeEIB1QgEOGA&sig2=oD8TmSaTKu19-kpy0AKFGQ

Just go to sammobile and find the latest firmware for your model (4.4.2 for example) and dont look at build number.
Just grab it and extract to desktop.
Put your device in recovery mode if you can, and wipe data/cache/system if you can.
Then put your phone in download mode and connect do computer, in ODIN choose AP and add your tar.md5 file from desktop.
Flash it.
Then pull out battery on first reboot when flashin. Put it back and get into recovery by pressing VolUp + Power. Wipe everything again and reboot.
Should be fine.

i was finally able to flash stock 4.3 by just moving the tar file into the same folder as odin, go figure , i still want 4.4!!LOL

Galaxy Note 3 SM N9005

ODIN MODE
PRODUCT NAME: SM-N9005
CURRENT BINARY: Samsung Official
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x1 (4)
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A3, P3
SECURE DOWNLOAD : ENABLE
UDC START
I gave my note3 to a technician, there was a problem (It didn't boot, instead stuck on samsung logo with recovery booting). The technician did his best and the phone began to work. Then I used the phone once ( for 24 hours) and the same problem came back. I tried to flash it with official Rom lollipop 5.0, bootloader and CWM by Odin v3.09, but that was in vain.
I need your help please.
Waiting for your reply.

Take it back to your technician .
Suggestion is a hardware problem .

JJEgan said:
Take it back to your technician .
Suggestion is a hardware problem .
Click to expand...
Click to collapse
I did it before trying by myself to fix the problem, but not solution. If it's a hardware problem, may be I have to try with another technician. Thanks.

This is exactly the same problem I am having.
My phone is now working on stock Lollipop but I was stuck with this for a while.
I found that if i flashed the CWM .tar file with Odin it would reboot and work fine.
Once you get to that point, download a stock rom from Sammobile - I used 4.4.2 just to get it working.
When i had installed 4.4.2 everything appeared fine, i went ahead and booted into stock recovery and did a full reset.
I then let the phone update to stock 5.0 using the built in updater.
Im running it as it is (stock rom, un-rooted and stock recovery) until i can research enough into the problem and how to get around it.
In Odin mode on my phone, there is a "write protection - enabled" line also, which im guessing is causing my problem on not being able to get cwm/twrp to work
My aim was to Root, custom recovery and custom Rom but I hit the exact brick wall you posted in the OP