back to stock. un-dev bl and un-cid

[en11gma]

just wanted to say i had been running my verizon note 3 (non-dev edition) like everyone else here
with the bl unlocked to dev edition and rooted most likely with either kingo or supersu through teamyemin or proyemin and i think there is another one too.

basically if you want to go back 100% original (including your original cid) its not as easy as you might think.

first thing i did was wipe everything that was possible to wipe from within twrp recovery.
next i booted to odin download mode
from there i flashed the OB6 official firmware
then i rooted using the kingo method as this seemed the most likely not to infect my computer and possibly only stole info from my phone. (this used the 2 files 1.tar and 2.tar flashed with odin for pc)
i then verified my root and installed terminal emulator end es file explorer root
i copied samsung_cid to phone sd card and used es file explorer root to move to ./data/local/tmp

changed my cid back to original and rebooted phone
booted to stock recovery and wiped everything i could and booted into odin download mode
flashed OF1 official

there is a very important part that could get alot of ppl phones into brick mode.
when you goto change the cid back to original you better already have the stock BL on and running and >>>NOT<<< the DEV-BL
that is why i chose to flash an official OB6 rom first

if you try to change the cid to original non-dev edition and reboot your phone this could have problems since you would have the dev bl flashed with a non dev bl cid

when the cid for the dev edition became available you could change the cid first and boot into the bl and it would say something like developer mode enabled or someting like that even if you had the stock bl flashed (not the dev bl)
this is fine

only problem is if you change that cid back to stock/original non-dev while you are running the dev bl

i dont know what would happen but i bet it wouldnt be good.


ok next part i think is important is getting rid of kingo root as much as possible and that is why i flashed the OB6 firmware first and then OF1 for my very last step.


ok thanks.

i know alot of ppl are probably gonna say why would you want to go back to stock original cid and my answer is this.

phone is really stable and also if i want to sell it which im thinking about.

hope it helped some ppl.

 

[ExpialZLD]

Where do we get our original Cid?

 

[bftb0]

The method used to do the unlocking runs the tool in two passes, like this:

pass1: change the CID.
pass2: (create debrick image &) alter the aboot partition sig to the DevEd sig.

There is no reason this can not be reversed (assuming you have root on ANY ROM) e.g. :

pass_negative_2: flash stock aboot to aboot partition.**
pass_negative_1: revert the CID by altering the original code to write your CID (minor code change and recompile).

** must be from the exact same version of boot firmware you have on the phone; you could use "dd" for this.

There's no reports of people trying this explicitly, but OTOH note this: there were owners of DevEd devices that accidentally flashed stock bootloaders. They didn't change their CID, and they didn't brick. They just couldn't go back to an unlocked bootloader any longer, or boot custom kernels: they converted their phones to retail without ever changing their CID.

Anyhow, it appears that you went through a ton of effort, when all you needed to do was flash the stock "aboot" back into place.

It probably isn't even necessary to revert the CID back.

Where do we get our original Cid?

You recorded it - as a precaution - when you went through the unlocking process. Didn't you?

As I mentioned above, it probably doesn't matter anyway.



@OP: did your "Custom" boot logo disappear eventually?

PS even after doing this the phone will still have a blown knox warranty flag and certain TZ/qseecom functionality will no longer work, even with 100% pure stock on the phone.

 

[ExpialZLD]

The method used to do the unlocking runs the tool in two passes, like this:

pass1: change the CID.
pass2: (create debrick image &) alter the aboot partition sig to the DevEd sig.

There is no reason this can not be reversed (assuming you have root on ANY ROM) e.g. :

pass_negative_2: flash stock aboot to aboot partition.**
pass_negative_1: revert the CID by altering the original code to write your CID (minor code change and recompile).

** must be from the exact same version of boot firmware you have on the phone; you could use "dd" for this.

There's no reports of people trying this explicitly, but OTOH note this: there were owners of DevEd devices that accidentally flashed stock bootloaders. They didn't change their CID, and they didn't brick. They just couldn't go back to an unlocked bootloader any longer, or boot custom kernels: they converted their phones to retail without ever changing their CID.

Anyhow, it appears that you went through a ton of effort, when all you needed to do was flash the stock "aboot" back into place.

It probably isn't even necessary to revert the CID back.



You recorded it - as a precaution - when you went through the unlocking process. Didn't you?

As I mentioned above, it probably doesn't matter anyway.



@OP: did your "Custom" boot logo disappear eventually?

PS even after doing this the phone will still have a blown knox warranty flag and certain TZ/qseecom functionality will no longer work, even with 100% pure stock on the phone.

Does by record do you mean by using a tool or like taking a picture of the cid

 

[bftb0]

Does by record do you mean by using a tool or like taking a picture of the cid

Cut-n-paste to a text file.

The tool spews out onto the screen the device's CID before it goes about changing it.

That assumes you followed the directions in the OP and used ADB. Or, didn't follow those instructions and used a terminal emulator. (I don't know whether or not the app shows you the output from the binary).

As I mentioned, folks that had DevEd devices (that is, "factory unlocked" bootloaders) that made the mistake of flashing stock firmware turned their DevEd phones into retail phones - without ever changing the CID to some other value. So it may not even matter - you end up with a "retail" phone with the same CID that you currently have.

In any event, if you didn't record the previous CID, there's nothing to do about it.


The OP mentions something called "samsung_cid". I presume he is talking about a mod of the original code that allows you to re-write the CID to an arbitrary value.