If you are not able to boot a patched boot image or a twrp image on Android 10, here is a workadound.
Machi007 said:
Boot TWRP and images is possible also on Android 10, but it needs some workaround...
1) Turn phone into Download Mode
2) Use command fastboot flash recovery twrp.img where twrp.img is your TWRP image you want to boot up
It shows this error (it is OKAY):
Code:
FAILED (remote: '(recovery_a) No such partition') //This is because an A/B Device does not have a recovery partition. It's located in the boot partition itself.
3) Now you can boot your TWRP recovery image, for example: fastboot boot twrp.img
Click to expand...
Click to collapse
Hay Guys!
One of the most important things on Android is to make backups. Every time you want to root or flash something, make backups!
I saw many people struggling with OTA because they didn't make backups to restore there images.
=========================================================================
If you DONT have any backup, but you want to restore stock, I'll upload all my stock backups as well as all patched boot images in this mega:
https://mega.nz/#F!52B0HCID!A1k8PiGn9OQbiEa_IJ3_EQ
This is just in case something went wrong with you backup. You should still make your own backups!!!
=========================================================================
In this post I will show you how to create a backup and how to restore it.
There are 2 ways to backup your Phone images.
TWRP:
Reboot ur phone into bootloader
You can do this via adb
Code:
adb reboot bootloader
You can do this by holding volume down + power button while your phone is connected to USB.
Boot into TWRP. you can use the TWRP image from my mega. DO NOT FLASH IT!!!
Code:
fastboot boot twrp.img
Hit the Backup button and backup boot image, system image and vendor image.
If you want to restore this images, you can restore them with TWRP. Just hit the restore button.
This may not work for all Devices. But you can flash the images via fastboot too.
The fastboot files looks like boot.emmc.win. Dont worry, this is img file. So you can rename it to boot.img or something.
ADB:
1Reboot ur phone into bootloader
You can do this via adb
Code:
adb reboot bootloader
You can do this by holding volume down + power button while your phone is connected to USB.
Find out your current slot
Code:
fastboot getvar current-slot
Boot into a patched boot image.
Code:
fastboot boot patched.img
Your phone shoud boot up. If it does,
then open ADB.
In ADB type there commands to dump the images.
Get root access by typing the "su"
Dump your boot, system and vendor from your current slot you found out on step 2
(The commands for dumping an image are below)
If you want to restore this images, you can restore them via fastboot.
Code:
fastboot flash [boot_{current-slot}/system_{current-slot}/vendor_{current-slot}] <image file>
Replace the {current-slot} with your current slot.
Example:
Current slot is a and you want to restore the boot image.
Code:
fastboot flash boot_a boot_a.img
If you still have Questions or need help, feel free to pm me.
Also you can leave a comment under this post.
Commands for dumping images:
#Backup A boot:
Code:
dd if=/dev/block/mmcblk0p52 of=/sdcard/boot_a.img
#Backup B boot:
Code:
dd if=/dev/block/mmcblk0p53 of=/sdcard/boot_b.img
#Backup A vendor:
Code:
dd if=/dev/block/mmcblk0p83 of=/sdcard/vendor_a.img
#Backup B vendor:
Code:
dd if=/dev/block/mmcblk0p84 of=/sdcard/vendor_b.img
#Backup A system:
Code:
dd if=/dev/block/mmcblk0p81 of=/sdcard/system_a.img
#Backup B system:
Code:
dd if=/dev/block/mmcblk0p82 of=/sdcard/system_b.img
Great tutorial and much appreciated. On the first sentence... There is a typo on the word "thinks".. it should be "things".
Danny1976 said:
Great tutorial and much appreciated. On the first sentence... There is a typo on the word "thinks".. it should be "things".
Click to expand...
Click to collapse
Thanks. fixed it :good:
Hail brother! Tnx!
might have shot the capability of OTA on experimenting with TWRP and it's possibilites of taking backups.
thought, I was careful, but wasn't enough.
so THANKS a lot for providing all the information and (of course) : the sp1 images.
January stock and patched images is now uploaded.
Hi! I have a Problem with the wifi not working after flashing back stock boot.img on slot a & b....if anyone could help I'll be grateful.
emicloud91 said:
Hi! I have a Problem with the wifi not working after flashing back stock boot.img on slot a & b....if anyone could help I'll be grateful.
Click to expand...
Click to collapse
Did you flash your own backups?
Do you have global 6.1?
Also, why did you flash A AND B?
¥sBielefeld said:
Hay Guys!
One of the most important things on Android is to make backups. Every time you want to root or flash something, make backups!
I saw many people struggling with OTA because they didn't make backups to restore there images.
=========================================================================
If you DONT have any backup, but you want to restore stock, I'll upload all my stock backups as well as all patched boot images in this mega:
https://mega.nz/#F!52B0HCID!A1k8PiGn9OQbiEa_IJ3_EQ
This is just in case something went wrong with you backup. You should still make your own backups!!!
=========================================================================
In this post I will show you how to create a backup and how to restore it.
There are 2 ways to backup your Phone images.
TWRP:
Reboot ur phone into bootloader
You can do this via adb
Code:
adb reboot bootloader
You can do this by holding volume down + power button while your phone is connected to USB.
Boot into TWRP. you can use the TWRP image from my mega. DO NOT FLASH IT!!!
Code:
fastboot boot twrp.img
Hit the Backup button and backup boot image, system image and vendor image.
If you want to restore this images, you can restore them with TWRP. Just hit the restore button.
This may not work for all Devices. But you can flash the images via fastboot too.
The fastboot files looks like boot.emmc.win. Dont worry, this is img file. So you can rename it to boot.img or something.
ADB:
1Reboot ur phone into bootloader
You can do this via adb
Code:
adb reboot bootloader
You can do this by holding volume down + power button while your phone is connected to USB.
Find out your current slot
Code:
fastboot getvar current-slot
Boot into a patched boot image.
Code:
fastboot boot patched.img
Your phone shoud boot up. If it does,
then open ADB.
In ADB type there commands to dump the images.
Get root access by typing the "su"
Dump your boot, system and vendor from your current slot you found out on step 2
(The commands for dumping an image are below)
If you want to restore this images, you can restore them via fastboot.
Code:
fastboot flash [boot_{current-slot}/system_{current-slot}/vendor_{current-slot}] <image file>
Replace the {current-slot} with your current slot.
Example:
Current slot is a and you want to restore the boot image.
Code:
fastboot flash boot_a boot_a.img
If you still have Questions or need help, feel free to pm me.
Also you can leave a comment under this post.
Commands for dumping images:
#Backup A boot:
Code:
dd if=/dev/block/mmcblk0p52 of=/sdcard/boot_a.img
#Backup B boot:
Code:
dd if=/dev/block/mmcblk0p53 of=/sdcard/boot_b.img
#Backup A vendor:
Code:
dd if=/dev/block/mmcblk0p83 of=/sdcard/vendor_a.img
#Backup B vendor:
Code:
dd if=/dev/block/mmcblk0p84 of=/sdcard/vendor_b.img
#Backup A system:
Code:
dd if=/dev/block/mmcblk0p81 of=/sdcard/system_a.img
#Backup B system:
Code:
dd if=/dev/block/mmcblk0p82 of=/sdcard/system_b.img
Click to expand...
Click to collapse
Can these images be used for downgrade to oreo? I am on pie (ta1068), unrooted and loocked bootloader.
Windoors said:
Can these images be used for downgrade to oreo? I am on pie (ta1068), unrooted and loocked bootloader.
Click to expand...
Click to collapse
No i don't think so. I never tested it.
Anyway.. You are locked, so you need to downgrade to unlock bootloader. You can use NTool or visit this
¥sBielefeld said:
No i don't think so. I never tested it.
Anyway.. You are locked, so you need to downgrade to unlock bootloader. You can use NTool or visit this
Click to expand...
Click to collapse
How to do it with NTool?
JurreTas said:
How to do it with NTool?
Click to expand...
Click to collapse
You need to buy Ntool credits. Just google it
¥sBielefeld said:
No i don't think so. I never tested it.
Anyway.. You are locked, so you need to downgrade to unlock bootloader. You can use NTool or visit this
Click to expand...
Click to collapse
I heard in nokia 6.1 u don't need to downgrade to unlock bootloader (just change slot a to b).
Anyways, if I have already unlocked my bootloader can i downgrade to oreo without ntool? Thanks
Windoors said:
I heard in nokia 6.1 u don't need to downgrade to unlock bootloader (just change slot a to b).
Click to expand...
Click to collapse
Nokia changed the Bootloader unlock algorithm with the August patch. So you need to be pre August patch.
A B slots work work like this:
Start: A(June)B(June) Currentslot A -> OTA UPDATE -> A(June)B(July) Currentslot B -> OTA -> A(August)B(July) current slot A and so forth.
So. If you are on Slot A and you have Januar installed, you B slot is on December. This means, switching the Slot does not help you with the bootloader unlock.
You have to downgrade.
Windoors said:
Anyways, if I have already unlocked my bootloader can i downgrade to oreo without ntool? Thanks
Click to expand...
Click to collapse
Yes you can use OST LA for downgrade if you are unlocked. Make sure you are critical unlocked too.
Thanks for clarifying. I unfortunately updated to January patch.
March update just released (V3.51F) with 530 MegaByte...
This is not just a security update but a complete software update.
Waiting for your files @MEGA.
Do we have to flash more than boot, system and vendor?
Last time (with pie october patch) radio and some other files were updated!
Updated to march security patch.
klauer said:
March update just released (V3.51F) with 530 MegaByte...
This is not just a security update but a complete software update.
Waiting for your files @MEGA.
Do we have to flash more than boot, system and vendor?
Last time (with pie october patch) radio and some other files were updated!
Click to expand...
Click to collapse
Why do you want to flash more?`If you are rooted, flash stock boot image. If ur modified ur system, flash stock system.
If you are complete stock, install OTA
Btw. Stock images for march are online
Are your images from Global version ? I had issues updating to March OTA (said that some partitions were modified) so I flashed your boot.img and system.img, but I still cannot update.
Solannae said:
Are your images from Global version ? I had issues updating to March OTA (said that some partitions were modified) so I flashed your boot.img and system.img, but I still cannot update.
Click to expand...
Click to collapse
Yes, they are global. I hade this issue a few weeks ago too. I had to reflash my phone for some reason...
Related
How to Remove Unlocked Bootloader Warning on Moto X4
Shoutout/Credits to xda member @AvenidaDelGato for the modified logo bin file.
Text Guide.
Make sure adb and fastboot are setup and working.
Donwload and Unzip the modified logo file. Place logo3.bin in platform-tools folders, or whereever you have fastboot and adb.
Navigate to adb/fastboot folder
Windows
Code:
adb devices
Code:
adb reboot bootloader
Code:
fastboot devices
Code:
fastboot flash logo_a logo3.bin
Code:
fastboot flash logo_b logo3.bin
Code:
fastboot reboot
Mac/Linux
Code:
./adb devices
Code:
./adb reboot bootloader
Code:
./fastboot devices
Code:
./fastboot flash logo_a logo3.bin
Code:
./fastboot flash logo_b logo3.bin
Code:
./fastboot reboot
Downloads
Modified Logo.bin zip file - https://forum.xda-developers.com/showpost.php?p=77013516&postcount=4
Mirror of Modified logo.bin zip file - https://mega.nz/#!eYFiVaxT!mpt4RhJDToEcJG4TSpw-CBePLIhd_hm8OjRGTu3egoU
ADB and Fastboot - https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Motorola Drivers - https://support.motorola.com/us/en/drivers
Thanks, that worked to remove the bootloader unlocked warning screen!
One other thing though is when the phone is first turned on while the Moto M logo is still on the screen (just before the Moto startup animation), a line of yellow console text appears over the Moto M logo that says "Verity mode is set to logging." Is there a way to turn that off? Aside from unlocking the bootloader, flashing the logo3.bin file and installing Magisk Manager from TWRP, my phone/ROM is a completely stock retail XT1900-1 (I didn't even flash TWRP to the recovery partition, I just booted it with fastboot to backup my device and install Magisk).
If anyone can help safely remove that line about verity logging without messing anything up that'd be awesome.
kofruge said:
If anyone can help safely remove that line about verity logging without messing anything up that'd be awesome.
Click to expand...
Click to collapse
I think verity is set to logging is not part of the logo. It's a text message which is coming up for a reason i do not know.
Be careful with this method, when you receive updates via OTA, you will not be able to update them since they will get an error ...
Oh yeah, didn't think of that... Any way to fix OTA installation after flashing this?
kofruge said:
Thanks, that worked to remove the bootloader unlocked warning screen!
One other thing though is when the phone is first turned on while the Moto M logo is still on the screen (just before the Moto startup animation), a line of yellow console text appears over the Moto M logo that says "Verity mode is set to logging." Is there a way to turn that off? Aside from unlocking the bootloader, flashing the logo3.bin file and installing Magisk Manager from TWRP, my phone/ROM is a completely stock retail XT1900-1 (I didn't even flash TWRP to the recovery partition, I just booted it with fastboot to backup my device and install Magisk).
If anyone can help safely remove that line about verity logging without messing anything up that'd be awesome.
Click to expand...
Click to collapse
It worked for me as well on LOS 16, except for the Verity Logging Text, would be nice if we could turn that of too?
Just installed this and it works fine, but is there an Android One version/can one be made? Thanks!
MeowDotEXE said:
Just installed this and it works fine, but is there an Android One version/can one be made? Thanks!
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-x4/themes/bootlogo-custom-bootlogos-dark-variant-t3832118
is there a way to restore the old logo?
vidra said:
is there a way to restore the old logo?
Click to expand...
Click to collapse
Just fastboot flash the boot logo file part of the factory firmware.
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
munchy_cool said:
How to Remove Unlocked Bootloader Warning on Moto X4
Shoutout/Credits to xda member @AvenidaDelGato for the modified logo bin file.
Text Guide.
Make sure adb and fastboot are setup and working.
Donwload and Unzip the modified logo file. Place logo3.bin in platform-tools folders, or whereever you have fastboot and adb.
Navigate to adb/fastboot folder
Windows
Code:
adb devices
Code:
adb reboot bootloader
Code:
fastboot devices
Code:
fastboot flash logo_a logo3.bin
Code:
fastboot flash logo_b logo3.bin
Code:
fastboot reboot
Mac/Linux
Code:
./adb devices
Code:
./adb reboot bootloader
Code:
./fastboot devices
Code:
./fastboot flash logo_a logo3.bin
Code:
./fastboot flash logo_b logo3.bin
Code:
./fastboot reboot
Downloads
Modified Logo.bin zip file - https://forum.xda-developers.com/showpost.php?p=77013516&postcount=4
Mirror of Modified logo.bin zip file - https://mega.nz/#!eYFiVaxT!mpt4RhJDToEcJG4TSpw-CBePLIhd_hm8OjRGTu3egoU
ADB and Fastboot - https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Motorola Drivers - https://support.motorola.com/us/en/drivers
Click to expand...
Click to collapse
I appreciate your work very much! Is it too much to ask for a AndroidOne Boot Logo?
HACK3DANDR0ID said:
I appreciate your work very much! Is it too much to ask for a AndroidOne Boot Logo?
Click to expand...
Click to collapse
No need to quote the OP.
HACK3DANDR0ID said:
I appreciate your work very much! Is it too much to ask for a AndroidOne Boot Logo?
Click to expand...
Click to collapse
i dont make bootlogos
download android one firmware, and flash logo.bin from there
munchy_cool said:
i dont make bootlogos
download android one firmware, and flash logo.bin from there
Click to expand...
Click to collapse
Found what i was looking for thanks
kofruge said:
If anyone can help safely remove that line about verity logging without messing anything up that'd be awesome.
Click to expand...
Click to collapse
wanb1i said:
It worked for me as well on LOS 16, except for the Verity Logging Text, would be nice if we could turn that of too?
Click to expand...
Click to collapse
Flash the attached modified bootloader (unzip first).
Code:
fastboot flash bootloader no-verity-warning-bootloader.img
Found it from a telegram channel. Tested it myself.
Credit @abrfilho
Code:
SHA256SUMs:
b2efd37d2bef4e2de5bcbd7ca3e643a1e1e246d597e6ed4389679d321bebd2f0 no-verity-warning-bootloader.img
fcf3391a13f757d3f998c9b14c5ef40e6084d65b2d0162273d3842e75f972281 no-verity-warning-bootloader.zip
gleenfield97 said:
Flash the attached modified bootloader (unzip first).
Found it from a telegram channel. Tested it myself.
Credit @abrfilho
Click to expand...
Click to collapse
It worked for me, thank you heaps!
gleenfield97 said:
Flash the attached modified bootloader (unzip first).
Found it from a telegram channel. Tested it myself.
Credit @abrfilho
Click to expand...
Click to collapse
I tried this, and bootlooped. I am on stock 9.0 Retail US. Perhaps this is not the right one for my device.
jhedfors said:
I tried this, and bootlooped. I am on stock 9.0 Retail US. Perhaps this is not the right one for my device.
Click to expand...
Click to collapse
Maybe it's not compatible with stock. I'm using Havoc.
The AndroidOne logo.bin if anyone else needs it.
Extracted from stock XT1900-1_PAYTON_FI_9.0_PPW29.69-26_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.
Md5: e306b8ea948a10ec304ca62ebcd60495
Just a warning: after flash the bootlogo file, it seems this change prevent OTA updates. Some hours ago, i receive the 2019 july security patch update and it fails at 90-95 percent. I make a factory reset and it didn't help. Then I flashed the stock rom and the update install very well.
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus 7 in fastboot mode (Power and volume + and volume-);
Connect the OnePlus 7 to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
FLASHER ADVANCED GUIDE
flash-all-partitions-fastboot.bat : this .bat will flash all possible partitions through fastboot (Except persist) , there are some criticals partitions that can't be flashed through fastboot;
flash-only-persist.bat : this .bat will flash only persist partition in fastboot mode (This is good for people that have problems with sensor);
flash-all-partitions-recovery-criticals.bat : this .bat will boot the twrp and will flash criticals partitions, use this carefully;
flash-system-boot-vendor.bat : this .bat is the same of older flash-all.bat and so it will flash only vendor, system and boot;
flash-all-partitions.bat : this .bat will run flash-all-partitions-fastboot.bat , then flash-only-persist.bat and then flash-all-partitions-recovery-criticals.bat .
Now usually the one needed is only the first "flash-all-partitions-fastboot.bat" but if you are badly bricked i recommend to use flash-all-partitions.bat .
DOWNLOAD
All roms on AFH: https://www.androidfilehost.com/?w=files&flid=295200
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (you need to extract images.zip before proceed)
Fastboot Partitions:
Code:
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash LOGO_a LOGO.img
fastboot flash LOGO_b LOGO.img
If you need also persist partition, this is the command:
Code:
fastboot flash persist persist.img
Criticals Partitions, for these you need to boot the TWRP:
Code:
fastboot boot TWRP.img
When you are in TWRP you need to run these commands to push and flash all criticals partitions:
Code:
adb push abl.img /sdcard/abl.img
adb shell dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_a
adb shell dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_b
adb push cmnlib.img /sdcard/cmnlib.img
adb shell dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/by-name/cmnlib_a
adb shell dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/by-name/cmnlib_b
adb push cmnlib64.img /sdcard/cmnlib64.img
adb shell dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/by-name/cmnlib64_a
adb shell dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/by-name/cmnlib64_b
adb push devcfg.img /sdcard/devcfg.img
adb shell dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/by-name/devcfg_a
adb shell dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/by-name/devcfg_b
adb push hyp.img /sdcard/hyp.img
adb shell dd if=/sdcard/hyp.img of=/dev/block/bootdevice/by-name/hyp_a
adb shell dd if=/sdcard/hyp.img of=/dev/block/bootdevice/by-name/hyp_b
adb push keymaster.img /sdcard/keymaster.img
adb shell dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/by-name/keymaster_a
adb shell dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/by-name/keymaster_b
adb push xbl.img /sdcard/xbl.img
adb shell dd if=/sdcard/xbl.img of=/dev/block/bootdevice/by-name/xbl_a
adb shell dd if=/sdcard/xbl.img of=/dev/block/bootdevice/by-name/xbl_b
adb push xbl_config.img /sdcard/xbl_config.img
adb shell dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/by-name/xbl_config_a
adb shell dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/by-name/xbl_config_b
adb push odm.img /sdcard/odm.img
adb shell dd if=/sdcard/odm.img of=/dev/block/bootdevice/by-name/odm_a
adb shell dd if=/sdcard/odm_config.img of=/dev/block/bootdevice/by-name/odm_b
adb push tz.img /sdcard/tz.img
adb shell dd if=/sdcard/tz.img of=/dev/block/bootdevice/by-name/tz_a
adb shell dd if=/sdcard/tz.img of=/dev/block/bootdevice/by-name/tz_b
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
Thanks to @SaiBork for first time tested
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
What does branded devices mean?
What about locking the bootloader. I noticed recovery image is not included
Recovery is a part of the boot image for A/B devices such as Oneplus 7.
---------- Post added at 02:47 PM ---------- Previous post was at 02:46 PM ----------
arvindgr said:
What does branded devices mean?
Click to expand...
Click to collapse
Branded device means it is customized by mobile service provider, such as T Mobile.
any way to flash this without erasing data
Dragonlord07 said:
any way to flash this without erasing data
Click to expand...
Click to collapse
There were multiple scripts included in the zip
Just Be sure to flash the script that does not include -w fastboot parameter
Also, @mauronofrio My phone was originally GM57AA, but since stock image is of GM57BA my phone become GM57BA. Any ideas on how to go back to GM57AA...?
Dragonlord07 said:
any way to flash this without erasing data
Click to expand...
Click to collapse
Just remove -w from the script
arvindgr said:
There were multiple scripts included in the zip
Just Be sure to flash the script that does not include -w fastboot parameter
Also, @mauronofrio My phone was originally GM57AA, but since stock image is of GM57BA my phone become GM57BA. Any ideas on how to go back to GM57AA...?
Click to expand...
Click to collapse
Just flash the GM57AA rom, there are boths in the link you can find in the first post
Ismael034 said:
What about locking the bootloader. I noticed recovery image is not included
Click to expand...
Click to collapse
Hello, I have sent you a message regarding this message. a greeting.
Stuck at boot animation. Is there a way to make it do it's thing on both slots?
fusk said:
Stuck at boot animation. Is there a way to make it do it's thing on both slots?
Click to expand...
Click to collapse
Go in stock recovery, go to wipe data, check also internal storage and wipe it, then it should work.
mauronofrio said:
Go in stock recovery, go to wipe data, check also internal storage and wipe it, then it should work.
Click to expand...
Click to collapse
There is 3 options. Reset system settings, wipe cache & erase everything. There does not appear to be an option to "wipe data" like it would say in twrp or check internal storage. I erased everything and restarted the process, hope that was what you meant.
---------- Post added at 19:23 ---------- Previous post was at 19:15 ----------
That worked, now my question is. The reason i was doing this was because slot B was unable to mount storage, slot A worked fine and phone worked fine. Would this process fix the issue i had with slot B?
fusk said:
There is 3 options. Reset system settings, wipe cache & erase everything. There does not appear to be an option to "wipe data" like it would say in twrp or check internal storage. I erased everything and restarted the process, hope that was what you meant.
---------- Post added at 19:23 ---------- Previous post was at 19:15 ----------
That worked, now my question is. The reason i was doing this was because slot B was unable to mount storage, slot A worked fine and phone worked fine. Would this process fix the issue i had with slot B?
Click to expand...
Click to collapse
if in the slots you have different roms with different security patches only the recent slot will be able to boot. In the .bat there is a command to wipe data, but i don't know why it doesn't work on the oneplus 7 pro
mauronofrio said:
if in the slots you have different roms with different security patches only the recent slot will be able to boot. In the .bat there is a command to wipe data, but i don't know why it doesn't work on the oneplus 7 pro
Click to expand...
Click to collapse
I don't have a 1+7p, so i wouldn't know anything about that. Phone was 9.5.5 when i got it, updated to 9.5.6 with some problems. Wanted to update to 9.5.7 which was unsuccessful. When loading slot B in twrp it could not mount storage or sdcard. Looking at cmd while running your tool, it looks like it's only working with slot A and not touching slot B at any point.
---------- Post added at 19:48 ---------- Previous post was at 19:28 ----------
Appears it worked, can now boot both slots and mount storage and sdcard on both. Thanks for the assist.
fusk said:
I don't have a 1+7p, so i wouldn't know anything about that. Phone was 9.5.5 when i got it, updated to 9.5.6 with some problems. Wanted to update to 9.5.7 which was unsuccessful. When loading slot B in twrp it could not mount storage or sdcard. Looking at cmd while running your tool, it looks like it's only working with slot A and not touching slot B at any point.
---------- Post added at 19:48 ---------- Previous post was at 19:28 ----------
Appears it worked, can now boot both slots and mount storage and sdcard on both. Thanks for the assist.
Click to expand...
Click to collapse
Hello friend, can you say how you did it in the end so that the two slots (A and B) will work? Thank you. Was it because you had encrypted memory and did not let mount slot B? What did you do? Thanks greetings.
mauronofrio said:
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
Click to expand...
Click to collapse
@mauronofrio Hello friend, thanks for your work, I want to ask you if these files to put a rom by fastboot are valid for my version of OnePlus 7 (not pro) Chinese version Gm1900?
Another question I have is, my oneplus 7 gm1900 came with the AA version and I manually added the BA version locally for local improvement. If this fastboot method works, could I put the BA or do I have to put the AA files first?
Thank you.
tURkOsANsE said:
Hello friend, can you say how you did it in the end so that the two slots (A and B) will work? Thank you. Was it because you had encrypted memory and did not let mount slot B? What did you do? Thanks greetings.
Click to expand...
Click to collapse
I did as mentioned. When the .bat failed, i entered "Go in stock recovery" and choose "erase everything" and then ran the .bat again and it worked. I had encryption on both, so that was not the issue. It's fixed now.
fusk said:
I did as mentioned. When the .bat failed, i entered "Go in stock recovery" and choose "erase everything" and then ran the .bat again and it worked. I had encryption on both, so that was not the issue. It's fixed now.
Click to expand...
Click to collapse
Thank you for answering friend, what version do you have of OnePlus 7? Do you have the Chinese version Gm1900 ?.
Before putting the rom by fastboot did you have Twrp installed?
mauronofrio said:
if in the slots you have different roms with different security patches only the recent slot will be able to boot. In the .bat there is a command to wipe data, but i don't know why it doesn't work on the oneplus 7 pro
Click to expand...
Click to collapse
Hello friend, thanks for your work, I want to ask you if these files to put a rom by fastboot are valid for my version of OnePlus 7 (not pro) Chinese version Gm1900?
Another question I have is, my oneplus 7 gm1900 came with the AA version and I manually added the BA version locally for local improvement. If this fastboot method works, could I put the BA or do I have to put the AA files first?
Thank you.
tURkOsANsE said:
Hello friend, thanks for your work, I want to ask you if these files to put a rom by fastboot are valid for my version of OnePlus 7 (not pro) Chinese version Gm1900?
Another question I have is, my oneplus 7 gm1900 came with the AA version and I manually added the BA version locally for local improvement. If this fastboot method works, could I put the BA or do I have to put the AA files first?
Thank you.
Click to expand...
Click to collapse
Yes it will work on the oneplus 7, there are 2 different thread for the fastboot roms this one is for oneplus 7 only. AA or BA there are not a lot of.differences, just use the one you prefer.
I accidentally made a mistake, flash custom kernel when my phone has custom kernel installed. Now every time i'm trying to boot up, my phone is only able to boot on fastboot mode, no recovery and i unable to install recovery too (stock/custom).
I wonder, is this method can save my phone?
Thank you.
cakriez92 said:
I accidentally made a mistake, flash custom kernel when my phone has custom kernel installed. Now every time i'm trying to boot up, my phone is only able to boot on fastboot mode, no recovery and i unable to install recovery too (stock/custom).
I wonder, is this method can save my phone?
Thank you.
Click to expand...
Click to collapse
Yes
Could anyone please help with a guide for rooting Nokia 3 and flashing TWRP that works for Android 9.0?
Thanks.
It's very easy if you have the bootloader already unlocked.
1.- Download magisk apk from github
2.- Install and download the zip
3.- Move the zip to a sd card
4.- Flash twrp using Sp Flash Tools
5.- Boot into recovery and flash magisk zip
That's all
I tried yesterday
Zhowlx said:
It's very easy if you have the bootloader already unlocked.
1.- Download magisk apk from github
2.- Install and download the zip
3.- Move the zip to a sd card
4.- Flash twrp using Sp Flash Tools
5.- Boot into recovery and flash magisk zip
That's all
I tried yesterday
Click to expand...
Click to collapse
Thank you for your answer.
What if you don't have your bootloader unlocked ? Do you just need to check the "Unlock Bootloader" switch in the developers options ? Thank you
Soupape50 said:
Thank you for your answer.
What if you don't have your bootloader unlocked ? Do you just need to check the "Unlock Bootloader" switch in the developers options ? Thank you
Click to expand...
Click to collapse
The only way Is unlocking the bootloader
Just follow this steps and it's done
https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-unlock-bootloader-nokia-3-t3699344
Zhowlx said:
The only way Is unlocking the bootloader
Just follow this steps and it's done
https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-unlock-bootloader-nokia-3-t3699344
Click to expand...
Click to collapse
Thank you really much for your answer, but I don't think this tutorial works on android Pie :/
unfortunately not, I downgrade the android version to nougat and from there I did the whole process, then updated to oreo and then to android p
Zhowlx said:
It's very easy if you have the bootloader already unlocked.
1.- Download magisk apk from github
2.- Install and download the zip
3.- Move the zip to a sd card
4.- Flash twrp using Sp Flash Tools
5.- Boot into recovery and flash magisk zip
That's all
I tried yesterday
Click to expand...
Click to collapse
have tried it?
Zhowlx said:
It's very easy if you have the bootloader already unlocked.
1.- Download magisk apk from github
2.- Install and download the zip
3.- Move the zip to a sd card
4.- Flash twrp using Sp Flash Tools
5.- Boot into recovery and flash magisk zip
That's all
I tried yesterday
Click to expand...
Click to collapse
Can you give more details like what zip ? what apk ( magisk or magisk manager)? How to boot into recovery? (Samsung is easier to boot than nokia so i dont know how to)
Zhowlx said:
unfortunately not, I downgrade the android version to nougat and from there I did the whole process, then updated to oreo and then to android p
Click to expand...
Click to collapse
Hey. How to downgrade nokia 3 from pie to nogaut ? I want to root my device
before you do this just remember this wipes your phone
you can unlock your nokia 3 on 9.0 just make sure bootloader is unlocked in dev settings and boot into fastboot.
then run the following commands
fastboot -i 0x2e04 oem key [MD5-key]
fastboot flashing unlock_critical
fastboot flash boot [path to whatever you're flashing e.g. magisk]
then run
fastboot reboot
and your phone will be rooted and the bootloader unlocked
NulledRoot said:
before you do this just remember this wipes your phone
you can unlock your nokia 3 on 9.0 just make sure bootloader is unlocked in dev settings and boot into fastboot.
then run the following commands
fastboot -i 0x2e04 oem key [MD5-key]
fastboot flashing unlock_critical
fastboot flash boot [path to whatever you're flashing e.g. magisk]
then run
fastboot reboot
and your phone will be rooted and the bootloader unlocked
Click to expand...
Click to collapse
How can I remove the orange state?
I mean, currently, if I lock the bootloader again, I get a red state.
and I can only skip it, if I connect it to the usb.
and start normally, without any status warning, if it is connected to the usb
djxpro said:
How can I remove the orange state?
I mean, currently, if I lock the bootloader again, I get a red state.
and I can only skip it, if I connect it to the usb.
and start normally, without any status warning, if it is connected to the usb
Click to expand...
Click to collapse
perhaps flash an unmodified boot image?
NulledRoot said:
perhaps flash an unmodified boot image?
Click to expand...
Click to collapse
that implies then that I could not root it.
****
I guess I'll keep the orange state.
NulledRoot said:
fastboot -i 0x2e04 oem key [MD5-key]
Click to expand...
Click to collapse
>>>>fastboot: unknown option -- i
TA-1032, android 9 (00W_5_120_SP02), OEM unlocking in dev.opt. enabled.
NOWAY!
ORANGE STATE (^_^)
fastboot oem key [md5 KEY]
fastboot flashing unlock
fastboot reboot
NulledRoot said:
before you do this just remember this wipes your phone
you can unlock your nokia 3 on 9.0 just make sure bootloader is unlocked in dev settings and boot into fastboot.
then run the following commands
fastboot -i 0x2e04 oem key [MD5-key]
fastboot flashing unlock_critical
fastboot flash boot [path to whatever you're flashing e.g. magisk]
then run
fastboot reboot
and your phone will be rooted and the bootloader unlocked[/QUOTE
How to get MD5-key ?
Click to expand...
Click to collapse
Hasnain77 said:
NulledRoot said:
before you do this just remember this wipes your phone
you can unlock your nokia 3 on 9.0 just make sure bootloader is unlocked in dev settings and boot into fastboot.
then run the following commands
fastboot -i 0x2e04 oem key [MD5-key]
fastboot flashing unlock_critical
fastboot flash boot [path to whatever you're flashing e.g. magisk]
then run
fastboot reboot
and your phone will be rooted and the bootloader unlocked[/QUOTE
How to get MD5-key ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-unlock-bootloader-nokia-3-t3699344
you need your SN from your phone and put it on the web that is in the thread
Click to expand...
Click to collapse
NulledRoot said:
before you do this just remember this wipes your phone
you can unlock your nokia 3 on 9.0 just make sure bootloader is unlocked in dev settings and boot into fastboot.
then run the following commands
fastboot -i 0x2e04 oem key [MD5-key]
fastboot flashing unlock_critical
fastboot flash boot [path to whatever you're flashing e.g. magisk]
then run
fastboot reboot
and your phone will be rooted and the bootloader unlocked
Click to expand...
Click to collapse
I am in very trouble to rooting my Nokia 3 ta-1032 pie... Pls help me how to unlock bootloader and flash twrp and root on nokia 3 pie security patch 5 October 2019:crying::crying:help me plz
aditya#777 said:
I am in very trouble to rooting my Nokia 3 ta-1032 pie... Pls help me how to unlock bootloader and flash twrp and root on nokia 3 pie security patch 5 October 2019:crying::crying:help me plz
Click to expand...
Click to collapse
get the twrp recovery image file from unofficialtwrp.com/nokia-3-root-twrp-3-2-3 ....
rename the file to recovery.img and put the file in adb directory.....also put the magisk.zip file in the sd card (don't put it in the internal memory)
then get into fastboot mode....then enter the following commands....
fastboot oem key [md5 hash]
fastboot flashing unlock
fastboot flash recovery recovery.img
fastboot reboot
while rebooting, instantly press vol up+power to go into recovery mode( dont let the phone to boot normally or you will have to flash twrp again and your phone might be in orange state but ignore that)....if it shows "no command" press the same buttons at the same time to get into recovery mode.....then install the magisk.zip and reboot....then install magisk.apk and you are done.... tried and tested on nokia 3 ta- 1032 android pie just today and it worked...
mech59 said:
get the twrp recovery image file from unofficialtwrp.com/nokia-3-root-twrp-3-2-3 ....
rename the file to recovery.img and put the file in adb directory.....also put the magisk.zip file in the sd card (don't put it in the internal memory)
then get into fastboot mode....then enter the following commands....
fastboot oem key [md5 hash]
fastboot flashing unlock
fastboot flash recovery recovery.img
fastboot reboot
while rebooting, instantly press vol up+power to go into recovery mode( dont let the phone to boot normally or you will have to flash twrp again and your phone might be in orange state but ignore that)....if it shows "no command" press the same buttons at the same time to get into recovery mode.....then install the magisk.zip and reboot....then install magisk.apk and you are done.... tried and tested on nokia 3 ta- 1032 android pie just today and it worked...
Click to expand...
Click to collapse
can you confirm that this method to root the phone is still working right now with the latest updates of nokia 3?
freaks211 said:
can you confirm that this method to root the phone is still working right now with the latest updates of nokia 3?
Click to expand...
Click to collapse
Don't do it !!! After rooting TA-1032 Pie 9, camera does not work !!!
Hier is what I did:
$ adb devices
$ adb reboot bootloader
$ fastboot devices
$ echo -n "NE1GXXXXXXXXXXXX" | md5sum | tr a-z A-Z | awk '{print $1}'
$ fastboot oem key YOUR-KEY
# the first time did not accepted
$ fastboot -i 0x2e04 oem key YOUR-KEY
$ fastboot oem key YOUR-KEY
$ fastboot flashing unlock
$ fastboot reboot
# Installed magisk v23.apk
$ fastboot flash boot magisk_patched-23000_7R099.img
$ fastboot reboot
I can confirm that this works on Nokia3 TA-1032, but the problem is the camera.
All you get is green background, if anyone knows hot to fix the green
background, please let me/us know.
Thank you,
so as the title suggests, my oneplus 7 pro is now stuck at fastboot and my only hope is on the img files from the unpacked payload.bin. but now after I extract it, i heard some of the img files are used to clear the user, data etc, can someone tell me which one is which?
The guide I followed:
https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/
https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-extract-payload-bin-ota-t3830962
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
the first link seem to be outdated since most of the img files it talked about don't exist but although the third link isn't, it told me how to flash each file, but my problem is that I don't want to lose my data, can someone tell me which img file is used to erase data? thanks a lot
shuaiouke said:
so as the title suggests, my oneplus 7 pro is now stuck at fastboot and my only hope is on the img files from the unpacked payload.bin. but now after I extract it, i heard some of the img files are used to clear the user, data etc, can someone tell me which one is which?
The guide I followed:
https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/
https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-extract-payload-bin-ota-t3830962
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
the first link seem to be outdated since most of the img files it talked about don't exist but although the third link isn't, it told me how to flash each file, but my problem is that I don't want to lose my data, can someone tell me which img file is used to erase data? thanks a lot
Click to expand...
Click to collapse
userdata.img will override your internal storage with zero bytes.
matze19999 said:
userdata.img will override your internal storage with zero bytes.
Click to expand...
Click to collapse
is that the only file? thanks
Edit:There don't seem to be a file called userdata.img it's a ONEPLUS 7 PRO rom
Right click and edit flash all.bat and remove the -w and save then u can run flash all.bat using the fastboot Rom, ur 3rd link
thank you and it lets me get into recovery in a boot loop but recovery only, I can't flash TWRP, what should I do next?
Bradl79 said:
Right click and edit flash all.bat and remove the -w and save then u can run flash all.bat using the fastboot Rom, ur 3rd link
Click to expand...
Click to collapse
thank you and it lets me get into recovery in a boot loop but recovery only, I can't flash TWRP, what should I do next?
shuaiouke said:
thank you and it lets me get into recovery in a boot loop but recovery only, I can't flash TWRP, what should I do next?
Click to expand...
Click to collapse
is your bootloader locked?
shuaiouke said:
thank you and it lets me get into recovery in a boot loop but recovery only, I can't flash TWRP, what should I do next?
Click to expand...
Click to collapse
We're you coming from a custom Rom, or stock. You might have to format data.
Bradl79 said:
is your bootloader locked?
Click to expand...
Click to collapse
it's kinda obvious, flash-all is flashing after all if ur bootloader is locked, how do u flash?
Note: This is for soft bricks only.
soft brick = can access fastboot or recovery
hard brick = no boot, black screen boot. etc.............
I found myself on OB4, tried to sideload another build and got stuck. Tried to boot into TWRP, no bueno, now what? I didn't want to use MSM tools and go though that whole process again. I've saved many of my devices with Linux, by just flashing the img files through fastboot commands. So if your comfortable with the command line this is easier then using the flash tools that relock your bootloader. This also works with Widows, so I remembered the files the fastboot flasher flashed, and just flashed them manually, you just need flash to the correct partition. So, if it's a boot img, then flash boot, and system flash system, and so on. List of files that I flashed.
First you'll need payload dumper, to extract files from payload.bin file inside whatever OTA, you want to flash. It will extract to a folder called payload_output, from there you can click and drag to command line.
https://androidfilehost.com/?fid=818070582850510260
I also provided a copy of my script, you'll need to edit to your files path. And save as .bat, .cab, or .exe...........
Commands I run before flash
fastboot format system
fastboot format userdata
1. boot.img
2. dtbo
3. modem
4. odm
5. qupfw
6. storsec
7. system
8. vbmeta
9. vendor
10. fastboot reboot
If device boots to recovery which should be stock, just wipe everything and you should boot into system without a problem.
Has the full rom been released yet?
arsalturtle891 said:
Has the full rom been released yet?
Click to expand...
Click to collapse
No, at least on Oxygen Updater. Are you on F20 and you want to root?
TheNewHEROBRINE said:
No, at least on Oxygen Updater. Are you on F20 and you want to root?
Click to expand...
Click to collapse
I'm on F18 with root and I want to upgrade to F20. Is there an LE2115_11.F.18 full rom by any chance. I can flash this and then upgrade to F20. I don't mind being without root for the time being
arsalturtle891 said:
I'm on F18 with root and I want to upgrade to F20. Is there an LE2115_11.F.18 full rom by any chance. I can flash this and then upgrade to F20. I don't mind being without root for the time being
Click to expand...
Click to collapse
When you rooted did you do fastboot flash or fastboot boot and then direct install in Magisk app?
I did the following:
Fastboot boot "patchedbootimage".img
Fastboot flash boot_a "patchedbootimage".img
Fastboot flash boot_b "patchedbootimage".img
arsalturtle891 said:
I did the following:
Fastboot boot "patchedbootimage".img
Fastboot flash boot_a "patchedbootimage".img
Fastboot flash boot_b "patchedbootimage".img
Click to expand...
Click to collapse
Then you can't restore your original boot image from Magisk. You should only ever do fastboot boot and then use direct install in Magisk. Unfortunately the latest full rom available for your device is LE2115_11_F.17, so I think your only chance is that someone share a stock F18 boot image so that you can flash it and then update.
arsalturtle891 said:
I did the following:
Fastboot boot "patchedbootimage".img
Fastboot flash boot_a "patchedbootimage".img
Fastboot flash boot_b "patchedbootimage".img
Click to expand...
Click to collapse
First command, you booted the patched boot image. All good. From there, install/open Magisk app and then select direct install option, and Magisk will automatically back up the stock boot and then flash the rooted boot.
Second commands shouldn't have been run.
shadabkiani said:
First command, you booted the patched boot image. All good. From there, install/open Magisk app and then select direct install option, and Magisk will automatically back up the stock boot and then flash the rooted boot.
Second commands shouldn't have been run.
Click to expand...
Click to collapse
Appreciate it!
shadabkiani said:
First command, you booted the patched boot image. All good. From there, install/open Magisk app and then select direct install option, and Magisk will automatically back up the stock boot and then flash the rooted boot.
Second commands shouldn't have been run.
Click to expand...
Click to collapse
I'm not seeing the attachment
Here is the stock unrooted F.18 boot.img. Make sure to extract it first.
So I was able to remove root by first following the same commands I used to root in the first place with the boot image you provided. However, I cannot update to F20 using the system update. It keeps failing
Ok, this time, you have to flash this unrooted boot.img that I provided. NOT just boot it like you do when trying to root. The system will check the flashed boot.img then proceed with OTA.
fastboot flash boot boot.img
Reboot, then try OTA update.
When you have the latest F.20 successfully booted, if you want root, you can get that boot.img through MSM readback feature. Or, I have F.20 boot.img too, and you can ask for that.
shadabkiani said:
Ok, this time, you have to flash this unrooted boot.img that I provided. NOT just boot it like you do when trying to root. The system will check the flashed boot.img then proceed with OTA.
fastboot flash boot boot.img
Reboot, then try OTA update.
When you have the latest F.20 successfully booted, if you want root, you can get that boot.img through MSM readback feature. Or, I have F.20 boot.img too, and you can ask for that.
Click to expand...
Click to collapse
I followed your steps and it still gives an installation error. Just to make sure, I uninstalled magisk through the magist app as well. Further, I did some research on the MSM readback feature. Can you link me to the correct one to use?
arsalturtle891 said:
I followed your steps and it still gives an installation error. Just to make sure, I uninstalled magisk through the magist app as well. Further, I did some research on the MSM readback feature. Can you link me to the correct one to use?
Click to expand...
Click to collapse
The MSM Tool for Global thread is here, but the download link in first post is incomplete. You can download the full tool from here. Make sure to download the correct package. The global one also works for LE2110 (the Chinese model).
So you have flashed my boot.img, and then you are updating from where? Through system update OTA, or from zip file downloaded with Oxygen Updater app?
shadabkiani said:
The MSM Tool for Global thread is here, but the download link in first post is incomplete. You can download the full tool from here. Make sure to download the correct package. The global one also works for LE2110 (the Chinese model).
So you have flashed my boot.img, and then you are updating from where? Through system update OTA, or from zip file downloaded with Oxygen Updater app?
Click to expand...
Click to collapse
I tried both methods and both fail (through system update OTA, and from zip downloaded with oxygen updater app)
I did the following:
fastboot boot "stockboot"
fastboot flash boot "stockboot"
AND I TRIED THIS TOO:
fastboot boot "stockboot"
fastboot flash boot_a "stockboot"
fastboot flash boot_b "stockboot"
arsalturtle891 said:
I tried both methods and both fail (through system update OTA, and from zip downloaded with oxygen updater app)
I did the following:
fastboot boot "stockboot"
fastboot flash boot "stockboot"
AND I TRIED THIS TOO:
fastboot boot "stockboot"
fastboot flash boot_a "stockboot"
fastboot flash boot_b "stockboot"
Click to expand...
Click to collapse
Why do you always "fastboot boot......" and then "fastboot flash boot...."?
Generally, fastboot boot.... will make you phone boot up the given image temporarily (whether it's a boot image or a bootable recovery image). Whereas, fastboot flash boot.... will permanently flash the given image. Normally, you only have to go with one of these methods depending on your task/goal.
Anyway, since you have flashed the stock unrooted boot.img and OTA is still failing, I suggest you just back up your personal data (photos, stuff) to PC or whatever, and then go with the MSM tool method. It will wipe all your data on phone, and revert your phone to OOS11 with locked bootloader. From there, you can take OTA updates all the way upto OOS13 F.20. This seems to be the simpler way to get out of your current predicament.
How to use MSM tool:
1. Download the package according to your device/variant, and extract it.
2. Power off your phone and keep it aside. DO NOT connect your phone to PC for now.
3. Run the MSM tool exe. It will take a couple of minutes to load.
4. Click on Target drop-down menu and choose O2 if you are on Global.
5. Click Start. It will go to Waiting for Device mode.
6. Now on your phone (which should already be powered off), press & hold both the vol+ and vol- buttons (NOT the power button) and connect the data cable from PC to your phone. Your phone's screen will still stay black and it will enter EDL mode.
7. The MSM tool will start flashing as soon as the connection is successful.
Note: You need to have OnePlus device drivers on PC.
I appreciate the support. Can you also provide me with the F20 boot image by any chance.
Sure. Stock unrooted F.20 boot.img attached. Make sure to unzip it.
By the way, if you have MSM tool, you can get your current boot.img from its readback feature. Super simple. Launch MSM tool. Press F8. Select the desired boot image (boot_a or boot_b). Enter the password as: oneplus. Click read. Power off phone, and get it into EDL mode by pressing holding vol- vol+ buttons then connecting data cable from PC. The desired boot.img will be dumped in C: drive.
Also, F.21 has just been released, so you better update to that. I haven't yet as I am currently on crDroid.
Anyway, F.20 boot has been attached.
Hello sir Can I get F.21 boot
vendor boot
dtbo
there're no FULL package out there for Global variant
Just only incremental update
How can I get that Full Image?
Or Should I extract it from India Variant Full Image F.21
will It work normally?