Disable Force Encryption? - Xiaomi Poco F1 Questions & Answers

Hi. I'm just wondering what this is that we flash before installing a new rom, why do we flash this, what does it do? Is it necessary to flash it?
Thanks

Just keep onething in mind before digging into this matter. Having a decrypted device is the same as having a stolen device. No security at all and the device gets extremely vulnerable and easy to be hacked. I don't really know why some people still decrypt their devices when we already got a TWRP which decrypts the device temporarily while booting on recovery (without actually decrypt your device permanently).

Disable Force Encryption (a.k.a DFE) is flashed during installing a custom rom to avoid the system encrypting /data partition when the devices boot for the first time.
DFE is not necessary but some custom recoveries (Official TWRP for example), needs the /data partition to be unencrypted to access the internal storage for you to flash something or to access /data and internal storage. (Except if you have SD Card, then DFE is no longer needed)
OrangeFox Recovery for example has its feature when installing custom recovery, flashing DFE is no longer needed because the recovery itself will patch the boot.img to avoid the system to encrypt data.
Final Verdict:
-If you want a secured device that has a lot of golden stuff inside, then do not flash DFE or disable the DFE on OrangeFox Recovery.
-If you want to access /data for your inconvenience, then flash DFE everytime you install a custom rom or enable DFE on OrangeFox Recovery.
Edit:
The unoffical TWRP that has data decryption patch doesn't works as new and updated vendor, boot.img, etc. comes in and the fix is useless. It only works on older system patches, e.g. MIUI 9.

If i decrypt the device. How to encrypt it again?

SamyakJ said:
If i decrypt the device. How to encrypt it again?
Click to expand...
Click to collapse
Security&Location > Encryption&credentials > Encrypt phone
I think it requires your phone to be at 100% charging to start the encryption.
---------- Post added at 08:36 AM ---------- Previous post was at 08:35 AM ----------
And I don't even know if it is stable or not after the encryption. I haven't tried encrypting the device via the Settings.

So this is where I am stuck since March 25th, oneplus 7 pro with oos 11 final and encrypted phone with a lot of precious data. All I need is root (not really need custom recovery).
Is there any way to get it rooted without data loss? I've tried to flash the patched boot image found in this thread but the phone keeps looping in boot until I force restart it then it boots normally. Tried that several times with no luck.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

can't you just backup all the data? you don't exactly need root for backups

I continue the post with 2 questions
sorry for the banality of the questions and I searched online and on the forum before asking
1) So if I don't disable the forced encryption the only problem I can have is the appearance of the set warranty bit kernel written every time the phone is rebooted?
2) What is the difference between these? (1) Tabs3_oreo_forced + encryption_disabler (2) Disable_Dm-Verity_ForceEncrypt-master (3) no-verity-opt-encrypt- ?
and how can I check the compatibility of the phone?
Tks !!!

Darklouis said:
Disable Force Encryption (a.k.a DFE) is flashed during installing a custom rom to avoid the system encrypting /data partition when the devices boot for the first time.
DFE is not necessary but some custom recoveries (Official TWRP for example), needs the /data partition to be unencrypted to access the internal storage for you to flash something or to access /data and internal storage. (Except if you have SD Card, then DFE is no longer needed)
OrangeFox Recovery for example has its feature when installing custom recovery, flashing DFE is no longer needed because the recovery itself will patch the boot.img to avoid the system to encrypt data.
Final Verdict:
-If you want a secured device that has a lot of golden stuff inside, then do not flash DFE or disable the DFE on OrangeFox Recovery.
-If you want to access /data for your inconvenience, then flash DFE everytime you install a custom rom or enable DFE on OrangeFox Recovery.
Edit:
The unoffical TWRP that has data decryption patch doesn't works as new and updated vendor, boot.img, etc. comes in and the fix is useless. It only works on older system patches, e.g. MIUI 9.
Click to expand...
Click to collapse
Is DFE and avb2.0 same?
Coz I'm using shrp and unable to find close avb2.0 ?

Related

Umidigi One Pro Q&A/Discussion/Project Treble

Ok I started this thread in hopes that I could get some answers from someone more knowledgeable than me on these MTK phones.
I've been reading online about flashing these GSI roms but I've seen multiple different methods. Some say use TWRP others say fastboot, or should I use SP flash tools...? And what are the proper wipes to prep for GSI flash? I've seen some say wipe everything except internal and others say just wipe dalvik/cache, and still others that say you must wipe in stock recovery then flash and boot twrp to flash system image...? Can any Umidigi Pros enlighten us a little? I'm sure google will bring more people to this page in time...or not?
I have flashed some GSI ROMs but everyone I've tried I cant seem to get root with Magisk. Magisk shows to be installed but when root apps call for root it just sits there and times out and I never get the prompt to grant root. This means I can't edit the APN which means no data which is not an option.
PS I've tried posting over in Umidigi community but it seems like a ghost town over there and I don't want to hijack any of the other threads here for our device as none of them are related to this issue.
Here also seems to be a ghost town unfortunately.....
ogeid79 said:
Here also seems to be a ghost town unfortunately.....
Click to expand...
Click to collapse
Yeah unfortunately... It's a shame such a good phone is going to waste. I blame Umidigi
razen_kain said:
Ok I started this thread in hopes that I could get some answers from someone more knowledgeable than me on these MTK phones.
I've been reading online about flashing these GSI roms but I've seen multiple different methods. Some say use TWRP others say fastboot, or should I use SP flash tools...? And what are the proper wipes to prep for GSI flash? I've seen some say wipe everything except internal and others say just wipe dalvik/cache, and still others that say you must wipe in stock recovery then flash and boot twrp to flash system image...? Can any Umidigi Pros enlighten us a little? I'm sure google will bring more people to this page in time...or not?
I have flashed some GSI ROMs but everyone I've tried I cant seem to get root with Magisk. Magisk shows to be installed but when root apps call for root it just sits there and times out and I never get the prompt to grant root. This means I can't edit the APN which means no data which is not an option.
PS I've tried posting over in Umidigi community but it seems like a ghost town over there and I don't want to hijack any of the other threads here for our device as none of them are related to this issue.
Click to expand...
Click to collapse
There are several methods to flash the GSI:
1.- BY FASTBOOT
2.- FOR A PERSONALIZED RECOVERY (TWRP)
3.- FOR FLASH TOOL.
But looks like you've already flashed them.
But you have problems with the root, this is because the libdirect-coredump.so file was installed in the vendor folder and not in the system folder.
What you have to do is the following:
/vendor/lib/libdirect-coredump.so
COPIED TO
/system/lib/libdirect-coredump.so
and
*
/vendor/lib64/libdirect-coredump.so
COPIED TO
Code:
/system/lib64/libdirect-coredump.so
drkiro said:
There are several methods to flash the GSI:
1.- BY FASTBOOT
2.- FOR A PERSONALIZED RECOVERY (TWRP)
3.- FOR FLASH TOOL.
But looks like you've already flashed them.
But you have problems with the root, this is because the libdirect-coredump.so file was installed in the vendor folder and not in the system folder.
What you have to do is the following:
/vendor/lib/libdirect-coredump.so
COPIED TO
/system/lib/libdirect-coredump.so
and
*
/vendor/lib64/libdirect-coredump.so
COPIED TO
Code:
/system/lib64/libdirect-coredump.so
Click to expand...
Click to collapse
Wow! I can't believe someone finally responded. So was this an error in the build or is there something I can do with the system image to correct it?
I still have this phone but I don't use it as my dd but I'd still like to know.
razen_kain said:
Wow! I can't believe someone finally responded. So was this an error in the build or is there something I can do with the system image to correct it?
I still have this phone but I don't use it as my dd but I'd still like to know.
Click to expand...
Click to collapse
If you have TWRP, ENTER MOUNT and mount the System partition and the vendor partition, with the TWRP file manager copy the files that I put before
I'm never able to mount anything in TWRP 3.2.3 or 3.2.3v2 on the OnePro, what am I doing wrong ?
targa said:
I'm never able to mount anything in TWRP 3.2.3 or 3.2.3v2 on the OnePro, what am I doing wrong ?
Click to expand...
Click to collapse
Are you getting errors when you attempt to mount them? They should be like "invalid argument" or something like that. In this case, you should use SP Flash Tools to flash the entire Eragon v2.5 OS with it's scatter file to your device, it -should- disable the encryption stopping you from tampering with /system and /data, and other partitions.
Also, I've been seeing people saying that you can't pass safetynet checks on the Umidigi One Pro, you can.
- Running Havoc OS 2.0
- Using Magisk v23 with modules: MagiskHide, MagiskHidePropsConfig
- Force BASIC key attestation spoofed to OnePlus 6
- Device Fingerprint spoofed to OnePlus 6
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Something to note, I was not able to get the module Universal SafetyNet Fix working on the One Pro.

[ROM][JOLLA][UNOFFICIAL]LINUX SailfishOS 3.2 [UGGLITE] 08-03-2020

Jolla SailfishOS 3.2.0.12 linux
IT IS NO ANDROID!
There's no guarantee nothing, don't use it if you don't know what you're doing!
SAVE your DATA before!
Make sure you have a custom recovery installed (TWRP is the preferred recovery. [I'm not using Fox recovery, I'm not going to give you advice.])
The full install tested with Official ugglite 3.3.1 TWRP.
Download LineageOS 14.1 & SailfishOS.
NEED FREE INTERNAL STORAGE SPACE ~2GB!!!!!!
NEED UNSECURE EXT4 /data Partition!
Boot into recovery.
Wipe data, cache,system partitions.
(If your /data partition secured, you need format /data to ext4 if you want to use this ROM.)
Flash LineageOS 14.1 ugglite ROM in TWRP (sideload or copy any storage)
Reboot, start LineageOS 14.1 (If TWRP warn that there is no system, it doesn't matter, go reboot.)
First boot may take up to 2 minutes.
Restart to TWRP again.
Flash SailfishOS 3.2 ugglite in TWRP (sideload or copy any storage)
Reboot
First boot may take up to 1 minute.
ssh: [email protected] (change password: settings - developer menu)
Dual boot: flash with TWRP or 'fastboot boot' Lineage boot.img, or flash with TWRP or 'fastboot boot' hybris-boot.img, from zip files.
Sailfish OS workig from /data partition, if you wipe data, deleted Sailfish OS
BACKUP, before wipe data.
Bugs:
No bootsplash.
Boot time 50-60 sec. Power off charge animation ~50 sec. Reboot, and power off time 15-20 sec.
I could only create a Jolla account on a PC.
Some video types are not playable (Jolla license).
DOWNLOAD ROMS SF
DOWNLOAD ROMS AFH​
Known issues: don't know
I'm not going to give you support for privat upgrades and other changes, fix it for yourself. Sorry.
*
Screenshots: LINK
ROM OS Version: 14.1 & 3.2.0.12
ROM Kernel: Linux 3.18-31-szancso & 3.18.140-szancso
ROM info: Lineage-14.1, system partition, Android quota no.
If you have previously used Android 9.x or 10.x ROM which has a quota set on the data partition, you can remove the quota in TWRP, and not need format the data partition (this method tested, working was for me, but no guarantee for by all means)
commands:
Code:
tune2fs -O ^quota /dev/block/bootdevice/by-name/userdata
tune2fs -Q ^usrquota,^grpquota /dev/block/bootdevice/by-name/userdata
If you then use a ROM that configures quota (fstab.qcom), you can start over, if do not want quota. Or cleaning from fstab: "quota".
Created 2020-03-08
Last Updated 2020-03-08
I am not aware that it contains malicious code in the ROM, I have never put it in. This is a ported ROM, all its elements come from the Internet.
Test update and alien-dalvik Android support:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to update ?
ByHorvyCZ said:
How to update ?
Click to expand...
Click to collapse
I do not support the update.
There may be a problem with WiFi, sounds, lights, etc.
If you want to upgrade, you have to solve it yourself, because if you can't upgrade it yourself, you can't fix problems.
Alien-dalvik is not going to be with upgrade, a separate thing, and to my knowledge warez. Anyway, it's almost uselessly bad. (At least the version I tried.)
I do not support this too. Sry.
Yes you're right. I tried to make a force update through the terminal.
Now Wifi doesn't work. Otherwise, I put it into operation.
I upgraded the system just to make sure other accounts were working.
Warning, do this at your own risk.
!!You can ruin the system or worse the whole phone !!
So, okey, open your terminal. :angel:
Code:
devel-su
Then you enter the root password, :good:
Code:
ssu release 3.2.1.20
This sets up what you want the system to update
Code:
version --dup
This will start the process of updating.
You should never close the terminal when you're running this command.
After all, restart phone, and you are done ! :silly:

upgrade to Android 10 OTA with unlocked bootloader

Hi guys,
i hope you can help me a little. This phone drives me crazy.
The goal: Android 10 OTA with TWRP
What i did so far:
bought the downgrade firmware to v1.200 with techmesto
bootloader unlocked
flashed TWRP 3.3.1.0 via fastboot flash boot *.img
WIFI can not be activated on v1.200 firmware
( Update on 2020.11.22: Wifi only works if the montly timestamp of the rom security patch level is the same of the TWRP time stamp)
thats why OTA update via APP is not possible
because of that, i tryed to adb sideload via TWRP the OTA firmware v1.390 FULL OTA from telegram "Nokia OTA Repository" ( i know 390 is android9. It should be just the first step)
I did this on A
reboot
firmware is still v1.200 (WTF?)
got the information via telegram to change the slot, done via TWRP, switched to B
reboot
phone is booting to default recovery and saying "...00WW_1_390" ... "can't load android system. your data may be corrupt"
flashed TWRP 3.3.1.0 via fastboot flash boot *.img on B (i guess)
my phone is now booting to TWRP only
boot to TWRP and restored full backup of v1.200
Result: my phone is now booting to TWRP only, no matter i activate A or B in TWRP. What can i do?
Is it possible to flash the Nokia OTA Repositorys via TWRP?
Best,
Hi, you should not flash TWRP on the device except for if you want to flash a custom ROM. Due to the way TWRP for this model is developed, your WiFi will not work if you flash the TWRP image to you boot slot. Basically the same if you flash any modified boot image.
Also, since the boot image is what is responsible for getting your device to boot to the system, flashing a TWRP to boot slot can also result in the device not booting at all and instead getting stuck with TWRP only.
What I recommend:
Load TWRP, flash any full OTA (Android 9 or 10)
Do a full wipe (factory reset equivalent - essentially erase userdata) and then change the slot (if current is B, change to A). And finally reboot.
Good if the device boots up.
If not, please use NFT to flash any full OTA update you'll find in the Telegram channel (Android 10 preffered). That should get your device to boot normally
The culprit for your non-working WiFi is not the 1200 firmware, but the fact that you flashed the TWRP image to your boot slot I hope that helps
singhnsk said:
...What I recommend:
Load TWRP, flash any full OTA (Android 9 or 10)
Do a full wipe (factory reset equivalent - essentially erase userdata) and then change the slot (if current is B, change to A). And finally reboot. ...
Click to expand...
Click to collapse
This worked very well. ( before and after i did a normal wipe in twrp). After installing v1390, I did the factory reset not in twrp but , after a reboot, in the default recovery. And the phone now boots again to android.
Thank you very much.
So to sumarize: After flashing an OTA with TWRP or adb sideload it is very important to "... then change the slot (if current is B, change to A)"
Android v1.390 wants to install an update 1510MB in size , directly at the first start assistant. There is no option to proceed without that direct update.
Is it possible to loose my unlocked bootloader with this update?
Aha.. Yeah, if you reset the device while OEM Unlocking is not enabled in the Settings (which disables device protection features) and a Google account was added, then the phone will trigger FRP lock which will force you to connect to a WiFi network before you can get into the phone. And such WiFi will then force you to update the phone before you can start to use it.
You can update though. It is okay. It won't affect an already unlocked bootloader. The bootloader will remain unlocked ?
thanks, yeah, nearly all done on my phone now.
But .... the default recovery doesn't work. After selecting "recovery mode" in fastboot mode i get a dead android. Can i fix this some how ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
UPDATE: i found the solution to enter the recovery mode after seeing the dead andorid no command screen:
"You have to press and hold the power button. Now press and release the volume up button but continue to hold power button"
After that i could enter the recovery mode.

SM-G950U/U1/W Android 9/Pie Stock Roms With Safestrap Recovery-US Snapdragon Models-Will Work For Phones That Won't Boot With DRK Verity Failed Errors

You can have safestrap on pie android 9 which gives you some ability to modify system files flash zips etc and have access too data and other partitions that are normally blocked but you can not run root on android 9 because root on android 9 requires a modified boot image.
Phone that fail DRK or DM-Verity check in recovery and wont boot this will work on those.
All Samsung stock rom features will work just like a fully stock rom will
Anything here with a .7z extension will get unzipped before using
Anything here with a .zip extension will get flashed as zip in safestrap
Anything here with a .tar or .md5 gets flashed in odin
Anything here with a .img extension gets flashed as image in safestrap
Additional Help Can Be Found In The Telegram Channel
Telegram Channel For 8 Series Root
Stock Rom Feature:
Debloated
Safestrap Recovery- Can be used to modify system etc
Safetynet Passes
Samsung Pay,Pass,Secure Folder Working
Google Pay Working
Samsung Cloud Enabled
Places Tab Enabled Verizon
Spam Caller Id Enabled Verizon
Call Recording Enabled Verizon
Native Status Bar Speed Meter Enabled Verizon
Custom Boot Animation
Native Hotspot Enabled
Multi User Support
Downloads
Odin3_v3.14.1_3B_PatcheD.7z
G950U1UEU8DVD4_SAFESTRAP.7z -- US Carrier Unlocked U1 Firmware
G950USQU8DUJ1_SAFESTRAP.7z -- US Carrier Firmware U Firmware
G950WVLU8CUF3_SAFESTRAP.7z -- Canadian Firmware
Prerequisites Before Flashing Pie With Safestrap Roms
You must have safestrap installed. Method too achieve this found Here
Pie With Safestrap Roms
1. Copy pie system image to your phone while phone is booted normally the image is too big too copy while booted in safestrap. This image will be flashed in safestrap using install tab and the the flash image tab at bottom. System images get flashed too system partition
2. After done flashing pie rom on initial flash of pie system image in safestrap you need to wipe data in safestrap reboot too download and flash BL_G95******_LEAVE_SAFESTRAP_V8.tar.md5 in BL slot in odin and G950U_CACHE_FORCE_REBOOT_V8.tar.md5 in Userdata slot in odin the phone will boot too stock recovery where you need to wipe cache and reboot .
3. Rebooting too stock recovery only needs to be done on initial pie system image flash or a reflash of a system image in safetrap. Rebooting back too safe strap and leaving will only require flashing BL_G95******_LEAVE_SAFESTRAP_V8.tar.md5 in odin BL slot and you can just let phone boot normally.
4. To enter safestrap on pie rom you will need too reboot too download mode and flashBL_ENG_BOOTLOADERS_SAFESTRAP_G95**_V8.tar.md5 in odin BL slot and when phone reboots it will reboot directly too safestrap. This may take a few seconds too up to a minute so be patient.
5. To leave safestrap and return too rom reboot too download mode and flash BL_G95******_LEAVE_SAFESTRAP_V8.tar.md5 in BL slot of odin and just let phone boot normally
6. Sometimes in safestrap when flashing zips you may get an error about failing too unmount system/resources busy most of the time this doesnt affect anything but if you get the error it would be a good idea to reboot recovery before flashing or doing anything else required in recovery.
Video Instructions
Video Safestrap.mp4
drive.google.com
SM-G955U/U1/W Files Found Here
SM-G955U/U1/W Android 9/Pie Stock Roms With Safestrap Recovery-US Snapdragon Models-Will Work For Phones That Won't Boot With DRK Verity Failed Errors
You can have safestrap on pie android 9 which gives you some ability to modify system files flash zips etc and have access too data and other partitions that are normally blocked but you can not run root on android 9 because root on android 9...
forum.xda-developers.com
jrkruse said:
So what can I do with a stock rom with no root and safestrap
Ever want diiferent boot animation
bootanimation.mp4
drive.google.com
Click to expand...
Click to collapse
Ever want stock call recording
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How about host adblocking?
How about access to data partition?
How about ability to delete or add apps to system apps?
How about make real data backups?
How about add particular CSC features or easily change CSC code?
How about add a CSC code not available on stock phone?
How about bypass certain hotspot restrictions?
How about edit the build.prop to maybe add multiuser support
These are just a few things you can do with safetrap?
This might sound stupid but is this root? or just a stock rom? cuz i really do like what this offers.

SM-N950U/U1/W Android 9/Pie Stock Roms With Safestrap Recovery-US Snapdragon Models-Will Work For Phones That Won't Boot With DRK Verity Failed Errors

You can have safestrap on pie android 9 which gives you some ability to modify system files flash zips etc and have access too data and other partitions that are normally blocked but you can not run root on android 9 because root on android 9 requires a modified boot image.
Phone that fail DRK or DM-Verity check in recovery and wont boot this will work on those.
All Samsung stock rom features will work just like a fully stock rom will
Anything here with a .7z extension will get unzipped before using
Anything here with a .zip extension will get flashed as zip in safestrap
Anything here with a .tar or .md5 gets flashed in odin
Anything here with a .img extension gets flashed as image in safestrap
Additional Help Can Be Found In The Telegram Channel
Telegram Channel For 8 Series Root
Stock Rom Feature:
Debloated
Safestrap Recovery- Can be used to modify system etc
Safetynet Passes
Samsung Pay,Pass,Secure Folder Working
Google Pay Working
Samsung Cloud Enabled
Places Tab Enabled Verizon
Spam Caller Id Enabled Verizon
Call Recording Enabled Verizon
Native Status Bar Speed Meter Enabled Verizon
Custom Boot Animation
Native Hotspot Enabled
Multi User Support
Downloads
Odin3_v3.14.1_3B_PatcheD.7z
N950USQS8DVB1_SAFESTRAP.7z -- US Carrier Firmware U Firmware
N950U1UEU8DUE2_SAFESTRAP.7z -- US Carrier Firmware U1 Firmware
N950WVLU8DUG1_SAFESTRAP.7z -- Canadian Firmware
Prerequisites Before Flashing Pie With Safestrap Roms
You must have safestrap installed. Method too achieve this found Here
Pie With Safestrap Roms
1. Copy pie system image to your phone while phone is booted normally the image is too big too copy while booted in safestrap. This image will be flashed in safestrap using install tab and the the flash image tab at bottom. System images get flashed too system partition
2. After done flashing pie rom on initial flash of pie system image in safestrap you need to wipe data in safestrap reboot too download and flash BL_N95******_LEAVE_SAFESTRAP_V8.tar.md5 in BL slot in odin and N950U_CACHE_FORCE_REBOOT_V8.tar.md5 in Userdata slot in odin the phone will boot too stock recovery where you need to wipe cache and reboot .
3. Rebooting too stock recovery only needs to be done on initial pie system image flash or a reflash of a system image in safetrap. Rebooting back too safe strap and leaving will only require flashing BL_N95******_LEAVE_SAFESTRAP_V8.tar.md5 in odin BL slot and you can just let phone boot normally.
4. To enter safestrap on pie rom you will need too reboot too download mode and flashBL_ENG_BOOTLOADERS_SAFESTRAP_N95**_V8.tar.md5 in odin BL slot and when phone reboots it will reboot directly too safestrap. This may take a few seconds too up to a minute so be patient.
5. To leave safestrap and return too rom reboot too download mode and flash BL_N95******_LEAVE_SAFESTRAP_V8.tar.md5 in BL slot of odin and just let phone boot normally
6. Sometimes in safestrap when flashing zips you may get an error about failing too unmount system/resources busy most of the time this doesnt affect anything but if you get the error it would be a good idea to reboot recovery before flashing or doing anything else required in recovery.
Video Instructions
Video Safestrap.mp4
drive.google.com
jrkruse said:
So what can I do with a stock rom with no root and safestrap
Ever want diiferent boot animation
bootanimation.mp4
drive.google.com
Click to expand...
Click to collapse
Ever want stock call recording
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How about host adblocking?
How about access to data partition?
How about ability to delete or add apps to system apps?
How about make real data backups?
How about add particular CSC features or easily change CSC code?
How about add a CSC code not available on stock phone?
How about bypass certain hotspot restrictions?
How about edit the build.prop to maybe add multiuser support
These are just a few things you can do with safetrap?
edit nvm i had skipped a step. the video helps alot thank you.
nvm stupid question i figured it out. everything is done. thanks.

Categories

Resources