So I've been flashing custom roms on this device for more than 1 week.
Its only now that when The rom finished flashing I get "failed command not read"
or something like that when the adb sideload goes to 47% And When I reboot to system
after formatting data it automatically boots into the bootloader.
any help please?
MaybeDontAsk said:
So I've been flashing custom roms on this device for more than 1 week.
Its only now that when The rom finished flashing I get "failed command not read"
or something like that when the adb sideload goes to 47% And When I reboot to system
after formatting data it automatically boots into the bootloader.
any help please?
Click to expand...
Click to collapse
Any ROM you sideload will have the 47% error, afaik. If you phone says step 1 and step 2, then it it successful. You can ignore that error. If your phone boots to the bootloader then the ROM is not good or you did something wrong when flashing. Make sure you have the latest OOS firmware on both slots before flashing a ROM.
I would suggest OOS 11 then flash ROM
I am pretty sure my b partition is corrupted, even flashing oos 11 doesn't help, adb sideload won't work on neither A or B partition like it used to, flash payload.bin from rom zip only works in the A partition cuz if I flash it in the B partition it will keep rebooting to fastboot, any help please?
MaybeDontAsk said:
I am pretty sure my b partition is corrupted, even flashing oos 11 doesn't help, adb sideload won't work on neither A or B partition like it used to, flash payload.bin from rom zip only works in the A partition cuz if I flash it in the B partition it will keep rebooting to fastboot, any help please?
Click to expand...
Click to collapse
I would just use MSM tool at this point, or search the thread here to restore using fastboot. Wiping partitions may help you to fastboot flash the imgs
azoller1 said:
I would just use MSM tool at this point, or search the thread here to restore using fastboot. Wiping partitions may help you to fastboot flash the imgs
Click to expand...
Click to collapse
That doesn't work, I've tried it a a lot. I am just using the fastboot enhanced to flash them with the payload.bin now
Related
Hello guys I need some help. I'm stuck in fastboot mode with no recovery or OS too l, let me retrace my steps.
I had my px3 rooted on stock but I was bored with stock and tried to flash bootleggers rom and followed instructions to wipe "everything" but internal storage, so I did including storage under internal storage and flashed the ROM and twrp with it. After it just rebooted back to recovery every time I tried normal boot. (I'm assuming I F'd up by wiping storage). So I googled what to do about looping recovery and one suggestion was to factory reset so I did; I can no longer access recovery. I've tried flashing factory image, flashing the twrp zip, trying to boot straight to twrp, I can't get to adb sideload and it says "no valid slot to boot" on fastboot screen any suggestions?
Got another on fastboot, "error booting boot.img"
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
fury683 said:
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
Click to expand...
Click to collapse
Yes it does and I've got everything from twrp .zip and .IMG, factory images and ota zip.
I did make progress just now and switched to slot B and got TWRP to show up:laugh: might just sideload OTA and pretend this never happened
Update, adb sideload taking too long to start
wergrun said:
Yes it does and I've got everything from twrp .zip and .IMG, factory images and ota zip.
I did make progress just now and switched to slot B and got TWRP to show up:laugh: might just sideload OTA and pretend this never happened
Update, adb sideload taking too long to start
Click to expand...
Click to collapse
You need to get back to fastboot, and run the flash all bat file from the full factory image.
TonikJDK said:
You need to get back to fastboot, and run the flash all bat file from the full factory image.
Click to expand...
Click to collapse
I tried that but I keeps giving me an error, I'll post it when I get the chance
Problem SOLVED! used video by MaowDroid "Pixel 2 (XL): Un-root and return to stock using factory images"
fury683 said:
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
Click to expand...
Click to collapse
I have the same issue, except my computer will not recognize the device in fastboot. I tried two different computers, Windows 10 and laptop running Linux.
wergrun said:
Problem SOLVED! used video by MaowDroid "Pixel 2 (XL): Un-root and return to stock using factory images"
Click to expand...
Click to collapse
Followed the video, but I get an error:
'FAILED (remote: Failed to write to partition Not Found)'
I've tried: bootloader, bootloader_a, bootloader_b and bootloader_other and get the same error.
I'm stuck....
SS823 said:
Followed the video, but I get an error:
'FAILED (remote: Failed to write to partition Not Found)'
I've tried: bootloader, bootloader_a, bootloader_b and bootloader_other and get the same error.
I'm stuck....
Click to expand...
Click to collapse
I did get that too but it was because I forgot to put a space after "bootloader_a ", are you Stuck at around the 9 minute steps?
Yes, right around the end at 9 minutes. Everything works fine - bootloader, radio, etc. When I get to the end of the img zip file I get this message:
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.360s
I am at a loss.
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.
[Deleted]
The flashing instruction makes no sense to me
Spookybear said:
INSTALLATION:
0. Backup your ROM, your data, your internal storage, and your settings/apps, to an external device
1. Reboot to your custom TWRP-based Recovery
2. The device will automatically reboot into OrangeFox recovery after installation (allow this to happen)
3. Enjoy!
(Note: There is no zip file because this recovery is too big to fit in the ramdisk.
Click to expand...
Click to collapse
Can you please clarify this?
I assume install .IMG to Ramdisk? It will likely come up, so just want to cover all bases.
gorilla p said:
Can you please clarify this?
I assume install .IMG to Ramdisk? It will likely come up, so just want to cover all bases.
Click to expand...
Click to collapse
I tried that...no dice...
Flash to both _a and _b using trwp but recovery does not boot... so back to trwp til some future info...
I flashed via TWRP, via flash .img to ramdisk, rebooted to recovery and nothing.
Stuck at "Bootloader unlocked" screen
Tried to boot via fastboot and it failed.
Was this recovery tested on the OP7 Pro? If so, what ROM was being used and what was the flashing process?
Gungrave223 said:
The flashing instruction makes no sense to me
Click to expand...
Click to collapse
Sorry, fixed the instructions.
avid_droid said:
Yeah directions are honestly the worst I've seen on XDA yet.
Click to expand...
Click to collapse
Sorry, fixed the instructions.
I have a feeling these new instructions aren't going to work either, considering we don't have a recovery partition.
Spookybear said:
Sorry, fixed the instructions.
Click to expand...
Click to collapse
still no dice
HTML:
Writing 'recovery'
FAILED (remote: '(recovery_a)
No such partition'
I guess the command should be
fastboot boot /path to recovery
But again this wont flash recovery permanently AFAIK, everytime we need to boot into recovery we have to flash it via fastboot
insaneparnoid said:
I guess the command should be
fastboot boot /path to recovery
But again this wont flash recovery permanently AFAIK, everytime we need to boot into recovery we have to flash it via fastboot
Click to expand...
Click to collapse
He updated it with fastboot flash, indicating that this is to be installed, however it doesn't appear to work at all at this point.
For me is working , latest OOS beta. Just had to disable vbmeta in order to boot.
we need a flashble zip for this.
is OTG working with OrangeFox ?
otakutw said:
we need a flashble zip for this.
Click to expand...
Click to collapse
Not exactly, try - fastboot flash recovery *drag the image into the cmd then press enter*
Can this recovery be decreased in size so that it can be flashed to the ramdisk?
EDIT: It seems twrp is even bigger than this. Twrp img is 30.7mb while this is 29.4mb. Twrp does flash to the ramdisk. If this could be permanently flashed, it would be perfect. If the size needs to be decreased, certain graphics could be moved to the internal storage to save space on the ramdisk.
Hahaha wow what are you doing here it's like you didn't even test this at all. I'm tried to flash the installer in twrp and it tells me that this recovery is only for guacamole not OnePlus 7 pro. So it does not support custom roms clearly cause I'm on bliss
shadowikr said:
Not exactly, try - fastboot flash recovery *drag the image into the cmd then press enter*
Click to expand...
Click to collapse
There is no recovery partition on modern Android devices. The boot.img ramdisk contains the recovery
My current Oneplus 6 is wiped. So no OS, but I am able to start fastboot or boot into recovery (twrp-3.3.1-2-enchilada). But I am not able to install OxygenOs, downloaded from the OnePlus website. Everytime I get the following message:
Code:
Installing zip file '/sdcard/OnePlus6Oxygen_22_OTA_045_all_2004142201_bdd6fdc6b6b1477f.zip'
Checking for Digest file...
Step 1/2
Error applying update: 7 (ErrorCode::
kInstallDeviceOpenError)
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/OnePlus6Oxygen_22_OTA_045_all_2004142201_bdd6fdc6b6b1477f.zip'
Updating partition details...
...done
Sideload failed as well, obviously, so I tried updating TWRP to version twrp-3.4.0-2-enchilada (see if that helps). But after flashing 3.4.0-2 to boot_b using the command `fastboot flash boot twrp-3.4.0-2-enchilada.img`, I am not able to boot into recovery anymore. Everytime I try to restore TWRP by running `fastboot flash boot twrp-3.3.1-2-enchilada.img` I am able to boot into recovery again, but I am not able to successfully upgrade TWRP or installing the Oxygen OS.
Any thoughts? I read so many articles with the same issue on XDA and Stackoverflow, but I tried almost everything without any luck, yet.
You should try msm tool for restore to stock oos
t0w3rh0u53 said:
My current Oneplus 6 is wiped. So no OS, but I am able to start fastboot or boot into recovery (twrp-3.3.1-2-enchilada). But I am not able to install OxygenOs, downloaded from the OnePlus website. Everytime I get the following message:
Sideload failed as well, obviously, so I tried updating TWRP to version twrp-3.4.0-2-enchilada (see if that helps). But after flashing 3.4.0-2 to boot_b using the command `fastboot flash boot twrp-3.4.0-2-enchilada.img`, I am not able to boot into recovery anymore. Everytime I try to restore TWRP by running `fastboot flash boot twrp-3.3.1-2-enchilada.img` I am able to boot into recovery again, but I am not able to successfully upgrade TWRP or installing the Oxygen OS.
Any thoughts? I read so many articles with the same issue on XDA and Stackoverflow, but I tried almost everything without any luck, yet.
Click to expand...
Click to collapse
Oneplus update files are not "flashable" and often do not contain a full os. They are meant to be interpreted by the updater app. I would recommend flashable zips made from official files
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Read instructions carefully, do not skip android versions.
gmfrvr said:
You should try msm tool for restore to stock oos
Click to expand...
Click to collapse
Thanks! The msm download tool did the trick!
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