yashsingh1/xdaforums huggingface dataset:
[HTC Droid DNA] mopartonyg:
read through this thread in general. They say you can ruu back to the previous version and then unlock and soff

http://xdaforums.com/showthread.php?t=2935556
[Galaxy S 5 Q&A, Help & Troubleshooting] Edgar J.:
Hello I cont find the Photo App from the app manager I think I disable it, any apk someone can share?
[Galaxy S 5 Q&A, Help & Troubleshooting] Protosb:
a little bit more info and we might help you.
[Galaxy S 5 Q&A, Help & Troubleshooting] mauriicio21:
photo app is google +
[8525, TyTN, MDA Vario II, JasJam General] lanwarrior:
I went to "Regional Settings" and under the "Date" tab, I do not see the ability to change the date format to D/M/yy (i.e. 31/01/07). The only one available is D/MMM/yy (31/Jan/07).

Is there any registry hack to change it to short date/month/year without spelling the month?
[8525, TyTN, MDA Vario II, JasJam General] hanmin:
I have it in mine. I have dd/mm/yy and also D/M/yy. You might want tell us which ROM you use and region you set. I'm using the UK region settings.
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
You try a registry change:

http://xdaforums.com/showpost.php?p=1127817&postcount=2

Mike
[8525, TyTN, MDA Vario II, JasJam General] lanwarrior:
Thanks, Mike! This is exactly what I needed!
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
No problem.

Cheers

Mike
[Sony Xperia Z Ultra] QA Bot:
Q&A for [Guide] Your New GPe

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [Guide] Your New GPe. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Sony Xperia Z Ultra] zhchaoxing:
Could you upload the GPe Sony Xperia Z Ultra Android L OTA ROM?

Could you upload and post the GPe Sony Xperia Z Ultra Android L OTA ROM? It's out for 3 days now.

Thanks!
[Verizon Galaxy Note 4 General] bdorr1105:
Nice guide I will have to do this
[Verizon Galaxy Note 4 General] jpcalhoun:
This is great work. Thanks so much. We've already seen a couple of our fellow Note 4 DE owners need a aboot backup to restore their unlocked bootloader. This is a must for any DE owner. It's like an insurance policy.
[Verizon Galaxy Note 4 General] newuser134:
How do you restore?

Once you use the dd command in terminal emulator or in adb, or once you have an efs-professional backup of your aboot, so you have an aboot.mbn or aboot.bak, how do you restore it if you have inadvertently, let's say, flashed a retail edition aboot by flashing a retail full tar file from Odin for instance? I bought a Note 3 DE last year, and I made a copy of my aboot as soon as I got it, using the dd command, the file is about 2mb, but so far I don't know how to restore it if it does get the retail aboot installed on it by accident. Could you please shed some light on the restoration procedure as well?

Also, I know if you backup your /efs partition on twrp, it can't be restored if you mess it up, supposedly that's what makes the phone tick and gives it its identity, I have read about a few people on this forum that accidentally deleted their /efs partition and their phone never worked right after that, like their unlock screen wouldn't work and a lot of other stuff was messed up, as they described. If you make a /efs backup with efs-professional, could it be restored correctly if the /efs partition gets corrupted by accident? I don't really know why anyone would need to delete that partition, but I think some rom or modem update procedure did it, but just in case it happens.

Thank you for the great work and tutorial
[Verizon Galaxy Note 4 General] radionerd:
Hopefully no one will have to be the Guinea Pig, and restore a corrupted aboot from accidentally flashing a retail TAR on their DE. As far as I know only one guy has tried aboot restore successfully, with big help from a dev who made his prior saved aboot flashable.

As far as I know aboot restore is untested with efsprofessional, I have successfully restored other partitions using efspro on my note-3 DE.

Unfortunately every DE version that has been released has had several folks overwrite aboot; accidentally, or in desperation flash retail Tars, by themselves, by Samsung service center, or at a retail store kiosk, like bestbuy.

Your DE warranty, and insurance is your backups. Samsung won't fix your corrupted system, if they do (only if no knox trip 0x0), you will receive your phone with a retail image put on it. Having an aboot backup could possibly bring it back to DE.

Been there done that, Most of the guys that had efs messed up on Note-3 DE, including myself, we used the first T-mobile TWRP version that didn't backup the right efs partition, upon TWRP restore we had major problems, some of us compounded the problems, me too :) TWRP was quickly updated, and a few of us figured out ways to rebuilt /efs.

"What I learned was backup your backup, then back that up too" I do complete TWRP backup as soon as rooted, DD of all partitions, then backup all partitions, except a few huge partitions using efspro.

Thanks WIP, hope to add soon "copy and paste" scripts for all the partitions.
[Verizon Galaxy Note 4 General] ACiDxCHRiST:
Thanks for the instructions. I hope to never need it, but I will follow this procedure just to be on the safe side.
[Verizon Galaxy Note 4 General] solidunit:
Doesn't TWRP handle this by ticking on the EFS checkbox when making a backup?
[Verizon Galaxy Note 4 General] radionerd:
TWRP does backup EFS, but not aboot, or a handful of other partitions. EFS pro can backup all partitions.
[Verizon Galaxy Note 4 General] tfly212:
When I get to the "read device" step I get an error saying it cannot find the pit file in the EFS folder. What am I missing? Thanks
[Verizon Galaxy Note 4 General] radionerd:
Did you click on the Manage box and select "create new"

Then read device

Then name note-4 on device name, display name, and description, then click save

go back to manage, click refresh

Then go to device filters, find your note 4

de-select all, then select aboot

Then click backup.

Now you should have a "double zipped" file of aboot in your computer efsprofessional folder, and on your sdcard.

Attached a few pictures from my note 3
[Verizon Galaxy Note 4 General] tfly212:
I did not the first time...but once I did it worked perfectly, thank you. I didn't think to click the dropdown as I knew Note 4 wasn't going to be on there. Might want to add that line to the instructions in case anyone else runs into the same issue.

All good now...going to donate to the dev tonight.
[Verizon Galaxy Note 4 General] radionerd:
Great!

I will go look at the wording of the OP
[Verizon Galaxy Note 4 General] radionerd:
Buy him some nappies for his kid :)

Thanks man,

I updated my OP with 27 8"x10" color glossy photos with circles and arrows ;)
[Verizon Galaxy Note 4 General] tfly212:
Will do...I have a little one also, and while a beer sounds better, the way they go through diapers is staggering.
[Verizon Galaxy Note 4 General] texasez:
How do I find my computers RSA key? I am on windows 8.1?
[Verizon Galaxy Note 4 General] radionerd:
You don't need to know the computer's RSA key, The RSA pop-up comes up on your phone when entering ADB mode. The key is in the pop-up, Just grant access.
[Verizon Galaxy Note 4 General] PaulPizz:
Is the "sbl1bak" a backup of the "sbl1" ????????
[Verizon Galaxy Note 4 General] radionerd:
Yup,

However sb1bak is empty on my note 4

Easy look at Note 4 partition Mounts by-name (trltevzw)

aboot -> /dev/block/mmcblk0p7 (2048KB)

apnhlos -> /dev/block/mmcblk0p1

boot -> /dev/block/mmcblk0p17

cache -> /dev/block/mmcblk0p25

carrier -> /dev/block/mmcblk0p26

dbi -> /dev/block/mmcblk0p5

ddr -> /dev/block/mmcblk0p6

efs -> /dev/block/mmcblk0p13

fota -> /dev/block/mmcblk0p19

mdm1m9kefs1 -> /dev/block/mmcblk0p14

mdm1m9kefs2 -> /dev/block/mmcblk0p15

mdm1m9kefs3 -> /dev/block/mmcblk0p10

mdm1m9kefsc -> /dev/block/mmcblk0p16

misc -> /dev/block/mmcblk0p20

modem -> /dev/block/mmcblk0p2

pad -> /dev/block/mmcblk0p11

param -> /dev/block/mmcblk0p12

persdata -> /dev/block/mmcblk0p23

persist -> /dev/block/mmcblk0p22

recovery -> /dev/block/mmcblk0p18

rpm -> /dev/block/mmcblk0p8

sbl1 -> /dev/block/mmcblk0p3

sbl1bak -> /dev/block/mmcblk0p4

ssd -> /dev/block/mmcblk0p21

system -> /dev/block/mmcblk0p24

tz -> /dev/block/mmcblk0p9

userdata -> /dev/block/mmcblk0p27
[Verizon Galaxy Note 4 General] texasez:
I finally get past the RSA problem by using installer mode on phone but the phone auto changes back to media device and then efs pro does not recognize the phone. I tried camera (ptp) mode but it will not go past pressing the device info button on efs pro. How do I make the phone stay in installer mode. I keep getting popups wanting me to install the verizon software but I did not install.

How do I keep the installer mode active?
[Verizon Galaxy Note 4 General] PaulPizz:
Your obviously on the dev edition?? Correct? If so if it's not to much to ask will you send me a copy of your sbl1. Please.

Sent from my SM-N910V
[Verizon Galaxy Note 4 General] rommer2:
HELP!

I sure hope this offer still stands! Attached is my aboot.bak

Thanks....
[Verizon Galaxy Note 4 General] newbe101:
radionerd fixed my aboot last month. It has been hard to login to XDA. What version of Android do you have on your phone now. The aboot fix only works with some versions. Good luck:cool:
[Verizon Galaxy Note 4 General] radionerd:
I'm working on your backup now,

Meanwhile put your note 4 into Odin download mode and look at lines 7 and 8, efuses and mode.

How To: (Power off, then hold power, home, vol down until starts, then press vol up to see diagnostics.. Take a picture, or copy down text. When you are ready to restart device: Hold Power, Home, vol down until display goes blank, then release buttons . Now it will enter Maintenance Boot Mode. Press Home for normal boot, or perform other options.

Normal DevEd below

AP SWREV: S1, T1 R1, A1, P1 (Should all be 1's on DevEds sold before 5.0.1, if 2's old aboot backup is worthless)

MODE: Developer (This shows that the device is still a DevEd and doesn't need the aboot restore)
[Verizon Galaxy Note 4 General] rommer2:
The fuses are all at 1 but the next line says secure download : enabled

So not in developer mode but no number 2's
[Verizon Galaxy Note 4 General] radionerd:
the modded aboot I sent back (PM) should unlock it back to DevEd
[Verizon Galaxy Note 4 General] rommer2:
Very nice!

I sent a little something to say thank-you.

Now I have to figure what to do in terms of rooting the device. I had already installed 5.1.1

Would the best way be to install trwp using adb?
[Verizon Galaxy Note 4 General] radionerd:
Glad you got it back from retail!

TWRP; adb, or Odin is easy.
[Verizon Galaxy Note 4 General] rommer2:
All good!

Rooted and running 5.1.1

Very smooth.

Thanks again.
[Verizon Galaxy Note 4 General] neva4self:
I recently ended up in a boot loop messing with my DE. Luckily I was able to recover from it, but it was a wake up call to be prepared for the worst case scenario, especially since I'm still a novice with rooting and custom roms. I have attached a copy of my aboot, which I created when I first received the device, after reading this thread. I checked my device using the above post and everything still matches up properly, however like I said I'd like to prepared just in case. That being said, can you modify my aboot accordingly and PM me where I can donate accordingly too. Thanks.

I also have a quick question, I recently purchased another Note 4 DE from someone who had bricked their device and sent it back to Samsung to have it flashed back to DE. When they got it back , Samsung had flashed 5.0.1 to it, instead of their original 4.4.4. The person then installed TWRP and Jasmine Rom but as per my request, they removed Jasmine Rom and did a factory reset before they shipped the device. They have not removed TWRP as they were not sure how to do so and return to stock recovery. My question is: With all the modification they have already done, can I use the EFS Pro method to make an unaltered stock aboot? Or do I have to figure out how to completely restore their device back to stock 5.0.1 everything including recovery before I make a truly stock unaltered aboot?
[Verizon Galaxy Note 4 General] radionerd:
I saved your backup, will try to get around to making a flashable for you. Unfortunately lately several DevEd owners have flashed retail 5.01 and higher. This increments the bootloader and Trust Zone rendering their aboot backup useless. Those folks can't recover with their aboot backup. Their only recourse is to ask Samsung to flash DevEd to current fuse2 bl.

All you need is; root and busybox to backup using EFS Professional method. You can install the latest zip of SuperSU via TWRP.

TWRP / FlashFire installable ZIP:

Stable: http://download.chainfire.eu/supersu-stable

Beta: http://download.chainfire.eu/supersu-beta

Latest: http://download.chainfire.eu/supersu

For busybox, install busybox app, I like Stephen Erickson's busybox
[Verizon Galaxy Note 4 General] neva4self:
I just used this thread to safe upgrade to 5.1.1: http://xdaforums.com/note-4-verizon/development/firmware-safe-upgrade-to-lollipop-t3313224 does that render my aboot useless also? My devide was still set to all 1's and Developer. I checked it right before I installed TWRP.

Ok, as soon as I receive the device I will try to create an aboot and get back to you about that one as well. Thanks.
[Verizon Galaxy Note 4 General] radionerd:
You are OK, "DevEd safe" upgrades are safe. The Developer has removed the toxic partitions from the upgrade package. Aboot, TZ, and possibly some other partitions are removed to make the upgrade safe for Developer devices. We must retain our original aboot.

Dev Ed owners must be very careful when flashing TARS. If the upgrade doesn't state that it is Developer Edition safe, don't flash without clarification from the Developer.
[Verizon Galaxy Note 4 General] neva4self:
Quick question, what does this mean for me? I just got that second Note 4 DE in the mail and I tried to flash TWRP and got stuck in a boot loop so I tried to flash the current SAFE UPGRADE of 5.0.1 and I got this message after Odin failed: SW REV CHECK FAIL: (tz) fused 2 > Binary 1 which I noticed is exactly what you mentioned. Now the person I bought the phone from did say they had a flashing issue previously and had to send it to Samsung and Samsung sent it back with 5.0.1 on it. I'm only asking because I see you mentioned (Their only recourse is to ask Samsung to flash DevEd to current fuse2 bl) which I have no idea what that means. I think it's crazy that Samsung wouldn't flash all DE's back to the original condition they shipped it in, even if they charged for such a service. We bought the phone because of what it was and what it had on it so if we encounter issues that do not involve replacing the hardware then they should at least return it back to how it was when we purchased it.
[Verizon Galaxy Note 4 General] neva4self:
Problem solved!! I reflashed TWRP using Odin and when it was done it booted me back to the initial setup and everything looks good. After a little bit of reading I'm assuming that since Samsung upgraded this deice to 5.0.1 I can't make a copy of the aboot. That's crazy.
[Verizon Galaxy Note 4 General] neva4self:
This is what I was talking about. So when I tried to flash the safe upgrade of 5.0.1 over the 5.0.1 upgrade that Samsung had placed on the device I got stuck in download mode with this error. I flashed TWRP while stuck in download mode with this error and it allowed me to at least get to the initial setup. I already have an aboot from my first Note 4 but you are saying that since this recent Note 4 has the AP SWREV: S1, T2, R1, A2, P1 line that I can't use an old aboot nor create a new one? So should I just chalk it up as a loss and go ahead and mod without the aboot?

I'm a little confused because even with all the errors my device still says DEVELOPER on the download screen and I have TWRP, SuperSU and Busy Box installed.
[Verizon Galaxy Note 4 General] pdtp:
I tried to backup the aboot after I got it back from Samsung using the method described in here and it did not work. As far as I could tell with the fuse error it only wanted to boot 5.1.1 stock image and not 5.0.1. I may have been wrong and gotten 5.1.1 from Samsung hence why you can't go back to 5.0.1.
[Verizon Galaxy Note 4 General] radionerd:
Backup your aboot. Your device is a fuse2 DevEd.

As long as it still says "Mode Developer" on the Odin mode screen it is unlocked.
[Verizon Galaxy Note 4 General] radionerd:
Make a backup of aboot. You need root and busy box for EFS Pro to work.

There are also other ways to extract a backup of aboot, if you can't get EFS pro to work.
[Verizon Galaxy Note 4 General] neva4self:
Nope I am definetly running 5.0.1 on the device. I am running 5.0.1 and I flashed Jasmine ROM v3.1. Can't back up aboot either though.

---------- Post added at 05:45 PM ---------- Previous post was at 05:37 PM ----------

I tried to back up aboot using EFS pro to work, I followed all the directions to the letter but when I click on READ PIT and I get the file not found nag screen, nothing happens. Meaning I get no script showing to save. I teired it from a couple of different PC's because I was running windows 10 on the first PC but een on windows 8 and making sure Microsoft .NET was running the correct version I still get no script after clicking READ PIT. Therefore when I click manage and then refresh and then the file I saved it gives me a file not found error because it is saving a fie with no script. I would love to try another method but I am only a novice when it comes to this type of thing, what would you suggest being the next easiest method?

Remember I've already sent you one aboot for my first Note 4 so it's not like I haven't done this before, for some reason EFS is not working at all this time around.
[Verizon Galaxy Note 4 General] radionerd:
Guide How To Copy Aboot using TWRP recovery

There are several other ways to copy the aboot partition:

You could use your recovery's file manager

Use adb dd or pull

FlashFire (Secondary Bootloader AP) *Not confirmed* file would have to be modified. Chainfire's compressed file structure is different

My OP points to how to install and use ADB DD commands

http://xdaforums.com/showpost.php?p=57080306&postcount=92

Instructions using TWRP file Manager.

In TWRP 1st click "mount" then select "system" (This should allow access to the file system so you can copy the file)

tick system box

Then open " TWRP's File Manager" and find the aboot partition (The path is in the photo: /dev/block/platform/msm_sdcc.1/by-name/aboot)

Then copy "aboot" It will prompt for a destination, select the folder "sdcard", this will avoid any permission conflicts writing to extsd... Confirm action, and reboot

Once you reboot the copy will be accessible in the internal scdard folder. copy the file to a safe place.
[Verizon Galaxy Note 4 General] radionerd:
I think [MENTION=5790686]anticloud[/MENTION] was successful using efspro after A2 fuse. Maybe he will chime in.

It's possible that efspro is broken in the latest DevED firmware.

Try this TWRP method : http://xdaforums.com/showpost.php?p=65676392&postcount=200
[Verizon Galaxy Note 4 General] doubleplay648:
I tried your method using TWRP, unfortunately I was unable to find msm_sdcc.1, I too have a developer edition that was incremented with A2, T2 after sending it to samsung. They sent me back with 5.0.1 and i took Hsbadr's safe incremented upgrade to 5.1.1

Has anyone had luck making a backup of their aboot partition after sending it into samsung. I am currently running jasmine 3.0 as 3.1 causes a bootloop. Any suggestions?
[Verizon Galaxy Note 4 General] neva4self:
I'm running Jasmine ROM v3.1 but I'm doing so on 5.0.1, if I'm not mistaken v3 through v3.1 are best with 5.0.1 and v4 through v4.1 are best wit 5.1.1. I'm glad you were able to get 5.1.1 installed correctly, ODIN kept failing on me at the last second of verification, literally the last second, and I kept getting that (software failure error) which kept me locked in download mode. I flashed v2.8.7.0 of TWRP using ODIN as a last resort because I was stuck and was surprised it passed in ODIN and fixed the "stuck on download screen" problem. I didn't want to mess with it anymore because I too was trying to use Hsbadr's safe upgrade to 5.1.1 when it kept failing. I tried flashing his safe 5.0.1 upgrade to see if it would pass with ODIN just so happens that 5.0.1 was the last upgrade I tried before I used flashing TWRP to get out of being stuck with the software error. So now I'm still on 5.0.1 but I'm using Jasmine ROM v3.1. I have two NOTE 4 DE's and on my original DE, I never had any issues using Hsbadr's safe upgrade to go from 5.0.1 to 5.1.1 and back again or using EFS Pro to backup my aboot so I figured on this recently Samsung flashed DE it was this A2, T2 fuse error not letting me do either. Anyhow since I'm up and running now, I don't even want to mess with it too much. If it ain't broke............ right. I'm not to savvy when it comes to messing with ADB so for now I'll leave it alone and hope for the best.
[Verizon Galaxy Note 4 General] radionerd:
It's in there, look around once you get to folder /dev/block/platform/... (The thumbnail had the correct path, I missed a folder in the text)

In the note 4 aboot is also called block "mmcblk0p7" or just "p7" (by-name it's "aboot", by number it's "p7") copy any one of those three as described in my prior post.
[Verizon Galaxy Note 4 General] stueycaster:
I'm running the DrKetan rom on my N4DE. In the DrKetan Utilities app under "Tasks" it has EFS Backup (SD Variant). This is what it saved. Is this something that a person could use to back up their aboot partition?

Sent from my SM-N920V DE
[Verizon Galaxy Note 4 General] urgodfather:
Don't know if anyone has noticed, but I already have some partitions backed up and shared publicly on my Debrick guide.
[Verizon Galaxy Note 4 General] bdlagain:
I have a question. This probably isn't the place but it's the only forum with new posts about the vzw note 4 de. I'm a bit of a noob tho I've rooted phones for years with all of your help. I'm still running kitkat & want to upgrade to lolli or marshmallow. Does twrp or cyangen have a mod on here for a de? Do I need to back up this bootloader first? Do I unroot, upgrade, then re-root? If one of you all could just throw me a link, that would be greatly appreciated. Thanx!
[Verizon Galaxy Note 4 General] radionerd:
EFS should be backed up if you're flashing roms. If you ever lost IMEI in a bad flash you could restore it with the backup you have. TWRP can also backup EFS partitions.

aboot.mdn partition is not included in your EFS backup.
[Verizon Galaxy Note 4 General] stueycaster:
I have the aboot.tar.md5 that I saved back when I first got my N4DE. I've tried a bunch of different roms without affecting my bootloader. I was just wondering if messing with the EFS thing built into this rom is worthwhile.

It's been so long since I saved it I have forgotten what I would need to do if I needed to reinstall my bootloader. Would I odin the ANI1 Bootloader then odin my aboot.tar.md5? Or I also have the other pertinent files I saved along with the aboot. Would I need to install them too or would the bootloader take care of them. Or would it be better to use the full firmware plus the aboot?

Sent from my SM-N920V DE