Related
What's up all. So I have a Verizon pixel rooted on 7.1. I want to sideload 7.1.1 but don't want lose the ability to re root etc. Just wanna make sure I have he steps down.
-flash back to stock boot image
-sideload 7.1.1 ota
-flash twrp
-flash root
Am I missing anything??
You could also flash back to stock boot image, boot up and take the OTA actually over the air.
Also, don't flash TWRP initially, just boot TWRP, flash twrp from inside twrp, reboot into recovery, then finally flash root (make sure to read the twrp rc1 thread, post #2) reboot to let root finish, and done. (unless you want a custom Kernel, then do this very last.
After doing a twrp backup and backing up the entire device, I used this method to update with twrp and root installed. I did not lose data.
Afterwards you will need to install TWRP and root.
mruno said:
After doing a twrp backup and backing up the entire device, I used this method to update with twrp and root installed. I did not lose data.
Afterwards you will need to install TWRP and root.
Click to expand...
Click to collapse
Ok that looks easy enough. What is the command you typed to flash the file after its modified?
computercarl said:
You could also flash back to stock boot image, boot up and take the OTA actually over the air.
Also, don't flash TWRP initially, just boot TWRP, flash twrp from inside twrp, reboot into recovery, then finally flash root (make sure to read the twrp rc1 thread, post #2) reboot to let root finish, and done. (unless you want a custom Kernel, then do this very last.
Click to expand...
Click to collapse
This sounds like the easiest way. Where do i get the stock boot image from? Do i extract it from the factory image zip file? And then once I get it what is the command I'd use to flash it?
https://www.androidfilehost.com/?fid=529152257862669140 is nde63p's boot.img. If you are on something else, you can extract it's boot.img from the factory image, there's a boot file in there. Fastboot boot <img file name> will boot it, then you can take the ota, reboot because the ota needs to finish. copy twrp.zip on to sd card, (were going to need it in a minute!) then fastboot boot twrp3020rc1.img the same way. From twrp, flash the zip. tell twrp to reboot into recovery. it will reboot into twrp, from the recovery (Or dont flash the zip, you dont have to, some prefer to remain on stock recovery) and then flash SU SR5 (How to install SuperSU SR5 on TWRP RC1: Before flashing the zip, in TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it. ) then finally flash a kernel. If you are going to flash root, might as well flash ElementalX 1.01 kernel from twrp. Hope that is a bit more breakdown.
computercarl said:
https://www.androidfilehost.com/?fid=529152257862669140 is nde63p's boot.img. If you are on something else, you can extract it's boot.img from the factory image, there's a boot file in there. Fastboot boot <img file name> will boot it, then you can take the ota, reboot because the ota needs to finish. copy twrp.zip on to sd card, (were going to need it in a minute!) then fastboot boot twrp3020rc1.img the same way. From twrp, flash the zip. tell twrp to reboot into recovery. it will reboot into twrp, from the recovery (Or dont flash the zip, you dont have to, some prefer to remain on stock recovery) and then flash SU SR5 (How to install SuperSU SR5 on TWRP RC1: Before flashing the zip, in TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it. ) then finally flash a kernel. If you are going to flash root, might as well flash ElementalX 1.01 kernel from twrp. Hope that is a bit more breakdown.
Click to expand...
Click to collapse
I extracted the boot.img and put in in my fastboot folder, but when I go to flash it it's saying file not found?? I named it boot.img and am typing fastboot flash boot boot.img. I've also tried fastboot boot boot.img and get the same message.
What am i doing wrong? Could I have the wrong boot image??
mpetruzz said:
Ok that looks easy enough. What is the command you typed to flash the file after its modified?
Click to expand...
Click to collapse
just double click the .bat file and it will perform all of the commands. the first boot afterwards will take a few mins.
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.
I updated to android 10 an hour ago, and placed my phone into the bootloader so I could re-flash TWRP. After I ran the command (fastboot flash boot C:\Users\USER\Downloads\twrp-3.3.1-4-guacamole.img), and tried rebooting, I couldn't leave the bootloader. I've tried using the buttons, trying to push the img to the phone and force it into TWRP, but nothing works. I think I didn't enable USB debugging when I entered the bootloader, but it was enabled before I updated.
It's a known issue, the commands aren't included in the bootloader for q yet. We need to wait for OnePlus to add them. To fix your problem, try fastboot booting the magisk patched boot.img for the 10 beta.
USB Debugging has nothing to do with fastboot.... Just flash stock boot img or a patched with twrp/magisk and boot your phone usually
mercenaryhmster said:
It's a known issue, the commands aren't included in the bootloader for q yet. We need to wait for OnePlus to add them. To fix your problem, try fastboot booting the magisk patched boot.img for the 10 beta.
Click to expand...
Click to collapse
Where do I find the patched boot image?
TheEndernaut said:
Where do I find the patched boot image?
Click to expand...
Click to collapse
If nothing helps, try to reflash with MsmDownloadTool.
TheEndernaut said:
Where do I find the patched boot image?
Click to expand...
Click to collapse
https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345
Also, once you flashed boot image and booted into Android, Download the twrp INSTALLER and install it via magisk module
From here
https://www.androidfilehost.com/?fid=1899786940962578045
GUGUITOMTG4 said:
https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345
Also, once you flashed boot image and booted into Android, Download the twrp INSTALLER and install it via magisk module
From here
https://www.androidfilehost.com/?fid=1899786940962578045
Click to expand...
Click to collapse
Was able to get past the bootloader, but once I swipe up to load the device, it blacks out
GUGUITOMTG4 said:
https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345
Also, once you flashed boot image and booted into Android, Download the twrp INSTALLER and install it via magisk module
From here
https://www.androidfilehost.com/?fid=1899786940962578045
Click to expand...
Click to collapse
I can't find the menue in magisk manager where I can install TWRP
TheEndernaut said:
I can't find the menue in magisk manager where I can install TWRP
Click to expand...
Click to collapse
Hamburger (upper left), modules, plus icon (bottom center), browse to twrp installer zip.
TheEndernaut said:
I updated to android 10 an hour ago, and placed my phone into the bootloader so I could re-flash TWRP. After I ran the command (fastboot flash boot C:\Users\USER\Downloads\twrp-3.3.1-4-guacamole.img), and tried rebooting, I couldn't leave the bootloader. I've tried using the buttons, trying to push the img to the phone and force it into TWRP, but nothing works. I think I didn't enable USB debugging when I entered the bootloader, but it was enabled before I updated.
Click to expand...
Click to collapse
First you don't flash the TWRP image.
That image is used as a fastboot boot. It is not to be flashed.
Normally, you would boot with that image and flash the TWRP zip to make it permanent.
Once TWRP is flashed, you need to also flash Magisk.
To get out of the situation you are in, you need a stock boot image to flash.
Once that is done, you can start over.
Read the instructions carefully before flashing images.
johnx818 said:
Hamburger (upper left), modules, plus icon (bottom center), browse to twrp installer zip.
Click to expand...
Click to collapse
There is no modules page
johnx818 said:
Hamburger (upper left), modules, plus icon (bottom center), browse to twrp installer zip.
Click to expand...
Click to collapse
There is no modules menu
tech_head said:
First you don't flash the TWRP image.
That image is used as a fastboot boot. It is not to be flashed.
Normally, you would boot with that image and flash the TWRP zip to make it permanent.
Once TWRP is flashed, you need to also flash Magisk.
To get out of the situation you are in, you need a stock boot image to flash.
Once that is done, you can start over.
Read the instructions carefully before flashing images.
Click to expand...
Click to collapse
Just to clarify then, when I run fastboot flash boot TWRP, I use the zip? If not, what command am I using?!
The command is "fastboot boot recoveryfilaneme.img" using the .img file
TheEndernaut said:
Just to clarify then, when I run fastboot flash boot TWRP, I use the zip? If not, what command am I using?!
Click to expand...
Click to collapse
No, no, no.
TWRP can only be flashed from either TWRP or Magisk.
On this device, you can only boot the image file. You can only flash the zip while running a booted TWRP or from the Magisk Manager.
TheEndernaut said:
Just to clarify then, when I run fastboot flash boot TWRP, I use the zip? If not, what command am I using?!
Click to expand...
Click to collapse
Hope I can explain myself. You are using a command you shouldn't be using: fastboot FLASH boot, you shouldn't flash the image from fastboot, you need to use that image to boot into recovery and then flash recovery itself from INSIDE recovery, then you NEED to flash Magisk from inside recovery too.
The command is: fastboot boot recovery.img
Btw, you can't see the "modules" option in Magisk because I think you flashed stock boot.img. Try flashing Magisk patched boot img and then flash recovery in Magisk as it was said before.
Did you click all the 3 buttons at once?
TheEndernaut said:
After I ran the command (fastboot flash boot C:\Users\USER\Downloads\twrp-3.3.1-4-guacamole.img)
Click to expand...
Click to collapse
This is not a command you will find in any guide for this device (at least not any guide that is correct)!
The command you used, flashed the image to over-write the boot partition, which is essentially the kernel. You no longer have a kernel, so of course the phone cannot properly boot to OS. This is also not the correct way to install TWRP, so therefore you have no TWRP installed on the phone, either.
Proper sequence to install TWRP would have been:
1) fastboot boot TWRP.img
This only "boots" into TWRP, but does not install it. I know the syntax here is confusing. "boot" versus "flash boot" do completely different things. In this case "boot" is the action. In the command you used "flash" is the action, and the "boot" partition is the location.
2) Flash TWRP installer zip
3) Flash Magisk
At this point, the easiest path is probably to do what was suggested in Reply #6 above (flash patched boot image, boot to OS, open Magisk and install TWRP from Magisk).
redpoint73 said:
This is not a command you will find in any guide for this device (at least not any guide that is correct)!
The command you used, flashed the image to over-write the boot partition, which is essentially the kernel. You no longer have a kernel, so of course the phone cannot properly boot to OS. This is also not the correct way to install TWRP, so therefore you have no TWRP installed on the phone, either.
Proper sequence to install TWRP would have been:
1) fastboot boot TWRP.img
This only "boots" into TWRP, but does not install it. I know the syntax here is confusing. "boot" versus "flash boot" do completely different things. In this case "boot" is the action. In the command you used "flash" is the action, and the "boot" partition is the location.
2) Flash TWRP installer zip
3) Flash Magisk
At this point, the easiest path is probably to do what was suggested in Reply #6 above (flash patched boot image, boot to OS, open Magisk and install TWRP from Magisk).
Click to expand...
Click to collapse
How do you install TWRP from Magisk?
blade35 said:
How do you install TWRP from Magisk?
Click to expand...
Click to collapse
Magisk/Modules/+/Select TWRP installer.zip
This TWRP works with Xiaomi 12
📌 [Shared] TWRP by skkk
âš¡âš¡A12/A13âš¡âš¡ ----------------------- BOOT VERSION Installation: Phone in fastboot mode Cmd: fastboot boot twrp.img or Power shell ./fastboot boot twrp.img then in Twrp go to Advanced -> flash current TWRP...
forum.xda-developers.com
Command to install:
1. boot your device in Fastboot mode
2. fastboot boot recovery_finename.img
This will temporary boot your device to TWRP
3. From TWRP go to Advanced and choose "Flash curent TWRP" - this will permanently install TWRP but will overwrite magisk scripts, so root will be lost.
4. Flash magisk from TWRP - this will fix root.
Thanks bro.
will this lost data or need to clear any caches after done installation TWRP?
you loose nothing and no caches to clear
geraldine said:
you loose nothing and no caches to clear
Click to expand...
Click to collapse
Well noted that.
I've tried and success!
Thanks again!
3.8.4
skkk/TWRP/A12/v3.8.4_A12 • AKR DL
dl.akr-developers.com
update 3.9
skkk/TWRP/A12/v3.9_A12 • AKR DL
dl.akr-developers.com
What does "boot" or "REC" mean? I always thought twrp is just a one file?
REC it's for direct flash the recovery with "fastboot flash recovery.img" (doesn't work for me)
BOOT it's for boot to the recovery "fastboot boot recovery.img" to flash permently go to advanced and "flash current twrp" (work great)
geraldine said:
update 3.9
skkk/TWRP/A12/v3.9_A12 • AKR DL
dl.akr-developers.com
Click to expand...
Click to collapse
Can I update from 3.8?
What is the changelog?
Yes, but you lose root. if there is.
double post, sorrry**
mmm, dont work for me, idk if im doing something wrong, when i put the command (fastboot boot recovery_name.img) it restarts, but the screen stays black and need the force the start.
I download this [BOOT]3.6.2_12-Mi12_v3.9_A12-cupid-skkk_632fca0d.img maybe im wrong with the version =/
darkevangelion said:
mmm, dont work for me, idk if im doing something wrong, when i put the command (fastboot boot recovery_name.img) it restarts, but the screen stays black and need the force the start.
I download this [BOOT]3.6.2_12-Mi12_v3.9_A12-cupid-skkk_632fca0d.img maybe im wrong with the version =/
Click to expand...
Click to collapse
There is a newer:
Downloading • AKR DL
immerzu2 said:
There is a newer:
Downloading • AKR DL
Click to expand...
Click to collapse
Thank you!! this version work, is it reccommended to make it permanent? i dont use root or magisk.
Hello. I have the latest TWRP installed on my Xiaomi 12. A friend of mine installed it. I would like to learn it, but the command "fasboot boot twrp.img" doesn't work for me. I don't know what I'm doing wrong, but the phone still won't boot into TWRP. I'm using ADB minimal and I renamed the downloaded file to twrp.img and put it in ADB minimal, then I used the command mentioned above, but still nothing happens, the phone won't enter TWRP. Once it enters TWRP, I use the command: "flash current twrp", I already know the next procedure. I welcome help. Thanks
Benoni1 said:
Hello. I have the latest TWRP installed on my Xiaomi 12. A friend of mine installed it. I would like to learn it, but the command "fasboot boot twrp.img" doesn't work for me. I don't know what I'm doing wrong, but the phone still won't boot into TWRP. I'm using ADB minimal and I renamed the downloaded file to twrp.img and put it in ADB minimal, then I used the command mentioned above, but still nothing happens, the phone won't enter TWRP. Once it enters TWRP, I use the command: "flash current twrp", I already know the next procedure. I welcome help. Thanks
Click to expand...
Click to collapse
" I would like to learn it, but the command "fasboot boot twrp.img" doesn't work for me"
Check with"fastboot devices"CMD or "./fastboot devices"Powershell before
the phone must be in fastboot mode.
CMD=fastboot boot recovery twrp.img
Powershell=./fastboot boot recovery twrp.img
Then use the twrp
go to Advanced > Flash Current TWRP
The Twrp .img must be in the same folder as the command.
Possibly post the screenshot of the result of the command
Flash TWRP-I still can't do it, I'm sending pictures
Benoni1 said:
Flash TWRP-I still can't do it, I'm sending pictures
Click to expand...
Click to collapse
Already said in the post above.
1/You wrote "fasboot" instead of fastboot.
2/Download SDK platform-tool extract the folder and put the twrp in it.
https://developer.android.com/studio/releases/platform-tools
3/ use the command from the folder where the twrp is.
NOSS8 said:
Already said in the post above.
1/You wrote "fasboot" instead of fastboot.
2/Download SDK platform-tool extract the folder and put the twrp in it.
https://developer.android.com/studio/releases/platform-tools
3/ use the command from the folder where the twrp is.
View attachment 5688077​
Click to expand...
Click to collapse
Hello, I already know it was successful. Thank you for your help. Best regards, Josef
fastboot flash recovery xxx.img is not correct.
the command is: fastboot flash recovery_ab xxx.img
A question: why the twrp version jumped from from 3.x directly to 5.x?
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?