Problem with PC connection... Can't see internal memory of the Smartphone. - Xiaomi Mi Mix 3 5g Questions & Answers

Hi,
I have unlocked Xiaomi Mix 3 5g. Phone never been rooted and I've never tried to apply custom ROM. SInce I've got it I'm on original software: at the moment MIUI Global 12.0.3. I've only had TWRP recovery applied but this wiped out ant went back to original recovery after my phone updated itself last time to 12.0.3.
Basically I've had phone ready to apply custom ROM but never done it accualy. I was always on original MIUI and TWRP recovery was applied to my phone.
A the moment after I connect phone to PC using cable, smartphone discovers PC connection but on PC I cannot see internal memory of my phone. And yes I have all needed drivers installed and I've tried using 3 different cables...
I think that may happened after my phone updated itself last time and went back to original recovery...
The worst problem is that now I cannot flash back to TWRP. When phone is connected to PC and I go to CMD, typing ''adb boot fastboot'' command is working and phone reboots itself to FASTBOOT MODE but once I'm in fastboot mode commands are not working and on flash attempt I only see < waiting for any device >
Any solution for this ?

Try using usb 2.0 ports or different computers.
I sometimes get mine to flash by inputting the command first then plugging the phone in afterwards.

Related

[Q] G2 Soft bricked no ROM on Internal Memory

SOLVED!
Hello All.. I have searching for hours not making much progress. Last night my LG G2 ran out of battery and I plugged it into the car charger and it soft bricked. I've been pretty busy lately so I'm on an old ROM Optimus DE 2.2. I don't have the ROM saved and I've been trying to ADB sideload the ROM back onto my phone but in the command prompt it says device not found. I tried installing some generic drivers and that didn't work. I tried the LGUnitedMobileDriver and that isn't working either.
I'm not sure what to do next. I have ADB on my computer and ADB sideload on my TWRP recovery, so I would like to push the ROM on my phone so I can flash it without having to wipe my phone. What drivers do I need; right now my phone shows up under other devices in device manager. Or am I sideloading wrong? Any help please lol..
I was caught off guard because of the random soft brick. If I would have been working on my phone I would have had the proper backups made. Thanks for any help, it is much needed I need my phone back ASAP!! Thanks again.
SOLVED
Finally figured it out. I had to updated my device (LG G2) with the ADB drivers not the LG drivers.
I went into Device Manager, right clicked my phone, clicked update driver software, clicked browse my computer, clicked let me pick from a list of drivers, then selected ADB drivers, then selected HTC Dream Composite ADB Interface. I believe the drivers I last installed were Snoop05's adb-setup-1.4.2.
Then I did a backup in TWRP, then I sideloaded the ROM. Next I had to wipe everything but internal memory and the use Nandroid Manager to restore my data from the backup... Took my whole day but at least I have a phone again.
The car charger soft bricked it ?
So you have TWRP, the drivers you can get from the LG site too. Just search for your model and go to software update section. This is for D802, i dont know if the drivers are the same: http://www.lg.com/uk/support-mobile/lg-D802
Hmm..i dont know how to use the sideload..
Another way can be with USB flash drive and OTG cable, i used my usb flash drive with OTG cable to flash ROMs from TWRP
Last option is lg flash tool and then reroot
Thanks for your help guys.. I appreciate it! Looks like I just needed to update my phone with the ADB drivers in Windows 8 Device Manager. I'm back up and running.
But yea so weird.. I haven't flashed anything on this phone in months so I guess something was corrupted when it died. I think it was trying to boot with too low of a charge and the battery died mid boot which corrupted something.
Although you've solved it let me recommend you another way.
Use : "adb push romname.zip /sdcard/romname.zip"
instead of "adb sideload romname.zip"

[Q] No Recovery, No Download Mode, Not Recognized in Fastboot mode by PC

Hello there!
So I accidentally bricked my phone a few days ago and now it is resting as a brick on my desk, but how did all of this happen, you may ask?
Well, the story is rather simple, I had the Simple ROM V. 1.4 installed on my G2 and decided to update it to version 2.0, which is posted here somewhere, but what I didn't notice was that the file I was downloading (even though it said it was compatible with all versions) was not for the D800 but for the LS980 and this bricked the phone.
First I was stuck on fastboot mode and was able to get my download mode back, but it kept saying that it couldn't flash the stock rom because it was the wrong model.
Looking online and through these forums, I found out that it was because the download mode that it had was not the right one to use, and that I needed to "destroy" download mode, enter once again in fastboot mode and flash the new download mode, this, however, turned out out to be impossible as the fastboot mode is no longer being detected by Windows nor Linux.
I installed back the USB drivers, installed Android ADB, changed the UDEV rules with mew vendors ID from the list provided by Google, updated the drivers on my PC and even tried to change the directory in which the phone would appear.
The problem resumes to this:
When in fastboot mode (connected to the PC) and type
Code:
fastboot devices
in both Windows and Linux, I get the response as
Code:
???????? devices
.
When I try with
Code:
adb devices
I get back nothing.
Curious thing is that the phone does appear on Device Manager as an Android ADB device and when on Linux I use the
Code:
lsusb
I get back that it is being recognized as
Code:
Google Inc. 18d1 d00d
, which I believe is the phone.
When trying to run any fastboot commands, the phone stays on "waiting for device" on Linux or "flashing" on Windows and later a messages pops back at me with
Code:
Error too many links
.
With all this in mind, I would like to ask you guys, is there something that I am missing?
Any help will be truly appreciated!
PS. Forgot to mention that I have tried with other computers and have the same result and the model of my phone is the D800.
Just to add a bit more into the case.
I had installed prior to all this mess, TWRP which had a Nandroid backup in the internal storage and file backup.
When using the LG Flash tool (KDZ one) I am able to see the available storage, which is about 2.5gb. This leads me to believe that both the Nandroid backup and Backup files are still in the internal storage.
Also, I did some more digging and got information that it might be the USB cable, however, this cable worked fine the first time and with other devices. and while connecting the phone with it to the PC it will still register the device as connected, but apparently no USB port is assigned or fastboot flash tool does not find the phone.

Please help! I seem to have bricked my G2

So yesterday I installed TWRP alongside CM13.
After that I got some problems with the ROM (rebooting, slow charging) so I decided to return to stock. To flash the stock .kdz I needed to go into download mode, that however did not work my phone just booted normally into CM when I tried to use the method to get into download mode (vol+ & USB). I even tried to force download mode through adb on PC however that also only rebooted the phone.
Then I did a wipe in TWRP (everything except Internal Storage) and shut off the phone.
Now I have the problem that I can not boot (because I obviously have no ROM installed anymore) but I also can't get into recovery anymore.
Also my phone seems to be in "only charge" mode from CM so my PC does not even recognize it correctly. I can't even see it in device manager and neither adb, nor the flash tool nor anything recognizes it.
When I connect my phone to the PC it just shows the CM battery icon that you see when you charge your phone while it's turned off and the LED is glowing yellow.
All of this are things that were new with CM so I guess there is still something left from CM that does prevent my G2 from acting as MTP.
Please tell me there is still hope...

Bricked Oneplus 2 (SOLVED)

**UPDATE I have unbricked my phone and the whole time I thought it was a software issue on my phone but it was a cable, I guess my cable got broken when I bricked my phone and I thought it was a software issue but it was not the whole time**
I have a bricked device and I would appreciate your help and I have tried EVERYTHING!!
here is how my oneplus 2 got bricked, I was on stock oxygen os 3.0 and rooted and I had twrp recovery 3.0.
So I did a full wipe on my device and when I was flashing the resurrection remix rom in twrp it said "Error 7" so then I reboot my phone and I was in a bootloop with no os.
I went back to twrp and flash the rom again and it not work. So then I tryed to transfer a file through my computer to my device and twrp was not recognizing it and tryed adb sideload and same thing and even in cmd I
typed "adb devices" and it not recognize it and I have the drivers installed, the 15 second 1click adb and fastboot.
And then I went to fastboot mode and then I tried first aid kit and the qualcomm mega unbrick guide and all the methods and still my oneplus 2 is not being recognized by PC and I am using the official oneplus 2 usb type c cable.
I have tried 2 windows 10 PC and I turned driver signniture enforcement off for the qualcomm drivers and nothing in device manager
I tried 1 Windows 7 PC and same thing and nothing in device manager
And I tried a Linux Mint virtual machine and I typed adb devices and fastboot device in the terminal and it was not recognizing it even though I installed the packages
So do you think the problem might be the cable? because it is the official one. But my device charges through the cable to and the cable was working before my phone got bricked. Or is it a driver problem? What do you guys think and please help and I will really appreciate it and thank you.
fahad999 said:
I have a bricked device and I would appreciate your help
here is how my oneplus 2 got bricked, I was on stock oxygen os 3.0 and rooted and I had twrp recovery 3.0.
So I did a full wipe on my device and when I was flashing the resurrection remix rom in twrp it said "Error 7" so then I reboot my phone and I was in a bootloop with no os.
I went back to twrp and flash the rom again and it not work. So then I tryed to transfer a file through my computer to my device and twrp was not recognizing it and tryed adb sideload and same thing and even in cmd I
typed "adb devices" and it not recognize it and I have the drivers installed, the 15 second 1click adb and fastboot.
And then I went to fastboot mode and then I tried first aid kit and the qualcomm mega unbrick guide and all the methods and still my oneplus 2 is not being recognized by PC and I am using the official oneplus 2 usb type c cable.
I have tried 2 windows 10 PC and I turned driver signniture enforcement off for the qualcomm drivers and nothing in device manager
I tried 1 Windows 7 PC and same thing and nothing in device manager
And I tried a Linux Mint virtual machine and I typed adb devices and fastboot device in the terminal and it was not recognizing it even though I installed the packages
So do you think the problem might be the cable? because it is the official one. But my device charges through the cable to and the cable was working before my phone got bricked. Or is it a driver problem? What do you guys think and please help and I will really appreciate it and thank you.
Click to expand...
Click to collapse
If your recovery mode is TWRP.. Then goto Mount -> Data
Then your computer will show your oneplus 2.
If still its not showing then update Driver Software of phone in device manager.
eldos777 said:
If your recovery mode is TWRP.. Then goto Mount -> Data
Then your computer will show your oneplus 2.
If still its not showing then update Driver Software of phone in device manager.
Click to expand...
Click to collapse
I tried both mount data on and off and still no luck, I have mtp enabled in twrp. I also checked device manager and there is nothing showing up. But twrp says that my phone is charging when my phone is connected to pc. I think the problem is probably the cable because the usb end of the cable looks sort of damaged, And I tried a Type-C OTG and put a usb on that and TWRP was not recognizing it
eldos777 said:
If your recovery mode is TWRP.. Then goto Mount -> Data
Then your computer will show your oneplus 2.
If still its not showing then update Driver Software of phone in device manager.
Click to expand...
Click to collapse
Holy crap the cable was the problem the whole time!!! I just went to the store and bought A new 3rd party USB-C cable and I plug it in to my pc and phone and immediately the pc installed drivers and now I could transfer files to TWRP from my PC!! It was a really hot sunny day today and I walked to the store which took 30 minutes and both ways 1 hour. I am so tired right now from the walk but it was worth it since my phone will be brought to life!! I am so happy right now!!!
fahad999 said:
Holy crap the cable was the problem the whole time!!! I just went to the store and bought A new 3rd party USB-C cable and I plug it in to my pc and phone and immediately the pc installed drivers and now I could transfer files to TWRP from my PC!! It was a really hot sunny day today and I walked to the store which took 30 minutes and both ways 1 hour. I am so tired right now from the walk but it was worth it since my phone will be brought to life!! I am so happy right now!!!
Click to expand...
Click to collapse
:good:
eldos777 said:
:good:
Click to expand...
Click to collapse
Thanks for your advice to for fixing the phone! I appreciate it!!

No USB connectivity and phone is soft-bricked

Hello everybody, I own an Xperia XC and a couple of months ago I’ve rooted it and I flashed 34.1.A.1.198 firmware, Advanced Stock Kernel and TWRP-recovery. All worked fine, until two weeks ago it lost suddenly the USB connectivity. I tried different USB-cables on different PC’s but neither the phone, nor the PC’s act in any way. Even in fastboot- or flashmode it doesn’t appear in the device manager of the PC’s. I made for a couple of times factory reset, I even changed the phone’s USB charging port with a new one, but nothing changed. I could load the phone only over a power strip with USB-power-supply. I tried to flash the firmware 34.1.A.1.198 again using flashfire (I made a pre-rooted .zip-file with PRFCreator) but now I get a boot-loop. The phone starts till Sony-Logo and after a few seconds it turns off and boots again. Trying to get in recovery mode has no effect (pressing volume up or down and Power-button).
Has anyone any idea, how can I solve this problem? Is there any possibility to make a hard reset without USB-connection?
man why did mess with your phone when you knew you cant use usb connection???
try this: press all buttons and hold them to turn the phone off then try to get access to twrp(or any recovery on your phone) then use a usb type-c flash memory with your phone to flash another zip and hopefully just bring the phone back to life
Kianush said:
man why did mess with your phone when you knew you cant use usb connection???
try this: press all buttons and hold them to turn the phone off then try to get access to twrp(or any recovery on your phone) then use a usb type-c flash memory with your phone to flash another zip and hopefully just bring the phone back to life
Click to expand...
Click to collapse
Thanks for your ansver Kianush, but it seems the phone can't handle any connected devices at the USB-port. Besides of that, when I try to connect it in flash- or fastboot mode, the LED goes green or respectively blue, but none of my PC's doesen't recognize it as a connected device in any way.
I tested the PC connection with an other Xperia XC (my daughter's), it worked without any problems. It was shown in the dewice manager as an "SOMC Flash Device".
It seems like some USB-kernel drivers are lost (?)
I think an option could be using s1tool, but I don't find something for Xperia XC and I don't know yet where the testpoint is for this phone.

Categories

Resources