Related
Hello everyone. Well, as per the title, after I flashed a new custom ROM (Ivan's AOSP to be specific), my Mi3 refused to boot properly and get stuck in the bootloop at the Mi logo and it would bootloop again and again and again....
Now, if I tried to enter twrp recovery by holding power button + volume up, it would refuse to boot into recovery and just bootloop again. But, I was able to access fastboot mode (don't know why but I could easily boot into fastboot mode)
I downloaded stock ROM for Mi3 and tried to flash it via MiFlash and it succeeded but the device would still bootloop. I also attempted to flash twrp recovery via flashboot and it succeeded, again, but my phone would refuse to at least boot into twrp recovery mode, again. Naturally my phone still had the bootloop at the Mi logo, sigh.
I don't know what to do anymore, aside from sending my phone to repair center that might charge a fortune. Please help!
try to flash official twrp recovery via fastboot
Rahuljs said:
try to flash official twrp recovery via fastboot
Click to expand...
Click to collapse
How to flash it ?? Method pls...
Currently i installed Kingroot in slimbit LP rom but after see people suggest method i uninstalled it & follow him tap root access in devolopment section & reboot but still not get Root access Than i try go in TWRP restore back this rom my phone stuck+ bootloop & keep loading in MI logo only !!! Pls help HELP HELP !! What should i do... i try fastboot flash fastboot rom failed too HELP HELP HELP !!!
Not going to send to phone center & currently my ROM can't not boot because of extend partition before & not stock partition... Help me PLEASE !!!
Many users confirmed the same symptoms. Is it possible that the damage caused by "software" since some people of India have visited the service center and asked to replace the motherboard of which cost $150?
Try flashing the phone via MIUI flashing tool as you were able to access fastboot mode
http://en.miui.com/a-234.html
xypherize said:
Hello everyone. Well, as per the title, after I flashed a new custom ROM (Ivan's AOSP to be specific), my Mi3 refused to boot properly and get stuck in the bootloop at the Mi logo and it would bootloop again and again and again....
Now, if I tried to enter twrp recovery by holding power button + volume up, it would refuse to boot into recovery and just bootloop again. But, I was able to access fastboot mode (don't know why but I could easily boot into fastboot mode)
I downloaded stock ROM for Mi3 and tried to flash it via MiFlash and it succeeded but the device would still bootloop. I also attempted to flash twrp recovery via flashboot and it succeeded, again, but my phone would refuse to at least boot into twrp recovery mode, again. Naturally my phone still had the bootloop at the Mi logo, sigh.
I don't know what to do anymore, aside from sending my phone to repair center that might charge a fortune. Please help!
Click to expand...
Click to collapse
Here is the link for tutorial for flashing recovery via fastboot mode. All commands are same just download the twrp recovery image from here. DON'T FORGET TO RENAME THE IMAGE FILE, BECAUSE ADB DOESN'T RECOGNISE ANY SPECIAL CHARACTER.
what did you do ? I'm stuck in the same situation word by word.
did you solve this issue ?
yohaneseko said:
Many users confirmed the same symptoms. Is it possible that the damage caused by "software" since some people of India have visited the service center and asked to replace the motherboard of which cost $150?
Click to expand...
Click to collapse
Seems like the problem is caused either because of this, or your battery's PCB simply fried because of unknown reason, maybe because faulty charger/cable or wrong charge voltage setting by the kernel? Also, seems like most of the similiar case stems from MM roms, including MIUI's own chinese developer ROM.
Some people with the exact same case stated that after replacing the battery, the device worked again, like this guy on iFixit: https://www.ifixit.com/Guide/Xiaomi+Mi+3+Battery+Replacement/50785
I haven't tested it yet on my bricked device (just ordered the battery today), but I really hope it was just the battery. I think fried mobo is kinda unthinkable, since if the mobo got fried, you probably can't even flash anything since the eMMC would probably also inaccessible.
Hi @rxl.noir, urang Bandung?
How much does it cost for battery replacement? I have sent my Mi3 to the seller because it's not even one year already.
rxl.noir said:
Seems like the problem is caused either because of this, or your battery's PCB simply fried because of unknown reason, maybe because faulty charger/cable or wrong charge voltage setting by the kernel? Also, seems like most of the similiar case stems from MM roms, including MIUI's own chinese developer ROM.
Some people with the exact same case stated that after replacing the battery, the device worked again, like this guy on iFixit: https://www.ifixit.com/Guide/Xiaomi+Mi+3+Battery+Replacement/50785
I haven't tested it yet on my bricked device (just ordered the battery today), but I really hope it was just the battery. I think fried mobo is kinda unthinkable, since if the mobo got fried, you probably can't even flash anything since the eMMC would probably also inaccessible.
Click to expand...
Click to collapse
yohaneseko said:
Hi @rxl.noir, urang Bandung?
How much does it cost for battery replacement? I have sent my Mi3 to the seller because it's not even one year already.
Click to expand...
Click to collapse
Heyaa~
For the battery, you could easily found it on Tokopedia started from 110k, although most of them are shipped from Jakarta. The replacement process is quite easy, you might only need #0 Phillips or any small plus screwdriver, a plastic card (for spudge replacement), and some guts :q. The details and steps are on my prev. post.
I haven't tried to sent it to the seller/distributor, since it might take a long time to get it done.
Just a little update;
I replaced my battery on my Mi3 that have the same exact case as yours, and it finally works. No more short bootloop, no more stuck in fastboot.
Hello guys...
I need a help. First, I will not gonna blame anyone for spreading the beta/alpha ROM links here.
I believe that many of Mi3w users are very exciting to hear that their device will get an upgrade. And I, one of them who want to be the first to taste Android M on Mi3, officially with MIUI.
The problem is, when updating from 6.1.12 to 6.1.21, suddenly my Mi3w experiencing short bootloop. Normally, boot process will display android text below MI.com, this short bootloop only display MI.com for about 2 seconds and after that, my device turn off, and on again with the same symptom. This process will drain battery very-very fast.
I tried several times to flash fastboot (yes, I still can access the fastboot via vol down + power), at the end of the process, the bootloop happens again and again.
If I kind of lucky, I can access recovery. I tried also to wipe all data, after I reboot, the bootloop happens again and again.
I have search the MIUI forum and found that many, not only me, experiencing the same. Is it possible that this is an error, a weakness, faulty the Mi3 devices have? If so, it was so shameful since Mi3 is one of their flagship.
Oh, anyway... Is there anybody here who can help me fix this problem?
Same for me. Flashed twrp via fastboot and installed ivans 6.0 for now because of the new partition table. Waiting for fix.
Hello everyone,
I have-or had- MI5 with latest cm14.1 on it, today I downloaded the latest rom from xiaomi.eu -Nougat-. I rebooted into recovery, wiped partitions, flashed the new rom, flashed successfully, and then flashed a font zip, the installer hanged at unmounting system for a long time, I forced rebooting it through holding power button the phone turned off and then never worked. nothing happens, no led when connecting to charger, pc does not recognize the phone at all, no sounds when connecting it. recovery and bootloader does not open. it is completely DEAD. Any help?
same h ere except i didn't get any errors while flashing except the normal command[log] error for all nougat roms. phone is just dead with no signs of life.
iXanza said:
same h ere except i didn't get any errors while flashing except the normal command[log] error for all nougat roms. phone is just dead with no signs of life.
Click to expand...
Click to collapse
I got this error as well,
After some search it seems using a deep flash cable could, I cannot make one currently so maybe you could take a look and try it
http://forum.xda-developers.com/showpost.php?p=69727277&postcount=2
I just checked the second post in the xiaomi eu thread
"- NEVER wipe /system partition manually in your life!"
hmm, I have always done this
Edit:
Many people reporting the same issue their.
There's another way to go to EDL mode which is this
https://www.youtube.com/watch?v=ED96PJ-qYMM
I haven't tried it yet as I don't have copper tweezers.
iXanza said:
There's another way to go to EDL mode which is this
https://www.youtube.com/watch?v=ED96PJ-qYMM
I haven't tried it yet as I don't have copper tweezers.
Click to expand...
Click to collapse
People reported it worked in xiaomi eu thread, gonna try once I have the tools, I wonder why the * dev didn't write "- NEVER wipe /system partition manually in your life!" before the download links
IMTLD said:
People reported it worked in xiaomi eu thread, gonna try once I have the tools, I wonder why the * dev didn't write "- NEVER wipe /system partition manually in your life!" before the download links
Click to expand...
Click to collapse
No clue. I'm taking it to the shop for them to do it for me tomorrow.
https://www.youtube.com/watch?v=ED96PJ-qYMM
Do follow the videos, i was hard brick 2 times but now it's working
The issue is, you flashed the CM14.1 on low battery, this then messed up the battery reading, while your device showed somewhere like 50% infact it was around 10%, what need to be done is, do a hard reset with power button a few times while connected to a charger, use a new charger/cable and let it charge for a long time, itll then switch on and charge, leave it to charge till 100% then do a full wipe including internal storage and install a new OS
Shaky156 said:
The issue is, you flashed the CM14.1 on low battery, this then messed up the battery reading, while your device showed somewhere like 50% infact it was around 10%, what need to be done is, do a hard reset with power button a few times while connected to a charger, use a new charger/cable and let it charge for a long time, itll then switch on and charge, leave it to charge till 100% then do a full wipe including internal storage and install a new OS
Click to expand...
Click to collapse
I don't really think that this is the problem because the "rom" flash completely successfully. I don't think that the font flash would cause all this mess. Anyway, I left it charging overnight and I keep pressing power button with vol +/- but nothing happens. Thanks anyway. it seems I have to either use test points or deep flash cable.
Hard bricked the phone with the same ROM here, tried to solve it with the video's testpoints (making contact between the two dots and plugging the USB).
Fortunately, MiFlash with adb and qualcomm drivers recognized the device. So I flashed many fastboot ROMs (miui 7/8 dev&stable) via MiFlash, but none of them made the device wake up. The only signal of life is the led blinking red when connected to a usb.
Still trying...
EDIT: ok, got it booting now. The red blinking led is actually a good sign, it means low battery. I just let it charge for about 20 min and the led changed to yellow, and then I could boot it up.
It seems like in all that time the phone was plugged into my PC usb port for flashing, it didn't charge the battery. So I think we should take into account what Shaky156 said, just in case.
jiaming2009 said:
Hard bricked the phone with the same ROM here, tried to solve it with the video's testpoints (making contact between the two dots and plugging the USB).
Fortunately, MiFlash with adb and qualcomm drivers recognized the device. So I flashed many fastboot ROMs (miui 7/8 dev&stable) via MiFlash, but none of them made the device wake up. The only signal of life is the led blinking red when connected to a usb.
Still trying...
Click to expand...
Click to collapse
I just revived my mi5 using the test point method, it is rather simple actually.
Make sure you are using miflashtool beta,
I downloaded this rom china developer
I noticed that even though I chose save user data, I still lost my data.
IMTLD said:
I just revived my mi5 using the test point method, it is rather simple actually.
Make sure you are using miflashtool beta,
I downloaded this rom china developer
I noticed that even though I chose save user data, I still lost my data.
Click to expand...
Click to collapse
Good to know it also worked for you, I just didn't believe that my battery was depleted from 70% just by hardbriking it...
After installing TWRP it asks to decrypt data even though I did not encrypt, hmmm what now
Edit:
I just did factory reset in TWRP and now I can see sdcard.
IMTLD said:
Hello everyone,
I have-or had- MI5 with latest cm14.1 on it, today I downloaded the latest rom from xiaomi.eu -Nougat-. I rebooted into recovery, wiped partitions, flashed the new rom, flashed successfully, and then flashed a font zip, the installer hanged at unmounting system for a long time, I forced rebooting it through holding power button the phone turned off and then never worked. nothing happens, no led when connecting to charger, pc does not recognize the phone at all, no sounds when connecting it. recovery and bootloader does not open. it is completely DEAD. Any help?
Click to expand...
Click to collapse
I also had my Mi5 die earlier today. Here's what I did to get it back:
1. Popped-open the back cover, removed the screws from the top panel
2. Disconnected battery (left side)
3. Connected battery back
4. Shorted the two contacts at the right side of the board
5. Plugged original USB in
Note that using a deep flash cable is a less intrusive way of doing steps 1-5, but that's what worked for me.
At this point, the PC detected the phone in EDL mode. I then attempted to flash the fastboot ROM for Mi 5, however, I kept getting errors about Missed Hello / Issue with COM port.
6. Downloaded an up-to-date version of Mi Flash (beta didn't work for me), disable Signature Enforcement (Windows 10) and install Qualcomm drivers
7. Downloaded a MIUI 7.5 fastboot rom
8. Flashed, got an error, about storage being not enough... But the screen turned on with the Mi logo. I was finally able to get the phone into Fastboot.
9. Successfully flashed MIUI 7.5 ROM using Mi Flash.
If you are still getting the COM port issue or Hello, try disconnecting the battery again and repeating steps 3-5.
Good luck.
idmissile said:
I also had my Mi5 die earlier today. Here's what I did to get it back:
1. Popped-open the back cover, removed the screws from the top panel
2. Disconnected battery (left side)
3. Connected battery back
4. Shorted the two contacts at the right side of the board
5. Plugged original USB in
Note that using a deep flash cable is a less intrusive way of doing steps 1-5, but that's what worked for me.
At this point, the PC detected the phone in EDL mode. I then attempted to flash the fastboot ROM for Mi 5, however, I kept getting errors about Missed Hello / Issue with COM port.
6. Downloaded an up-to-date version of Mi Flash (beta didn't work for me), disable Signature Enforcement (Windows 10) and install Qualcomm drivers
7. Downloaded a MIUI 7.5 fastboot rom
8. Flashed, got an error, about storage being not enough... But the screen turned on with the Mi logo. I was finally able to get the phone into Fastboot.
9. Successfully flashed MIUI 7.5 ROM using Mi Flash.
If you are still getting the COM port issue or Hello, try disconnecting the battery again and repeating steps 3-5.
Good luck.
Click to expand...
Click to collapse
Thanks for the reply, but I already fixed it this way. I used miflashtool beta since the final release did not work.
The problem is did you lose your data after the flash? because I lost mine even though I checked save data in miflashtool
IMTLD said:
Thanks for the reply, but I already fixed it this way. I used miflashtool beta since the final release did not work.
The problem is did you lose your data after the flash? because I lost mine even though I checked save data in miflashtool
Click to expand...
Click to collapse
At that point, I didn't really care if I lost data since I didn't have much on it anyway. Nice to hear that you got yours back. Those were dark hours, yes?
Thanks for giving a hope (checking way to recover from video). I'll get proper screwdrivers soon and try do the same.
I have narrowed down the issue, its the nougat firmware thats caused these recent issues. Xiaomi has distributed an unstable bootloader. I highly recommend reverting back to marshmallow firmware and OS
Shaky156 said:
I have narrowed down the issue, its the nougat firmware thats caused these recent issues. Xiaomi has distributed an unstable bootloader. I highly recommend reverting back to marshmallow firmware and OS
Click to expand...
Click to collapse
but how my mi5 now hardbricked no fastboot no recovery no edl
IMTLD said:
People reported it worked in xiaomi eu thread, gonna try once I have the tools, I wonder why the * dev didn't write "- NEVER wipe /system partition manually in your life!" before the download links
Click to expand...
Click to collapse
I can confirm that this 100% works for me. You need to be a bit patient with the tweezers and getting the contact points right. It didn't immediately work for me, and I think I had to try a dozen times at least. But eventually it did recognize it. Once MiFlash can see it, you need to use the latest China stable rom. I tried the latest china dev, but it kept on giving errors of missing hello packets.
Hello,
my Redmi 4x won't boot. I tried to find some solution for this issue, but I can't find it anywhere, so I created this new thread to ask you for your help.
Last night I was out in the city and my phone died because of low battery, so after I came home I just wanted to charge it as usual. Battery logo showed up and it was behaving as always, but when I tried to turn it on it couldn't boot again.
After pressing the power button the splash screen flashes for a brief moment and then it just turn off again. This happens all the time from the moment my phone died. I'm not sure what went wrong here. I can't get it to recovery mode either. So I wanted to do a fresh start and flash it again with new ROM here (Ressurection Remix 6 is what I have now)
I'm able to get it on fastboot mode, but once I try to flash it with MiFlash I get error message like "error:FAILED (remote: Critical partition flashing is not allowed)"
So I looked up for a solution and I found that I need to get it in EDL mode with adb.exe
I tried this solution but with no luck. Phone is restarting but it won't turn on again and the fastboot mode is lost.
I'm not really sure if I have right drivers for it. Qualcomm HS-USB Diagnostics 900E is what I have now. I can't also change the usb debugging mode obviously, so I'm also trying to find some solution for this issue either (is there any chance how to turn it on with adb.exe?)
I think it's softbricked but i'm not really sure.
Thank you for your help
p3wp3w said:
Hello,
my Redmi 4x won't boot. I tried to find some solution for this issue, but I can't find it anywhere, so I created this new thread to ask you for your help.
Last night I was out in the city and my phone died because of low battery, so after I came home I just wanted to charge it as usual. Battery logo showed up and it was behaving as always, but when I tried to turn it on it couldn't boot again.
After pressing the power button the splash screen flashes for a brief moment and then it just turn off again. This happens all the time from the moment my phone died. I'm not sure what went wrong here. I can't get it to recovery mode either. So I wanted to do a fresh start and flash it again with new ROM here (Ressurection Remix 6 is what I have now)
I'm able to get it on fastboot mode, but once I try to flash it with MiFlash I get error message like "error:FAILED (remote: Critical partition flashing is not allowed)"
So I looked up for a solution and I found that I need to get it in EDL mode with adb.exe
I tried this solution but with no luck. Phone is restarting but it won't turn on again and the fastboot mode is lost.
I'm not really sure if I have right drivers for it. Qualcomm HS-USB Diagnostics 900E is what I have now. I can't also change the usb debugging mode obviously, so I'm also trying to find some solution for this issue either (is there any chance how to turn it on with adb.exe?)
I think it's softbricked but i'm not really sure.
Thank you for your help
Click to expand...
Click to collapse
Hi, most likely your battery is faulty. Current draw during Android kernel boot up phase is above 1A whereas only around 0.2A for a working OS, that's why neither OS nor recovery can start when the battery develops high ESR (internal resistance). Do the following test:
fully recharge the battery
do not disconnect the charger
turn it on
Your Android may now actually work again but you must use a short quality cable connected to a 2A+ charger, which will support the battery at boot time - and you can disconnect it later.
k23m said:
Hi, most likely your battery is faulty. Current draw during Android kernel boot up phase is above 1A whereas only around 0.2A for a working OS, that's why neither OS nor recovery can start when the battery develops high ESR (internal resistance). Do the following test:
fully recharge the battery
do not disconnect the charger
turn it on
Your Android may now actually work again but you must use a short quality cable connected to a 2A+ charger, which will support the battery at boot time - and you can disconnect it later.
Click to expand...
Click to collapse
Thank you, but the battery wasn't the main issue, because once I was able to flash it through EDL mode to the latest stable official ROM, the battery was on 93% already.
Now I'm stuck with MI logo and powered by android with 3 blinking dots above. I watched somewhere, that it could last for 7 minutes, but for me even the 15 minutes is not enough, so I guess i'm in bootloop.
For some reason my bootloader is locked again, even though I already made the unlocking process earlier before I flashed to Resurection remix 6. My phone doesn't even appear in device manager. I can't even use it as a storage, so I could try to flash it to custom ROM.
I'm not really sure wat happened and how is it possible to brick your phone by just draining your battery to 0%
Ok, phone is alive again. It booted up right after I inersted microSD card in slot. I didn't know this was necessary...
Hey!
I was using my phone as normal, and installed an update for PixelPlusUI, it was working fine and all, until earlier today, i tried going into recovery to fix an app issue. After that, the phone just bootlooped. I figured that going into Fastboot would fix that, but the problem is, i can't reach any of those modes. It just goes to the Redmi logo, reboots, and repeats that infinitely.
I heard about EDL mode, but that seems atleast so far, unreacheable.
Is there any way for me to reach it? Maybe by letting the battery dry out and then plug the powered off phone with Volume -, or am i out of luck here? Im pretty sure this is caused by the stupid VBMeta checks XIAOMI phones has.
Matsilagi said:
Hey!
I was using my phone as normal, and installed an update for PixelPlusUI, it was working fine and all, until earlier today, i tried going into recovery to fix an app issue. After that, the phone just bootlooped. I figured that going into Fastboot would fix that, but the problem is, i can't reach any of those modes. It just goes to the Redmi logo, reboots, and repeats that infinitely.
I heard about EDL mode, but that seems atleast so far, unreacheable.
Is there any way for me to reach it? Maybe by letting the battery dry out and then plug the powered off phone with Volume -, or am i out of luck here? Im pretty sure this is caused by the stupid VBMeta checks XIAOMI phones has.
Click to expand...
Click to collapse
Vbmeta means Android Verified Boot.
Vbmeta is default for all android devices and it was made by Google.
It is not specific made by Xiaomi.
Android Verified Boot 2.0
https://source.android.com/security/verifiedboot/avb
What changes did you do when you fixed the app issue?
Couldn't do any, just tried to boot into recovery, then got into that bootlooop cycle, couldn't reach anything.
Managed to get into EDL and SP Flash Tool mode, however, im a bit confused on what i need to flash to get it back to life with stock MIUI or atleast boot to main system to use ADB.
My IMEI is fixed on the phone stickers so i can reasily recover that aswell, any help is appreciated.
EDIT: Now i just need help flashing as it seems, what do i need to do to properly re-flash / re-boot the phone without losing IMEI and that sorta stuff? I plan on switching back to Pixel Plus UI again so, it isn't an issue.
EDIT2: Completely fixed, followed VD's guide on EDL/Mediatek Bypass method and flashed a normal GLOBAL rom, all was fixed, no IMEI lost.