Hey Guys I need your help.
I think I bricked my OnePlus 3. (BTW yes its unlocked)
What still works:
1. Fastboot
2. TWRP and Stock recovery
3. ADB Sideload
I use twrp 3.1.0-0
Fastboot looks like this:
FASTBOOT MODE
PRODUCT_NAME: msm8996
VARIANT - MTP UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMER - [censored]
SECURE BOOT - enabled
DEVICE STATE - unlocked
But I cant boot into any system. I think I corrupted the /data partition or sth.
What I tried:
1. Flashing boot.img and system.img via fastboot -> Result: Still won't boot. I get the Oneplus and android logo and a blackscreen after this.
2. Flashing stock rom / lineage rom / newest stock rom via TWRP Sideload or Stock-recovery Sideload -> TWRP gives me this error: Updater process ended with ERROR: 7
Any Ideas?
Premaider said:
Hey Guys I need your help.
I think I bricked my OnePlus 3. (BTW yes its unlocked)
What still works:
1. Fastboot
2. TWRP and Stock recovery
3. ADB Sideload
I use twrp 3.1.0-0
Fastboot looks like this:
FASTBOOT MODE
PRODUCT_NAME: msm8996
VARIANT - MTP UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMER - [censored]
SECURE BOOT - enabled
DEVICE STATE - unlocked
But I cant boot into any system. I think I corrupted the /data partition or sth.
What I tried:
1. Flashing boot.img and system.img via fastboot -> Result: Still won't boot. I get the Oneplus and android logo and a blackscreen after this.
2. Flashing stock rom / lineage rom / newest stock rom via TWRP Sideload or Stock-recovery Sideload -> TWRP gives me this error: Updater process ended with ERROR: 7
Any Ideas?
Click to expand...
Click to collapse
Flash stock recovery and flash stock oos
v.konvict said:
Flash stock recovery and flash stock oos
Click to expand...
Click to collapse
says "installation failed" when I try to install stock oos on stock recovery via adb sideload
edit: If I manually flash (via fastboot) boot.img and system.img and then twrp recovery twrp says I do not have a system installed. why that?
edit2: while flashing system.img it first says "Invalid sparse file format at header magi" but then continues normally. does this help?
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
try this
save all your data before
Spector_Prophet said:
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
try this
save all your data before
Click to expand...
Click to collapse
He could also try the one that flashes OxygenOS 4.0.3: Newer unbrick tool
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 versionP - 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_sproutbuild_number=V12.0.11.0.RFQMIXMuserdata_version=20210615.0000.00
Full Fastboot Android 11 ROM Global version with May 2021 Security patch (V12.0.9.0.RFQMIXM)device=laurel_sproutbuild_number=V12.0.9.0.RFQMIXMuserdata_version=20210506.0000.00Full Fastboot Android 11 ROM Global version with April 2021 Security patch (V12.0.8.0.RFQMIXM)device=laurel_sproutbuild_number=V12.0.8.0.RFQMIXMuserdata_version=20210409.0000.00
Full Fastboot Android 10 ROM Global version with November 2020 Security patch (V11.0.23.0.QFQMIXM)device=laurel_sproutbuild_number=V11.0.23.0.QFQMIXMuserdata_version=20201124.0000.00
Full Fastboot Android 10 ROM Global version with October 2020 Security patch (V11.0.22.0.QFQMIXM)device=laurel_sproutbuild_number=V11.0.22.0.QFQMIXMuserdata_version=20201017.0000.00
Full Fastboot Android 10 ROM Global version with September 2020 Security patch (V11.0.21.0.QFQMIXM)device=laurel_sproutbuild_number=V11.0.21.0.QFQMIXMuserdata_version=20200917.0000.00
Full Fastboot Android 10 ROM Global version with August 2020 Security patch (V11.0.20.0.QFQMIXM)device=laurel_sproutbuild_number=V11.0.20.0.QFQMIXMuserdata_version=20200804.0000.00
Full Fastboot Android 10 ROM Global version with July 2020 Security patch (V11.0.19.0.QFQMIXM)device=laurel_sproutbuild_number=V11.0.19.0.QFQMIXMuserdata_version=20200717.0000.00
Full Fastboot Android 10 ROM Global version with June 2020 Security patch (V11.0.16.0.QFQMIXM)device=laurel_sproutbuild_number=V11.0.16.0.QFQMIXMuserdata_version=20200623.0000.00
Full Fastboot Android 10 ROM Global version with May 2020 Security patch (V11.0.15.0.QFQMIXM)device=laurel_sproutbuild_number=V11.0.15.0.QFQMIXMuserdata_version=20200507.0000.00
Full Fastboot ROM Global version with March 2020 Security patch (V10.3.16.0.PFQMIXM)device=laurel_sproutbuild_number=V10.3.16.0.PFQMIXMuserdata_version=20200324.0000.00
Full Fastboot ROM Global version with January 2020 Security patch (V10.3.13.0.PFQMIXM)device=laurel_sproutbuild_number=V10.3.13.0.PFQMIXMuserdata_version=20200116.0000.00
Full Fastboot ROM Global version with November Security patch (V10.3.9.0.PFQMIXM)device=laurel_sproutbuild_number=V10.3.9.0.PFQMIXMuserdata_version=20191107.0000.00
Full Fastboot ROM Global version with October Security patch (V10.3.8.0.PFQMIXM)device=laurel_sproutbuild_number=V10.3.8.0.PFQMIXMuserdata_version=20191012.0000.00
Full Fastboot ROM Global version with August Security patch (V10.3.4.0.PFQMIXM)device=laurel_sproutbuild_number=V10.3.4.0.PFQMIXMuserdata_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_sproutbuild_number=V12.0.7.0.RFQEUXMuserdata_version=20210513.0000.00
Full Fastboot Android 11 ROM EU version with April 2021 Security patch (V12.0.6.0.RFQEUXM)device=laurel_sproutbuild_number=V12.0.6.0.RFQEUXMuserdata_version=20210415.0000.00
Full Fastboot Android 11 ROM EU version with March 2021 Security patch (V12.0.5.0.RFQEUXM)device=laurel_sproutbuild_number=V12.0.5.0.RFQEUXMuserdata_version=20210311.0000.00Full Fastboot Android 11 ROM EU version with January 2021 Security patch (V12.0.3.0.RFQEUXM)device=laurel_sproutbuild_number=V12.0.3.0.RFQEUXMuserdata_version=20210129.0000.00
Full Fastboot Android 10 ROM EU version with November 2020 Security patch (V11.0.10.0.QFQEUXM)device=laurel_sproutbuild_number=V11.0.10.0.QFQEUXMuserdata_version=20201125.0000.00
Full Fastboot Android 10 ROM EU version with October 2020 Security patch (V11.0.9.0.QFQEUXM)device=laurel_sproutbuild_number=V11.0.9.0.QFQEUXMuserdata_version=20201019.0000.00
Full Fastboot Android 10 ROM EU version with September 2020 Security patch (V11.0.8.0.QFQEUXM)device=laurel_sproutbuild_number=V11.0.8.0.QFQEUXMuserdata_version=20200926.0000.00
Full Fastboot Android 10 ROM EU version with August 2020 Security patch (V11.0.6.0.QFQEUXM)device=laurel_sproutbuild_number=V11.0.6.0.QFQEUXMuserdata_version=20200817.0000.00
Full Fastboot Android 10 ROM EU version with July 2020 Security patch (V11.0.5.0.QFQEUXM)device=laurel_sproutbuild_number=V11.0.5.0.QFQEUXMuserdata_version=20200723.0000.00
Full Fastboot Android 10 ROM EU version with June 2020 Security patch (V11.0.3.0.QFQEUXM)device=laurel_sproutbuild_number=V11.0.3.0.QFQEUXMuserdata_version=20200611.0000.00
Full Fastboot Android 10 ROM EU version with May 2020 Security patch (V11.0.2.0.QFQEUXM)device=laurel_sproutbuild_number=V11.0.2.0.QFQEUXMuserdata_version=20200512.0000.00
Full Fastboot Android 10 ROM EU version with April 2020 Security patch (V11.0.1.0.QFQEUXM)device=laurel_sproutbuild_number=V11.0.1.0.QFQEUXMuserdata_version=20200424.0000.00
Full Fastboot ROM EU version with March 2020 Security patch (V10.3.17.0.PFQEUXM)device=laurel_sproutbuild_number=V10.3.17.0.PFQEUXMuserdata_version=20200325.0000.00
Full Fastboot ROM EU version with February 2020 Security patch (V10.3.15.0.PFQEUXM)device=laurel_sproutbuild_number=V10.3.15.0.PFQEUXMuserdata_version=20200220.0000.00
Full Fastboot ROM EU version with January 2020 Security patch (V10.3.14.0.PFQEUXM)device=laurel_sproutbuild_number=V10.3.14.0.PFQEUXMuserdata_version=20200116.0000.00
Full Fastboot ROM EU version with December Security patch (V10.3.13.0.PFQEUXM)device=laurel_sproutbuild_number=V10.3.13.0.PFQEUXMuserdata_version=20191211.0000.00
Full Fastboot ROM EU version with November Security patch (V10.3.12.0.PFQEUXM)device=laurel_sproutbuild_number=V10.3.12.0.PFQEUXMuserdata_version=20191113.0000.00
Full Fastboot ROM EU version with August Security patch (V10.3.7.0.PFQEUXM)device=laurel_sproutbuild_number=V10.3.7.0.PFQEUXMuserdata_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?
********
Don't flash the patched boot, boot it and use Magisk manager to install (direct). It will flash the correct boot partition for you.
Hello, I'm trying to install magisk and ramdisk says 'no', I tried some different versions and HIDE magisk I'm having the same problem
safetynet into magisk says :
basicIntegrity -
ctsprofile -
evaltype HARDWARE
safetynet googleplay version says:
mi 9 se fail
safetynet request success
response signature validation fail (response payload validation failed )
my room is the global stock 12.0.4.0 QFBEUXM
my twrp is twrp-3.5.2_9-0-grus.img
my bootloader is unlock
android version 10
I downloaded the firmware, extract the boot.img , patched it through magisk and flash via fastbot, but still RAMDISK says NOT ..
= /
i'm lost
any solutionS?
THANKS <3
Hello, I want to root my device and install magisk. This is my device:
xiaomi redmi note 8 pro (begonia)
Miui Global Stable 12.5.7.0 (RGGEUXM)
Android Version: 11 RP1A.200720.011
Bootloader: unlocked
I flashed twrp with BRP3.5.2v3.1.
Code:
ECHO Recovery for Miui 12.5 Android 11
fastboot flash recovery BRP3.5.2v3.1.img
fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
fastboot reboot recovery
I installed contained Magisk-v22103.zip via twrp > advanced > install magisk. TWRP flashing window shows Magisk 23.0 Installer.
Then Wipe Cache / Dalvic. Then > advanced > close avb 2.0.
Then Wipe Cache / Dalvic. Then Reboot System.
Starting magisk app shows version 23.0 (23000) paket com.topjohnwu.magisk.
Status SafetyNet check: basicIntegrity negative, ctsProfile negative, evalType Hardware.
I followed two guides with loading magisk modules MagiskHide_Props_Config-v6.1.2-v137(75), Riru-v26.1.4.r522.8b379cedb5(522).zip, safetynet-fix-v2.1.1.zip and safetynet-fix-v2.2.1.zip, Busybox_for_Android_NDK-1.34.1(13411).zip.
I installed Termux app, hit commands su + setenforce 0. I did fingerprinting Google Pixel 5 and 4a.
Both these guides not helped passing the safetynet check, since
Status SafetyNet check: basicIntegrity positive, ctsProfile negative, evalType Hardware.
While Magisk-v22103.zip has SafetyNet check, Magisk-25.2.zip doesn't have and Magisk-25.2.zip is not able to load any modules by internet but just by 'install from storage'.
Why is it like that and what should I do to install magisk properly passing the safetynet check?