Related
My Xiaomi mi5 does not turn on.
No lights, fastboot is not accessible, resetting it does not do anything.
Basically for any combination of buttons that I press, nothing happens and the screen stays black - it is completely dead.
However, when I plug it into my pc, the devices shows up as qualcomm hs-usb qdloader 9008 (COM3) which is the only sign of life from the phone.
What I want to know is if it is possible for me to unbrick the phone from this situation. I understand that I need to get into fastboot in order to flash the ROM, but is there a way to get to fastboot using my pc? Or even turn the phone on with commands? At the moment ADB and Fastboot does not recognise my phone, is there a way to make it detect it from the state it is in?
Thanks
sivd said:
My Xiaomi mi5 does not turn on.
No lights, fastboot is not accessible, resetting it does not do anything.
Basically for any combination of buttons that I press, nothing happens and the screen stays black - it is completely dead.
However, when I plug it into my pc, the devices shows up as qualcomm hs-usb qdloader 9008 (COM3) which is the only sign of life from the phone.
What I want to know is if it is possible for me to unbrick the phone from this situation. I understand that I need to get into fastboot in order to flash the ROM, but is there a way to get to fastboot using my pc? Or even turn the phone on with commands? At the moment ADB and Fastboot does not recognise my phone, is there a way to make it detect it from the state it is in?
Thanks
Click to expand...
Click to collapse
Do you have all the necessary driver installed? I think yes and that is why you are seeing in (COM3) port. You can do one thing, Unplug the phone from PC and Press and Hold Vol Down (-) and plug in again. If not works then you can also Press and HOLD Vol Down and Press and HOLD Power button until you see Fast boot menu. If don't work then try the same thing with Vol UP button. Then you suppose to see a MI phone logo with a USB cable.
"qualcomm hs-usb qdloader 9008" Is a signal of Hard Brick for QCOM devices (Like for LG G2);
http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830
As you can see here, for fix it you need all partition files, all system files, and a programm
But i dont know if it will works also on SD820, you might need all files for Mi5
Just a question: How did you bricked your phone?
EDIT:
I had an idea: maybe inside fastboot rom you can find all files you need, it might be worth a try, at least you can send it to your shop where you bought it
sivd said:
However, when I plug it into my pc, the devices shows up as qualcomm hs-usb qdloader 9008 (COM3) which is the only sign of life from the phone.
What I want to know is if it is possible for me to unbrick the phone from this situation. I understand that I need to get into fas,tboot in order to flash the ROM
Click to expand...
Click to collapse
1: if you're detecting it as qcom 9008, there's a good chance it's in EDL mode, which is good news
2: download MiFlash from here: https://www.androidfilehost.com/?fid=24521665358595574
3: download the latest dev rom from here: http://update.miui.com/updates/v1/fullromdownload.php?d=gemini&b=X&r=cn&n=
4: Extract the files to C:\
5: Open MiFlash & point the folder to the root ROM folder, example: C:\gemini_foo_bar, NOT C:\gemini_foo_bar\images
6: connect your phone & select flash all (1st option from the left, bottom of MiFlash tool)
This might take a few tries (example - you might receive "missed hello packets)
Once you're done, you can stay with the China Dev, unlock the bootloader & flash a xiaomi.eu rom, or CM.
Good luck.
adwinp said:
1: if you're detecting it as qcom 9008, there's a good chance it's in EDL mode, which is good news
2: download MiFlash from here: https://www.androidfilehost.com/?fid=24521665358595574
3: download the latest dev rom from here: http://update.miui.com/updates/v1/fullromdownload.php?d=gemini&b=X&r=cn&n=
4: Extract the files to C:\
5: Open MiFlash & point the folder to the root ROM folder, example: C:\gemini_foo_bar, NOT C:\gemini_foo_bar\images
6: connect your phone & select flash all (1st option from the left, bottom of MiFlash tool)
This might take a few tries (example - you might receive "missed hello packets)
Once you're done, you can stay with the China Dev, unlock the bootloader & flash a xiaomi.eu rom, or CM.
Good luck.
Click to expand...
Click to collapse
I also had the same issue with black screen and no responses from vol. & power buttons. But when I notice that in device manger it showed the qcom driver, then I new that there was hope to recover the phone. I can confirm that this will unbrick your phone. I MiFlash'd the China Rom (non-dev), unlocked the bootloader, MiFlash'd MiFlash_xiaomi.eu_gemini_V7.2.13.0.MAACNDB_6.0 rom, sideload lastest stable EU rom, TRWP and SuperSU.
adwinp said:
1: if you're detecting it as qcom 9008, there's a good chance it's in EDL mode, which is good news
2: download MiFlash from here:
3: download the latest dev rom from here:
4: Extract the files to C:\
5: Open MiFlash & point the folder to the root ROM folder, example: C:\gemini_foo_bar, NOT C:\gemini_foo_bar\images
6: connect your phone & select flash all (1st option from the left, bottom of MiFlash tool)
This might take a few tries (example - you might receive "missed hello packets)
Once you're done, you can stay with the China Dev, unlock the bootloader & flash a xiaomi.eu rom, or CM.
Good luck.
Click to expand...
Click to collapse
Thank you so much, this has worked perfectly and saved me a lot of money! I really appreciate your help, thank you again!
sivd said:
Thank you so much, this has worked perfectly and saved me a lot of money! I really appreciate your help, thank you again!
Click to expand...
Click to collapse
Glad you could salvage your device.
Now remember - from great flashing power comes great responsibility ;]
adwinp said:
1: if you're detecting it as qcom 9008, there's a good chance it's in EDL mode, which is good news
2: download MiFlash from here: https://www.androidfilehost.com/?fid=24521665358595574
3: download the latest dev rom from here: http://update.miui.com/updates/v1/fullromdownload.php?d=gemini&b=X&r=cn&n=
4: Extract the files to C:\
5: Open MiFlash & point the folder to the root ROM folder, example: C:\gemini_foo_bar, NOT C:\gemini_foo_bar\images
6: connect your phone & select flash all (1st option from the left, bottom of MiFlash tool)
This might take a few tries (example - you might receive "missed hello packets)
Once you're done, you can stay with the China Dev, unlock the bootloader & flash a xiaomi.eu rom, or CM.
Good luck.
Click to expand...
Click to collapse
Thanks for the guide, 1 q tho: what to do when i get the "missed hello packets, try to recover" message?, wait or restart the process?
Ok, solved by disabling driver sign (press F8 during boot)
Hello , i got the same problem as described at this topic and here is my problems :
I can't turn on my phone and i can't put it in fastboot mode ( tryed a lot of buttons combinations)
But when i plug it into my pc - it recognizes as Android
I have tryed to install drivers but windows shows mistake and can't install that
When my device connected to pc and i press volume + and power buttons - in few minutes system(WIN 10) recognizes it as ADB interface(can't install drivers too) and i have acess to mi5 internal storage ( i can download photos and so on )
But mi flash doesn't see phone in any mode and i feel that my device is still alive and i can recover it but don't know how....
I will be grateful for any help !
Isteran said:
Hello , i got the same problem as described at this topic and here is my problems :
I can't turn on my phone and i can't put it in fastboot mode ( tryed a lot of buttons combinations)
But when i plug it into my pc - it recognizes as Android
I have tryed to install drivers but windows shows mistake and can't install that
When my device connected to pc and i press volume + and power buttons - in few minutes system(WIN 10) recognizes it as ADB interface(can't install drivers too) and i have acess to mi5 internal storage ( i can download photos and so on )
But mi flash doesn't see phone in any mode and i feel that my device is still alive and i can recover it but don't know how....
I will be grateful for any help !
Click to expand...
Click to collapse
If you can see it in adb, you might be able to see it in fastboot.
Try go in to fastboot (even though you can't see it on screen.)
And try fastboot oem device-info see if you can get anything. Then we go from there.
DrBubblewrap said:
If you can see it in adb, you might be able to see it in fastboot.
Try go in to fastboot (even though you can't see it on screen.)
And try fastboot oem device-info see if you can get anything. Then we go from there.
Click to expand...
Click to collapse
tryed a lot of time to go to fastboot , but nothing happened...
same issue
I've been having the same problem with my MI5, 128gb running MIUI8 6.6.23CN, unlocked bootloader
It started when I did an OTA from 6.6.16, then OTA failed, I tried again this time it downloaded full rom and went into my twrp but installation started automatically. Then it rebooted but the system stayed in black screen. I forced-rebooted it, then everything was fine and I was on 6.6.23. I was using the phone normally for a few hours, then around 6hr later after I upgraded, I took phone out of my bag and it was bricked. I tried everything, no fastboot, no adb, no recovery, no led, nothing on screen. MiFlash reconizes (cuz of the 9008 status) but flash fails. I event opened it up, disconnected the 3 cables from the battery and hold onto power buttons for few seconds to try to drain whatever power it has left in system. Reconnected battery but no change.
I gave up, put phone back in case and was going to ask friend to take it back to send to china for repair the next day, but then I too it out an hour before I go meet my friend and suddenly, phone led flashed red and I see on screen out-of-battery icon. I plugged it in to charge then LED flickered quickly in red for a bit then turn solid red, then turned orange. I let it charged for 10min or so, and pressed power+Vol_Down for few seconds. Lo and behold, I got the bunny on screen and went into fastboot. I was able to re-flash 6.6.23 and phone was good to go again. (but why did removing battery cables do the same thing? Maybe I didn’t leave it disconnected long enough?)
Good story until this part… then 2 days later, I wanted to test MI Talk with friend, I click on it, and phone froze. Both touch sensor light stayed on. I waited about 15 second and forced reboot. Phone vibrates once and then went into hard brick again. Exactly same situation, nothing works.
Now I am waitng for phone to discharge by itself. God knows how many days it will take. It was 96% charged. (1st time I had about 45% and too a day to discharge)
Only if I can get back into fastboot......
tkrave said:
I've been having the same problem with my MI5, 128gb running MIUI8 6.6.23CN, unlocked bootloader
It started when I did an OTA from 6.6.16, then OTA failed, I tried again this time it downloaded full rom and went into my twrp but installation started automatically. Then it rebooted but the system stayed in black screen. I forced-rebooted it, then everything was fine and I was on 6.6.23. I was using the phone normally for a few hours, then around 6hr later after I upgraded, I took phone out of my bag and it was bricked. I tried everything, no fastboot, no adb, no recovery, no led, nothing on screen. MiFlash reconizes (cuz of the 9008 status) but flash fails. I event opened it up, disconnected the 3 cables from the battery and hold onto power buttons for few seconds to try to drain whatever power it has left in system. Reconnected battery but no change.
I gave up, put phone back in case and was going to ask friend to take it back to send to china for repair the next day, but then I too it out an hour before I go meet my friend and suddenly, phone led flashed red and I see on screen out-of-battery icon. I plugged it in to charge then LED flickered quickly in red for a bit then turn solid red, then turned orange. I let it charged for 10min or so, and pressed power+Vol_Down for few seconds. Lo and behold, I got the bunny on screen and went into fastboot. I was able to re-flash 6.6.23 and phone was good to go again. (but why did removing battery cables do the same thing? Maybe I didn’t leave it disconnected long enough?)
Good story until this part… then 2 days later, I wanted to test MI Talk with friend, I click on it, and phone froze. Both touch sensor light stayed on. I waited about 15 second and forced reboot. Phone vibrates once and then went into hard brick again. Exactly same situation, nothing works.
Now I am waitng for phone to discharge by itself. God knows how many days it will take. It was 96% charged. (1st time I had about 45% and too a day to discharge)
Only if I can get back into fastboot......
Click to expand...
Click to collapse
You don't have to go into fastboot to use miflash if you have stock recovery
Sent from my MI 5 using Tapatalk
vf1 said:
You don't have to go into fastboot to use miflash if you have stock recovery
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
how do you flash stock recovery if you dont need to go into fastboot? now I am unable to go into recovery or fastboot as the phone does not boot at all. connecting it to PC reconizes the phone as the infamous "Qualcomm HS-USB QDLoader 9008" device.
Its been 4 days and the damn battery hasnt run out yet as I can still plug into pc and get qualcom 9008 to come up. I think I am going to send to china to get it fixed properly if I still cannot get the red flicker of low battery power to come up by tomorrow.
It has happened to me 3-4 times already. It didnt want to boot. No signs of life either. I even sent a message to the shop for sending it back..the only thing that was telling me it wasn't completely dead, was the qualcomm driver ,while on USB connection with the PC, which you are referring to as well
Here is what you could try doing. Try pressing the power button for about 30 seconds at first. If it does not boot, try bending the phone real gently back and forth (don't break it!!). Preferably, hit it gently with your palm while holding it in your other hand.( -- I know it might sound weird --) I noticed that it's shutting down while i have it in my pocket and doing some work which squeezes the phone a bit against my leg.
I came to the conclusion that some connection must become loose when some pressure is being applied to it.. Unfortunately it has to be a design flaw of the phone. Nothing random with yours or mine , in my opinion. // I have a case and tempered glass installed as well since the first minute I got it in my hands..
Sent from my MI 5 using XDA-Developers mobile app
Thanks for the tips Takkaros. I tried what you said but nothing changed (though I was a bit scared to bend it too hard). 1st time it happened to me, I had around 40-50% battery and somehow battery completely drained 24hr later so I got the red blinking low of battery light and was able to charge the phone up and go back into fastboot, which solved everything. this time it happened when I had 96% battery(which I knew cuz I was using the phone, then clicked MI Talk and phone froze, then bricked). I wish there is a way for me to force a battery drain without opening it up. I did opened it up once(on the 1st brick) and disconnected the 3 battery cables, but it was still in brick state when I put everything back.
The qualcomm 9008 driver detection was also my concern about sending back the phone. Chances are by the time my phone reaches the repair shop, battery is completely dead and they simply charge the battery then flash a stable rom and send it back to me without changing out the motherboard or whatever. Which in such case it will be faster for me to just wait a week or two and do myself, instead of shipping it to china and wasting shipping cost and probably will take 4-6 weeks.
I am not sure whats wrong with this phone. Sometimes it turns off while i have in on charge at night, with the Green led lighting. I can get into recovery mode but all the partitions are missing. I cant wipe anything and all my files are not there. If I restart the recovery 2-3 times everything comes back to normal. Maybe there is something wrong with the flash drive. If honorbuy replied to my messages i'd sent it back to them asap. This is not a reliable phone for daily use
Sent from my MI 5 using XDA-Developers mobile app
Try using mi flash. Follow the instruction
Sent from my MI 5 using Tapatalk
I am sending back the phone to china to have them "fix" it. Not sure what they will do, hopefully they either swap me a new phone or swap out the motherboard or something. I just hope they dont just boot into fastboot (after battery completely drained and system resets) and flash new rom and send it back to me.
Probably will take a month or so. Good thing i still have my old phone.
tkrave said:
I am sending back the phone to china to have them "fix" it. Not sure what they will do, hopefully they either swap me a new phone or swap out the motherboard or something. I just hope they dont just boot into fastboot (after battery completely drained and system resets) and flash new rom and send it back to me.
Probably will take a month or so. Good thing i still have my old phone.
Click to expand...
Click to collapse
This happened to me recently. I used mi flash and the global 7.2.4 stable fastboot rom to get it going again. Wouldn't work for me with with with newer versions. Think edl has been disabled on them.
I'm in a big predicament. A few weeks ago I installed the MOAR ROM on my Note 5. After installing this ROM I was no longer able to connect my phone to PC. I tried a Windows 8 PC which says I have an unrecognized USB device plugged in. I tried going into Developer settings to set USB mode to MTP but the option didn't exist. I had all USB drivers installed as well. My wife's phone is recognized no problem. When plugging the phone into my linux machine absolutely nothing happened. It used to show the phone in the left navigation panel in my window manager but after installing MOAR ROM it was no longer detected.
Anyway, today I was trying to play Cartoon Wars 3 and since my phone is rooted it wouldn't let me play. I decided to go into the Super User app and disable it to see if the game would work and it didn't. When I went to re-enable the app it said installation failed and asked me to reboot. I clicked reboot and was sent into a boot loop. I thought okay no big deal, I'll just restore a backup in TWRP. When I go to restore the backup and select the backup file it asks which partitions to restore, but there are no boxes to check. It usually has options like system and data but now it's just blank. I tried a factory reset and I'm still in a bootloop. I'm at a complete loss. I don't know what else to do. I've tried download mode and everything but no matter what I do my phone isn't detected by my pc.
I appreciate any help. I don't know what to do. I'm out of a phone right now and don't have a backup. Not to mention I'm in between jobs right now and can't afford a new one right now.
Just flash a stock rom from sammobile.com
Pre req:
*Odin(any vers)
*Stock rom
Steps
*Extract the downloaded stock rom in your PC
*In twrp wipe everything except internal, then boot in to download mode.
*Once in download mode, connect your phone to your pc, then open Odin.
*In Odin, check the "AP" section and locate the downloaded stock rom(the extracted one)
*Hit start.
Hpe that helps
herculesPh said:
Just flash a stock rom from sammobile.com
Pre req:
*Odin(any vers)
*Stock rom
Steps
*Extract the downloaded stock rom in your PC
*In twrp wipe everything except internal, then boot in to download mode.
*Once in download mode, connect your phone to your pc, then open Odin.
*In Odin, check the "AP" section and locate the downloaded stock rom(the extracted one)
*Hit start.
Hpe that helps
Click to expand...
Click to collapse
Thank you for your reply but it seems you didn't read my post. My phone is not recognized by any pc.
What is the terminal command to restore a backup? That's pretty much my last ditch effort.
Well I broke my recovery so I'm screwed. I contacted Samsung and they said they would service it for free. Wish me luck.
What would cause the phone to stop being recognized by the PC? I narrowed it down to the MTP software or the micro usb charge port. My Windows computer says Device Descriptor Request Failed. Linux box does nothing. No USB devices are listed when I run lsblk.
weinerwad3000 said:
I'm in a big predicament. A few weeks ago I installed the MOAR ROM on my Note 5. After installing this ROM I was no longer able to connect my phone to PC. I tried a Windows 8 PC which says I have an unrecognized USB device plugged in. I tried going into Developer settings to set USB mode to MTP but the option didn't exist. I had all USB drivers installed as well. My wife's phone is recognized no problem. When plugging the phone into my linux machine absolutely nothing happened. It used to show the phone in the left navigation panel in my window manager but after installing MOAR ROM it was no longer detected.
Anyway, today I was trying to play Cartoon Wars 3 and since my phone is rooted it wouldn't let me play. I decided to go into the Super User app and disable it to see if the game would work and it didn't. When I went to re-enable the app it said installation failed and asked me to reboot. I clicked reboot and was sent into a boot loop. I thought okay no big deal, I'll just restore a backup in TWRP. When I go to restore the backup and select the backup file it asks which partitions to restore, but there are no boxes to check. It usually has options like system and data but now it's just blank. I tried a factory reset and I'm still in a bootloop. I'm at a complete loss. I don't know what else to do. I've tried download mode and everything but no matter what I do my phone isn't detected by my pc.
I appreciate any help. I don't know what to do. I'm out of a phone right now and don't have a backup. Not to mention I'm in between jobs right now and can't afford a new one right now.
Click to expand...
Click to collapse
you can try this code and test if it work
*#0808#
Familiaaa said:
you can try this code and test if it work
*#0808#
Click to expand...
Click to collapse
The phone does not boot. Recovery does not boot. The only thing the phone does is go into download mode. The phone does not connect to any computer so I cannot use odin.
weinerwad3000 said:
The phone does not boot. Recovery does not boot. The only thing the phone does is go into download mode. The phone does not connect to any computer so I cannot use odin.
Click to expand...
Click to collapse
when your phone is in download mode,it doesn't work to connect it with samsung kies on your pc?
You could try using the Kies software to reload the stock firmware. Here's an overview of what to do:
- if you don't already have the Kies software installed on your PC, download it (just search Google) and install it. The first time it runs it'll update itself to the latest version so make sure you run it once before proceeding.
- put your phone in Download mode: with the phone completely off, press and hold the Volume Down and Home and Power buttons simultaneously, and release them all when you see the Samsung splash screen
- connect the phone to your PC with the USB cable that came with the phone
-- if you've never had the phone connected to your Windows-based computer before, you'll see messages about installing drivers, etc - just wait until this is done (may take 5 or 10 minutes) [I don't know what happens if you have a Mac - it probably just works]
- in the Kies software, select the second item in the Tools menu and just follow the prompts to enter the model number (in CAPS) and IMEI/Serial Number (both found under the battery - it's ok to remove the battery at this point)
- the Kies software should start downloading the correct firmware for your phone from the Internet; once that's done (depending on your Internet connection speed) it'll begin downloading that to the phone (this probably takes 10 minutes or so)
jubei79 said:
when your phone is in download mode,it doesn't work to connect it with samsung kies on your pc?
You could try using the Kies software to reload the stock firmware. Here's an overview of what to do:
- if you don't already have the Kies software installed on your PC, download it (just search Google) and install it. The first time it runs it'll update itself to the latest version so make sure you run it once before proceeding.
- put your phone in Download mode: with the phone completely off, press and hold the Volume Down and Home and Power buttons simultaneously, and release them all when you see the Samsung splash screen
- connect the phone to your PC with the USB cable that came with the phone
-- if you've never had the phone connected to your Windows-based computer before, you'll see messages about installing drivers, etc - just wait until this is done (may take 5 or 10 minutes) [I don't know what happens if you have a Mac - it probably just works]
- in the Kies software, select the second item in the Tools menu and just follow the prompts to enter the model number (in CAPS) and IMEI/Serial Number (both found under the battery - it's ok to remove the battery at this point)
- the Kies software should start downloading the correct firmware for your phone from the Internet; once that's done (depending on your Internet connection speed) it'll begin downloading that to the phone (this probably takes 10 minutes or so)
Click to expand...
Click to collapse
Kies doesn't work either. I already tried that. When I hook up the phone It says "Device Descriptor Request Failed". It used to connect to my computers until I put MOAR ROM on the phone. Since then it stopped being recognized by my computers. There's either something wrong with the connection or something got corrupted.
weinerwad3000 said:
Kies doesn't work either. I already tried that. When I hook up the phone It says "Device Descriptor Request Failed". It used to connect to my computers until I put MOAR ROM on the phone. Since then it stopped being recognized by my computers. There's either something wrong with the connection or something got corrupted.
Click to expand...
Click to collapse
What have you already tried?
- are you sure you're using a data cable and not a charging-only cable?
- have you tried a different computer?
- have you installed the Kies software?
- what does Device Manager show when the phone is connected?
- assuming that the phone is working normally, does the phone show anything when you connect it?
- do you have try windows 8 or 10?
can be you found a solution in this forum
http://forums.androidcentral.com/sa...-not-being-recognised-download-mode-odin.html
jubei79 said:
What have you already tried?
- are you sure you're using a data cable and not a charging-only cable?
- have you tried a different computer?
- have you installed the Kies software?
- what does Device Manager show when the phone is connected?
- assuming that the phone is working normally, does the phone show anything when you connect it?
- do you have try windows 8 or 10?
can be you found a solution in this forum
http://forums.androidcentral.com/sa...-not-being-recognised-download-mode-odin.html
Click to expand...
Click to collapse
I've tried 4 different cables. My wife's S5 works perfectly fine on all computers. I have tried in Windows 7, 8, 8.1, and 10. I've also tried in Linux Mint. It used to work until I installed MOAR Rom. Windows says Device Descriptor Request Failed. Linux doesn't do anything when hooked up. lsblk doesn't show the device either.
I have a bit of an update. Apparently something happened with all my data cables. I hooked up my wife's phone the other day and I was all of a sudden receiving the same error as the note 5. I went out and bought a new data cable and now her phone connects again. I'm waiting for the Note 5 to charge up so I can try Odin. I'll post back my results.
I apologize to those who told me it was the cable. I just didn't see that it was conceivable that all 4 of my data cables were all of a sudden damaged. Never underestimate the ability of children to destroy every working cable you own.
Well I'm still getting the error. I have some usb cables coming in the mail so once i try those out I'll get back to everyone.
weinerwad3000 said:
Well I'm still getting the error. I have some usb cables coming in the mail so once i try those out I'll get back to everyone.
Click to expand...
Click to collapse
Were you able to fix your issue. I have the same issue. Note 5 N9208, I can get into Recovery (TWRP) and Download mode, but can not boot. The USB connection is showing USB Device Descriptor failed. I have tried 5 different cables and Windows 7/10 Ubuntu and cant get the phone to show up on the PC. I also have changed the USB port of the phone. Any insight would be helpful.
musab_bari said:
Were you able to fix your issue. I have the same issue. Note 5 N9208, I can get into Recovery (TWRP) and Download mode, but can not boot. The USB connection is showing USB Device Descriptor failed. I have tried 5 different cables and Windows 7/10 Ubuntu and cant get the phone to show up on the PC. I also have changed the USB port of the phone. Any insight would be helpful.
Click to expand...
Click to collapse
I ended up trying to replace the port and accidentally cut the ribbon for the LCD screen. Ended up getting a new phone.
Hello!
I am a happy owner of a OP3T 128GB version, but I've currently ran into an interesting issue . I am familiar with rooting android, fastboot, adb and stuff and I have limited experience (a begginer, but a quick learner ) with some other android phones. I hope I'm not creating a duplicit question - I am really sorry if I am, but I haven't found a solution to my problem even after hours spend behind the desk.
Long story short - accidentaly did an Advanced wiped in TWRP (3.1.1-0) and wiped my system (OS) and everything in the phone. I don't really care about the data, but checking the Sysem box in Advanced wipe menu has brought me into serious trouble it seems. Of course, I got a bootloop - my bad, right , nothing I can't fix I thought... But when I approached to try to flash a zip or .img of a system file/stock ROM respectively, I found literally no way to do so. My phone isn't recognized by my PC(s) (Windows and Mac) and I tried everything I could. The device isn't even a Qualcomm or sth. in the device manager - simply nothing, I can only get the device to charge sometimes when connected to the PC (seen in TWRP). I cannot connect an USB key to it via OTG either in TWRP to flash from there - TWRP just does not seem to know I even plugged a USB into the phone. I tried OP drivers, adb naked drivers, the phone and the PC just don't seem to be communicating at all.
The device can boot into fastboot, recovery (TWRP) and if proceeded TWRP prompts with "No OS installed" and I get a bootloop as expected. Is there any way I could try to flash the device with proper firmware? I do have the firmware and everything, I just can't seem to find a way how to flash it . I am a young student who just likes to play with tech stuff and devices and messed up and cannot help myself and I am really hopeless at this point . Any advice is greatly appriciated.
Thank you so much.
Matus
If you can flash/boot into TWRP, then probably nothing is lost. While in TWRP, if you connect your phone with PC, what happens? Do you hear the usual USB connection sound? If yes, what appears in the device manager?
Even if it doesn't appear in device manager, don't worry.
Boot into TWRP, go to storage, DISABLE MTP and enable it again. I know it sounds dumb, but just try it. It will be recognized as long as you have the proper drivers installed.
After that copy the zip of an OxygenOS based ROM like FreedomOS and flash it. Don't wipe anything. It will boot fine. I've done that a few times, never had a problem.
Thanks for the advice guys - no, no sound, nothing - as I said, I only get the charging (+) icon in twpr next to the battery percentage.
I did disable and enable MTP before - although not plugged in a pc during the process - will try if I have the chance.
One more thing that might ring a bell for someone - I tried the key combo for hard reset today(power + vol down) for a couple second and moments later I got a fuzzy (random colored pixels) screen and a red led. Weird, if you ask me.
P.S.: Today I tried to chat with OP a bit - 230 Eur for a new MB (64GB) and 255 Eur for my 128GB version - I just wanted to know, I'm still not admitting failure though. But as a student, these numbers from the support literally hurt me when reading...
grello said:
Hello!
I am a happy owner of a OP3T 128GB version, but I've currently ran into an interesting issue . I am familiar with rooting android, fastboot, adb and stuff and I have limited experience (a begginer, but a quick learner ) with some other android phones. I hope I'm not creating a duplicit question - I am really sorry if I am, but I haven't found a solution to my problem even after hours spend behind the desk.
Long story short - accidentaly did an Advanced wiped in TWRP (3.1.1-0) and wiped my system (OS) and everything in the phone. I don't really care about the data, but checking the Sysem box in Advanced wipe menu has brought me into serious trouble it seems. Of course, I got a bootloop - my bad, right , nothing I can't fix I thought... But when I approached to try to flash a zip or .img of a system file/stock ROM respectively, I found literally no way to do so. My phone isn't recognized by my PC(s) (Windows and Mac) and I tried everything I could. The device isn't even a Qualcomm or sth. in the device manager - simply nothing, I can only get the device to charge sometimes when connected to the PC (seen in TWRP). I cannot connect an USB key to it via OTG either in TWRP to flash from there - TWRP just does not seem to know I even plugged a USB into the phone. I tried OP drivers, adb naked drivers, the phone and the PC just don't seem to be communicating at all.
The device can boot into fastboot, recovery (TWRP) and if proceeded TWRP prompts with "No OS installed" and I get a bootloop as expected. Is there any way I could try to flash the device with proper firmware? I do have the firmware and everything, I just can't seem to find a way how to flash it . I am a young student who just likes to play with tech stuff and devices and messed up and cannot help myself and I am really hopeless at this point . Any advice is greatly appriciated.
Thank you so much.
Matus
Click to expand...
Click to collapse
1) try to update the twrp to the official 3.1.1.0. Then flash the latest modem firmware for your device and try to flash a custom rom like lineage os (a 7.x rom)
If you connect the phone to PC in TWRP and your phone is not recognized, chances are good that either your phone's USB or the cable (or the USB port on the computer) is not working. You can try to download the adb driver installer from here, just to check if your phone is listed by the installer: http://adbdriver.com/downloads/
Update - tried the MTP Enable/disable option in TWRP (in the Mount menu) while plugged into the PC, with no luck
IvanPrince - have you actually read the description of my problem? I have the 3.1.1-0 and even if not, how should I actually flash another version of twrp? The problem here is I cannot seem to find a WAY how to flash ANYTHING on the device.
I'll see about the adb drivers and update.
Thanks all,
Does the phone show up as anything on the PC when you boot to fastboot? I re-read but didn't see anything about it.
Nope - nothing. By now, I believe it is a hardware problem as the phone indeed got wet before my mistake with the advanced wipe. It appears to work just fine though, apart from the connectivity issue, so I believe the MB should be ok as everything else, including the screen is.
I just have one, perhaps a little courageous thing I'd like to ask from someone kind enough. Anyone with a Oneplus 3 or 3T who's not afraid to open the phone for a couplne minutes and has a multimeter alongside with a USB cable should be able to help me. :angel:
Could you, my awesome stranger, check where the 4 USB pins (on the side where you plug them into the PC) lead (make contact/'BEEP' on the multimeter) with the actual phone motherboard? It would REALLY help me in troubleshooting and perhaps saving 250 Eur. So far, I have this: (same color means contact) at that point. See picture.
BLACK - GND (all the heatsinks are connected to GROUND as well)
GREEN - DATA +
YELLOW - DATA -
RED - VCC
If anyone decides to open up their phone and help out a fellow xda guy, it will be greatly appriciated. :angel:
Hey Bro I was curious to know if you tried this method of recovering from a hard brick... When I first got my 3t something similar happened to me. I can't remember all the details of my hard brick but I thought I was f***ed. Please try this if you have not already.
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Might be a dumb question, but you did remember to mount the USB when you connected the otg right?
If the bootloader is unlocked, you can save it.
I would flash the stock recovery and the latest factory image (4.1.7)
Download them both from here:
http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.7/
After flashing the stock recovery using fastboot, boot to stock recovery and sideload through ADB the stock factory image.
Reboot and after checking that everything is working fine, feel free to relock the bootloader if you wish to stay 100% stock.
If the computer doesn't recognize it at all then it's a driver problem, not the phone... at least that's what I think.
try to use the program to fix my oneplus 3t it said download complete. try to restart
try to use the program to fix my oneplus 3t it said download complete. try to restart it and can press the screen and it keep rebooting it like the screen is frozen
please help me out
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 …
Hello everybody,
To explain things a bit better than just this title. I have a Mi 5 that was working smoothly for quite a long time. Had a modified MIUI ROM flashed on it with many specific apps such as xposed, Magisk and also TWRP. However, my GPS has turned completely dead for some months. Couldn't use it anymore. After some researches, I found out it could be software related. So I decided to flash a new ROM (AOSP Extended) to see if that could fix the GPS issue.
First I backed up the whole system via adb on my laptop and then wiped the whole system. It turns out after trying to flash the AOSP ROM, I came across a message saying I should have MIUI 8.1.30 or older. Or something like that... Can't remember exactly. Just read that I was supposed to update my ROM to a newer stock ROM to be able to flash AOSP in a second time. I did a lot of different operations and I can't remember them all but it turns out one moment, adb started to flash a ROM because the adb command line was saying it. But it failed. Aftert that moment, my phone definitely got bricked. I have no clue what exactly happened, it's kind of confused...
Currently, the phone is always displaying dark screen with mi logo and "unlocked" mention below. Power and volume up will just reboot it to the same state (meaning twrp is not longer installed or accessible). In this dark screen mode, plug the phone to a computer will do nothing, it's not even detected in devices manager. On the other side, power and volume down will boot the phone into fastboot mode, the computer beeps when I plug the USB cable and I can briefly see the Android device with a yellow warning in the dev manager. But after something like 20 seconds, fastboot mode goes off and phone restarts on black MIUI screen.
I've tried to install Google drivers, Qualcomm drivers and did numerous actions but the phone isn't detected anymore. Also, tried to type command "adb devices" in the short time when the phone is detected by computer in fastboot but it shows an empty list. I'm pretty desperate, seems I've tried anything and I've no ideas now... Just saw there is possibly a hardware fix which requires to dismount the back of the phone. Not sure what it does but I'll try it out if no other solution shows up...
Any idea is welcome ! Thanks
Well, looks like my thread wasn't so popular Finally found a workaround after nearly 8 hours searching for a fix. Thought that might help anybody else having the same struggle as mine. What I can tell is that it's not related to the computer used since I've made the same operations on 3 different computers, same problem for each of them. In fact, there were two problems :
First the bootloader not remaining more than 30 seconds. To stop this, I had to open the devices manager and as soon as the Android device would appear after turning it into Fastboot, I would right click on the visible device (appearing with an exclamation mark) and update manually the driver following the process that is described in many topics (locate the Google Android devices USB drivers that I downloaded right before). The time is quite short so you have to be pretty fast, otherwise, the MI 5 would disappear, forcing you to do the fastboot mode operation again. I have to say that doing it without the device being recognized is not working. So if you install with the legacy driver option, it's not going to be associated directly to the device. At least, not in my case.
Once I had done this, the Fastboot mode would remain on. I found my way pretty fast until that moment but the problem was adb wouldn't detect my device. Typing "adb devices" command would return no result, no matter what I did. Strangely, installing an old version of MiFlash (last ones gave me error) would help the computer to detect the device. I don't know why, possibly because the drivers are better ? Anyway, MiFlash helped me to access the phone and Flash a new ROM. Usually, I was just using adb and it would do the job but this time not.
Hope it can help !