Related
Hello guys,
my Oneplus 3 is hard bricked, I tried the methods in the Mega Unbrick guide, my device already gets shown as Qualcomm 9008 ... in Device Manager, so I started the MSM DownloadTool and it flashed anything without errors. But when the phone reboots I get a black screen and the white led is on.
I can't even boot to stock recovery (Volume down + power doesn't work and rebooting to recovery through fastboot doesn't work, too....) my bootloader is locked and all attempts to unlock the bootloader are failing with the error "remote: oem unlock is not allowed"
So at the moment I'm stuck in fastboot and nothing else works -.-
Can someone please help me?
The unbrick tool has an old firmware, can I replace the files with files from a newer firmware?
Thanks!
Have you tried the exact steps from Method 2? Maybe unzip it? If that doesn't work which is highly unlikely then there is not much you can do.
Puddi_Puddin said:
Have you tried the exact steps from Method 2? Maybe unzip it? If that doesn't work which is highly unlikely then there is not much you can do.
Click to expand...
Click to collapse
Yeah I tried it as I said, the MSM DownloadTool showed me Completed and the phone tried to boot up after that.
I'm now contacting the OP Customer Support, I've read a few times that they have other files to unbrick the phone with the MSM Tool.
min-dfreak said:
Yeah I tried it as I said, the MSM DownloadTool showed me Completed and the phone tried to boot up after that.
I'm now contacting the OP Customer Support, I've read a few times that they have other files to unbrick the phone with the MSM Tool.
Click to expand...
Click to collapse
Ye thats the only thing you can currently do... May i ask what you have done how did it get bricked?
I just updated AICP ota and after flashing the update my phone didn't boot up. The screen went black immediately.
So I thought that it is maybe a Problem with the ROM and I tried to go back to stock.
Flashed the stock recovery and locked the bootloader, but I couldn't boot to the stock recovery.
There it started...
Switch off the phone, connect usb ,open unbrick tool full ( method 2),Press vol up,down and power buttons same time ,tool will recognize phone then start , you must unbrick now.
NEVER LOCK YOUR PHONE.
drmuruga said:
Switch off the phone, connect usb ,open unbrick tool full ( method 2),Press vol up,down and power buttons same time ,tool will recognize phone then start , you must unbrick now.
NEVER LOCK YOUR PHONE.
Click to expand...
Click to collapse
Please read, I already did that.
The tool completed it successfully, but still black screen after a reboot.
Only the LED is flashing white.
I already contacted the support, they will do it remotely tomorrow.
min-dfreak said:
Please read, I already did that.
The tool completed it successfully, but still black screen after a reboot.
Only the LED is flashing white.
I already contacted the support, they will do it remotely tomorrow.
Click to expand...
Click to collapse
Never but never lock your bootloader...
If recovery, boot or system partition is modified. There's no harm in re locking otherwise..
Hi guy i have a big problem i buy a one plus 3 i was using it 1 month and there was a update i don't remember what it was oreo or nougat when the update downloaded i install it and the i got a bootloop 2 hours didn't boot and my device is not rooted and didn't enable developer option i tried to install stock rom by adb and fastboot with sideload it load but it stuck on 50% then it say failed tried to install recovery in fastboot i installed drive oneplus 3 ect but can't flash it i think because i have oem locked i trien to unlocked it says failed 00.6s ect and i don't have guarantee i have dash and cable charger i can charge it and go to fastboot and recovery but when i boot my phone normally i show logo one plus then the two red bullet who move then it power off
Dsn Fouad said:
Hi guy i have a big problem i buy a one plus 3 i was using it 1 month and there was a update i don't remember what it was oreo or nougat when the update downloaded i install it and the i got a bootloop 2 hours didn't boot and my device is not rooted and didn't enable developer option i tried to install stock rom by adb and fastboot with sideload it load but it stuck on 50% then it say failed tried to install recovery in fastboot i installed drive oneplus 3 ect but can't flash it i think because i have oem locked i trien to unlocked it says failed 00.6s ect and i don't have guarantee i have dash and cable charger i can charge it and go to fastboot and recovery but when i boot my phone normally i show logo one plus then the two red bullet who move then it power off
Click to expand...
Click to collapse
I'm assuming your device is OnePlus3 and not 3T
Okay. Firstly give a try to Oneplus3 openbeta Nougat special edition.
Oneplus3 : http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Method 1 : specific recovery for open beta24 available in Oneplus downloads
https://downloads.oneplus.com
Find legacy roms and find openbeta 24
Method 2: latest TWRP
If your bootloader is locked this isn't gonna work. But if it is still in unlocked .
Download TWRP for Oneplus3 from official TWRP site
Flash the recovery you choose using fast boot.
Now using asn command, try to flash the special edition.
Mostly this solves your issue. It helped me.
Let me know whether you face any issues.
Note: in this method you may lose every data you have on the phone. It boots up (if at all ? ) with fresh firmware and fresh storage (sometimes)
SivaMaxwell said:
I'm assuming your device is OnePlus3 and not 3T
Okay. Firstly give a try to Oneplus3 openbeta Nougat special edition.
Oneplus3 : http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Method 1 : specific recovery for open beta24 available in Oneplus downloads
https://downloads.oneplus.com
Find legacy roms and find openbeta 24
Method 2: latest TWRP
If your bootloader is locked this isn't gonna work. But if it is still in unlocked .
Download TWRP for Oneplus3 from official TWRP site
Flash the recovery you choose using fast boot.
Now using asn command, try to flash the special edition.
Mostly this solves your issue. It helped me.
Let me know whether you face any issues.
Note: in this method you may lose every data you have on the phone. It boots up (if at all ? ) with fresh firmware and fresh storage (sometimes)
Click to expand...
Click to collapse
Yeah i have oneplus 3 my bootloader is locked can't flash anything im going to try method 1
By the way why beta 24 why not lastest update ? And whene i download it do you want me to flash it with sideload like #adb sideload openbeta24.zip ?
Dsn Fouad said:
Yeah i have oneplus 3 my bootloader is locked can't flash anything im going to try method 1
By the way why beta 24 why not lastest update ? And whene i download it do you want me to flash it with sideload like #adb sideload openbeta24.zip ?
Click to expand...
Click to collapse
The file I gave link to is a special edition by Oneplus for Openbeta-Nougat. You can go to Nougat from any rom.
Rom: http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Specific recovery should be downloaded from Oneplus website.
You can sideload using adb or store internal storage and flash.
I tried with latest TWRP recently and it worked.
Note that all your data gets wiped if you use oneplus-recovey and asn sideload
SivaMaxwell said:
The file I gave link to is a special edition by Oneplus for Openbeta-Nougat. You can go to Nougat from any rom.
Rom: http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Specific recovery should be downloaded from Oneplus website.
You can sideload using adb or store internal storage and flash.
I tried with latest TWRP recently and it worked.
Note that all your data gets wiped if you use oneplus-recovey and asn sideload
Click to expand...
Click to collapse
The problem is i dont have store internal storage and when i try to flash anything it say oem locked not allowed and when i flash a rom with adb sideload jfjd.zip it stuck on 60% will it be complete if i use your beta ?
Dsn Fouad said:
The problem is i dont have store internal storage and when i try to flash anything it say oem locked not allowed and when i flash a rom with adb sideload jfjd.zip it stuck on 60% will it be complete if i use your beta ?
Click to expand...
Click to collapse
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
SivaMaxwell said:
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
Click to expand...
Click to collapse
Thanks i will download and give it a try
SivaMaxwell said:
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
Click to expand...
Click to collapse
Before that i downloaded msm download tool 3.0.8 i tested it and it boot but it say enter pin password i dont know what is the pin i didn't use a pin before it was working
Dsn Fouad said:
Before that i downloaded msm download tool 3.0.8 i tested it and it boot but it say enter pin password i dont know what is the pin i didn't use a pin before it was working
Click to expand...
Click to collapse
Simply reboot to recovery and say yes to wipe every data.
Note1:
all your internal data is wiped in the method I suggested. I can recall there is a method to recover data only if bootloader is unlocked. If your bootloader is locked there is no other way.
Note2: your data will be formatted to f2fs file system. If you want to flash any custom ROM, YOU SHOULD CHECK COMPATIBILITY WITH F2FS in that ROM forums.
It's better to always have EXT4 file system. You can change this file system with TWRP
SivaMaxwell said:
Simply reboot to recovery and say yes to wipe every data.
Note1:
all your internal data is wiped in the method I suggested. I can recall there is a method to recover data only if bootloader is unlocked. If your bootloader is locked there is no other way.
Note2: your data will be formatted to f2fs file system. If you want to flash any custom ROM, YOU SHOULD CHECK COMPATIBILITY WITH F2FS in that ROM forums.
It's better to always have EXT4 file system. You can change this file system with TWRP
Click to expand...
Click to collapse
Bootloader is locked i tryed to flash the 24 beta yoi give me but it stuck on 47 and say failed im just going to sell it
Dsn Fouad said:
Bootloader is locked i tryed to flash the 24 beta yoi give me but it stuck on 47 and say failed im just going to sell it
Click to expand...
Click to collapse
Even if the bootloader is locked, you can boot into the current rom and unlock simply by going to advanved options.
It is a very simple process.
hello,
i have a problem with my redmi note 5 whyred.
it's a global.
I had unlocked, installed twrp, tried some custom roms, but i wanted to come back to miui, so i have flashed by miflash, and and unfortunately I forgot to tick the box "flash all" , then it has relock (with twrp and custom rom)...
Now i have the rom beta global 8.10.11 , it works well but when i try to re-unlock by miunlock tool, it stop at 99% with " couldn't unlock error (-1)"
I have enabled developper options, oem unlock, usb debugging, etc... tried some differents drivers and differents computer with windows 7 or 10, some mi-unlock versions.... but it always stop at 99%
someone could help me? thanks
tofclaire said:
hello,
i have a problem with my redmi note 5 whyred.
it's a global.
I had unlocked, installed twrp, tried some custom roms, but i wanted to come back to miui, so i have flashed by miflash, and and unfortunately I forgot to tick the box "flash all" , then it has relock (with twrp and custom rom)...
Now i have the rom beta global 8.10.11 , it works well but when i try to re-unlock by miunlock tool, it stop at 99% with " couldn't unlock error (-1)"
I have enabled developper options, oem unlock, usb debugging, etc... tried some differents drivers and differents computer with windows 7 or 10, some mi-unlock versions.... but it always stop at 99%
someone could help me? thanks
Click to expand...
Click to collapse
did you bind account in developers options?
yes of course, i have already unlocked several xiaomi...i don't understand this error...
I think it's related to having re-locked with twrp and a custom rom, but i don't know what to do for re-unlocking now... however the rom 8.11.8 works well...
tofclaire said:
I think it's related to having re-locked with twrp and a custom rom, but i don't know what to do for re-unlocking now... however the rom 8.11.8 works well...
Click to expand...
Click to collapse
Can you try to run the unlocking tool as an Administrator?
yes, and tried with differents drivers, and with or without unsigned ,windows 7 or 10...
tofclaire said:
yes, and tried with differents drivers, and with or without unsigned ,windows 7 or 10...
Click to expand...
Click to collapse
As admin did not work?
Try an earlier version of the tool...sometimes it helps as they introduce changes...
not works as admin and i ve tried several older versions... ? and several computer...
however my mi account works well...i can locate my device etc...
any advices? ?
Try accessing EDL mode.
tofclaire said:
any advices?
Click to expand...
Click to collapse
well
can you try
1. fastboot boot recovery.img ? (use orangefox recovery)
and ... try flashing "recovery.img" TAKEN FROM FASTBOOT ROM of the MIUI (same version u are running now)
OR
2. flash fasboot rom, WIPE ALL , this will restore the original recovery and try unlocking the fone now!
Nitin890 said:
Try accessing EDL mode.
Click to expand...
Click to collapse
edl mode is locked now with locked bootloader (since rom 8.1), no?
YasuHamed said:
well
can you try
1. fastboot boot recovery.img ? (use orangefox recovery)
and ... try flashing "recovery.img" TAKEN FROM FASTBOOT ROM of the MIUI (same version u are running now)
OR
2. flash fasboot rom, WIPE ALL , this will restore the original recovery and try unlocking the fone now!
Click to expand...
Click to collapse
can't flash fastboot rom by miflah , it says "no allowed with locked bootloader... i will try your "1." but i can boot on orangefox if my bootloader is locked ?
i have already miui recovery
tofclaire said:
edl mode is locked now with locked bootloader (since rom 8.1), no?
Click to expand...
Click to collapse
Here are somethings u may try:
Reinstall mi unlock with latest one.
Check all the drivers.
Ensure that ur phone and pc must be on same Ip address before unlocking.
If using windows 10 you must turn off signed driver verification by pressing and holding shift key while rebooting pc selecting troubleshoot startup ( summit like that) then signed driver verification off its option 7 ( pressing f7 to select) when pc reboots install driver again this time a message pops up and says driver unsigned do you wish install select install anyway now when running the unlock program( as administrator).
I hope these things will help otherwise wait for 7 to 9 days and then try unlocking.
Nitin890 said:
Here are somethings u may try:
Reinstall mi unlock with latest one.
Check all the drivers.
Ensure that ur phone and pc must be on same Ip address before unlocking.
If using windows 10 you must turn off signed driver verification by pressing and holding shift key while rebooting pc selecting troubleshoot startup ( summit like that) then signed driver verification off its option 7 ( pressing f7 to select) when pc reboots install driver again this time a message pops up and says driver unsigned do you wish install select install anyway now when running the unlock program( as administrator).
I hope these things will help otherwise wait for 7 to 9 days and then try unlocking.
Click to expand...
Click to collapse
how can i check if phone and pc are on same ip ?
no more luck...always "couldn't unlock" ....
i don't understand... even i have re-locked by flashing miui with twrp and a custom rom, my phone works well. I have miui recovery, i have re-flashed miui with recovery miui assistant and mi pc suite. I can reset by miui recovery, i can update all friday the beta rom, my miui account is ok for unlocking...
tofclaire said:
how can i check if phone and pc are on same ip ?
Click to expand...
Click to collapse
Connect pc and phone to same network then bind ur phone to account and try unlocking.
Hope this works.
Have flashed custom ROMs on devices in they past but so far have stuck with stock on my Mi Max 3.
Now I am thinking do I take the leap into custom ROMs again, if so what advantages do they offer the Mi Max 3 and which is the best one to flash ?
Cheerz guys'n'gals
Mark
elio321 said:
Have flashed custom ROMs on devices in they past but so far have stuck with stock on my Mi Max 3.
Now I am thinking do I take the leap into custom ROMs again, if so what advantages do they offer the Mi Max 3 and which is the best one to flash ?
Cheerz guys'n'gals
Mark
Click to expand...
Click to collapse
Have you unlocked bootloader yet and flashed recovery? If not, i can tell you the steps because its a little bit tricky to get the Mi Max 3 going.
Wmateria said:
Have you unlocked bootloader yet and flashed recovery? If not, i can tell you the steps because its a little bit tricky to get the Mi Max 3 going.
Click to expand...
Click to collapse
No I have not unlocked the bootloader or flashed recovery yet.. I would be very grateful for a step by step guide please
Thank you
Mark
elio321 said:
No I have not unlocked the bootloader or flashed recovery yet.. I would be very grateful for a step by step guide please
Thank you
Mark
Click to expand...
Click to collapse
Its really simple:
****Prerequisite****
When you have the bootloader unlocked...
Then you can proceed to page 5 of the AOSiP Rom thread. Here's download link from the thread.
https://drive.google.com/open?id=1-1mAQMRX8T34ya4z_IEL69tiyto5A95w
Minimal ADB and Fastboot program should work for USB Debugging, i think you should know that already since you flashed before. Oh and make sure you put the Recovery file in the directory where you will enter Fastboot Flash Recovery (Recovery name).img when using the program, or the program of your choice, etc.
Note: Make sure you get a USB 2.0 adapter in case connecting device via bootloader does not work after entering command: adb reboot bootloader... and fastboot devices (most newer pc's may not read the device while running adb program, check connection with "adb devices" (phone on) and "fastboot devices" (bootloader)
If all is good, lets get to it.
Step 1: Press and hold power + volume down to enter bootloader
Step 2: enter: fastboot flash recovery (recovery name).img
Wait... ... ... ...
Step 3: enter: fastboot boot (recovery name).img
Wait some more ... .... ......... .........
Be patient and the rocovery should prompt you, make sure you have the language in english... disregard the enter password for now in cace it pops up, just press cancel.
Step: 4 Now... Go to wipe/advanced wipe/ and repair/change partitions, press on DATA and change the Data Partition to EXT4....now encryption is disabled. DO NOT REBOOT. Stay on recovery. I think you can mount usb device to put rom files to the phone, but use a Micro SD Card just in case.
Steo 5: Now you can flash a Rom.. to flash a its required to flash miui firmware so for example, a Rom like AOSiP or Lineage OS on page 1 will ask you to (in that order):
°flash required firmware 9.6.27
°the Rom (latest build)
°GApps
°Magisk 19.3
In case any errors in flashing, change DATA partition to EXT2 and back to EXT 4. And wipe system, internal, cahces.
Otherwise.... You did it!!!!
After using your phone for a bit, you can go back to recovery: Nijel's TWRP Recovery or Orange Recovery 10 which just came out. Do not use, official recovery from TWRP.
Side note: To get to recovery manually, hold volume up + power. Wait until the Xiaomi splash animation immediately dims and let go of power button.
I did Custom Rons on Mi Max 2 and always came back to Miui.
Mi Max 3, with active ARB, is more complicated, because if necessary roolback is a problem.
Xiaomi.eu works well and has frequent updates, but be careful.
sfairmm said:
I did Custom Rons on Mi Max 2 and always came back to Miui.
Mi Max 3, with active ARB, is more complicated, because if necessary roolback is a problem.
Xiaomi.eu works well and has frequent updates, but be careful.
Click to expand...
Click to collapse
I've so far only gone Xiaomi.eu on my Mi Max 3 and have no complaints.. easy to update and as above, regular updates that are working well.. but once support is dropped.. I'll consider a custom.
TLDR below
Some of the backstory of this device:
This is my girlfriend's first android device, tried so hard to convince her to switch from iPhone to Android, I finally managed to convince her, but... this happened...
So since this is not my device and I wanted a pure Android 12 experience (which I bragged about), I installed Pixel Extended Android 12 Beta to the device. (Only android 12 experience that I got during that time)
This is what I did,
Unlocked the bootloader after 7 days ( using Miunlocktool )
With the phone still in factory firmware, I used pixel extended's recovery image which is located here https://sourceforge.net/projects/pex-alioth/files/1-11-21/
Steps that I did ( fastboot flash boot boot.img > fastboot flash vendor_boot vendor_boot.img > fastboot reboot recovery > Format data > adb sideload PEX.zip > Reboot )
After rebooting, the phone is now in PEX4.0 beta and she proceed to use the devices for several months after PixelExperience released their stable ROM for OTA updates and zero maintenance from my side.
When PixelExperience released their stable ROM, took her phone, trying to shut down the phone so I can go into fastboot and I realized that the phone isn't powering on at all which no display, plugged into my PC, no USB indicator as well.
The phone is dead from a shutdown which shocked me. My guess initially is some kind of electric damage that ruined the motherboard. So I sent this to Xiaomi's service center to get this fixed.
After picking up the phone from the service center yesterday, I have been told that the phone is hard bricked and not some kind of faulty hardware. I am pretty sure they reflashed the firmware with Xiaomi flash tool and it is now running on the global ROM 12.5, with an unlocked bootloader
Feeling weird at the hard brick, I thought I messed up somewhere.
On my second attempt to install PixelExperience, I managed to go into fastboot and sideloaded the zip into ADB. This is the command I used.
( enable USB debugging > adb reboot bootloader > fastboot flash boot PE_recovery.img > adb sideload PE.zip > Reboot )
With the sideload showing success message Total xfer: 1.00x I restarted the device and found that the device is now hard bricked once again.
Super confused, I double-checked the recovery img and ROM to make sure that the files aren't corrupted. Prior to installing, I also made sure to update my ADB and fastboot to the latest version.
----
TLDR
After getting phone hard bricked for the first time, on my second attempt to load a custom rom, the phone hard bricked again.
( enable USB debugging > adb reboot bootloader > fastboot flash boot PE_recovery.img > adb sideload PE.zip > Reboot )
Click to expand...
Click to collapse
What could go wrong here?
Upon typing here I think I forgot to do a wipe data before reboot, will this cause the phone to hard brick?
I guess I am sending this phone to the service center tomorrow again, made this thread to know what can I do to make sure this doesn't happen again.
Will I be better off using TWRP instead of their custom recovery image?
Am I messing up something here that caused the phone to hard brick? This image is also the exact image my POCO f3 is currently running which I sideloaded successfully and still running fine.
Should I do an update on MiUI before proceeding to install a PixelExperience?
Should I do a reflash after recovering the phone from Xiaomi's service center?
Could this be some kind of hardware problem?
I ordered my phone online but purchased her phone in the store, are there any differences here?
Any help or input is really appreciated, I have been doing this for quite a while now and never faced such an issue before.
I don't know a lot about bricks in general but i think you are supposed to format data after you flash the recovery because that's what i did after installing arrow os but i don't know how would that cause a hard brick.
PE a12 rom is busted that's why that thread is closed.
Your device is in EDL mode. Contact authorized users to unbrick your phone. Will cost you around $25-$30
regedit12345 said:
PE a12 rom is busted that's why that thread is closed.
Your device is in EDL mode. Contact authorized users to unbrick your phone. Will cost you around $25-$30
Click to expand...
Click to collapse
The problem is I have another exact device which is running the latest version of PE fine.
jylee1997123 said:
The problem is I have another exact device which is running the latest version of PE fine.
Click to expand...
Click to collapse
Yeah i know. your device got bricked because it got updated via the OTA and the pixel firmware got flashed on your device that why your device is in EDL mode.
regedit12345 said:
Yeah i know. your device got bricked because it got updated via the OTA and the pixel firmware got flashed on your device that why your device is in EDL mode.
Click to expand...
Click to collapse
I think there is some confusion here.
Are you referring to the first hard brick? No OTA update is performed because it is running PEX which does not support OTA updates.
If you are referring to the second hard brick, the phone is never in PE firmware at all. The moment I tried to flash PE rom, the phone got hard bricked with these steps. ( enable USB debugging > adb reboot bootloader > fastboot flash boot PE_recovery.img > adb sideload PE.zip > Reboot )
2 Devices
1) My personal device (POCO F3 Alioth) - Working fine with current latest stable PE
2) Her device (POCO F3 Alioth) - HardBricked, EDL when flashing with these steps ( enable USB debugging > adb reboot bootloader > fastboot flash boot PE_recovery.img > adb sideload PE.zip > Reboot )
jylee1997123 said:
TLDR below
Some of the backstory of this device:
This is my girlfriend's first android device, tried so hard to convince her to switch from iPhone to Android, I finally managed to convince her, but... this happened...
So since this is not my device and I wanted a pure Android 12 experience (which I bragged about), I installed Pixel Extended Android 12 Beta to the device. (Only android 12 experience that I got during that time)
This is what I did,
Unlocked the bootloader after 7 days ( using Miunlocktool )
With the phone still in factory firmware, I used pixel extended's recovery image which is located here https://sourceforge.net/projects/pex-alioth/files/1-11-21/
Steps that I did ( fastboot flash boot boot.img > fastboot flash vendor_boot vendor_boot.img > fastboot reboot recovery > Format data > adb sideload PEX.zip > Reboot )
After rebooting, the phone is now in PEX4.0 beta and she proceed to use the devices for several months after PixelExperience released their stable ROM for OTA updates and zero maintenance from my side.
When PixelExperience released their stable ROM, took her phone, trying to shut down the phone so I can go into fastboot and I realized that the phone isn't powering on at all which no display, plugged into my PC, no USB indicator as well.
The phone is dead from a shutdown which shocked me. My guess initially is some kind of electric damage that ruined the motherboard. So I sent this to Xiaomi's service center to get this fixed.
After picking up the phone from the service center yesterday, I have been told that the phone is hard bricked and not some kind of faulty hardware. I am pretty sure they reflashed the firmware with Xiaomi flash tool and it is now running on the global ROM 12.5, with an unlocked bootloader
Feeling weird at the hard brick, I thought I messed up somewhere.
On my second attempt to install PixelExperience, I managed to go into fastboot and sideloaded the zip into ADB. This is the command I used.
( enable USB debugging > adb reboot bootloader > fastboot flash boot PE_recovery.img > adb sideload PE.zip > Reboot )
With the sideload showing success message Total xfer: 1.00x I restarted the device and found that the device is now hard bricked once again.
Super confused, I double-checked the recovery img and ROM to make sure that the files aren't corrupted. Prior to installing, I also made sure to update my ADB and fastboot to the latest version.
----
TLDR
What could go wrong here?
Upon typing here I think I forgot to do a wipe data before reboot, will this cause the phone to hard brick?
I guess I am sending this phone to the service center tomorrow again, made this thread to know what can I do to make sure this doesn't happen again.
Will I be better off using TWRP instead of their custom recovery image?
Am I messing up something here that caused the phone to hard brick? This image is also the exact image my POCO f3 is currently running which I sideloaded successfully and still running fine.
Should I do an update on MiUI before proceeding to install a PixelExperience?
Should I do a reflash after recovering the phone from Xiaomi's service center?
Could this be some kind of hardware problem?
I ordered my phone online but purchased her phone in the store, are there any differences here?
Any help or input is really appreciated, I have been doing this for quite a while now and never faced such an issue before.
Click to expand...
Click to collapse
dont use pixel extended ive too had motherboard bricking issues with it pixel experience works perfectly for me with no issues
Zainullahk1234 said:
dont use pixel extended ive too had motherboard bricking issues with it pixel experience works perfectly for me with no issues
Click to expand...
Click to collapse
That is what I thought initially as well. However, PE disappointed me as well with the 2nd hard brick. Did I miss any step that caused this? Or this is PE related?
Try flashing aospa.
jylee1997123 said:
That is what I thought initially as well. However, PE disappointed me as well with the 2nd hard brick. Did I miss any step that caused this? Or this is PE related?
Click to expand...
Click to collapse
hmm i dunno then pe works perfectly on my x3 pro
are you sure your using the correct firmware?
try flashing miui firmware over it and booting (cause mabye the oss vendor is the issue)
or just sell your f3 and get the f4 once it comes out (looks to have snapdragon 8 gen 1!)
Try installing CrDroid, follow their installation steps, they work very well
I think most stable Aosp rom for poco f3 is Arrow Os don't use PE again
usmanjavid said:
I think most stable Aosp rom for poco f3 is Arrow Os don't use PE again
Click to expand...
Click to collapse
You definitely haven't tried PPUI
regedit12345 said:
You definitely haven't tried PPUI
Click to expand...
Click to collapse
LOL
dont mention that buggy mess
regedit12345 said:
You definitely haven't tried PPUI
Click to expand...
Click to collapse
i tried installing this instead of arrow os and i couldn't even boot into it it would just go back to miui
Zainullahk1234 said:
LOL
dont mention that buggy mess
Click to expand...
Click to collapse
I have tried all the A12 roms including syberia and arrow and by far this is the best rom. The maintainer of the rom is dev himself and very active and responsive on the telegram grp.
[Discontined][12.0][alioth/aliothin] Pixel Plus UI Poco F3 / Xiaomi Mi 11X / Redmi K40
This tread was discontined as far as I dropped support of PixelPlusUI Project. Thanks to all users and supporters who was Interested to project. Future Development for Poco F3 will be according to own new project - VoidUI Project Github...
forum.xda-developers.com
Well, thank you all for the suggestion. But I am not trying to find a rom that suits me or has fewer bugs. I am trying to figure out what goes wrong during my installation or if I missed something.
Is PE really that bad? I have been using them for quite a while now though
i have seen pixel extended that got his thread closed because at shutdown the phone bricked so it really is the roms fault
jylee1997123 said:
Well, thank you all for the suggestion. But I am not trying to find a rom that suits me or has fewer bugs. I am trying to figure out what goes wrong during my installation or if I missed something.
Is PE really that bad? I have been using them for quite a while now though
Click to expand...
Click to collapse
Pixel extended= bad
pixel experience= amazing
jylee1997123 said:
Well, thank you all for the suggestion. But I am not trying to find a rom that suits me or has fewer bugs. I am trying to figure out what goes wrong during my installation or if I missed something.
Is PE really that bad? I have been using them for quite a while now though
Click to expand...
Click to collapse
That's why I suggest using CrDroid, mostly because I haven't failed any installation following their installations steps, the ROM being stable and having good customizations is a perk that comes with it
Hi all,
I hope someone will be able to guide me as how to recover from this.
So today I tried flashing my POCO F3 with MIUI 14 (xiaomi.eu_multi_HMK40_POCOF3_V14.0.4.0.TKHCNXM_v14-13) from the stock version MIUI 12.
I first successfuly unlocked the bootloader using MiUnlock. I then unlocked the developer options , usb unbugging etc. again on the fresh phone.
I also had USB / ADB and fastloader drivers installed.
I downloaded xiaomi.eu_multi_HMK40_POCOF3_V14.0.4.0.TKHCNXM_v14-13 , phone was already in fastboot and connected to the computer so run 'windows fastboot first install with data format' as an administrator which opened the cmd , after agreeing it started flashing the first few files successfully but when it gets to " Sending 'cmnlib64_ab' (504 KB) " the process just stopped there and it has been like this for around 30 mins - no error ...simply stuck on this step .....
I am not sure on what to do now to avoid bricking my phone, should I leave it connected ? Disconnect it and try flashing it again ? Download an older version of Xiaomi.Eu ROM (e.g MIUI 13 ) ?
Leave it connected for about 1 hour or so until you get success or error confirmation. If failed just reboot to system. If system failed to show up then go to fastboot again and install xiaomi.eu a12 version.
This is exactly why I hate fastboot method and always install rom from twrp
Flash 14.0.5 via orangefox recovery.
I left it overnight and nothing happened . I disconnected the phone and it rebooted ok. I am kind of worried about trying again. Is the twrp method safer ?
Just discovered that I stupidly set the "USB debugging (Security settings) on but I forgot to turn on "USB debugging" which is a few lines above in settings. Could that be what has stopped the process?
Phone should flash fine even if debugging is off. I would recommend you to make sure that the cable doesnt even move an inch during the whole flashing process as that sometimes interrupts it especially if you have a loose port.
I just switched the usb port from the back of the pc (which I think are USB 3.0) to the front panel of the PC (I suspect USB 2.0 ) and tried flashing the MIUI 14 from yesterday again - It worked !!!!
*Deleted
Hi,
You could check out my post,
Fastboot not working in Windows 11 [Resolved]
Hello! I cant get my Windows 11 virtual machine to detect my Xiaomi 12 when its in Fastboot mode. Does any one happen to have any ideas to solve this? It shows up as 'Android' in device manager. I've also attempted to install a drivers manually...
forum.xda-developers.com
I hope it might help for the future
Hi...
Is it possible to flash a ROM that says "...V12.0.6....V12-10" for example, on a device that shipped with MIUI 11 Android 10, directly, without first updating the device to MIUI 12 normally?
Carl_OX said:
Hi...
Is it possible to flash a ROM that says "...V12.0.6....V12-10" for example, on a device that shipped with MIUI 11 Android 10, directly, without first updating the device to MIUI 12 normally?
Click to expand...
Click to collapse
you can do if you flash the fastboot version by mi flash tool, and your bootloader is unlocked.
mogamycool said:
you can do if you flash the fastboot version by mi flash tool, and your bootloader is unlocked.
Click to expand...
Click to collapse
Thanks... I really appreciate the early reply.
But can't I do this using the recovery method? And also must the android and miui versions of both the global stock rom and custom rom be the same?
Nevermind...thanks for your help
if you want to flash specific version of android, then you need unlocked bootloader and mi flash tool, otherwise make updater app do its job. and no need for the global stock rom and custom rom be the same. just put in your mind to backup your data .
mogamycool said:
if you want to flash specific version of android, then you need unlocked bootloader and mi flash tool, otherwise make updater app do its job. and no need for the global stock rom and custom rom be the same. just put in your mind to backup your data .
Click to expand...
Click to collapse
Thanks boss