Database Info

[DAISY][OFFICIAL][FASTBOOT] v10.0.2.0.PDLMIFJ

V10.0.2.0.PDLMIFJ Pie Official Release by Xiaomi: Mod edit link removed.
GUIDE:
1. Make a backup.
2. Unlock Bootloader.
3. Enter in fastboot mode or EDL.
4. Use MiFlash.

Whats the reason for not using MiFlash?

And especially why relock the bootloader with the script, if anything goes wrong your device could be bricked!?

downloadonlyaccount said:
Whats the reason for not using MiFlash?
Click to expand...
Click to collapse
The packaging hierarchy is slightly different from that of an official because this is a repackaged that a user has made of 4PDA.
You can try if you think MiFlash will work. I only tested this via Flash.bat script on fastboot mode.

Working perfectly
in my use, these problems have been solved:
•SIM Card Issue, Solved
•No Disturb on camera, Solved
•Wi-Fi bug, Solved
I'm still analyzing the update..

Patched boot for this ROM https://drive.google.com/file/d/1dBX2dZV_wWgSip8d9lk0lrO_JHfxGdKU/view?usp=drivesdk

seryioo said:
4. Run "Flash.bat" (It will erase all your data and relock bootloader)
*If you don't want to relock bootloader, remove "fastboot oem lock" from "Flash.bat" and save.
Click to expand...
Click to collapse
Just a short question, will data be kept when not executing the OEM relock?
edit: Ok, i found out the the line "fastboot -w" will erase the user data. Anyone tried without this one?

downloadonlyaccount said:
Just a short question, will data be kept when not executing the OEM relock?
edit: Ok, i found out the the line "fastboot -w" will erase the user data. Anyone tried without this one?
Click to expand...
Click to collapse
Yes, just remove the two lines from flash.bat. Worked without problems here.

davze said:
Yes, just remove the two lines from flash.bat. Worked without problems here.
Click to expand...
Click to collapse
I can confirm, worked well for me too.

Official OTA is out everywhere

Just for beta team...
CarlosAG10 said:
Official OTA is out everywhere
Click to expand...
Click to collapse

ada12 said:
Just for beta team...
Click to expand...
Click to collapse
Nope, for everyone

ok thanks for info , this info is not available in forum mi
CarlosAG10 said:
Nope, for everyone
Click to expand...
Click to collapse

ada12 said:
ok thanks for info , this info is not available in forum mi
Click to expand...
Click to collapse
It is now

yes thanks I wait ota ...
CarlosAG10 said:
It is now
Click to expand...
Click to collapse

seryioo said:
4. Run "Flash.bat" (It will erase all your data and relock bootloader)
Click to expand...
Click to collapse
It is not necessary to delete data and reset the system!
You can upgrade to the newer version.
If you use Mi Flash Tool, select: flash_all_except_storage.bat
Or manually via fastboot:
Code:
adb reboot bootloader
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash modem modem.img
fastboot flash rpm rpm.img
fastboot flash tz tz.img
fastboot flash keymaster keymaster.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cmnlib cmnlib.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash mdtp mdtp.img
fastboot flash aboot aboot.img
fastboot flash sbl1 sbl1.img
[COLOR="DarkOrange"]fastboot boot patched_boot.img[/COLOR]
Open Magisk -> Install -> direct

Very nice! Thank you bro!
Worked without locking the bootloader

Mattania said:
Patched boot for this ROM https://drive.google.com/file/d/1dBX2dZV_wWgSip8d9lk0lrO_JHfxGdKU/view?usp=drivesdk
Click to expand...
Click to collapse
Thanks It's working.

********

CarlosAG10 said:
Official OTA is out everywhere
Click to expand...
Click to collapse
Downloading now
Cheers

Can't flash stock boot image

I am stuck in fastboot. The bootloader is unlocked and I do not have twrp. Everytime I try to install twrp I get this message "FAILED (remote: Failed to load/authenticate boot image: Load Error)" I think it is because my boot image is not there.
When I try to install factory boot image (fastboot flash boot.img) I get this message:
PS C:\platform-tools> fastboot flash C:\Users\Admin\Downloads\boot_stock.img
unknown partition 'C:\Users\Admin\Downloads\boot_stock.img'
error: cannot determine image filename for 'C:\Users\Admin\Downloads\boot_stock.img'
HELP PLEASE

fastboot flash boot boot.img
u missed the boot partition

Bradl79 said:
fastboot flash boot boot.img
u missed the boot partition
Click to expand...
Click to collapse
Just tried and it looks to have flashed, but I am still stuck in bootloader/fastboot menu
here is the output:
PS C:\platform-tools> fastboot devices
efba8ca6 fastboot
PS C:\platform-tools> fastboot flash boot C:\Users\Admin\Downloads\boot_stock.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.118s]
writing 'boot'...
OKAY [ 0.393s]
finished. total time: 2.520s

did you flash the correct boot.img for the correct phone model and os version?
you may just want to flash the fastboot rom

Bradl79 said:
did you flash the correct boot.img for the correct phone model and os version?
you may just want to flash the fastboot rom
Click to expand...
Click to collapse
Thank you! That fixed my problem. I flashed 10.0.1-GM21BA-OnePlus7ProOxygen_21.E.21_OTA_021_all_1910071445_8d6a-FASTBOOT

Now I'm back to stock and not rooted. Good thing I backed up my software before flashing.
What's the easiest way to gain root access again? Which specific files do I need?
My phone is GM1917 on Android 10 Oxygen OS 10.01.GM21BA

champstar said:
Now I'm back to stock and not rooted.
Click to expand...
Click to collapse
That is what flashing a stock boot.img does. What were you trying to accomplish by flashing stock boot.img?
champstar said:
Now I'm back to stock and not rooted.
What's the easiest way to gain root access again? Which specific files do I need?
Click to expand...
Click to collapse
Fastboot boot TWRP, then flash Magisk zip.
Use TWRP unofficial version -70 if you are on Android Q.

redpoint73 said:
That is what flashing a stock boot.img does. What were you trying to accomplish by flashing stock boot.img?
Fastboot boot TWRP, then flash Magisk zip.
Use TWRP unofficial version -70 if you are on Android Q.
Click to expand...
Click to collapse
Thank you! I am now rooted again. There's so much information available online, it is hard to nail down exactly what to do once something messes up.

Now my wifi is not working. I flashed the stock boot image so my kernel should be back to stock right?
I am on TWRP 3.3.1-70 and Magisk is up to date.

champstar said:
Now my wifi is not working. I flashed the stock boot image so my kernel should be back to stock right?
I am on TWRP 3.3.1-70 and Magisk is up to date.
Click to expand...
Click to collapse
Broken wifi probably means you flashed the wrong stock boot.img.

redpoint73 said:
Broken wifi probably means you flashed the wrong stock boot.img.
Click to expand...
Click to collapse
That did the trick, I flashed modded magisk for OS 10 and now wifi is working.

How to go back from custom rom to factory

files are from current available factory image available. be sure to use latest available fastboot application.
1. reboot to fastboot
2. fastboot erase userdata (all data is deleted, have a backup)
3. fastboot reboot-bootloader
4. fastboot flash bootloader bootloader-sunfish-s5-0.2-6539975.img
5. fastboot reboot-bootloader
6. fastboot flash radio radio-sunfish-g7150-00018-200701-b-6643937.img
7. fastboot reboot-bootloader
8. fastboot update image-sunfish-rp1a.201005.006.zip
9. fastboot reboot-bootloader
10. choose recovery
11. on the android icon with the red warning shield hold power and press volume up
12. Stock recovery appears. Choose wipe data / factory reset
if in any case the fastboot command gets stuck, replug the device and/or restart bootloader. BE CAREFULL WHEN DOING THIS WHILE RUNNING fastboot flash bootloader !!!!BRICK POSSIBLE!!!!!
After that you can boot up and see its working.
if everything is right, you should flash both slots before
relocking bootloader
so repeat above steps and do point 4. and 6. fastboot flash with
fastboot flash --slot all
from above steps. Check phone boots on both slots. Active slot can be switched via
fastboot --set-active=a
verify it boots then
fastboot --set-active=b
verify again it boots
then proceed with
fastboot flashing lock
(data will be wiped)

If you're doing it this way you should flash the images to both slots.
Fastboot flash bootloader --slot all (image)
Reboot bootloader
Fastboot flash radio --slot all (image)
Reboot bootloader
Then
Fastboot update (extracted sunfish folder)
Let it do its thing.
Incase there's any doubt on both slots being stock you can just adb sideload the OTA after you boot

Edmontonchef said:
If you're doing it this way you should flash the images to both slots.
Fastboot flash bootloader --slot all (image)
Reboot bootloader
Fastboot flash radio --slot all (image)
Reboot bootloader
Then
Fastboot update (extracted taimen folder)
Let it do its thing.
Incase there's any doubt on both slots being stock you can just adb sideload the OTA after you boot
Click to expand...
Click to collapse
indeed that is correct , ill add this to the post though in case something goes wrong i normally only affect active slot to reduce brick possibility

Is it safe to downgrade from 11 to 10 this way?

forty-second said:
Is it safe to downgrade from 11 to 10 this way?
Click to expand...
Click to collapse
Yes, just keep in mind whenever rolling back asb or android versions you'll have to format data.

You can do this in a more simple way by flash the stock image via official website from android, just click and follow the instruction

forty-second said:
Is it safe to downgrade from 11 to 10 this way?
Click to expand...
Click to collapse
from stock to stock its easier

I9602283 said:
You can do this in a more simple way by flash the stock image via official website from android, just click and follow the instruction
Click to expand...
Click to collapse
if that would be the case i would not have written this guide

It'll be nice when we have a working TWRP, then you can format data and flash/sideload an OTA if needed.

Edmontonchef said:
It'll be nice when we have a working TWRP, then you can format data and flash/sideload an OTA if needed.
Click to expand...
Click to collapse
Seems unlikely; lots of challenges getting custom recoveries working w/A11+

guide
r0tt0r said:
if that would be the case i would not have written this guide
Click to expand...
Click to collapse
Did you ever look at factory packs? It has flash_all scripts for Linux and Windows and its do all steps as needed.
Or I'm wrong?

boomo15 said:
Did you ever look at factory packs? It has flash_all scripts for Linux and Windows and its do all steps as needed.
Or I'm wrong?
Click to expand...
Click to collapse
go and unlock ur phone, flash superiorOS fe. (that was the one i was on) then go back to stock.
tell me if it was all so easy. this guide is meant if you run into issues like i did and i wanted to not have you struggle through the same.
if you think running "bat" without seeing any output of what is happening and sit for an hour without anything has happened at all cause fastboot is stuck, then do so and skip this thread.

Edmontonchef said:
If you're doing it this way you should flash the images to both slots.
Fastboot flash bootloader --slot all (image)
Reboot bootloader
Fastboot flash radio --slot all (image)
Reboot bootloader
Then
Fastboot update (extracted taimen folder)
Let it do its thing.
Incase there's any doubt on both slots being stock you can just adb sideload the OTA after you boot
Click to expand...
Click to collapse
Im confused when you mentioned "Fastboot update (extracted taimen folder)" taimen?
thanks is advance

mauri311 said:
Im confused when you mentioned "Fastboot update (extracted taimen folder)" taimen?
thanks is advance
Click to expand...
Click to collapse
Sorry I meant sunfish (brainfart)
When you extract the factory image a second folder will show up. It'll say image.sunfish.
You can type in the terminal ( fastboot update ) then drag and drop that folder. Works the same way as flash-all. Just update bootloader and radio first.

Not enough space
Hello,
I end at point 8:
error: failed to load 'image-sunfish-rp1a.201005.006.zip': Not enough space
How can I fix the problem ?

foxxof said:
Hello,
I end at point 8:
error: failed to load 'image-sunfish-rp1a.201005.006.zip': Not enough space
How can I fix the problem ?
Click to expand...
Click to collapse
it should be fixable by
fastboot erase system_a
or
fastboot erase system_b
depending on your current active slot.

r0tt0r said:
it should be fixable by
fastboot erase system_a
or
fastboot erase system_b
depending on your current active slot.
Click to expand...
Click to collapse
fastboot erase system_a
output :
erasing 'system_a' . . .
FAILED (remote: Partition should be erased in fastbootd)
finished. total time: 0.138s
fastboot erase system_b
output :
erasing 'system_b' . . .
FAILED (remote: Partition should be erased in fastbootd)
finished. total time: 0.147s
:crying:
i downloaded the latest sdk. (r30.0.5 not 30.0.4)
now it works!

foxxof said:
fastboot erase system_a
output :
erasing 'system_a' . . .
FAILED (remote: Partition should be erased in fastbootd)
finished. total time: 0.138s
fastboot erase system_b
output :
erasing 'system_b' . . .
FAILED (remote: Partition should be erased in fastbootd)
finished. total time: 0.147s
:crying:
i downloaded the latest sdk. (r30.0.5 not 30.0.4)
now it works!
Click to expand...
Click to collapse
btw the message partition should be erased in fastbootd is as far i know the recovery fastboot not the one coming at first (boot recovery, at little android press power+vol)

Partition should be erased in fastbootd
foxxof said:
fastboot erase system_a
output :
erasing 'system_a' . . .
FAILED (remote: Partition should be erased in fastbootd)
finished. total time: 0.138s
fastboot erase system_b
output :
erasing 'system_b' . . .
FAILED (remote: Partition should be erased in fastbootd)
finished. total time: 0.147s
Click to expand...
Click to collapse
adb reboot bootloader
fastboot reboot fastboot
fastboot erase system_a or system_b
---------- Post added at 02:45 PM ---------- Previous post was at 02:16 PM ----------
r0tt0r said:
go and unlock ur phone, flash superiorOS fe. (that was the one i was on) then go back to stock.
tell me if it was all so easy. this guide is meant if you run into issues like i did and i wanted to not have you struggle through the same.
if you think running "bat" without seeing any output of what is happening and sit for an hour without anything has happened at all cause fastboot is stuck, then do so and skip this thread.
Click to expand...
Click to collapse
Way! Why so much emotions over simple suggestion? You where unlucky and give people a guide in case which is replicate all commands from scripts. Good!
And for record my experience with this device in short!
Received – setup – Android 11 – OTA to 006 – Canary – root – boot – check all stuff – install my apps – check again – pm list for bloatware
flash superiorOS – make notes not working stuff – root – check again – same not working stuff
flash factory android 10 with flash_all – boot – check
flash CalyxOS – check – root – worked – back to stock with flash all Android 10 – check – all good
flash RR – check – root – buggy for me
flash Android 11 with flash_all – flash GrapheOS -- root -- some apps not working
flash SuperiorOS – root – flashed blu-spark kernel – remove unneeded stuff – restore backup – same bugs
flash factory – root – blu-spark – debloat – working on stock now.
All time I used flash-all and no any problems. And thank you for your suggestion to skip this tread!:good:

Awesome guide - Thank you!
FYI - To lock the bootloder, I had to use " fastboot flashing lock "

Question [SOLVED][HELP][FIRMWARE][FASTBOOT]

what to do if I executed fastboot erase boot erase cpucp erase dtbo erase modem erase oplusstanvbk erase oplus_sec erase shrm erase splash erase qweslicstore erase vbmeta_vendor erase vbmeta_system erase vendor_boot erase vm-bootsys?
I can't run Fastboot, I pushing power button/ other etc, but screen is black
SOLUTION: I took the msm for One plus 9 pro EU and flashed using lite firehose, and then installed the firmware for Oneplus 9 via local update

MURSHIG said:
what to do if I executed fastboot erase boot erase cpucp erase dtbo erase modem erase oplusstanvbk erase oplus_sec erase shrm erase splash erase qweslicstore erase vbmeta_vendor erase vbmeta_system erase vendor_boot erase vm-bootsys?
I can't run Fastboot, I pushing power button/ other etc, but screen is black
Click to expand...
Click to collapse
What would make you wanna run these commands.? I don't know what to tell you ,download msm tool and hope you can get into edl mode. Then I'd leave my device alone if I were you. https://onepluscommunityserver.com/list/Unbrick_Tools/

mattie_49 said:
What would make you wanna run these commands.? I don't know what to tell you ,download msm tool and hope you can get into edl mode. Then I'd leave my device alone if I were you. https://onepluscommunityserver.com/list/Unbrick_Tools/
Click to expand...
Click to collapse
I was flashing rom by Fastboot and before flashing I was would erase partitions I will flash

I have Mac PC, but I can use linux or mac
MURSHIG said:
I was flashing rom by Fastboot and before flashing I was would erase partitions I will flash
Click to expand...
Click to collapse

MURSHIG said:
I have Mac PC, but I can use linux or mac
Click to expand...
Click to collapse
You've probably done ireversible damage to device . Factory reset does the same

mattie_49 said:
You've probably done ireversible damage to device . Factory reset does the same
Click to expand...
Click to collapse
my device automatically run Qualcomm EDL and I see it when plugging it to windows PC, but I can't flash it with MSM cause error no valid TRG ID

when I installed global firmware it says image not mismatch device, when I flashing t-mobile it saying no valid tag id

can I flash it with QFIL and lineage-os rom zip?And I want TWRP

have u telegram?
mattie_49 said:
You've probably done ireversible damage to device . Factory reset does the same
Click to expand...
Click to collapse

will it https://forum.xda-developers.com/t/...a-sahara-connection-error-check-this.4308601/ work for me?

I took the msm for One plus 9 pro EU and flashed using lite firehose, and then installed the firmware for Oneplus 9 via local update

MURSHIG said:
I took the msm for One plus 9 pro EU and flashed using lite firehose, and then installed the firmware for Oneplus 9 via local update
Click to expand...
Click to collapse
Good deal

mattie_49 said:
Good deal
Click to expand...
Click to collapse
I'd def take an ota update ota if available to cover back the eu firmware on both slots.

Not a local update, just flash stock rom via extracting payload.bin files and flashing via fastboot them

Question [RESOLVED] Cannot flash recovery - Partition/Volume full

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