Database Users

[Q] How to chage CSC?

Hi
My phone is N910U and it's CSC code is BRI (Thailand)
I was waiting for lollipop update, but it seems that only some countries have received the update.
So I decided to chage CSC to whatever the New Zealand CSC is to get the official update.
My phone isn't rooted and it runs stock rom.
While I was trying to flash recovery.tar via odin, it shows an error:
<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!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I used correct recovery file, and this happens when I want to flash autoroot too.
USB debugging on, download mode, stock USB cable, reinstalled driver
Does anyone know how to resolve this issue?
Also, can I just download New Zealand firmware and flash it via odin?
Will my phone not brick and be able to use it in the UK?
Any help would be very appreciated
EDIT: FIXED - Disable reactivation lock

Do you have reactivation lock enabled? If so, disable it before flashing stuff in odin

absinthesummer said:
Do you have reactivation lock enabled? If so, disable it before flashing stuff in odin
Click to expand...
Click to collapse
Thanks for your reply
the reactivation lock was enabled, so I disabled it. But it is still not working.
It shows slightly different error
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I really have no idea what went wrong.
Do you have any clue?

Have you tried flashing cf auto root since disabling reactivation lock? Typically in my experience you need to have root access before you flash a custom recovery.
Edit: that's not always the case, but when it comes to Samsung devices and odin, you should try to follow the usual steps: root then recovery.

absinthesummer said:
Have you tried flashing cf auto root since disabling reactivation lock? Typically in my experience you need to have root access before you flash a custom recovery.
Edit: that's not always the case, but when it comes to Samsung devices and odin, you should try to follow the usual steps: root then recovery.
Click to expand...
Click to collapse
Thank you for your suggestion.
I tried to root it first, and it gave me the same error(new one) as above.
I never had an issue when I was playing around with my SGS3 couple of years ago. Rooting, recovery, custom rom all flashed well via odin.
Any idea?

Thank you very much.
I was just redoing all the procedures, and found out that the reactivation lock is reactivated!
I disabled, again, and it worked!
Thank you again XD

cosmostronomer said:
Thank you very much.
I was just redoing all the procedures, and found out that the reactivation lock is reactivated!
I disabled, again, and it worked!
Thank you again XD
Click to expand...
Click to collapse
Very glad to hear it! That reactivation lock is the number one issue when odin fails (on this device anyway)

problems rooting note 3 AT&T 5.0

I had my device rooted on an older version of android (4.4 I believe). I removed root and was able to update OTA to 5.0 lolipop. Now I cant seem to root it at all. I've tried Kingo and Odin. Here is the log from Odin after it failed.
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> recovery.img
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone side:
ODIN MODE
Product name: SM-N900A
Current Binary: Samsung official
Knox Warranty Void: 0X0
Qualcom Secure Boot: Enable (CSB)
RP SWREV: S2, T2, R2, A3, P2
SECURE DOWNLOAD: ENABLE
UDC START
SYS REV CHECK FAIL : No Version
Secure Magiccode Check Fail : Recovery
Any help is needed, Thank you.

In KK nand write start error could be reactivation lock is enabled. But in L that menu nowhere to be found. Maybe I missed it somewhere.
Sorry just noticed it's not mentioned on you download mode description. I guess it's different with at&t version.
Sent from my SM-N920C

I was told to look for reactivation lock, but I can't find it either.
Sent from my SAMSUNG-SM-N900A using XDA-Developers mobile app

AT&T forum ???
http://forum.xda-developers.com/showthread.php?t=2574886

I'm not concerned with my phone being fake. I bought it through AT&T brand new over 2 years ago.
Sent from my SAMSUNG-SM-N900A using XDA-Developers mobile app

I think he means that you should ask in at&t forum.
Sent from my SM-N920C

OK thanks, I'll try there.
Sent from my SAMSUNG-SM-N900A using XDA-Developers mobile app

recovery problem in n9oo

i have a 32 gb n900 phone that with official lolipop that i was put it from sammobile.com and flash it by odin, then i tried 2 do a root with odin but it is not succes so i do it by kingo root
now, i need to flash a xda's developer Rom 2 my mobile by odin but there are a problem in odin to flash recovery !!!
i tried 2 use a varity of recoveries but it is not useful
it (odin) present that the recovery is failed with red and give
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
plz help because every things i did 2 make a recovry is unsuccedes

Then turn off reactivation lock
Sent from my GT-N7000

Rosli59564 said:
Then turn off reactivation lock
Sent from my GT-N7000
Click to expand...
Click to collapse
then after what ???
and how can I do this ??

As far as I remember reactivation locked is only available in KK. Not sure with Lollipop. I'm not with stock Lollipop for long. Some more my phone has just broke so I couldn't tell more about it.
Sent from my GT-N7000

Did you Troy different USB cables and USB ports?
I have reactivation lock on note 3 n900w8 so maybe some versions of note 3 have the lock in lollipop.

WARNING: PHE update not downgradeable

Just tried to downgrade the Note 7 after updating to PHE and it's a no go.
Message on the phone says: SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
Here is Odin's log:
<ID:0/005> Odin engine v(ID:3.1205)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> emmc_appsboot.mbn
<ID:0/005> lksecapp.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I don't think I'm doing anything wrong. I've upgraded and downgraded with Odin a few times before without any problems.
I've tried both PH3 and PH9 firmware versions.
It's not looking good for rooting...

lightning413 said:
Just tried to downgrade the Note 7 after updating to PHE and it's a no go.
Message on the phone says: SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
Here is Odin's log:
<ID:0/005> Odin engine v(ID:3.1205)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> emmc_appsboot.mbn
<ID:0/005> lksecapp.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I don't think I'm doing anything wrong. I've upgraded and downgraded with Odin a few times before without any problems.
I've tried both PH3 and PH9 firmware versions.
It's not looking good for rooting...
Click to expand...
Click to collapse
No you're correct. It doesn't have the ability to downgrade.

Do the replacement notes come with the PHE update? Is the update forced? I need to get my phone replaced at Best Buy but I can't lose root.

zeroempathy said:
Do the replacement notes come with the PHE update? Is the update forced? I need to get my phone replaced at Best Buy but I can't lose root.
Click to expand...
Click to collapse
I grabbed my replacement today and it came with PH9, though it sure wanted to install PHE shortly after initial boot. It's giving the option to delay for now.

zeroempathy said:
Do the replacement notes come with the PHE update? Is the update forced? I need to get my phone replaced at Best Buy but I can't lose root.
Click to expand...
Click to collapse
I just got mine and while I was there, I saw them activating and updating everyone's phone so when it came to my turn, I ask for them not to activate. I told them I didn't have time to go through it and would do it later when I got home.
It's still at PH9.
I just grabbed the full PHE firmware update and am talking to another dev to try to find out if there is a chance we can modify this update to remove the rev lock and root.
Will keep everyone posted.

Did you disable OEM lock in developer tools?
Sent from my SM-N930P using XDA-Developers mobile app

richardjrdeal said:
Did you disable OEM lock in developer tools?
Sent from my SM-N930P using XDA-Developers mobile app
Click to expand...
Click to collapse
by my understanding, that only relates to bootloader unlocking, and does not work for said purpose.

How can I use the IMEI to find the telephone number that was attached to the device???
Sent from my SM-N930P using Tapatalk

Sterist said:
by my understanding, that only relates to bootloader unlocking, and does not work for said purpose.
Click to expand...
Click to collapse
It keeps someone from wiping your phone. Pretty sure if you unlock it, it will allow you to Odin back.
Sent from my SM-N930P using XDA-Developers mobile app

I was reading on a Note 7 thread was someone that reset their phone ( http://forum.xda-developers.com/note-7/how-to/note-7-n930fd-f-downgrade-to-100-t3469787/page3) to get it back to pre- PHE update. Has anybody with a sprint phone tried to reset their phone before flashing in odin to downgrade.?

There is no way to have it downgraded
Sent from my SM-N930P using Tapatalk

sterstar2012 said:
There is no way to have it downgraded
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
hi. i have a question. When my phone sprint note 7 has pk1 made unlock carrier. First using odin put a combine rom COMBINATION_FA60_N930VVRU2APIB_CL9208905_QB11007042_REV00_user_mid_noship_MULTI_CERT and then using samsung tool pro to unlock. after this put a PHE by odin and now working unlock. is this a downgrade or not?. i want to have ph3 or ph9 for root and avoid kill my phone and use my phone like a smartphone.

https://drive.google.com/file/d/0Bw6tEApjkJtRRm05bHN4SXhEUkU/view

Help SM-G935F FRP Bypass

Hey guys please help me.
Long story short first: my stepsister wanted to get a new phone and gift this one to my stepdad. She apparently just factory resetted it with her google account on it but now when you start it up the FRP message pops up and the login doesn't work properly. This is the first time I even heard about FRP because I'm using a pretty old phone. I want to help because I'd consider myself good at computers and rooted my ex-smartphone years ago. Now I simply tried using this tutorial how to bypass it:
https://forum.xda-developers.com/general/general/bypass-frp-samsung-galaxy-s7-edge-t3765638
But that didn't work out because the ROM wasn't the right one for this device.
I spent the night downloading a previous stock ROM for it from a random website which took 12 hours
It was named DBT-G935FXXS1DQL1. Like I said stock ROM, I don't know if that's the right way. I wanted to downgrade it so I could use the bypass method from the tutorial.
But... That didn't work out either, Odin failed at this stage:
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> param.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the smartphone this error message appeared in the download mode:
"SW REV. CHECK FAIL. DEVICE: 2, BINARY: 1"
Here are the informations I have from the recovery mode:
samsung/hero2ltexx/&hero2lte
7.0/NRD90M/G935FXXS2DRDI
user/release-keys
And this is standing in the download mode:
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G935F
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: ON
Secure Download: Enabled
WARRANTY VOID: 0 (0x0000)
RP SWREV: B:2 K:0 S:0
Please help me, I really have no clue about this flashing older firmwares and such.
Thank you in advance, Philipp

Hello, have you managed to solve this?
I have also similar problem
Samsung/hero21texx/hero2lte
8.0.0/R16NW/G935FXXU2EREM

No, I'm waiting for somebody who knows more.

e4zyphil said:
No, I'm waiting for somebody who knows more.
Click to expand...
Click to collapse
Me too, do you think this may work?
https://www.youtube.com/watch?v=KVYQyvJ7IVY

Balkrish999 said:
Me too, do you think this may work?
/watch?v=KVYQyvJ7IVY
Click to expand...
Click to collapse
this worked for me, thanks :good::good: