Related
Hellpppp!
I can't boot nor flash custom recovery anymore after updatting to last Global Miui 11.15,
using :
fastboot boot twrp.img
stuck at : downloading 'boot.img'...
using fastboot flash recovery twrp.img
nothing happens,.
is this something with xiaomi ARP ?
Why don't you flash for example global stable through fastboot and see how it goes you just need to extract the tar.gz file and run the flash_all.sh file on the terminal.
Use mi flash with TGZ firmware.
if you can open the back cover then use test point method
XBowman said:
Hellpppp!
I can't boot nor flash custom recovery anymore after updatting to last Global Miui 11.15,
using :
fastboot boot twrp.img
stuck at : downloading 'boot.img'...
using fastboot flash recovery twrp.img
nothing happens,.
is this something with xiaomi ARP ?
Click to expand...
Click to collapse
XBowman said:
Hellpppp!
I can't boot nor flash custom recovery anymore after updatting to last Global Miui 11.15,
using :
fastboot boot twrp.img
stuck at : downloading 'boot.img'...
using fastboot flash recovery twrp.img
nothing happens,.
is this something with xiaomi ARP ?
Click to expand...
Click to collapse
Same here
Should I just downgrade to MIUI 9 just to flash TWRP?
Update: I succeed flash twrp
Here's how i did it:
- Go to EDL mode using test point
- Flash MIUI 9 (I used version 7.9.7) using MiFlash
- Boot to fastboot and flash twrp
- Boot twrp using fastboot
Follow bellow steps (carefully) for flashing GSI in realme 3/3i on Android 10, we have only tested few GSIs Like CherishOS, LineageOS, HavocOS etc.
All GSIs have different methods to flash kn Realme 3/3i.
Provided method have tested on CherishOS (GSI Snaps are below)
What you need to flash GSI:
Platform tool (Bootloader should be unlock)
LineageOS 17.1.zip
https://bit.ly/oOo17o1rm1821Orangefox recovery.img
28.81 MB file on MEGA
bit.ly
Boot.img (do not try any other boot.img)
File on MEGA
bit.ly
Dmverity zip file
3.25 MB file on MEGA
bit.ly
GSI image (system.img)
We are flashing CherishOS this time.
https://bit.ly/CherishGSIrmx1821
Steps to Flash:
Copy LineageOS 17.1 and Dmverifyzip file into SD Card.
Flash orangefox
Commands:
fastboot flash recovery xxx.img (xxx is recovery name)
fastboot -w
fastboot reboot recovery
In OrangeFox Recovery
Goto format data and type yes
Now goto wipe, Wipe everything except SD Card and swipe
Now goto files>SD Card and flash LineageOS 17.1 zip file
After flashing done simply reboot to system (no need to wipe cache)
Your phone will boot in lineageos, in lineage OS 17.1 Goto Developer options and enable "Advance Restart" now press power button and click on reboot> recovery, your phone will reboot into recovery. Now goto files and flash Dmverityzip file and after flashing done goto reboot > bootloader (no need to wipe cache).
Once you rebooted into bootloader (fastboot mode) type below commands.
"fastboot --disable-verity --disable-verification flash boot boot.img"
(note this should be the same boot file which i have share in this thread)
"fastboot erase system"
"fastboot flash system xxx.img"
(xxx is cherishOS.img, wait for flashing completion)
"fastboot -w"
"fastboot erase para"
"fastboot reboot"
(Wait atleast 5-10 minites your phone will be in realme logo state, do not panic)
The End.
Special Thanks To Ujjwal for Flashing.
Feel Free to Join https://t.me/joinchat/WM3heLvnFTYXzeOb
azharmansoori said:
Follow bellow steps (carefully) for flashing GSI in realme 3/3i on Android 10, we have only tested few GSIs Like CherishOS, LineageOS, HavocOS etc.
All GSIs have different methods to flash kn Realme 3/3i.
Provided method have tested on CherishOS (GSI Snaps are below)
What you need to flash GSI:
Platform tool (Bootloader should be unlock)
LineageOS 17.1.zip
https://bit.ly/oOo17o1rm1821Orangefox recovery.img
28.81 MB file on MEGA
bit.ly
Boot.img (do not try any other boot.img)
File on MEGA
bit.ly
Dmverity zip file
3.25 MB file on MEGA
bit.ly
GSI image (system.img)
We are flashing CherishOS this time.
https://bit.ly/CherishGSIrmx1821
Steps to Flash:
Copy LineageOS 17.1 and Dmverifyzip file into SD Card.
Flash orangefox
Commands:
fastboot flash recovery xxx.img (xxx is recovery name)
fastboot -w
fastboot reboot recovery
In OrangeFox Recovery
Goto format data and type yes
Now goto wipe, Wipe everything except SD Card and swipe
Now goto files>SD Card and flash LineageOS 17.1 zip file
After flashing done simply reboot to system (no need to wipe cache)
Your phone will boot in lineageos, in lineage OS 17.1 Goto Developer options and enable "Advance Restart" now press power button and click on reboot> recovery, your phone will reboot into recovery. Now goto files and flash Dmverityzip file and after flashing done goto reboot > bootloader (no need to wipe cache).
Once you rebooted into bootloader (fastboot mode) type below commands.
"fastboot --disable-verity --disable-verification flash boot boot.img"
(note this should be the same boot file which i have share in this thread)
"fastboot erase system"
"fastboot flash system xxx.img"
(xxx is cherishOS.img, wait for flashing completion)
"fastboot -w"
"fastboot erase para"
"fastboot reboot"
(Wait atleast 5-10 minites your phone will be in realme logo state, do not panic)
The End.
Special Thanks To Ujjwal for Flashing.
Feel Free to Join https://t.me/joinchat/WM3heLvnFTYXzeOb
Click to expand...
Click to collapse
After booting to LineageOS 17.1, and flashing the DM verity disabler, Can i flash the unmodified Android 11 GSI system.img instead of CherishOS.img? Is it going to work?
ATDteam said:
After booting to LineageOS 17.1, and flashing the DM verity disabler, Can i flash the unmodified Android 11 GSI system.img instead of CherishOS.img? Is it going to work?
Click to expand...
Click to collapse
Yes, unmodified GSI will work. Just follow our process from "fastboot --disable-verity --disable-verification etc etc"
azharmansoori said:
Yes, unmodified GSI will work. Just follow our process from "fastboot --disable-verity --disable-verification etc etc"
Click to expand...
Click to collapse
Thank you i will do it when i recover my Realme 3 from being dead. i hard bricked my phone, No Fastboot, No Charge, No Recovery no sign of life in screen, can you suggest how can i fix this? or do you ever encounter this?
ATDteam said:
Thank you i will do it when i recover my Realme 3 from being dead. i hard bricked my phone, No Fastboot, No Charge, No Recovery no sign of life in screen, can you suggest how can i fix this? or do you ever encounter this?
Click to expand...
Click to collapse
There is only option to go to Service Center.
azharmansoori said:
There is only option to go to Service Center.
Click to expand...
Click to collapse
oh i see. however i manage to Extract the OFP firmware of realme 3 with auth_file, scatter file and all the img(s), the only problem is the Download-Agent File, there is a DA file thing error when flashing using SP Flash Tool. By the way thanks a lot.
ATDteam said:
oh i see. however i manage to Extract the OFP firmware of realme 3 with auth_file, scatter file and all the img(s), the only problem is the Download-Agent File, there is a DA file thing error when flashing using SP Flash Tool. By the way thanks a lot.
Click to expand...
Click to collapse
Please see other thread, which is in Guides of Realme 3 for (how to unbrick realme 3, do follow his process and like his post if you successfully unubrick).
azharmansoori said:
Please see other thread, which is in Guides of Realme 3 for (how to unbrick realme 3, do follow his process and like his post if you successfully unubrick).
Click to expand...
Click to collapse
yah i figure it out, im the one who posted the Unbrick Tutorial. Thanks.
ATDteam said:
yah i figure it out, im the one who posted the Unbrick Tutorial. Thanks.
Click to expand...
Click to collapse
Pleasure, would you please contact me at t.me/azharmansoori22 as i am facing issue in your bat file.
azharmansoori said:
Follow bellow steps (carefully) for flashing GSI in realme 3/3i on Android 10, we have only tested few GSIs Like CherishOS, LineageOS, HavocOS etc.
All GSIs have different methods to flash kn Realme 3/3i.
Provided method have tested on CherishOS (GSI Snaps are below)
What you need to flash GSI:
Platform tool (Bootloader should be unlock)
LineageOS 17.1.zip
https://bit.ly/oOo17o1rm1821Orangefox recovery.img
28.81 MB file on MEGA
bit.ly
Boot.img (do not try any other boot.img)
File on MEGA
bit.ly
Dmverity zip file
3.25 MB file on MEGA
bit.ly
GSI image (system.img)
We are flashing CherishOS this time.
https://bit.ly/CherishGSIrmx1821
Steps to Flash:
Copy LineageOS 17.1 and Dmverifyzip file into SD Card.
Flash orangefox
Commands:
fastboot flash recovery xxx.img (xxx is recovery name)
fastboot -w
fastboot reboot recovery
In OrangeFox Recovery
Goto format data and type yes
Now goto wipe, Wipe everything except SD Card and swipe
Now goto files>SD Card and flash LineageOS 17.1 zip file
After flashing done simply reboot to system (no need to wipe cache)
Your phone will boot in lineageos, in lineage OS 17.1 Goto Developer options and enable "Advance Restart" now press power button and click on reboot> recovery, your phone will reboot into recovery. Now goto files and flash Dmverityzip file and after flashing done goto reboot > bootloader (no need to wipe cache).
Once you rebooted into bootloader (fastboot mode) type below commands.
"fastboot --disable-verity --disable-verification flash boot boot.img"
(note this should be the same boot file which i have share in this thread)
"fastboot erase system"
"fastboot flash system xxx.img"
(xxx is cherishOS.img, wait for flashing completion)
"fastboot -w"
"fastboot erase para"
"fastboot reboot"
(Wait atleast 5-10 minites your phone will be in realme logo state, do not panic)
The End.
Special Thanks To Ujjwal for Flashing.
Feel Free to Join https://t.me/joinchat/WM3heLvnFTYXzeOb
Click to expand...
Click to collapse
azharmansoori said:
Follow bellow steps (carefully) for flashing GSI in realme 3/3i on Android 10, we have only tested few GSIs Like CherishOS, LineageOS, HavocOS etc.
All GSIs have different methods to flash kn Realme 3/3i.
Provided method have tested on CherishOS (GSI Snaps are below)
What you need to flash GSI:
Platform tool (Bootloader should be unlock)
LineageOS 17.1.zip
https://bit.ly/oOo17o1rm1821Orangefox recovery.img
28.81 MB file on MEGA
bit.ly
Boot.img (do not try any other boot.img)
File on MEGA
bit.ly
Dmverity zip file
3.25 MB file on MEGA
bit.ly
GSI image (system.img)
We are flashing CherishOS this time.
https://bit.ly/CherishGSIrmx1821
Steps to Flash:
Copy LineageOS 17.1 and Dmverifyzip file into SD Card.
Flash orangefox
Commands:
fastboot flash recovery xxx.img (xxx is recovery name)
fastboot -w
fastboot reboot recovery
In OrangeFox Recovery
Goto format data and type yes
Now goto wipe, Wipe everything except SD Card and swipe
Now goto files>SD Card and flash LineageOS 17.1 zip file
After flashing done simply reboot to system (no need to wipe cache)
Your phone will boot in lineageos, in lineage OS 17.1 Goto Developer options and enable "Advance Restart" now press power button and click on reboot> recovery, your phone will reboot into recovery. Now goto files and flash Dmverityzip file and after flashing done goto reboot > bootloader (no need to wipe cache).
Once you rebooted into bootloader (fastboot mode) type below commands.
"fastboot --disable-verity --disable-verification flash boot boot.img"
(note this should be the same boot file which i have share in this thread)
"fastboot erase system"
"fastboot flash system xxx.img"
(xxx is cherishOS.img, wait for flashing completion)
"fastboot -w"
"fastboot erase para"
"fastboot reboot"
(Wait atleast 5-10 minites your phone will be in realme logo state, do not panic)
The End.
Special Thanks To Ujjwal for Flashing.
Feel Free to Join https://t.me/joinchat/WM3heLvnFTYXzeOb
Click to expand...
Click to collapse
Can I do this on Lineage os 18.1 using its boot.img for fastboot -disable...., can flash any A11 gsi, and what about gapps, you, you haven't flashed any gapps.
ritukanta said:
Can I do this on Lineage os 18.1 using its boot.img for fastboot -disable...., can flash any A11 gsi, and what about gapps, you, you haven't flashed any gapps.
Click to expand...
Click to collapse
Yes you can flash LineageOS boot.img on Android 11 GSIs.
Amd what for custom rom users, I'm using a11 ppui, what changes will be added, and can I do it with only orfox??
RIVEEKS said:
Amd what for custom rom users, I'm using a11 ppui, what changes will be added, and can I do it with only orfox??
Click to expand...
Click to collapse
No you can do with other suppoted recoveries like SHRP, PBRP (Official) etc.
Exactly a year ago I bought Poco F3, unlocked the bootloader and installed ArrowOS. Now I'm trying to figure out how to change my ROM and I can't really find any answers. I have the ArrowOS recovery and it's useless, I can't install another recovery with it. My fastboot also seems to be broken(?), it has a different logo and it's detected on my computer when I do (fastboot devices) but other than that it gives me a bunch of errors
I would like to at least know how to change the recovery. Is it possible that my bootloader got locked? One last thing, when I installed ArrowOS I used TWRP and updated it using OTA updates, now TWRP is gone.
Please help me
You need fastboot for TWRP.
It could not have gotten locked, no.
Arealhooman said:
It could not have gotten locked, no.
Click to expand...
Click to collapse
I just found a guide on Youtube for flashing twrp and I followed it to the (fastboot boot <TWRP>) part and I got this error
Sending 'boot.img' (196608 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Does this mean it got locked..?
Uh….maybe… did you lock it… what does it say in dev Setting sunder oem unlock.
Arealhooman said:
Uh….maybe… did you lock it… what does it say in dev Setting sunder oem unlock.
Click to expand...
Click to collapse
I don't have any oem unlock option in ArrowOS and I never locked anything wtf, I just used it as a normal phone and only did OTA updates + sometimes FW updates when required
Is there anyway to fix it?
ADB & Fastboot Binaries: https://developer.android.com/studio/releases/platform-tools
OrangeFox Recovery (recommended): https://orangefox.download/device/alioth
Install the Recovery ZIP by either ADB Sideload in ArrowOS Recovery
or you can extract the "recovery.img" and fastboot boot it ("fastboot boot recovery.img") and select "Install current Recovery"
Then you simply flash the ROM.zip (select "Reflash Recovery after ROM Flash") -> Reboot Recovery -> Format Data
The OTA Update has replaced your TWRP with ArrowOS Recovery, because ROM Updates replace the boot-partition (along with other system related partitions). The boot-partition contains the recovery-environment.
Only install Custom Recoveries from inside the Recovery, because Fastboot can only replace partitions entirely (and boot-partitions contains both bootloader & recovery)
The bootloader of the Poco F3 cannot (or shouldn't) be locked on Custom Software.
gobertel said:
I just found a guide on Youtube for flashing twrp and I followed it to the (fastboot boot <TWRP>) part and I got this error
Sending 'boot.img' (196608 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Does this mean it got locked..?
Click to expand...
Click to collapse
Download these:
https://sourceforge.net/projects/mipa-project/files/arrow-mipa/arrow-13.0/alioth/Additions/boot.img/download
https://sourceforge.net/projects/mipa-project/files/arrow-mipa/arrow-13.0/alioth/Additions/vendor_boot.img/download
First link, "fastboot flash boot boot.img"
Second link, "fastboot flash vendor_boot vendor_boot.img"
Then Fastboot booting into your Recovery-file should work.
Also, what's the problem with ArrowOS anyway? We've ArrowOS MiPa, it's a good and reliable ROM.
cyanGalaxy said:
Download these:
https://sourceforge.net/projects/mipa-project/files/arrow-mipa/arrow-13.0/alioth/Additions/boot.img/download
https://sourceforge.net/projects/mipa-project/files/arrow-mipa/arrow-13.0/alioth/Additions/vendor_boot.img/download
First link, "fastboot flash boot boot.img"
Second link, "fastboot flash vendor_boot vendor_boot.img"
Then Fastboot booting into your Recovery-file should work.
Click to expand...
Click to collapse
I noticed that these are for ArrowOS 13, I'm on 12.1 and they did not work
Do you also suggest I go into fastboot by which method because each one looks different
Recovery > Advanced > Enter fastboot
Or
Hold power button with volume down method
Also I'm just looking to update to Android 13 in general
Thank you for helping me out by the way
gobertel said:
I noticed that these are for ArrowOS 13, I'm on 12.1 and they did not work
Do you also suggest I go into fastboot by which method because each one looks different
Recovery > Advanced > Enter fastboot
Or
Hold power button with volume down method
Also I'm just looking to update to Android 13 in general
Click to expand...
Click to collapse
Both methods of booting into Fastboot is the same I would guess.
Yes we do have ArrowOS MiPa, you should only need to flash the ArrowOS 13 MiPa ROM ZIP in Recovery, but I rather recommend you using OrangeFox or TWRP for that.
What do you mean by "did not work". "Did not work" can mean anything.
Are you using the latest official ADB & Fastboot Binaries? The ones I've given you?
If yes, you can use this Payload Dumper Tool, to extract the "vendor_boot.img" and "boot.img" from ArrowOS 12. Maybe those from Arrow v12 can be flashed.
[Windows] Payload Dumper GUI - dump boot.img and other img files from payload.bin.
Hello there. Was bored and decided to make a gui that dumps Payload.bin file for easy flashing. Tested on Lineage OS 18 Payload.bin Result: Credits: Based on vm03 payload_dumper script. Github: Payload_dumper.py...
forum.xda-developers.com
cyanGalaxy said:
Both methods of booting into Fastboot is the same I would guess.
Yes we do have ArrowOS MiPa, you should only need to flash the ArrowOS 13 MiPa ROM ZIP in Recovery, but I rather recommend you using OrangeFox or TWRP for that.
What do you mean by "did not work". "Did not work" can mean anything.
Click to expand...
Click to collapse
fastboot flash boot boot.img
Sending 'boot_a' (196608 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
fastboot flash vendor_boot vendor_boot.img
Sending 'vendor_boot_a' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
fastboot boot recovery.img
Sending 'boot.img' (196608 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Another thing to add is I still I get the unlock symbol when booting up the phone, I dont know if that makes a difference
cyanGalaxy said:
Are you using the latest official ADB & Fastboot Binaries? The ones I've given you?
If yes, you can use this Payload Dumper Tool, to extract the "vendor_boot.img" and "boot.img" from ArrowOS 12. Maybe those from Arrow v12 can be flashed.
[Windows] Payload Dumper GUI - dump boot.img and other img files from payload.bin.
Hello there. Was bored and decided to make a gui that dumps Payload.bin file for easy flashing. Tested on Lineage OS 18 Payload.bin Result: Credits: Based on vm03 payload_dumper script. Github: Payload_dumper.py...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes I'm using the exact one you gave me and I will try it
gobertel said:
Yes I'm using the exact one you gave me and I will try it
Click to expand...
Click to collapse
Yup try it.
Else, here I have the vendor_boot.img & boot.img from the latest ArrowOS MiPa (February). More up-to-date than the SourceForge links.
Either the 2 files from ArrowOS v12, or the latest v13 ones that I've uploaded here, should definitely work.
Also try rebooting Fastboot Mode.
XDA doesn't let me upload the boot.img ඞ
cyanGalaxy said:
XDA doesn't let me upload the boot.img ඞ
Click to expand...
Click to collapse
Starting to think I should just give up, no matter what I do I get (Download is not allowed on locked devices)
The fastboot method you suggested does not work, it gets stuck on (waiting for any devices) but the recovery one works although like I said, I get the error no matter what I do
Is it locked or what?? I'm trying to figure that out and if it is how did it even get locked in the first place
I'm guessing there's no way to resolve it and that I'll be stuck on Android 12 for eternity
So sorry for wasting your time, I always end up with weird issues in everything
gobertel said:
Starting to think I should just give up, no matter what I do I get (Download is not allowed on locked devices)
The fastboot method you suggested does not work, it gets stuck on (waiting for any devices) but the recovery one works although like I said, I get the error no matter what I do
Is it locked or what?? I'm trying to figure that out and if it is how did it even get locked in the first place
I'm guessing there's no way to resolve it and that I'll be stuck on Android 12 for eternity
So sorry for wasting your time, I always end up with weird issues in everything
Click to expand...
Click to collapse
Waiting for any devices means your PC does not detect the phone.
Download this: https://cdn.alsgp0.fds.api.mi-img.com/micomm/MiFlash2020-3-14-0.rar
And install the USB driver.
And no it's not locked, the Unlocked symbol during Boot is normal. I think it was a bug with older ArrowOS Bootloader versions. Not quite sure.
cyanGalaxy said:
Waiting for any devices means your PC does not detect the phone.
Download this: https://cdn.alsgp0.fds.api.mi-img.com/micomm/MiFlash2020-3-14-0.rar
And install the USB driver.
And no it's not locked, the Unlocked symbol during Boot is normal. I think it was a bug with older ArrowOS Bootloader versions. Not quite sure.
Click to expand...
Click to collapse
IT WORKED. Thank you so much, it was a driver issue but the exact version you gave me didn't work, I had to find another one
So for context I messed up and flashed to boot twrp and now I'm trying to my phone gets out of fastboot but i cant...
So what i did was: "fastboot flash boot_a twrp.img" and "fastboot flash boot_b twrp.img" and now it is stuck on fastboot... so I tried to flash_all.bat from V13.0.8.0.SKHEUXM and V13.0.9.0.SKHEUXM and both gave me this error when this line was executed:
fastboot flash super images\super.img error: cannot load 'images\super.img'
By the way I can still flash twrp into boot and it works but gives many error on mount metadata and root...
So I could use some help to unbrick this phone thank you...
Try the command fastboot continue
Try flashing your ROMs' boot.img in Fastboot.
This tool can dump the individual IMG-files from ROM ZIPs:
[Windows] Payload Dumper GUI - dump boot.img and other img files from payload.bin.
Hello there. Was bored and decided to make a gui that dumps Payload.bin file for easy flashing. Tested on Lineage OS 18 Payload.bin Result: Credits: Based on vm03 payload_dumper script. Github: Payload_dumper.py...
forum.xda-developers.com
Your problem with not being able to run flash_all.bat might be a something with your PC, the SDK Platform Binaries (outdated version?), your USB-cable, your USB-port, or maybe you just need to disconnect/reconnect.
I recommend OrangeFox Recovery: https://orangefox.download/device/alioth
The recovery.img from the ZIP can be booted with fastboot boot recovery.img
Thank for the help guys but I din't try miflash tool tried it and it worked
after flash stock rom using miflash and click clean all and lock , the flashing was successful then the phone was stuck on bootloader and now i cant even turn off the phone, the screen stay in fastboot..what should i do? please help me and tell me what to do step by step cz now the bootloader is locked..
Can you post the Miflash log?
Miflash/log folder, Txt file + or -25kb.
Use spoiler.
If you have a Chinese version (K40s)and you have locked the bootloader on a rom other than Chinese, it comes from that.
bvyral said:
after flash stock rom using miflash and click clean all and lock , the flashing was successful then the phone was stuck on bootloader and now i cant even turn off the phone, the screen stay in fastboot..what should i do? please help me and tell me what to do step by step cz now the bootloader is locked..
Click to expand...
Click to collapse
you know the Steps to Flash StockROM, only look 4 another Firmware, iam Think its Not the Correct
System23 said:
you know the Steps to Flash StockROM, only look 4 another Firmware, iam Think its Not the Correct
Click to expand...
Click to collapse
What do you mean( only look 4 another Firmware)?
NOSS8 said:
What do you mean( only look 4 another Firmware)?
Click to expand...
Click to collapse
you must Flash the Correct Firmware 4 ya Device, when ya have this the Device Boot Corectly after Flash it!! thats why iam Think its not the Correct Firmware you used!!
look here to Find your Firmware Xiamoi Pocco F4 Firmware Archiv
System23 said:
you must Flash the Correct Firmware 4 ya Device, when ya have this the Device Boot Corectly after Flash it!! thats why iam Think its not the Correct Firmware you used!!
Click to expand...
Click to collapse
I'm not the OP.
With the bootloader unlock you can flash any version of stock rom, EEA, Global, etc, and lock the bootloader.
Except if you have a K40S or you have to let the bootloader unlock.
System23 said:
look here to Find your Firmware Xiamoi Pocco F4 Firmware Archiv
Click to expand...
Click to collapse
But i got the firmware from here..i choose poco f4 global fastboot type
NOSS8 said:
I'm not the OP.
With the bootloader unlock you can flash any version of stock rom, EEA, Global, etc, and lock the bootloader.
Except if you have a K40S or you have to let the bootloader unlock.
Click to expand...
Click to collapse
Yea..the bootloader is now locked..what should i do?..and can it be done?..
bvyral said:
Yea..the bootloader is now locked..what should i do?..and can it be done?..
Click to expand...
Click to collapse
Do you have a Poco F4 or a K40S?
Can you post the Miflash log?
Miflash/log folder, Txt file + or -25kb.
Use spoiler
bvyral said:
Yea..the bootloader is now locked..what should i do?..and can it be done?..
Click to expand...
Click to collapse
If you need to leave Fastboot mode, just press and keep a combination of the Power button + the Volume Down for about 10 seconds.
have you any Expierience with Fastboot and the Terminal? than i have Read that your Device has A/B Partitions!!! That means SLOT A has now your Flashed Firmware & SLOT B has the older StockROM!!! Normaly when a Partition is Broken it changes the SLOT Automaticly!!!! with Terminal and fastboot can you Interact with the Device via PC!!!! so that you can use this commands to become the Information witch SLOT is Active, and SET one of the Booth Partitions!!!!
Show Activ SLOT
fastboot getvar current-slot
SET a SLOT
fastboot set_active b
or
fastboot set_active a
Show Activ SLOT
fastboot getvar current-slot
Reboot the Device
fastboot reboot
I have write a simple script that Downloads the Firmware,Extract it,copy Files 4 Flash,and Start Flash!!!
you Found that in my Onlinestorage Here >> Xiaomi_POCCO_F4_Firmware_Flash
Only Download it and extract it!!!
Run "Download_Firmware.cmd" and Connect Device via USB to PC and start it in Fastboot-Mode!!!
The Firmware is
Device: POCO F4 Global
Codename: munch
Version: V14.0.2.0.TLMMIXM
Branch: Stable
Type: Fastboot
Size: 6.3 GB
Release Date: 2023-03-12
Package Name: munch_global_images_V14.0.2.0.TLMMIXM_20230312.0000.00_13.0_global_cad4c8f425.tg
After the Download its extract it and delete the Archives and still 1 Firmware Folder exists!!!
After that its start the "flash_all.bat" that comes with this Firmware!!!! So make sure you have Connected the device via USB
to PC and have started Fastboot-Mode!!
than let it Flash the MIUI ROM!!!! if this Method working the Device will be Start normaly!!!
If this not work use "MIFLASHTOOL" and click on select and choose the Firmware Folder!! and Flash it with this Method!!!!
hope one of the Options will Work!!
System23 said:
have you any Expierience with Fastboot and the Terminal? than i have Read that your Device has A/B Partitions!!! That means SLOT A has now your Flashed Firmware & SLOT B has the older StockROM!!! Normaly when a Partition is Broken it changes the SLOT Automaticly!!!! with Terminal and fastboot can you Interact with the Device via PC!!!! so that you can use this commands to become the Information witch SLOT is Active, and SET one of the Booth Partitions!!!!
Show Activ SLOT
fastboot getvar current-slot
SET a SLOT
fastboot set_active b
or
fastboot set_active a
Show Activ SLOT
fastboot getvar current-slot
Reboot the Device
hope one of the Options will Work!!
Click to expand...
Click to collapse
You cannot use Mi Flash with a locked bootloader.
System23 said:
have you any Expierience with Fastboot and the Terminal? than i have Read that your Device has A/B Partitions!!! That means SLOT A has now your Flashed Firmware & SLOT B has the older StockROM!!! Normaly when a Partition is Broken it changes the SLOT Automaticly!!!! with Terminal and fastboot can you Interact with the Device via PC!!!! so that you can use this commands to become the Information witch SLOT is Active, and SET one of the Booth Partitions!!!!
Show Activ SLOT
fastboot getvar current-slot
SET a SLOT
fastboot set_active b
or
fastboot set_active a
Show Activ SLOT
fastboot getvar current-slot
Reboot the Device
fastboot reboot
I have write a simple script that Downloads the Firmware,Extract it,copy Files 4 Flash,and Start Flash!!!
you Found that in my Onlinestorage Here >> Xiaomi_POCCO_F4_Firmware_Flash
Only Download it and extract it!!!
Run "Download_Firmware.cmd" and Connect Device via USB to PC and start it in Fastboot-Mode!!!
The Firmware is
Device: POCO F4 Global
Codename: munch
Version: V14.0.2.0.TLMMIXM
Branch: Stable
Type: Fastboot
Size: 6.3 GB
Release Date: 2023-03-12
Package Name: munch_global_images_V14.0.2.0.TLMMIXM_20230312.0000.00_13.0_global_cad4c8f425.tg
After the Download its extract it and delete the Archives and still 1 Firmware Folder exists!!!
After that its start the "flash_all.bat" that comes with this Firmware!!!! So make sure you have Connected the device via USB
to PC and have started Fastboot-Mode!!
than let it Flash the MIUI ROM!!!! if this Method working the Device will be Start normaly!!!
If this not work use "MIFLASHTOOL" and click on select and choose the Firmware Folder!! and Flash it with this Method!!!!
hope one of the Options will Work!!
Click to expand...
Click to collapse
not working...error:FAILED (remote: Erase is not allowed in Lock State)
OK, original Tools and Firmware cannot Flash in locked BL!! than you can Flash in Recovery or in EDL Mode!! you stuck at Fastboot Mode so you cant Flash via Recovery!!! or you use fastboot in Terminal and test the following commands!!!
Boot Recovery via fastboot
fastboot boot xxx/Images/recovery.img
or
Reboot Recovery
fastboot reboot recovery
or
Flash Boot/Recovery
fastboot flash boot xxx/Images/boot.img
fastboot flash recovery xxx/Images/recovery.img
fastboot reboot
when this not working you can use EDL-Mode!!!
Poco F4 test Point Reboot 9008 EDL - ROM-Provider
Poco F4 test point is typically a set of pins on the device's circuit board that can be shorted together in order to put the device into edl mod
romprovider.com
Than you can Flash it with QPST or QFiL Tool from Qualcomm!!! but i must look when i at home if the fastboot Firmware includes all needed Files!!! rawprogrammer0.xml patch0.xml firehosexxxx.mbn
System23 said:
OK, original Tools and Firmware cannot Flash in locked BL!! than you can Flash in Recovery or in EDL Mode!! you stuck at Fastboot Mode so you cant Flash via Recovery!!! or you use fastboot in Terminal and test the following commands!!!
Click to expand...
Click to collapse
Stop posting non-solutions.
Miflash unusable with the bootloader locked. (Yet noted on the OP).
Regarding your last post, the command syntax is wrong and it will not change anything.
For EDL mode, you don't know, it is not necessary to open the phone to enter EDL mode and anyway, it will not have permission to flash.
QPST or QFiL Tool from Qualcomm may work but not on this device (too recent) and Sahara is a very sensitive program and requires some experience to avoid errors such as:
ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.
ERROR: function: sahara_main:983 Sahara protocol error
ERROR: function: main:320 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail process fail.
Poco F4 (Munch) Firmware Flash File (Stock ROM) - ROM-Provider
Download Poco F4 Firmware Flash File stock ROM, here we share latest firmware for Xiaomi Poco F4 with flash tool & usb driver
www.google.de
with MiFlash in EDL-Mode and the EDL-Firmware GLO, its like this Article a working Solution!! and i dont know if fastboot reboot edl with special edl fastboot work, and I dont know if it can Start with ButtonsCombo!!! adb reboot edl is not availible wile stuck at Fastboot-Mode!! iam only give ideas to test them out, in variants they i know!! Iam Testing my variants out to find a way that works!!!
NOSS8 said:
Stop posting non-solutions.
Miflash unusable with the bootloader locked. (Yet noted on the OP).
Regarding your last post, the command syntax is wrong and it will not change anything.
For EDL mode, you don't know, it is not necessary to open the phone to enter EDL mode and anyway, it will not have permission to flash.
QPST or QFiL Tool from Qualcomm may work but not on this device (too recent) and Sahara is a very sensitive program and requires some experience to avoid errors such as:
ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.
ERROR: function: sahara_main:983 Sahara protocol error
ERROR: function: main:320 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail process fail.
Click to expand...
Click to collapse
give me more Input, iam intressted to read more!!!
System23 said:
give me more Input, iam intressted to read more!!!
Click to expand...
Click to collapse
This is not the subject of the thread. (do some research).
If it is impossible to enter recovery or fastboot mode and if it is not a HW problem, the phone is in EDL Mode.
It will not appear on the PC unless you install the Qualcomm drivers and will be detected by Miflash (in Fastboot mode, no need to log in) on a com port (login mandatory), but you will not have permission to flash (requires a special account).
This permission is not needed on very old devices.
Until the OP has answered my questions, I could not provide him with a possible solution.
System23 said:
have you any Expierience with Fastboot and the Terminal? than i have Read that your Device has A/B Partitions!!! That means SLOT A has now your Flashed Firmware & SLOT B has the older StockROM!!! Normaly when a Partition is Broken it changes the SLOT Automaticly!!!! with Terminal and fastboot can you Interact with the Device via PC!!!! so that you can use this commands to become the Information witch SLOT is Active, and SET one of the Booth Partitions!!!!
Show Activ SLOT
fastboot getvar current-slot
SET a SLOT
fastboot set_active b
or
fastboot set_active a
Show Activ SLOT
fastboot getvar current-slot
Reboot the Device
fastboot reboot
I have write a simple script that Downloads the Firmware,Extract it,copy Files 4 Flash,and Start Flash!!!
you Found that in my Onlinestorage Here >> Xiaomi_POCCO_F4_Firmware_Flash
Only Download it and extract it!!!
Run "Download_Firmware.cmd" and Connect Device via USB to PC and start it in Fastboot-Mode!!!
The Firmware is
Device: POCO F4 Global
Codename: munch
Version: V14.0.2.0.TLMMIXM
Branch: Stable
Type: Fastboot
Size: 6.3 GB
Release Date: 2023-03-12
Package Name: munch_global_images_V14.0.2.0.TLMMIXM_20230312.0000.00_13.0_global_cad4c8f425.tg
After the Download its extract it and delete the Archives and still 1 Firmware Folder exists!!!
After that its start the "flash_all.bat" that comes with this Firmware!!!! So make sure you have Connected the device via USB
to PC and have started Fastboot-Mode!!
than let it Flash the MIUI ROM!!!! if this Method working the Device will be Start normaly!!!
If this not work use "MIFLASHTOOL" and click on select and choose the Firmware Folder!! and Flash it with this Method!!!!
hope one of the Options will Work!!
Click to expand...
Click to collapse
thanks, after managing to unlock the phone just by moving it to local disk c, after some googling n youtubing, and i tried ur method again ,editing some flash_all bat.((
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *munch" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *munch" || exit /B 1))
and run it....it works.. i sincerely thanks you..