Related
Hi, earlier, I wanted to change the rom of my mi 5s. I've got an error 7 follow by "Failed to update system image" on twrp during the flash. I tried many things: edit the installation script, format all the data, update and downgrade TWRP, lock and unlock bootlander and finally perform a fastboot flash using mi flash and the last one worked. But I am not longer able to flash a custom rom without getting error 7 after the "Patching system image unconditionally" message. I've tested lineage, pixel experience, miui, even 8.1 rom but same result. I'm stuck with fastboot global miui 10 (oreo )
Btw, I think that after the error the partition are corrupted since I can't repair them with TWRP.
I don't know what I can do more.I think that i figured out that I am able to flash system.img file using fastboot but I can't flash zip rom using recovery.
As anyone encounter this ?
bob_bricoleur said:
Hi, earlier, I wanted to change the rom of my mi 5s. I've got an error 7 follow by "Failed to update system image" on twrp during the flash. I tried many things: edit the installation script, format all the data, update and downgrade TWRP, lock and unlock bootlander and finally perform a fastboot flash using mi flash and the last one worked. But I am not longer able to flash a custom rom without getting error 7 after the "Patching system image unconditionally" message. I've tested lineage, pixel experience, miui, even 8.1 rom but same result. I'm stuck with fastboot global miui 10 (oreo )
Btw, I think that after the error the partition are corrupted since I can't repair them with TWRP.
I don't know what I can do more.I think that i figured out that I am able to flash system.img file using fastboot but I can't flash zip rom using recovery.
As anyone encounter this ?
Click to expand...
Click to collapse
This usually happens when a partition is missed the way that TWRP doesn´t recognice the exact model and this error 7 is a kind of protection to avoid further mistake.
Some TWRP has in-built the option to fix system issue in advanced settings or then of try to flash a system image this option could appear.
Can you upload from any of the roms the updater script that is inside?
Also sometime you did a repartition? Or flashed some GSI?
SubwayChamp said:
This usually happens when a partition is missed the way that TWRP doesn´t recognice the exact model and this error 7 is a kind of protection to avoid further mistake.
Some TWRP has in-built the option to fix system issue in advanced settings or then of try to flash a system image this option could appear.
Can you upload from any of the roms the updater script that is inside?
Also sometime you did a repartition? Or flashed some GSI?
Click to expand...
Click to collapse
Here is a script from pixel experience:
https://pastebin.com/DXgKrB8Z
I have the error "E1001: Failed to update system image" or "E2001: Failed to update vendor image" or just error 7 if I remove all the abort and assert.
I never did a repartition or flashed a GSI.
bob_bricoleur said:
Here is a script from pixel experience:
https://pastebin.com/DXgKrB8Z
I have the error "E1001: Failed to update system image" or "E2001: Failed to update vendor image" or just error 7 if I remove all the abort and assert.
I never did a repartition or flashed a GSI.
Click to expand...
Click to collapse
Just to be sure I guess you removed all the lines with getprop and not only the words.
Try first flashing persist image through fastboot.
If not flash the rom not through fastboot but using EDL mode and MiFlash tool, if you have unlocked bootloader you can send device through adb with: adb reboot edl or through fastboot with: fastboot oem edl
SubwayChamp said:
Just to be sure I guess you removed all the lines with getprop and not only the words.
Try first flashing persist image through fastboot.
If not flash the rom not through fastboot but using EDL mode and MiFlash tool, if you have unlocked bootloader you can send device through adb with: adb reboot edl or through fastboot with: fastboot oem edl
Click to expand...
Click to collapse
Yep I removed all the line
I managed to flash a full fastboot rom with mi flash and I think that during the process, a persist image was flashed. So i'm runing a stock miui. I even managed to flash Twrp and magisk. But I can't flash a rom through TWRP even after that :crying:
bob_bricoleur said:
Yep I removed all the line
I managed to flash a full fastboot rom with mi flash and I think that during the process, a persist image was flashed. So i'm runing a stock miui. I even managed to flash Twrp and magisk. But I can't flash a rom through TWRP even after that :crying:
Click to expand...
Click to collapse
Some times causes different results flashing the fastboot full image through EDL mode (download mode) instead of through fastboot mode.
It could be the issue the TWRP version if there is other available.
And you could try deleting the recovery partition with fastboot erase recovery, then boot (don´t flash yet) to recovery using fastboot boot whateveriscalled.img, then in TWRP flash the TWRP image or the installer zip, then reboot for first time to TWRP and try again.
12S Ultra unofficial TWRP - link MEGA
Credit - UnofficialTWRP
They released TWRP under 12S Pro, but the code name is Thor which stands for 12S Ultra, and after flashing, I do confirm this is for 12S Ultra.
now they have a proper 12S Ultra section!
Download the image and rename as recovery.img for simplicity.
fastboot boot recovery.img (or full file name)
in TWRP, go to "Advanced" and "flash this twrp."
edit: the recovery image file is too large to be flashed directly via fastboot, so you need to boot first then flash using twrp!
edit2: backup and restore function may not be working properly on this version of twrp! I get boot loops everytime I do a full system backup and full restore after bricking the device, especially on the data partition. Clean installing rom then restoring data only still get boot loops. so use it with caution.
I suggest you to use 3rd party backup apps to do backups on apps and data, and stick to the flashing and other functions only for twrp.
original source unofficialtwrp.com
Nabicook said:
12S Ultra unofficial TWRP - link MEGA
Credit - UnofficialTWRP
They released TWRP under 12S Pro, but the code name is Thor which stands for 12S Ultra, and after flashing, I do confirm this is for 12S Ultra.
Download the image and rename as recovery.img for simplicity.
fastboot boot recovery.img (or full file name)
in TWRP, go to Advanced and flash this twrp.
original source unofficialtwrp.com
Click to expand...
Click to collapse
Awesome thanks. But why not Fastboot flash recovery recovery.img?
No. You must type fastboot flash boot recovey. img
dungnghien said:
No. You must type fastboot flash boot recovey. img
Click to expand...
Click to collapse
No I'm pretty sure it's:
fastboot flash recovery twrp.img
However my question was why the method outlined by @Nabicook vs this method. Is it because of the dual partition?
GodKingKnight said:
Awesome thanks. But why not Fastboot flash recovery recovery.img?
Click to expand...
Click to collapse
Because not only it is the method unofficialtwrp suggested, but also the size of the recovery img file is too large to be flashed via fastboot.
I already tried
fastboot flash recovery recovery.img
fastboot flash recovery_a recovery.img
and so on, but all failed.
only way to properly install this version of twrp is to boot first then let twrp to install itself to both a/b partitions.
Hi!
I'm following your guide...and after uploading recovery nothing happens
rebooting into recovery through ADB or just using buttons...still sends me into fastboot mode
What can I do?
joiliko said:
Hi!
I'm following your guide...and after uploading recovery nothing happens
rebooting into recovery through ADB or just using buttons...still sends me into fastboot mode
What can I do?
Click to expand...
Click to collapse
are you sure you did
fastboot boot (your recovery file name).img
it should automatically boot into twrp without touching anything from fastboot mode.
then install twrp through the advanced option in twrp
Nabicook said:
are you sure you did
fastboot boot (your recovery file name).img
Click to expand...
Click to collapse
Great many thanks! I was actually doing flash boot
Nabicook said:
then install twrp through the advanced option in twrp
Click to expand...
Click to collapse
Still having issues:
After flashing twrp + magisk, reboot sends me into fastboot mode ..
As I get it, previously I've messed up with boot image, flashing recovery into that partition
So question is:
Do I need to reflash stock boot.img (need help with getting it, stock recovery rom is packed into .bin and I'm unable to extract boot image
Or can I simply reflash stock ROM (in recovery or fastboot mode?)
*my phone is unlocked already
joiliko said:
Still having issues:
After flashing twrp + magisk, reboot sends me into fastboot mode ..
As I get it, previously I've messed up with boot image, flashing recovery into that partition
So question is:
Do I need to reflash stock boot.img (need help with getting it, stock recovery rom is packed into .bin and I'm unable to extract boot image
Or can I simply reflash stock ROM (in recovery or fastboot mode?)
*my phone is unlocked already
Click to expand...
Click to collapse
yeah you can try flashing stock boot img, and if that doesnt work, you can download fastboot rom and flash stock rom using flash all without wiping data(there is .bat file that says something like install without formatting).
That will fix any kind of brick issues of xiaomi device, and you just redo the twrp part.
joiliko said:
Still having issues:
After flashing twrp + magisk, reboot sends me into fastboot mode ..
As I get it, previously I've messed up with boot image, flashing recovery into that partition
So question is:
Do I need to reflash stock boot.img (need help with getting it, stock recovery rom is packed into .bin and I'm unable to extract boot image
Or can I simply reflash stock ROM (in recovery or fastboot mode?)
*my phone is unlocked already
Click to expand...
Click to collapse
How to Extract payload.bin and get stock boot image file
To extract the payload.bin file from Android stock firmware and get stock boot image file, you should refer to the instructions given in here.
www.droidwin.com
My idea worked!
I used the method above to extract boot.img & flashed it successfully
Can someone tell me why wipe data and settings dosent work on my 12s ultra every time reboots the twrp after i press the icon... Im try at 7.5 version the same and on 7.2
You Want Video turorial ?
Cheack This Out;- https://forum.xda-developers.com/t/...stom-rom-installation-video-tutorial.4583503/
Tutorial Install Custom rom Selene
Requirements :
- Unlocked Bootloader
- PC / Laptop with working adb fastboot, SP Flash Tools
- recovery and fastboot MIUI Stock ROM ( ID, EEA, Global, CN, Taiwan / pick one that work, or your currently ROM Version )
- put your recovery miui ROM & custom rom to Microsd / OTG
How To : (If you never update OTA then go STEP 1, else go STEP 2)
- BACKUP YOUR IMEI FIRST (on twrp and backup it to another storage or cloud)
STEP 1
- boot to fastboot mode
- flash twrp / ofox command type on minimal adb fastboot "fastboot flash boot nametwrpfile.img" (make sure the twrp file on same folder at the minimal adb fastboot folder)
- press vol + & power
- Format Data
- Yes
- install / flash MIUI Recovery rom, check reflash TWRP / OFOX
- reboot to "BOOTLOADER"
After reboot to bootloader,Device will be in fastboot.
- flash vbmeta " fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img " (make sure the twrp file on same folder at the minimal adb fastboot folder)
- reboot "fastboot reboot " ( if success booting up to system go to STEP 2, if not success, read again from start )
STEP 2
- no need to setup anything, you can skip all that MIUI Setup
- reboot to twrp recovery, press vol + & power
- Format Data
-Yes
- install / flash Custom rom with check automatically reflash TWRP after flashing a ROM checked
- reboot ( If you skipped STEP 1 and not booting, back to fastboot or TWRP, then Go to STEP 1 first, if can't boot to either TWRP / Fastboot, Then you need MTK Bypass + SP Flash Tool)
- ( If you DONE STEP 1 but still no luck check SPECIAL CASE )
- DONE
SPECIAL CASE
if your phone bootloop on mi logo, then do:
- reboot to twrp/recovery, press vol + & power (wait it, be patient)
-If not boot on TWRP, Go to Fastboot
-Reflash TWRP [fastboot flash boot twrp.img]
-Now Boot in to TWRP
- install image boot.img on boot partition from miui rom you have used on first step (see above)
- reflash twrp, install image twrp.img on recovery ramdisk
- [Even if you go to TWRP Without Reflashing again,you still need to flash boot.img on boot and twrp on ramdisk]
- reboot system
- setup phone with ur mobile internet data (if the custom rom have gapps), cause ur wifi bluetooth hotspot are died
- go to twrp again, install custom kernel to fix bug wifi hotspot bluetooth (but u can't instal yukina starlight, it will make bootloop, use another I Will Recomend Yukina Stamine)
- done u can reboot system
N.B. - If You are in MIUI 13,Then it will won't Work,First Downgrade to MIUI 12.5.xx
N.B. - Just Do Normal Format,Dont Wipe like Delvik,cache,System,Vendor etc.
N.B. - Try To Take All Files(Twrp.img,boot.img,miui recovery.zip,Custom rom zip, custom kernel.zip) In your Memory card and Avoid Use OTG
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
not working in my device
fastboot flash boot twrp.img
my device went in bootloop
i have also tried
Fastboot boot twrp.img
this is throwing " status read failed (too many links)
(also tried with downgrading to MIUI-12 but no success)
Then i tried to boot into fastbootD mode.
with command "Fastboot reboot fastboot"
Now my device is in the infinite boot loop.
Please help
Is that Redmi 10 Selene ?
And Which twrp you used ?
Neelthegamer007 said:
Is that Redmi 10 Selene ?
And Which twrp you used ?
Click to expand...
Click to collapse
is its redmi 10 selene
and i have used twrp you placed here
NOOBOHOLIC said:
is its redmi 10 selene
and i have used twrp you placed here
Click to expand...
Click to collapse
Install miui 12.5.** with fastboot rom,and then unlock bootloader or if its unlocked then disable security by flashing vbmeta.img , comand on post.
Then flash TWRP
fastboot flash boot [space] drag and drop twrp.img file,after flashing reboot your device by holding power button.
Neelthegamer007 said:
Install miui 12.5.** with fastboot rom,and then unlock bootloader or if its unlocked then disable security by flashing vbmeta.img , comand on post.
Then flash TWRP
fastboot flash boot [space] drag and drop twrp.img file,after flashing reboot your device by holding power button.
Click to expand...
Click to collapse
But nothing is working now its just stucked in the bootloop
not booting into recovery
not booting into fastboot
how i do it further
You need SP flash tool, and mtk auth bypass just download it, bypass mtk auth and go to sp flash tool, on auth file section select mtk scatter file from miui fastboot rom/images folder, and on sp flash tool un select every file except boot or boot.img
And click the download button [ must be sure that you need to only download the boot.img file,no other file.]
After download,you can go fastboot
If you can't understand
Get help from YouTube.
I only want root. Is it better to install magisk from this twrp(After downgrading). Or staying in miui 13 & flashing patched boot image?
Tawsif999 said:
I only want root. Is it better to install magisk from this twrp(After downgrading). Or staying in miui 13 & flashing patched boot image?
Click to expand...
Click to collapse
If you only root,then take miui 13 rom's fastboot file and extract boot.img, patch with magisk anf flash vbmeta 1st and then patched boot.img eith adb, enough
Tawsif999 said:
I only want root. Is it better to install magisk from this twrp(After downgrading). Or staying in miui 13 & flashing patched boot image?
Click to expand...
Click to collapse
Downgrade is not nessesery with only root
Neelthegamer007 said:
If you only root,then take miui 13 rom's fastboot file and extract boot.img, patch with magisk anf flash vbmeta 1st and then patched boot.img eith adb, enough
Click to expand...
Click to collapse
Are you sure I need the fastboot rom only. Because I'm already downloading a recovery rom.
And after downloading I have to flash the vbmeta.img before flashing patched boot image? But why? vbmeta is already included in the rom. Can you please explain this.
Tawsif999 said:
Are you sure I need the fastboot rom only. Because I'm already downloading a recovery rom.
And after downloading I have to flash the vbmeta.img before flashing patched boot image? But why? vbmeta is already included in the rom. Can you please explain this.
Click to expand...
Click to collapse
You need to flash vbmeta for disabled verified boot, otherwise patched boot.img is not verified,so flashing patched boot.img will be fail or will be cause of a bootloop
And as i know on recovery rom you won't get the boot.img file,but i,m not sure if you got on recovery rom then it's also file,i will work,and i,m 100 % sure, and vbmeta is inside the rom for enable verified boot,but you need to disable it to flash patched boot img file,its necessary for most of the devices,but in some device, its not necessary,but why would you take risk of a unwanted bootloop?
Disable vbmeta command
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
Any other query's ?, just reply....
Neelthegamer007 said:
You need to flash vbmeta for disabled verified boot, otherwise patched boot.img is not verified,so flashing patched boot.img will be fail or will be cause of a bootloop
And as i know on recovery rom you won't get the boot.img file,but i,m not sure if you got on recovery rom then it's also file,i will work,and i,m 100 % sure, and vbmeta is inside the rom for enable verified boot,but you need to disable it to flash patched boot img file,its necessary for most of the devices,but in some device, its not necessary,but why would you take risk of a unwanted bootloop?
Disable vbmeta command
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
Any other query's ?, just reply....
Click to expand...
Click to collapse
Thank you very much. I thought I have to flash using fastboot flash vbmeta vbmeta.img. But now I can understand, the command is not for flashing. It's for disabling verification.
Tawsif999 said:
You are most welcome
Click to expand...
Click to collapse
can you tell me more for install custom rom i try 5days and 50time bootloop please help
Teaykhuad said:
can you tell me more for install custom rom i try 5days and 50time bootloop please help
Click to expand...
Click to collapse
Sure,are you active right now ? Reply again,i eill give you my telegram..
yes i trying to booting now i dm you
Teaykhuad said:
yes i trying to booting now i dm you
Click to expand...
Click to collapse
How's your experience?
Neelthegamer007 said:
How's your experience?
Click to expand...
Click to collapse
Good bro You teach me to flash custom rom and pixel expirence is not bad but im go to miui and install https://forum.xda-developers.com/t/ultra-rooted-miui-package.4487967/ this for speed and fast animation
Neelthegamer007 said:
Tutorial Install Custom rom Selene
Requirements :
- Unlocked Bootloader
- PC / Laptop with working adb fastboot, SP Flash Tools
- recovery and fastboot MIUI Stock ROM ( ID, EEA, Global, CN, Taiwan / pick one that work, or your currently ROM Version )
- put your recovery miui ROM & custom rom to Microsd / OTG
How To : (If you never update OTA then go STEP 1, else go STEP 2)
- BACKUP YOUR IMEI FIRST (on twrp and backup it to another storage or cloud)
STEP 1
- boot to fastboot mode
- flash twrp / ofox command type on minimal adb fastboot "fastboot flash boot nametwrpfile.img" (make sure the twrp file on same folder at the minimal adb fastboot folder)
- press vol + & power
- Format Data
- Yes
- install / flash MIUI Recovery rom, check reflash TWRP / OFOX
- reboot to "BOOTLOADER"
After reboot to bootloader,Device will be in fastboot.
- flash vbmeta " fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img " (make sure the twrp file on same folder at the minimal adb fastboot folder)
- reboot "fastboot reboot " ( if success booting up to system go to STEP 2, if not success, read again from start )
STEP 2
- no need to setup anything, you can skip all that MIUI Setup
- reboot to twrp recovery, press vol + & power
- Format Data
-Yes
- install / flash Custom rom with check automatically reflash TWRP after flashing a ROM checked
- reboot ( If you skipped STEP 1 and not booting, back to fastboot or TWRP, then Go to STEP 1 first, if can't boot to either TWRP / Fastboot, Then you need MTK Bypass + SP Flash Tool)
- ( If you DONE STEP 1 but still no luck check SPECIAL CASE )
- DONE
SPECIAL CASE
if your phone bootloop on mi logo, then do:
- reboot to twrp/recovery, press vol + & power (wait it, be patient)
-If not boot on TWRP, Go to Fastboot
-Reflash TWRP [fastboot flash boot twrp.img]
-Now Boot in to TWRP
- install image boot.img on boot partition from miui rom you have used on first step (see above)
- reflash twrp, install image twrp.img on recovery ramdisk
- [Even if you go to TWRP Without Reflashing again,you still need to flash boot.img on boot and twrp on ramdisk]
- reboot system
- setup phone with ur mobile internet data (if the custom rom have gapps), cause ur wifi bluetooth hotspot are died
- go to twrp again, install custom kernel to fix bug wifi hotspot bluetooth (but u can't instal yukina starlight, it will make bootloop, use another I Will Recomend Yukina Stamine)
- done u can reboot system
N.B. - If You are in MIUI 13,Then it will won't Work,First Downgrade to MIUI 12.5.xx
N.B. - Just Do Normal Format,Dont Wipe like Delvik,cache,System,Vendor etc.
N.B. - Try To Take All Files(Twrp.img,boot.img,miui recovery.zip,Custom rom zip, custom kernel.zip) In your Memory card and Avoid Use OTG
View attachment 5793645
Click to expand...
Click to collapse
How do I restore WiFi and Bluetooth after flashing
So, I upgraded from MIUI 13 Stable to MIUI 14 Weekly today (clean flash via fastboot). What I hadn't realized is that my TWRP was still on A12, so TWRP couldn't read internal storage.
But when I tried to flash the A13 TWRP via Fastboot, I get this error:
Code:
Warning: skip copying recovery image avb footer (recovery partition size: 104857600, recovery image size: 201326592).
Sending 'recovery' (196608 KB) OKAY [ 6.370s]
Writing 'recovery' FAILED (remote: 'Error flashing partition : Volume Full')
fastboot: error: Command failed
So, somehow, my recovery partition is way too small (or it is just full? But I already erased the old TWRP, so currently I have no recovery)
And the only way I can boot into TWRP is to use the fastboot boot command to temporarily boot into it.
Is there a way to deal with this without doing a wipe?
EDIT: My dumbass was trying to flash the Boot version of TWRP instead of the Rec version
TWRP
BOOT VERSION
Installation:
Phone in fastboot mode
Cmd:
fastboot boot twrp.img
Power shell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP.
NOSS8 said:
TWRP
BOOT VERSION
Installation:
Phone in fastboot mode
Cmd:
fastboot boot twrp.img
Power shell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP.
Click to expand...
Click to collapse
Thanks for the reply, but I don't think the issue is related to fastboot since I can't flash the image in TWRP either.
wizpizz said:
Thanks for the reply, but I don't think the issue is related to fastboot since I can't flash the image in TWRP either.
Click to expand...
Click to collapse
Which img?
NOSS8 said:
Which img?
Click to expand...
Click to collapse
skkk's A13 TWRP image
wizpizz said:
skkk's A13 TWRP image
Click to expand...
Click to collapse
Btw the error message I get after trying to 'flash current TWRP' is this:
Code:
cd /tmp/abrec/ && /system//bin/magiskboot repack -n /dev/block/bootdevice/by-name/recovey_a /tmp/abrec/rec_a.img process ended with ERROR: 1
Error repacking image.
wizpizz said:
Thanks for the reply, but I don't think the issue is related to fastboot since I can't flash the image in TWRP either.
Click to expand...
Click to collapse
And if I try to flash it via 'Install', I get:
Code:
size of image larger than target device
wizpizz said:
skkk's A13 TWRP image
Click to expand...
Click to collapse
Installing Twrp and rooting are two different things.
No need for Twrp to root.
Is it weekly stock rom or Xiaomi Eu rom?
NOSS8 said:
Installing Twrp and rooting are two different things.
No need for Twrp to root.
Is it weekly stock rom or Xiaomi Eu rom?
Click to expand...
Click to collapse
I am such a moron lmao. I was trying to flash the Boot version of TWRP instead of the Rec version... Just flashed the Rec version and it works now. You made me check back on the TWRP thread, so thanks I guess ahah
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?