Develop Bugs

Help. Two Mi Max stuck on Mi logo.

I have a two phones.
Mi Max 3/32 : Global 8.1.6.0. I recieved OTA to 8.2.1.0. Start downloading, on 40%+- phone freeze and reboot. Stuck on MI logo and dont boot. Dont show powered by android. Just mi logo.
Then i flash 8.2.1.0 trough MiFlash, bootloader locked, and... Same situation. Stuck on bootlogo. I Flash china rom, i flash global, flash older version. Come on Xiaomi! What wrong with you?!
Okay. Story #2
Mi max pro 3/64. Global 8.0.3.0. I downloading OTA, press instal, phone reboot and go install update. Ok. After this process, phone boot and... Cycle reboot. Again and again. On launcher, on setup wizards, on mi logo. Everywhere. Hmmm, okay, i open miflash repeat all as in story #1. Not effect. Zero. Cycle reboot. How?!
I dont know.
Both phones not bricks. But and dont work.
Debugging on usb is a necessary? I dont activated bcaz my phones dont booted. Funny, yeah.

Can it connect via adb?
Sent from my MI MAX using Tapatalk

RAMBO29 said:
Can it connect via adb?
Sent from my MI MAX using Tapatalk
Click to expand...
Click to collapse
yes

If it can connect via adb, flash via EDL mode and see.

If you are on miu you must check developer settings cause miui time to time unchecks option oem unlocking (in my case two times) for this reason ever i look at this and allow usb debugging always must be allowed and look at dev options is absolutely necessary to correct flash of roms, may be you are rooted when you tried to update and system cannot update by this way (device itself or autoupdate). to solve try first installing same version through fastboot, probably yet you don`t loose your data. but you must select option "flash_all_except_storage" from your unpacket zip rom

IndDoc said:
If it can connect via adb, flash via EDL mode and see.
Click to expand...
Click to collapse
hmm, for this it is necessary unlock boot?

SubwayChamp said:
If you are on miu you must check developer settings cause miui time to time unchecks option oem unlocking (in my case two times) for this reason ever i look at this and allow usb debugging always must be allowed and look at dev options is absolutely necessary to correct flash of roms, may be you are rooted when you tried to update and system cannot update by this way (device itself or autoupdate). to solve try first installing same version through fastboot, probably yet you don`t loose your data. but you must select option "flash_all_except_storage" from your unpacket zip rom
Click to expand...
Click to collapse
okay,
I did so. flash firmware and immediately bootloop. no root.

Dark_Eyes said:
hmm, for this it is necessary unlock boot?
Click to expand...
Click to collapse
Not required if you're going to flash the stable version.

IndDoc said:
Not required if you're going to flash the stable version.
Click to expand...
Click to collapse
sorry my mistake, i try but fastboot devices comand work (see device), adb ... not.
flash via fastboot
FAILED (remote: device is locked. Cannot erase).
need to unlock, yep?

That's not EDL, that's fastboot. See here for a guide how to use EDL mode.

IndDoc said:
That's not EDL, that's fastboot. See here for a guide how to use EDL mode.
Click to expand...
Click to collapse
i know about that. but my phones flashing via miflash (edl mode, Qualcomm HS-USB QDLoader 9008) and no boot (mi logo or mi logo plus powered by android stuck 5-10-15-55 mins)
why? i dont know.
upd. It's a MIRACLE. one phone (3/32) is ALIVE

Dark_Eyes said:
i know about that. but my phones flashing via miflash (edl mode, Qualcomm HS-USB QDLoader 9008) and no boot (mi logo or mi logo plus powered by android stuck 5-10-15-55 mins)
why? i dont know.
upd. It's a MIRACLE. one phone (3/32) is ALIVE
Click to expand...
Click to collapse
Good! Make sure you are flashing the right verison. If your phone is stuck on 'powered by android' screen, it's a good sign. It means your phone will eventually boot up.

IndDoc said:
Good! Make sure you are flashing the right verison. If your phone is stuck on 'powered by android' screen, it's a good sign. It means your phone will eventually boot up.
Click to expand...
Click to collapse
this is not quite right.
2nd phone flashing, booting, setup wizard (white screen, w\out miui 8 logo, freeze, reboot. cycle.)
1st phone working 5-7 min, freeze and reboot, stuck mi logo w\out powered by android. damn.

Dark_Eyes said:
this is not quite right.
2nd phone flashing, booting, setup wizard (white screen, w\out miui 8 logo, freeze, reboot. cycle.)
1st phone working 5-7 min, freeze and reboot, stuck mi logo w\out powered by android. damn.
Click to expand...
Click to collapse
Sounds like you have a hardware problem. Take it to a service center.

IndDoc said:
Sounds like you have a hardware problem. Take it to a service center.
Click to expand...
Click to collapse
agree, it seems. thank you.

Dark_Eyes said:
this is not quite right.
2nd phone flashing, booting, setup wizard (white screen, w\out miui 8 logo, freeze, reboot. cycle.)
1st phone working 5-7 min, freeze and reboot, stuck mi logo w\out powered by android. damn.
Click to expand...
Click to collapse
Well, let me tell the way that I flash exactly, for me works perfectly, EDL never work for me. Flash for fastboot couldn't work properly if you place files in any side of your PC. I place adb folder in main disk, in my case c:, unpack all the files of you rom beside the 4 files of adb in same folder (adb has created a path in system environment) then in mode fastboot with usb plugged device (how you loosed your data) right click on "flash_all" for rom can repair your partitions. (I don't remember now if appears with right click option to execute like an administrator better) don't use meanwhile your pc. may that help you

SubwayChamp said:
Well, let me tell the way that I flash exactly, for me works perfectly, EDL never work for me. Flash for fastboot couldn't work properly if you place files in any side of your PC. I place adb folder in main disk, in my case c:, unpack all the files of you rom beside the 4 files of adb in same folder (adb has created a path in system environment) then in mode fastboot with usb plugged device (how you loosed your data) right click on "flash_all" for rom can repair your partitions. (I don't remember now if appears with right click option to execute like an administrator better) don't use meanwhile your pc. may that help you
Click to expand...
Click to collapse
correct me:
you reboot to fastboot (vol- + power), rabbit logo, connect usb w\out pressing any buttons
create folder adb (4files adb + all files of firmware w\out folder image)
and run flash all
unlock boot required?

Dark_Eyes said:
correct me:
you reboot to fastboot (vol- + power), rabbit logo, connect usb w\out pressing any buttons
create folder adb (4files adb + all files of firmware w\out folder image)
and run flash all
unlock boot required?
Click to expand...
Click to collapse
Yes, mode fastboot in device with any trick like EDL, just connect to pc, no unlock bootloader required but must be an stock rom, fastboot image rom

SubwayChamp said:
Yes, mode fastboot in device with any trick like EDL, just connect to pc, no unlock bootloader required but must be an stock rom, fastboot image rom
Click to expand...
Click to collapse
after i click flash all, window appears 1 sec and all. no effect. what wrong?

Dark_Eyes said:
after i click flash all, window appears 1 sec and all. no effect. what wrong?
Click to expand...
Click to collapse
Recogniced device?, type first fastboot devices to be sure

Soft bricked OPO3, Fastboot with no recovery

Hi guys,
Rooted Oneplus 3 is soft bricked. Please help me!!! :crying:
:crying:Quick desription: Fastboot formatted it. My PC detects it.
Tried to Fastboot flash latest TWRP ("twrp-3.0.2-0-oneplus3.img") via CMD Prompt.
After that I get a message saying that the processed was "finished" (within 0.802s!).
Now I reboot+volume down and bootloop continues. Phone starts, I see the normal warnings I used to get after rooting it. Then I see the Oneplus logo for a fraction of a second and then it boots again and the process repeats itself.
I think it may be worth mentioning that the reason all this happened is an encryption problem that occurred while I was flashing a rom update with TWRP: After the flashing finished, got an error saying "unable to mount storage". Wiped cache+dalvik and then restarted. Got a black screen that did not display any signs of life after several minutes. Then turned it off and on by long press on the power button. Then I got an error saying that the encyption process was disrupted and that I have to wipe my phone (strange given that I did not select any encryption button in TWRP). Anyhow, then I fastboot formatted the phone and that's it.
Thank so much for anyone who can help!!!

fastboot flash recovery recovery.img (I recommend blu_spark's TWRP) reboot to recovery, if it doesn't work, try:
fastboot boot recovery recovery.img
See if you boot to recovery and then try flashing a custom ROM.

Hi Fobos, thanks for responding quickly.
I tried using fastboot boot command (with twrp-3.0.2-0-oneplus3.img). No luck with that.
Also, didn't find a downloadable blu_spark *.img version for twrp recovery. would you be so kind to add a link?
Thank you.

Now I think it's hard bricked ( Help!!!
Phone just stopped responding. Mostly doesn't respond. Occasionaly turns on for a nano second, flashes the +1 logo and turns off. Most of the time it doesnt even do that any more when I press (long / short press) the power button!
Somebody help, please!!

ppppp44 said:
Phone just stopped responding. Mostly doesn't respond. Occasionaly turns on for a nano second, flashes the +1 logo and turns off. Most of the time it doesnt even do that any more when I press (long / short press) the power button!
Somebody help, please!!
Click to expand...
Click to collapse
Keep calm and breath in. I was in the same situation.
Take a breath.
So, you have 2 ways depending on what you want. You can either go back to full stock with a flashing tool or you can install a custom recovery and then installing a custom rom (or stock one). I suggest the flashing tool.
Just follow the steps here: https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306 and if you have any question come back here and ask them.
Good luck.

Recoveryhttps://forum.xda-developers.com/devdb/project/dl/?id=24575
First format recovery by using command
fastboot format recovery
then flash recovery using
fastboot flash recovery "recovery.img"

Kayembe said:
Keep calm and breath in. I was in the same situation.
Take a breath.
So, you have 2 ways depending on what you want. You can either go back to full stock with a flashing tool or you can install a custom recovery and then installing a custom rom (or stock one). I suggest the flashing tool.
Just follow the steps here: https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306 and if you have any question come back here and ask them.
Good luck.
Click to expand...
Click to collapse
Hey Keyembe, thanks for the reply...
Tried to follow the instructions you posted. Did everything to allow unsigned drivers to be installed. Disabled it on from the advanced boot settings, and - when that didn't work, also running on test mode. Neither options work:
In the device manager I right click the android device (currently in fastboot mode), which is installed with Google drivers. I try to update the driver software to the unsigned driver and I get an error saying it's not compatible with my system (Win10 Pro) and that I should make sure it is compatible with an x64 based system.
What now?
Tx
Hey! Thanks for the reply...

anup807 said:
Recoveryhttps://forum.xda-developers.com/devdb/project/dl/?id=24575
First format recovery by using command
fastboot format recovery
then flash recovery using
fastboot flash recovery "recovery.img"
Click to expand...
Click to collapse
Hi Anup!
Thanks for the link to the Blu_Spark version of TWRP.
On CMD Prompt, tried to format recovery, console stopped responding. "Fastboot format recovery"...Just stops responding
Also tried "Fastboot delete recovery". I get a message saying "deleting recovery..." then also stops responding. Nothing happens from there.
I tried to use the OPO3 Root Toolkit. It does detect the fastboot device, but when I try to flash or boot or do anything else other than detection, it is unable to find the device. Says operation failed.
What now? :crying:

You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/

Machiel187 said:
You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Click to expand...
Click to collapse
Check your cable (try another one), even reinstall your adb drivers on your machine (if Windows).
Let the device charge for 30 minutes at least then retry (charge with new cable too).

ppppp44 said:
Hey Keyembe, thanks for the reply...
Tried to follow the instructions you posted. Did everything to allow unsigned drivers to be installed. Disabled it on from the advanced boot settings, and - when that didn't work, also running on test mode. Neither options work:
In the device manager I right click the android device (currently in fastboot mode), which is installed with Google drivers. I try to update the driver software to the unsigned driver and I get an error saying it's not compatible with my system (Win10 Pro) and that I should make sure it is compatible with an x64 based system.
What now?
Tx
Hey! Thanks for the reply...
Click to expand...
Click to collapse
Firstly, plug your phone on your computer in recovery mode or fastboot mode.
When you go in cmd and you type "adb devices" do you get anything?
If that works and you still can access recovery, you can install stock rom available on the OnePlus site. Here's a link : http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.3/
Boot into recovery, then install from adb.

Machiel187 said:
You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Click to expand...
Click to collapse
Thanks mate, followed the instructions on this post. I never get the device to be detected as Qualcomm. All I get is "Android Phone". I did install the Qualcomm drivers despite the warning I got for installing unsigned drivers. Installation went OK. When I go to the device manager again I still identifies the device as android phone. Also when I click "Have Disk" and select the qualcomm drivers I get an error saying they are incompatible with the device or with an x64 based system (regardless of them being signed or not).
Any ideas?
thanks again..

Kayembe said:
Firstly, plug your phone on your computer in recovery mode or fastboot mode.
When you go in cmd and you type "adb devices" do you get anything?
If that works and you still can access recovery, you can install stock rom available on the OnePlus site. Here's a link : http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.3/
Boot into recovery, then install from adb.
Click to expand...
Click to collapse
Hey Kayembe,
I only get to fastboot mode. No Adb device detected. No recovery mode available.

ppppp44 said:
Thanks mate, followed the instructions on this post. I never get the device to be detected as Qualcomm. All I get is "Android Phone". I did install the Qualcomm drivers despite the warning I got for installing unsigned drivers. Installation went OK. When I go to the device manager again I still identifies the device as android phone. Also when I click "Have Disk" and select the qualcomm drivers I get an error saying they are incompatible with the device or with an x64 based system (regardless of them being signed or not).
Any ideas?
thanks again..
Click to expand...
Click to collapse
Strange. Are you sure you turned off Driver Signature Enforcement?
When you hold the power button 10 seconds and plug the phone in, it should not be on. The screen should stay black. (looks like its off)
So make sure it's not trying to boot, because then it probably shows up as Android Phonee again.

Machiel187 said:
Strange. Are you sure you turned off Driver Signature Enforcement?
When you hold the power button 10 seconds and plug the phone in, it should not be on. The screen should stay black. (looks like its off)
So make sure it's not trying to boot, because then it probably shows up as Android Phonee again.
Click to expand...
Click to collapse
That's exactly what happens but when it's not in fastboot mode [ either after 10 seconds power button press or after i see the +1 logo (black screen)] - phone is not detected by my pc.
Yeah I'm sure about the driver signature enforcement. It's definitely off.
What am I doing wrong?
Thanks

ppppp44 said:
That's exactly what happens but when it's not in fastboot mode [ either after 10 seconds power button press or after i see the +1 logo (black screen)] - phone is not detected by my pc.
Yeah I'm sure about the driver signature enforcement. It's definitely off.
What am I doing wrong?
Thanks
Click to expand...
Click to collapse
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.

Puddi_Puddin said:
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.
Click to expand...
Click to collapse
ok I somehow managed to flash Blu_Spark Twrp and got it to work.
Within TWRP, flashed OnePlus3Oxygen_16_OTA_051_all_1704112009_2521.zip
and also SuperSU.zip, and no_verity.zip.
Getting some errors.
Device still doesn't boot.
Attaching the log TXT here.
I am desperate... please help.,..

Puddi_Puddin said:
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.
Click to expand...
Click to collapse
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((

ppppp44 said:
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((
Click to expand...
Click to collapse
try "default_password" for the password

ppppp44 said:
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((
Click to expand...
Click to collapse
Go to Fastboot type 'fastboot erase userdata' (you have to reflash OOS tho.. Make sure you are on the latest TWRP. I'm not a fan of Bluspark but his TWRP is currently more up 2 date.

No OS image now, please help!

I tried to root my device, and I eventually I managed, but i missed the step to recover my android phone backup from google drive during the startup setup, so I found some tutorial and it seems to tell me erase the phone back to factory so that I can see the startup setup again.
Now the device only boots into TWRP, and I have downloaded two different stock image , V10.0.1.0 and V10.0.2.0, trying to install in recovery mode, so I follow instruction, wipe system before install.
but both of them giving me error, not opening the zip file.
Now I can not use my phone, how can I install a OS please?

luckyvictor said:
I tried to root my device, and I eventually I managed, but i missed the step to recover my android phone backup from google drive during the startup setup, so I found some tutorial and it seems to tell me erase the phone back to factory so that I can see the startup setup again.
Now the device only boots into TWRP, and I have downloaded two different stock image , V10.0.1.0 and V10.0.2.0, trying to install in recovery mode, so I follow instruction, wipe system before install.
but both of them giving me error, not opening the zip file.
Now I can not use my phone, how can I install a OS please?
Click to expand...
Click to collapse
Hello,
I think a solution is to use MiFlash and to restore your phone, you will loose all of your data, your recovery and magisk.
Download link : https://xiaomiflashtool.com/
- Boot your phone in Fastboot and connect it to your computer,
- Extract the stock rom to a folder normally you will obtain some files with a folder called images.
- In MiFlash select this folder.
- Click on refresh, if your phone is connected to your computer and in fastboot mode it will appear.
Now select clean all and click on flash button.
Your phone will reboot normally.
If it doesn't work tell me !
Pierre
If I helped you drop a thanks !

Pierre_C said:
Hello,
I think a solution is to use MiFlash and to restore your phone, you will loose all of your data, your recovery and magisk.
Download link : https://xiaomiflashtool.com/
- Boot your phone in Fastboot and connect it to your computer,
- Extract the stock rom to a folder normally you will obtain some files with a folder called images.
- In MiFlash select this folder.
- Click on refresh, if your phone is connected to your computer and in fastboot mode it will appear.
Now select clean all and click on flash button.
Your phone will reboot normally.
If it doesn't work tell me !
Pierre
If I helped you drop a thanks !
Click to expand...
Click to collapse
There is no stock rom available on that website, so can I use the stock rom that I found on internet? do I need those batch script?

luckyvictor said:
There is no stock rom available on that website, so can I use the stock rom that I found on internet? do I need those batch script?
Click to expand...
Click to collapse
Download this stock oreo rom (You will install pie after if you want) http://bigota.d.miui.com/V9.6.11.0.ODLMIFF/daisy_global_images_V9.6.11.0.ODLMIFF_20181112.0000.00_8.1_8028e3bf1c.tgz
You will obtain an archive, unzip it while you obtain a folder with some .bat ans .sh ans a folder called "images". At that time run MiFlash and select the folder that contain these files. After follow the instructions of the old post
If you have some questions I'm here
Pierre
If I help you drop a thanks: )

Pierre_C said:
Download this stock oreo rom (You will install pie after if you want) http://bigota.d.miui.com/V9.6.11.0.ODLMIFF/daisy_global_images_V9.6.11.0.ODLMIFF_20181112.0000.00_8.1_8028e3bf1c.tgz
You will obtain an archive, unzip it while you obtain a folder with some .bat ans .sh ans a folder called "images". At that time run MiFlash and select the folder that contain these files. After follow the instructions of the old post
If you have some questions I'm here
Pierre
If I help you drop a thanks: )
Click to expand...
Click to collapse
Should I use those script? e.g Flash All, Flash all except storage and also Flash All Except data and Storage?

luckyvictor said:
Should I use those script? e.g Flash All, Flash all except storage and also Flash All Except data and Storage?
Click to expand...
Click to collapse
Flash All

Pierre_C said:
Flash All
Click to expand...
Click to collapse
ok, now I have downloaded it, extract it and using MiFlash tool, it gives me error of length cannot be less than 0

luckyvictor said:
ok, now I have downloaded it, extract it and using MiFlash tool, it gives me error of length cannot be less than 0
Click to expand...
Click to collapse
Send me your logs they are in C:\Xiaomi

Pierre_C said:
Download this stock oreo rom (You will install pie after if you want) http://bigota.d.miui.com/V9.6.11.0.ODLMIFF/daisy_global_images_V9.6.11.0.ODLMIFF_20181112.0000.00_8.1_8028e3bf1c.tgz
You will obtain an archive, unzip it while you obtain a folder with some .bat ans .sh ans a folder called "images". At that time run MiFlash and select the folder that contain these files. After follow the instructions of the old post
If you have some questions I'm here
Pierre
If I help you drop a thanks: )
Click to expand...
Click to collapse
There's already a fastboot Pie rom for mi a2 Lite
http://bigota.d.miui.com/V10.0.2.0....0.PDLMIFJ_20181221.0000.00_9.0_fed1fcdf5d.tgz

Pierre_C said:
Send me your logs they are in C:\Xiaomi
Click to expand...
Click to collapse
[21:22:00]: 在 System.String.Substring(Int32 startIndex, Int32 length)
在 MiUSB.USB.GetUsbNodeInformation(String DevicePath)
在 XiaoMiFlash.code.Utility.TreeViewUsbItem.AddHubNode(String HubPath, String HubNodeName)
在 XiaoMiFlash.code.Utility.TreeViewUsbItem.get_AllUsbDevices()
在 XiaoMiFlash.code.Utility.UsbDevice.GetDevice()
在 XiaoMiFlash.MainFrm.RefreshDevice()

luckyvictor said:
[21:22:00]: 在 System.String.Substring(Int32 startIndex, Int32 length)
在 MiUSB.USB.GetUsbNodeInformation(String DevicePath)
在 XiaoMiFlash.code.Utility.TreeViewUsbItem.AddHubNode(String HubPath, String HubNodeName)
在 XiaoMiFlash.code.Utility.TreeViewUsbItem.get_AllUsbDevices()
在 XiaoMiFlash.code.Utility.UsbDevice.GetDevice()
在 XiaoMiFlash.MainFrm.RefreshDevice()
Click to expand...
Click to collapse
Install xiaomi driver in MiFlash and retry

Pierre_C said:
Install xiaomi driver in MiFlash and retry
Click to expand...
Click to collapse
I have installed the USB driver, the qualcomm usb driver, and install those 5 drivers within MiFlash tool (google, nvidia, microsoft, microsoft, qualcomm), and i still get the same error.
is it because my phone has nothing but only the TWRP? no OS? so it can not be detected by the computer?

luckyvictor said:
I have installed the USB driver, the qualcomm usb driver, and install those 5 drivers within MiFlash tool (google, nvidia, microsoft, microsoft, qualcomm), and i still get the same error.
Click to expand...
Click to collapse
Run MiFlash in administrator

Pierre_C said:
Run MiFlash in administrator
Click to expand...
Click to collapse
Tried, same error.
is it because my phone has nothing but only the TWRP? no OS? so it can not be detected by the computer?

luckyvictor said:
Tried, same error.
is it because my phone has nothing but only the TWRP? no OS? so it can not be detected by the computer?
Click to expand...
Click to collapse
download minimal adb and fastboot and install it. Open it enter "fastboot devices" and send me the output.

Pierre_C said:
download minimal adb and fastboot and install it. Open it enter "fastboot devices" and send me the output.
Click to expand...
Click to collapse
fastboot device does return a id
69d2d83f0505 fastboot
so does it mean I should be able to use MiFlash?
By the way, I really appreciate your help so far, you are so great.

luckyvictor said:
fastboot device does return a id
69d2d83f0505 fastboot
so does it mean I should be able to use MiFlash?
By the way, I really appreciate your help so far, you are so great.
Click to expand...
Click to collapse
Try run flash_all.bat manually
No problem for my help this is normal
Pierre

Pierre_C said:
Try run flash_all.bat manually
No problem for my help this is normal
Pierre
Click to expand...
Click to collapse
it works!!
But something quite strange, the machine is a bit slow, and i have typed the correct (for sure) password for my wifi a few times, and only the 7th or 8th try it connects.
and I dont seem to be able to install apps from google play, they all stuck in download pending.
Can I actually 'factory reset' the phone to the status when it was out of the box?

luckyvictor said:
it works!!
But something quite strange, the machine is a bit slow, and i have typed the correct (for sure) password for my wifi a few times, and only the 7th or 8th try it connects.
and I dont seem to be able to install apps from google play, they all stuck in download pending.
Can I actually 'factory reset' the phone to the status when it was out of the box?
Click to expand...
Click to collapse
Yes try a factory reset or try restart your phone

Pierre_C said:
Yes try a factory reset or try restart your phone
Click to expand...
Click to collapse
I used erase all data (factory reset), and this was how I ended up booting only into TWRP.

Question no access to phone

when trying to install a new ROM, I completely locked out myself
- fastboot leads to (new ?) orange FASTBOOT screen but
- device will not be recognized via adb/fastboot
- TWRP leads to screen teamwin Recovery Project 3.7.0_12-0 and then goes into bootloop to the same screen
any ideas?
last thing I tried was changing the filesystem inside twrp

gartmann said:
when trying to install a new ROM, I completely locked out myself
- fastboot leads to (new ?) orange FASTBOOT screen but
- device will not be recognized via adb/fastboot
- TWRP leads to screen teamwin Recovery Project 3.7.0_12-0 and then goes into bootloop to the same screen
any ideas?
last thing I tried was changing the filesystem inside twrp
Click to expand...
Click to collapse
Would be nice if you can share a photo of the "new Fastboot screen".
You mean TWRP doesn't function properly?
Did Fastboot work before? What have you done exactly?
If you need more direct help I can give you my Telegram or Discord

It doesn't properly start. These are the pics of the three possibilities I have now.
Fastboot was working before.
Last thing before was the changing the filesystem to (i thing) ExFat

gartmann said:
It doesn't properly start. These are the pics of the three possibilities I have now.
Fastboot was working before.
Last thing before was the changing the filesystem to (i thing) ExFat
Click to expand...
Click to collapse
Orange fastboot is fastbootd, first somehow get your pc to recognise the phone , then to reboot to normal fastboot you gotta use "fastboot reboot bootloader"
From there miflash
Fastbootd can only flash certain partitions - if you run miflash from it , it'll fail I think

gartmann said:
It doesn't properly start. These are the pics of the three possibilities I have now.
Fastboot was working before.
Last thing before was the changing the filesystem to (i thing) ExFat
Click to expand...
Click to collapse
If the Windows installed drivers are the problem, this will fix it:
Boot Windows with Driver Signature Enforcement disabled by doing this:
Open Windows' Power Menu, and while holding SHIFT-key, click Restart.
Select "Startup Settings" > Restart.
Screenshot
Click 7 for Disable Driver Signature Enforcement.
Screenshot
Get Mi Flash, extract the folder, and run Mi Flash.
Click "Driver" in the top-bar and click Install.
Screenshot
After doing this, the drivers are correctly installed and Fastboot and ADB commands should work.
Then you can proceed to temporarily boot a TWRP or OrangeFox that actually works.
"fastboot boot twrp.img"
I recommend OrangeFox.
You can install a recovery with "Install RamDisk" (both have this option).
If you want to flash MIUI or a Custom ROM, flashing the Recovery-flashable ZIP for MIUI or for the Custom ROM, should suffice.

My problem is, that (even after new driver installation with Mi Flash) the PC doesn't recognise the Poco F3 (but recognises without any problem my old Mi Mix 3).
So I concluse that the problem is on Poco side but I have ho idea what I can do it the phone isn't recognised.

gartmann said:
My problem is, that (even after new driver installation with Mi Flash) the PC doesn't recognise the Poco F3 (but recognises without any problem my old Mi Mix 3).
So I concluse that the problem is on Poco side but I have ho idea what I can do it the phone isn't recognised.
Click to expand...
Click to collapse
Does device show up in device manager ? Did you setup adb tools and issue "fastboot reboot bootloader" command ? If this doesn't work, what about "fastboot devices"
Come back when you do this , don't use mi flash untill you reboot phone into bootloader ( blue fastboot )
Maybe even check if adb commands work through twrp as a last resort ... "adb reboot bootloader"

Rstment ^m^ said:
Orange fastboot is fastbootd, first somehow get your pc to recognise the phone , then to reboot to normal fastboot you gotta use "fastboot reboot bootloader"
From there miflash
Fastbootd can only flash certain partitions - if you run miflash from it , it'll fail I think
Click to expand...
Click to collapse
The Orange Fastboot isnt fastbootd, its normal fastboot. The icon changed from the doll miui 12.5 to this orange fastboot on miui 13
gartmann said:
My problem is, that (even after new driver installation with Mi Flash) the PC doesn't recognise the Poco F3 (but recognises without any problem my old Mi Mix 3).
So I concluse that the problem is on Poco side but I have ho idea what I can do it the phone isn't recognised.
Click to expand...
Click to collapse
Download mi unlock tool and run it. Click on the settings icon on the top right corner and download its drivers, it'll ask you to connect the phone to the pc. (connect it on fastboot mode)

If I connect the phone I get the message, that the usb-device isn't recognised, no problem with poco f1 and poco f3
mi unlock tool gives (also after driver installation) this

gartmann said:
If I connect the phone I get the message, that the usb-device isn't recognised, no problem with poco f1 and poco f3
mi unlock tool gives (also after driver installation) this
View attachment 5737887
Click to expand...
Click to collapse
try changing the cable and also try changing the usb port on pc
if still no problems, then the phone port could be faulty
btw, i only meant to say is to download the drivers from mi unlock tool, after that, you can try and flash the stock rom in mi flash tool

gartmann said:
My problem is, that (even after new driver installation with Mi Flash) the PC doesn't recognise the Poco F3 (but recognises without any problem my old Mi Mix 3).
So I concluse that the problem is on Poco side but I have ho idea what I can do it the phone isn't recognised.
Click to expand...
Click to collapse
Did you do my steps including the Driver Signature Enforcement part?
I'm asking because otherwise I'm out of ideas lol
Kinda fked up that Fastboot isn't working for you...
Since Recovery isn't booting for you. Only Fastboot may be your last chance. So try and see if it works with other PCs... other cables... whatever. You gotta make Fastboot to work.

Question Stuck in bootloop Xiaomi 11T

Hello,
I tried to install a GSI rom on my phone, but I encountered a lot of problems, I couldn't erase the system because it said "system" partition was not found. So I tried many things like editing the partitions. But now, my phone is stuck in bootloop, and I can't enter recovery mode or fastboot mode.
Please help :/

lonyyy_ said:
Hello,
I tried to install a GSI rom on my phone, but I encountered a lot of problems, I couldn't erase the system because it said "system" partition was not found. So I tried many things like editing the partitions. But now, my phone is stuck in bootloop, and I can't enter recovery mode or fastboot mode.
Please help :/
Click to expand...
Click to collapse
Hi!
I struggled with this for a while as well but I found what works for me.
first, make sure you have the proper drivers installed ( just google MTK drivers and you'll find plenty of links for auto-installers ).
you gotta bypass the auth and flash with sp flash tool.
for the bypass:
I use MTK META Utility v75 ( again, google and you'll find it ).
click "disable Auth", then plug in your phone while holding volume up button. If it doesn't disable the BRom protection, you gotta use libusb to install the device filter.
Once the auth is disabled, use sp flash tool to flash the stock firmware.
first, in options, click connections, select the right comport.
in format, click the "format all except bootloader". VERY IMPORTANT YOU CLICK THIS.
next in download select the download agent and scatter file ( found inside the fastboot stock rom folder ).
Check everything EXCEPT PRELOADER and click download

RadixMalum said:
Hi!
I struggled with this for a while as well but I found what works for me.
first, make sure you have the proper drivers installed ( just google MTK drivers and you'll find plenty of links for auto-installers ).
you gotta bypass the auth and flash with sp flash tool.
for the bypass:
I use MTK META Utility v75 ( again, google and you'll find it ).
click "disable Auth", then plug in your phone while holding volume up button. If it doesn't disable the BRom protection, you gotta use libusb to install the device filter.
Once the auth is disabled, use sp flash tool to flash the stock firmware.
first, in options, click connections, select the right comport.
in format, click the "format all except bootloader". VERY IMPORTANT YOU CLICK THIS.
next in download select the download agent and scatter file ( found inside the fastboot stock rom folder ).
Check everything EXCEPT PRELOADER and click download
Click to expand...
Click to collapse
Thank you ! But how can I do this, my phone is stuck in a bootloop?

lonyyy_ said:
Thank you ! But how can I do this, my phone is stuck in a bootloop?
Click to expand...
Click to collapse
if you do the whole bypass thingy it's gonna skip certain boot-checks which causes the loop, putting it in a different mode. from there, sp flash tool can access the device.
you can also just hold down the volume up button and then plug in the usb, 9/10 the bypass utillity will catch the BRom

RadixMalum said:
Hi!
I struggled with this for a while as well but I found what works for me.
first, make sure you have the proper drivers installed ( just google MTK drivers and you'll find plenty of links for auto-installers ).
you gotta bypass the auth and flash with sp flash tool.
for the bypass:
I use MTK META Utility v75 ( again, google and you'll find it ).
click "disable Auth", then plug in your phone while holding volume up button. If it doesn't disable the BRom protection, you gotta use libusb to install the device filter.
Once the auth is disabled, use sp flash tool to flash the stock firmware.
first, in options, click connections, select the right comport.
in format, click the "format all except bootloader". VERY IMPORTANT YOU CLICK THIS.
next in download select the download agent and scatter file ( found inside the fastboot stock rom folder ).
Check everything EXCEPT PRELOADER and click download
Click to expand...
Click to collapse
So the BROM protection is now deactivated, but I can't find any COM port in the connection panel. And what is the fastboot stock rom folder ? I need to download the stock rom of Xiaomi 11T?

lonyyy_ said:
So the BROM protection is now deactivated, but I can't find any COM port in the connection panel. And what is the fastboot stock rom folder ? I need to download the stock rom of Xiaomi 11T?
Click to expand...
Click to collapse
alright I'm guessing you'll first need to add the device filter for the port.
download libusb, run it and click add filter. while you have the phone in bypass mode, you should see a mediatek device in the list. add that one.
and yeah. but you can just download it from mi.com!

RadixMalum said:
alright I'm guessing you'll first need to add the device filter for the port.
download libusb, run it and click add filter. while you have the phone in bypass mode, you should see a mediatek device in the list. add that one.
and yeah. but you can just download it from mi.com!
Click to expand...
Click to collapse
Ok, thanks ! I'm downloading the ROM, but in libusb, it doesn't recognize my device...

RadixMalum said:
alright I'm guessing you'll first need to add the device filter for the port.
download libusb, run it and click add filter. while you have the phone in bypass mode, you should see a mediatek device in the list. add that one.
and yeah. but you can just download it from mi.com!
Click to expand...
Click to collapse
Soo... libusb wasn't working, but I figured out that I have like one minute to flash, during this time, it recognizes the com port etc...
First, it says "lib da not match" in download-agent, then in scatter-loading file it says "the scatter file contains an unsupported version"...

lonyyy_ said:
Hello,
I tried to install a GSI rom on my phone, but I encountered a lot of problems, I couldn't erase the system because it said "system" partition was not found. So I tried many things like editing the partitions. But now, my phone is stuck in bootloop, and I can't enter recovery mode or fastboot mode.
Please help :/
Click to expand...
Click to collapse
Sir, from indonesia? I just flash vbmeta with spflashtool, or python brom mode . Sorry bad english

Okay, thanks everyone! I got my phone working again by using mtkclient python and mi flash tool!

RadixMalum said:
Hi!
I struggled with this for a while as well but I found what works for me.
first, make sure you have the proper drivers installed ( just google MTK drivers and you'll find plenty of links for auto-installers ).
you gotta bypass the auth and flash with sp flash tool.
for the bypass:
I use MTK META Utility v75 ( again, google and you'll find it ).
click "disable Auth", then plug in your phone while holding volume up button. If it doesn't disable the BRom protection, you gotta use libusb to install the device filter.
Once the auth is disabled, use sp flash tool to flash the stock firmware.
first, in options, click connections, select the right comport.
in format, click the "format all except bootloader". VERY IMPORTANT YOU CLICK THIS.
next in download select the download agent and scatter file ( found inside the fastboot stock rom folder ).
Check everything EXCEPT PRELOADER and click download
Click to expand...
Click to collapse
Hey,
My friend is trying to follow your reply in order to get her phone out of bootloop.
Not sure if you are aware but if you google for "MTK META Utility v75" as you instruct people to do... you get a wall of spam uploads which are zip files with passwords on... which gives the impression that basically every spammer wanting to get a virus onto your computer, or youtuber wanting to force you to watch their videos, is uploading crap marked as "MTK META Utility".
Perhaps you could actually provide links to trustworthy software or make a topic with a proper guide for people to follow, instead of just a reply to someone's question?

lonyyy_ said:
Okay, thanks everyone! I got my phone working again by using mtkclient python and mi flash tool!
Click to expand...
Click to collapse
Please can you tell me how?? I am having the same problem and my phone is just rebooting constantly but I cant open fastboot. Please or I don't know if my phone is dead

I have some experience with rooting this device and I can tell you that this device can install TWRP but it doesn't boot system after install ikr sad