yashsingh1/xdaforums huggingface dataset:
[Verizon Galaxy Note 3 General] bftb0:
If it worked the Odin/Download screen will say "MODE: DEVELOPER".

---------- Post added at 07:17 PM ---------- Previous post was at 07:12 PM ----------

The very first post in this thread points out that the SDcard inserted in the phone will be overwritten & formatting destroyed. You need to format it if you haven't already.

I don't know about SD cards, but I have a variety of USB sticks - most of them can be mounted in TWRP as a OTG USB disk drive, but at least one of them can't. It's actually the smallest (& oldest) of all of them. I'm not sure it has anything to do with formatting or size.
[Verizon Galaxy Note 3 General] b3y0ndd34th:
Thank you for your input, but that's a little of the pot calling the kettle black... I never once said the data on my card was missing. I knew the script would format the sd card, thus I used a spare 2 GB sd card for installation without any issues. The data on my sd card is fine.

The problem was with the recovery, which I shouldn't have posted a question here about in the first place, but I figured others might have faced the issue and could point me in the right direction.

To reiterate, since you missed it, the sd card does not mount in the recovery, it shows as 0 mb when I try to mount it, so there for I can't make a back up to the sd card, only to the internal memory. This sd card is a 32 gb.

I used my 16 gb sd card as an alternative (which also has data on it) and was able to mount the sd card in the recovery, and I was able to make a back up to it.

I assume this is a limitation of TWRP, or something misconfigured with my sd card. Both sd cards are formatted in FAT32.

Apparently there is an update coming that addresses this issue, something about adopted storage.
[Verizon Galaxy Note 3 General] freddt2790:
well I have just 1 more question so does this make the device a developer version or just changes the cid
[Verizon Galaxy Note 3 General] ryanbg:
Just an update, I recompiled the binary with some fixes from beaups to address the "samsung device only" error for users on 4.4 roms. The download link is in the OP, don't use the attached one.
[Verizon Galaxy Note 3 General] bftb0:
Both, if you do it correctly. If you only run the tool once it will only change your CID.
[Verizon Galaxy Note 3 General] freddt2790:
By twice you mean

so do you mean that i should run both again or do you mean if i just run the first 1 it will change my cid and i run second 1 it makes it develoer device BUT I THINK I KNOW THE ANSWER WHEN I BOOT INTO DOWNLOAD MODE IT SAYS DEVELOPER MODE
[Verizon Galaxy Note 3 General] bftb0:
This tool is meant to be run in a bare minimum of two passes.

If the first pass succeeds the CID will be changed.

If the first pass fails it will print an error message on the screen and the CID will not be changed.

The second phase will not occur until the CID has been changed

If the CID has already been changed, the tool will automatically skip to the second phase where it attempts to convert the device to a developer edition device.

If the second phase fails, the tool will print an error message on the screen

The important point in all of this is to read the messages that the tool prints on the screen.

If you are having trouble you can't resolve by reading the thread, then cut-n-paste the error message the tool produces into a post and ask what those messages mean. Either that or say "I tried everything and nothing worked"... and wait and watch while exactly nobody replies.

If you see "MODE: DEVELOPER" on the Odin/Download screen, then congrats, you have an unlocked bootloader.

.
[Verizon Galaxy Note 3 General] max366:
I've tried searching and I can't seem to find an answer. When running this I get the message: [-] can't get current cid, find it and fix the code

Any suggestions?

Thanks
[Verizon Galaxy Note 3 General] bftb0:
It seems that different releases of the stock kernels create a file in /sys that contains the CID (of both the primary eMMC flash chip and the external SD card) in varying locations. Not sure why it kept moving, but the original code tried up to three different locations in /sys until it found something to read... and then gave up with the message you provided if it could not find a CID file.

[MENTION=1923941]donc113[/MENTION] modified the code (see post #218) for 4.4.x in this regards, so it checks for the CID value in slightly different locations. I see [MENTION=766721]ryanbg[/MENTION] recently recompiled the binary, he might have done something like this as well.

You can find the location in your kernel in a root shell, e.g.

su
cd /sys
find . -name cid -print

(it will be the mmc1 path)

and then run the "strings" command on the version of the "samsung_unlock_n3" file you have downloaded:

strings samsung_unlock_n3 | grep cid

to verify whether the location your kernel is using is being checked by the version of samsung_unlock_n3 that you downloaded.

[Edit 8/25/2016] Based on feedback from member shallmann, it appears that specific binary versions released within the Unlock Thread should be used depending on the firmware revision of your phone. See this post in that thread.

TL;DR use the version in post #218 (or perhaps [MENTION=766721]ryanbg[/MENTION]'s new version from a few days ago)

Please post your findings (including the ROM version you have on your phone) to help others out.
[Verizon Galaxy Note 3 General] max366:
Thanks for the reply and the good info! I tried both downloads original and the updated one posted yesterday. I will check out post 218 and try it out. Im on the run at the moment and likey won't be able to try to mess aroubd with it until the morning, when I do I will post my results. Thanks again!:)
[Verizon Galaxy Note 3 General] bftb0:
They don't seem to be congruent

[MENTION=766721]ryanbg[/MENTION] (2016-08-02) "samsung_unlock_n3" searches for:

/sys/block/mmcblk0/device/cid

/sys/devices/platform/msm_sdcc.1/mmc_host/mmc0/mmc0:0001/cid

/sys/class/mmc_host/mmc0/mmc0:0001/cid

[MENTION=1923941]donc113[/MENTION]_20160425 (post #218) "unlock" searches for

/sys/devices/msm_sdcc.1/mmc_host/mmc0/mmc0:0001/cid

/sys/devices/platform/msm_sdcc.1/mmc_host/mmc0/mmc0:0001/cid

/sys/class/mmc_host/mmc0/mmc0:0001/cid

/sys/devices/msm_sdcc.1/mmc_host/mmc1/mmc1:0001/cid

FWIW, the MJ7 kernel ("4.3") has the cid file at

/sys/devices/msm_sdcc.1/mmc_host/mmc1/mmc1:0001/cid

so ryanbg's recently-compiled code wouldn't work there; I don't know exactly which path the 4.4 release kernels (NC2/NC4/NK1) used.

===>> what version are you on?

[Edit 8/25/2016] Based on feedback from member shallmann, it appears that specific binary versions released within the Unlock Thread should be used depending on the firmware revision of your phone. See this post in that thread.

TL;DR use the version from post #218
[Verizon Galaxy Note 3 General] max366:
Success Via donc113 post #218! Thank you for your help.

I'm on Stock OTA 4.4.2 NC4

Neither of ryanbg's worked, the original (samsung_unlock_n3) gave the warning about the wrong device and the recently compiled version (unlock_n3) gave the error that it couldn't find the current cid. As you pointed out the path for my cid was

sys/devices/msm_sdcc.1/mmc_host/mmc1:0001/cid

Which is why donc113's version (unlock) worked and ryanbg's did not. just needed to look in the right place :)

Thanks again!
[Verizon Galaxy Note 3 General] ryanbg:
I'll update the binary. Beaups original code doesn't check /sys/block/mmcblk0/device/cid which seems to be the best location to check, which I added in the initial version and forgot to put it back in the new version. Sorry for the inconvenience!

EDIT: Binary in OP download link (not attachment) has been updated to address this issue.

[MENTION=2341536]bftb0[/MENTION] I'd be happy to share the source code if you're interested, the only difference from beaups original source is checking /sys/block/mmcblk0/device/cid and the signature/CID.
[Verizon Galaxy Note 3 General] donc113:
Makes it a developer edition

---------- Post added at 04:01 PM ---------- Previous post was at 03:52 PM ----------

The source I used is posted in post #218 and the only changes were to change the dev aboot signature (and dev cid) and add the 4th place to look for the cid.
[Verizon Galaxy Note 3 General] ultraJtown03:
When I enter the first command on adb it says failed to copy . Why? I need help
[Verizon Galaxy Note 3 General] bftb0:
Just guessing here but the most likely scenario is that you either:

- didn't enable USB debugging on the device, or

- didn't accept the pop-up dialog on the phone accepting the inbound ADB connection, or

- numerous other reasons including no working driver installed on the PC, no cable, etc.

[Edit 8/25/2016] Based on feedback from member shallmann, it appears that specific binary versions released within the Unlock Thread should be used depending on the firmware revision of your phone. See this post in that thread.

Many people have successfully used this in a terminal emulator rather than using adb. In that case, copy the executable file ("unlock" from post #218) to /data/local/tmp using a file manager app and then run the last 5 (non-adb) commands in a terminal emulator app.

su
cd /data/local/tmp/
chmod 777 unlock
chown root.root unlock
./unlock

If you have problems, cut-n-paste the output of the tool into a post here.
[Verizon Galaxy Note 3 General] patttpatttyoooo:
SD Card Issue

I have an issue with my 32 GB SD Card that was formatted with the commands. It shows that its a 63.9 MB drive with 57.1 MB remaining. When I entered Disk Management with the SD card in my PC's reader, there are a bunch of partitions on it, varying in size. What can I do to get all my space back, is it fine to format the SD card, or do I need to copy the files that are on the SD card and then format it?
[Verizon Galaxy Note 3 General] bftb0:
There is only a single large - and "raw" - file on your SDcard at the moment. The first 256 MB are literally a bit for bit copy of the first 256MB of the flash memory chip from your phone, captured just prior to the "aboot" partition on your phone being modified.

Now, that copy actually has two partition tables in it: something called a "protective MBR partition table", which is sort of the old-fashioned partition table format that Windows expects to see for partition tables on SD cards, and after that a more modern partition table called either a "primary GPT" partition table or UEFI primary GPT table.

Because the from/to copying starts from the beginning of the flash chip in your phone and to the beginning of the SD card, the offset locations of these tables on the SDcard is exactly where they would normally be located!

But there is a problem: there is supposed to be a secondary GPT which is located at a fixed offset from the END of the SDcard, and it never got copied

So that's why disk partitioning programs get confused: first, the secondary GPT never got copied, and 2nd, because the SD card may not be the same size as the source flash chip (32 Gb). In your case they match, but in other cases (where the SD card is smaller than 32GB), the information in the copied (primary) GPT says there are partitions located at offsets beyond the end of the card!

Now back to your questions: that 256MB raw data dump is something called a "debrick image" which can be used in specialized situations to rescue a Samsung Galaxy phone from a hard bricking. Will you ever need it? Probably not. The same thing could be said of me; but I kept a copy of it on my PC "just in case". In a couple of years when I'll have a different phone, it will get deleted. But it's sitting there in the meantime if I need it.

Yes, you can just format your SD card. It should return to 32 GB. If it doesn't, format it using your phone. (Windows tries hard to avoid knowing anything about foreign file systems and partitions, so if it sees something it doesn't understand, a lot of times it will refuse to alter the partitioning involved. Usually advanced Windows users will utilize a 3rd party disk management tool for doing these things, to get around Windows impediments).
[Verizon Galaxy Note 3 General] patttpatttyoooo:
Makes more sense, thank you for the answer. I copied the debrick image to my PC, and went ahead and formatted the SD card with EaseUS Partition Master, since Windows' utitily is a pain to deal with.
[Verizon Galaxy Note 3 General] fire3element:
Now that we essentially have a "Developer Edition" Note 3, what files can we use to flash back to stock?

I am referring to using ODIN to flash a complete stock image. Over the last few years of comments observed about the Dev Ed. Note 3, you CAN NOT use retail FW on the Dev models. It will lock the bootloader right?

That was part of the frustration with Samsung selling Developer phones, then providing ZERO support afterwards.

I am planning on performing a complete NAND wipe of the Note 3 with Odin.

My reason being, I feel that there is something borked in one of the partitions after the update from MI9 to MJ7.

If any of you were around when this phone was new, you might remember the issues with reception taking a dive off the cliff after that initial update.

I know for certain that my launch day device suffered a hefty blow after the MJ7 update. No amount of wiping and flashing has been able to fix it since.

But now that we have an unlocked bootloader, I am hopeful that we can flash back to MI9 (read: Complete NAND wipe and reflash w/Odin) and work our way back up from there.

Even if that is possible, where do we find a complete image to flash? As I mentioned before, we can not use a retail image now. At least that is what I have understood after reading lots of comments over the past few years.

Does anyone know of a source? Sammobile only has the retail FWs from what I can see.

I also have had a bad booting issue with Jasmine 5.0.2 on FW OB6.

Absolutely no pattern at all, just refuses to boot. Not talking about a bootloop. This happens at the bootloader stage where you would use vol + or vol - to boot into one of your virtual ROMs. Even when not holding any buttons, it still refuses to boot. At times, it will refuse to boot for days. Other times its just 1 of 10 tries where it gets stuck.

No amount of wiping or flashing has resolved this.

May or may not be related to faulty partitions before going to Jasmine. All I know is that there are radio issues on this phone that were not present until the update from MI9 to MJ7.

So, anyone have any info on where we can obtain an image to flash for Dev Ed. VZW Note 3 ?

The idea should be possible to flash a retail FW image and Re-Root, then unlock the bootloader again. But I am unsure if that could cause other complications considering the bootloader unlock method used.
[Verizon Galaxy Note 3 General] mouka75:
help how I just change my code to unlock the bootlaoder my cid starts with 11 plz help meeee
[Verizon Galaxy Note 3 General] bftb0:
Search this thread. This question has been answered at least half a dozen times, and always with the same answer:

at this time what you want is not possible.

.
[Verizon Galaxy Note 3 General] ozz200127:
I had root and unlocked my Verizon note 3 but soft bricked it trying to flash resurrection..so I did a of1 stock flash through Odin to start over but when I did it didn't do it fresh..it put me back to like a restore and then I needed to reroot and then try ed unlocking bootloader but the cammonds would go through..do u know way I'm doing wrong?
[Verizon Galaxy Note 3 General] bftb0:
The cammonds actually print error messages right on the screen.

If you had bothered to tell us what those messages were we would almost certainly know.

Your post is almost the equivalent of asking something like

"I have a problem, what is the solution?"

Vague. VAGUE.

FAIL.

TRY TO SUPPLY RELEVANT DETAILS.

ps did you have an SD card in the slot? Needs to be there & will get overwritten. You should be using the unlocker tool from post #218 in this thread.
[Verizon Galaxy Note 3 General] Warrior1988:
I used this for SM-900A didn't brick it nor did it unlock the bootloader but it's made for Verizon anyways just thought I would try it lol
[Verizon Galaxy Note 3 General] RaaidR:
Did you run it twice?
[Verizon Galaxy Note 3 General] Warrior1988:
Yup
[Verizon Galaxy Note 3 General] bftb0:
Did it change your CID in the first pass, and overwrite your SDcard in the 2nd?

BTW, even on nearly identical hardware (carrier variants of the SM-N900x) the DevEd signatures are different. Sort of a leap of faith that a completely different phone model from Sammy + BigRed would be susceptible to the same method... using the same signature.

Was there even a DevEd model of that phone shipped?
[Verizon Galaxy Note 3 General] Warrior1988:
Yes to all. Not sure if they came out with an Dev edition for the SM-900A
[Verizon Galaxy Note 3 General] bftb0:
:o

Well that's certainly interesting. On all the Samsung eMMC SM-N900x carrier variants, this method works by literally cloning the CID of a known DevEd phone and copying verbatim the DE sig from that device into the aboot partition of the clone.

But if a DE device never existed for the SM-900A... then what device to clone?
[Verizon Galaxy Note 3 General] Warrior1988:
Maybe I should try flashing 4.4.2 tar then try?
[Verizon Galaxy Note 3 General] bftb0:
I can't see how that is going to help anything. You have to find an owner of a DevEd of your phone model (SM-900A) and get a copy of their aboot partition. (binary) Comparison to the aboot.mbn firmware blob from the same release firmware will show the differences. If there never was a DevEd edition you are SOL.

Note that this is partly speculation; Samsung is free to do things differently from phone model to phone model. (Although it is typical for vendors to re-use technology simply because they save money by doing so.)

As an example, Android devices on Tegra (nVidia) SOCs use per-device encryption of the bootloader when they get installed; you can copy them but they are useless for every device in the world except the device they came from.

PS Nobody should be attempting what Warrior1998 tried. He took a huge gamble of hard-bricking his phone by doing so.
[Verizon Galaxy Note 3 General] shallmann:
Hello,

I get stuck at ./unlock. I get 'error : only position independent executables (PIE) are supported.' II tried flashing patch-pie.zip from this thread: http://xdaforums.com/showpost.php?p=56123703&postcount=13 and bypass-pie.zip from http://xdaforums.com/google-nexus-5/development/fix-bypassing-pie-security-check-t2797731, no change. Any idea what I'm doing wrong?
[Verizon Galaxy Note 3 General] bftb0:
What phone are you trying this on?

Did you compile the code yourself?

Not a single person on any SM-N900V release has mentioned your issue (and it has been successfully used on at least 5 different firmwares from MJ7 through OF1)
[Verizon Galaxy Note 3 General] shallmann:
I'm on SM-N900V. OF1 firmware. Rooted thanks to those wonderful people in Yemen. No i did not compile myself. Tried adb as well as terminal, same results.

It is probably my own ineptitude. What happened was I thought I applied the bootloader unlocker. Pretty sure I did not, looking back. I then (tried) installing twrp from the play store, rebooted and got the Verizon 'unauthorized software' lock. I then flashed the stock ROM. But I don't think it was a clean flash, all my apps and data were still there, it was like almost like an update, I just had to root again . It was after all that I started getting the error.

Anyway thank you for your quick response. I should have thought about it more before posting. I will factory reset, reflash and try again.
[Verizon Galaxy Note 3 General] bftb0:
Hmmm that's really odd. A restriction like that would be enforced by the default loader (or libdl.so) which I would think would be identical for everyone on the same firmware release, and you are the first person on OF1 to mention this symptom.

==>> did you happen to install a busybox or something so that the "shell" you were running was something besides /system/bin/sh in adb?

That binary seems to be dynamically linked ... so it is feasible that the complaints are about a dynamic library that is pulled in during loading, not something about the binary itself.

==>> did you install anything else that might have tweaked something in /system/lib?

If you encounter the same problem, dump your environment ("env" command) to see if there is any funny business going on with "LD" environment variables.

I don't think *anyone* in here is installing twrp using a market app BTW - they are going to the twrp.me site and downloading the hltevzw or hlte twrp image builds from there.

.
[Verizon Galaxy Note 3 General] shallmann:
I did a factory reset, from Settings first, also from recovery. Also wiped cache just for good measure. I had busybox installed before, tried again after the latest stock rom flash without it. Same error. How do I dump my environment, where do I put the 'env' command? Thanks for your help.
[Verizon Galaxy Note 3 General] bftb0:
Just type "env" in the terminal emulator (or better yet adb shell) and hit return.

I'm assuming that your "./unlock" binary is [MENTION=1923941]donc113[/MENTION] 's from post #218 - MD5 signature should be ea856efcb7de0ca8ff428522dbdc0267

is that right?
[Verizon Galaxy Note 3 General] shallmann:
Yes I used the file from post 218. Here's the environment dump:

u0_a239@hltevzw:/ $ env

_=/system/xbin/env

PATH=/system/bin:/system/xbin

LOOP_MOUNTPOINT=/mnt/obb

ANDROID_ROOT=/system

VIBE_PIPE_PATH=/dev/pipes

SHELL=/system/bin/sh

ANDROID_SOCKET_zygote=9

KNOX_STORAGE=/data/knox/ext_sdcard

ANDROID_ASSETS=/system/app

TERM=screen

ANDROID_PROPERTY_WORKSPACE=8,0

ANDROID_BOOTLOGO=1

HOSTNAME=hltevzw

ANDROID_DATA=/data

BOOTCLASSPATH=/system/framework/core-libart.jar:/system/framework/conscrypt.jar:/system/framework/okhttp.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/ims-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/apache-xml.jar:/system/framework/sec_edm.jar:/system/framework/timakeystore.jar:/system/framework/seccamera.jar:/system/framework/scrollpause.jar:/system/framework/stayrotation.jar:/system/framework/smartfaceservice.jar:/system/framework/commonimsinterface.jar:/system/framework/imsmanager.jar:/system/framework/sprengine.jar:/system/framework/smartbondingservice.jar:/system/framework/secocsp.jar:/system/framework/secEmailBC.jar:/system/framework/knoxvpnuidtag.jar:/system/framework/simageis.jar:/system/framework/qcmediaplayer.jar:/system/framework/oem-services.jar:/system/framework/org.codeaurora.Performance.jar:/system/framework/vcard.jar:/system/framework/tcmiface.jar

EMULATED_STORAGE_SOURCE=/mnt/shell/emulated

EMULATED_STORAGE_TARGET=/storage/emulated

ANDROID_STORAGE=/storage

MKSH=/system/bin/sh

MC_AUTH_TOKEN_PATH=/efs

EXTERNAL_STORAGE=/storage/emulated/legacy

LD_PRELOAD=libsigchain.so:libNimsWrap.so

RANDOM=2941

ASEC_MOUNTPOINT=/mnt/asec

SECONDARY_STORAGE=/storage/extSdCard

USER=u0_a239

HOME=/data/data/jackpal.androidterm/app_HOME

SYSTEMSERVERCLASSPATH=/system/framework/services.jar:/system/framework/ethernet-service.jar:/system/framework/wifi-service.jar

u0_a239@hltevzw:/ $