Database Users

[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

[Q] won't boot normal or recovery [desperate]

Can someone help with a possible bricked an SGH-i337 4.3 UCUEMK2 build?
Got this on eBay & it "ran" great but this nagging voice kept saying, "it could be better on KitKat."
First let me say I’ve been rooting & flashing ROMs for years but this had me stumped.
After performing a successful "saferoot" I found RomManager couldn’t install ColckworkMod due to a locked bootloader.
I did install "Safestrap" but w/o fully understanding how to use it I may have killed it.
As of now I cannot boot into recovery, normal booting shows the Samsung logo with an unlocked padlock symbol.
Odin connects but with a locked bootloader I’m not sure if that will help since NAND write fails.
In download mode at the triangle screen this is what it reads:
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Knox Kernel Lock: 0x0
Knox Warrantee Void: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC Burst Mode enabled
Any Devs out there that can prevent this from becoming an aquarium chew toy please help.
I’ve been trying to fix it for 2 weeks & about to give-up.
much thanks, Rick

You will be able to flash the full MK2 firmware using odin
Sent from my SAMSUNG-SGH-I337 using Tapatalk

Thanks jmjoyas
jmjoyas said:
You will be able to flash the full MK2 firmware using odin
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I've been looking for the modem/radio MD5 file but no luck so far. Even if I do find it I'm not sure if my locked bootloader will let me flash it.

rfreynolds said:
I've been looking for the modem/radio MD5 file but no luck so far. Even if I do find it I'm not sure if my locked bootloader will let me flash it.
Click to expand...
Click to collapse
Try here http://forum.xda-developers.com/showthread.php?p=49562527
Sent from my SAMSUNG-SGH-I727

MANY THANKS to jmjoyas & jd1639
after following your advice all is back to normal & backed up. now i need to study safestrap & push on to kitkat. thanks again guys.

[Q] boot failure, logo stuck.

Hey guys, i will go direct into topic
i have note 2 n7100
1- i made a factory reset from settings menu on phone then the mobile didn't load again (stuck into logo)
2- tried all recovery ROM with all methods and no luck.
3- Downloaded and installed official ROM from SAMMOBILE and the mobile loaded and worked.
4- Installed a custom ROM.
5- Made a wipe to go back for the official ROM again and starting from here everything went bad..
my mobile didn't accept any ROMS, recovery or anything.
just rebooted and stuck on Samsung logo
i tried many things for 3 days but no luck.
Please HELP.
-----
-----
EDIT:
i know that wiping from recovery mode might solve the problem ,, but i don't have access to recovery mode. i have access to download mode. and sure i tried MANY times to flash recovery roms with ODIN and no luck.

Which rom u r using nd which method ... Cwm 6.04. ???
Sent from my GT-N7100 using Tapatalk

sufiyankatra said:
Which rom u r using nd which method ... Cwm 6.04. ???
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
rom of what ?
CWM is a recovery and i said that all of recovery roms were failed.

probably you have enabled knox, just flash official firmware again
Enviado do meu GT-N7100 através de Tapatalk

monteiro-ribas said:
probably you have enabled knox, just flash official firmware again
Enviado do meu GT-N7100 através de Tapatalk
Click to expand...
Click to collapse
I did, the same one which worked before..
but it turned to the same result.
stuck with Samsung logo

siimoz said:
I did, the same one which worked before..
but it turned to the same result.
stuck with Samsung logo
Click to expand...
Click to collapse
Have you tried booting into recovery and performing a full data wipe from there? Including (internal) SDCard?

EmptyArea said:
Have you tried booting into recovery and performing a full data wipe from there? Including (internal) SDCard?
Click to expand...
Click to collapse
There's no recovery enabled
i tried to flash (philz , twrp2 and cmw 2 ) none of them is booting.

So we know what bootloader you have, what does it say (in the top left) when you're in download mode?
#Also, you should ask for this thread to be moved to Q&A

EmptyArea said:
So we know what bootloader you have, what does it say (in the top left) when you're in download mode?
#Also, you should ask for this thread to be moved to Q&A
Click to expand...
Click to collapse
here it is:
ODIN MODE
Product name: GT-N7100
CUSTOM BINARY DOWNLOAD: YES (12 COUNTS)
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX WARRANTY VOID: 1
RP SWREV: A2

So you're on a 4.3+ bootloader, I haven't looked into that much - I'm assuming you can downgrade and have a custom recovery, but I'm not sure on the procedure. (Although i imagine Knox Warranty is irreversible - not like that matters because you would simply say: "I've got know idea what that [KNOX] is" and "My phone must have come like that."
It would not be the first time someone has opened a phone to find the software in a peculiar state!)
Either way you should be able to install and 4.3 stock rom and get stock recovery back.
Perhaps it's your odin and OS setup. Try flashing a few different versions of recovery, on different PCs*, with different cables and different versions of odin. If that doesnt work try the same with different stock ROMs. It's what I'd try whilst seeking more expert advice.
*if on Win7 try running odin 'as Windows XP'
Also see here:
http://techbeasts.com/2014/01/17/how-to-deknox-samsung-galaxy-s3-s4-note-2-note-3/

EmptyArea said:
So you're on a 4.3+ bootloader, I haven't looked into that much - I'm assuming you can downgrade and have a custom recovery, but I'm not sure on the procedure. (Although i imagine Knox Warranty is irreversible - not like that matters because you would simply say: "I've got know idea what that [KNOX] is" and "My phone must have come like that."
It would not be the first time someone has opened a phone to find the software in a peculiar state!)
Either way you should be able to install and 4.3 stock rom and get stock recovery back.
Perhaps it's your odin and OS setup. Try flashing a few different versions of recovery, on different PCs*, with different cables and different versions of odin. If that doesnt work try the same with different stock ROMs. It's what I'd try whilst seeking more expert advice.
*if on Win7 try running odin 'as Windows XP'
Also see here:
http://techbeasts.com/2014/01/17/how-to-deknox-samsung-galaxy-s3-s4-note-2-note-3/
Click to expand...
Click to collapse
Thank you for your help, i am downloading a different stock ROM now.
but can you please tell me more about that downgrading thing?

I'm not too sure I'm afraid.
My objective, if I were you, get a custom recovery working and install Wamrick's NC3 - stock kernel will work for you as your bootloader is 4.3 and I don't think you can downgrade that due to Knox.

EmptyArea said:
I'm not too sure I'm afraid.
My objective, if I were you, get a custom recovery working and install Wamrick's NC3 - stock kernel will work for you as your bootloader is 4.3 and I don't think you can downgrade that due to Knox.
Click to expand...
Click to collapse
still.. i don't know how to make the Custom recovery work! as you see in the boot loader i tried to flash 12 times and nothing happened.

And you've tried flashing a full stock 4.3 rom from Sammobile right? Running odin as win XP (if on 7)

i9505 Set Warranty Bit: Kernel

Welcome guys,
I have Galaxy S4 and I wanted to install Custom ROM. Unfortunately when I installed TWRP (the newest build), my phone displays "Set warranty bit: kernel" and then it boots into Recovery Mode (twrp works fine), but stock ROM doesn't boot. I don't know how to deal with it. Will custom ROM install fix that problem? I don't want to brick it.
I have access to download mode, TWRP (as I said before, when I turn phone on, it boots into TWRP instantly), but unfortunately ODIN doesn't recognize phone at all.
Please help :crying:

Does the computer recognize the phone?
After installing, did you select the option to allow changes to the internal memory?
Tried different USB cables and USB ports?
If you get the phone recognized by Odin, I suggest flashing a stock ROM via Odin and checking the phone to ensure complete functionality. Once you know the phone is working on a stock ROM, maybe start with an older version of TWRP such as 2.87.
Flashing a custom recovery should not prevent the phone from booting a stock ROM.

audit13 said:
Does the computer recognize the phone?
After installing, did you select the option to allow changes to the internal memory?
Tried different USB cables and USB ports?
If you get the phone recognized by Odin, I suggest flashing a stock ROM via Odin and checking the phone to ensure complete functionality. Once you know the phone is working on a stock ROM, maybe start with an older version of TWRP such as 2.87.
Flashing a custom recovery should not prevent the phone from booting a stock ROM.
Click to expand...
Click to collapse
I'm such an idiot. When knox is tripped you cant run stock ROM, so basically I just installed LineageOS and it works hah

Tripping knox does not prevent a phone from running a stock ROM.

audit13 said:
Tripping knox does not prevent a phone from running a stock ROM.
Click to expand...
Click to collapse
So it's strange though. I couldnt boot stock ROM and the only thing I had to do was install a custom one. Anyway, thanks for the answer

I've flashed TWRP to a number of Samsung phones which cause Knox to trip and the warranty bit to change from 0x0 to 0x1. Despite this, I have been able to flash and use stock ROMs with a tripped Knox indicator.
Maybe the phone needed a factory reset using the stock recovery after being flashed with Odin?

audit13 said:
I've flashed TWRP to a number of Samsung phones which cause Knox to trip and the warranty bit to change from 0x0 to 0x1. Despite this, I have been able to flash and use stock ROMs with a tripped Knox indicator.
Maybe the phone needed a factory reset using the stock recovery after being flashed with Odin?
Click to expand...
Click to collapse
Aaaand here we got the problem. I tried to install twrp many times and unfortunately the stock one stopped running (dont ask, i dont know how it happened). Despite this everything worked but I wanted to install custom ROM and then that problem happened. It was just the lack (??) of stock ROM or knox blocked the availability to boot it.
Oh, completely forgot. I installed TWRP by LineageOS' tutorial on their page

It all worked out in the end which is the important part.
Thanks for sharing your solution.