Does anyone know where to get the stock boot.img? I have artic & travis' custom kernel flashed and, long story short, I need to flash back to stock for now. I have a MetroPCS model btw.
use payload dumper and extract boot.img from latest firmware downloaded from oneplus website
Software Upgrade - OnePlus.com
Get the latest OxygenOS updates for your device.OxygenOS is always evolving. Learn about the latest features and improvements, and get even more out of your device.
www.oneplus.com
[TOOL] A QUICK Android OTA payload dumper
Made with Go. By utilizing goroutines, this can extract img files from (full) OTA payload.bin really quickly. See how fast this is: https://i.imgur.com/adpijqf Source Code: https://github.com/ssut/payload-dumper-go Prebuilt binaries...
forum.xda-developers.com
Ytube21 said:
use payload dumper and extract boot.img from latest firmware downloaded from oneplus website
Software Upgrade - OnePlus.com
Get the latest OxygenOS updates for your device.OxygenOS is always evolving. Learn about the latest features and improvements, and get even more out of your device.
www.oneplus.com
[TOOL] A QUICK Android OTA payload dumper
Made with Go. By utilizing goroutines, this can extract img files from (full) OTA payload.bin really quickly. See how fast this is: https://i.imgur.com/adpijqf Source Code: https://github.com/ssut/payload-dumper-go Prebuilt binaries...
forum.xda-developers.com
Click to expand...
Click to collapse
That's OEM and will prevent me from updating OTA
You can factory reset and then use the GSI method to get a copy of stock boot.img, I don't know if anyone has done this before for MetroPCS
I have most of the previous Tmobile boot.img available at this archive, I don't know if it works for MetroPCS: https://androidfilehost.com/?w=files&flid=329532
T-Mobile and MetroPCS are using a unified image and will customize for the proper providers tools and boot logo based in sim inserted during initial setup.
The boot.img is the same for both.
Related
That device can't install TWRP yet, so only method that OPN users have to root his phones is that:
https://forum.xda-developers.com/oneplus-nord/how-to/guide-how-to-root-oneplus-nord-t4139411
I think to simplyfy that method in two scripts, one to extract payload.bin and root your phone, and another to convert that extracted payload.bin to fastboot installable ROM.
Make sure that you have python installed in your computer before use it.
Here is the steps to use it:
1. Download any OxygenOS update from Some_Random_Username's Repo:
https://forum.xda-developers.com/oneplus-nord/how-to/oneplus-nord-repo-oxygen-os-builds-t4138085
2. Download the script:
English v1 version for Windows: https://www.androidfilehost.com/?fid=8889791610682922150
Spanish v1 version for Windows: https://www.androidfilehost.com/?fid=8889791610682922151
3. Extract the script on any folder
4. Extract "payload.bin" file from OxygenOS update, downloaded previously on step 1
5. Execute "payload.bat" and follow the steps on the script
OPTIONAL: After root your phone or extract "payload.bin" file, you can use "flash-all.bat" file from scripts file to flash whole OxygenOS update from fastboot mode!
TIPS:
- As Some_Random_Username said, you should backup your /persist once rooted (dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img) and save it somewhere on your cloud/computer, because this might save you from a broken fingerprint sensor and an RMA in the future if it turns out this device has same issue as 8-series when it comes to crossflash regional builds of OOS.
This step will be include to the script in the future
Credits:
@topjohnwu for making Magisk
@Some_Random_Username for original guide and updated repo build of Oxygen OS
@mauronofrio for original fastboot script
Reserved
You can fastboot boot twrp.img and then flash magisk, so flashing a boot image is not the only way to root.
Yup:good:
The fastboot roms are already available in the dedicated thread and with the twrp i made you can flash magisk and also stock roms, i really don't know at what this is needed
mauronofrio said:
The fastboot roms are already available in the dedicated thread and with the twrp i made you can flash magisk and also stock roms, i really don't know at what this is needed
Click to expand...
Click to collapse
goRt said:
You can fastboot boot twrp.img and then flash magisk, so flashing a boot image is not the only way to root.
Click to expand...
Click to collapse
I know that fastboot roms is already in the dedicated thread, but maybe isn't updated or any people want to extract himself (for example, now you don't have latest 10.5.5 version uploaded!)
Also with TWRP, you can't install it as normal recovery yet, so maybe people want to do and try it with fastboot method, and can use my script for help himselves.
That is another and automated method to help people only
dimusa said:
I know that fastboot roms is already in the dedicated thread, but maybe isn't updated or any people want to extract himself (for example, now you don't have latest 10.5.5 version uploaded!)
Also with TWRP, you can't install it as normal recovery yet, so maybe people want to do and try it with fastboot method, and can use my script for help himselves.
That is another and automated method to help people only
Click to expand...
Click to collapse
Twrp can also be flashed if needed
Hi guys so Many users are facing issue while they are rooted and twrp installed on there phone.
They can't able to Flash update through stock settings OR via twrp if they tries to flash it via twrp manually facing no wifi and Bluetooth.
So here is the process to flash any incremental update via twrp just we need update zip, vbmeta image and boot image of old oos version respective to your new update means if. We are upgrading to V11 we need V10 boot img
U can use following commands to extract your current stock boot img after connecting to PC
adb shell
dd if=/dev/block/sdc49 of=/sdcard/boot.img
exit
Note: Remember this process will replace your twrp and removes root to gain root access. We need to repeat twrp installation shown in the following tutorial
TUTORIAL TWRP AND ROOT NORD 2 OXYGEN OS 11 ( Links updated!)
SO finally I successfully rooted with TWRP and root access.thanks to all developers @Eastw1ng @TheMalachite Following are all download links combined in one post Also there are two threads like unlocking boot loader and twrp but there are some...
forum.xda-developers.com
You can gain root acess only by flashing magisk.zip file after step no 7 given under instructions but I didn't tested it yet.
DOWNLOADS:
1)Download update v11 from Telegram :
®D$ in OnePlus Nord 2 Community
t.me
2) DOWNLOAD V13:
®D$ in OnePlus Nord 2 Community
t.me
3) Download V14 update zip:
️ in OnePlus Nord 2 Community
t.me
4) Download A15 update zip:
e9708c8610bae8fa64d76e0f9a55dda444ce981a.zip
drive.google.com
We can also download update in system update process. Just download OTA update and when we boot in twrp just click install and then go to following folder there you will find update.zip
/data/OTA-package/update.zip
5)A17 update zip:
https://t.me/OnePlusNord2GlobalOfficial/81364
Download vbmeta:
vbmeta.img | by TheMalachite for OnePlus Nord 2 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Download boot.img:
1) upgrade from v10 to v11(indian)
boot.img
drive.google.com
2) upgrade from v11 to v13(indian)
bootnew.img
drive.google.com
3)Upgrade from v13 to v14:
Rose in OnePlus Nord 2 Community
t.me
4)Upgrade from A14 to A15:
Rose in OnePlus Nord 2 Community
t.me
5)15 Boot img india (update from A15 to AA16)
https://t.me/OnePlusNord2GlobalOfficial/57795
5)A16 boot.img to upgrade to A17:
Rose in OnePlus Nord 2 Community
A16 stock boot image
t.me
6)17 BOOT IMG Upgrade to A18 (boot.img vbmeta zip extract file)
Rose in OnePlus Nord 2 Community
t.me
Boot img for nord 2 EU REGION :
File folder on MEGA
mega.nz
This another thread for all boot img of EU region
Stock Boot & Patched images Oneplus Nord 2 Oxygen 11.3 DN2103_11_A.07/09/10 EEA
Flash at your own risk. I am not responsible for any damage or data loss to the device during this process! https://mega.nz/folder/fZx2nBaR#Q33lJstFRMQg6_0j7Z0TJw Special Thanks: @HofaTheRipper @phhusson
forum.xda-developers.com
Instructions :
1) Download all file from the link given under this thread place them at one place on your phone so it can be easily accessible when we boot in TWRP.
2)Now to boot in TWRP use following root acess app called as advance reboot. Open it and click reboot to recovery
Advanced Reboot Tools [ROOT] - Apps on Google Play
Provides lots of options for restarting your device; excellent for tweakers.
play.google.com
Or you can use adb command after connecting phone to pc in USB debugging mode.
adb reboot recovery
3) when phone boot in TWRP click install tab now go to folder where we placed All files.
4) click install image tab at bottom now you we see image files boot. img and vbmeta.img that we downloaded
5)now select boot.img and then select boot partation and slide bottom bar after successful installation
6)click reboot and select recovery phone will boots back to twrp( This step is optional)
7)Now again click Install and find our old folder now select update.zip file and slide bottom bar it will take 2min for complete falshing of zip.
8)now agian click install now click install image and select vbmeta.img
9)Now click reboot system phone will reboots and take 10min.
Now you are successfully updated and have new OOS 11.3 A11 version on your phone without any issues.
Follow the video:
New update v13 update process :
New update A14 update process:
New update A15:
New update A16:
New A18 update:
pankspoo said:
Hi guys so Many users are facing issue while they are rooted and twrp installed on there phone.
They can't able to Flash update via twrp if they tries to flash it via twrp manually facing no wifi and Bluetooth.
So here is the process to flash any incremental update via twrp just we need update zip, vbmeta image and boot image of old oos version respective to your new update means if. We are upgrading to V11 we need V10 boot img.
Follow the video:
Click to expand...
Click to collapse
good Instructions! Reboot after flashing boot.img isnt necessary. OTA Update zip can be downloaded within OTA App in Settings (do not press reboot). After downloading you can reboot to TWRP and the file location is: /data/OTA-package/update.zip.
HofaTheRipper said:
good Instructions! Reboot after flashing boot.img isnt necessary. OTA Update zip can be downloaded within OTA App in Settings (do not press reboot). After downloading you can reboot to TWRP and the file location is: /data/OTA-package/update.zip.
Click to expand...
Click to collapse
Yes but I don't want to go to automatic reboot and flashing process of OTA Update installation after download which may cause some issues for new users.
The old boot.img I image is the stock one not rooted right? How can you extract it from your firmware if you're not rooted? From the Nandroid backup maybe?
Edit, found out: https://forum.xda-developers.com/t/how-to-extract-your-boot-img-from-any-rom-adb.3760210/ Just had to google it
Don't wo
Raygen said:
The old boot.img I image is the stock one not rooted right? How can you extract it from your firmware if you're not rooted? From the Nandroid backup maybe?
Click to expand...
Click to collapse
Donts worry from here every new updates we will provide all stock boot. img
Thread updated for latest update v13 for India region
HI. This is my 1st OnePlus and OxygenOS. I am now on DN2103_11_A.11 and OTA is available. It is DN2103_11_A.12
Basically I can flash it from TWRP and I do not need to save and flash boot.img afterwards bec OS will be the same version. Is that so? Or am I wrong? And I have to follow threads instructions ?
Thank you
jis251 said:
HI. This is my 1st OnePlus and OxygenOS. I am now on DN2103_11_A.11 and OTA is available. It is DN2103_11_A.12
Basically I can flash it from TWRP and I do not need to save and flash boot.img afterwards bec OS will be the same version. Is that so? Or am I wrong? And I have to follow threads instructions ?
Thank you
Click to expand...
Click to collapse
NO u need A11 boot img of only DN 2103 firmware not indian I don't have that now first flash that then flash update zip of v12 then flash Vbmeta now that's done
pankspoo said:
NO u need A11 boot img of only DN 2103 firmware not indian I don't have that now first flash that then flash update zip of v12 then flash Vbmeta now that's done
Click to expand...
Click to collapse
HI. And thx for quick reply. I mange now, thank you.
DN2103 A.11 stock boot img :
HofaTheRipper said:
DN2103 A.11 stock boot img :
Click to expand...
Click to collapse
You got it do it now
HofaTheRipper said:
DN2103 A.11 stock boot img :
Click to expand...
Click to collapse
HI and thx. I have made TWRP backup, boot and vbmeta
So I can first restore boot then flash OTA and then restore vbmeta, yes? (Version 11)
I do not have to flash boot and vbmeta, restore does the same??
jis251 said:
HI and thx. I have made TWRP backup, boot and vbmeta
So I can first restore boot then flash OTA and then restore vbmeta, yes? (Version 11)
I do not have to flash boot and vbmeta, restore does the same??
Click to expand...
Click to collapse
Don't use backup boot image restore process.
Just download above boot image given
https://forum.xda-developers.com/attachments/boot_stock_a11-img.5461307/
and vbmeta image given in. My thread
vbmeta.img | by TheMalachite for OnePlus Nord 2 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
And u r update zip of device of your region not mine
First flash boot img then. Install update zip then. Flash Vbmeta done
pankspoo said:
Don't use backup boot image restore process.
Just download above boot image given
https://forum.xda-developers.com/attachments/boot_stock_a11-img.5461307/
and vbmeta image given in. My thread
vbmeta.img | by TheMalachite for OnePlus Nord 2 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
And u r update zip of device of your region not mine
First flash boot img then. Install update zip then. Flash Vbmeta done
Click to expand...
Click to collapse
Thx. OK I do that.
Magisk is installed (patched) to boot image so after OTA and Vbmeta I flash Magisk to keep root.
jis251 said:
Thx. OK I do that.
Magisk is installed (patched) to boot image so after OTA and Vbmeta I flash Magisk to keep root.
Click to expand...
Click to collapse
Yes
pankspoo said:
Download boot.img:
1) upgrade from v10 to v11(indian)
boot.img
drive.google.com
2) upgrade from v11 to v13(indian)
bootnew.img
drive.google.com
Click to expand...
Click to collapse
Do the boot.img files in the original post only work on the Indian variant? Where can I get the A11 boot.img for the European variant if I want to update to A12?
NetSoerfer said:
Do the boot.img files in the original post only work on the Indian variant? Where can I get the A11 boot.img for the European variant if I want to update to A12?
Click to expand...
Click to collapse
Ok I will upload in thread
NetSoerfer said:
Do the boot.img files in the original post only work on the Indian variant? Where can I get the A11 boot.img for the European variant if I want to update to A12?
Click to expand...
Click to collapse
File folder on MEGA
mega.nz
Use boot images from stock folder
pankspoo said:
U can use following commands to extract your current stock boot img after connecting to PC
adb shell
dd if=/dev/block/sdc49 of=/sdcard/boot.img
exit
Click to expand...
Click to collapse
Still trying to wrap my head around this (although updating worked fine from A11 to A12 on my EEA variant, thanks @pankspoo!).
Can I actually extract a stock boot.img from a Magisk-rooted phone? Is it stock (in which case why is root removed by the update.zip) or is it modified (in which case, why can I extract it as stock)?
NetSoerfer said:
Still trying to wrap my head around this (although updating worked fine from A11 to A12 on my EEA variant, thanks @pankspoo!).
Can I actually extract a stock boot.img from a Magisk-rooted phone? Is it stock (in which case why is root removed by the update.zip) or is it modified (in which case, why can I extract it as stock)?
Click to expand...
Click to collapse
You can use those adb commands while booted in TWRP, without being rooted. So you'll extract the stock boot image
..the vbmeta.img and boot_a from the unlocked variant? I tried flashing TWRP kind of half cocked, and yea... Anyhow, if someone has either\or or both of these files, hook a brother up!
Disregard. I was able to unbrick with the dre8t_10_O.05_210713.ops firmware floating around. It wouldnt let me flash via MSMDownloadTool, however I was able to decrypt/extract the ops file with the oppo_decrypt python script, then reflash the vbmeta and vbmeta_system partitions plus boot_a and userdata with the extracted files.
PHEW had me scared for a minute
the.real.p3y0t3 said:
..the vbmeta.img and boot_a from the unlocked variant? I tried flashing TWRP kind of half cocked, and yea... Anyhow, if someone has either\or or both of these files, hook a brother up!
Click to expand...
Click to collapse
For future reference:
For unlocked variant:
Download the latest OTA update from the OnePlus website and you can use any assortment of payload dumpers to obtain all of the raw image files.
My payload dumper of preference is Fastboot Enhanced/Payload Dumper. It can even install the full OTA via fastboot/fastbootd
For T-Mobile and Metro variants I would recommend the T-Mobile MSM tool and update from there.
The download link to "Incremental OTAs" can be scraped from the system logcat at time of download.
I haven't looked much into incremental OTA and how it is setup yet.
Thanks for the heads up. I actually already had the above mentioned OPS file when I bricked my device, I just hadn't been able to extract, then decrypt it. Had to download a obscure bzip2 binary for windows to extract the tar, etc etc.
A seller from ebay sent a t-mobile (2118) that was carrier unlocked, wasn't able to unlock the bootloader. Is there anything I can do?
I have posted all the boot.img files for N200 A12 to AFH for DE2117 US OEM firmware and now latest for DE2118 (Tmobile/metro)
I am also posting the OFFICIAL Lineage Magisk patched boot.img but may not always be up to date, so do check the date as you must have same version!
N200 Official LineageOS_2023_06-14-Magisk 26.1 pre-patched
boot.ing for OFFICIAL Lineage
I have posted both the original file as well as pre-patched with Magisk v25.2 for each.
The T-Mobile/Metro image versioning is ONE NUMBER BEHIND the OEM version. As of today the current version with December update is:
DE2117-C_23 (OEM)
DE2118-C_21 (T-Mobile/Metro)
PREREQUISITES: (see other guides)
You must have your bootloader unlocked.
USB debugging enabled and your PC authorized. (ADB commands working)
Latest Android Platform Tools installed on PC
1. Simply allow phone to take OTA updates until your on latest version.
2. Open Settings and click: "About Device" -> "Version" and Build Number must match EXACTLY on your system information screen with the boot.img file you are going to install:
{
"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"
}
In this example it is US/OEM (DE2117) at patch level C_17.
You MUST patch the boot.img with EXACT SAME model version AND Patch level!
I wrote a simplified dummies guide to flash US OEM rom with Fastboot Enhance tool and convert T-Mobile/PCS phone to US/OEM wiith only Fastboot Enhance GUI tool along with msmtool backup.
3. Go to my "Boot.img Files" folder on AFH and download the Magisk pre-patched boot.image file for YOUR MATCHING version and place it to the same folder that you installed Android Platform Tools.
DE2117 US OEM - Pre-Patched with Magisk v25.2:
boot.img C_15
boot.img C_16
boot.img C_17
boot.img C_18
boot.img C_19
boot.img C_20
boot.img C_21
DE2117 US OEM - Pre-Patched with Magisk v26.1:
boot.img C_22
boot.img C_23
DE2118 T-Mobile/MetroPCS - Pre-Patched with Magisk v25.2:
boot.img C_5
boot.img C_17
boot.img C_18
boot.img C_19
boot.img C_20
DE2118 T-Mobile/MetroPCS - Pre-Patched with Magisk v26.1:
boot.img C_21
boot.img C_22
With File Explorer in the folder with platform tools and the boot.img file you just downloaded, type "cmd" in the address bar and a dos window will open up in that folder.
4. Then switch the phone to fastboot mode:
C:\>adb reboot bootloader
You should see the phone fastboot screen and the last line MUST say the bootloader is: UNLOCKED.
5. Flash the Magisk Patched boot.img file.
In this example the command would be:
C:\>fastboot flash boot DE2117.boot.C_18.Magisk_Patched.v25.2.img
6. Reboot phone:
C:\>fastboot reboot
7. After phone boot up there will be a green android icon with Magisk v1.0 on your home screen/drawer. Run it and it will upgrade itself to the latest Magisk version.
Your now ROOTED.
8. To KEEP root and avoid an OTA update before I have posted the latest boot.img file you should:
Open settings -> "System Settings" -> "Developer Options" and then turn off "Automatic System Updates"
I should post new boot.img updates within 24 hours to the same folder.
Technical Information:
Before A12 you could use the command: "fastboot boot boot.img" and boot the previous patched Magisk boot image and then let Magisk backup your current image and then patch it as the old one was usually still working enough to get the new boot.img this way and let Magisk store the untouched boot.img file so it could remove the patch in app.
This ability has been removed starting with the first A12 C_15 image.
Also, the OP OTA update is checking for more than just the original boot.img and will fail an OTA update with Magisk installed with the boot.img restored and Magisk loaded in ram.
Hiding the Magisk app, installing safetynet-fix-v2.2. and Shamiko-v0.5.2-120 Magisk Module will allow you to pass Safetynet and get your banking/streaming apps working, but only removing Magisk completely will allow OTA updates now.
There are two ways to get partial OTA update boot.img file if you want to do it on your own at this point.
1. Grab the partial ota update .zip file by looking at syslog when OTA app on phone starts downloading it. Take the last dumped full OTA and patch it with the only payload dumper that will merge partial OTA's with existing full OTA:
https://github.com/vm03/payload_dumper
2. If you don't mind wiping your phone, you can take the newest partial OTA update and then change to inactive slot and install the last full OTA image and then pull the boot.img from the inactive slot that has the newest OTA installed. And then reinstall full ota update again and take latest partial update.
UPDATE: If you flash the last full OTA C_16 and want OTA updates to work, you must flash it TWICE now. Once in fastboot mode and only the MODEM.IMG file will flash and then switch to fastbootd mode and flash it again and every image other than the modem will flash. If the modem does not match the rom, as well as the BOOT.IMG (non modified) then OTA WILL FAIL!!
Un-modified BOOT.IMG files for DE2117 US OEM N200:
boot.img C_15
boot.img C_16
boot.img C_17
boot.img C_18
boot.img C_20
boot.img C_21
boot.img C_22
boot.img C_23
Un-modified BOOT.IMG files for DE2118 Tmobile/MetroPCS N200:
boot.img C_5
boot.img C_7
boot.img C_8
boot.img C_9
boot.img C_11
boot.img C_12
boot.img C_15
boot.img C_16
boot.img C_17
boot.img C_18
boot.img C_19
boot.img C_20
boot.img C_21
boot.img C_22
The C_5 through C_16 DE2118 images are pointing to towardsdawn's AFH section.
I added them here so one post has all the boot.img files in one place to make it easier to find.
waiting for your tmo to us oem conversion guide! thanks
scanman0 said:
I have posted all the boot.img files for A12 to AFH for DE2117 US OEM firmware.
I have posted both the original file as well as pre-patched with Magisk v25.2 for each.
As of now there are three versions. (C_15, C_16, and C_17)
PREREQUISITES: (see other guides)
You must have your bootloader unlocked.
USB debugging enabled and your PC authorized. (ADB commands working)
Latest Android Platform Tools installed on PC
1. Simply allow phone to take OTA updates until your on latest version. (C_17 as of today)
2. Open Settings and click: "About Device" -> "Version" and Build Number must match EXACTLY on your system information screen with the boot.img file you are going to install:
View attachment 5696281
In this example it is C_17.
If it says DE18CB then STOP!
This is the T-Mobile/MetroPCS infected firmware and is NOT the same as the US OEM firmware.
I wrote a simplified dummies guide to flash US OEM rom with Fastboot Enhance tool and convert T-Mobile/PCS phone to US/OEM wiith only Fastboot Enhance GUI tool along with msmtool backup.
3. Go to my "Boot.img Files" folder on AFH and download the Magisk pre-patched boot.image file for YOUR MATCHING version and place it to the same folder that you installed Android Platform Tools.
https://androidfilehost.com/?a=show&w=files&flid=335815
With File Explorer in the folder with platform tools and the boot.img file you just downloaded, type "cmd" in the address bar and a dos window will open up in that folder.
4. Then switch the phone to fastboot mode:
C:\>adb reboot bootloader
You should see the phone fastboot screen and the last line MUST say the bootloader is: UNLOCKED.
5. Flash the Magisk Patched boot.img file.
In this example the command would be:
C:\>fastboot flash boot DE2117.boot.C_17.Magisk_Patched_v25.2.img
6. Reboot phone:
C:\>fastboot reboot
7. After phone boot up there will be a green android icon with Magisk v1.0 on your home screen/drawer. Run it and it will upgrade itself to the latest Magisk version.
Your now ROOTED.
8. To KEEP root and avoid an OTA update before I have posted the latest boot.img file you should:
Open settings -> "System Settings" -> "Developer Options" and then turn off "Automatic System Updates"
I should post new boot.img updates within 24 hours to the same folder.
Technical Information:
Before A12 you could use the command: "fastboot boot boot.img" and boot the previous patched Magisk boot image and then let Magisk backup your current image and then patch it as the old one was usually still working enough to get the new boot.img this way and let Magisk store the untouched boot.img file so it could remove the patch in app.
This ability has been removed starting with the first A12 C_15 image.
Also, the OP OTA update is checking for more than just the original boot.img and will fail an OTA update with Magisk installed with the boot.img restored and Magisk loaded in ram.
Hiding the Magisk app, installing safetynet-fix-v2.2. and Shamiko-v0.5.2-120 Magisk Module will allow you to pass Safetynet and get your banking/streaming apps working, but only removing Magisk completely will allow OTA updates now.
There are two ways to get partial OTA update boot.img file if you want to do it on your own at this point.
1. Grab the partial ota update .zip file by looking at syslog when OTA app on phone starts downloading it. Take the last dumped full OTA and patch it with the only payload dumper that will merge partial OTA's with existing full OTA:
https://github.com/vm03/payload_dumper
2. If you don't mind wiping your phone, you can take the newest partial OTA update and then change to inactive slot and install the last full OTA image and then pull the boot.img from the inactive slot that has the newest OTA installed. And then reinstall full ota update again and take latest partial update.
Click to expand...
Click to collapse
Is there a Bootimg. file for DE_2118_11_C.16 I could not find one?
jayram1408 said:
Is there a Bootimg. file for DE_2118_11_C.16 I could not find one?
Click to expand...
Click to collapse
!!! This is ONLY for Tmobile/MetroPCS A12 running C_16 firmware !!!
boot_11_C.16_DE2118_tmobile_stock.img | by towardsdawn for Nord N200 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
What's changed in the update or was it just security updates?
weirdfate said:
What's changed in the update or was it just security updates?
Click to expand...
Click to collapse
It is NOT new and it is for the MetroPCS/T-Mobile infected rom.
I posted it OFF TOPIC and this is why I used all the !!! marks.
I updated the parent thread with the September security patch C_18 boot.img files as promised!
Bump.
Updated guide and added latest DE2118 boot.img files for Tmobile/MetroPCS that do not want to convert to US/OEM firmware
Are you able to get boot image for 11.0.1.12.DE18CB device DE2118? Ty
Angelk3 said:
Are you able to get boot image for 11.0.1.12.DE18CB device DE2118? Ty
Click to expand...
Click to collapse
If someone posts it anyplace I will add it here. The best solution is to convert phone to US OEM. Then you can use the pre-patched boot.img files I post here.
Angelk3 said:
Are you able to get boot image for 11.0.1.12.DE18CB device DE2118? Ty
Click to expand...
Click to collapse
It's hosted here
@scanman0 thanks for making this post! very helpful to have it all in one place
I don't know if you uploaded T-mobile C.18 and forgot to post the link or not, but I uploaded it here. AndroidFileHost still isn't working for me for whatever reason
I have successfully converted my T-Mobile phone to a DE2117 and have it at version C_19 with the boot.img patched with Magisk. Magisk is updated to the latest and I have been looking into the things I should do with Magisk. However what I read online isn't matching with what I'm seeing on my phone. Is Magisk the Magisk manager? I'm also not seeing an option to check the Safety Net? I've also read I can look for Magisk modules in Magisk but I don't see a way of searching for modules to install? Am I missing something? Any insight would truly be appreciated!
Galaxy-Geek#1 said:
I have successfully converted my T-Mobile phone to a DE2117 and have it at version C_19 with the boot.img patched with Magisk. Magisk is updated to the latest and I have been looking into the things I should do with Magisk. However what I read online isn't matching with what I'm seeing on my phone. Is Magisk the Magisk manager? I'm also not seeing an option to check the Safety Net? I've also read I can look for Magisk modules in Magisk but I don't see a way of searching for modules to install? Am I missing something? Any insight would truly be appreciated!
Click to expand...
Click to collapse
The ability to check for Safety Net in Magisk was taken out, as was the ability to search modules through Magisk. Both must be done outside the app now though installing modules can still be performed in through Magisk.
Link575 said:
The ability to check for Safety Net in Magisk was taken out, as was the ability to search modules through Magisk. Both must be done outside the app now though installing modules can still be performed in through Magisk.
Click to expand...
Click to collapse
Thank you! That makes sense then. Is there a post or guide how to check safety net (and what it does tbh last root I used was SuperSu for Android 7) and where I can find some good Magisk modules?
Galaxy-Geek#1 said:
Thank you! That makes sense then. Is there a post or guide how to check safety net (and what it does tbh last root I used was SuperSu for Android 7) and where I can find some good Magisk modules?
Click to expand...
Click to collapse
There is a big list of magisk modules here
I use YASNAC but if you just search for safety net checker in the Google play store there's plenty of them. It fails on my rooted N200. You only need it to pass if you want to use apps that check for it (generally financial apps like Google Pay or games that have anti cheat checks)
Galaxy-Geek#1 said:
Thank you! That makes sense then. Is there a post or guide how to check safety net (and what it does tbh last root I used was SuperSu for Android 7) and where I can find some good Magisk modules?
Click to expand...
Click to collapse
Np and towardsdawn answered that question pretty completely right above. In case you do want or need it to pass safety net you can download magisk module called universal safety net fix here.
Should that not work (it should unless you're on lineage) you can try magiskhide props config found here with instructions. I just use the fingerprint for the de2117 and everything works fine.
towardsdawn said:
There is a big list of magisk modules here
I use YASNAC but if you just search for safety net checker in the Google play store there's plenty of them. It fails on my rooted N200. You only need it to pass if you want to use apps that check for it (generally financial apps like Google Pay or games that have anti cheat checks)
Click to expand...
Click to collapse
Link575 said:
Np and towardsdawn answered that question pretty completely right above. In case you do want or need it to pass safety net you can download magisk module called universal safety net fix here.
Should that not work (it should unless you're on lineage) you can try magiskhide props config found here with instructions. I just use the fingerprint for the de2117 and everything works fine.
Click to expand...
Click to collapse
Thank you both! I'll look into those modules and the safety net stuff (but may not be needed much in my case since it's not my main device). One last question if you don't mind, do I need to install TWRP? From the looks of it, there isn't a good working version for this phone but just wanna confirm before I assume I'm done with any factory reset or things like that.
Galaxy-Geek#1 said:
Thank you both! I'll look into those modules and the safety net stuff (but may not be needed much in my case since it's not my main device). One last question if you don't mind, do I need to install TWRP? From the looks of it, there isn't a good working version for this phone but just wanna confirm before I assume I'm done with any factory reset or things like that.
Click to expand...
Click to collapse
From what I've read in the forums I don't recommend it, seems like it's easy to brick your phone or lose important functionality. You can factory reset by going to fastboot mode or with msm download tool. You can unroot by flashing stock boot image
Does anyone have Pre-Patched with Magisk v25.2 boot.img for the last December update DE2118_11_c.19?
Can I safely flash new firmware on my nokia g11 Plus using "SP Flash Tool"?
They say that the program is for flashing devices based on the mediatek processor, but from what I know the nokia g11 plus has a Unisoc T606 processor?
Is there any other software to upload firmware to this phone model?
I want to flash Stock ROM
How to use SPD Upgrade Tool to install or flash .pac Stock ROM (firmware)
Step-by-Step guidelines to Install or Flash .pac Firmware (ROM) on devices powered by Spreadtrum/Unisoc Chipset using the SPD Upgrade Tool.
androidmtk.com
aIecxs said:
How to use SPD Upgrade Tool to install or flash .pac Stock ROM (firmware)
Step-by-Step guidelines to Install or Flash .pac Firmware (ROM) on devices powered by Spreadtrum/Unisoc Chipset using the SPD Upgrade Tool.
androidmtk.com
Click to expand...
Click to collapse
Thanx for answer, so i already have the program.
I have searched for several hours for software but all of them are just in .Bin format :c and the program requires a firmware in .Pac format
Strange because I downloaded the firmware from the given link.
Payload.Bin could be installed via recovery but on nokia g11 plus it is so poor it only has three useless options like reboot or turn of device :v
the file you have is not full firmware (because of the small file size) it's more likely just incremental OTA update file.
you can however have a look inside with payload dumper.
[TOOL] A QUICK Android OTA payload dumper
Made with Go. By utilizing goroutines, this can extract img files from (full) OTA payload.bin really quickly. See how fast this is: https://i.imgur.com/adpijqf Source Code: https://github.com/ssut/payload-dumper-go Prebuilt binaries...
forum.xda-developers.com
aIecxs said:
the file you have is not full firmware (because of the small file size) it's more likely just incremental OTA update file.
you can however have a look inside with payload dumper.
[TOOL] A QUICK Android OTA payload dumper
Made with Go. By utilizing goroutines, this can extract img files from (full) OTA payload.bin really quickly. See how fast this is: https://i.imgur.com/adpijqf Source Code: https://github.com/ssut/payload-dumper-go Prebuilt binaries...
forum.xda-developers.com
Click to expand...
Click to collapse
Yeah right, it is OTA, If I don't find StockRom, I won't fix this brick, soo annoying cuz there is no .Spd firmware to flash in internet.
I even searched on Chinese forums, such a charm of these phones?
can only find 1.8gb OTA update.zip flashable for recovery mode.
maybe ask nokia support. or contact this guy (see unbrick EDL Package)
https://romprovider.com/nokia-g11-plus-firmware-stock-rom