Database Users

Samsung Keyboard shows null?

Hello people, I bought a second hand galaxy note today, using Samsung keyboard, when I press the letter keys, instead of getting the corresponding letter I am getting "null" on the screen. Other keyboard works fine.

You need to flash CSC according ROM you have installed
Give this detail from setting - about phone
Baseband ?
Kernel ?
version ?
as well dial this
*#1234#
and input result here

Baseband: N7000XXLPT
Kernel: 3.0.15-N7000XXLQ2-CL605927
[email protected]#3
Build number: IML74K.XXLQ2
PDA: N7000XXLQ2
Phone: N7000XXLPT
CSC: Unknown
I bought this phone second, the previous owner must have flash it without CSC

Flash the same ROM again with putting the ROM file in the [Cash] option in Mobile Odin.
Search for this ROM - UK I guess - in dr.ketan topic.
Good luck

Is it important to have csc?

FinancialWar said:
Is it important to have csc?
Click to expand...
Click to collapse
If you don't want it to do what it's doing it is. It contains other boots and bobs to do with the region your in.
Sent from my GT-N7000 using Tapatalk 2

FinancialWar said:
Baseband: N7000XXLPT
Kernel: 3.0.15-N7000XXLQ2-CL605927
[email protected]#3
Build number: IML74K.XXLQ2
PDA: N7000XXLQ2
Phone: N7000XXLPT
CSC: Unknown
I bought this phone second, the previous owner must have flash it without CSC
Click to expand...
Click to collapse
find lq2 rom and flash csc by selecting pda tab in odin. remembet yoy will lose data, so backup first.
Sent from my GT-N7000 using xda premium

I had look at your thread, does that mean I have to buy Mobile Odin Pro for the newer ICS firmware?

you can flash csc.with pc.odin too.
mobile odin have some.extra benifit like keep root while flashing. it is hassle free from pc connection.
so it is not must, just optional.
Sent from my GT-N7000 using xda premium

I am confused. I just bought the Mobile Odin and am getting
" superuser access is needed but could not be acquired . are you rooted and did give permission.
what am I supposed to do?

have you open supersu appl and updated binary?
if your root is proper, first time it will ask to grant permission.
Sent from my GT-N7000 using xda premium

dr.ketan
I went through the root process in your "When all other method fails to root your device"
after everything was done, I am stuck on the Welcome to GT-N7000 screen.
Keeps on getting error messages popping up, then the phone would go blank and then slowly display this weird greenish screen.
here is the message report from Odin
OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> factoryfs.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!

FinancialWar said:
dr.ketan
I went through the root process in your "When all other method fails to root your device"
after everything was done, I am stuck on the Welcome to GT-N7000 screen.
Keeps on getting error messages popping up, then the phone would go blank and then slowly display this weird greenish screen.
here is the message report from Odin
OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> factoryfs.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
Click to expand...
Click to collapse
yes it is common, b'coz kj1 hav old kernel. now. just flash newer cf root kernel like lb1 .
Sent from my GT-N7000 using xda premium

dr.ketan said:
yes it is common, b'coz kj1 hav old kernel. now. just flash newer cf root kernel like lb1 .
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
How do I flash the newer cf root kernel?
Sent from Samsung Galaxy Note

I think the question needs to be asked, do you actually want root and non standard firmware/kernel?
If you just want a standard phone but want to solve the problem you originally asked about then just download and flash factory firmware from Sammobile.com using pc odin.
Sent from my GT-N7000 using XDA

FinancialWar said:
How do I flash the newer cf root kernel?
Sent from Samsung Galaxy Note
Click to expand...
Click to collapse
Download this and flash with Mobile odin
http://download.chainfire.eu/149/CF-Root/SGN/CF-Root-SGN_XX_OXA_LB1-v5.0-CWM5.zip

scotthubbard said:
I think the question needs to be asked, do you actually want root and non standard firmware/kernel?
If you just want a standard phone but want to solve the problem you originally asked about then just download and flash factory firmware from Sammobile.com using pc odin.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
it won't work because my kernel is too old? I tried that already and I get error messages

dr.ketan said:
Download this and flash with Mobile odin
http://download.chainfire.eu/149/CF-Root/SGN/CF-Root-SGN_XX_OXA_LB1-v5.0-CWM5.zip
Click to expand...
Click to collapse
That seems to do the trick, the note is now running the ICS firmware probably.

dr.ketan said:
You need to flash CSC according ROM you have installed
Give this detail from setting - about phone
Baseband ?
Kernel ?
version ?
as well dial this
*#1234#
and input result here
Click to expand...
Click to collapse
Android Version: 2.3.5
Baseband: N7000XXLA4
Kernel Version: 2.6.35.7-N7000XXKJ1-CL627135 [email protected] #2
Build: GingerBread.XXKJ1
PDA: N700XXKJ1
Phone: N7000XXLA4
CSC: Unknown
What do i do? Im also facing the same issue with the keyboard? Let me know ASAP Explain in noob language please

Flash csc this way
Open pc odin - select csc tab - point to rom file which you hav flashed.
Flash.
Sent from my GT-N7000 using xda premium

[Q] Flashing stock Android

Sorry if this is in the wrong place but I'm kind of a noob at this forum stuff and I'm posting here because I need serious help.
So now you'll probably cringe and maybe even get mad at how much of an idiot I am after reading this but here goes:
Last week I rooted my phone and flashed the leaked 4.3 update for the S4. Nothing went wrong so I got curious. I'd heard of cyanogenmod before so I decided I'd try that. That worked too. Now the problem is that I'm not really liking CM so I decided to unroot/flash the stock rom. This is where it gets bad: The tutorial I used for the rooting didn't tell me to back anything up. So I don't have any backups of my own stock rom.
I did some digging and found multiple pages with stock rom links but none of them are of my country. I've tried flashing the 4.3 again but Odin always says "FAIL!" What the hell do I do?

poninaine said:
Sorry if this is in the wrong place but I'm kind of a noob at this forum stuff and I'm posting here because I need serious help.
So now you'll probably cringe and maybe even get mad at how much of an idiot I am after reading this but here goes:
Last week I rooted my phone and flashed the leaked 4.3 update for the S4. Nothing went wrong so I got curious. I'd heard of cyanogenmod before so I decided I'd try that. That worked too. Now the problem is that I'm not really liking CM so I decided to unroot/flash the stock rom. This is where it gets bad: The tutorial I used for the rooting didn't tell me to back anything up. So I don't have any backups of my own stock rom.
I did some digging and found multiple pages with stock rom links but none of them are of my country. I've tried flashing the 4.3 again but Odin always says "FAIL!" What the hell do I do?
Click to expand...
Click to collapse
Have you tried this: http://forum.xda-developers.com/showthread.php?t=2265477
Don't worry about it not being from your country. You can change the CSC to your country's later but first get your phone working.

kingzain900 said:
Have you tried this: http://forum.xda-developers.com/showthread.php?t=2265477
Don't worry about it not being from your country. You can change the CSC to your country's later but first get your phone working.
Click to expand...
Click to collapse
What do you mean? I can just download a random country's firmware? In another thread it said to not do that. I followed this tutorial and download the HOME.tar file the guy uploaded but I got FAIL almost instantly on Odin.

Go to Sammobile, download the latest stock firmware for your country and flash using Odin.
Sent from my GT-I9505

poninaine said:
What do you mean? I can just download a random country's firmware? In another thread it said to not do that. I followed this tutorial and download the HOME.tar file the guy uploaded but I got FAIL almost instantly on Odin.
Click to expand...
Click to collapse
If you are worried about the different firmwares, then you can get your country's firmware from here: http://www.sammobile.com/firmwares/1/?model=GT-I9505&pcode=0#firmware.
Please note that these are the latest firmwares and likely to have the latest bootloader and hence the Knox problem. So it's upto you.

My country's firmware isn't there...

poninaine said:
My country's firmware isn't there...
Click to expand...
Click to collapse
That's why I mentioned that download a firmware from the earlier link, then change the CSC to your country's. First check what's your country's three letter code and find the CSC for it.

kingzain900 said:
That's why I mentioned that download a firmware from the earlier link, then change the CSC to your country's. First check what's your country's three letter code and find the CSC for it.
Click to expand...
Click to collapse
I downloaded Hungarys HOME.tar.md5 but it fails.
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!

Odin Failure to flash CWM Galaxy S4 ATT

Hey guys, I'm having a little trouble getting custom roms installed on my Galaxy S4. Here is a little information about the phone
Carrier: ATT
Model: Galaxy SGH - 1337
Android version 4.2.2
After spending a few hours here on XDA both searching the site and posting on the help thread, I've come to no solution.
So yesterday due to a level of frustration with the amount of bloat that comes pre-installed on the Samsung devices, I decided I would try to set up a custom rom. I've used the Towelroot site to root the device (enable superuser access and disable Knox,) But wasn't able to install CWM. I've downloaded and installed the CWM Rom Manager and inside that app is an option to install CWM manually. Of course it isn't that easy, because although it says it's installed the recovery, when I boot into recover mode, it is still the stock android recovery mode.
So I turned to Odin. Specifically Odin 3.09. This is where the problems start. I start my phone and enable download mode. The phone is recognized by Odin and I choose the CWM file I have (recover-clockwork-touch-6.0.4.4-jflteatt.tar.) I press start and the process begins, but before long I see FAIL! in red at the top
The message box reads as follows:
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
I've tried using three different usb cables (including the stock s4 cable included in the packaging) and several different ports of course to no avail.
What exactly does FAIL! (Auth) mean? That seems to be the point where it goes south.
Could I be flashing a bad file? Is the CWM.tar.md5 not the correct file to flash?
I've tried several different versions of both Odin and CWM. Is there something else that I have to do before this step? I've read a lot about the S4 being a pain to load custom roms onto.
Anyways if anyone has a fix to this particular solution then let me know. Otherwise I'll take really any other viable solution to enabling custom roms on the Galaxy S4 for ATT. I'd like this to be a thread that people see when they google search it, so I won't give up and I'll be sure to post with the best process that I can find!

Your boot loader is locked. So, no custom recovery and kernel. The only working recovery we have is safestrap.
More info - http://forum.xda-developers.com/showthread.php?t=2616221

misterbreadcrum said:
Hey guys, I'm having a little trouble getting custom roms installed on my Galaxy S4. Here is a little information about the phone
Carrier: ATT
Model: Galaxy SGH - 1337
Android version 4.2.2!
Click to expand...
Click to collapse
I see this above but need more info... Are you completely stock right now?
You will NOT be able to Odin any CWM to this phone. See below for other brief info for you to look into for CWM/TWRPand how to install IF on MDB or MDL firmware. Or if MF3 Your ONLY OPTION is Safestrap and limited to TouchWiz based Roms.
If you are then when you go to Settings/More/About Phone what does your Baseband say? Does it end with MDB, MDL, MF3?
IF it ends with MDB or MDL the look up Casual Root with TWRP. This will allow you to flash ANY Roms.
IF it ends with MF3 Then look up Safestrap for MF3. This will allow you to flash Safestrap versions of Roms.
ALSO IF it is MF3 you might as well update to MK2 or NB1 then use their safestrap version for root
Sent fron I337 Red BadAss Themed ShoStock 7.0

Help changing from custom rom to legit update (Samsung S5)

Okay so to keep it brief, I am on alliance rom v5.3, running kitkat 4.4.2 on my Samsung S5, recently Lollipop has come out and I would like to update.
this was my first custom romming so needless to say I'm kinda scared, I am pretty sure I can find out how to flash to another custom rom but how would I go about getting to the default so that I can accept normal update? or is there a custom rom that is usually kept updated? (I am a sucker for having the latest version of things)
Also is there anything I should know about going from one custom rom that is rooted to another? or is it exactly like going from stock to custom?

DarkVamprism said:
Okay so to keep it brief, I am on alliance rom v5.3, running kitkat 4.4.2 on my Samsung S5, recently Lollipop has come out and I would like to update.
this was my first custom romming so needless to say I'm kinda scared, I am pretty sure I can find out how to flash to another custom rom but how would I go about getting to the default so that I can accept normal update? or is there a custom rom that is usually kept updated? (I am a sucker for having the latest version of things)
Also is there anything I should know about going from one custom rom that is rooted to another? or is it exactly like going from stock to custom?
Click to expand...
Click to collapse
just look for stock lollipop rom for your phone ( sammobile)/and flash with odin, just make sure to do a full wipe before flashing the stock rom

Thanks for the quick reply, will this allow me to get future updates? like hotfixes released and stuff? I saw somewhere that once you flash it does something to the kernal which makes updates possibly brick the phone.

Just factory reset the custom, then use ODIN to flash the Stock ROM
Flashing the stock ROM will allow OTA updates so long as you don't root or flash anything else custom like recovery - it needs to stay 100% stock for OTA
But you can still root, and each time an OTA arrives, grab the new ROM from sammobile dot com and use ODIN to flash it, that will update your phone, leaving everything in tact, all your data and images etc will be fine, only thing you'll need to do after updating is root the phone again

Thank you both, I have found my phone model on sammobile but the list of firmwares there is no Australian firmwares(Im Australian) or even any US firmares, the only primarily english firmware that I can see on the list is for the united kingdom? are those what I use or am I missing something? Sorry if I should know this =\
Edit: it shows that I have the G900F under Model number in the settings.

DarkVamprism said:
Thank you both, I have found my phone model on sammobile but the list of firmwares there is no Australian firmwares(Im Australian) or even any US firmares, the only primarily english firmware that I can see on the list is for the united kingdom? are those what I use or am I missing something? Sorry if I should know this =\
Edit: it shows that I have the G900F under Model number in the settings.
Click to expand...
Click to collapse
Try a UK firmware, the latest version BOE5 is in my sig link on MEGA, much faster than Sammobile
There is also samsung-updates dot com you can check out

Sorry to bug you but im getting errors when trying to use odin, im getting "Secure check fail : aboot" on my phone and the following on odin
Code:
<ID:0/007> Odin v.3 engine (ID:7)..
<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> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
Looking up the codes I see stuff about having the wrong boot loader and to flash a different boot loader and modem and that its impossible to get with others saying its possible but should never be done, then others saying that I need to turn off reactivation lock.
At this stage I have factory reset it(it automatically booted after so I turned off) and I downloaded your G900FXXU1BOE5_G900FOXA1BOE5_G900FXXU1BOE5 file and put that in the AP section of odin.

DarkVamprism said:
Sorry to bug you but im getting errors when trying to use odin, im getting "Secure check fail : aboot" on my phone and the following on odin
Code:
<ID:0/007> Odin v.3 engine (ID:7)..
<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> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
Looking up the codes I see stuff about having the wrong boot loader and to flash a different boot loader and modem and that its impossible to get with others saying its possible but should never be done, then others saying that I need to turn off reactivation lock.
At this stage I have factory reset it(it automatically booted after so I turned off) and I downloaded your G900FXXU1BOE5_G900FOXA1BOE5_G900FXXU1BOE5 file and put that in the AP section of odin.
Click to expand...
Click to collapse
Are you sure you had the phone in Download Mode?
Volume DOWN & HOME & POWER (Then volume up when asked)
And yes, disable Reactivation lock before flashing anything or you'll end up with major problems requiring a massive mess on to fix
Using ODIN 3.10.6 ?

think you need pitfiles with the rom

Yea it was in download mode and I have never heard of this reactivation thing :S the instructions I read had nothing like that in there, any other settings I should change? luckily it booted fine so ill look into changing that.
Edit: Using Odin 3.09 Also I checked and reactivation was disabled.

ad0dh67 said:
think you need pitfiles with the rom
Click to expand...
Click to collapse
Yea I was wondering the same
Try this OP
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Load it into the PIT section along with the ROM in the AP section together and try again
---------- Post added at 19:14 ---------- Previous post was at 19:12 ----------
DarkVamprism said:
Yea it was in download mode and I have never heard of this reactivation thing :S the instructions I read had nothing like that in there, any other settings I should change? luckily it booted fine so ill look into changing that.
Edit: Using Odin 3.09 Also I checked and reactivation was disabled.
Click to expand...
Click to collapse
Here's the latest ODIN
https://mega.co.nz/#!Exo3yADS!y7pFS5-9RVhp4vDxTRAQARAwkjyQAB_9mDZWfXkLqko

There is no pit section inside of Odin 3.10?
Edit: Nevermind I found it but it says not to use it unless im an engineer, how badly will this screw me up =\ Im kind of scared to.

DarkVamprism said:
There is no pit section inside of Odin 3.10?
Click to expand...
Click to collapse
There is on the lower left log / options / PIT section, although clicking that says to load it into the CSC section
Try using the PIT file with your 3.09 version of ODIN first as Im not sure where 3.10.6 wants the PIT file loaded into, it's not very clear

Okay in 3.09 there is a pit up the top where I can put it but but there is also a csc? which one am I supposed to put it in?

DarkVamprism said:
Okay in 3.09 there is a pit up the top where I can put it but but there is also a csc? which one am I supposed to put it in?
Click to expand...
Click to collapse
Put it in the PIT section
I'm just reading up on what 3.10.6 means with that engineer warning
Make sure you load the stock ROM into AP together with the PIT file in the PIT section before flashing

I tried using the rom in the AP and the pit inside the PIT but now its saying secure check fail : pit =\
attempted with odin 3.09

DarkVamprism said:
I tried using the rom in the AP and the pit inside the PIT but now its saying secure check fail : pit =\
attempted with odin 3.09
Click to expand...
Click to collapse
Are you running ODIN as Admin? (Right click > Run as Administrator)
Using a native PC running Windows? All Samsung drivers installed?
It almost sounds as if your bootloader is locked, but you managed to flash custom recovery and root right?

Yea I do have custom recovery and a custom rom and had rooted it. although inside the about device section it said I was using G900F I noticed the download mode said G900I so I searched for my old box and on the box it says it is a G900I so I assume the rom I used modified the model number, could this be screwing with anything?

DarkVamprism said:
Yea I do have custom recovery and a custom rom and had rooted it. although inside the about device section it said I was using G900F I noticed the download mode said G900I so I searched for my old box and on the box it says it is a G900I so I assume the rom I used modified the model number, could this be screwing with anything?
Click to expand...
Click to collapse
Looks like you need to grab the G900I ROM and PIT
I'd try with just the ROM first, hopefully ODIN saved you from bricking when it realised it was for the wrong model phone
Get the G900I ROM, stick it into ODIN like you originally tried, see how you go from there
EDIT - Now it makes sense why there was no Australian ROM for your G900F, there is for the G900I

Okay, good news is sam mobile had the correct firmware now that im using the correct model number(doh) and the phone still boots fine, will update when I have downloaded and tried it, thanks for sticking with me.

[Q] [HELP] I can't ROOT anymore! what's wrong? Can you help me please?

My phone: SM-N9005 (Philippines) Knox 0x1 ; Custom Status
Before, it was it was rooted with KitKat 4.4.2 and I got SuperSU by using CF auto-root. (CF-Auto-Root-hlte-hltexx-smn9005.tar) here is the file name to be sure, then knox was tripped.
later a few months. I accidentally accepted a auto software update. Biggest mistake! After, the update was done. My SuperSU is gone and I lost root permission. Yet my status is still Custom.
I tried flashing CF auto root again to my phone with Odin 3.09 and 3.07. Both Failed! I tried approx 15 times. Then I flashed to 5.0 lollipop (N9005DXUGBOF1_N9005OLBGBOF1_XTC) thinking that might work, then I tried flashing it again with CF auto-root, still failed though! Then I was thinking maybe, CF auto-root didn't work because of a 5.0 bootloader. I went back to 4.4.2 KK (N9005XXUGNI4_N9005OLBGNL1_XTC) again, and i tried flashing CFAR again with Odin 3.09 and 3.07, and guess what?! I still failed. Please HELP! it's been a long day!

kenmante said:
My phone: SM-N9005 (Philippines) Knox 0x1 ; Custom Status
Before, it was it was rooted with KitKat 4.2.2 and I got SuperSU by using CF auto-root. (CF-Auto-Root-hlte-hltexx-smn9005.tar) here is the file name to be sure, then knox was tripped.
later a few months. I accidentally accepted a auto software update. Biggest mistake! After, the update was done. My SuperSU is gone and I lost root permission. Yet my status is still Custom.
I tried flashing CF auto root again to my phone with Odin 3.09 and 3.07. Both Failed! I tried approx 15 times. Then I flashed to 5.0 lollipop (N9005DXUGBOF1_N9005OLBGBOF1_XTC) thinking that might work, then I tried flashing it again with CF auto-root, still failed though! Then I was thinking maybe, CF auto-root didn't work because of a 5.0 bootloader. I went back to 4.4.2 KK (N9005XXUGNI4_N9005OLBGNL1_XTC) again, and i tried flashing CFAR again with Odin 3.09 and 3.07, and guess what?! I still failed. Please HELP! it's been a long day!
Click to expand...
Click to collapse
Can you install this APP and add screenshots pls?

Ok!

kenmante said:
Ok!
Click to expand...
Click to collapse
Seems all ok.
1. Try to flash TWRP custom recovery via ODIN.
2. Flash this file via TWRP.

Do I really need to be in 4.4 Kitkat?

kenmante said:
Do I really need to be in 4.4 Kitkat?
Click to expand...
Click to collapse
Are you insane, dude? Remove your ****ing imei?

Joku1981 said:
Seems all ok.
1. Try to flash TWRP custom recovery via ODIN.
2. Flash this file via TWRP.
Click to expand...
Click to collapse
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)