Question OTA failed on rooted device? - OnePlus Nord N200 5G

I'm not sure if it's just me, but:
{
"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"
}

btw safetynet passes

T3CHN0T33N said:
I'm not sure if it's just me, but:View attachment 5441879
Click to expand...
Click to collapse
you could try unrooting, updating the ota, then reflashing magisk again. or you could simply flash the OTA update from twrp.

I'll probably just flash the OTA via adb & fastboot... but do you know where to get the OTA updates?

this?

oh, well that explains some stuff...

rooted stock ROM with stock recovery. I have not tried sideloading it, I will try that. I will report back when I do

Revert boot back to original with Magisk uninstall
After reverting back to original, go to apply OTA update.
After applied OTA, go back to Magisk and install in unused partition, and reboot after finished.

I had the same problem, went through a whole bunch of different methods (which I edited out of this post and hid below) until I figured out my problem was when I installed magisk I followed the official guide and did "fastboot flash boot boot_patched.img" I believe this flashes both A and B boot partitions, and the OTA checks both partitions for untouched hash values. I believe doing Magisk restore image or uninstall doesn't restore both partitions, only the active one.
To recover from this, I used MSMDownloadTool to restore to factory image, then I followed this guide to install Magisk and only touch the active partition (the key command is to use fastboot boot boot_patched.img and then direct install Magisk from Magisk Manager). To get OTA update, you can do Magisk restore image, then install the OTA update, then repeat the above. I think the phone automatically reboots after OTA finishes so you can't really keep Magisk, you have to reinstall Magisk after the reboot.
I'm guessing you don't necessarily have to restore to factory image, you could just do fastboot flash boot_a boot.img and fastboot flash boot_b boot.img to reset the device to pass OTA check and then reinstall Magisk using the method above.
I have the same problem, stock recovery. I tried uninstalling Magisk using "restore image" (I had to also make my own Magisk backup boot.img to do this following this guide) and applying the update but it didn't work. Reading the logcat the error message is "The hash of the source data on disk for this operation doesn't match the expected value".
I used EnumC's stock boot.img from his root guide, but not sure if that is the issue or not.
Even completely uninstalling Magisk and rebooting doesn't allow the update. I'm not sure how they detect it. It did finally let me update after doing a factory image reset and OEM unlock with MSMDownloadTool.
If you really want Magisk and updates you can extract boot.img from here, patch it with Magisk, and flash it. I don't think I'm going to bother with that because after a factory image reset you lose all of your data and you have to go through the setup process again, and you get all of the default bloat apps back.

I found out that disabling "Automatic system updates" under Developer Options means the phone won't automatically reboot during the OTA so I tried to get the 11.0.1.8 update using Magisk's "install to inactive slot after OTA". For whatever reason that bricked my phone. The method I ended up doing was:
Uninstall Magisk, Restore images
Get OTA, but don't reboot when it says to
adb su and then dd the new boot.img
Continue system update and reboot the phone
Patch the new boot.img in Magisk
fastboot boot the new patched.img
Direct install Magisk and reboot

mingkee said:
Revert boot back to original with Magisk uninstall
After reverting back to original, go to apply OTA update.
After applied OTA, go back to Magisk and install in unused partition, and reboot after finished.
Click to expand...
Click to collapse
I know it's been a while but, Magisk just completely removes itself when uninstalling, making it imposable to "install to inactive slot after OTA"

T3CHN0T33N said:
I know it's been a while but, Magisk just completely removes itself when uninstalling, making it imposable to "install to inactive slot after OTA"
Click to expand...
Click to collapse
Make sure you do Uninstall Magisk > Restore Images instead of Complete Uninstall. Then do OTA, when OTA says reboot now instead of rebooting do Magisk install to inactive slot, then reboot.
Yeah I think the safest way is to completely uninstall Magisk and not use Magisk's inactive slot option, I think the OTA needs to verify the boot sector before finishing the update otherwise you may get in a bootloop. I tried doing the inactive slot option and the OTA is still stuck on the reboot step.
To fix this I uninstalled Magisk completely, booted back to the old slot and then ran OTA reboot. Then I installed Magisk as normal.

Related

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.

HELP! [Infinix HOT 10i X659B] Phone stuck at booting after trying to install a patched-boot from Magisk.

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

Question How to correctly Root and install TWRP in T225N?

It is now on android 11, 32 storage, sim support
Current guides aren't enough for me
m
Civil123y said:
Current guides aren't enough for me
Click to expand...
Click to collapse
why? have unlocked bootloader already ? please show your download mode screen.!
For this step Yes i unlocked successfully
What i did next is flashing whole ap patched with bl cp csc
I have root and r/w system.
Whole AP or just boot.img?
Abish4i said:
Whole AP or just boot.img?
Click to expand...
Click to collapse
Whole( i tried boot.img once it works without system rw)
With whole, i can use mixplorer and lucky patcher to remove system apps completely.
And i didn't succeed running twrp
Civil123y said:
Whole( i tried boot.img once it works without system rw)
With whole, i can use mixplorer and lucky patcher to remove system apps completely.
And i didn't succeed running twrp
Click to expand...
Click to collapse
what your magisk version.? didn't success run or access twrp? how did you installed twrp file?
tom.android said:
what your magisk version.? didn't success run or access twrp? how did you installed twrp file?
Click to expand...
Click to collapse
My tab is 225n,
i used 225 twrp
I flashed it in user data slot once with ap ,,,csc,,,etc
And i tried it in ap slot.
Posts about twrp are a bit vague to me.
Magisk 25.2
I tried 24 also
Could i have done it wrong. I followed guides out there
Civil123y said:
Could i have done it wrong. I followed guides out there
Click to expand...
Click to collapse
Can you show log from ODIN? Did it successfully went through also did you uncheck auto reboot as well as multidisabler after.
Check specifically magisk 24.2
Civil123y said:
Could i have done it wrong. I followed guides out there
Click to expand...
Click to collapse
OK listen carefully this is my trick to install this twrp.
1. don't used latest uses only v.24.x
2. patch magisk the whole ap file. and flash it at AP slot of Odin.
3. flash BL ,CSC in normal way.
4. OK if flash twrp.tar file at USERDATA slot
5. if you not set to disable auto-reboot at Odin option , you must very quickly press and hold power+vol up yourself.
6. if you can't access to twrp ( recovery mode ) in step 5 please uses command > adb reboot recovery
**** please use magisk v24.x only for the 1'st time to access twrp.
Abish4i said:
Can you show log from ODIN? Did it successfully went through also did you uncheck auto reboot as well as multidisabler after.
Check specifically magisk 24.2
Click to expand...
Click to collapse
Odin passed successfully, no errors, (if multidisabler is inside twrp , i can't run twrp at all)
tom.android said:
OK listen carefully this is my trick to install this twrp.
1. don't used latest uses only v.24.x
2. patch magisk the whole ap file. and flash it at AP slot of Odin.
3. flash BL ,CSC in normal way.
4. OK if flash twrp.tar file at USERDATA slot
5. if you not set to disable auto-reboot at Odin option , you must press and hold power+vol up yourself.
6. if you can't access to twrp ( recovery mode ) in step 5 please uses command > adb reboot recovery
**** please use magisk v24.x only for the 1'st time to access twrp.
Click to expand...
Click to collapse
Number 4? Should i flash it with number 3 or i should reboot again to download mode to flash it separately.?
I should use twrp from github 225 for my 225n?
@tom.android couldn't we just skip 5 step.
i.e start without flashing TWRP.
Civil123y said:
Number 4? Should i flash it with number 3 or i should reboot again to download mode to flash it separately.?
I should use twrp from github 225 for my 225n?
Click to expand...
Click to collapse
What is your KG status?
odin slot
1.BL slot. >>bl file from your firmware.
2.AP slot.>>ap file (patch from magisk v24)
3.CP slot.>>cp file from your firmware
4.CSC slot>>csc file from your firmware
( safty first not uses CSC_HOME
5.USERDATA>> twrp.tar
-flash all at the same time.
-Disable auto-restart from odin option
when odin finished flashing you must press and hold (power + vol up.) to access recovery mode.
can't used "multidisabler"???
- another error may be this twrp 225 not for 225N. don't known sorry.
Abish4i said:
@tom.android couldn't we just skip 5 step.
i.e start without flashing TWRP.
What is your KG status?
Click to expand...
Click to collapse
This before flashing, right now
{
"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"
}
Not working after reflashing stock and doing steps.
Civil123y said:
Not working after reflashing stock and doing steps.
Click to expand...
Click to collapse
Use telegram?
And did you use CSC and patched ODIN?
Currently your CSC is ?
Can access recovery mode or not , what showing up.

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