hello
i have problem with mi3w
i run antutu benchmark or run recording video or else high load process - my device go to bootloop
if i connect charger (AC or USB from laptop) and run same high load process - my device is work perfect
how i can resolve my probleme?
thanks
ps: factory reset, reflash to miui isn't help
Related
Phone Information : HTC Incredible S, S-ON, 4EXT Recovery
I was using SVHD 2.1 ROM from quit some time, since last week, phone was lagging too much and when I connect phone to PC it was not showing me storage options. Phone was charging but I did not see any increase in battery percentage. I wanted to try VIVOKAT by szezso so went for flashing the ROM. This is where the problem started.
I did wipe data, wipe cache, wipe dalvic and wipe boot. After that I flashed VIVOKAT and when I try to flash boot.img, I found that it was not showing me "fastboot usb" mode. I tired different cable with no luck. And as expected phone is stuck in boot animation.
I thought there might be driver issue, so I re-installed HTC Sync but that also did not help.
Later I did restore of backup taken using CWMR before rooting, Now, restore appears to be successful, but phone is not booting, when I try to start it, it restarts into recovery.
can you guys please help me in resolving this issue
I tried with other PC and other HTC phone combination, USB Cable is fine and other phone is detected so I believe my phone's USB is not working.
When I restarted my phone with USB connected windows indicates that device is connected/disconnected and gives USB error. If I click that message USB devices window opens and it says - Windows has stopped this device because it has reported problems. (Code 43).
What options I have now?
I reflashed SVHD 2.1 and kangaroo kernal v19 on which I was earlier and phone booted
will check USB again after full recharge and will let you guys know.
anyone knows if replacing USB port (phone hardware) will help? asking as phone is charging normally when connected to charger but not when connected to PC
Lately I was flashing mi3 trough fastboot on w7ulti64bit when something went wrong and now its cold dead.
I have been looking for solution everywhere and as usual xda is my last resort for help with phones, usually I found here what I was looking for but this time it is first time when I have to post new threat.
So basically I found that battery controller had some cold soldier on chip, whole module gives 0v while cell itself 2,8v so I think I fixed it since now whole battery module shows 3.3v and cell itself 3.8v after charging.
But im unable to wake up phone in to fastboot or any other way to reflash it.
When connected to 2000mAh charger there is solid red light, when connected to PC it lit for a second then goes off and PC recognizes mi3 as USB input device and HID compliant device.
I have tried to update drivers for those devises so miflash would recognize it and allow to flash it but without any success.
Any idea what else I could do with it, or how to force flash to flash at least boot sector?
Shamoth said:
Lately I was flashing mi3 trough fastboot on w7ulti64bit when something went wrong and now its cold dead.
I have been looking for solution everywhere and as usual xda is my last resort for help with phones, usually I found here what I was looking for but this time it is first time when I have to post new threat.
So basically I found that battery controller had some cold soldier on chip, whole module gives 0v while cell itself 2,8v so I think I fixed it since now whole battery module shows 3.3v and cell itself 3.8v after charging.
But im unable to wake up phone in to fastboot or any other way to reflash it.
When connected to 2000mAh charger there is solid red light, when connected to PC it lit for a second then goes off and PC recognizes mi3 as USB input device and HID compliant device.
I have tried to update drivers for those devises so miflash would recognize it and allow to flash it but without any success.
Any idea what else I could do with it, or how to force flash to flash at least boot sector?
Click to expand...
Click to collapse
Try mi flash tool
Main problem is that I have tried all 3 miflash I could found 2.11.6 20131108 20140509 and none of them recognizes device and I can't even initiate flashing process ;/
it sounds like a driver issue. just download all the drivers you can find for your phone.
Shamoth said:
Lately I was flashing mi3 trough fastboot on w7ulti64bit when something went wrong and now its cold dead.
I have been looking for solution everywhere and as usual xda is my last resort for help with phones, usually I found here what I was looking for but this time it is first time when I have to post new threat.
So basically I found that battery controller had some cold soldier on chip, whole module gives 0v while cell itself 2,8v so I think I fixed it since now whole battery module shows 3.3v and cell itself 3.8v after charging.
But im unable to wake up phone in to fastboot or any other way to reflash it.
When connected to 2000mAh charger there is solid red light, when connected to PC it lit for a second then goes off and PC recognizes mi3 as USB input device and HID compliant device.
I have tried to update drivers for those devises so miflash would recognize it and allow to flash it but without any success.
Any idea what else I could do with it, or how to force flash to flash at least boot sector?
Click to expand...
Click to collapse
Same problem here, waiting for someone give the solution
if the device is not getting detected in any of the mi flash tools,i feel its a clear sign of driver issues ,
ZenR2 said:
if the device is not getting detected in any of the mi flash tools,i feel its a clear sign of driver issues ,
Click to expand...
Click to collapse
r u following correct procedure for using MI flash tool ?
is ur Phone able to boot to FLash mode ( turn phone off > Press volume + Key then Press Power on - it will show flash mode )
Now Open MI Flash tool > Press Refesh > it will show phone now ( a number will b shown instead of name Xiamo Mi3)
Now Extract Fastboot rom to C Drive ( it should look like this C:\ROM (Location should not cointain space)
Now click Browse > advance > select C:\ROM\Folder\ select bat file
Its not drivers issue since its get detected as QUALCOMM HS-USB QDLoader 9008 or QUALCOMM HS-USB Diagnostic 9006 depending of its state.
In QDLoader it is recognized by miflash as COM20 device and I can upload by miflash or qpst boot image, then it switches to diagnostic that is recognized by some sort of string and I can upload/proceed with rest of rom flashing that includes creating partitions and writing data to them.
Main problem is that when its successfully flashed it is still cold dark, while PC can see it and all partitions like 28 of them...
And I think its related to the fact that qpst reports phone as in download mode.
Any idea how to exit that mode, like in Mi2 that was forced to enter "service" by shortening some pins to put it download mode to flash cold dead ones?
agdag said:
magdag from en.miui.com forum seems to be able to hekp ..or try [email protected] , jason provide paid service
Click to expand...
Click to collapse
You were already looking at it
Kinda wasted a lot of Mine and Yours time and some of my money
If You got any other ideas since that time how to resurrect it just let me know.
Any solution?
Is there any solution to this problem? My phone has been cold brick for 3 days now. Doesnt boot up or charge up. Detected on connecting to PC with a sound, but Shows as Com 10 or 20 on Miflash and thus cannot be flashed.
Cannot boot into fastboot as well.
Anyone anything?
androidy88 said:
Is there any solution to this problem? My phone has been cold brick for 3 days now. Doesnt boot up or charge up. Detected on connecting to PC with a sound, but Shows as Com 10 or 20 on Miflash and thus cannot be flashed.
Cannot boot into fastboot as well.
Anyone anything?
Click to expand...
Click to collapse
You can check the steps I took for recovering from a similar problem here: http://en.miui.com/forum.php?mod=viewthread&tid=22811
If you have any other questions, tag me on your reply and i'll try my best to help.
I bricked my device flashing magisk. So, I bought fastboot cable and restored it using KFHD_SRT_v1.3.5- 7.3.0: https://forum.xda-developers.com/showthread.php?t=1951254
After this I flashed custom ROM (lineage OS 13) that I was using before my device got bricked. I faced so unusual problems with USB connection and charging (described below). So, I restored stock firmware again but this didn't help at all....
Problem I faced after restoring tablet:
1) Usb connectivity and charging.
After connecting device to computer there is no reaction on computer or tablet (even no sound and charging!). Same with connecting to charger. Tablet is charging but the proccess is not displayed anywhere (even in battery options in settings), except increasing battery percentages in the status bar. If I connect device to computer or charger and will reboot it (tablet, not PC) it will be recognized and charging process will begin! BUT after disconnecting device it will show still connected to the PC or charger until next reboot...
2)Wakelock and battery draining.
So, the next issue is that device doesn't go to deep sleep and even sleep. I installed BetterBatteryStats to check the processes and wakelocks and found "usb3v3_wake_lock" in kernel wakelocks which prevents tablet to go into sleep mode. It's always in active mode, aproximately 98% of time, so battery draining really fast...
First of all, I thought that problems was caused by installing TWRP, but after restoring to stock had no sense. Even after restoring stock recovery and boot via KFHD_SRT_v1.3.5 it does't help. Also I've tried to flash diffrent Roms with different android OS versions (RR, lineage, AOSP). For now I am wondering what could cause described problems and would like to find solution
Hi
After googleing a lot and trying at least 1001 ADB and Fastboot-tutorials I still am stuck. I only want to flash my A2 with stock ROM, but as soon as fastboot kicks in the connection stops.
My phone is unstable (how? see below) but not bricked! I can ...
... access recovery mode and fastboot anytime
... establish data and PTP connections to my PC (Win 10)
... use it normally (apps, WLAN ...) as long as flight mode is on!!!!! :cyclops:
... connect the phone with XiaoMi Tool V2 to my PC
but as soon as fastboot kicks in I loose connection.
Meanwhile I'm out of ideas how to establish fastboot-connection.
Here's the reason I want to flash - in case it matters: After an Andorid update (or at least it seems this is the reason) the screen started to unlock/lock erratically. There never was enough time to enter the code, so I made a factory reset. The problem still prevails, but without screenlock (and looooots of patience) I can access my phone. Debugging and bootloader are turned on now. The only way to stop this screenlock/unlock behavior is to turn on flight mode ...
If the phone is connected to a PC I can hear the "unplug sound" as soon as fastboot starts and XiaoMi Tool V2 looses connection.
BTW: Even with many attempts I never managed to establish a connection to Mi PC suite.
And the USB-connection-preferences very often turn to "no data connection". To fix this I usually have to plug out/in or even change USBport or even the computer.
What should I try to flash mi Mi A2?
Thanks and greetings
Phillip
Philipp_P said:
Hi
After googling a lot and trying at least 1001 ADB and Fastboot-tutorials I still am stuck. I only want to flash my A2 with stock ROM, but as soon as fastboot kicks in the connection stops
My phone is unstable (how? see below) but not bricked! I can ...
... access recovery mode and fastboot anytime
... establish data and PTP connectios to my PC (Win 10)
... use it normally (apps, WLAN ...) as long as flight mode ist on!!!!! :cyclops:
... connect the phone with XiaoMi Tool V2 to me PC
but as soon as fasstboot kicks in I loose connection.
Meanwhile I'm out of Ideas how to establish fastboot-connection.
Here's the reason I want to flash - in case it matters: After an Andorid update (or at least it seams this is the reason) the screen startet to unlock/lock erratically. There never was enoug time to enter the code, so I made a factory reset. The problem still prevails, but without screenlock (and looots of patience) I can access my phone. Debugging and bootloader are turned on. The only way to stop this behaviour ist to turn on Flight Mode ...
If the phone ist connected to a PC I can hear the "unplug sound" as soon as fastbot starts and XiaoMi looses connection.
BTW: Even with many atempts I never managed to estabilsh a connection to Mi PC suite.
And the USB-Connection-Pfreferences very often turn to "no data connection". To fix this I usually have to plug out/in or even change USBport or even the computer (-> Win -Laptop)t! Whith no result.
What should I try to flash mi Mi A2?
Thanks and greetings
Phillip
Click to expand...
Click to collapse
Sounds strange . Does RIL work ? Like gsm and sim card ...anyway you need to buy a screwdriver from Amazon or Wish or Whereever and open your phone ..
Search for tutorial videos on youtube on " test point " . You will short the phone forcing it into edl ( deep flash ) mode . In edl you don't use fastboot but rather qualcomm 9008 drivers .
You can flash stock rom with QPST ( Qualcomm flash tool ) or just the regular Miflash from Xiaomi .
In any case ..UNINSTALL ALL I SAY ALL the stuff you have installed on your pc right now including adb .Reboot .Install Qualcomm 9008 drivers .Then download the LATEST VERY NEWEST version of Miflash that comes with drivers ..follow the instructions to install drivers and Mifash itself .
Then follow video tut to enter edl state with test point
VERY IMPORTANT HAVE MIFLASH PREPARED to flash very soon as in 1 or 2 minutes after you enter edl because there is a timeout after which you will get errors and would have to do the test point again ...
Good luck ..if the phone is stolen or contains stolen parts or you used some bypass to enter it to bypass lock screen once it connects to internet or gsm the troubles will most probably return ..if it was or is just some glitch this will solve it .
Thanks for your help!
I’m not familiar to what RIL is all about. I just googled it, and I guess it works. I can receive SMS when flight mode is turned off and I get a 4G-connection. I can’t do phone calls, but that’s due to the screenlock-problem as soon as flight mode is turned off. I can’t even enter a phone number then … :silly:
I never heard of edl before but found videos. I’ll give it a try. Thanks for all your tips, especially about the edl-timeout. :good:
One last question before I start regarding the uninstalling of EVERYTHING … How can I be sure, I got rid of EVERYTHING? Windows program uninstall showed be "Mi PC Suite", "Universal ADB driver" and "Windows driver package Android USB device class …" I uninstalled all of it.
But I also used Minimal ADB/fastboot and XiaoMi Tool V2 (and probably other stuff I don’t remember anymore) as portable versions. I can delete those fodlers, but is that really enough regarding the drivers that were installed?
Philipp_P said:
Thanks for your help!
I’m not familiar to what RIL is all about. I just googled it, and I guess it works. I can receive SMS when flight mode is turned off and I get a 4G-connection. I can’t do phone calls, but that’s due to the screenlock-problem as soon as flight mode is turned off. I can’t even enter a phone number then … :silly:
I never heard of edl before but found videos. I’ll give it a try. Thanks for all your tips, especially about the edl-timeout. :good:
One last question before I start regarding the uninstalling of EVERYTHING … How can I be sure, I got rid of EVERYTHING? Windows program uninstall showed be "Mi PC Suite", "Universal ADB driver" and "Windows driver package Android USB device class …" I uninstalled all of it.
But I also used Minimal ADB/fastboot and XiaoMi Tool V2 (and probably other stuff I don’t remember anymore) as portable versions. I can delete those fodlers, but is that really enough regarding the drivers that were installed?
Click to expand...
Click to collapse
sure for the portables just delete the folders
Giving up
Screwdrivers arrived, disassembling the phone was surprisingly easy. Actually hitting the tinytiny EDL-contacts was surprisingly difficult on the other hand. :silly: But I managed. But also with EDL my computer pretends my mobile doesn’t exist when plugged in. I guess there must be a hardware-problem somewhere. A this point I give up and buy another one. Thanks for your support, KevMetal.
Philipp_P said:
Screwdrivers arrived, disassembling the phone was surprisingly easy. Actually hitting the tinytiny EDL-contacts was surprisingly difficult on the other hand. :silly: But I managed. But also with EDL my computer pretends my mobile doesn’t exist when plugged in. I guess there must be a hardware-problem somewhere. A this point I give up and buy another one. Thanks for your support, KevMetal.
Click to expand...
Click to collapse
Sorry didn't work friend. Are you sure ? Did you remember to install Qualcomm 9008 drivers from Qualcomm ? Remembering to disable driver verification on windows 10 ...try just more time ...who knows ..
I used a computer with windows 7, because I found on the internet that there are less problems than with Win 10 …
Hi Guys,
I got given a bricked X Performance (dalvik and internal archive have been deleted) and the only feedback from the phone is when I press On+VolUp, after 3 vibrations the phone boots but it freezes on the white start SONY screen. I tried different combination of starting buttons but that's the only reaction I get back from the phone.
Sony xperia companion from the PC is not detecting any device.
I was wondering if I can try to connect using any software (which one?) trying to fastboot or enter flashmode and maybe fix somehow, can you suggest me where/which software and drivers to install in my PC?
Also, I red on the net that an extreme fix could be a hardbrick reset using testpoints, but again, I couldn't find any info in internet where are the contacts inside the phone to be used as testpoints, any clue/suggestion please?
Thanks a lot
Giulia
See if you can connect to Flash tool and reset/reinstall it: https://developer.sony.com/develop/open-devices/get-started/flash-tool/download-flash-tool/