hi all,
i have a very big issue, yesterday my zuk z2 pro goes, suddenly, to 900E error ( black screen+ blue led), after that i tried the cable methode to go on EDL, it worked, but after that, when i flash the zui 1.9 with miflash, it appears a xml error after 5 secondes, and when i flash with qfil, the flash works, but when it goes to boot, the phone goes on bootloop, i've tried that with zui 1.9 and 2.5, but same result, now i'm lost, i've no idea what to do.
P.S: my device is a z2121 4gb ram, 64gb rom, it was on 4.0 zui version, with locked bootloader
I finally found the solution, it was a hardware issue, my battery makes some shortcircuits with the mother board, one or the two must be changed, now the device booted up on zui 1.9, after this, i'll but a new device nearly, it was a very bad experience
Az_yaz said:
I finally found the solution, it was a hardware issue, my battery makes some shortcircuits with the mother board, one or the two must be changed, now the device booted up on zui 1.9, after this, i'll but a new device nearly, it was a very bad experience
Click to expand...
Click to collapse
have you changed your hardware?
the battery or mother board?
and does your phone boot normally?
thx n sorry for my english
reezalsf said:
have you changed your hardware?
the battery or mother board?
and does your phone boot normally?
thx n sorry for my english
Click to expand...
Click to collapse
The problem was the motherboard, i've unplugged every part of the motherboard, cleaned this motherboard then replugged , and the phone booted up, now it works like a charme,
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 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.
hi
my mi3 was on miui 8.1 stable last day the phone switched off and it short bootloops on the Mi logo.
it only goes into fastboot mode and i tried to flash roms via that and it dosent work.
it goes back to bootloop again.
i even tried shortcircuting the motherboard and trying to flash ROM because i thought it was hard bricked and had no success
can anyone tell me what to do or replace ?
ive heard its either eMMC or battery
thanks
https://forum.xda-developers.com/xiaomi-mi-3/help/mi3-bootloop-stays-fastboot-modus-t3656560
kingnikpic said:
hi
my mi3 was on miui 8.1 stable last day the phone switched off and it short bootloops on the Mi logo.
it only goes into fastboot mode and i tried to flash roms via that and it dosent work.
it goes back to bootloop again.
i even tried shortcircuting the motherboard and trying to flash ROM because i thought it was hard bricked and had no success
can anyone tell me what to do or replace ?
ive heard its either eMMC or battery
thanks
Click to expand...
Click to collapse
Persistant and continuous bootloops is normally a result of the battery being at the end of it's life - I would seriously recommend replacing the battery. Fortunately batteries for this device are fairly inexpensive, and like always, when troubleshooting issues - always start with replacing the least expensive components that are likely the cause to your issue.
I too had to replace the battery in my Xiaomi Mi 3W due to continous boot loops, they would only occur when attempting to do anything CPU intensive, and likewise, my device would remain on in recovery and fastboot without a problem. Anyhow, replacing the battery cleared my symptoms instantly.
Don't waste your time/money with eBay batteries. The best battery I've found, that is much alike the original is the Nohon Battery... This can be purchased at aliexpress for a good price: https://www.aliexpress.com/item/Ori...32677903782.html?spm=a2g0s.9042311.0.0.YHewuy
Best Regards,
Stickman89
Hello All
Sorry to bother you again with my troubles.
My xz1 compact (with LOS 17.1.5 last version of OS , Sony Firmware .228) wasn't charging battery anymore last night (no way to make it charge) , and went off out of battery. I dissasemblied it to check and clean the charging port, and the current came back and charged the battery full. But after reassembly the phone booted and stay stucked on start screen with unresponsive screen.
No way to unlock, no response of the touch screen, no ADB operation possible as the phone was "unauthorized" in the terminal window. .
I went rebooting on TWRP recovery to back up my files, and there the screen worked perfectly ! i could do my backups, wipe everything and reinstall LOS 17.1.5, but again on startup the touchscreen is away !! ... the touch screen looks fully functional when on TWRP, could it come from a software or hardware issue on my phone ? .
Someone in my city told me that I've could have boken one small resistors near to the screen connector on motherboard, but I can't see anything when comparing to the motherboards images
Bye and thanks for your help.
It's incredible, as I can perfectly manage the phone on TWRP recovery app, but no way to do anything on screen when a system is booted
Hello all, still trying to fix that problem... After full wipe and formatting (via TWRP, screen is working on it), and reinstall of LOS I get system to boot, but with black screen, the phone react to button press (power and volume), but no to any screen command . Is there a way to test services and perpiherals with TWRP ? Tryed to move back to sony stock firmware .228, but with bootloader unlocked it's not possible. Thank for any hint or suggestion, bye.
seven hole said:
Tryed to move back to sony stock firmware .228, but with bootloader unlocked it's not possible
Click to expand...
Click to collapse
I'm running .228 with an unlocked bootloader. If the flashtool or Newflasher isn't working then you need to use Sonys TOOL. As for your main issue, I have no idea, it is strange though.
SXUsr said:
I'm running .228 with an unlocked bootloader. If the flashtool or Newflasher isn't working then you need to use Sonys TOOL. As for your main issue, I have no idea, it is strange though.
Click to expand...
Click to collapse
Thank you @SXUsr yes it is a strange issue, as the screen works with TWRP, and the hardware looks no faulty .. my only clue is that I've touched and clean the Charging port to cure a bad connection ( and it's charging directly now )
I will try to reinstall Sony .228 from newsflasher or Sony "Emma" tool (thanks a lot for the link I couldn' find it by research) and I will maybe know if it's a soft or hardware issue !
Firmware .228 reinstalled from newsflasher . the screen seems to work .. the telephone is still with bootloader unlocked ... Now I'm back on ungoogling it . Thanks
I just wanna ask after the oct update i got bootloop now when i try to go to service center they told me that the problem is the motherboard. When i explain to them the reason i just update it then bootloop they always tell me the problem is motherboard. And i need to fix it and the cost is half the price of the phone. Now i need some help. When i try to turn on its stuck to androide one then off whne i try to go to fastboot its okay. When i charge it it turns on and off. I jus need some help.
mrvonzuela said:
I just wanna ask after the oct update i got bootloop now when i try to go to service center they told me that the problem is the motherboard. When i explain to them the reason i just update it then bootloop they always tell me the problem is motherboard. And i need to fix it and the cost is half the price of the phone. Now i need some help. When i try to turn on its stuck to androide one then off whne i try to go to fastboot its okay. When i charge it it turns on and off. I jus need some help.
Click to expand...
Click to collapse
is your bootloader unlocked?
If so, have you tried booting latest twrp image from fastboot?
Code:
fastboot boot twrp.img
Sounds like you may at least have to try to wipe and format your phone at the cost of all data.
But then you could use the situation to install a good custom ROM..
If you were doing a normal update, your phone should revert to the previous slot after a few attempted reboots.
Keep trying to reboot.
If nothing else works, try flashing september version from EDL (search it on the forums).
I flashed and still couldn't boot at first. I tried restarting a lot of times, until it got on the "Retry" or "Power off" option. I let the phone sit on this screen until it shut itself off. After tried booting up a few more times until it finally did.
I was not plugged in during this.
I'm not going near that october patch ever again.
Hello everyone,
I'm using mi A2 (64gb). It is rooted and was running on Resurrection Remix 8.6.2. Somedays earlier, I let my phone idle, suddenly it starts rebooting, just like bootlooping. After seeing that I booted in recovery and wiped dalvik and cache then rebooted and the phone rebooted in system successfully. But then I noticed the power menu appearing continuously on the home screen, I tried to dismiss it but it rebooted again and so on. From then, only the splash screen appeared for 8 seconds and it reboots again. I can boot into recovery or fastboot but only for 2-3 seconds then it reboots.
I've searched on the internet and was flashing firmware manually from fastboot but accidentally, I flashed an image file in a wrong location and the phone screen turned off and nothing appeared. Then I found that it had entered in EDL mode. but still it is rebooting and I can't flash firmware from mi flashing tool as fastboot wasn't working.
This is the problem of my phone. A help would be amazing! Thank you!
Ps. I'm new here and it is my first post so if anything is wrong. I beg your pardon and sorry for my bad English.
Rm789 said:
Hello everyone,
I'm using mi A2 (64gb). It is rooted and was running on Resurrection Remix 8.6.2. Somedays earlier, I let my phone idle, suddenly it starts rebooting, just like bootlooping. After seeing that I booted in recovery and wiped dalvik and cache then rebooted and the phone rebooted in system successfully. But then I noticed the power menu appearing continuously on the home screen, I tried to dismiss it but it rebooted again and so on. From then, only the splash screen appeared for 8 seconds and it reboots again. I can boot into recovery or fastboot but only for 2-3 seconds then it reboots.
I've searched on the internet and was flashing firmware manually from fastboot but accidentally, I flashed an image file in a wrong location and the phone screen turned off and nothing appeared. Then I found that it had entered in EDL mode. but still it is rebooting and I can't flash firmware from mi flashing tool as fastboot wasn't working.
This is the problem of my phone. A help would be amazing! Thank you!
Ps. I'm new here and it is my first post so if anything is wrong. I beg your pardon and sorry for my bad English.
Click to expand...
Click to collapse
Try shorting testpoint in motherboard then enter EDL mode,
Then use mi flash tool.need to remove battery first.
How? Watch youtube, for mi6x. Mi 6x = a2, sort of.
~yes, you need to remove/open the phone.
shizuni said:
Try shorting testpoint in motherboard then enter EDL mode,
Then use mi flash tool.need to remove battery first.
How? Watch youtube, for mi6x. Mi 6x = a2, sort of.
~yes, you need to remove/open the phone.
Click to expand...
Click to collapse
Thank you for replying
One thing to note I'm in edl mode already. Do I need to short the test points again?
Rm789 said:
Thank you for replying
One thing to note I'm in edl mode already. Do I need to short the test points again?
Click to expand...
Click to collapse
U said rebooting even in edl, if not. Dont. Just make sure you have enough battery juice.
Use xiaomi tools. Or not, I uncompressed the file and click flash all.
shizuni said:
U said rebooting even in edl, if not. Dont. Just make sure you have enough battery juice.
Use xiaomi tools. Or not, I uncompressed the file and click flash all.
Click to expand...
Click to collapse
Yes, phone is rebooting in edl mode. I also charged it to around 40 minutes before connect it to pc but no hope. I got it
Thank you so much for the clarification.
i have a similar issue, phone reboots when flashing reached vendor b and goes into bootloop, anybody ?