Develop Bugs

[SOLVED]fastboot with linux: Arc device not detected

Hello,
I wanted to update one SE Arc Experia already running cm7, but with a few months old Rom.
fastboot is not detecting my device, and I have no ideas why. After a few hours of search, I am still unable to fastboot it.
Arc is running fine with cm7.2.0 with FXP Kernel, debug is ON.
I am on Ubuntu 11.10, and everything is correctly set up. I already flashed Rom & Kernel in the past. The file 51-android.rules is in /etc/udev/rules.d.
Code:
#SE Arc Xperia
SUBSYSTEMS==”usb”, ATTRS{idVendor}==”0fce″, ATTRS{idProduct}==”014f″, OWNER:="gabx", GROUP:="plugdev", MODE=”0666″
the usb is working :
Code:
[email protected]:~/Xperia/xperia$ lsusb
Bus 001 Device 005: ID 0fce:0dde Sony Ericsson Mobile Communications AB
fastboot executable is in my box, with correct permission. The fastboot command works.
The phone is correctly in download mode, with the blue led (turn off, press menu, plug USB).
When I fastboot devices, I have no entry :
Code:
[email protected]:~/Xperia/xperia$ fastboot devices
[email protected]:~/Xperia/xperia$
Weird, the -i 0x0fce option doesn't seems correct:
Code:
[email protected]:~/Xperia/xperia$ fastboot -i 0x0fce devices
usage: fastboot [ <option> ] <command>
.../.... list here of all otions and command
Sudoing doesn't change anything.
Code:
[email protected]:~/Xperia/xperia$ fastboot reboot
< waiting for device >
The device is not detected. Why ??
TY for any help
EDIT
As I couldn't fastboot my device, I placed the boot.img from cm7 update on my sdcard. then from terminal emulator on my device:
Code:
flash_image boot /sdcard/boot.img
Then reboot in recovery, but now black screen, can't boot at all!!

gabx said:
The device is not detected. Why ??
TY for any help
Click to expand...
Click to collapse
Funny how I lost a whole day investigating the same issue Answer: invalid fastboot binary. Use this one
gabx said:
As I couldn't fastboot my device, I placed the boot.img from cm7 update on my sdcard. then from terminal emulator on my device:
Code:
flash_image boot /sdcard/boot.img
Then reboot in recovery, but now black screen, can't boot at all!!
Click to expand...
Click to collapse
Don't use flash_image, it doesn't work with Xperias
Cheers,
z

zdzihu said:
Funny how I lost a whole day investigating the same issue Answer: invalid fastboot binary. Use this one
Don't use flash_image, it doesn't work with Xperias
Cheers,
z
Click to expand...
Click to collapse
TY so much. Yes, a lot of wasting time, checking everything on my Linux box!! Your answer is nice to me, as I was doubting about my Linux set up, and now I feel safe.
I managed to settle everything today on a Winodows box, in just 15 mn! Fastbooted boot.img, flashed update from sdcard, et hop!
TY for the binary. I will use it next time on my Linux box.

fastboot -i 0x0fce devices
Click to expand...
Click to collapse
shouldnt it be
Code:
fastboot -i 0xfce devices
instead?

try running
Code:
fastboot -i 0x0fce
.
You might also require running it as root. At least that's what i'm forced to do everytime, i guess it has sth to do with the udev entry but not sure what.
Also running as root means i'm not able to use tools like FlashTool, but if you just need fastboot, it will probably work.
Cheers,
G

g el said:
try running
Code:
fastboot -i 0x0fce
.
You might also require running it as root. At least that's what i'm forced to do everytime, i guess it has sth to do with the udev entry but not sure what.
Also running as root means i'm not able to use tools like FlashTool, but if you just need fastboot, it will probably work.
Cheers,
G
Click to expand...
Click to collapse
You need to add the udev rule mentioned in OP and it will work for regular users too.
Code:
#SE Arc Xperia
SUBSYSTEMS==”usb”, ATTRS{idVendor}==”0fce″, ATTRS{idProduct}==”014f″, OWNER:="yourusernamehere", GROUP:="plugdev", MODE=”0666″
Also, I don't use 'fastboot -i 0x0fce' (just fastboot <command>) and it still works fine
Cheers,
z

zdzihu said:
You need to add the udev rule mentioned in OP and it will work for regular users too.
Code:
#SE Arc Xperia
SUBSYSTEMS==”usb”, ATTRS{idVendor}==”0fce″, ATTRS{idProduct}==”014f″, OWNER:="yourusernamehere", GROUP:="plugdev", MODE=”0666″
Also, I don't use 'fastboot -i 0x0fce' (just fastboot <command>) and it still works fine
Cheers,
z
Click to expand...
Click to collapse
Agree totally, no need sudoing, neither use option. As previoulsy mentioned, a wrong binary was the only culprit. Usually, fastboot is trivial in Linux, with the only condition being the correct android rules in /etc/udev.

OTA update problem

Hi i bought a secondhand HTC one X (my other HOX got stolen) Anyway after the download for software update got completed it says "We have determined that your phone may be running modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone. If you did not modify your system software or would like help reverting your system, please contact us via support section at www.htc.com."
I also downloaded the root checker it says "not rooted".
Android version : 4.0.3
Htc sense version : 4.0
Software number : [email protected](chinese characters)
HTC SDK API level 4.12
HTC Extension version : HTCExtension_403_1_GA_7
Kernel Version : [email protected] #1 SMP PREEMPT
Baseland version : 1.1204.105.14
Build number: 1.29.728.12 CLS62864 release-keys
Browser version : WebKit/534.30
Can anyone help me? Thanks in advance.

rollyblu said:
Hi i bought a secondhand HTC one X (my other HOX got stolen) Anyway after the download for software update got completed it says "We have determined that your phone may be running modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone. If you did not modify your system software or would like help reverting your system, please contact us via support section at www.htc.com."
I also downloaded the root checker it says "not rooted".
Android version : 4.0.3
Htc sense version : 4.0
Software number : [email protected](chinese characters)
HTC SDK API level 4.12
HTC Extension version : HTCExtension_403_1_GA_7
Kernel Version : [email protected] #1 SMP PREEMPT
Baseland version : 1.1204.105.14
Build number: 1.29.728.12 CLS62864 release-keys
Browser version : WebKit/534.30
Can anyone help me? Thanks in advance.
Click to expand...
Click to collapse
In bootloader mode run the following command - fastboot getvar version-main. That will tell you the RUU version you will need to flash to get back to complete stock as the rom you currently have may be customised and the update will not be successfully applied to that rom. You will then need to locate the necessary ruu (try here) and flash that with a locked bootloader.

ClydeB1 said:
In bootloader mode run the following command - fastboot getvar version-main. That will tell you the RUU version you will need to flash to get back to complete stock as the rom you currently have may be customised and the update will not be successfully applied to that rom. You will then need to locate the necessary ruu (try here) and flash that with a locked bootloader.
Click to expand...
Click to collapse
Hi thanks.. Can you give me a detailed step by step as to what i have to do? Thanks

It says...
****UNLOCKED***
ENDEAVORU PVT SHIP S-ON RL
HBOOT-0.95.0000
CPLD-None
MICROP-None
RADIO-None
eMMC-bootmode:disable
CPU-bootmode: disable
HW Secure boot: enable
MODEM Path: Off
May 8 2012, 21:32:10

Btw i tried to put the phone to bootloader mode and select the fastboot. My only selections are
HBOOT
REBOOT
REBOOTLOADER
POWER DOWN
It doesnt have the "fastboot getvar version-main"..

You got to have HTC drivers installed on the pc, and you also need the fastboot files on the pc. When you put the phone in the bootloader menu you should see "fastboot usb" when you connect the phone to the pc.
Then you open a command prompt in the fastboot folder and type the command
Fastboot getvar version-main

Mr Hofs said:
You got to have HTC drivers installed on the pc, and you also need the fastboot files on the pc. When you put the phone in the bootloader menu you should see "fastboot usb" when you connect the phone to the pc.
Then you open a command prompt in the fastboot folder and type the command
Fastboot getvar version-main
Click to expand...
Click to collapse
Thanks for the reply.. it says version-main: 1.29.163.13

rollyblu said:
Thanks for the reply.. it says version-main: 1.29.163.13
Click to expand...
Click to collapse
Pretty sure that's a Vodafone France handset...seems to tie in with previous RUU versions

EddyOS said:
Pretty sure that's a Vodafone France handset...seems to tie in with previous RUU versions
Click to expand...
Click to collapse
I can't seem to find the RUU version with the link provided. (http://htcruu.com/?dir=Endeavor)..

rollyblu said:
I can't seem to find the RUU version with the link provided. (http://htcruu.com/?dir=Endeavor)..
Click to expand...
Click to collapse
Yeah, only seems the previous one is available. Looks like you're stuck unless someone has a Nandroid

I don't see the one you need in the backup collection thread

[q] please help!!!

Hello I am currently following this guide http://forum.xda-developers.com/showthread.php?t=1506258 and i am on step eleven.
I cannot get the recovery.img to load because it says i am out of memory. At first it said "error: cannot load 'recovery.img': Visual C++ CRT: Not enough memory to complete call to strerror"
I have been looking at these threads for this problem"
http://forum.xda-developers.com/showthread.php?t=1515361
http://forum.xda-developers.com/showthread.php?t=1315372
http://forum.xda-developers.com/showthread.php?t=1457894&highlight=out+of+memory
I am still new to this and if anyone can help it would be much appreciated
HTC Droid Incredible ADR6300
MEID:
A100001783180A
Phone Number:
0000003541
IMSI:
310000000003541
Android Version:
2.3.4
Baseband Version:
2.15.10.12.20
Kernel Version:
2.6.35.13-g22d3486
[email protected] #1
Tue May 22 20:56:42
Build Number:
4.08.605.19 CL539174 release-keys
Software Number:
4.08.605.19 710RD
Browser Version:
WebKit/533.1
PRI Version:
1.70_002
PRL Version:
58006
ERI Version:
5
No Service on the phone. it has been reset. I also unlocked it using HTCdev. and have the Unlock_code.bin saved.

Are you putting the phone in fastboot-usb mode?
I also recommend you use Twrp 2.4.4.0 recovery .img .

Yes the phone is in fastboot usb mode. That's what the recovery menu thing says. Also i am able to access fastboot from the terminal but for some reason when i try to flash the recovery.img it gives me that c++ out of memory error.
I also saw a thread about TWRP 2.4.4.0 touch recovery for KFireHD 7? will the recovery .img be compatable for my device? also the recovery .img is 8MB and my original recovery. img is 3MB. how fix my memory problem?
Sent from my M886 using xda app-developers app

[6039] Custom Recovery - TWRP - 2.8.7.0

Hello guys/girls,
I have built successfully a TWRP 2.8.7.0 recovery for Alcatel Idol 3 6039 4.7 inch (tested on 6039y). The recovery image can be downloaded from here:
Edit (30.09.2015): I think this will be the final version of the recovery. The date/time issue is fixed now and additionally small adjustments to the initialization process have been added.
twrp_recovery-2.8.7.0-idol347.img
md5sum: 175be787d67839d15beab7285279a72c
Please note that the latest OTA updates from the end of August and the start of September disable the fastboot commands which means that this recovery cannot be started as described below (if your device is already upgraded)!!! The device will return FAILED (remote: unknown command) when you try to boot the recovery.
If you find yourself in this situation but want root access please see this thread.
It can be tested as follows:
- enable the developer options
- allow the USB debugging
- reboot to bootloader:
Code:
adb reboot-bootloader
- start the recovery image with:
Code:
fastboot -i 0x1bbb boot twrp_recovery-2.8.7.0-idol3-6039y.img
Please do not forget first to make a backup of the system partition by selecting System Image from the Backup settings. The backup image will be needed in order to install future OTA updates if available, so please keep it in a safe place.

petrov.0 said:
Hello guys/girls,
I have built successfully a TWRP 2.8.7.0 recovery for Alcatel Idol 3 6039 4.7 inch (tested on 6039y). The recovery image can be downloaded from here:
twrp-2.8.7.0-idol3-6039y.img
It can be tested as follows:
- enable the developer options
- allow the USB debugging
- reboot to bootloader:
Code:
adb reboot-bootloader
- start the recovery image with:
Code:
fastboot -i 0x1bbb boot twrp_recovery-2.8.7.0-idol3-6039y.img
Please do not forget first to make a backup of the system partition by selecting System Image from the Backup settings. The backup image will be needed in order to install future OTA updates if available, so please keep it in a safe place.
Click to expand...
Click to collapse
Great job! A couple of the outstanding issues on the 6045 TWRP are that the date/time stamp of the backup is screwy because of a known bug with 64 bit chips and also the recovery identifies every model as a Y model (you can see in recovery.log) because the boot.img for a Y was used. Yours may also encounter one or both of these issues. I suggested in the other thread they consider building for each model using the individual boot.img but didn't get a reply.

famewolf said:
Great job! A couple of the outstanding issues on the 6045 TWRP are that the date/time stamp of the backup is screwy because of a known bug with 64 bit chips and also the recovery identifies every model as a Y model (you can see in recovery.log) because the boot.img for a Y was used. Yours may also encounter one or both of these issues. I suggested in the other thread they consider building for each model using the individual boot.img but didn't get a reply.
Click to expand...
Click to collapse
Yes, the date/time stamp is wrong. The device model however is not much . The ro.product.model is shown as idol347. It is a custom build after all.

I tried to use TWRP on my 6039Y and it's not working. Well to be more precise I don't know if your custom recovery works or not because I can't seem to get past the first step. Here's what happened
Code:
adb reboot-bootloader
So the device reboots, but doesn't get past the first screen (Alcatel OneTouch Powered by Android) even after a minute or so. Should I let it more time or is this the bootloader?
Then i try this
Code:
fastboot -i 0x1bbb devices
This seems to have no effect, the command seems to execute without any consequence and I'm able to type a new line in cmd
And if I try
Code:
fastboot -i 0x1bbb boot twrp_recovery-2.8.7.0-idol3-6039y.img
I get a <waiting for device> and I'm stuck on that line, having to Ctrl+C to stop the command and reboot the phone by holding power
Yes I know, I'm on Windows and it might be the drivers causing this. However I have installed the ADB drivers through SDK just fine. I would like to be able to install the drivers from the phone but the only options I see in the USB connection settings are MTP, PTP and Charging only. Any idea on how to get that CD-Rom option to appear?
Thanks for your help in advance

Rorshan said:
I tried to use TWRP on my 6039Y and it's not working. Well to be more precise I don't know if your custom recovery works or not because I can't seem to get past the first step. Here's what happened
Code:
adb reboot-bootloader
So the device reboots, but doesn't get past the first screen (Alcatel OneTouch Powered by Android) even after a minute or so. Should I let it more time or is this the bootloader?
Click to expand...
Click to collapse
This is OK it's in the bootloader.
Rorshan said:
Code:
fastboot -i 0x1bbb devices
This seems to have no effect, the command seems to execute without any consequence and I'm able to type a new line in cmd
And if I try
Code:
fastboot -i 0x1bbb boot twrp_recovery-2.8.7.0-idol3-6039y.img
I get a <waiting for device> and I'm stuck on that line, having to Ctrl+C to stop the command and reboot the phone by holding power
Click to expand...
Click to collapse
Looks like a driver issue. I use Linux no problems here no need of drivers too.
Rorshan said:
Yes I know, I'm on Windows and it might be the drivers causing this. However I have installed the ADB drivers through SDK just fine. I would like to be able to install the drivers from the phone but the only options I see in the USB connection settings are MTP, PTP and Charging only. Any idea on how to get that CD-Rom option to appear?
Thanks for your help in advance
Click to expand...
Click to collapse
Try with the drivers posted by @famewolf here or with these.
Meanwhile the first post has been updated with a new link. Please download the recovery again. There was a bug with the screenlock in the previous build. The screenlock is disabled in this one.

Alright I'll make sure to try that. Otherwise I guess I'll just try with Linux or Mac. Thanks
Sent from my 6039Y using Tapatalk

Rorshan said:
Alright I'll make sure to try that. Otherwise I guess I'll just try with Linux or Mac. Thanks
Sent from my 6039Y using Tapatalk
Click to expand...
Click to collapse
A quick check of the dirvers shared by @famewolf shows that they should work on windows with 6039y (at least to start the recovery). These are the vendor and the product IDs of 6039y from one of the INF files in the archive so the drivers should be compatible with the device when is in the bootloader (they match with those reported by the device).
Code:
USB\VID_1BBB&PID_D00D.DeviceDescRelease="Android Sooner Single ADB Interface"
I don't see however the IDs for the recovery mode:
Code:
[726530.487224] usb 1-4: New USB device found, idVendor=18d1, idProduct=4ee2
and the IDs from when the phone is connected as MTP device:
Code:
[726695.431624] usb 1-4: New USB device found, idVendor=1bbb, idProduct=af2b
but I hope everything to be OK. Good luck.

Why is this thread in Mi Note pro development section ? It's about idol 3 6039....

frankee207 said:
Why is this thread in Mi Note pro development section ? It's about idol 3 6039....
Click to expand...
Click to collapse
I asked the moderator to move it to the development section of Idol 3, but something went wrong. The moderator is informed about this. Now I'm waiting to be moved to the Idol 3 forum again.

petrov.0 said:
I asked the moderator to move it to the development section of Idol 3, but something went wrong. The moderator is informed about this. Now I'm waiting to be moved to the Idol 3 forum again.
Click to expand...
Click to collapse
Yeah I was thinking that's a bit strange! Got me excited thinking theres newer TWRP for Mi Note Pro xD

Cyanogen recovery
Here is a download link of the cyanogen recovery (built from the 12.1 branch). It's useless. But if someone wants to try it. The md5sum of the image is 3ff21bbf5ece48422f3135fa583eaa78

Should this work on 6039J?

Has not been tested on 6039J until now, but you can try it. Don't rush with backups wipes etc. (because the partition table can be different) just boot with it through fastboot. You can examine your partitions with the recovery from the repartitioning guide which contains gdisk (if your phone is not rooted yet). But this is only if this one works with your device. By the way what is the J version ? Dual sim ?

I'm trying to create a backup of the 6039S (North American 16GB, 1-SIM/1-SD model), and am having some issues with fastboot.
ADB is working flawlessly, and I can boot into the bootloader. As petrov.0 noted earlier in this thread there is no dedicated bootloader screen, just the onetouch splashscreen displays.
I can enter:
Code:
fastboot -i 0x1bbb devices
and the device shows up: "6346ce6d fastboot".
However, when I go to run any of the OEM commands, e.g.
Code:
fastboot -i 0x1bbb oem device-info
it shows:
...
FAILED (remote: unknown command)
finished. total time: 0.016s
Any ideas? By all appearances the alcatel driver seems to be working, but could this still be a driver issue?

Bradlee22 said:
I'm trying to create a backup of the 6039S (North American 16GB, 1-SIM/1-SD model), and am having some issues with fastboot.
ADB is working flawlessly, and I can boot into the bootloader. As petrov.0 noted earlier in this thread there is no dedicated bootloader screen, just the onetouch splashscreen displays.
I can enter:
Code:
fastboot -i 0x1bbb devices
and the device shows up: "6346ce6d fastboot".
However, when I go to run any of the OEM commands, e.g.
Code:
fastboot -i 0x1bbb oem device-info
it shows:
...
FAILED (remote: unknown command)
finished. total time: 0.016s
Any ideas? By all appearances the alcatel driver seems to be working, but could this still be a driver issue?
Click to expand...
Click to collapse
Probably this problem is not related to the driver. Something is different in your device. By the way can you boot this recovery ?

petrov.0 said:
Probably this problem is not related to the driver. Something is different in your device. By the way can you boot this recovery ?
Click to expand...
Click to collapse
No, I can't boot this TWRP recovery either. I get the same error message: FAILED (remote: unknown command).

I must admit that the internal sd card has not been mounted properly until now. I found the proper way however how to do it. The first post has been updated and now contains a link to the recovery which includes the corrections. The configuration files with which I do these recoveries, are also publicly available now and can be found here. Nothing special but ...

Bradlee22 said:
No, I can't boot this TWRP recovery either. I get the same error message: FAILED (remote: unknown command).
Click to expand...
Click to collapse
Any output from
Code:
fastboot -i 0x1bbb getvar secure
fastboot -i 0x1bbb getvar version-bootloader
fastboot -i 0x1bbb getvar all

petrov.0 said:
Any output from
Code:
fastboot -i 0x1bbb getvar secure
fastboot -i 0x1bbb getvar version-bootloader
fastboot -i 0x1bbb getvar all
Click to expand...
Click to collapse
Nothing useful from any of those.
Code:
fastboot -i 0x1bbb getvar secure
Output is:
secure:
finished. total time: 0.016s
Code:
fastboot -i 0x1bbb getvar version-bootloader
Output is:
version-bootloader:
finished. total time: -0.000s
Code:
fastboot -i 0x1bbb getvar all
Output is:
all:
finished. total time -0.000s
P.S. Thanks for your help. It's much appreciated!

Bradlee22 said:
Nothing useful from any of those.
Click to expand...
Click to collapse
remote: unknown command is a protocol error, as long as I understand the source. What is the host OS ? Windows ... which version ... did you try to start cmd.exe as administrator ? Which drivers you use ? On what port is your device connected (USB 2 or USB 3). Do you have access to a Linux box ? If you have try from there. I'm not sure how Windows handles the sharing of the USB ports with a virtual machine. You can try to start a distro in VirtualBox, which have option to expose a device connected on the host to the guest system and then to try fastboot from there.

[ROM][OFFICIAL][FASTBOOT]Xiaomi Mi A3 (laurel_sprout)

Hello!
On this thread we could keep a list of all fastboot ROMs that can be used to flash into Mi A3.
Version build number explained:
Example: 10.3.4.0.PFQMIXM
10.3.4.0 - Firmware version​P - Android version (P-> Pie / Android 9).​FQ - Smartphone model code (FQ = Xiaomi Mi A3).​MI - Firmware build type (MI for Global | EU for Europe)​XM - Firmware version code​
Global versions (PFQMIXM) or QFQMIXM):
Full Fastboot Android 11 ROM Global version with June 2021 Security patch (V12.0.11.0.RFQMIXM)​​device=laurel_sprout​build_number=V12.0.11.0.RFQMIXM​userdata_version=20210615.0000.00​
Full Fastboot Android 11 ROM Global version with May 2021 Security patch (V12.0.9.0.RFQMIXM)​​device=laurel_sprout​build_number=V12.0.9.0.RFQMIXM​userdata_version=20210506.0000.00​​Full Fastboot Android 11 ROM Global version with April 2021 Security patch (V12.0.8.0.RFQMIXM)​​device=laurel_sprout​build_number=V12.0.8.0.RFQMIXM​userdata_version=20210409.0000.00​
Full Fastboot Android 10 ROM Global version with November 2020 Security patch (V11.0.23.0.QFQMIXM)​​device=laurel_sprout​build_number=V11.0.23.0.QFQMIXM​userdata_version=20201124.0000.00​
Full Fastboot Android 10 ROM Global version with October 2020 Security patch (V11.0.22.0.QFQMIXM)​​device=laurel_sprout​build_number=V11.0.22.0.QFQMIXM​userdata_version=20201017.0000.00​
Full Fastboot Android 10 ROM Global version with September 2020 Security patch (V11.0.21.0.QFQMIXM)​​device=laurel_sprout​build_number=V11.0.21.0.QFQMIXM​userdata_version=20200917.0000.00​
Full Fastboot Android 10 ROM Global version with August 2020 Security patch (V11.0.20.0.QFQMIXM)​​device=laurel_sprout​build_number=V11.0.20.0.QFQMIXM​userdata_version=20200804.0000.00​
Full Fastboot Android 10 ROM Global version with July 2020 Security patch (V11.0.19.0.QFQMIXM)​​device=laurel_sprout​build_number=V11.0.19.0.QFQMIXM​userdata_version=20200717.0000.00​
Full Fastboot Android 10 ROM Global version with June 2020 Security patch (V11.0.16.0.QFQMIXM)​​device=laurel_sprout​build_number=V11.0.16.0.QFQMIXM​userdata_version=20200623.0000.00​
Full Fastboot Android 10 ROM Global version with May 2020 Security patch (V11.0.15.0.QFQMIXM)​​device=laurel_sprout​build_number=V11.0.15.0.QFQMIXM​userdata_version=20200507.0000.00​
Full Fastboot ROM Global version with March 2020 Security patch (V10.3.16.0.PFQMIXM)​​device=laurel_sprout​build_number=V10.3.16.0.PFQMIXM​userdata_version=20200324.0000.00​
Full Fastboot ROM Global version with January 2020 Security patch (V10.3.13.0.PFQMIXM)​​device=laurel_sprout​build_number=V10.3.13.0.PFQMIXM​userdata_version=20200116.0000.00​
Full Fastboot ROM Global version with November Security patch (V10.3.9.0.PFQMIXM)​​device=laurel_sprout​build_number=V10.3.9.0.PFQMIXM​userdata_version=20191107.0000.00​
Full Fastboot ROM Global version with October Security patch (V10.3.8.0.PFQMIXM)​​device=laurel_sprout​build_number=V10.3.8.0.PFQMIXM​userdata_version=20191012.0000.00​
Full Fastboot ROM Global version with August Security patch (V10.3.4.0.PFQMIXM)​​device=laurel_sprout​build_number=V10.3.4.0.PFQMIXM​userdata_version=20190815.0000.00​
Europe versions (PFQEUXM or QFQEUXM or RFQEUXM):
Full Fastboot Android 11 ROM EU version with May 2021 Security patch (V12.0.7.0.RFQEUXM)​​device=laurel_sprout​build_number=V12.0.7.0.RFQEUXM​userdata_version=20210513.0000.00​
Full Fastboot Android 11 ROM EU version with April 2021 Security patch (V12.0.6.0.RFQEUXM)​​device=laurel_sprout​build_number=V12.0.6.0.RFQEUXM​userdata_version=20210415.0000.00​
Full Fastboot Android 11 ROM EU version with March 2021 Security patch (V12.0.5.0.RFQEUXM)​​device=laurel_sprout​build_number=V12.0.5.0.RFQEUXM​userdata_version=20210311.0000.00​​Full Fastboot Android 11 ROM EU version with January 2021 Security patch (V12.0.3.0.RFQEUXM)​​device=laurel_sprout​build_number=V12.0.3.0.RFQEUXM​userdata_version=20210129.0000.00​
Full Fastboot Android 10 ROM EU version with November 2020 Security patch (V11.0.10.0.QFQEUXM)​​device=laurel_sprout​build_number=V11.0.10.0.QFQEUXM​userdata_version=20201125.0000.00​
Full Fastboot Android 10 ROM EU version with October 2020 Security patch (V11.0.9.0.QFQEUXM)​​device=laurel_sprout​build_number=V11.0.9.0.QFQEUXM​userdata_version=20201019.0000.00​
Full Fastboot Android 10 ROM EU version with September 2020 Security patch (V11.0.8.0.QFQEUXM)​​device=laurel_sprout​build_number=V11.0.8.0.QFQEUXM​userdata_version=20200926.0000.00​
Full Fastboot Android 10 ROM EU version with August 2020 Security patch (V11.0.6.0.QFQEUXM)​​device=laurel_sprout​build_number=V11.0.6.0.QFQEUXM​userdata_version=20200817.0000.00​
Full Fastboot Android 10 ROM EU version with July 2020 Security patch (V11.0.5.0.QFQEUXM)​​device=laurel_sprout​build_number=V11.0.5.0.QFQEUXM​userdata_version=20200723.0000.00​
Full Fastboot Android 10 ROM EU version with June 2020 Security patch (V11.0.3.0.QFQEUXM)​​device=laurel_sprout​build_number=V11.0.3.0.QFQEUXM​userdata_version=20200611.0000.00​
Full Fastboot Android 10 ROM EU version with May 2020 Security patch (V11.0.2.0.QFQEUXM)​​device=laurel_sprout​build_number=V11.0.2.0.QFQEUXM​userdata_version=20200512.0000.00​
Full Fastboot Android 10 ROM EU version with April 2020 Security patch (V11.0.1.0.QFQEUXM)​​device=laurel_sprout​build_number=V11.0.1.0.QFQEUXM​userdata_version=20200424.0000.00​
Full Fastboot ROM EU version with March 2020 Security patch (V10.3.17.0.PFQEUXM)​​device=laurel_sprout​build_number=V10.3.17.0.PFQEUXM​userdata_version=20200325.0000.00​
Full Fastboot ROM EU version with February 2020 Security patch (V10.3.15.0.PFQEUXM)​​device=laurel_sprout​build_number=V10.3.15.0.PFQEUXM​userdata_version=20200220.0000.00​
Full Fastboot ROM EU version with January 2020 Security patch (V10.3.14.0.PFQEUXM)​​device=laurel_sprout​build_number=V10.3.14.0.PFQEUXM​userdata_version=20200116.0000.00​
Full Fastboot ROM EU version with December Security patch (V10.3.13.0.PFQEUXM)​​device=laurel_sprout​build_number=V10.3.13.0.PFQEUXM​userdata_version=20191211.0000.00​
Full Fastboot ROM EU version with November Security patch (V10.3.12.0.PFQEUXM)​​device=laurel_sprout​build_number=V10.3.12.0.PFQEUXM​userdata_version=20191113.0000.00​
Full Fastboot ROM EU version with August Security patch (V10.3.7.0.PFQEUXM)​​device=laurel_sprout​build_number=V10.3.7.0.PFQEUXM​userdata_version=20190814.0000.00​
A site with mirror links to all fastboot images released so far has been shared with us by @Codebucket. Thank him for this.
This SITE, by @yshalsager, has all download links for both Fastboot ROMs and Recovery packages. Great job. Don't forget to thank him for this.
NOTES:
The scripts included on the *.bat and *.sh files assume that your device is currently on slot a. If it really is, they will work with no issues. If it's not then you have 3 choices (choose only one of them):
Before executing any of the bat (or sh if you're using Linux), change your active slot to a through fastboot (fastboot --set-active=a or fastboot set_active a)
Open the *.bat (or *.sh) file that you want to run and, before the line where you see fastboot %* reboot, add a line with fastboot %* set_active a (on linux fastboot $* set_active a) and save the file.
Open the *.bat (or *.sh) file that you want to run and find "system_other.img". Replace that with system.img and save the file.
Cheers!

My phone is stuck at erasing after flashing this stock rom

PKQ1.190416.001.V10.3.4.0.PFQMIXM
https://bigota.d.miui.com/V10.3.4.0...0.PFQMIXM_20190815.0000.00_9.0_00838b4c0e.tgz

drozo8o8 said:
My phone is stuck at erasing after flashing this stock rom
Click to expand...
Click to collapse
Becouse this fastboot images contain mistakes in *.bat scripts. It is need to set active slot "A" after flashing or flash system.img to slot "B" instead of "system_other.img".
So, here is pack of fixed *.bat.

Displax said:
Becouse this fastboot images contain mistakes in *.bat scripts. It is need to set active slot "A" after flashing or flash system.img to slot "B" instead of "system_other.img".
So, here is pack of fixed *.bat.
Click to expand...
Click to collapse
I got into the factory recovery and it says "f2fs error status 255" when formatting data

Displax said:
Becouse this fastboot images contain mistakes in *.bat scripts. It is need to set active slot "A" after flashing or flash system.img to slot "B" instead of "system_other.img".
So, here is pack of fixed *.bat.
Click to expand...
Click to collapse
Attention, the system_other.img file exists. And the scripts are flashing them to system_b (system partition on slot b). Not really sure what is this system_other.img but I guess it could be a dummy system.img just to not leave it blank.
Anyway, there isn't really a command to change slot to a...one could always perform that manually...but still. This is weird.
The stuck on erasing is not normal, I think.

Typhus_ said:
Attention, the system_other.img file exists. And the scripts are flashing them to system_b (system partition on slot b). Not really sure what is this system_other.img but I guess it could be a dummy system.img just to not leave it blank.
Anyway, there isn't really a command to change slot to a...one could always perform that manually...but still. This is weird.
The stuck on erasing is not normal, I think.
Click to expand...
Click to collapse
Is there a way to flash over edl yet ? like I remember getting some programmer files for the chip.

drozo8o8 said:
Is there a way to flash over edl yet ? like I remember getting some programmer files for the chip.
Click to expand...
Click to collapse
I think that any latest MiFlash tools is able to flash in EDL mode. You could try it.

I need a programmer file which isnt out yet... Idk what else to do, anyone got some ideas ?

Typhus_ said:
Attention, the system_other.img file exists. And the scripts are flashing them to system_b (system partition on slot b). Not really sure what is this system_other.img but I guess it could be a dummy system.img just to not leave it blank.
Anyway, there isn't really a command to change slot to a...one could always perform that manually...but still. This is weird.
The stuck on erasing is not normal, I think.
Click to expand...
Click to collapse
Just add this line fastboot %* set_active a before fastboot %* reboot and script will work.

OKay so after flashign this and getting back to stock recovery where it did ask me to factory reset im getting an error whle formatting data
e:/sbin/mkfs.f2fs failed with status 255
e:format volume: failed /sbin/mkfs.f2fs on dev/block/bootdevice/by-name/userdata: no such file or directory

fastboot flashing unlock
fastboot flashing unlock_critical
chmod +x flash_all.sh
sudo sh flash_all.sh
it´s work for me

drozo8o8 said:
OKay so after flashign this and getting back to stock recovery where it did ask me to factory reset im getting an error whle formatting data
e:/sbin/mkfs.f2fs failed with status 255
e:format volume: failed /sbin/mkfs.f2fs on dev/block/bootdevice/by-name/userdata: no such file or directory
Click to expand...
Click to collapse
What? That's strange...the recovery does not "see" the userdata partition... That's not good.
I think that in EDL mode you could fix that. But I think you need the correct "prog_firehose" file for it to work.
I'm sorry I can't help you that much but it seems your userdata partition, or better yet, the symlink to your userdata partition is missing.
Enviado do meu Mi A3 através do Tapatalk

Displax said:
Becouse this fastboot images contain mistakes in *.bat scripts. It is need to set active slot "A" after flashing or flash system.img to slot "B" instead of "system_other.img".
So, here is pack of fixed *.bat.
Click to expand...
Click to collapse
:good:
The .bat script was the problem !! Thanks to this, I installed a ROM. Thank you so much.

Can anyone backup Miui camera apk from Android one, i want to port the app to AOSP roms??

Stefke93 said:
Can anyone backup Miui camera apk from Android one, i want to port the app to AOSP roms??
Click to expand...
Click to collapse
https://drive.google.com/file/d/1JiDwgaPw6CCdkbsH19SF6hKqFjBMzT6h/view?usp=sharing

My device is V10.3.5.0.PFQIXM
Im trying to find a stock with this number: V10.3.5.0.PFQIXM, but I dont find it. There are someone that have a link?

nelinthon said:
Im trying to find a stock with this number: V10.3.5.0.PFQIXM, but I dont find it. There are someone that have a link?
Click to expand...
Click to collapse
This is the second OTA in August which is currently rolling out as an incremental update. Hopefully we can find the OTA URL soon.

I tried to install this rom, but my device get a loop. Only start on fastboot mode. Can anyone help me???

nelinthon said:
I tried to install this rom, but my device get a loop. Only start on fastboot mode. Can anyone help me???
Click to expand...
Click to collapse
Did you follow the steps I've explained on the "NOTES" present on the OP?