yashsingh1/xdaforums huggingface dataset:
[Verizon Galaxy Note 3 General] donc113:
That's what I did....after that...it will show the custom and unlock symbol....not an issue for me.
[Verizon Galaxy Note 3 General] mrram:
Which TWRP Recovery?

Which TWRP Recovery are you installing?
[Verizon Galaxy Note 3 General] donc113:
The newest twrp-3.0.2-0-hltevzw-4.4.img
[Verizon Galaxy Note 3 General] njdan30:
awesome work i went the adb route no problems at all awesome being able to make full backups again, use titanium back up and root explorer etc.i put my s6 and crappy jailbroken iphone 6plus away to try this on two old notes laying around.cant wait to flash some roms soon. thanks for all the hard work
[Verizon Galaxy Note 3 General] bftb0:
Well you know as soon as you say that someone's going to use it for something else. For instance, me!

It worked a treat on a MJ7 / 4.3 SM-900V (Yes, I verified my CID before I started.)

I might now have the worlds only VZW MJ7 dev ed N3, LOL. Well maybe not, maybe there are some MI9's floating around ;) :D

Now all I need to do is figure out what to do with my newfound freedom. (Probably find out that later kernels won't be happy with a MJ7 bootloader? )

Thanks for building that - ryanbg's build wouldn't let me past the /proc/cmdline thing on MJ7 either, and mis-directing his binary to other files ( e.g. /data/zzzline instead of /proc/cmdline ) didn't change that result.

Thanks to [MENTION=711482]beaups[/MENTION], [MENTION=766721]ryanbg[/MENTION], and [MENTION=1923941]donc113[/MENTION].

PS. One thing that struck me as odd is that as soon as I had completed the 2nd reboot, my Win7 PC wanted to download new drivers for the phone - almost as if the USB root hub was seeing new PID identifiers for the phone as a result of changing the CID. I guess that could make sense for the mass storage driver, as the CID is a eMMC identifier, but the WU driver downloads seemed to involve gadget drivers and ADB drivers. Well, I have a list of all the prior VID/PID IDs, I guess I can take a look after a little sleep.
[Verizon Galaxy Note 3 General] ryanbg:
I think it's insignificant as far as VID/PID. You can unlock latest OTA also, so shouldn't be an issue running latest kernels.
[Verizon Galaxy Note 3 General] bftb0:
Thanks. My impression is that doing so requires using stock Odin flashes, re-rooting, and reapplying the CID/aboot sig change... so I'm still subject to BL anti-rollback and rooting availability on a per release basis, even having dev ed privs. Is that more or less correct - that dev ed behavior doesn't get me any additional liberties wrt kanging arbitrary images into an Odin flash bundle?

(For instance is it possible to mix a pre rooted /system image with an otherwise stock Odin flash set, or is all the signing enforcement still active on a dev ed phone?)

If anyone wants to throw out a few N3 must-read thread URLs on these topics, I'd be grateful:

(1) Odin mix-n-match / advanced usage

(2) Dev Ed user's guide

(3) Achievable rollbacks

cheers
[Verizon Galaxy Note 3 General] ryanbg:
There's root for latest OTA. My advice is to Odin to latest, and then unlock. Odin won't flash because of some goofiness with the image signature and the dev signature, since the dev signature is hashed and signed along with the rest of the code image, so it'll fail if you try to Odin. You can DD the image just fine with dev sig/CID, but it's safer to just unlock the organic way.
[Verizon Galaxy Note 3 General] dzejlan2:
My phone cant read sdcard. Is there any way to unlock phone without sdcard?
[Verizon Galaxy Note 3 General] mrram:
Will you guy provide help to unlock AT&T Note 3 bootloader?
[Verizon Galaxy Note 3 General] bftb0:
I miss fastboot. And phones with fewer than 25 partitions, too. :D

Assuming your SD card slot is dead, the answer is yes - but only if you compile beaups' code - with the CID / sig modifications given by openbottle... AND comment out the "backup_loaders()" usage inside of do_dev_loaders() in beaups' code samsung_unlock.c

That's an exact recipe for what you need to do if you don't have a working SD card slot on your SM-N900V. Note that beaups put that (safety backup) in the code for a reason. But it is a safety feature, not a requirement of the CID change. The binaries provided to date though check that the backup copy is made correctly before writing the dev ed signature into "aboot", so you can't use ryanbg's or donc113's binaries on your device - you will need to compile from the sources.

.
[Verizon Galaxy Note 3 General] donc113:
No, an SD card is required. Why can't your phone read an SD card?
[Verizon Galaxy Note 3 General] jellyhead:
Is it just a dead SdCard? I have a bunch of old ones laying around and used one of those so my current card wouldn't be corrupted if something went wrong.
[Verizon Galaxy Note 3 General] dzejlan2:
Sd card slot is dead :(
[Verizon Galaxy Note 3 General] donc113:
My binary has been updated and should work on older and newer OS Verizon Note 3's
[Verizon Galaxy Note 3 General] screwedbyexisten:
We can reformat the SD when its done right? the 20 partitions is a bit nuts and android only mounts the small FAT partition.
[Verizon Galaxy Note 3 General] donc113:
Yes
[Verizon Galaxy Note 3 General] beaups:
Have you posted source for the binary you created/are sharing?

--beaups
[Verizon Galaxy Note 3 General] donc113:
No..

It's your code, slightly modified... I would be happy to PM it to you.

Esentially all I did was add a 4th CID4 to the check and changed dev_cid[] and dev_sig [] to the appropriate Note 3 values.
[Verizon Galaxy Note 3 General] bd177:
Yes you can reformat.
[Verizon Galaxy Note 3 General] beaups:
You should post it (just include it it any zips you create or post).

--beaups
[Verizon Galaxy Note 3 General] donc113:
Ok..

Not a problem....I will redo the zip tonight and replace the current zip
[Verizon Galaxy Note 3 General] en11gma:
i had my sm-n900v on stock official of1

i then rooted and bl unlock with the samsung_unlock_n3 a ways back

before that was released there was another script called "samsung_cid" that would let you view your current cid and also let you change the cid

i have my original cid in a txt file.

heres my problem

i had to revert to stock official OF1

i did not change my CID back to original (not sure if there is a way with the new apk) but here i am

using emmc brick debug tool shows i have the new CID for bl unlock but of course odin mode shows i do not have the developer edition

so im about rdy to root and do this all again but does the unlocker need me to put my original cid in first before i run the program to bl unlock again?

thanks
[Verizon Galaxy Note 3 General] en11gma:
couple questions.

i was stock OF1

i rooted with arabic tool.

i then did the unlock with "samsung_unlock_n3"

i did not have busybox installed.

odin shows im developer edition.

anyway to fix the damaged sd card error besides formatting?
[Verizon Galaxy Note 3 General] en11gma:
whats going on with sd card repair from within android?

how do we fix?

format/erase card does not work

aparted does not work

always says its checking for errors

i have used yemen unlock before and never got that padlock custom screen. (i even removed kingroot and installed supersu over it)

this time i used that arabic tool and i have custom padlock screen

i do not want to install xposed

i would like to know why or what is causing it to trigger?

note: i have had the custom padlock screen before and it went away by itself. this time it dont seem like it is gonna go away by itself
[Verizon Galaxy Note 3 General] bftb0:
No. In fact it wants to see that the CID has been updated to the DevEd value before it writes the signature blob to aboot.

As for the "custom" image that is dependent on attribution processes which run after the phone has booted (possibly also in the stock recoveries as well). It can disappear, but it won't happen immediately after a flashing to full stock - those attribution processed need to work for a while before that happens. (Think of it this way - there is no way that the bootloader scans all of /system /data et cetera during booting in order to decide whether anything has been changed - the phone would take forever to boot if that were the case).

If you flash a non-stock boot or recovery image on the phone - even with the developer mode enabled - you will trip the Knox Warranty fuse. (I'm not sure if it was absolutely determined that it really is an irreversible fuse, ryanbg might know if anyone does). I suppose it is possible that if the Knox warranty fuse is set, you'll always see "Custom", but I don't know if that is true or not.

If you are worried about the "Custom" display, then I suppose that means that you are worried about the warranty flag too. If that's the case, you probably shouldn't be doing any of this.
[Verizon Galaxy Note 3 General] wanb1i:
seems the apk download link isn't working, is there another one?:confused:
[Verizon Galaxy Note 3 General] bftb0:
No.

The original post said that the card would be overwritten. That's not damage, it's what it was supposed to do.

beaups' code wrote 0x10000 blocks each of block length 0x1000 (total of 256 MB) to the beginning of the card. So the original bootblock and partition table (if any) is gone, and the first 256 MB of the card are overwritten with the first 256 MB of flash memory data from your phone.

The purpose of that operation was to have a "debrick image" on a SD card so that if something went horribly wrong, you could still recover from that disaster using ODIN. (The phone detects problems in booting and will boot off of the copies of all the bootloader partitions on the SD card, assuming that they pass all signature checking, just like in the ordinary boot) See here.

If there were some precious files on your SD Card and you were fortunate enough that the data was stored beyond the first 256 MB on the card, the data is still there; but you will need a forensics tool to recover them. (If that's what you mean by "fix").

If you have a spare 256 MB on your PC someplace it's a good idea to "raw dump" that off the card before you re-format so you will have a debrick image if case you ever need it.

If you just want to have a formatted card back, go ahead and format it. Probably not with Windows, as there will be a new UEFI/GPT on the card (with 25 partitions!), and Windows tends to get confused if it sees anything out of the ordinary. But you can try. Or just dd if=/dev/zero some zeros onto the card for a couple of MB before handing it to windows for formatting.
[Verizon Galaxy Note 3 General] donc113:
Source code added to zip and posting updated with new zip
[Verizon Galaxy Note 3 General] 1Xfan:
I have been out of the VZW Note 3 loop for a while; not much going on for many months. Then I saw this new posting the other day and wet my pants! :D Sweet & many thanks !!!

I am still on 4.4.2 Biggins ROM; never jumped to 5.+.

I am rooted, and with flashfire. Is it safe to assume this exploit will work on the 4.4.2/ NC4 bootloader? ... without having to flash to 5.0+ (?)
[Verizon Galaxy Note 3 General] bftb0:
I did it on MJ7, and it worked there :D

And now I have a marshmallow ROM (cm13) and a true TWRP (4.3) recovery running on top of MJ7 firmware.

Never lost root - I either had it in the external recovery, or the ROM, or both.

Your Knox warranty flag will get tripped though as soon as you install a custom bootable image (recovery or boot partitions)

good luck.
[Verizon Galaxy Note 3 General] arucarda:
Wiped my sdcard...

Done this 3 times, 2 out of 3 wiped the sdcard, I recommend pulling it first. Running ob6
[Verizon Galaxy Note 3 General] bftb0:
Bad advice.

You read this part, right?

If you look at beaups' code you will see that

a) the program needs to run TWICE (just as the OP's post instructs)

b) on the first run, it only changes the CID

c) the SD card is overwritten on the 2nd invocation of the program or anytime it finds a CID which matches the DevEd CID.

d) the program will not perform the final and most crucial step of the process - writing a signature blob into the aboot partition - if it fails to find a SD card and write to it.

So if you ran the program three times, then yes, it would have overwritten the SDcard two times. And if you don't use a SDcard, the program will error out rather than completing the process.

That's what it is supposed to do. It is creating a safety mechanism known as a "debrick image" SD card (look it up) that can boot the phone into Odin Mode if a disaster happens.

So, no. Follow the instructions as given, and use a spare SD card. It's probably a good idea to save the SD card "as is" as a safety precaution.
[Verizon Galaxy Note 3 General] donc113:
From 4.4.2 (rooted) i ran my version of unlock... Worked fine... Loaded TWRP, (that does void warranty bit but mine is LONG out of warranty), flashed Jasmine 6.1 and the lean kernel. Zero problems (i followed the instructions and made a backup before flashing Jasmine and then wipped phone) and all is working well... I am still using NK1 modem and zero issues for phone or data.
[Verizon Galaxy Note 3 General] 1Xfan:
That's too bad it voids nox:(

I'm sure there is a way to disable nox. Someone will find it.

Good to hear it worked for you, and I'm not the only one who didn't jump to marshmallow.

Sent from my SM-N900V using Xparent Skyblue Tapatalk 2
[Verizon Galaxy Note 3 General] bftb0:
This is a sincere question, not snark: does anyone own a Note 3 which is still under warranty?

If the phone's warranty has already expired due to time since purchase... then isn't that little flag just a meaningless cosmetic detail?

I tend to purchase gear and use it until it's seriously obsolete (close to zero value), so I don't have a feel for whether an Odin flag affects used equipment value.
[Verizon Galaxy Note 3 General] donc113:
There's two flags/fuses. Knox and warranty. Flashing TWRP instead of the standard recovery will "blow" the warranty fuse but NOT the Knox fuse.
[Verizon Galaxy Note 3 General] icedventimocha:
Thanks to all involved. Used the apk, had to do it twice but that was most likely due to the delay in the supersu promts.
[Verizon Galaxy Note 3 General] djshaff:
God I can't believe this actually happened! So coming from 4.4.2, I'm unlocked, did full whip and running Dirty Unicorns, and everything works beautifully, huge thanks to donc113 on post 217 to get this to work on 4.4.2!! Only problem, pull your extSD card before you run this! It nuked mine, and everything on it, it was mentioned once early on in this thread but I skimmed past and forgot while looking for my fix!

Also, I think I am on MJE modems, or at least one of the earlier ones that seemed to work better.
[Verizon Galaxy Note 3 General] icedventimocha:
So if we need to Odin back to stock do we use Normal or the Dev version tars?
[Verizon Galaxy Note 3 General] thunderblaster88:
Dev, we have dev phones now
[Verizon Galaxy Note 3 General] icedventimocha:
Thanks. Thought I had bricked testing out a stock rom I'm trying to get together, but finally back to normal (until the next test most likely lol)
[Verizon Galaxy Note 3 General] NeoHiPPy1980:
This is a bad idea and should *NOT* be recommended to other folks looking to do this. Yes, it nukes your card, but for a *reason*-- read post #253 by bftb0; It's a debrick image, in case someone/something screws up. Rather than telling people to pull their cards, explain that they should use a card they don't mind getting wiped out.

Don't encourage bricking; Rather, *explain* why and what happens.

That said, I'm glad to hear everything's working well for you! [emoji2] Since you're running Dirty Unicorns, have you noticed whether or not S-Pen features work? I read somewhere in this thread that it doesn't, but I'm still hoping to find something different or a method to implement it.
[Verizon Galaxy Note 3 General] matsuyamakaze:
I cannot unlock my bootloader I've tried over and over. I'm on jasmine 6.0.1 sm900v I've followed videos tutorials nothing. I'm on of1 idk what to do next.

---------- Post added at 06:21 PM ---------- Previous post was at 06:19 PM ----------

Also samsung_unlock_n3 won't stick to temp folder.
[Verizon Galaxy Note 3 General] ExpialZLD:
Curious, how do we go back to a stock note 3 without dev?
[Verizon Galaxy Note 3 General] bftb0:
Not to mention that (as the code is currently written) samsung_unlock_n3 won't even complete the job it was created to do without an SD card present.

I guess that makes it a (bad idea)^2.

I suppose someone could comment that out of the code; then beaups' prophecy will be complete:

[MENTION=6029523]matsuyamakaze[/MENTION]

You really should cut-n-paste some output from your session. "tried over and over" is a vague and useless description of both what you attempted as well as the results you got. "samsung_unlock_n3" prints error messages if they occur. So do most Unix commands.

If you want us to guess, then OK, here goes: I guess... ummm... lima beans. Or 37, whichever comes first.

.
[Verizon Galaxy Note 3 General] daddylonglegs:
Sorry if this has been answered but does this work for the Verizon version of the phone? The SM-N900V?

Basically I really care about root the most. After I unlock the bootloader, just install a custom recovery then SuperSU? Any specific custom recovery needed for this phone? Any specific version of SuperSU? Thank you. Sorry if this has been answered but does this work for the Verizon version of the phone? The SM-N900V?

Basically I really care about root the most. After I unlock the bootloader, just install a custom recovery then SuperSU? Any specific custom recovery needed for this phone? Any specific version of Super
[Verizon Galaxy Note 3 General] bftb0:
This forum is for the SM-N900V after all. So, yes.

This does not give you root; you need to already have root to do this.

This provides more freedom in the sense that you can use a true recovery and/or custom boot/kernel, not just a "intercept-a-stock-boot" method. That means more choices of ROMs and less likelihood of accidentally losing root if something goes wrong with your ROM, as you will have a 2nd booting method (the recovery) which is rooted.

The first thing you should do - even before doing this - is to back everything up** on the phone that you possibly can to an external computer. (Yes, that's probably many GBs of stuff.) This method is not supposed to wipe anything other than an SD card, but accidents do happen. Get yourself a cheap spare SD card, say 2 GB or 4 GB, and use that for this procedure instead of your daily driver SD card.

Install a custom recovery. (Note that doing this will blow the "Knox warranty" fuse the first time it is booted.)

The first order of business after you install a custom recovery (e.g. twrp) is to make a true backup** using the recovery. This will allow you to restore whatever you are currently using. (Note that psuedo-backups that involve stock-boot-interception are only useful for "slots" within that method, not the rooted stock ROM itself)

After that, the SuperSU you use should be guided by the instructions from the creator of the ROM that you intend to install.

Once again, you need to have root already in order use this technique - so you probably already have SuperSU installed.

Use the version of SuperSU your ROM builder recommends. Note: for the SM-N900V, use the hltevzw versions of TWRP, not "hlte".

If you have ancient firmware (e.g. MI9, MJ7,MJE,NC4) you might have to use 3.0.2-0-hltevzw-4.3 instead of -4.4 but I would recommend the latest.

You're welcome.

Now you are just repeating yourself.

** Backups can be huge - more than 10GB. If your phone (fake /sdcard, a.k.a. "internal storage") or real SD card doesn't have that much free space, the easiest way around this obstacle is to get yourself:

- a USB OTG cable

- a high-capacity micro SD Card (32 GB or 64 GB, faster is better)

- a USB card adapter stick (I'm using an IOGear USB 3.0 adapter)

TWRP allows you mount USB storage devices, so long they are FAT formatted. (In principle you could use an externally powered USB hard drive, but most people have such HDDs formatted as NTFS volumes and the small portable ones are not typically externally powered - powering one from the phone is probably not a good idea)
[Verizon Galaxy Note 3 General] marloweloy:
For those of you who are asking about the version of TWRP to use, it is so easy. Once you have flashify installed, just click on "Recovery Image" under the "flash" tab and it will ask you if you want to install TWRP. That's it. :)
[Verizon Galaxy Note 3 General] Mike_Disturbed_1992:
How, in the world, does this even work?

Where do I put the Samsung_Unlock_N3 file? Do I extract it or leave it as a zip file? The terminal emulator won't find the file at all :confused: please help. I'm running safeatrap right now and I really just want to see how Cm13 is. Haven't had much experience with terminal emulators. Thanks!
[Verizon Galaxy Note 3 General] jellyhead:
I used the SamsungUnlockerN3.apk posted earlier in this topic and it worked perfectly. I initially removed my SDcard to prevent data loss but the realized it is required an SDcard to perform the unlock. I just used an old SDcard and it worked. Make sure you have an SDcard in the slot.
[Verizon Galaxy Note 3 General] Mike_Disturbed_1992:
I get to the part where it asks me to type yes, I type yes, then it gives me a message that says it will work for some Samsung devices only and it will kill other devices go back to Google 10|u0_a203@hltevzw:/

Did you get this message? What should I enter after it says that?
[Verizon Galaxy Note 3 General] bftb0:
That happens for one of three reasons:

(A) you are not running 'samsung_unlock_n3' as root.

(B) you are using the OP's binary (there was a bug reading /proc/cmdline that seemed to be release dependant, possibly a SElinux issue). Use donc113's patched version a little later in the thread.

(C) your phone is not made by Samsung
[Verizon Galaxy Note 3 General] 1Xfan:
The op needs to be updated! ... Perhaps a new thread should be started; That contains script(s) exploits that work on all bootloaders.

Sent from my SM-N900V using Xparent Skyblue Tapatalk 2
[Verizon Galaxy Note 3 General] Mike_Disturbed_1992:
THANK YOU [MENTION=1923941]donc113[/MENTION]

Any chance you might want to make this possible on the Retail Verizon Note 4? They finally have boot loader unlock but my laptop is broken! Also I can confirm that your method works also with 4.3 (that's what my note 3 was on) mi9!
[Verizon Galaxy Note 3 General] donc113:
I didn't write the original code, [MENTION=711482]beaups[/MENTION] wrote it. I just made some minor modifications for the Note 3 based on information from [MENTION=1949695]jrkruse[/MENTION] and [MENTION=766721]ryanbg[/MENTION].

I have no idea if it'd work a note 4 or brick it. But one of the other 3 may know. If nothing else.. Someone would have to provide a cid and dump of aboot from a dev edition Note 4.
[Verizon Galaxy Note 3 General] snowman46919:
My CID starts with 11. I am not sure where that leaves me. I used the root method that was recently posted on here.