upgrade to Android 10 OTA with unlocked bootloader - Nokia 7.2 Questions & Answers

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.

Related

will you solve this?

Ok, I'll explain the problem(s)
My mate 10 pro (BLA-L09) can boot in recovery (TWRP 3.2.1-0) and fastboot:
When I flash other recovery with the .img by recovery (like for example the stock recovery) give me error;
When I flash other recovery with the .img by fastboot (like for example the stock recovery) give me error;
When I flash ROM by .zip/UPDATE.APP give me error;
In fastboot mode I read "Phone Locked FRP unlock"
the phone has no ROM in it, wehn I boot it automatically put me to recovery;
So, My bootloader is locked and I can't unlock it beacause I can't boot the phone.
I just want to reinstall the stock ROM, have you any ideas?
thanks to all
flash recovery from fastboot
Shandroid_94 said:
Ok, I'll explain the problem(s)
My mate 10 pro (BLA-L09) can boot in recovery (TWRP 3.2.1-0) and fastboot:
When I flash other recovery with the .img by recovery (like for example the stock recovery) give me error;
When I flash other recovery with the .img by fastboot (like for example the stock recovery) give me error;
When I flash ROM by .zip/UPDATE.APP give me error;
In fastboot mode I read "Phone Locked FRP unlock"
the phone has no ROM in it, wehn I boot it automatically put me to recovery;
So, My bootloader is locked and I can't unlock it beacause I can't boot the phone.
I just want to reinstall the stock ROM, have you any ideas?
thanks to all
Click to expand...
Click to collapse
If the FRP is unlocked, just unlock your bootloader again with your unlock code from huawei.
Or pay 4 euros and use dc unlocker.
I can't unlock bootloader 'cause dc unlocker can give me the code only when the smartphone is booted, and it hasn't a ROM mounted in..
Could you specify the error?
EngrVan said:
Could you specify the error?
Click to expand...
Click to collapse
which one?
Shandroid_94 said:
When I flash other recovery with the .img by recovery (like for example the stock recovery) give me error;
When I flash other recovery with the .img by fastboot (like for example the stock recovery) give me error;
Click to expand...
Click to collapse
These.
EngrVan said:
These.
Click to expand...
Click to collapse
1st pic, tried to flash recovery.img by fastboot;
2nd pic, tried to flash system.img by fastboot;
3rd pic, tried to flash stock ROM by TWRP 3.2.1-0 (Yeah, it CAN'T works, but whatever I flash it's the same results)
4th pic, dc-unclocker that can't pick up code for unlocking bootloader
{
"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"
}
Should have used dc-unlocker to read the bootloader code first, then unlock manually.
Now you have two options; wait for the unlock code page to get back up or use FunkyHuawei to restore your phone.
Since you don't have your bootloader unlocked you can't flash images as the partitions are protected. This causes the "Command not allowed" errors.
How did you erase/delete/remove the ROM in the first place? Anything you did before the incident?
Try to boot to erecovery... (vol + on boot w/o usb cable plugged in) Load the rescue system image over wifi. Hope it works!
I said just unlock bootloader because obviously you must alredy have the code if you have TWRP installed, that means that at some point you had it unlocked and you should have a code.
Anyway, huawei unlock page is up, so you should be able to get the code again in case you lost it. Dcunlocker gives your the data needed like imei, product id (not sure about this one) and SN in the box.
I think dc unlocker can unbrick your device (you need like 15 credits) it uses a back door to flash and unbrick. then you can get the unlock code to unlock.
Another thng you can try is flashing the BLA-Recovery no check from hwota8 directrly from TWRP (flash image) transfer it to your device through mtp or adb push.

[FW] 7.1.1 & 6.0.1 Service Tech Firmwares - Debrick - Upgrade - Downgrade

FOR THE ASUS 3 ZOOM ZE553KL
I Found These Working Asus Service Technicians Full Stock Firmwares. They Include Files That Are Not In Asus' Website FW.
Includes The Last 7.11 Nougat Before Oreo Was Released
Info I Found About Tech Fw:
note that this firmware is different from the usual firmware by asus. It is used for servicing the phone, it restores all partition from factory except for imei, s/no, mac address etc. Google account lock is active in this firmware.
The firmware is used by asus flash tool to restore your phone partitions. If by any chance, the restore is not successful using the tool, just unzip the file and flash manually (flashall_aft.cmd)
you need this firmware if your partitions are totally corrupted (example if you cannot go into fastboot mode). Most of the time, bricked phones can be restored by flashing asus stock recovery (recovery.img), then stock asus firmware. If that doesn't solve the bricking, then you will need the raw/service firmware.
Click to expand...
Click to collapse
These Are Untouched Full Stock FW
You Can Just Flash The Normal Files Recovery.img, Boot.img And System.img To Change Android Versions Or To Unbrick
Recovery.img, Boot.img And System.img And The Emmc_appsboot_8953.mbn File (Could Be The Bootloader)were The Only Changes Throughout The Fw's, All The Other Files/partitions Are The Same Such As The Radios Etc
The Bootloader Lock Status Doesnt Get Changed Afaik
You Can Still Update Using Asus' Builtin Update
They Are In Zip Format, Unzip Them To Their Own Folder
HOWTO FLASH
PREREQUISITES:
Make A Nandroid Backup
If Bootable Remove/Signout Of Google Account
(Might Work With Locked Bootloader, IDK)
Ze553kl(Zenfone3 Zoom) Phone With Unlocked Bootloader(used unlocker apk from asus website when phone was in running state)
Unlocking Bootloader App Available From Asus - was for upto nougat 7.11
Usb Asus Drivers
Usb Debugging Enabled On Phone, Maybe Not But Wont Hurt To Try
Computer Running Windows
Usb Data Cable For Phone
ON PHONE
If Bootable Enable Usb Debugging, Uncheck Verify Apps Via Usb, Remove Google Account
Backup Internal Sdcard - Most Def As It Will Get Wiped
Make Nandroid Backup
Remove Sdcard, Just In Case
Put Phone Into Fast Boot Mode- Unplugged, Phone Powered Off - Vol Up + Power Button Pressed, Hold Both Until Screen Comes On.
Plug Usb In Cable To Phone From Pc.
METHODS:
After Unzipping Them To Their Own Folder
1. From Within The Extracted Folder Double Click "Flashall_aft.cmd" Will Auto Open Command Prompt And Start Flashing All The Files Via Its Included Fastboot, Or....
2. Manually Open Command Prompt Within The Unzipped Folder And Type "Flashall_aft.cmd", Or....
3. Use Your Local Copy Of Adb/Fastboot And Manually Flash These Files And Commands:
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot format userdata
fastboot reboot
------------------------------------------------------------------------
IF STILL BRICKED OR ODD BEHAVIOR BUT CAN BOOT TO BOOTLOADER/FASTBOOT THEN DO THESE COMMANDS WHEN IN FASTBOOT MODE
Code:
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot erase userdata
fastboot -w
fastboot erase splash
fastboot erase cache
THEN RE-BOOT BACK INTO BOOTLOADER AND CHOOSE ONE OF THE THREE METHODS
- -------------------------------------------------------------------------------------
Disclaimer Im Not Responsible For Yours Or Anyone Elses Devices, Do At Your Own Risk
DOWNLOADS
FIRMWARES I FOUND UPLOADED TO ANDROIDFILEHOST:
CHECK THE MD5 AFTER DOWNLOADING.
ZE553KL-WW_71.60.139.30_7.1.1_NOUGAT_2018/03.zip - The Last Nougat Before Release Of Oreo
Just Want To Flash The Base Files, Goto This Thread By Me
ZE553KL-WW-20.32.67.25_7.1.1_NOUGAT_2017/07.zip
ZE553KL-WW_11.40.86.71_ 6.0.1_MM_2017/04.zip - Not Tested By Me
ZE553KL-WW_10.40.47.107_6.0.1_MM_2017/02.zip - Afaik The Initial Fw Shipped W/the Phone
ADB_FASTBOOT_1.4.1.ZIP
SCREENSHOTS
ZE553KL-WW_71.60.139.30_7.1.1_NOUGAT_2018/03
{
"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"
}
..
ZE553KL-WW_10.40.47.107_6.0.1_MM_2017/02
..
..
..
Hi all, which twrp for ze553kl mm?
Ciao
Bassofondale said:
Hi all, which twrp for ze553kl mm?
Ciao
Click to expand...
Click to collapse
try the latest from here, currently twrp-3.2.3-0-Z01H-20181014.img
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Thank you!

TWRP 3.3.1-Z3 Build 2020-02-12

{
"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"
}
This is the latest TWRP 3.3.1 build by The Muppets.
This TWRP supports Android 8-10 for now.
ROM recommended:
LineageOS 16.0, LineageOS 17.1 and CarbonRom 8.0
Download:
TWRP 3.3.1-Z3 or Mirror
How to install:
First of all you MUST flash lastest 23.5.A.1.291 firmware with FlashTool at least one time, for upgrade the bootloader (You need this upgrade for boot on recovery).
Via fastboot:
Reboot your phone on fastboot mode.
Flash revovery using this command:
Code:
fastboot flash FOTAKernel <filename>
Via Official TWRP App (You need root):
Install the app from Google Play Store and download recovery
Copy it to your internal or external memory.
Open the app, give root permissions and tap on TWRP FLASH.
Tap on Select a file to flash...
Select the recovery.img and flash it.
Via Old TWRP (You need root):
Download the zip TWRP here.
Reboot to old TWRP.
Choose your TWRP zip file and FLASH.
Wipe dalvik/cache.
Reboot
Version Information
Status: Stable
Created: 2019-10-28
Last Updated: 2020-02-12
This is a joke, isn't it?
Not working. Anyway.
kvadratt said:
Not working. Anyway.
Click to expand...
Click to collapse
Look my update thread, you can try Flash via old twrp...
Twrp
Hey guys
I want to install lineage 16 and I need twrp 3.3
Twrp install with success but dosen't work
Pls help
Sony z3 dual d6633
23.5.A.1.291
ronnay ryukay said:
Look my update thread, you can try Flash via old twrp...
Click to expand...
Click to collapse
Hi ronnay.
There's any difference between twrp-3.3.1-0.4 by NeoArian i've installed now?
Which is more newer twrp?
Thx.
jmpcarceles said:
Hi ronnay.
There's any difference between twrp-3.3.1-0.4 by NeoArian i've installed now?
Which is more newer twrp?
Thx.
Click to expand...
Click to collapse
There, this is the TWRP recommendation version for LOS 16 and 17.1
What's the difference between TWRP 3230 flashed lineage os or any other and TWRP 3310 flashed...
Working?
Is this custom recovery working because I'm afraid to flash it?
Looks like is not working... I've flashed this recovery because I want to flash the latest Carbon Rom and when I enter on recovery, it just reboots the phone. I had to reinstall my old recovery and now is working again. I'll try to find another version.
Best regards.
I was able to install this recovery. Unfortunately, adb sideload does not work for me. Whenever I start adb sideload, adb on my computer cannot see my device anymore. As soon as I leave adb sideload, adb works again and lists my device as expected.
Is this a known bug? Or has anyone a solution to this problem?
I am using adb version 30.0.3-6597393 with adb-bridge version 1.0.41 on Windows 7. I installed the original Sony adb drivers from the Sony developer website.
Nasion06 said:
Is this custom recovery working because I'm afraid to flash it?
Click to expand...
Click to collapse
Hello again,
I was wrong, is working fine but you have to check if works in your phone. If you have unlocked the bootloader just enter into fastboot and flash it as FOTAKernel or recovery. If doesn't enter into recovery and it just reboot the phone, don't panic, because always you can use the fastboot mode to install an old version. I've fixed this problem using the Emma software from Sony (aka Sony Flash Tool), and installing the latest version (WARNING: all data will be erased).
If you have an updated version of Android (mine was Carbon 6.1 and that is why it failed), then maybe you'll not have any problem.
EDIT: I recomend you to flash one version of the TWRP as "recovery" (fastboot flash recovery recovery.img), because it works even when the phone won't boot. My phone was not booting and it just vibrated without showing the Sony logo, so I was not able to enter to the FOTAKernel recovery, and this recovery was always working allowing me to recover the phone.
Best regards.
Flash to boot only
I currently have TWRP 3.2.3 and am using Carbon Rom 6.1
I downloaded it and rebooted to recovery.When I went to flash the only option is flash to boot.Nothing else.Thank you for taking your time to reply.I am not going to flash this because in about a year I will get a new phone and I don't want to hard brick my Z3.
Thank you and best regards,
Nasion G.
Sony z3 single d6033
23.5.A.1.291
"fastboot reboot recovery" doesn't boot into the twrp
Instead it boots into the system
But if I boot the phone with "PWR+VolDOWN" pressed, I reach the working TWRP.
Thank you!
I can confirm the above:
command: fastboot flash recovery twrp-3.3.1-z3-20200212.img
optional command: fastboot reboot -> turn phone off
Press "PWR+VolDOWN" to start your phone into TWRP
Install your ROM via MicroSD - possibly sideloading works as well, haven't tried
twrp-3.3.1-z3-04.img support os 17.1 restore function.
Only after restore, flash one file[fix_rootfs_label.zip].
Code:
sony z3 os 17.1 TWRP v3.3.1-0.4_Z3
Download
displaciamento said:
I can confirm the above:
command: fastboot flash recovery twrp-3.3.1-z3-20200212.img
optional command: fastboot reboot -> turn phone off
Press "PWR+VolDOWN" to start your phone into TWRP
Install your ROM via MicroSD - possibly sideloading works as well, haven't tried
Click to expand...
Click to collapse
I did as shown in the post, I pressed the power down vol buttons and it doesn’t go up.
araujo99 said:
I did as shown in the post, I pressed the power down vol buttons and it doesn’t go up.
Click to expand...
Click to collapse
You try pressed the power buttom. Then you will see the SONY screen and the phone is shocked, press vol down button.

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

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