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.
Related
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 ?
Hi sorry if i post in bad section so i need help i downloaded an CWM ClockWorkMod Recovery for SM-G318H Samsung Galaxy Trend 2 lite i apply the update so it was almost done but an error marked in red and reboot after update failure.
Any suggestion it happens with any zip file for Temp Recovery i have here an picture :crying:
I Attached an picture with the failure so if you have any suggestion reply there.
P.S. I Don't trust changing permanent recovery and even download mode odin.
@AlinTecsan
You used phone's Stock Recovery to flash something other than the phone's signed Stock ROM. Hence you got "E: signatue verification failed" error.
Flashing CWM on stock recovery
jwoegerbauer said:
@AlinTecsan
You used phone's Stock Recovery to flash something other than the phone's signed Stock ROM. Hence you got "E: signatue verification failed" error.
Click to expand...
Click to collapse
This i know so i try flashing the CWM so this not work so to sign the custom recovery with signed stock rom so how i fix thanks for replying
@AlinTecsan
Look inside here.
Looked Here
jwoegerbauer said:
@AlinTecsan
Look inside here.
Click to expand...
Click to collapse
I Looked here so fastboot it flash and erase sorry so my phone will not support the advanced boot options and no match found for my model at all so thanks again for the link
Use TWRP instead of CWM
@AlinTecsan
It’s true that CWM Recovery is a widely used recovery, but it’s not anymore in the league, now it’s TWRP all the way up with no contender around!
Since the software company which developed CWM Recovery has stopped building its versions anymore, there are no new releases of CWM Recovery released within the last 5 years what are ready to be used on mainstream Android devices.
Take note that TWRP can get successfully flashed on A/B systems.
TWRP Will work for my device?
jwoegerbauer said:
@AlinTecsan
It’s true that CWM Recovery is a widely used recovery, but it’s not anymore in the league, now it’s TWRP all the way up with no contender around!
Since the software company which developed CWM Recovery has stopped building its versions anymore, there are no new releases of CWM Recovery released within the last 5 years what are ready to be used on mainstream Android devices.
Take note that TWRP can get successfully flashed on A/B systems.
Click to expand...
Click to collapse
Does have what have cwm?Like factory reset apply update from sdcard sideload cache wipe reboot and change theme i would like to try hope the file is compatibile with my device before to start i will backup the stock recovery :good:
AlinTecsan said:
Does have what have cwm?Like factory reset apply update from sdcard sideload cache wipe reboot and change theme i would like to try hope the file is compatibile with my device before to start i will backup the stock recovery :good:
Click to expand...
Click to collapse
{
"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"
}
I Flash an 2.8.7.0 TWRP
jwoegerbauer said:
Click to expand...
Click to collapse
It work fine so i need to change to red if possible so work good so i sent pictures soon I like to know how i restore the stock recovery i backup the whole firmware so i like to change to red .TWRP Work with all devices?
@AlinTecsan
You have to re-flash device's Stock ROM to get device's Stock Recovery back.
Stock ROM And recovery
jwoegerbauer said:
@AlinTecsan
You have to re-flash device's Stock ROM to get device's Stock Recovery back.
Click to expand...
Click to collapse
I have to say i extract from my correctly firmware code the recovery.img so i will made an tar file or i guess to restore recovery stock in case of problem so i know with .tar.md5 backups.
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.
Ok i need some emergency help please: what i did:
Downloaded stock rom (exact version number of my Infinix Note 10i X659B) X659B-H696AvAw-R-OP-210330V152
Grabbed boot.img, placed on phone folder,
installed magisk apk, patched with magisk apk and put that patched-img to the folder in my PC.
Got minimal adb tools, used adb reboot bootloader to put phone on fastboot (saw fastboot screen on phone) did:
fastboot flash boot_a patch-boot.img
fastboot flash boot_b patch-boot.img
(renamed the file to patch-boot.img for convenience)
Now phone is stuck booting
{
"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"
}
i only see the "Infinix" start up screen, then a message: Orange State: Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
to be fair that message appeared when i unlocked the bootloader, and beside the data wipe, the phone worked just fine
So where i think i screwed up is by installing it on boot_b too, (guide i followed said that i should also patch boot_b if my phone have a/b system (which it does, also magisk app also told me)
So what i can do? I cant seem to be able to put my phone down on fastboot again to try to patch either the stock image or reflash the whole phone. Or i just bricked my brand new phone? :'(
With Android having an A/B image partition layout the user-runable Android is that in slot A. Slot B is only used to temporarily store OTAs: When update process successfully ends then at phone's reboot whole slot B gets copied into slot A and finally device gets booted into updated slot A. My POV: It's always an idiocy to flash a patched boot.img to slot B.
To get rid off of all modifications you applied so far you're recommended to re-flash phone's Stock ROM.
jwoegerbauer said:
with Android having an A/B image partition layout the working Android is that in slot A. Slot B is only used to temporarily store OTAs: When update process successfully ends then at phone's reboot whole slot B gets copied into slot A and finally device gets rebooted ( into updated slot A ). My POV: It's always an idiocy to flash a patched boot.img to slot B.
To get rid off of all modifications you applied so far you're recommended to re-flash phone's Stock ROM.
Click to expand...
Click to collapse
How you can recommend i reflash the whole rom? I cant seem to find how to get the phone into another state. Volumen Up + Power does nothing, phone keeps trying to reboot.
Volume Down + Power does nothing either
Volume UP+Down+Power keeps the screen off, but i can hear windows connecting/disconnecting every 10 seconds or so. so how i connect it to, lets say, SP Flash Tools (considering is a MTK device)?
Well tried to do it with SP Flash Tools, but after trying to "Format All+Download" with all the checkboxes subsystems selected, i get a "auth file needed" error
Didn't find any of that in the firmware i downloaded :c
You need mtk bypass tool for that
mgdark said:
Well tried to do it with SP Flash Tools, but after trying to "Format All+Download" with all the checkboxes subsystems selected, i get a "auth file needed" error
Didn't find any of that in the firmware i downloaded :c
Click to expand...
Click to collapse
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.