After the S20 screen screen died I decided to go Poco X3 pro then I was told that it dies randomly and after alot of googling the Mi 10T seemed like the perfect deal to ever exist for me so I went on and bought one yesterday so far so happy I won't lie it feels so so good no clue what all the trash talk about its screen coming from S20 with wqhd+ always enabled I see no difference what so ever with mi 10t but then again am nearly blind (sad fact lol) after I got home I did a factory reset from the settings (no mi account was logged) I had a second hand note 9 pro and I got traumatized cuz I did a factory reset with the last owner acc linked to it and never used the phone ever after thanks to the mi lock xD
Dry I get off topic alot forgive me alright now the the phone is back to factory status the sound/mic/Bluetooth earphones/wired earphones no longer working I was like am sure this little miui 13 update notifications will solve that no problems and I went on to download it after it finished I did it and it caused the phone to go into a bootloop and it occasionally end the bootloop through going to recovery by it self and not doing anything cuz it to restart into bootloop again (am telling u guys this phone is HAUNTED) alright after crying to blindness in the shower I go for round 2 now armed with Google/YouTube/XDA and Reddit I was like yea boi certainly you will fix this hard earned phone
I went to try
-wipe data from recovery then reboot
-remove SIM tray
-put a SIM card
-remove the SIM card
-wait for as far as the black screen past the mi with 3 loading dots go (led light on) and call it
-safe mode
-unlocking back cover and unplugging the battery (friend halped me with emotional support cuz that part scared the living out of me) WHY THEY MAKE BATTERY SO HARD TO UNPLUG
-fastboot command every single one I could find
-leaving it reboot for 5 hours
Conclusion: non of the solutions above worked for me
So I went to cry in the shower again and came back for round 3
Now I went on to download every Xiaomi mi 10t driver I could find / Qualcomm drivers / miflash tool (every single version) / miflash tool pro ( the one with black logo) / Xiaomi tool V2 by Francisco I think (forgive me if I name u wrong Francisco cuz it's been a tough day) / mipc suit assistant / every mi 10t ROM recovery or fastboot I could find ( I didn't have a clue what the difference between them was but I learned it along the lol journey ).
After installing everything I started testing
And the Results are as follow:
-miflash tool with every ROM except for one : erase boot error / erase is not allowed in lock state
I still can't understand this error cause the ROMs I downloaded re supposed to be official not custom ROMs or something and re supposed to be able to flash with locked bootloader without mi auth specially that my phone does not have mi account linked to it.
One ROM tho did give me flash success in like 1 second after clicking flash but nothing happens and nothing changes.
-miflash tool pro the phone gets recognised and show me to click flash recovery but clicking it make nothing happen while in YouTube it shows a second window to proceed with flash for other people
-clicking the flash_all.bat and all the other different flash_xxx.bat blinks a CMD window and nothing happen
-flashing with ADB by all different methods results in all kind of errors and non works
-mi pc suit assistant doesn't even detect the phone in recovery but when I put it in fastboot it show screen saying that I should back up then proceed to fastboot but rebooting back to fastboot make nothing happens and trying to click back or the flash button in the assistant shows nothing (different version of mi assistant shows device not supported when I start it in fastboot and shows nothing in recovery)
-Xiaomi unlock tool V2 by the one who was so so so close from saving me Francisco him self this one unlike the other apps do go much further after clicking the option for bricked phone (cuz the other option for modding require unlocked bootloader) and choosing the redmi k30s ultra appollo (cuz no mi 10t on the list) and letting it download the ROM it started flashing it (OMG ITS A SIGN THAT AM GOING IN THE RIGHT PATH) the phone shows a loading screen that freez at 4.99% but it goes further later on (same thing do happen for other guy on YouTube but he end up with better result then I did in the end) and once it reaches 90% or 91% am not sure cuz it happens so fast the Xiaomi unlock tool V2 shows error in the laptop and the phone goes back into its never ending bootloop version of ouroboros (Francisco if u reading this please feel free to add option to load other ROMs then the one Ur app download to it self to flash cuz I felt like one of the ROMs I have could maybe work and someone else may be in the same situation one day too)
nothing work for me but I have a good feeling about miflash tool if I know what causing the erase not allowed in lock despite the ROM being stock and does not need unlocked bootloader.
I took the phone to a Xiaomi service centre but they refused to provide any help saying that my phone was never supposed to exist in my country and is only sold in Europe and they can't provide any help for me, they treated me the same with the issue with my redmi note 9 pro when the phone got mi lock despite showing the box and all its paper, the original owner purchase paper and giving them my national ID
If someone have a solution please tell me cuz I truly need Ur help and have no other options and no clue what to do at this point am completely a newbie at this never flashed a ROM before today and never had such an issue and sorry again for making this long but I truly wanted to explain everything I tried and provide as much information to the issue as I can
XDA Geniuses my phone fate is at ur hands if u choose to help me
EDIT: I was so nervouse I forgot to say that the phone is MI 10T and fixed some typos despite so many more exist cuz my English suck
It's been months now and am still trying but can't get the phone to work and no one seem to know a solution to the issue am facing
Little update after months of trying something popped out now when I flash the phone with MiFlashPro (the one with black logo) the phone make it to 90% then reboot but it's still bootlooping the same the only difference now that the phone MIUI version actually changed it went from 13.0.6 to 13.0.8 so since the version is changing something is changing wish did not happen before now am gonna try the older versions and see if it's even possible to downgrade thro recovery flash or not and then will try the miui12.5 since that's the last it been working fine on
Yep the MiFlashPro does not let u flash old ROM and won't allow u to downgrade
Does anyone know of a way to side load recovery ROMs ?? At this point I should go try and apply for a phone repair certificate then apply for a job or internship in Xiaomi repair center so I can get access to the EDL so I can revive my phone
Related
Long story short:
EDIT: I somehow magically (after 2 hours of trying) got into recovery, cleaned and wiped everything and booted into MIUI. Switched to CM 12.1, leaving this thread for anyone that experiences the same problem.
1. I was running CM11-R24, with an early version of the Xcelerate kernel. All was fine and well but today it restarted on its own a couple of times. It would enter a bootloop that I managed to get out of by going into recovery and rebooting from there.
2. Bootloop happened again, couldn't get into recovery.
3. Installed newest twrp recovery via fastboot. No change.
4. Managed to hardbrick my phone by installing a wrong .img of a global version.
5. Managed to revert back to a softbrick by installing the right (hopefully) global version of my mobile phone.
6. I did manage to read a logcat inbetween and I remember there being something about the kernel settings being nulled to default, because there was a failed boot 2 times in a row.
Links:
Hard-brick to soft-brick procedure I followed - http en.miui.c o m thread-54139-1-1.html
Used global version: Singapore 50? Going to try other versions
Settings in MiFlash tool (using 2014.11 version). - http postimg.o r g /image/hh122e54j
Current problems:
1. When powering up the phone, it will not go beyond the Mi logo.
2. When trying to enter recovery (volup+power) I enter another loop. It is normally 10-15 seconds of Mi logo, power down, 3-5 seconds of Mi logo, power down. Repeat. I do not stop holding the recovery combination while this happens.
3. I have installed via fastboot all of these recoveries - TWRP 2830, TWRP 2860, Philz latest recovery. After installing each of them, I can not enter recovery mode again. Flashing a new recovery doesn't seem to change that.
I have access to fastboot, currently I installed the stable fastboot rom version "armani_images_JHCCNBH45.0_4.3_cn_e7e373f319".
I can not get adb to recognize the device, only fastboot. Can't get a logcat because of it. If you think I might be doing it wrong, please walk me through the process.
How do I get it back to working condition? The phone was bought in Bulgaria from a retailer, but I don't know which country it was originally shipped from, only that it's a WCDMA version.
Throw it away and get your self some reliable phone unlike redmi , it's a crap lots of issue ... I prefer Motorola .
ford.sushil said:
Throw it away and get your self some reliable phone unlike redmi , it's a crap lots of issue ... I prefer Motorola .
Click to expand...
Click to collapse
Oh oh oh don't be rude everyone has his own priorities and financial limitations
Bootloop
Dude, I have the same problem, can you help plus?
So my brother gave me his old G3 which never turned on again after 1 year or less of use, I believe the problem it had was the LG famous black screen or whatever, I never had a LG phone of my own, but I heard something about it and that it happens to up to the G4 (G5 maybe). I took it to a repair shop and they got it to turn on and make it functional, but it didn't last much longer than a month, it then started freezing completely to the state it's now, which turns on but then it freezes after 10 seconds or something.
I doubt this has anything to do with the software, but still I don't miss anything by trying. So far I've tried installing a custom ROM but there is a problem, it has no recovery nor fastboot installed, I don't even know how this is possible, and I know this is the case because when I try to access any of both I get the LG logo with some white letters on the top left saying some kind of boot security error.
I tried installing the fastboot img through my pc with sdk tools but idk if either the file was corrupted or what but I couldn't make it work (tested multiple I believe), and without the fastboot I can't install a custom recovery.
So I'm hearing any suggestions you guys might have before throwing this phone already.
Hi, I have a serious problem here and maybe somebody has an idea.
Recently i upgraded via provided OTA update to 9.5.4.0 and everything seem to work fine, but I did afterwards a factory reset (via the menu of the phone) to the device- Mi account was deleted and bootloader is locked.
So i didn´t play at all with the mobile before.
I already requested now (after the problem occured) the unlock of the bootloader and got the feedback of Xiaomi that i can use now the Unlocker tool.
Unfortunately the device needs to have an MI account binding to use the Unlocker tool.
After the factory reset the device starts from scratch and i get the famous MIUI9 beginning screen, can choose the language and the region. Then the device try approx. 30 times to continue and end always with a message (only for some seconds): "Find Device closed unexpectedly". After approx. 30 times im ending up in the MI-Recovery 3.0 where i can choose REBOOT, WIPE DATA, CONNECT WITH MI ASSISTANT (PC-SUITE)
REBOOT: will do again 30 times the message: "Find Device closed unexpectedly"
WIPE DATA: starts from the choose of language and region again and it doesn´t matter which language i choose ends up in the MI-Recovery 3.0
CONNECT WITH MI ASSISTANT: ends up with the english version, that i can´t connect, but with the Chinese version, i can at least open the downloaded ROM 9.5.4.0 and start the flashing process which hang up immediately and doesn´t go beyond 0%. It ends up with some chinese messages i can´t read
FASTBOOT could be reached by pressing Vol- + On/Off, but doesn´t help with a locked bootloader i guess
So if anybody have an idea how to overcome the situation it would be quite helpful.
Thx
I think you can flash fastboot miui rom with locked bootloader, just search the google for procedure, you would need to delete some lines in bat file for it to work. You will loose all data of the phone for sure, and you will need a miflash tool. After that you are good as new. It might be an issue that you have not enabled developer part. If this doesnt work, try to flash a recovery image via original recovery, i think i saw it somewhere ( cant post url)..
Yes, please share the link if possible, esp. the information about the BAT file, cause actually i searched since days and tried from MiFlash Tool until QFil everything.
I got developer part enabled before, but doing a reset to factory doesn´t allow me to re-enable anything.
How to flash something from original recovery, cause i´m not able to boot e.g. into EDL mode- I only can do something in FastBoot mode and meanwhile i´m a bit lost, cause i tried Recovery ROMS as well as FastBoot Roms and all of my flashing activities end up in the same scenario. Every flashing possibility i know is aborted.
Thx & cheers
Exact the same problem for me.
i have the same problem, some help would be great.
neo920768 said:
Hi, I have a serious problem here and maybe somebody has an idea.
Recently i upgraded via provided OTA update to 9.5.4.0 and everything seem to work fine, but I did afterwards a factory reset (via the menu of the phone) to the device- Mi account was deleted and bootloader is locked.
So i didn´t play at all with the mobile before.
I already requested now (after the problem occured) the unlock of the bootloader and got the feedback of Xiaomi that i can use now the Unlocker tool.
Unfortunately the device needs to have an MI account binding to use the Unlocker tool.
After the factory reset the device starts from scratch and i get the famous MIUI9 beginning screen, can choose the language and the region. Then the device try approx. 30 times to continue and end always with a message (only for some seconds): "Find Device closed unexpectedly". After approx. 30 times im ending up in the MI-Recovery 3.0 where i can choose REBOOT, WIPE DATA, CONNECT WITH MI ASSISTANT (PC-SUITE)
REBOOT: will do again 30 times the message: "Find Device closed unexpectedly"
WIPE DATA: starts from the choose of language and region again and it doesn´t matter which language i choose ends up in the MI-Recovery 3.0
CONNECT WITH MI ASSISTANT: ends up with the english version, that i can´t connect, but with the Chinese version, i can at least open the downloaded ROM 9.5.4.0 and start the flashing process which hang up immediately and doesn´t go beyond 0%. It ends up with some chinese messages i can´t read
FASTBOOT could be reached by pressing Vol- + On/Off, but doesn´t help with a locked bootloader i guess
So if anybody have an idea how to overcome the situation it would be quite helpful.
Thx
Click to expand...
Click to collapse
This seems to be a major bug I had it but resolved it by following this Test Point Method: http://en.miui.com/thread-1351514-1-1.html :good:
I used uBreakiFix to remove the back without chipping the did the process myself
@andril: Thx for the answer. Honestly from all what I read up to now, I expect such an answer, but I still have some questions:
Is this a bug, which is related to the latest upgrade only, or could this be happen also with older SW release?
Does the EDL testpoint method really work with the newest release I have?
Does it make sense to wait maybe for a new release to try the PC-Suite method again?
I don‘t fear to open the device, but want to avoid this of course if there is any possibility.
Thx&cheers
Gosh I was considering resetting my phone before selling on now I'm worried may have the same issue!
I don't think I'll be buying Xiaomi anytime soon.
@neo920768 it sounds bad but it works - @riz157 Not sure if it is a hardware bug after reset - I am glad i didn't do it after updating to the latest Global ROM
Just to give a feedback, that opening the device and flashing in EDL mode works good. Opening the device worked fine and you need to be careful about the fingerprint sensor, but after finishing you don‘t see anything on the device and everything works fine. Flashing with latest fastboot rom has also the small improvement, that you can choose between a lot of Regions, not only China.
Cheers and good luck to everybody
Thx
Hi everyone.
I have been reading a few posts about bootloops in hopes that someone would have been facing the same issue as me. It seems my case is a bit different. I am desperate for some help!
My Max 3 came initially with a chinese ROM but I followed some wonderful tutorials here and I unlocked it and installed initially the xiaomi.eu ROM. Then a couple of months later I installed AOSiP ROM, I updated it a couple of times dirty flashing over it, and settled in exactly the "AOSiP-9.0-Pizza-nitrogen-20190719" build. And there i was, for 4 months, all stable, then suddenly today I was going to unlock the phone with my fingerprint and asked for password.
This happens exactly 1 time per day but I noticed that today it was the second time. Then doesn't matter how many times I put my password correctly, it would keep asking for my password. So I decided to restart the device... and then the bootloop issue started. It starts, reaches the moment in which the AOSiP logo shows and (not even 1 second until the logo shows) freezes, and restarts the device.
I can access the recovery without issues so I didn't panic yet, I backed up all I could, wiped everything I could, started from zero: firmware 9.9.3 + AOSiP-9.0-Pizza-nitrogen-20191117 + gapps. The bootloop still there, in exactly the same way. So at this point I have no clue what could be the reason. I was always careful not to trigger any anti-rollback, it was all going good, now not even with a full factory reset seems to work. I even reinstalled the recovery.
Any ideas? does anyone know what could I try next? Thank you very much advance.
I forgot to attach some logs. I got using the TWRP Advanced > Copy Log option.
Well, I guess I completely screwed it now. I had the brilliant idea to go back to some of the original steps I did way back and flashed an old xiaomi.eu ROM "xiaomi.eu_multi_MIMAX3_8.8.9_v10-8.1", that completely bricked the phone. Screen doesn't even turn on anymore. Is it the end for my Max 3?
diegoocampo said:
Well, I guess I completely screwed it now. I had the brilliant idea to go back to some of the original steps I did way back and flashed an old xiaomi.eu ROM "xiaomi.eu_multi_MIMAX3_8.8.9_v10-8.1", that completely bricked the phone. Screen doesn't even turn on anymore. Is it the end for my Max 3?
Click to expand...
Click to collapse
The mi max 3 has arb enabled, so flashing old rom can cause it to brick.
Have you tried different button combinations to enter fastboot? If you can get to fastboot, just flash a fastboot rom, if that works.
If the brick is caused by triggering ARB, then that may cause some issues, and may need an Authorized Account to flash the ROM from scratch, with some qualcomm flashing tools things.
Though, there may be some way to bypass the authorization for mi max 3 on the internet and have your device unbricked.
Thank you for your replies. Yes probably ARB, I thought my phone had never installed a ROM with ARB and so I was safe to install xiaomi.eu_multi_MIMAX3_8.8.9_v10-8.1 (which it is also to be pre-ARB), but I guess I made a mistake at some point.
Situation now:
- with Mi Flash I am getting the authorization error with almost any ROM, with very old ROMs I am not even able to start the flashing process
- with Qualcomm QFIL tool I always get an error "function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes". And I also tried with the patched files from here https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
I think at this point I tried everything that can be tried. My bootloader was unlocked, but at this point I am not even sure if its unlocked anymore since I can't see anything on the device screen.
The only positive thing is that the phone always shows under the Windows 10 device manager "Qualcomm HS-USB QDLoader 9008", so at least is a bit alive, and with the Mi Flash at least for some ROMs starts the flash process. I am not sure if disassembling it and trying things like removing the batter would make any difference.
If anyone knows any other way to bypass authorization please let me know.
Here I am back with another update:
- I fixed the full brick by disassembling the phone and disconnecting the battery, with the battery disconnected I could finally flash a Chinese ROM. That however was just the beginning... more problems came
- Common problem I guess is that after booting with that Chinese ROM i was getting a message about how the encryption was interrupted. This was easy, just changed the file system of Data and formatted it and it was fixed.
- Now I am stuck in another hard to solve problem. Any ROM that boots will not allow me to use WiFi or SIM cards. And the reason is that the IMEI is not set anymore. Reading about it I see that this is related with the EFS partition being corrupted. Nothing seems to work now. I don't have any EFS backup . Anyone knows how to fix the IMEI in this case?
Hey XDA,
Been a long time since I last posted. Long story short, phone was in my sister's posession. She now bought a Mi 9 SE and gave me this RN5 to fiddle with it. Apparently it hard-bricked itself. No, she doesn't fiddle with android devices, as in Rooting or unlocking bootloaders.
Symptoms:
- Doesn't show any life at all - plugging it into my PC yields no "Device connected sound", plugging it into a powerbrick doesn't turn on the screen, no vibrations, no sounds coming from it
- Was never unlocked
- Had a screen replacement
What I tried so far:
- Test point method to jump into EDL mode works every time, so that's my only way in
- Flashing an older MIUI 9 ROM with the Patched .efl with MiFlash 2018 (Flash completed, still bricked)
- Flashing an older MIUI 9 ROM with the Patched .mbl with QFIL (Flash completed, still bricked)
- Flashing latest MIUI 11 with the Patched .efl with MiFlash 2018 (Flash completed, still bricked)
Once again, I can't enter Fastboot, Recovery or get the phone to interact with my PC except with Testpoint EDL method.
I welcome any ideas with open arms, so thank you for any suggestions
UPDATE #1 - Huh, after flashing the latest firmware through QFIL one last time before giving up, I left the phone on the USB Cable, connected to my PC. To my surprise, after 2 hours, the device actually powered on, flashing the MI Logo for a second and the "Battery Charging" icon for a spilt second before rebooting and repeating this. I may just leave it connected to my PC throughout the night , but chances are that it's more of a battery or battery connector problem than a firmware/software problem. Will update if something new happens.
khmmm weird behavior. Please report your progress, its really interesting stuff... learning process.
Good luck and stay safe!
Do you have an authorized Xiaomi account? I also encountered a similar problem, but every time I swipe in, it prompts for authorization.
xiebincnz said:
Do you have an authorized Xiaomi account? I also encountered a similar problem, but every time I swipe in, it prompts for authorization.
Click to expand...
Click to collapse
Did you use patched mbl or elf file??