yashsingh1/xdaforums huggingface dataset:
[Verizon Galaxy Note 4 General] wy1d:
It was the same phone. I gave my aboot to ryanbg to make the flashable image.
[Verizon Galaxy Note 4 General] azumandias:
The bootloaders are signed for each individual device. His DE bootloader wouldn't work in a different phone, RE otherwise.
[Verizon Galaxy Note 4 General] christiebunny:
I don't mean to derail the thread, but I'm curious..... so here's a newbie question from someone *without* a DE, that's eagerly awaiting root, and wanting to learn more.... Is it the lack of PGP signature that's actually what locks the RE Note 4's? i.e. 'aboot w/ sig' == unlocked, 'aboot w/o sig' == locked?
[Verizon Galaxy Note 4 General] azumandias:
Thanks for the file size confirmation. Yeah, I have a backup of each partition on my phone, sd card and computer. I am not losing this bootloader.:laugh:

That is s very intriguing idea but we don't have the other half of the key to even try signing it. Has anyone posted a RE bootloader for comparison?
[Verizon Galaxy Note 4 General] gatesjunior:
You have to have the Private key in order to sign the bootloader. I have already thought through this whole process. Even if I left the keys in the file, as is, and then tried to insert my CID values in the bootloader, it will fail.

(Dan Rosenberg credit to statement) -> The bootloader uses an RSA-2048 public key contained in aboot to decrypt a signature contained in the boot image itself, and compares the resulting plaintext against the SHA1 hash of the boot image. Since any modifications to the boot image would result in a different SHA1 hash, it is not possible to generate a valid signed boot image without breaking RSA-2048, generating a specific SHA1 collision, or obtaining Samsung's private signing key.
[Verizon Galaxy Note 4 General] azumandias:
So you're getting right on top of breaking the RSA-2048, right? :laugh:
[Verizon Galaxy Note 4 General] ryanbg:
Samsung uses SHA-256 now. They also have two keys, the Odin/boot/recovery/etc... key, and the CID signature key.
[Verizon Galaxy Note 4 General] bdorr1105:
hey [MENTION=766721]ryanbg[/MENTION], if I send you my aboot, can you make a flashable. I didnt screw up yet and I dont think I will, but just in case...Also if its cool, do I need to strip the 00s before I send it or do you do that? I am not sure I understand the why and when you strip them from reading these posts.
[Verizon Galaxy Note 4 General] ryanbg:
Just send me your aboot and I'll take it from there.
[Verizon Galaxy Note 4 General] bdorr1105:
Hey ryan did you get my aboot...I dont know how to attach in a pm, so I uploaded it to devhost and emailed the link to it....Was the link good?
[Verizon Galaxy Note 4 General] bdorr1105:
???? What happened everything ok
[Verizon Galaxy Note 4 General] gatesjunior:
He will get back to you. I have noticed at times it takes him a while to get back to you. But, he does get back with people. Send him another PM as a friendly reminder.. :) If you don't hear from him, send it to me and I will take care of it for you.
[Verizon Galaxy Note 4 General] ryanbg:
Sorry guys, busy with the holidays and family! I do have your bootloaders, and I will package them! Just be patient:)
[Verizon Galaxy Note 4 General] jon3640:
Hey guys, is it even remotely possible to use an aboot from developer edition and run it on retail version?? This might sound dumb but worth asking question though... I know im just a junior member here on the forums but got some 4yrs dev. Behind the scenes. The 2 device are the same physically correct? With different signed software?? The N4 is how ever my first bootloader locked device. Just throwing this out there..
[Verizon Galaxy Note 4 General] jpcalhoun:
My understanding is that will not work because each is individually signed and therefore device specific.
[Verizon Galaxy Note 4 General] scarygood536:
no not as of yet. The aboot is assigned specifically for each DE device. they have unique keys per device. Read back a couple pages it's mentioned a few times. We don't have the ability to sign or own keys, but if we did maybe it would be a different story. I'd like to see samsung release a tool to do this. Void our warranty. That way the demand for DE are met and everyone is happy right? :P
[Verizon Galaxy Note 4 General] bdorr1105:
Hey Ryan thanks man... Yea I politely stopped I figured you would get around to it... Anyway thank you for the update..... Does you usually pm or just post in here with the flashable aboot?
[Verizon Galaxy Note 4 General] anticloud:
successfully restored aboot, but not from unlocked state..

using EFS Pro, and odin, have reflashed a saved aboot.mbn - where the aboot.mbn was backed up using the latest EFS Pro Beta tool etc... it produced a flashable tar etc... and no ill effects have been noticed at all..

as far as restoring from a locked bootloader, have not had the fortitude to try - being nice here...

rob g
[Verizon Galaxy Note 4 General] salmanslick:
how do i know

how do i know if my note 4 developer edition has an unlocked bootloader ? i bought it off ebay
[Verizon Galaxy Note 4 General] radionerd:
Put it into download mode (turn off, hold 3 buttons down, power, home, volume down) enter download mode, then look It should say (Mode: developer)
[Verizon Galaxy Note 4 General] salmanslick:
got it thanks
[Verizon Galaxy Note 4 General] anticloud:
giving up a developer edition is kinda like giving up an unlimited data plan w / your carrier...

and one who is able to find a dev edition, well, that's just a good day all around!!
[Verizon Galaxy Note 4 General] radionerd:
I tried to make a aboot.tar.md5 for a DE owner that locked his bootloader with the LP OTA, his aboot,mbn is about 10kb larger than the one [MENTION=766721]ryanbg[/MENTION] made. Odin fails upon flash of my tar. The guy has a complete backup of all his partitions.

The attached screen capture shows the sha256 is about 10kb larger. All of his partitions were pulled out using EFS Professional, then decompressed back to aboot.mbn. Any help?

Thanks!

View attachment 3245335
[Verizon Galaxy Note 4 General] radionerd:
OK,

My aboot.mbn has the exact same 10kb of data at the end.

I guess a should trim this????

View attachment 3245344
[Verizon Galaxy Note 4 General] radionerd:
Glad you got it going again!!!!

All I did was make a flash-able TAR. from your backup

You get praise for making a backup of aboot! Everyone that has a Developer Device should have a copy of aboot Here is my easy guide.

Here are some of the guys that figured this out They should get the praise: [MENTION=766721]ryanbg[/MENTION], [MENTION=4243514]Hashcode[/MENTION] [MENTION=4395895]BeansTown106[/MENTION] [MENTION=4939386]Surge1223[/MENTION]

Cheers!

Radionerd :good:
[Verizon Galaxy Note 4 General] azumandias:
OK, I have to ask... When we get an ODIN flashable tar for our DE's, we will be removing the bootloader from that tar and flashing ourselves into LP. So, did you try simply flashing your aboot.mbn over the LP version to see if you had a LP DE? Wouldn't that be the same as flashing a LP tar minus the aboot.mbn?

If not, is there anyone willing to try this? That is, make sure you have a good aboot.mbn backup, take the OTA, then flash the aboot.mbn to get a LP DE. Please, please don't try it unless you are sure of the consequences, but is there anyone willing to try it?
[Verizon Galaxy Note 4 General] anticloud:
in my first attempt to restore my phone back to a de with kitkat anj5, i did flash the aboot.tar.md5 that radionerd fixed for me... and it did say Mode: Developer with a boot back into LP no problem, so, essentially yes it was a dev lp note 4, nice...

however, I just for the heck of it flashed twrp and although the flash was a success - did not show errors, it was unable to boot into twrp recovery, it had landed me back in stock recovery... radionerd thinks that there is a possibility to use the Tmo twrp for Lp - and I'm willing to try this. I can always get myself back where I am now ( confident ) so no harm no foul...
[Verizon Galaxy Note 4 General] bagery77:
I understand you'll still want ryanbg's official word on this. But I'm positive I read that he or one of the other pros said aboots are phone specific and would brick someone's device if not applied to the one from which it came. Else they'd be selling like hotcakes around here.
[Verizon Galaxy Note 4 General] gatesjunior:
Yes, do NOT flash any DEV's aboot file on any other phone. The aboot is assigned to the device specifically for the DEV phones. They will NOT work on other devices other than the original device they came from. And it would not be feasible to try and manipulate the aboot, because not only is it assigned to the specific device, but is also signed with keys. Removing trailing 0's at the end of an aboot is one thing to get it back to its original state that it was in for that particular device and a whole other thing to manipulate it to work on another.
[Verizon Galaxy Note 4 General] anticloud:
gotcha, and thanks -

Take the following as a notable, do not attempt this yourself yet - hsbadr or another developer will give the final go-ahead and or properly cooked roms etc, but just take this as where we are at, at the moment...

btw - thanks to radionerd's suggestions - I was able to do the LP OTA, reflash my original aboot.mbn - now, a developer LP edition... furthermore, I used the T-Mobile TWRP for Note 4 as my recovery (openrecovery-twrp-2.8.1.1-trltetmo.img.tar**), then used the SuperSU (UPDATE-SuperSU-v2.16.zip), so I have a Verizon Note 4 Developer Edition Lollipop, Rooted, With TWRP, successfully backed up and restored, as well as tested root apps like root explorer, removal of some bloatware (i.e. cmas.apk)

** Do not flash SuperSU from the openrecovery-twrp-2.8.1.1-trltetmo.img.tar to your Verizon Note 4, won't work; Only use the UPDATE-SuperSU-v2.16.zip; if a later T-mobile TWRP has the same SuperSU then it may work but untested...

Runs like a champ - a bit warmer than kitkat, aside from that, LP is cool...

rob
[Verizon Galaxy Note 4 General] radionerd:
Glad your running LP ok.

Have tried the latest TWRP? I think its 2.8.6.0-trltevzw.zip for our VZW. 2.8.5.0-trltevzw works on my DE. Also the latest SuperSU should work.
[Verizon Galaxy Note 4 General] anticloud:
gonna try that now... will let you know...

---------- Post added at 06:06 PM ---------- Previous post was at 05:46 PM ----------

ok, flashed with Odin twrp-2.8.6.0-trltevzw.img.tar, it goes into TWRP recovery, right on :) seems a bit faster than the t-mo version. I did not have the opportunity to update supersu, yet notably, I do own pro, and when I attempted to download it at the store it thought I have not purchased it before - not sure if that's a store thing / issue, but strange...
[Verizon Galaxy Note 4 General] ryanbg:
For reference, I made a statement about this earlier in the year. The reason there is a extra data is because there's a memory leak in aboot. Save the first 512 bytes (0x200) and delete everything after that.
[Verizon Galaxy Note 4 General] stueycaster:
I just had this conversation in the "Lollipop on dev edition?" thread.

Do I need to do something different here? This is where I got the EFSProBackup file. From the "[GUIDE] VZW Note-4 DE Backup Developer Partitions by radionerd" thread.

These conversations seem to be contradictory. Or did I miss something? Or does this only pertain to flashing Lollipop? [MENTION=3529306]Sokudoningyou[/MENTION] sais he was using Definitive rom. That's a KK rom.
[Verizon Galaxy Note 4 General] :
However you want to take it it didn't work for me until I edited the aboot backup as it states in my link and also in the OP of this thread.

"Eye glazing stuffs: The backups can be un-zipped to a tar, aboot.mbn.tar. Then unzipped again to reveal the unzipped partitions. These can be selectively modified into an Odin flash-able tar.md5. This part should be done by a developer because some hex editing and special software adds an md5 checksum .

Don't be the one that flashes a stock image tar, or allows a repair kiosk to touch your precious. Hopefully the insurance policy you just made won't ever have to be claimed.

Check back for correction, and updates. Please post your results good, or bad to this thread."
[Verizon Galaxy Note 4 General] stueycaster:
OK that's cool. Who can edit my aboot.mbn and turn it into an Odin flashable tar for me? Or do you think I could do it myself?
[Verizon Galaxy Note 4 General] Sokudoningyou:
This page has a step by step for creating your own tar.
[Verizon Galaxy Note 4 General] :
I can take a crack at it if you want. There are a few others who can as well. If a mistake is made it will just not flash so no harm is done. PM me a link to your backed up aboot and I'll try.
[Verizon Galaxy Note 4 General] stueycaster:
Oops you wanted this in a PM.
[Verizon Galaxy Note 4 General] :
No problem, I sent you the modded aboot for Odin. I'm pretty sure I did it right because the file size is the same as mine. You will have to test it to make sure. Again it will either flash if it's good or not if I made a mistake.

---------- Post added at 02:20 PM ---------- Previous post was at 02:12 PM ----------

That's good for creating the tar.md5 but the backed up aboot still needs to be edited with a hex editor following these instructions. There is a long string of 0's at the end of the file along with the extra data stated in the instructions I tagged that need to be deleted. It's a little tricky at first but not too difficult.
[Verizon Galaxy Note 4 General] stueycaster:
It flashed just fine and it still shows MODE: Developer in Download. Thanks a lot.
[Verizon Galaxy Note 4 General] radionerd:
Stueycaster,

Sorry to confuse, there was a false report of successfully flashing an efspro tar of aboot. It does need to be modified.

I have since modified an efspro tar and made aboot flashable. Restoring a DE back from retail locked. (Thanks to ryanbg for hints from earlier threads)

I will update my efspro guide this weekend, when I get back home.

The partitions you saved as an efspro tar are golden, if you ever somehow corrupt or overwrite aboot an Odin flash can be created if one hasn't already been created for you [emoji38]

Thanks
[Verizon Galaxy Note 4 General] anticloud:
Hi radionerd, welcome back, now I'm confused... so, aboot.mbn does not need to be trimmed? I tried flashing an aboot.mbn that came from a EFSPro and it did not work, strange, it did flash to KK before, but not now.

the one you modified for me (unless you did not modify it) or was that just turn to a md5?

rob
[Verizon Galaxy Note 4 General] radionerd:
My guess is that your efs Odin tar flash was identical to what was in aboot prior to your mishap. It probably doesn't recheck aboot until it's changed. So we all learned some more ;)

All backups of aboot definitely do need to be modified in Note4 and S5 DE's If they are overwritten with stock. (Per ryanbg's post)
[Verizon Galaxy Note 4 General] ajh16:
As I understand it, the only thing that makes a dev device a dev device is that there is a signed bit of code that breaks the trust chain and tells it to load anything. It does a check against the device ID prior to doing this and thus isn't of any use to unlocking retail devices. Basically, the "unlocked" developer editions are still locked, they've just been given a signed code path that can run anything on that particular device. To adapt it to another device, you would need the signing key from Samsung to be able to create the device specific aboot's or sign one that does the same thing without the phone's ID check. Short of breaking in to Samsung, this is not going to be cryptographically feasible unless a major cryptanalysis breakthrough occurs (highly unlikely, bordering on impossible).
[Verizon Galaxy Note 4 General] gatesjunior:
Yeah I know, we have come along ways since then...
[Verizon Galaxy Note 4 General] therealunforgiven:
Help locked note 4

Hey guys I love xda and I'm so grateful. Here is the problem. I got two note 4 developer edition phones. One is mine the other girlfriend. When I got the phones I backed up about on both of them. She took OTA update can anybody help me. Thanks for your time
[Verizon Galaxy Note 4 General] therealunforgiven:
Hello thanks so much xda. I made a post as a reply im sorry did not mean to do that. I have two note 4 Developer Edition. I backed up both of them as shown. my note 4 is fine but my girlfriend is not she took ota. any help thanks

I do have the aboot back up file
[Verizon Galaxy Note 4 General] radionerd:
Put her phone into odin download mode (boot with 3 keys held down Power+home +Volume Down) and attach a photo or text that's on the screen

If your "baseband version" ( on "About phone" screen) was originally BOG5 KK, and now baseband version is above 5.0.1 LP the backup of aboot won't do any good. The odin screen will also show this T2, A2 shows fuse increment. (some of the latest DevEds came with LP. An aboot backup of this LP version would work here because the fuse is originally T2,A2 out of the box ) If you bought a KK DevEd It must read T1, A1 for your aboot backup to be able to recover. If so PM me your backup.
[Verizon Galaxy Note 4 General] therealunforgiven:
Thanks for your time it does read T2,A2 this was a KitKat phone. Really thanks you guys help a lot of people
[Verizon Galaxy Note 4 General] radionerd:
Samsung has been agreeing to reflash to DevEd. If you want to send the phone into them turn a round is about 10 days.

Call the number on your receipt. 800-757-0280. They need to understand that this is a Developer Device and it took an OTA that locked the bootloader. Make sure the CSR understands this. You need them to flash it back to latest Developer Edition firmware. They should flag the RMA so they don't just flash retail and send it back locked.

If they don't understand, ask for a supervisor.
[Verizon Galaxy Note 4 General] hilokilo:
Turns out you're quite right this whole time!
[Verizon Galaxy Note 4 General] gatesjunior:
Indeed :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] radji:
My S3 is still running 4.1.2. Haven't wanted to update, but the AT&T notifications are becoming VERY annoying.

I don't mind updating, but I do want the option of going back to 4.1.2 if I don't like the newer ROMs.

What I've read is I need to flash the MJB2 bootloader which doesn't carry eFUSE, correct?

Then I can flash a 4.3 or 4.4.2 ROM with modem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
MJB is 4.3 and Knox is included with the stock ATT 4.3 ROM.

Is your phone carrier unlocked? If not, you could flash to stock 4.1.1, unlock the phone, and upgrade to a newer ROM or bootloader if you want.

Once you are on a stock 4.3 ROM, you cannot go back to a stock 4.1.2 or 4.1.1 ROM as the 4.1.1/4.1.2 modem/baseband will not with with a 4.3 bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] radji:
No, the phone is not carrier unlocked. I have read thru the thread on how to unlock an S3 on 4.1.2 (http://xdaforums.com/showthread.php?t=2529200).

But as I posted in my OP, my question is about the MJB2 bootloader, not the EMJB. There are threads which differentiate that the EMJB is the stock 4.3 bootloader which enables the eFUSE, and the MJB2 is a modded bootloader which does not enable the eFUSE. I'm just trying to avoid all traces of KNOX.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Do you want to go to kk?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] radji:
Doesn't matter to me, 4.3 or 4.4. I just want to use the easier process. That, and I want to use a rooted, stock ROM. I haven't found a stock ROM for 4.4 that is prerooted with KNOX removed, debloated, etc.

But I will keep looking.

Problem is most of the ROMs here state I need to update the modem. And if you update the modem, you need to update the bootloader with it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
deodexed/rooted/SElinux set to permissive/touchwiz 4.4.2/lot of debloting..

http://xdaforums.com/showthread.php?t=2848080

all the above, really bebloted (dont know about root)

http://xdaforums.com/showthread.php?t=2725750

one more....

http://xdaforums.com/showthread.php?t=2725192

on the side of kindness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] radji:
Thank you for those. But they don't address my original question...

Is there an MJB or NE4 bootloader that has been modded to not activate eFUSE?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
really dont know. hopefully someone more knowledgeable will chyme in. :confused:

err on the side of kindness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] radji:
Sorry. I meant MJ2 bootloader, not MJB2.

My original question is does the MJ2 bootloader activate eFUSE, and if it doesn't, will it work with 4.3 and 4.4 ROMs?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
i have not flashed a ROM that enabled KNOX. and at least one of those threads states that they are knox free. as i understand it, the mjb bootloader was 'official' upgrade the mj2 (which i had till just recently) is the OTA upgrade; but essentially they are the same.

yes, i have flashed many 4.3.x & 4.4.x ROMs on mj2.

err on the side of kindness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] StoneyJSG:
Question: I am on the NE4 bootloader. Can I flash the MJ2 bootloader and boot custom ROMS / custom recovery without tripping the KNOX warranty bit?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
The latest cm11 and aosp roms will require a kk bootloader and modem to access the carrier's data network.

I have seen posts where people have flashed the latest modem and bootloader from a custom recovery but I don't know if flashing the bootloader will activate Knox or install Knox.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
NO , dont flash mj2. you WILL BRICK

err on the side of kindness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] radji:
Well, in reading more of the bootloader/knox issue, all of the current bootloaders will activate the eFUSE. But, activating KNOX is more dependent upon the ROM you are on and the one you want to load. I am on a 4.1.2 debloated stock ROM without KNOX, and am probably going to load up	S3Rx 3.0 TouchWiz 4.3 MJB (4-13-14) Full AROMA as it says its totally KNOX free.

I just don't want that damn 0x1 flag to show up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] StoneyJSG:
I hear you! I don't want to trip my warranty bit either, mine is 0x0 right now and want to keep it that way. You're lucky you're on 4.1.2, my GS3 came with 4.3 and then one day it decided to update to 4.4.2 by itself since I forgot to tell the update no and just kept closing it instead. KNOX is an even bigger pain on 4.4, thankfully I disabled it and froze it. Also, what is S3Rx?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
a very nice 4.4.2 touchwiz by [MENTION=2972841]enewman17[/MENTION]. good good builder.

http://xdaforums.com/showthread.php?t=2848080
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] radji:
I decided to go with S3Rx 4.2. I've heard nothing but horror stories about Touchwiz on KitKat. Didn't want to touch it with a 10 ft pole. Good thing was S3Rx made it relatively painless to update.

So far the phone is running good on S3Rx.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
glad to here.
[Greenify] gabrielcarretas:
Hey, you can not buy on amazon store greenify donation?

a greeting
[Greenify] codeknight11:
Same here. Even I wanted to know why I am unable to buy greenify from amazon. The redirects me to amazon store's homepage and if I search for greenify on the amazon appstore, it doesnt show up. I asked this earlier but didnt get a proper answer.