Related
Hey, Ive tried to install xiaomi.eu rom but didnt realize that i needed the chinese rom and that the global didnt work for this, after ive installed using TWRP the rom, ive rebooted and it just went black, not recovery, not fastboot.
BT was unlocked.
I also see my phone as qualcomm...qloader 9008 when connecting to my pc
Any help?
after having a few heartattacks, ive installed a good Miflsah and a good fastboot rom, and managed to restore my phone to its former glory
no need for further help, but i have a few advices
dont be stupid like me, and listen to directions like theyre the word of god, when they say change from chinese rom to a non official rom, YOU NEED CHINESE, global wont work
and if you're having problems with miflash giving errors, try a bunch of downloads, old, new, everything.
Hi, yet another brick here!
I had an AOSP ROM but I had problems with it. I entered TWRP, downloaded a MIUI official ROM for recovery, wiped the phone from TWRP and decrypting it (there was an option for that). Then I did try to flash the ROM and... black screen. No signs of life.
However, when I connect it to the computer it detects it as the famous Qualcom xxx 9008 (COM10) device. But fastboot is not working, when I type "fastboot devices" it doesn't return anything. ADB doesn't recognize the phone either. Everywhere I saw that I should use MiFlash to recover it, but I took a look at the scripts and are using fastboot to perform the process. But since fastboot doesn't recognize the device, it won't work. I get stuck all the time at "Failed to receive the hello packet".
Fastboot doesn't detect my phone either on Linux or Windows. I tried Linux, virtual Windows 10 (x64) and at last I'm trying on a Windows 10 (x64) computer (no virtualization). No matter what I do, it always stays at the same point. I also used several MiFlash versions (from old builds from last year to the most up-to-date version of XiaomiMiFlash). But since fastboot is not detecting the phone I think there's no point in switching MiFlash versions.
So... what can I do? Should I use the pin short-circuit /deepflash cable method? As of I understand, that is what you use to get into EDL, but if my device is showing 9008 in device manager doesn't it mean that I'm already in EDL? I'm not really sure because all the threads I saw in several forums are a bit messy.
I'll appreciate any help. I don't have phone since 3 days ago and I can survive without it but I need it for my work.
Thank you in advance!
EDIT:
Forgot to say, if I try to power off and power on it doesn't do anything BUT when I plug and unplug from the charger it does show a battery icon with the charged percentage. That's the only sign of life from the phone, aside from being recognized as a 9008 device, but that actually happens when I try to (blindly) get in fastboot mode.
FIXED!!! After four hours testing out several options I found the solution: Open up the phone, unplug the battery cable, plug it again, and voilà. The phone automatically got recognized (again) as Qualcomm 9008 device but this time the flash went on flawlessly. It took less than 5 minutes, once succeeded I powered on the device and it ran into MIUI 8 in less than 5 minutes.
So, if you find issues with the command "fastboot devices", unplug the battery and try it again before troubling yourself with deepcables or shortcircuits ;-D
NOTE: Taking out the back cover is very easy, search on youtube, I bought the thing you need for 1$ at the store next to my home (sorry I don't know what it's called).
So, I tried to update to Pie.
I was on Stock Oreo rooted without encryption.
Wiped everything except sdcard, installed Pie and the boot img for encryption fix.
Rebooted to TWRP, flashed the zip from verity fix, flashed latest Magisk.
Rebooted to system, stuck with the dots rotating.
Tried to redo it again, adding the step for the firmware flash.
But when wiping i accidentally wiped sdcard too, so I have no more the required files inside TWRP.
Tried to connect both TWRP and bootloader via adb/fastboot but phone is not recognized.
All the drivers are installed it always worked before (Win7).
Now everytime I try to connect the 3T to PC it says Unknown Device in Device Manager, but all the drivers are installed.
Apparently the phone is not sending its data, because in device properties i see VID & PID = 0000.
Trying to manually attach a driver to it (with right click, update driver) gives error, no driver available for the device (using any adb drivers .inf).
So basically now I'm stuck with a phone without files in it, but with only TWRP working.
How can I send the rom files without adb/fastboot? Any trick?
I also tried to use USB OTG from TWRP but apparently any usb stick is not recognized.
Tried different USB ports and different cables. Seems like a problem with the phone usbC port, not sure.
It's an hard brick at this point?
Just go with the Qualcomm factory restore mode/tools. Turn off phone, hold volume up while connecting phone to PC, install the drivers for the Qualcomm 9008 device and then run the factory recover tool. You can find out all this in the factory restore thread, just make sure you have the 3t and not the normal 3 as they have different firmwares for the hardware.
Skickat från min ONEPLUS A3003 via Tapatalk
Format the device in latest TWRP and reboot it back to TWRP then connect the USB cable to PC. It should ideally recognize your 3t. I never had any issue while recognizing the phone in TWRP menu.
if nothing helps, the final step is obviously try he Qualcomm factory restore mode/tools.
pitrus- said:
Just go with the Qualcomm factory restore mode/tools. Turn off phone, hold volume up while connecting phone to PC, install the drivers for the Qualcomm 9008 device and then run the factory recover tool. You can find out all this in the factory restore thread, just make sure you have the 3t and not the normal 3 as they have different firmwares for the hardware.
Skickat från min ONEPLUS A3003 via Tapatalk
Click to expand...
Click to collapse
sandeep_kumar said:
Format the device in latest TWRP and reboot it back to TWRP then connect the USB cable to PC. It should ideally recognize your 3t. I never had any issue while recognizing the phone in TWRP menu.
if nothing helps, the final step is obviously try he Qualcomm factory restore mode/tools.
Click to expand...
Click to collapse
I already tried that too. It always appear as unknown device, even with that method.
Just to be clear, I never had problem before and I already used TWRP mount and fastboot/adb to load files without having a running ROM. I was always able to move file with any of them.
This is different, it seems like an hw problem, the phone it's not sending his IDs when connecting to CP so the PC can't identify what it is even if drivers are installed.
Now, I'm not sure if the problem lies in the physical USBC port or if the failed Pie upgrade ruined somethin in the bootloader or something else.
Then I'd say broken USB cable, have you tried with another cable or a shorter cable?
Skickat från min ONEPLUS A3003 via Tapatalk
pitrus- said:
Then I'd say broken USB cable, have you tried with another cable or a shorter cable?
Skickat från min ONEPLUS A3003 via Tapatalk
Click to expand...
Click to collapse
Tried many cables, ports and PCs.
I also tried to clean the port with a wooden stick without luck.
At this point i believe it's the usbC port or the motherboard.
I think something at the USB MTP level went faulty, because charge works fine (dash charge too).
I just can't transfer files anymore. Not even with an OTG dongle.
Since there is no other way to trasnfer the ROM zip (network is not available inside TWRP) I requested an RMA and tomorrow OnePlus send a carrier to pick it up for repair.
I have not still updated the device. I am on custom ROM. After reading your problem I am scared to install it on my device.
I think it is better to go to stock completely with locked bootloader with 5.0.8 and then accept update. After that, I can unlock the bootloader and root the device.
i just recently had this problem dude, not even 20 mins ago, find and use a diffrent usb cable/port or if u have a usb hub use that along with ur new cable, it finally worked after hours of countless tries
sandeep_kumar said:
I have not still updated the device. I am on custom ROM. After reading your problem I am scared to install it on my device.
I think it is better to go to stock completely with locked bootloader with 5.0.8 and then accept update. After that, I can unlock the bootloader and root the device.
Click to expand...
Click to collapse
Don't worry, if the USB port is working you can always recover. Just be sure your PC recognize the device first, in case anything happens.
cmurder61 said:
i just recently had this problem dude, not even 20 mins ago, find and use a diffrent usb cable/port or if u have a usb hub use that along with ur new cable, it finally worked after hours of countless tries
Click to expand...
Click to collapse
I've been trying for the whole day with 5 different cables, 4 different PC and every usb port of them. I just didn't try with an hub because i don't have one, but i don't think it makes any difference. Anyway the phone i ready to be send for repair now.
if that's ur lat hope, go for it, but the specific cable i used was a belkin usb cable from walmart, u should also update ur adb drivers, if i could id let u use my pc lol
cmurder61 said:
if that's ur lat hope, go for it, but the specific cable i used was a belkin usb cable from walmart, u should also update ur adb drivers, if i could id let u use my pc lol
Click to expand...
Click to collapse
Nah its not the cable or drivers, I test roms every 1/2 months and always been fine with uploading files with adb, fastboot or MTP. Nothing changed. Must be some hardware issue.
Oneplus already sent me the shipment code and i'm waiting for UPS to pick up the package today.
matrixino said:
Nah its not the cable or drivers, I test roms every 1/2 months and always been fine with uploading files with adb, fastboot or MTP. Nothing changed. Must be some hardware issue.
Oneplus already sent me the shipment code and i'm waiting for UPS to pick up the package today.
Click to expand...
Click to collapse
i see, well good luck to ya
So something I noticed, I've updated my phone loads of times via firmware Finder and the update tool on my PC with no issues. So I haven't needed to update my phone for a couple of months so I had no reason to connect my phone to my pc. Yesterday I went to do the usual update procedure and plug my phone in and realised my computer doesn't recognise my phone whatsoever. My phone is unlocked and currently rooted as a side note. So I checked to see if I had fastboot and when trying to boot into it, it just reboots the phone. Does anyone have any idea what to do?
CaseyS said:
So something I noticed, I've updated my phone loads of times via firmware Finder and the update tool on my PC with no issues. So I haven't needed to update my phone for a couple of months so I had no reason to connect my phone to my pc. Yesterday I went to do the usual update procedure and plug my phone in and realised my computer doesn't recognise my phone whatsoever. My phone is unlocked and currently rooted as a side note. So I checked to see if I had fastboot and when trying to boot into it, it just reboots the phone. Does anyone have any idea what to do?
Click to expand...
Click to collapse
https://forum.xda-developers.com/hu...432e5r1p9b195-9-0-0-195-t3888894/post79832003 this way should work unless something has changed on your PC? E.g. drivers uninstalled?
Solved the issue. My cable must have been damaged at some point and would only let me charge the phone. Used a different cable and everything worked as usual. Thanks for the suggestion though
Hello Everyone, so 2 days ago i hard bricked my MI 8 with flashing an eu rom over global mi 8 rom with twrp then when i rebooted the phone it stuck at mi logo so i tried to goto recovery mode again but nothing happens when i press power + volume up its just mi logo and i tried to go to fastboot mode but not luck i get a black screen....................so i decided to connect it to a computer but no signs of anything(not detected).....so i searched google a little and i found a solution wich envolved disassembling the phone the method called EDL method with test point,,,,,,,so i opened my phone with my friends and tried to do the test points,,,when i joined the testpoints and then connecting the phone to pc.....nothing happened.....it should detect the phone but nothing happens.....please help guys!!!
Keep trying with edl, maybe it's a driver issue, but if you can't get it to edl I don't think you can recover your phone ?
mi_guel said:
Keep trying with edl, maybe it's a driver issue, but if you can't get it to edl I don't think you can recover your phone
Click to expand...
Click to collapse
I have been trying....but no luck till now:crying::crying::crying:
alandxaled said:
I have been trying....but no luck till now:crying::crying::crying:
Click to expand...
Click to collapse
You need to use QPST.
Also you didn't need to open the phone, that step is outdated.
Go ahead and read up on installing all of the needed drivers and as long as your phone is linked to you. That is you have the phone registered to your MiCloud account this issue should be fixable.
I dont have a lot of time today or tomorrow. but I am willing to try and help you figure this issue out.
tsongming said:
You need to use QPST.
Also you didn't need to open the phone, that step is outdated.
Go ahead and read up on installing all of the needed drivers and as long as your phone is linked to you. That is you have the phone registered to your MiCloud account this issue should be fixable.
I dont have a lot of time today or tomorrow. but I am willing to try and help you figure this issue out.
Click to expand...
Click to collapse
I installed the drivers...but the main problem is that when i connect it to the pc ....the pc did not recognize the phone not even in device manager
alandxaled said:
I installed the drivers...but the main problem is that when i connect it to the pc ....the pc did not recognize the phone not even in device manager
Click to expand...
Click to collapse
This could be an issue with the PC...happens all the time.
If the battery is not completely dead, or if the usb port is not completely fried you should be able to at least see the port.
It's also possible that you are not in EDL.
Simply Flashing the EU rom over Global will not brick your phone, I have done that myself many times. Was your bootloader unlocked? If not then you will probably need to take it to a Xiaomi Service center.
Does the phone mac any vibrations when pressing and holding both the volume up and down ( at same time along with the power button?
Have you tried alternate usb c cables?
If you have a newer computer with usb 3.0 ports you will need to use a Usb hub., which will downgrade the connection to usb 2?
Is ADB Installed on this computer along with generic android drivers?
is the computer up to date?
Have you tried an alternate user and are you using the admin account?
If you have a device that uses linux, see if Linux will see the phone.
If you have tried everything, and you still you see the phone, and the phone has not been exposed to an extreme amount of force or to water. It may be that your usb card in the phone is fried or there is a short in the internal usb flex cable. ( It's the wire that connects the usb card to the motherboard.
You can Google the steps to make your own deep flash cable, that would help rule things out much faster.
I am going to sleep now. Good Luck.
@tsongming Do you know why he bricked his phone? I mean he just flashed .eu.
tsongming said:
This could be an issue with the PC...happens all the time.
If the battery is not completely dead, or if the usb port is not completely fried you should be able to at least see the port.
It's also possible that you are not in EDL.
Simply Flashing the EU rom over Global will not brick your phone, I have done that myself many times. Was your bootloader unlocked? If not then you will probably need to take it to a Xiaomi Service center.
Does the phone mac any vibrations when pressing and holding both the volume up and down ( at same time along with the power button?
Have you tried alternate usb c cables?
If you have a newer computer with usb 3.0 ports you will need to use a Usb hub., which will downgrade the connection to usb 2?
Is ADB Installed on this computer along with generic android drivers?
is the computer up to date?
Have you tried an alternate user and are you using the admin account?
If you have a device that uses linux, see if Linux will see the phone.
If you have tried everything, and you still you see the phone, and the phone has not been exposed to an extreme amount of force or to water. It may be that your usb card in the phone is fried or there is a short in the internal usb flex cable. ( It's the wire that connects the usb card to the motherboard.
You can Google the steps to make your own deep flash cable, that would help rule things out much faster.
I am going to sleep now. Good Luck.
Click to expand...
Click to collapse
1-My Bootloader was unlocked yes!
2-i flashed eu rom over evolution rom(Custom rom)
3-Yes It Does Vibrate
4-Yes I Have Tried Other Usb Cables
5-yes, adb installed with generic usb driver
6-yes its updated and i tried mutliple ports
7-i haven't tried linux
8-and i dont think that my usb card is fried because before that it was working
And Another Thing That Might Have A connection with the problem"Before i flashed eu rom over custom rom the unlocked text was shown in the display when booting with mi logo but now that text has gone"
alandxaled said:
1-My Bootloader was unlocked yes!
2-i flashed eu rom over evolution rom(Custom rom)
3-Yes It Does Vibrate
4-Yes I Have Tried Other Usb Cables
5-yes, adb installed with generic usb driver
6-yes its updated and i tried mutliple ports
7-i haven't tried linux
8-and i dont think that my usb card is fried because before that it was working
And Another Thing That Might Have A connection with the problem"Before i flashed eu rom over custom rom the unlocked text was shown in the display when booting with mi logo but now that text has gone"
Click to expand...
Click to collapse
The EU rom does not lock the bootloader, the developers actually removed the bit of code that will allow MiFlash to lock the bootloader. Whenever leaving or returning to Miui, storage must be formatted.
The problem with these custom roms for the Mi8 is that These mi8 developers do not work together ( like most do, on other threads) These developers are always fighting and arguing and accusing each other of stealing their code, while they do it themselves and they all have their own way of doing things. Ideally every rom should use the same device tree, firmware and vendor...The basics! But no, everyone does things differently.
I would suspect that your phone bricked due to firmware encryption or just corruption. Even though it seems that it can't be fixed, you will surely be able to fix it eventually.
Many people were eventually able to solve this exact issue in the past with success. so start with the basics., and dont give up when or if it fails, just try again on a different device, and be sure to disable Windows defender. Because it's possible you could have your computer setup in a way that it will make this process harder to resolve, temporarily disable the antivirus and firewall etc.
Download the All in One tool: https://forum.xda-developers.com/mi-8/development/tool-tool-one-driverstwrpfactory-t3895807 If it gets flagged, and completely disabled. then your computer is helping contribute to this issue.
If you can successfully install and open the tool, use it to update adb and android drivers and to apply system wide adb access. Next manually setup the phone , even if it claims to not see a fastboot device. and attempted to remove encryption. if this fails find a Linux machine to complete these tasks.
See if you can leave EDL, by pressing and holding the power and volume down. >>>>> Even if you dont see the fastboot screen the computer may see the phone in fastboot.
I definitely believe that you will have a easier path to getting this issue resolved sooner by using linux. If you can "format" ( not wipe) user data, install TWRP and root the rest will obviously be easy.
---------- Post added at 06:23 PM ---------- Previous post was at 06:22 PM ----------
Boiisxu said:
@tsongming Do you know why he bricked his phone? I mean he just flashed .eu.
Click to expand...
Click to collapse
He didn't format user data, or the file was somehow corrupted
And I do think it's unlocked, because I re-flashed TWRP and it still works, Magisk flashed without issues too, so I'm not sure what suddenly caused MIUI to say it's locked
Another thing worth mentioning is that my phone is no longer recognised by adb, even though I went through the steps I had previously to make it work (doing things in fastboot still works, but no matter what I try the phone won't be recognised as a device using adb)
Edit: For some reason it's recognised as a device again even though all I did was restarting it into recovery and fastboot a few times, which I've done before already
Just Xiaomi things
I once softbricked my device and it didn't even show up in the device manager. I thought I was fu*ked, but after restarting the phone a couple of times and plugging to a different USB port my PC suddenly started recognizing my phone again.
Yet another issue, the previous update was from MIUI 12.0.5 to 12.0.6, so nothing much, but now when I updated to 12.5, the phone isn't even detected when connecting to the pc normally, tried with debugging on and off and with fastboot, just doesn't seem to be recognised as a device
I swear to god MIUI has a mind of it's own and just wants to troll me, I post here and it magically works again