yashsingh1/xdaforums huggingface dataset:
[Verizon Galaxy Note 3 General] bftb0:
The CID is a unique identifier associated with the eMMC (flash memory) chip in your phone. It is not uncommon for handset makers to dual- or triple- source memory parts from different vendors. (Doing so gives them pricing power over their suppliers as well as mitigate delivery leadtime risks when builds are occuring) So, phones of the same model can be built with eMMC chips from different vendors.

The '15' apparently indicates a specific chip vendor; apparently this particular exploit relies on some private (vendor-specific) eMMC low-level command interface that are known for only that single chip vendor. It is likely that similar commands exist for other vendor's chips, but the exact structure of the API for those other vendors is unknown at this time, and is fairly unlikely to be the same (as they are not part of a public, standardized interface).

Where that leaves you is that you can't use this exploit. Sorry.

---------- Post added at 09:04 AM ---------- Previous post was at 08:56 AM ----------

The OP of the VZW Note 4 thread (ryanbg) is the OP of this thread. It's the same method, but with the binary over in that thread built with CID and signature blobs that correspond to the Note 4 developer edition.

So you should be asking questions about your VZW Note 4 over there in that thread, not this one.

Even though the OP recommended not doing it, if you read the threads carefully you'll see that people are successfully using the method using a root shell in a terminal emulator on the phone itself. So the broken laptop isn't a complete obstacle. You just need root on the VZW N 4 to begin with. (I'm not familiar with VZW Note 4 rooting, so I don't know what the issues are.)

good luck
[Verizon Galaxy Note 3 General] snowman46919:
Well thanks for that explanation. What I was finding was that the CID could indicate whether it was a carrier device or a dev device but your info seems to point me somewhere else.
[Verizon Galaxy Note 3 General] bftb0:
Both the Developer Edition devices and retail devices for which this particular exploit work have CIDs which start with 15 (hex). Literally, it indicates who made the eMMC chip, not what kind of software is on the chip, or how it is partitioned, etc.

That initial "15" is used by a specific eMMC (flash memory) chip maker - it is assigned by the SD Card association (sdcard.org). Looking around briefly, I couldn't find a vendor number listing to figure out who makes the 0x11 eMMC chips.

More info is in [MENTION=711482]beaups[/MENTION] Sam Dunk document (.pdf)
[Verizon Galaxy Note 3 General] thrgk:
I was rooted, and I think unlocked bootloader, I followed jrkruse instructions to unlock bootloader. I think it worked since I see the unlock custom picture when booting, however I tried to flash twrp with flashify and now the phone wont boot, saying something about going into a verizon store to get help.

Any idea?
[Verizon Galaxy Note 3 General] bftb0:
There is no "think", only you did or did not.

The way to check for sure is by booting to the Odin download mode (Vol-Down+Home+Power), at which point the phone will clearly say "MODE: Developer" at the bottom of the text lines if you succeeded. The "Custom" bit applies to the /system partition, not either of the boot partitions ("boot" or "recovery")

Your phone is behaving exactly like a retail phone would behave - it refuses to boot if it finds either the boot partition or the recovery partition are not signed correctly.

Actually, that's a very important question - can you boot into the OS, even if not the recovery? The way to try that is to pull the battery, wait 5 seconds, put battery back in, do the "Odin Mode" startup (Vol-Down+Home+Power and hold that combo until you see something besides the B&W splash screen), and if it gives you the "do you really want to do this" prompt, select Cancel - it should attempt a normal OS boot at this point. (This procedure will also clear the boot communication block, so that the phone won't keep attempting to boot the recovery.)

If you can not boot back into your OS, your only recourse is to Odin the phone back to complete stock to a firmware release at the same level as whatever you had on the phone on before (or higher), re-reroot, and start this process over. You will lose whatever is on the phone except for the external SDcard if that is the case. Note that only certain releases have a known rooting method. (Off the top of my head, I don't know what the list of releases vs. corresponding rooting methods is)

sorry.
[Verizon Galaxy Note 3 General] mrram:
Any chance for AT&T Note 3 being unlock?
[Verizon Galaxy Note 3 General] dreadcool:
Is there any unlock method for the Toshiba Galaxy Note 3? The black one?
[Verizon Galaxy Note 3 General] matsuyamakaze:
Just flash the of1 and you'll reboot back to where you started and your phone will be the way you left it.

---------- Post added at 01:51 AM ---------- Previous post was at 01:50 AM ----------

For the go to a Verizon store message this ^^^
[Verizon Galaxy Note 3 General] thrgk:
All fixed. I flashed recovery stock and it works. Still rooted and now I'm officially unlocked bootloader.

Is twrp on 5.0 possible ? I did try flashing again and same thing occured. Is there a zip I can flash via flashfire
[Verizon Galaxy Note 3 General] bftb0:
Did you flash the stock recovery in Odin, or were you able to boot into the rooted ROM while the non-stock recovery was still installed?

Good that you didn't need to start from scratch.

I got trwp-3.0.2-0-hltevzw-4.3.img to work correctly on a Safestrap'ed MJ7 (which is 4.3 firmware) The hltevzw-4.4.img wouldn't boot for me, but it probably will for you as you have later firmware. Actually, I flashed a whole bunch of different recoveries, one at a time - including later releases of stock recoveries, but also increasing versions of trwp in the 2.x series. I was trying to find the highest version of either type that would still boot correctly.

A lot of them worked, surprisingly even a few later revs of the stock recoveries (which of course are no good for rooting, I was just curious how picky Samsung's firmware was behaving).

Oh! I just remembered - the download link for the TWRP site for htlevzw is not directly accessible from the device-pick page: here it is (you have to edit the URL)

https://dl.twrp.me/hltevzw/

Anyhow, maybe the different version of my bootloader accounts for me never seeing the "go to the Verizon store" message; in my experience the non-working recoveries just wouldn't boot, but no other warnings beyond "set warranty flag". It is possible that later firmware releases are more picky... (had you really unlocked the boot loader?) but the whole point of DevEd is to allow booting of unsigned kernels.

good luck
[Verizon Galaxy Note 3 General] donc113:
You are NOT bootloader unlocked IF you get that unauthorized by Verizon message after flashing TWRP.

You also keep saying you used flashFIRE when the recommended program is flashIFY

YES TWRP on 5.0 is possible... I and many others are using it now.
[Verizon Galaxy Note 3 General] donc113:
Read this posting and the 2 after it.

http://xdaforums.com/showthread.php?p=66529235
[Verizon Galaxy Note 3 General] kingbooga:
I understand this method needs a SD card. My SD card port doesn't read cards anymore, I do have a microusb flash drive though. Would it be possible to use that instead?
[Verizon Galaxy Note 3 General] bftb0:
No, use of the external SD Card is hard coded

but ...

see this post..

And then afterwards contact [MENTION=7432781]dzejlan2[/MENTION] via PM.

Tell him I sent you his way. I helped him get unlocked (via PM), and now he can help you. :D

That's how we roll.

.
[Verizon Galaxy Note 3 General] kingbooga:
Great, will do, thanks!

Edit. dev without sd card is really easy and worked like a charm.. Although I messed up flashing twrp somehow and spent a few hours loading stock of1 on my phone over and over again. Only to realize I lost dev after the first flash.. Did it again and everything worked great.
[Verizon Galaxy Note 3 General] bbolton_98:
need help

rooted, installed su and busybox

ran samsung_unlock_n3 app

installed twrp app

installed twrp recovery

now show goto vzn upapproved software

goto download mode it doesnt show dev edition

what is the best way to either reunlock bootloader or reflash back to stock?

Got it reflashed stock recovery and reunlocked bootloader , tks for the awesome work
[Verizon Galaxy Note 3 General] donc113:
You must run the unlock app twice. The first time changes the cid... The second time unlocks the bootloader.

Do NOT load TWRP until you are SURE you are unlocked.

You can try this to get past the unauthorized software notice

Boot into DOWNLOAD mode and select CANCEL that should boot your phone
[Verizon Galaxy Note 3 General] bftb0:
:D

You and dzejlan2 both had very good reasons to do that because your card slots were not working.

But the original coder put that "SDcard debrick image" creation in there for a good reason and since it is counter to his desires, it's probably a good idea to NOT release that binary into the wild. Thanks to [MENTION=7432781]dzejlan2[/MENTION] for helping you out.
[Verizon Galaxy Note 3 General] kingbooga:
I figured as much, I was pretty hesitant to go through with it. But it is SO nice to use the micro USB as something to flash through, safe strap wouldn't let me.

Plus the whole reason I was back on XDA was because I was getting a quit loop for system ui and android keyboard quitting which lasted through a factory reset and Jasmine rom.. I felt like I didn't have much to lose.

Thanks so much for your help! Finally I feel like my phone is complete and is set up exactly how I want. I sent my first note 3 in for warranty right when 4.4.2 came out.. Was pretty unhappy when I realized how much I loved an open bootloader.
[Verizon Galaxy Note 3 General] arucarda:
Not bad advice, I pulled the card after the second time when I pulled the battery and had no problems
[Verizon Galaxy Note 3 General] riqmarmes:
Has anyone tried Temasek's CM13 without a Verizon SIM? <== Desperately wants a CM13 that works with another carrier

Edit:eek:k so you can get Temasek's CM13 working fine with non Verizon SIM by flashing hlte TWRP (not hltevzw) and getting his CM13 build for hlte (not hltevzw) and yes it will work fine (all good for me at least, using this bootloader unlock)

fyi: I had TWRP hltevzw flashed prior to flashing the other TWRP version
[Verizon Galaxy Note 3 General] onyx10:
my SD card slot is dead as well and I'm new to ADB(not totally incompetent, flashed a few ROMS, rooted, solved occasional boot loops) I'm not sure i understand this unlock without the SD card. could you PM me a walk-through(assume I'm an infant here)
[Verizon Galaxy Note 3 General] bftb0:
[MENTION=4124801]onyx10[/MENTION]

I helped dzejlan2, then

dzejlan2 helped kingbooga.

Guess who's turn it is to help you? ;) Give the king a PM.

BTW, what is it that folks are doing that ends up frying their SDcard slot? Static electricity?
[Verizon Galaxy Note 3 General] jellyhead:
So I tried the modified version for 4.4.2 and it worked OK. I had TWRP working then I flashed a ROM and now it won't boot. I'm assuming it's because now I need DEV edition roms. I tried to fin a working link for the TW rom fixer for the DEV edition

flash-tw44-sys-files-fixes-v1.0.zip

All links I found are down, anyone have a working link.....or another possible reason for this phone not booting? I could just reflash back to stock but I'd rather fix it as it is.
[Verizon Galaxy Note 3 General] bftb0:
erm, what?

"Dev Edition" ROMs - in the past - allowed the use of ROMs that used custom boot partitions. They were not available to users with retail devices as the "locked' firmware would refuse to boot anything not signed by Samsung. Owners of Dev Edition devices were free to use either "Dev Edition" ROMs, or ROMs that would work with SafeStrap ( == stock boot partition & kernel) - they could use either kind.

This thread is about a method which turns a retail device into a developer edition device through the CID change mechanism. So that means that - so long as you have actually unlocked the bootloader (as indicated by the text "MODE: Developer" on the Odin Download screen), you can use either type of ROM, "Dev Edition" or not.

That being said it sounds like your problem has something to do with borking a ROM or installing it incorrectly and almost nothing to do with this thread, so your question should probably be asked in a different thread.

.
[Verizon Galaxy Note 3 General] onyx10:
They tried unfortunately I have an 1101 CID and from what I gather I have no option of using this exploit☹️
[Verizon Galaxy Note 3 General] jellyhead:
Obviously I don't have any experience with a DEV edition phone. I was reading through the unbricking post and the file was linked indicating that it was to be used when flashing retail ROMs on a DEV edition. Not sure what went wrong then because this is a Stock Deodex NC4 4.4.2 that I've flashed several times before with no problems.
[Verizon Galaxy Note 3 General] wraithalchemist:
I need the info on the workaround for the broke SD slot also. Can someone pm me how to do this. Just bought this phone for 50 bux and now am stuck here on this horrible stock ROM ... Well jasmine anyway..
[Verizon Galaxy Note 3 General] bftb0:
Step -1. Download the eMMC Brickbug Check app from the market and verify that your device CID starts with 0x15. If it's something else than 0x15, then STOP you can go no further.

Step 0. Read entire thread from beginning to end. Yes, really - all of it.

Step 1. Download and install the Android SDK (and NDK option) to your PC. ('doze/Unix/Mac)

Step 2. Download donc113's code (provided in his .zip file)

Step 3. Modify 2 lines in the source code so that the SD card write operation does not run, but appears as if it has run successfully. It will be obvious which two lines they are.

Step 4. Compile the code with your mods using Android NDK toolchain cross-compiler (arm-linux-androideabi-gcc etc)

Step 5. Follow the instructions in the OP using your binary.
[Verizon Galaxy Note 3 General] wraithalchemist:
OK so if you mean does it start with 15 then yes it does. Below the string of numbers there is a 0x00 next to fw but my other says the same thing tho and everything was successful that on since it had a working SD slot.

Edit: I have ran this already on the stock ROM before I flashed jasmine. It was before I knew that it had dead card reader so first part is done. It is identical to the other that it worked on. Number for number and letter for letter. I just need to do the last step now.
[Verizon Galaxy Note 3 General] narcosis34:
Guys anything i tried i cant change the baseband version and with no verizon sim i dont have LTE , anyone have an idea how to resove this ?
[Verizon Galaxy Note 3 General] bftb0:
Wrong thread.
[Verizon Galaxy Note 3 General] ~~Reaper~~:
You guys are awesome!! Im back to a noob at this after 7 years of stock phones. This was explained nicely, even I could follow it. :)
[Verizon Galaxy Note 3 General] S.N.@.K.3:
need help

As [MENTION=5018105]wraithalchemist[/MENTION] and [MENTION=2341536]bftb0[/MENTION] described, I understood 50 to 60% but I want to will it work for my Cid i have uploaded the scren**** also. And if it wont work what I do ? In downloading mode Developer mode is not showing thts means I have a locked bootloader? And I cant install Rom? Recovery? Root?

Please help me I have been trolling this forum for 1 week and I am very confused.
[Verizon Galaxy Note 3 General] bftb0:
From the image you posted, your CID starts with 0x11. In brief, your phone is not capable of being unlocked with this method.

If you read through this thread more carefully you will find the more detailed explanation of why this applies to only one vendor's (Samsung) eMMC flash memory chips in [MENTION=711482]beaups[/MENTION] document "Sam Dunk". Search this thread (or XDA) for "Sam Dunk" if you are curious.

I would answer your question about root - which is a separate issue (and a prerequisite to using this method) - but this thread is not about getting root. Ask that question in the appropriate thread/forum, not this one.
[Verizon Galaxy Note 3 General] xaronax:
I'm about to give up on this myself. I followed all the instructions to the best of my ability. I'm out of bandwidth for the month and cannot get it to work. CID 100% starts with 15. I've been running BajaROM for ages and I'm finally tired of it. My SD card reader is fried as well. I have no idea why. I honestly think it got fried with software. I've literally only used it once and I only take my phone apart on my ESD mat. That's another matter. I'm going to try to follow this chain of people helping people and get advice on how to build my own version without the SD card requirements, but I don't think I'll even make it that far. Android Studio and the NDK took me 3 days to download.

My current problem is that when I run the script, it tells me;

Do you understand the implications of these warnings?

(Yes/No)

Yes

[-] this is for (some) Samsung devices onlly

[-] it WILL kill other devices. go back to google

10|root@hltevzw:/data/local/tmp #

I don't even know where to begin parsing that. I obviously have a Verizon Note 3 connected, with a CID starting in 15. Absolutely no idea what I have done wrong. I don't even know if I should be running it in adb shell in system, recovery, or bootloader. The instructions do not say anything about it.

If anyone gives a crap, I'd sure welcome the help.
[Verizon Galaxy Note 3 General] bftb0:
The 2nd pass of the program - as publicly distributed - does require you to have a working SDcard slot (and a card in there). But your first problem:

is that the first release (ryanbg) of the tool seemed to be sensitive to OS version - it couldn't parse /proc/cmdline correctly, and failed with the above error on many phones for which the exploit is perfectly valid. donc113 fixed this particular problem in his release; but his release also requires a working SD card slot.

Try PM'ing the prior users in the thread who had non-functioning SD card readers. It is my impression that they based their code compilation off of donc113's code, so the 2nd problem (above) is fixed, and the requirement of needing a SD card is removed. I think everyone who went down this route succeeded.
[Verizon Galaxy Note 3 General] donc113:
More than likely your SD card is NOT fried and if it is... It has nothing to do with the unlock program. The error message you see (and as explained by [MENTION=2341536]bftb0[/MENTION]) occurs when the original program tried to read the command line and failed due to versioning... The program then exited and NEVER does anything with the SD card.

That error has been fixed and the current version (page 22 of this subject) works fine on Note 3's with a eMMC chip with cid starting with 15.

The program WILL overwrite a micro SD card you have in the slot above your SIM card. It is designed that way to allow you to avoid hard bricking your phone in case something goes wrong.

The program needs to be run twice... First time will change your CID and reboot. Nothing is done first time thru to the SD. The 2nd time unlocks the bootloader.. And reboots. And that is when the SD card is overwritten.

Once you boot the 2nd time... There is no longer a need for that inage on the SD card, so it can be reformated in settings->storage after you 'unmount' it... And you will regain full capacity of the SD card.

I simply used a spare microSD I wasn't using for the process.
[Verizon Galaxy Note 3 General] godrick15:
I'm on Jasmine Rom with Multisystem. Can this run over Multisystem?

How do I start fresh? My SD card is partitioned and I want to uninstall Multisystem and just have TWRP.
[Verizon Galaxy Note 3 General] bftb0:
This method is independent of whatever ROM you currently have on your phone... and can succeed, so long as your phone is:

- a SM-N900V [Verizon Samsung Galaxy Note 3]

- must also have a CID which starts with 0x15 [indicating it was built with a Samsung eMMC flash memory chip], and

- it must be rooted.

Once you have completed this operation and verified it's success - by booting into Odin mode and seeing the text: "Mode: Developer" at the bottom of the text (upper left corner of screen) - then you are free to install a custom recovery into the recovery partition (which is /dev/block/mmcblk0p15 on the SM-N900V)

You should absolutely verify that your newly installed custom recovery is booting before you take any next steps.

If you complete these activities successfully - your existing ROM behavior will be absolutely unchanged... and then it will be time for you to ask questions about "what next?" in a different thread - not this one. Even the question "how do I install a custom recovery?" doesn't really belong in this thread, so consider this a bonus gift:

Get either the -4.3 or -4.4 TWRP recovery for "hltevzw" from here* and transfer it to your /sdcard (internal).

Use a terminal emulator, and get a root shell with the "su" command:

$ su

# cd /sdcard

# dd if=twrp-3.0.2-0-hltevzw-4.3.img bs=2048 of=/dev/block/mmcblk0p15

Note that "p15" is incredibly important - if you screw up and write to the wrong partition, you could brick your phone permanently. Before you hit return, check that twice - maybe even 3 times. Then count to five and look at it again to make sure it is correct.

good luck

*PS if you are on old bootloader firmware - e.g. MI9, MJ7, or MJE - you won't be able to boot the TWRP "4.4" recoveries. But the -4.3 recovery seems to work just fine on MJ7.
[Verizon Galaxy Note 3 General] xaronax:
Thanks for the advice. SD Card is not an option for me. The reader simply does not work. It hasn't worked for months. I don't even know if this is worth my time because I can't even get adb to sideload into Safestrap. I'm pretty much giving up. Even if I get the phone unlocked, I have no way to push a ROM to it. Very frustrating.
[Verizon Galaxy Note 3 General] bftb0:
/sdcard on the SM-900V is not actually a SD card.

You can use adb wirelessly if you want to avoid using a USB cable, or what the heck just use Dropbox or something. Mail it to yourself and download it.

PS. If there is an Android phone and a Windows PC that can't talk over a USB cable, about 99.995% of the time that is a Windows issue. The same PC (hardware) booted into Linux would have no problems.
[Verizon Galaxy Note 3 General] xaronax:
I think you're misunderstanding my issues. My SD card slot does not function. At all. Zero. I cannot copy files to it so that I can flash them in recovery. The phone has absolutely no issues talking over USB in everything except recovery. Unless you know some magic method or there's something I'm too stupid to understand, I do not know how to install a ROM without an SD card or ADB. ADB is broken in recovery (Safestrap). It took me all day yesterday to get Safestrap to update to the latest version. ADB works perfectly fine in system and in the bootloader. It does not work in recovery. I do not know how to troubleshoot something that literally hangs when I try to put it in sideload mode. Brick wall, end of attempt. I don't have the time, patience, or bandwidth to get a Linux image installed on something and fight with getting drivers working, and I really don't have the patience to try to follow the rabbit hole of steps that were recommended to get a random string of people to help me compile a custom version of a tool with zero instructions. Not even remotely close. The phone is such an aggravating broken mess that I can't even stand to use it for anything but tethering. It's most likely going into a trashcan by the end of the week, and I'll move on to something that isn't Samsung.
[Verizon Galaxy Note 3 General] donc113:
Alright..... Let's resolve 2 issues... By SD card you mean the 'external' SD card that plugs in on top of the SIM card... That is what isn't working for you... correct?

If you don't care about the phone and wish to simply toss it in the trash... I will EMAIL you a version of unlock that will skip the write to external SD.

This presumes you are already rooted.