Related
Hi Guys,
My Mi3 is bricked.I did a repartition some months back and I wanted to install MIUI 7.I used Miflash but it is showing size too large error while flashing.My recovery is replaced with stock recovery.I tried to use ADB to push the file,that is also not working as it is shoing device not found while I am in recovery.I installed Miphonemanager as well for that.But there is no luck.I am out of ideas.Can anyone please help me.
Can anyone let me know which driver I need to choose in driver manager for android in desktop? Currently I tried CMCC Composite ADB driver and Xiaomi Android Interface.
Flash latest TWRP first. What happened during repartition?
You can allways acces the eeprom writer through short circuiting the sim card, there are a lot of tutorials, the only way to brick this phone is breaking its hardware
nsakhare said:
Hi Guys,
My Mi3 is bricked.I did a repartition some months back and I wanted to install MIUI 7.I used Miflash but it is showing size too large error while flashing.My recovery is replaced with stock recovery.I tried to use ADB to push the file,that is also not working as it is shoing device not found while I am in recovery.I installed Miphonemanager as well for that.But there is no luck.I am out of ideas.Can anyone please help me.
Can anyone let me know which driver I need to choose in driver manager for android in desktop? Currently I tried CMCC Composite ADB driver and Xiaomi Android Interface.
Click to expand...
Click to collapse
Install custom recovery through fast boot mode... Then flash the repartition revert zip .. There is one revert zip in miui forum which ends like this "....EIPerroVerde". Only this revert zip works..Then use miflash .. It should work..
Sent from my MI 3W using Tapatalk
aniketkuber said:
Install custom recovery through fast boot mode... Then flash the repartition revert zip .. There is one revert zip in miui forum which ends like this "....EIPerroVerde". Only this revert zip works..Then use miflash .. It should work..
Sent from my MI 3W using Tapatalk
Click to expand...
Click to collapse
The correct repartition zips can be found in the thread in my signature.
Reproduced here for Tapatalk or mobile users:
http://forum.xda-developers.com/xiaomi-mi-3/general/extremely-useful-flashable-zips-t3080860
The Dork Knight Rises said:
The correct repartition zips can be found in the thread in my signature.
Reproduced here for Tapatalk or mobile users:
http://forum.xda-developers.com/xiaomi-mi-3/general/extremely-useful-flashable-zips-t3080860
Click to expand...
Click to collapse
Hey Knight (didn't want to call you Dork :angel: )
I have a messed up phone,
2 questions here :
1- Would repartitioning reset ALL the partitions ?
2- When installing a ROM with fastboot, will ALL the partitions be filled with the necessary data ?
(I'm in doubt because of IMEI data)
Btw, can anyone point me to a link with WORKING fastboot ROM downloads ?
Inonotting said:
Hey Knight (didn't want to call you Dork :angel: )
I have a messed up phone,
2 questions here :
1- Would repartitioning reset ALL the partitions ?
2- When installing a ROM with fastboot, will ALL the partitions be filled with the necessary data ?
(I'm in doubt because of IMEI data)
Btw, can anyone point me to a link with WORKING fastboot ROM downloads ?
Click to expand...
Click to collapse
Repartitioning will wipe both your system partitions [EDIT: Seems I was wrong?]. If you want to use MIUI 7, you can use either extended partition, or stock partition using the zip from my link.
For fastboot I guess you'll need stock.
No, installing a MIUI fastboot ROM shouldn't touch your IMEI. But yeah everything else can be overwritten, depending on which bat file you use when flashing.
The process I'd recommend right now is to flash TWRP IMG using fastboot(use the 15-second ADB installer and look up a tutorial on how to flash an IMG. Basically just put the IMG into the adb/fastboot installation directory and then open a terminal window and then fastboot flash)
And as for MIUI fastboot ROM, you just gotta find the thread on MIUI forums. Google can help
The Dork Knight Rises said:
Repartitioning will wipe both your system partitions. If you want to use MIUI 7, you can use either extended partition, or stock partition using the zip from my link.
For fastboot I guess you'll need stock.
No, installing a MIUI fastboot ROM shouldn't touch your IMEI. But yeah everything else can be overwritten, depending on which bat file you use when flashing.
The process I'd recommend right now is to flash TWRP IMG using fastboot(use the 15-second ADB installer and look up a tutorial on how to flash an IMG. Basically just put the IMG into the adb/fastboot installation directory and then open a terminal window and then fastboot flash)
And as for MIUI fastboot ROM, you just gotta find the thread on MIUI forums. Google can help
Click to expand...
Click to collapse
Thanks ... but ....
I was under the impression that there were many more partitions (about 28).
Check this site:
http://en.miui.com/thread-138246-1-1.html
Basically, I'm looking for an easy way out to make a REAL factory reset from PC.
Inonotting said:
Thanks ... but ....
I was under the impression that there were many more partitions (about 28).
Check this site:
http://en.miui.com/thread-138246-1-1.html
Basically, I'm looking for an easy way out to make a REAL factory reset from PC.
Click to expand...
Click to collapse
Well there ARE a LOT of partitions on any device, but the important ones are system, boot, data, cache, modem etc.
That guide seems to manually mess with the partition table, so it gets down and dirty.
The easiest thing would be to do what I said, flash TWRP or CWM r7 by furniel and then the proper stock partition zip. Then use MiFlash or recovery to flash any ROM.
I think I'm back online
The Dork Knight Rises said:
Well there ARE a LOT of partitions on any device, but the important ones are system, boot, data, cache, modem etc.
That guide seems to manually mess with the partition table, so it gets down and dirty.
The easiest thing would be to do what I said, flash TWRP or CWM r7 by furniel and then the proper stock partition zip. Then use MiFlash or recovery to flash any ROM.
Click to expand...
Click to collapse
OK,
I followed your links and flashed :
First : Repartition to Stock Layout
Then : Repartition to 1.2GB Single System
Strange, after this, I did a normal reboot, it rebooted into my old ROM.
Shouldn't that have been erased after partitioning ?
Anyway,
Then I flashed ; update-XenonHD-08-08-15-signed-.zip
WAIT WAIT .....
as I'm typing, I'm flashing update-XenonHD-09-05-15-signed-cancro.zip,
first ROM in a few weeks that seems to be installing.
Let me check is it really installed .... YEP .... progress
Flashing : pa_gapps-modular-pico-5.1-20150418-signed
Everything seems to be going smooth
OK, for the time being .... all good.
Thanks a lot :good:
If your device cannot boot, flash it thru fastboot mode. See the full detailed tutorial on en.miui.com
Well you can directly flash with miflash even with the extended partition. Just edit the fastboot script (.bat extension with windows) and search for line
fastboot flash system+system1
And then delete system1
Fastboot flash system
And use those script for flashing via miflash
I was running Freedom OS CE 2.5 and I dirty flashed official OOS 4.1.0 and got into a bootloop.
I restarted the phone into twrp and it told me that it was read only so I wasn't seeing any zip files. I tried to use repair in the Wipe section by changing file format. I think I chose FAT...I honestly can't remember. But when I swipe to repair and I got stock on updating partition. So I restarted the device into twrp again but this time I'm stock on just the splash screen....won't start.
All I'm getting into is bootloader mode.
Help please
Use fastboot to wipe recovery and flash TWRP again. Alternatively, directly sideload your ROM.
Anova's Origin said:
Use fastboot to wipe recovery and flash TWRP again. Alternatively, directly sideload your ROM.
Click to expand...
Click to collapse
Thank you so much. But what about how I tried changing the format from what it was originally? Should I be worried or that's a minor issue?
ddaharu said:
Thank you so much. But what about how I tried changing the format from what it was originally? Should I be worried or that's a minor issue?
Click to expand...
Click to collapse
You should reformat those partitions that you've changed. Ext4 or f2fs for /data and ext4 for all other partitions. This can be done through either fastboot or TWRP.
Anova's Origin said:
You should reformat those partitions that you've changed. Ext4 or f2fs for /data and ext4 for all other partitions. This can be done through either fastboot or TWRP.
Click to expand...
Click to collapse
Are these the commands I should use?
c:\adb>fastboot erase recovery
c:\adb>fastboot flash recovery twrp
Well as you said, after this I can reenter recovery and reformat the partitions and I should be fine right?
Thanks for all your help man...
ddaharu said:
Are these the commands I should use?
c:\adb>fastboot erase recovery
c:\adb>fastboot flash recovery twrp
Well as you said, after this I can reenter recovery and reformat the partitions and I should be fine right?
Thanks for all your help man...
Click to expand...
Click to collapse
Dont forget the ".img" when referring to images"
c:\adb>fastboot flash recovery twrp.img
Anova's Origin said:
Dont forget the ".img" when referring to images"
c:\adb>fastboot flash recovery twrp.img
Click to expand...
Click to collapse
One last question. Is there any twrp version you'll recommend? Or anyone is good?
ddaharu said:
One last question. Is there any twrp version you'll recommend? Or anyone is good?
Click to expand...
Click to collapse
3.0.4-1 has proven to be the most stable so far.
I've also been using 3.1.0-1 for a while and haven't noticed any issues.
Avoid 3.1.0.0 though, as there has been many reports of issues with it.
Anova's Origin said:
3.0.4-1 has proven to be the most stable so far.
I've also been using 3.1.0-1 for a while and haven't noticed any issues.
Avoid 3.1.0.0 though, as there has been many reports of issues with it.
Click to expand...
Click to collapse
MY PHONE IS RUNNING AGAIN! thanks for your help man.
Btw! Seeing that the positions were somewhat corrupted, I actually had to use stock recovery to sideload the stock ROM then flash TWRP and finally on freedom is 2.6.1
Thanks again, mate. :highfive:
ddaharu said:
I was running Freedom OS CE 2.5 and I dirty flashed official OOS 4.1.0 and got into a bootloop.
I restarted the phone into twrp and it told me that it was read only so I wasn't seeing any zip files. I tried to use repair in the Wipe section by changing file format. I think I chose FAT...I honestly can't remember. But when I swipe to repair and I got stock on updating partition. So I restarted the device into twrp again but this time I'm stock on just the splash screen....won't start.
All I'm getting into is bootloader mode.
Help please
Click to expand...
Click to collapse
I faced a similar issue with twrp , just try to flash twrp again using fastboot mode , in case it does not work again then try to flash it a few more times , it would surely work , I have already tried it , but before that try to factory reset ur phone using twrp and reboot to twrp and only use the first method if the problem exists after that
9891ishu said:
I faced a similar issue with twrp , just try to flash twrp again using fastboot mode , in case it does not work again then try to flash it a few more times , it would surely work , I have already tried it , but before that try to factory reset ur phone using twrp and reboot to twrp and only use the first method if the problem exists after that
Click to expand...
Click to collapse
Thanks. I got through.
Hey guys,
My younger brother had TWRP installed on his OP3. Yesterday he applied OTA and his phone got bricked. I unbricked it from MSMtool method (Qualcom Driver). It got unbricked and i have stock rom now however phone is stuck at android is upgrading (45 minutes). I tried restarting it and now it is in boot loop. i tried to flash latest OxygenOS from adb sideload and it got bricked again. Can anyone tell me what to do now or what is wrong with the device.
abdullah.ahsan11 said:
Hey guys,
My younger brother had TWRP installed on his OP3. Yesterday he applied OTA and his phone got bricked. I unbricked it from MSMtool method (Qualcom Driver). It got unbricked and i have stock rom now however phone is stuck at android is upgrading (45 minutes). I tried restarting it and now it is in boot loop. i tried to flash latest OxygenOS from adb sideload and it got bricked again. Can anyone tell me what to do now or what is wrong with the device.
Click to expand...
Click to collapse
You have TWRP installed? Use Method 2 of the unbrick guide. Now you want to wipe every partition then adb push your rom (not sideload) and manually flash it. Make sure you are on the latest Bluspark twrp.
Puddi_Puddin said:
You have TWRP installed? Use Method 2 of the unbrick guide. Now you want to wipe every partition then adb push your rom (not sideload) and manually flash it. Make sure you are on the latest Bluspark twrp.
Click to expand...
Click to collapse
I am using method 2, the OS gets stuck on bootloop that's why i tried to sideload later
I don't have a working recovery, all i can get is stock recovery, how can i install twrp?
I've tried flashing (fastboot flash recovery recovery.img) it but it is not working
abdullah.ahsan11 said:
I am using method 2, the OS gets stuck on bootloop that's why i tried to sideload later
I don't have a working recovery, all i can get is stock recovery, how can i install twrp?
I've tried flashing (fastboot flash recovery recovery.img) it but it is not working
Click to expand...
Click to collapse
Why is it not working? Does it give an error or something?
Puddi_Puddin said:
Why is it not working? Does it give an error or something?
Click to expand...
Click to collapse
Yes, it says flashing partition not allowed.
I suppose it is because usb debugging is off.
abdullah.ahsan11 said:
Yes, it says flashing partition not allowed.
I suppose it is because usb debugging is off.
Click to expand...
Click to collapse
Nah, In windows, go to Device Manager. How does your device show up? It has to do with wrong drivers.
Puddi_Puddin said:
Nah, In windows, go to Device Manager. How does your device show up? It has to do with wrong drivers.
Click to expand...
Click to collapse
Yes It shows up correctly.
abdullah.ahsan11 said:
Yes It shows up correctly.
Click to expand...
Click to collapse
What is correctly? What does it say? You might want to try different ADB drivers. You should be able to always flash In fastboot..
abdullah.ahsan11 said:
Yes, it says flashing partition not allowed.
I suppose it is because usb debugging is off.
Click to expand...
Click to collapse
Check again the bootloader to be unlocked. Use the tool for that, is it on OP3 forum, then retry to get a stock rom up before anything else (TWRP, custom rom, etc)
Sent from my OnePlus3 using XDA Labs
follow this instruction -
1- go into twrp and wipe everything even internal and formate it .
2- unistall all adb driver and oneplus driver also .. then clean tmp file from window
3rd- install latest adb+ oneplus 3 driver ..again restrat ..
4th-boot in fastboot mod and lock your bootloader
5th-flast latest build of oxygen stock recovery from fastboot
6th than again wipe or factory reset the device via stock recovery
7th open stock recoery than flash latest build of oxygen os via sideload
8th reboot the device and setup quikly
9th-unlock bootloader, flash bluespark recovery , flash rom, flash supersu ..
10th play with device
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
To clarify:
- I already tried erasing userdata and cache from fastboot
-I already tried flashing recovery images from twrp, stock and bluspark
Thanks in advance guys.
Pavononer23 said:
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
Thanks in advance guys.
Click to expand...
Click to collapse
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
rykanator said:
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
Click to expand...
Click to collapse
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Pavononer23 said:
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Click to expand...
Click to collapse
can you boot into the bootloader/fastboot?
rykanator said:
can you boot into the bootloader/fastboot?
Click to expand...
Click to collapse
Yes I can
Pavononer23 said:
Yes I can
Click to expand...
Click to collapse
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
rykanator said:
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
Click to expand...
Click to collapse
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Pavononer23 said:
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Click to expand...
Click to collapse
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
rykanator said:
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
Click to expand...
Click to collapse
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Pavononer23 said:
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Click to expand...
Click to collapse
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
rykanator said:
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
Click to expand...
Click to collapse
It is not working, I think I lost my Oneplus 3t...
Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
I mean idk if you wanna do this, but you could always try to "format userdata", then flash the stock recovery, and then sideload OOS. but you would lose all of your data in your internal storage, and it's still not a guarantee. there are some posts about doing a full wipe and starting from scratch. I'd look into those. Best of luck reviving your OP3T
Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
nicknacknuke said:
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
Click to expand...
Click to collapse
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
pitrus- said:
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
Click to expand...
Click to collapse
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Pavononer23 said:
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Click to expand...
Click to collapse
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
przemcio510 said:
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
Click to expand...
Click to collapse
I can't install the drivers:
-First, stupid Windows policy saying that its driver is the best one available.
-Second, choosing from a disk to avoid one saying that the driver is not a x64 one.
Pavononer23 said:
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Click to expand...
Click to collapse
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
redpoint73 said:
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
Click to expand...
Click to collapse
There were no errors when flashing TWRP. When I tried rebooting using fastboot(fastboot boot recovery.img) it got stuck in the message saying booting up... and the only thing that changed was that my phone left the bootloader screen to a screen with the Oneplus logo and a fastboot mode message under it.
The command I used was fastboot flash recovery recovery.img(Name of the actual recovery file)
TLDR: I tried installing AEX rom and I bricked my mi9, getting it in a fastboot loop. Flashed a bunch of things and now I think my firmware is messed up. Help.
First I flashed TWRP, then I flashed the AEX rom and gapps, but phone got in bootloop, then I tried just flashing the ROM and it worked. After I flashed gaps it got into bootloop again.
Then I read the instructions from the AEX thread and I flash the recommended Firmware file (v9.6.13), and the flash failed.
I wiped everything, reflashed the ROM without gapps, and at restart the phone. Got stuck in fastboot.
Tried reinstalling TWRP with no success. Tried flashing MIUI with their flash tool but it didn't ended the flash procedure even after 20 minutes...
I tried to directly boot the recovery image (TWRP) and I was surprised that the phone booted in MIUI, but wifi wasn't working. Did not test anything else. Restarting the phone got me again in fastboot loop.
I tried again flashing with mi flash tool and this time was succesfull.
Then I tried to flash a MIUI eu ROM and got the phone again in fastboot loop. Flash was succesfull, but when restarting TWRP said that there is no OS installed.
I decided to give up and flash global MIUI 10.2.13 back.
But now my phone has some problems. Auto brightness doesn't work and video recording freezes the camera app when image stabilization is enabled.
So, is there a way to reflash 10.2.13 rom firmware using mi flash tool?
I suppose the first Firmware flash that was unsuccessful messed the firmware up...
Or how do I get my phone back to factory status...
I suppose v9.6.13 firmware is China developer and was an upgrade and that I should downgrade to 10.2.13 rom firmware.
Or flashing developer global will solve the problem? And how do I do that?
TWRP: https://forum.xda-developers.com/Mi-9/development/recovery-twrp-3-3-1-siankatabg-t3934962
AEX: https://forum.xda-developers.com/Mi-9/development/rom-aospextended-v6-6-t3956100
Have you ever tried fastboot rom ? Now it's the only solution to recover your phone !
macgyverx86 said:
TLDR: I tried installing AEX rom and I bricked my mi9, getting it in a fastboot loop. Flashed a bunch of things and now I think my firmware is messed up. Help.
First I flashed TWRP, then I flashed the AEX rom and gapps, but phone got in bootloop, then I tried just flashing the ROM and it worked. After I flashed gaps it got into bootloop again.
Then I read the instructions from the AEX thread and I flash the recommended Firmware file (v9.6.13), and the flash failed.
I wiped everything, reflashed the ROM without gapps, and at restart the phone. Got stuck in fastboot.
Tried reinstalling TWRP with no success. Tried flashing MIUI with their flash tool but it didn't ended the flash procedure even after 20 minutes...
I tried to directly boot the recovery image (TWRP) and I was surprised that the phone booted in MIUI, but wifi wasn't working. Did not test anything else. Restarting the phone got me again in fastboot loop.
I tried again flashing with mi flash tool and this time was succesfull.
Then I tried to flash a MIUI eu ROM and got the phone again in fastboot loop. Flash was succesfull, but when restarting TWRP said that there is no OS installed.
I decided to give up and flash global MIUI 10.2.13 back.
But now my phone has some problems. Auto brightness doesn't work and video recording freezes the camera app when image stabilization is enabled.
So, is there a way to reflash 10.2.13 rom firmware using mi flash tool?
I suppose the first Firmware flash that was unsuccessful messed the firmware up...
Or how do I get my phone back to factory status...
I suppose v9.6.13 firmware is China developer and was an upgrade and that I should downgrade to 10.2.13 rom firmware.
Or flashing developer global will solve the problem? And how do I do that?
TWRP: https://forum.xda-developers.com/Mi-9/development/recovery-twrp-3-3-1-siankatabg-t3934962
AEX: https://forum.xda-developers.com/Mi-9/development/rom-aospextended-v6-6-t3956100
Click to expand...
Click to collapse
Hmm, so where are you at now!? Have you got twrp installed? and 10.2.13 but with issues, right? or are you on stock recovery?
Current status: I managed to flash fastboot global ROM in mi flash, and stock recovery.
But the firmware is messed up.
Camera doesn't work well. And from normal use I saw that Gyroscope, light sensor and compas aren't working at all...
Phone reboots itself and I can't unlock it because pattern isn-t recognized anymore, untill I reset it by long pressing the power button.
From CIT menu gyro, light sensor and compass are definitely not working.
Would flashing latest firmware from TWRP be a possible solution? My bootloader is still unlocked and I can flash TWRP.
Or should I format vendor partition first? And then flash firmware?
Fastboot flash did solved firmware problem.
macgyverx86 said:
Current status: I managed to flash fastboot global ROM in mi flash, and stock recovery.
But the firmware is messed up.
Camera doesn't work well. And from normal use I saw that Gyroscope, light sensor and compas aren't working at all...
Phone reboots itself and I can't unlock it because pattern isn-t recognized anymore, untill I reset it by long pressing the power button.
From CIT menu gyro, light sensor and compass are definitely not working.
Would flashing latest firmware from TWRP be a possible solution? My bootloader is still unlocked and I can flash TWRP.
Or should I format vendor partition first? And then flash firmware?
Fastboot flash did solved firmware problem.
Click to expand...
Click to collapse
To be honest I'm not entirely sure if it'll help, but, I'd put global stable flashable zip on otg, then I'd flash twrp again, boot to twrp using buttons not commands, wipe cache, dalvik, vendor, system, data, internal. Then format data, swiping with confirmation 'yes'. Then flash latest global again over the clean device from otg. You could try using mauronfrio's twrp 3.3.1-35 instead of the one you linked get it here. That's just what I'd try, can't say whether it'll help and no guarantees it'll fix anything... Let us know the outcome bud.
You can download the latest flashable rom from here
I can't see why ur sensors etc aren't working anymore, it's got to be all software related me thinks
Do not try to reboot after wipes, you'll have nothing installed
reg66 said:
... I'd put global stable flashable zip on otg, then I'd flash twrp again, boot to twrp using buttons not commands, wipe cache, dalvik, vendor, system, data, internal. Then format data, swiping with confirmation 'yes'. Then flash latest global again over the clean device from otg. ....
Click to expand...
Click to collapse
Correct me if I am wrong, but flashing a stock MIUI zip form twrp won't work.
Or you are saying that I should flash a xiaomi eu ROM?
Got another sugestion:
Someone said that there is the posibility that mi flash didn't flash persist partition and that I should try to force flash it.
Referred thread here: https://forum.xda-developers.com/re.../how-to-flash-persist-partiton-redmi-t3830310
Is this a possibility?
And shouldn't mi flash reflash everything?
macgyverx86 said:
Correct me if I am wrong, but flashing a stock MIUI zip form twrp won't work.
Or you are saying that I should flash a xiaomi eu ROM?
Click to expand...
Click to collapse
Hold tight bud, just checking. I remember doing that - and the stock rom flashes but you no longer have twrp, it flashes the whole system/vendor including recovery. But hang on 'cos I might be recalling my pocophone F1 for that proceedure. The reason I suggest to reflash twrp is simply to have better control over a fully clean wipe, before progressing to flash rom again. Like I say, hang on just checking...
---------- Post added at 08:49 PM ---------- Previous post was at 08:47 PM ----------
macgyverx86 said:
Got another sugestion:
Someone said that there is the posibility that mi flash didn't flash persist partition and that I should try to force flash it.
Referred thread here: https://forum.xda-developers.com/re.../how-to-flash-persist-partiton-redmi-t3830310
Is this a possibility?
And shouldn't mi flash reflash everything?
Click to expand...
Click to collapse
Yes, miflash should flash everything, but you say you started flashing other stuff when it all went wrong, so I'm really not sure what's happened to ur device. Hang on anyway, still checking on the flashable zip ..
---------- Post added at 09:06 PM ---------- Previous post was at 08:49 PM ----------
Nope, I think you're right, it was the poco I was getting muddled with - haven't had to do this in while (poco has flashable stock zips somewhere...). It is possible to do it with lazy flasher, but that may start getting messy again. Have you tried re-flashing fastboot? Can you wipe much at all in the stock recovery - again, I can't remember.
Failing that, yeah, I'd seriously consider flashing twrp and flashing mi-globe or eu rom. I prefer mi-globe (although currently using beast rom) over eu simply because you can customize it more on the website. Though, I wouldn't recommend pre-rooting it. Root after, if need be. Any way, we'll cross that bridge later... For now just try to re-flash
reg66 said:
Can you wipe much at all in the stock recovery - again, I can't remember.
Click to expand...
Click to collapse
Didn't get this.
Is it ok to format vendor partition? will it be recreated wen flashing again? using mi flash or from twrp?
macgyverx86 said:
Didn't get this.
Is it ok to format vendor partition? will it be recreated wen flashing again? using mi flash or from twrp?
Click to expand...
Click to collapse
I'm pretty sure you won't be able to wipe much in stock recovery, but just wipe what you can and try and re-flash fastboot. Don't flash twrp yet. You could try downloading again the fastboot file, in case of any corruption. Hopefully on the second flash all will be well. But that said, it should've been OK on the first flash :/ in theory
just flashed xiaomi eu rom and everything seems to work now. All sensors are working.
I had to disable signature check, and i got an mounting /system error -> got the message that is installed without changes... whatever that means
And now in TWRP, I think, my files are encrypted without enabling it.
Will try other roms later.
Thanks for the help.
macgyverx86 said:
just flashed xiaomi eu rom and everything seems to work now. All sensors are working.
I had to disable signature check, and i got an mounting /system error -> got the message that is installed without changes... whatever that means
And now in TWRP, I think, my files are encrypted without enabling it.
Will try other roms later.
Thanks for the help.
Click to expand...
Click to collapse
Glad you got it working, phew!
macgyverx86 said:
just flashed xiaomi eu rom and everything seems to work now. All sensors are working.
I had to disable signature check, and i got an mounting /system error -> got the message that is installed without changes... whatever that means
And now in TWRP, I think, my files are encrypted without enabling it.
Will try other roms later.
Thanks for the help.
Click to expand...
Click to collapse
Go the same problem as you,i tried Android Q beta rom and after reflashing stock fastboot rom with mi flash,the sensors and video not working,any solution?
gm007 said:
Go the same problem as you,i tried Android Q beta rom and after reflashing stock fastboot rom with mi flash,the sensors and video not working,any solution?
Click to expand...
Click to collapse
I just flashed Xiaomi EU rom, did a CIT test and all sensors were working.
Try that. I'm curious it it works for you.
macgyverx86 said:
I just flashed Xiaomi EU rom, did a CIT test and all sensors were working.
Try that. I'm curious it it works for you.
Click to expand...
Click to collapse
Yes it worked with eu rom,but i managed to fix it on stock global stable by flashing an old miui 10.2.6 fastboot rom,Than updated to the latest one 10.2.13
gm007 said:
Yes it worked with eu rom,but i managed to fix it on stock global stable by flashing an old miui 10.2.6 fastboot rom,Than updated to the latest one 10.2.13
Click to expand...
Click to collapse
So 10.2.13 fastboot image is to blame here.
macgyverx86 said:
So 10.2.13 fastboot image is to blame here.
Click to expand...
Click to collapse
Not sure maybe flashing eu rom first have fix it .