yashsingh1/xdaforums huggingface dataset:
[Verizon Galaxy Note 3 Android Development] DutchDogg54:
Encryption is a big process and you'd probably remember if you did it. Pretty simple to determine if you're encrypted, though. Go to Menu > Settings > Security > Encrypt Device. If you are NOT ecrypted (like most people aren't) then you'll see a screen with a big button along the bottom that says "Set Screen Lock Type." (Or if you just happen to use "password" as your screen lock type and have a password of at least 6 characters and including 1 number, then you'll just see a button that says "encrypt device.")

If you see something else, you might have encrypted your device. Hashcode recommends not using encryption with safestrap.
[Verizon Galaxy Note 3 Android Development] SdRasta:
Awesome. Just wanted to make sure. Thanks
[Verizon Galaxy Note 3 Android Development] kobeback:
please help

Im in the same boat. Can i get that link?
[Verizon Galaxy Note 3 Android Development] DutchDogg54:
Like he said it's in his signature but here ya go

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

Sent courtesy of my Note 3 & XDA Premium
[Verizon Galaxy Note 3 Android Development] kobeback:
thanks

Life Saver pal. God bless.
[Verizon Galaxy Note 3 Android Development] effry:
Any hint on when the international version will get SS on kitkat? The at&t already has it
[Verizon Galaxy Note 3 Android Development] jamor414:
I installed SuperSu with Normal settings instead of custom TWRP - do I need to reinstall and choose the TWRP option or should i keep normal settings installed? I haven't safestrapped yet
[Verizon Galaxy Note 3 Android Development] deuce_biggins:
Normal settings will work
[Verizon Galaxy Note 3 Android Development] Rob_Storm:
Any plans to update to twrp 2.7?
[Verizon Galaxy Note 3 Android Development] dakoop:
Where have all the roms gone? Baja seems like the only one updated in months. Am I missing something or is everyone waiting for kit kat or have they just abandoned us?
[Verizon Galaxy Note 3 Android Development] dragonfly1113:
I've had safestrap on my note 3 for a while i put a beans rom in the rom slot 2 and in rom slot 1 i still have the stock rom, i NEVER go to the stock rom slot anymore, whats the best way to go about deleting that rom slot to free up more room for the beans slot that i'm using as a every day driver?

Sorry if this has already been answered just wasnt sure what exact words to type to search on. reason i'm doing this is running low on app storage space now.
[Verizon Galaxy Note 3 Android Development] DutchDogg54:
Couple ways to skin that cat...

Safest would probably be to:

1) Do a Nandroid backup in safestrap of your Stock Rom, just in case.

2) Do Titanium Backup (or whatever your comparable app might be) (no system apps) of your Beans Slot ROM.

3) Do a full wipe of the stock slot & reflash the Beans ROM on the stock slot.

4) Restore apps and then selectively restore the data you need for the ones that need a data restoration.

A little sloppier but should still work:

1) Do a Nandroid backup in safestrap of your Stock Rom, just in case.

2) Do a Nandroid backup in safestrap of your Beans Slot Rom.

3) I'd recommend naming these two backups so you're not stuck wondering which is which with two backups done nearly back-to-back.

4) Do a full wipe of the stock slot.

5) Restore the Beans backup to the stock slot.

Once you have booted up and are satisfied you no longer need the Beans slot data go ahead and delete it.
[Verizon Galaxy Note 3 Android Development] dragonfly1113:
Sweet thanks will give it a go tonight :) appreciate all your advice.
[Verizon Galaxy Note 3 Android Development] pelo88:
HALP

Hi, I'm hoping someone can help... I JUST noticed in the nick of time (or too late if there is nothing I can do) that a kid entered my password wrong 5 times and my phone said it's going to restart and factory reset (a Google Device Policy enforcement)!

I pulled the battery and booted into Safe Strap and began a backup.

It's still going (I've over 5GB of data and thank goodness enough free space on my SD card for it). What I'll try next is wiping cache and dalvik (I think those options are there). I'm using the stock rom in the stock rom slot and it's rooted. If wiping cache and dalvik doesn't make the rom forget that the password was incorrectly tried over 5 times is there ANYTHING else I can do????????

---------- Post added at 02:54 PM ---------- Previous post was at 02:44 PM ----------

Didn't work :(

Wiping cache and dalvik still has the phone booting into the "you have incorrectly attempted to unlock the phone 6 times the phone will now be reset to factory reset" message.

I don't know how to prevent this from happening.

---------- Post added at 03:18 PM ---------- Previous post was at 02:54 PM ----------

GOT IT!!!

I just had to mount data and system in recovery and use the file manager to delete:

/data/system/password.key

for good measure I deleted gesture.key too

Thanks to this thread too:

http://xdaforums.com/showthread.php?t=2292671
[Verizon Galaxy Note 3 Android Development] alphamale:
If I wanted to downgrade the recovery should I follow the same steps as I would do if upgrading by going to stock rom slot first. And would my previous rim lots be reset would I have to re flash roms
[Verizon Galaxy Note 3 Android Development] Az Biker:
Check out the Note 3 link in my sig for step by step to revert to older version of SS.

Notorious 3
[Verizon Galaxy Note 3 Android Development] fredderf81:
backups do not restore

so i created a backup of my rom just now. everything appears to have backed up properly, no errors. wiped the rom slot. installed the updated version of the rom...realized i forgot a few things...wiped the slot and went to restore my backup and receive backup failed. any ideas?
[Verizon Galaxy Note 3 Android Development] Hashcode:
Make sure your system / data sizes are big enough to be restored to.

Also feel free to pm me your /tmp/recovery.log file right after the failed restore.
[Verizon Galaxy Note 3 Android Development] Capaints:
Thank You Hashcode

I just installed Safestrap 3.65 ......... it went very easy and straightforward, Nice :victory:

Would like to say THANK YOU Hashcode for your Hard Work.

I loaded 3.65 is it Safe to go to the New Beta ver. ?

$11.11
[Verizon Galaxy Note 3 Android Development] Hashcode:
You can stay on v3.65 for Android 4.3 base. However, all devices will need to move up to a newer version (yet to be released) which will work with KK.

v3.71 was a testing build for the most part as it moved to a more generic 4.4 hijack method with some minor updates.
[Verizon Galaxy Note 3 Android Development] Hashcode:
FYI, I need to debug some recent changes, but I plan on releasing a new Safestrap specific for those on the KK build (NC2).

As the current (v3.65/v3.71) Safestrap is *NOT* compatible with 4.4
[Verizon Galaxy Note 3 Android Development] jrbxx7:
Thanks Hashcode can't wait. All hail to the android gods!

TaPpEd from my HyPeR NIII
[Verizon Galaxy Note 3 Android Development] polo2883:
Anxiously waiting for this before I try kitkat.
[Verizon Galaxy Note 3 Android Development] Hashcode:
OP is updated with new download links for the folks on KK.

REMEMBER: THIS IS A BETA. I'M ACTIVELY WORKING ON GETTING MY DEVICE TO BOOT THE TW KK ROM TO MAKE THIS EASIER TO DEBUG. BUT THE DEVELOPER EDITIONS HAVE SOME SERIOUS ISSUES MOVING TO NEWER FIRMWARE. SO IT'S TAKING SOME TIME.

NEW REQUIREMENT FOR KK SAFESTRAP:

Busybox MUST be installed on the stock rom-slot. Luckily, [MENTION=4395895]BeansTown106[/MENTION] has embedded busybox into the initial odex ROM which retains root. Hopefully other devs will keep this trend.

HOW DO I INSTALL SAFESTRAP?

Requirement: Root

Requirement: busybox. If your stock ROM doesn't have it built-in you need to grab "Busybox" from the Play Store and run the installer. (It should already be installed)

Requirement: Allow APK install from Unknown Sources

Download the Safestrap APK

Find the APK using a Filemanager tool and open it on your device, then click "Install".

(If updating from an existing Safestrap you might be warned that this will over-write the existing installation. Click the "Yes" equivalent to this message.)

Once installed, open up the Safestrap application as you would any other app.

Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..

Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.

From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.

That's it for the installation! Read below for a brief overview of Safestrap Recovery v3.x

KNOWN ISSUES:

[v3.72] Sometimes the installation doesn't work correctly. If you don't see the splashscreen after a rebooting. Install Safestrap again. (DEBUGGING THIS AS I GET TIME)

[v3.72] Busybox is now required for the Safestrap APK to work correctly

[v3.72] ROM-SLOTs aren't supported yet

[v3.72] "Reboot Recovery" doesn't work in the APK

If you don't see files on "Micro SDcard" for some reason try tapping that area and swapping to "Internal Storage" and then back again.

No Aroma installer support. This is due to the stock Note 3 kernel framebuffer. To build a recovery which worked, it needed QCOM patches. So will Aroma.

If you try a .zip file with an Aroma installer, it will most likely just hang.

If you use the "4way reboot" mod, then "Reboot Recovery" button in the Safestrap APK won't work correctly.

NEW TO v3.72:

TWRP 2.7.0.x update for the base recovery. This includes vibration support, backup time/date fixes and more.

ROM-SLOTs now have a 16gb size limit (vs 4gb previously) [THEY DON'T WORK YET IN KK THO SO BE PATIENT]

DOWNLOADS:

CONFIRM THAT YOU ARE USING AN VERIZON WIRELESS SAMSUNG GALAXY NOTE 3

[KITKAT:NC2]

LATEST BETA FILE: Safestrap-HLTE-3.72-kk-B01.apk

Mirror 1 (Goo.im)

Mirror 2 (Crackflasher)

Enjoy
[Verizon Galaxy Note 3 Android Development] BossJ:
Awesome Man! Testing backing up right now. it installed perfectly booted perfectly... Thanks for all you do Hash!
[Verizon Galaxy Note 3 Android Development] TheLoonyRebel:
Alright here's my recovery.log of what I'm getting when I try to create a ROM slot. I'm getting 0 memory under /system. I used slot 4 but I'm getting this no matter what slot I try to format and use.
[Verizon Galaxy Note 3 Android Development] Hashcode:
rom-slots don't work at the moment and I'm currently having issues debugging this version of SS. So for now we'll stay away from rom-slot issues.
[Verizon Galaxy Note 3 Android Development] TheLoonyRebel:
Alright. I was hoping my recovery.log could be of use. :highfive:
[Verizon Galaxy Note 3 Android Development] Bern612:
Oh yes....thank you hash for ss
[Verizon Galaxy Note 3 Android Development] LeftyGR:
For information sake. Flashing, backup, restoration seems to work as they should with me. Settings stick. But no new splash. Still the old one. Unless it's only new when ss is enabled? Nonetheless, pretty good so far!

<Note3>
[Verizon Galaxy Note 3 Android Development] Harleydroid:
Thanks for this update [MENTION=4243514]Hashcode[/MENTION]. The vibration in ss recovery threw me off a sec then I remembered reading that in the description. But I like that so thanks again man. So thankful for everything you do for the android community.
[Verizon Galaxy Note 3 Android Development] Hashcode:
Yeah eventually I'll dig into it. I just don't want to grab a bunch of logs now and then lose them before I get my device re-setup.
[Verizon Galaxy Note 3 Android Development] Frank Westlake:
Fails to enter SafeStrap Recovery on SM-N900V-MI9. De la Vega root, SuperSU (latest).

Installed and repeatedly installed hijack and uninstalled hijack. Then I tried a few times installing hijack without uninstalling it. Every time the "Reboot to Recovery" button is pressed it resets to the point where SSRecovery normally runs, but it then resets again and continues into the Launcher.

Reinstalling 3.71 still works fine.

Frank

ADDED

Busybox and all it's links are in '/system/xbin'.
[Verizon Galaxy Note 3 Android Development] Hashcode:
All users on the new Kitkat leak should read this:

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

Summary (tho you'll miss the reasons why): DONT TAKE OTAS. PROTECT THIS BUILD AS BEST YOU CAN. IT'S VERY UNIQUE.
[Verizon Galaxy Note 3 Android Development] Afro Samurai:
I was holding out but I'll take the leap, but I do know better than to take an OTA. Thanks for the heads up.
[Verizon Galaxy Note 3 Android Development] Hashcode:
I actually think this leak build will have a lot more potential than what rolls out in a few days for KK update.
[Verizon Galaxy Note 3 Android Development] popkurn611:
So developers can actually use this leak build to incorporate in their Roms? They won't need to wait for the official correct?
[Verizon Galaxy Note 3 Android Development] TSman74:
Thanks [MENTION=4243514]Hashcode[/MENTION] for all the work you put into this and also for the DE. You and the rest of the devs keep the N3 exciting to own (despite all VZW's efforts!)! :good:

Donation sent: ******25V6685734P
[Verizon Galaxy Note 3 Android Development] dooku77:
[RECOVERY LOCKED/MJ7,MJE,NC2] Safestrap Recovery v3.72 [2014-04-22 KK BETA]

Edited*** found my answer
[Verizon Galaxy Note 3 Android Development] LexusBrian400:
This forum is aimed at Questions and Answers. Edit your post with what you learned, dont just delete it :)
[Verizon Galaxy Note 3 Android Development] dooku77:
Lol it was something I read. I posted a question but went further back in the thread and found it. I must've passed over it. It was in regard to using the other ROM slots. I wanted to create a safeslot but read they weren't active yet.
[Verizon Galaxy Note 3 Android Development] Hashcode:
Yep. And I'm actually recommending users stay away from the official OTA.
[Verizon Galaxy Note 3 Android Development] VirusZer0:
Hey [MENTION=4243514]Hashcode[/MENTION] I was using the latest version of SS on Bean ODEX version of 4.4.2, in recovery I went to wipe, I clicked wipe data and typed YES. After that the phone rebooted to the Note 3 with the custom and padlock, and looped from there, didn't have the option to boot back to recovery even after batt pull. I had to ODIN to MJE and reroot. Just a heads up. Not sure if this is an issue or just something unique that happened to myself.
[Verizon Galaxy Note 3 Android Development] ncdub:
[MENTION=4243514]Hashcode[/MENTION], thanks for the SS update. For all of it really. You, [MENTION=3544615]beanstown[/MENTION], [MENTION=5265029]Nitroglycerin[/MENTION] and the rest of the Note 3 devs make this amazing phone worth keeping.
[Verizon Galaxy Note 3 Android Development] highdro:
The new recovery works excellent so far. It seemed to load up faster and scrolling is much smoother. I was previously on 3.65 and I never tried any betas until now so it could have been that way in 3.71 but on 3.65 scrolling was choppy for me. Thanks a lot Hash!
[Verizon Galaxy Note 3 Android Development] mastibeta:
i dont see the KK safestrap download.
[Verizon Galaxy Note 3 Android Development] milski65:
Click on CF download op. First one listed in group.
[Verizon Galaxy Note 3 Android Development] LeftyGR:
Yeah don't do that. If you do anything more than factory reset within ss recovery and reboot before flashing a new rom, you end up in limbo and only odin can save you.

<Note3>
[Verizon Galaxy Note 3 Android Development] BossJ:
yes yes, you should never have to type YES in SS... if anything you just delete the "slot" but on STOCK Slot you can't do this, and if you delete all your "data" on your STOCK slot. Only odin can make you right again :D

Thank goodness for ODIN.
[Verizon Galaxy Note 3 Android Development] mastibeta:
Why do i not see this?

nevermind, i got it.
[Verizon Galaxy Note 3 Android Development] Hashcode:
Hmm. In reality this probably is a conditional bug that I need to fix (and doesn't happen very often).

The hijack / recovery files are on the system partition. So even tho you wiped internal storage you should have been able to re enter recovery. :/

At some point I'll debug this.
[Verizon Galaxy Note 3 Android Development] repsol_23:
[MENTION=4243514]Hashcode[/MENTION]

I was running 3.65 for the longest time and last night I went to install the beta version so that I could do the kit kat update but I'm having some troubles. After installing the beta I no longer see the splash screen for recovery. I have spent hours reinstalling and trying to go back to 365 and even 371 but still get the same thing. I'm at my wits end and unless I can figure this out I feel like my only option is to odin back to mje, reroot, and start the process all over for installing kit kat leak.

Would you happen to have any suggestions before I take such drastic measures?

Any help would be greatly appreciated!!!

Tap'n & Talk'n on my Note 3
[Verizon Galaxy Note 3 Android Development] LeftyGR:
Can you give us what procedure you are doing to change ss version? Are you performing the steps (how to upgrade ss, not install) in the op verbatim?

And the new beta is for when you are already on kk. All previous revs are for jb.
[Verizon Galaxy Note 3 Android Development] repsol_23:
Crap. I thought I was too put new version prior to installing kitkat.

What I did was:

go into 365 and I uninstall recovery

reboot

find beta apk and install

reboot

go into safestrap and install recovery

reboot

Then I get no splash screen but I boot up straight into beans.

Tap'n & Talk'n on my Note 3
[Verizon Galaxy Note 3 Android Development] VirusZer0:
Yeah it was really weird, it just came up with the padlock then a white line across the screen, almost like a CRT display, and then back to the custom padlock. Oh well, I'm back up now an on the Deodexed stock rooted 4.4.2. Thanks a MILLION man!
[Verizon Galaxy Note 3 Android Development] sfld:
You need to use 3.65 to flash the 4.4.2 deodexed rom... reboot into download mode and download the firmware/bootloader. when it boots to your home screen you can then download the 3.72 apk and install it, it will overwrite the older version 3.65. After that you are good to go with the newest ss
[Verizon Galaxy Note 3 Android Development] repsol_23:
That's just it. When I uninstall the beta version and go thru the process of installing 365 I still get the issue of the splash screen not showing. So now I can even get into safestrap. It shows that the recovery is installed but I can't get it to be active.

Thanks for the help!!

Tap'n & Talk'n on my Note 3
[Verizon Galaxy Note 3 Android Development] Hashcode:
Can you pop onto the IRC channel: #safestrap on irc.freenode.net? I can walk you through some steps to clear out the Safestrap files manually and then make sure that they are being installed correctly.
[Verizon Galaxy Note 3 Android Development] xxVAGRANTxx:
Yup and it scrolls so damn smoothly now too ?
[Verizon Galaxy Note 3 Android Development] repsol_23:
I tried to got to the site you said but it keeps timing out on my phone and here at work it says that the page is unavailable.

Any suggestions other than pm's?
[Verizon Galaxy Note 3 Android Development] rclar144:
Having issues using new KK safestrap.....I'm running new 4.4.2 odex and after I install safestrap 3.72 it won't reboot into recovery!!??? So I can't install deadexed.....:eek:
[Verizon Galaxy Note 3 Android Development] sfld:
are you manually turning the phone off then trying to enter recovery? You cant use the reboot to recovery features as they dont work
[Verizon Galaxy Note 3 Android Development] rclar144:
Thx man! Got it....never even crossed my mind to try manually! :D
[Verizon Galaxy Note 3 Android Development] Frank Westlake:
If you want testing on an MI9 I can do that without fear of destroying the device. I've replaced my 900V with a 900T and I'm keeping the V only for spare parts. I plan on doing other experimenting with it as I get time.

Frank
[Verizon Galaxy Note 3 Android Development] sfld:
no problem
[Verizon Galaxy Note 3 Android Development] jr_718:
Since reboot recovery doesn't work...I tried rebooting into recovery using rom toolbox...Phone rebooted into bootloop...bypassed it by taking the battery reboot.into.download mode then select cancel (reboot phone normally)..everything back to normal. ..BTW the time and date are accurate as well..Thank you sir for all your work..
[Verizon Galaxy Note 3 Android Development] Frank Westlake:
[MENTION=4243514]Hashcode[/MENTION], I might have found something for you. In the SuperSU logs one of the scripts shows the error message (paths abbreviated):

THE CALL:

.../files/busybox rm -r .../files/install-files

STDERR:

rm: cannot remove '...files/install-files': no such file or directory

The paths are correct and '...files/install-files' with its subdirectories and files are there, but they are owned by root 755 and everything else is user 755.

Frank

ADDED:

I un-hijacked then hijacked to look at fresh SuperSU logs. The following log says it can't find 'e2fsck'. It is in the zip but not in the file system. It's strange, 'install-files/etc' is in place but 'install-files/bin' is not, but they are both in the archive.

--------------------

CALL:

sh /data/data/com.hashcode.safestrap/files/recovery-install.sh /data/data/com.hashcode.safestrap/files

STDOUT:

CURRENTSYS =

Archive: /data/data/com.hashcode.safestrap/files/install-files.zip

creating: install-files/

creating: install-files/bin/

inflating: install-files/bin/e2fsck

creating: install-files/etc/

creating: install-files/etc/safestrap/

inflating: install-files/etc/safestrap/ramdisk-recovery.img

inflating: install-files/etc/safestrap/2nd-init.zip

inflating: install-files/etc/safestrap/safestrapmenu

inflating: install-files/etc/safestrap/ss.config

creating: install-files/etc/safestrap/rootfs/

inflating: install-files/etc/safestrap/rootfs/init

inflating: install-files/etc/safestrap/bbx

inflating: install-files/etc/safestrap/ss_function.sh

creating: install-files/etc/safestrap/res/

inflating: install-files/etc/safestrap/res/splashkeys.sec_touchscreen

inflating: install-files/etc/safestrap/res/background-safe.png

inflating: install-files/etc/safestrap/res/background-safe-light.png

inflating: install-files/etc/safestrap/res/background-nonsafe.png

inflating: install-files/etc/safestrap/res/background-nonsafe-light.png

inflating: install-files/etc/safestrap/res/background-blank.png

creating: install-files/etc/safestrap/flags/

inflating: install-files/etc/safestrap/flags/version

inflating: install-files/etc/safestrap/flags/recovery_mode

STDERR:

cp: can't stat '/data/data/com.hashcode.safestrap/files/install-files/bin/e2fsck': No such file or directory

chown: /system/bin/e2fsck: No such file or directory

chmod: /system/bin/e2fsck: No such file or directory

----------------

Frank
[Verizon Galaxy Note 3 Android Development] GoNavyMike:
Excuse me but............

What is NC2? I'm running MJE 4.3 Baja 11. Also does anyone know how to improve the radio? My reception now sucks and has been bad for about two months. I do clean installs so I know it's not from a dirty install.

Thanks,

GoNavyMike
[Verizon Galaxy Note 3 Android Development] Harleydroid:
NC2 is the kit Kat build. New kernel and baseband. Follow the instructions in the op for installation. There's a good video too. Go to the thread by beans for the build.

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

★ [ROM/ROOT][N900VVRUCNC2][4.4.2] Stock Root Odex/DeOdex [04/23/14]★
[Verizon Galaxy Note 3 Android Development] GoNavyMike:
NC2...

Thanks.
[Verizon Galaxy Note 3 Android Development] Harleydroid:
You bet. Hashcode is calling this a very unique build. Possibly have Kexec for loading a 2nd kernel at boot. So possibly might be able to run aosp roms. But we will see what happens. If you load up this build guard it from any future ota's.
[Verizon Galaxy Note 3 Android Development] Diceroll:
Does anybody know if it will be possible to use roms from other Note 3s.
[Verizon Galaxy Note 3 Android Development] BluPhant:
Try taking back off and make sure all screws tightened.

Blu

Sent from my Samsung Galaxy Note III ... BajaRom Style