Question Hard bricked phone several months after installing a custom ROM - Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40

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

Related

Did factory reset rooted XT 1799-2, now phone only boots into recovery mode

Hi,
My previous post relates to this one. Due to that problem I got, I had to factory reset my device to get my camera working again. However, instead, my phone rebooted into TWRP and would not boot system normally. When I tried to go to factory mode via fastboot I ended up in endless bootloop. Back in TWRP I tried to restore my backed up ROM from before rooting, but nothing really changed. I am really desperate because I have not find any solutions for my model and I don't want to use other montana models stock ROMs as I suspect them not to be compatible. What shall I do?
Cheers
Six
sixtheninth said:
Hi,
My previous post relates to this one. Due to that problem I got, I had to factory reset my device to get my camera working again. However, instead, my phone rebooted into TWRP and would not boot system normally. When I tried to go to factory mode via fastboot I ended up in endless bootloop. Back in TWRP I tried to restore my backed up ROM from before rooting, but nothing really changed. I am really desperate because I have not find any solutions for my model and I don't want to use other montana models stock ROMs as I suspect them not to be compatible. What shall I do?
Cheers
Six
Click to expand...
Click to collapse
Flash montana_retcn stock rom via rsd lite or fastboot and your device will boot again but it will lose all your files
jvfigueredo said:
Flash montana_retcn stock rom via rsd lite or fastboot and your device will boot again but it will lose all your files
Click to expand...
Click to collapse
Thanks senor, but how do I flash it via fastboot? Can't I use TWRP instead?
jvfigueredo said:
Flash montana_retcn stock rom via rsd lite or fastboot and your device will boot again but it will lose all your files
Click to expand...
Click to collapse
Ok I was able the Stock rom, but it is Chinese, not the global one wihout Gapps and lots of bloatware. Do you know if there is also a GLOBAL stock ROM I can get? Conversely, is there perhaps a custom ROM like Lineage OS or others that is compatible with this device? Cheers
sixtheninth said:
Ok I was able the Stock rom, but it is Chinese, not the global one wihout Gapps and lots of bloatware. Do you know if there is also a GLOBAL stock ROM I can get? Conversely, is there perhaps a custom ROM like Lineage OS or others that is compatible with this device? Cheers
Click to expand...
Click to collapse
Sorry this is the stock rom of montana_retcn, to install the playstore by the store that comes in it, and it has the English language.
The rom that you were supposed to be a shop rom of the store that you bought, mine came with one of this but unfortunately I do not know where it has to download ...
jvfigueredo said:
Sorry this is the stock rom of montana_retcn, to install the playstore by the store that comes in it, and it has the English language.
The rom that you were supposed to be a shop rom of the store that you bought, mine came with one of this but unfortunately I do not know where it has to download ...
Click to expand...
Click to collapse
Ok I guess there is nothing more to be done here. Any custom ROMs are also probably not lying around too I guess :/
sixtheninth said:
Hi,
My previous post relates to this one. Due to that problem I got, I had to factory reset my device to get my camera working again. However, instead, my phone rebooted into TWRP and would not boot system normally. When I tried to go to factory mode via fastboot I ended up in endless bootloop. Back in TWRP I tried to restore my backed up ROM from before rooting, but nothing really changed. I am really desperate because I have not find any solutions for my model and I don't want to use other montana models stock ROMs as I suspect them not to be compatible. What shall I do?
Cheers
Six
Click to expand...
Click to collapse
Turn off the device, boot into Fastboot Flash Mode using vol down + power, using volume keys scroll and select factory mode and device will turn on. the next time you boot up the device, it won't go into TWRP directly. I have faced this issue many times. Hope this helps.
rizwan.mahai said:
Turn off the device, boot into Fastboot Flash Mode using vol down + power, using volume keys scroll and select factory mode and device will turn on. the next time you boot up the device, it won't go into TWRP directly. I have faced this issue many times. Hope this helps.
Click to expand...
Click to collapse
Not in this case. What Factory Mode did was that it got stuck in loading loop playing the Moto logo endlessly for over 5 minutes. Anyway, the phone is now hard bricked so I am facing even larger issue )
sixtheninth said:
Not in this case. What Factory Mode did was that it got stuck in loading loop playing the Moto logo endlessly for over 5 minutes. Anyway, the phone is now hard bricked so I am facing even larger issue )
Click to expand...
Click to collapse
I'm having the same problem with my wifes g5s.
I have found that from twrp>restart>bootloader (phone then enters bootloader) I can the immediately choose "start" to boot the phone.
But that is a hassle I'd prefer my wife not having to go through...
SvenHee said:
I'm having the same problem with my wifes g5s.
I have found that from twrp>restart>bootloader (phone then enters bootloader) I can the immediately choose "start" to boot the phone.
But that is a hassle I'd prefer my wife not having to go through...
Click to expand...
Click to collapse
Flash stock ROM via fastboot problem will be solved..
As far as people who need play store can flash gapps via TWRP as a same method we use for custom ROMs.
P.S. i will not suggest to buy XT1799-2 because this SKU is purely made for Chinese Market, if you need any custom ROM go to Weibo.com/diyroms and post a request to build a custom ROM for this device.
And there are some custom ROMs available that you can search via baidu.com ( Chinese Search Engine).
I will try to find any ROM and post for you guys and also post. Request to build for XT1799-2.
CHEERS
so have you find any global custom rom for this device ?
aamszia said:
so have you find any global custom rom for this device ?
Click to expand...
Click to collapse
Yes you can flash Viper Pie for Xt1792
Already tested at Xt1799

Question Poco f3 Error: Sending modem_ab

good evening
I have been trying to return to stock miui from Pixel Experience since yesterday but get this error every time I try to flash the Firmware and do not know what I can do about it. I would be happy if somebody knew what this error is from and what might fix it.
Same problem. Don't try more things because you will brick your phone like mine.
Thanks for your reply. What did you do that bricked your Phonem? This way I know what to avoid. Thanks you in advance
As you are sure your device is a eea one, try with this last official stable firmware : Version: V13.0.7.0.SKHEUXM
You can find it here https://new.c.mi.com/global/miuidownload/detail/device/1900394
Fastboot version here at bottom : https://xiaomifirmwareupdater.com/miui/alioth/stable/V13.0.7.0.SKHEUXM/
Or https://bigota.d.miui.com/V13.0.7.0...EUXM_20220627.0000.00_12.0_eea_e461331a7d.tgz
Thanks you so much I will try that
and i did not mention this but I started this whole project of returning to miui because my poco was and still is in a bootloop and is only accessible over fastboot, not recovery and even though it sometimes gets to the system it almost instantly crashes and reboots
Still the Same Error unfortunatelly
nockcx said:
and i did not mention this but I started this whole project of returning to miui because my poco was and still is in a bootloop and is only accessible over fastboot, not recovery and even though it sometimes gets to the system it almost instantly crashes and reboots
Click to expand...
Click to collapse
Ok,
Do you have any idea what you did that may have caused this bootloop ?
Have you used any Qualcomm Tools or any soft in EDL mode ?
No, I did not do anything that would mess with the system to my knowledge . which is why i really do not know what to do. Can This Error occur because of a USB 3.0 used to flash? The Phone even tries to reboot when it is detected as a Fastboot device, maybe This has Something to do with it. Maybe it loses the Connection and therefore the flashing process stops. Are there possible ways to fix This?
Try with the latest android platform tools.
Put the content of platform tools archive in the fastboot folder and launch flash_all.bat don't use flash_all_lock
Still the Same Error . Can This be because of a Driver or a hardware issue?
i had similar issues but with the super partition when trying to flash from cmd.
flashing with miflash instead solved it.
It doesnt seem to make any difference to the error whether i flash it via cmd or miflash
nockcx said:
Still the Same Error . Can This be because of a Driver or a hardware issue?
Click to expand...
Click to collapse
Maybe : So as you can try with other PC, USB cable, USB connector, reinstall USB drivers...
I already tried with two Notebooks, I will try again tomorrow with another PC and installing USB drivers again. Thank you
You could try redownloading the MIUI ROM... you got it from xiaomifirmwareupdater.com right?
And yes ^^, try other PCs/laptops and other USB-cables.
Just please make sure
Unfortunately, Fastboot-Flashing is a gamble. It's not a solid protocol. It has zero protection against sudden USB-connection loss.
And manufacturers like Xiaomi go out of their way and block Qualcomm's EDL Mode, which is the only way to recover your phone in case Fastboot Mode stops working, because that Mode itself can also get damaged.
Fixed - first flash a miui recovery rom from twrp make sure the rom version lower than the latest one, now flash and boot miui , now just update from miui updater once you updated to the latest version , now try to flash the fastboot rom that you trying to flash, it should work.
I cant access a bootloader like TWRP because the phone still keeps rebooting after a couple of seconds in the bootloader so i cant really do much. I only have access to fastboot
nockcx said:
just flash a custom vbmeta and then install a custom recovery in to the boot partition like fastboot flash boot ....flash both the slots boot_a and boot_b the run fastboot reboot recovery do all this with latest platform tools
Click to expand...
Click to collapse
okay Im as far as I have never been with a very weird method, maybe somebody can explain. Because my poco always wants to reboot I found out a way to keep in in Fastboot mode. I repeatedly press the power and volume down button, This way it stays on for a lot longer, but it still is not enough to succeed at flashing the rom. It also lets me believe that my problem is not a software but probably a hardware problem, otherwise and cannot explain this suuuper weird behavior. what do you guys think? is there a possible fix you know?

Question [lineageOS][Recovery]Stuck with fastboot bootloader bootloop

I had lineage19.1 working and a respective custom recovery with it. That was cool. Then I got dumb...
I proceeded to flash the new custom recovery for lineage-20.0-20230103-recovery-lemonadep.img. I am still not sure if the recovery needs updates or how to do so anyway. Can I still upgrade to version 20.0 with a recovery from 19.1? Regardless I am stuck in fastboot loop.
I am lost. I can't get to recovery mode anymore. How do I check things and see what to do next?
Hi.
I have been looking into lemonadep a bit lately.
I found a (renewed) 9 Pro a few days ago.
Should be here by the end of the week and I test more then. ​
Might want to ask your question in the LOS 20 thread.
Development [ROM][OFFICIAL][lemonadep][13] LineageOS 20 - Link
Cheers.
MintyFreshSocks said:
I had lineage19.1 working and a respective custom recovery with it. That was cool. Then I got dumb...
I proceeded to flash the new custom recovery for lineage-20.0-20230103-recovery-lemonadep.img. I am still not sure if the recovery needs updates or how to do so anyway. Can I still upgrade to version 20.0 with a recovery from 19.1? Regardless I am stuck in fastboot loop.
I am lost. I can't get to recovery mode anymore. How do I check things and see what to do next?
Click to expand...
Click to collapse
I suppose you are about to flash lineage20,
if so, search "payload-dumper" tool
from the rom's payload.bin extract dtbo, vendor_boot and boot img files, flash them to the related partitions, and your phone should be ready to load the new rom via sideloading it
Thank you for your time and consideration.
I have lost track of my own efforts here. Basically I'm right where I left off, with a little less battery. I am now onto the process of using MSM tool from this place. I get things started and then I reach "param preload failed" under the status, in the MSM tool. Is there any hope? I get scared when reading this disclaimer...
"If you modified any partition not touched by MSM, namely param and persist but there are others, you face a possibility of a hard brick. MSM will reset your "Enable OEM Unlocking" in dev settings and you might get a corrupt boot. Restore your backups before attempting. That said, If all you just tried to convert a ROM using OTA payload.bin, you should be fine."
...because yea I'm a curious kitty. I think I was messing in just about everything dangerous that I could... I still have a bootloader screen, thats fun to play with... I've got the right driver from qualcomm and it says the proper "QDloader 9008." But still no dice with MSM.
Is MSM the only option? I found this other OEM reFlash tutorial. I have questions tho...
Step 4: Gives me a prompt that says "Server Busy" "This action cannot be completed because the other program is busy. Choose 'Switch To' to activate the busy program and correct the problem."
I'm gonna stop running through the dark and hope someone can be my savior. A wing and a prayer.
What phone you got tmo,global EU?
I always assumed it was the global version. Bought it in the USA. Model LE2125
Host Machine is a Legion 7 16ACHg6.
Perhaps "New generation USB 3.0/3.1 ports may not allow the QPST tool to recognize your phone and could also cause problems during the flashing process."
Q1. Would there be a way to test and verify this possibility with my current machine? I am using the factory "red" usb-c cable.
Q2. How to verify no other drivers are causing issues simultaneously. (I went through quite a number of drivers before this)
Alas, my previous question regarding this "alternative MSM tutorial" and what the Server Busy means, should take precedence I think.
I am new to XDA and the android community and I truly love and thank you all. There is so much here and so much more opportunity. Thanks again.

[SOLVED] boot loop after i tried to fix broken root

I tried for like 3 hours to find a boot.img and i had root on my phone, but without wifi and sound.
a quick google search showed me that it was because i had a wrong version of the boot.img, afterwards i found another one and now after i have tried installing twrp, booting and flashing using adb (stock and modified versions of boot.img) but it just keeps bootlooping. in twrp i cant wipe, make a backup, see any files in /storage/ and i have no clue what to do next.
What model 7T do you have? HD1907? What was the rom that you were using before you installed TWRP on? OOS12 does not support TWRP. Custom rom A13 does not support TWRP. Only a few custom rom A12 and OOS11 support TWRP.
Idk but I'm just wondering if flashing the last working rom image (dirty flash)? That would eliminate TWRP(?) and eliminate Magisk(?) while hopefully keeping the device from being wiped possibly?
*** Hopefully someone could/would verify this before you attempt... ***
i was on android 11 but i cant remember the version, i have HD1903 (EU ver). i THINK i had the one from the oneplus website(https://service.oneplus.com/us/search/search-detail?id=2096229) but idk anymore
I JUST RANDOMLY TRIED BOOTING MY PHONE AGAIN AND IT WORKED imma check if everything works and will regardless still look at this thread bc it can prob break easily
nah wifi and sound still dont work, but im not in bootloop anymore
MimKA22 said:
I JUST RANDOMLY TRIED BOOTING MY PHONE AGAIN AND IT WORKED imma check if everything works and will regardless still look at this thread bc it can prob break easily
nah wifi and sound still dont work, but im not in bootloop anymore
Click to expand...
Click to collapse
Msmtool back to oos11
can you describe how to use it or send a link to tutorial or smth thx man <3
MimKA22 said:
can you describe how to use it or send a link to tutorial or smth thx man <3
Click to expand...
Click to collapse
[OP7T][OOS 11.0.5.1 HD65AA/BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
i cant find the file for my current version and it doesnt work if i try it with the only version that is android 11
and i cant turn my phone back on
and after i installed the drivers i had to restart my pc and now there is this thing at the bottom right:
testmode
windows 10 pro
...
i waited until my phone had no more battery charge and now im bootlooping again :/
nvm it just booted
im downgrading it now and i dont get the error "smth communication smth" in msmtool anymore
alr it worked my phone is wiped again but i can turn on wifi and sound
but how do i root my phone now? I have an Idea, im gonna write step by step what i think gets me a rooted phone please confirm if that would not break my phone ^^' (bootloader already unlocked)
1. enable usb debugging and allow my pc
2. download and install the latest magisk version from the github
3. download magisk patched boot.img for ver 11.0.5.1BA BUT since i cant find anything on the internet im gonna have to use the zip file from the unbrick tool thing (https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_7T/EU_HD65BA/R/) and then patch the boot.img using magisk myself
4. then use platform tools and type following commands: "adb reboot fastboot", "fastboot flash boot {the patched boot image file}"
5. then use magisk to direct install the root thing
i just realisized the unbrick thing that i wanted to use instead of a boot.img doesnt have a boot.img in it... WHERE CAN I FIND A BOOT.IMG brooo androidfilehost.com doesnt have it the unbrick tool doesnt have it
omg i realized i could update my phone to 11.0.9.1 then download the same version from official website and use the dumper to get the boot.img **** meee
wait it sais its 11.0.9.1HD65 AA and not BA **** me
k nvm i just changed the site settings to germany and now its BA
i just went for it and now my phone is rooted thank you very much for your help i would've prob tried to revert back to stock for like 2 weeks and then cry that i cant root my phone thank you so much xd

Question POCO F3 gets stuck during flashing with MIUI 14 XIAOMI.EU

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

Categories

Resources