Hey all.
I use a Redmi Note 3 (Snapdragon) and upto now I used CM13. I wanted to switch back to MIUI 8, as it supports LTE, so I tried to flash the MIUI ROM using TWRP. My device bricked and doesnt go past the loading screen. The bootloader also got locked and my device is also not being detected in adb command prompt. In device manager, I can only see ADB Bootloader driver but not any other. I tried installing ADB drivers again but it doesnt work. I believe I did not enable USB debugging. I have a TWRP backup of the previous ROM on my pc but is there any way to flash it?
Please help
Hi , I am new to xda and was previously viewing the posts of other users only, now I have an issue with one of my devices. I have a phicomm passion 660 in INDIA AKA Phicomm P660 in Europe.issue is the digitizer is broken ,USB debug is not enabled, ADB and Fastboot doesn't recognise the device as it appears to be issue with Google USB drivers( which is obvious due USB debug not enabled), all I want to do is use optical mouse to use the device again for DEDICATED VR VIEWING, I can boot the device to Fastboot and in normal boot the pc recognises the device as MTP, I tried steps from many other posts but since the device is not recognised by ADB , the result is ground zero,cant install cwm through sdcard due signature verification error.so any help or direction to relevant posts would be very helpful
Related
Hello Guys,
I would like to flash a Redmi Note 3 pro with twrp.
The problem is it is not recognized by PC. It's not even showing anything in device Manager.
I installed usb drivers from Xiaomi, I booted to Fastboot Mode and connected the Phone to the PC. Nothing is happening. No device ist showing in device Manager.
I tried 3 different USB cables and also to connect it to a notebook instead using my PC. No Chance.
Then I tried to connect a Redmi Note 4X in Fastboot mode and the same happened. IT IS Not recognized and the device manager don't show a new device.
Both phones are officialy unlocked.
Anyone who faced the same problem and can help
Joe886 said:
Hello Guys,
I would like to flash a Redmi Note 3 pro with twrp. The problem is it is not recognized by PC. It's not even showing anything in device Manager. I installed usb drivers from Xiaomi, I booted to Fastboot Mode and connected the Phone to the PC. Nothing is happening. No device ist showing in device Manager. I tried 3 different USB cables and also to connect it to a notebook instead using my PC. No Chance. Then I tried to connect a Redmi Note 4X in Fastboot mode and the same happened. IT IS Not recognized and the device manager don't show a new device. Both phones are officialy unlocked. Anyone who faced the same problem and can help
Click to expand...
Click to collapse
Hi, so you have tried 2 PCs, 2 phones and 3 cables. I think you missed it in the Device Manager. Please connect your RN3P phone in fastboot mode and run http://www.uwe-sieber.de/usbtreeview_e.html then do File/Save full report, and post it here. Alternatively, run any live Linux and post lsusb output.
Thank you for your reply.
As it seems I can´t post links because i`m new and when I try to post the report here it says I can`t because it has more than 30000 caracters
But as I said it won´t be recognized. Both of them won`t.
When I connect them in working mode I can´t even access the data like pictures etc.
One of the 3 usb-cables were originaly packaged as I at first suspected the usb cables were faulty.
But now a friend of mine come by and I tested to connect his Redmi note 4x and it is working. The only difference is that he has miui 8 and I have miui 9 from xiaomi.eu.
So I am out of ideas now. The only I can imagine is that both usb ports on the smartphone are ****ed and therfore it won´t connect properly.
Charging is no problem by the way
Bro you have to setup adb drivers perfectly a single error in setting up leads error but no worry it would not harm your device....
So first of all setup adb driver from the given link it will show you how to setup adb driver
Then go your processor of setting up twrp.
If you need any help on setting up twrp just reply on it....
Hi,
I have a Redmi note 5, just 5 months old. Recently it fell down and the screen is completely broken. Unable to see the screen and touch is not working. I want to recover data from the phone. I was trying without any luck for past couple of days. Tried following things and none helped.
1. Connected phone to PC via USB cable, but since by default MTP is not enabled internal storage is not displayed.
2. Tried to use MI PC suit but seems like it's not supporting the Android version or MiUi version. I have Android N and MiUi 10. Tried with multiple versions of PC suit and no luck.
3. Reboot to fastboot mode : I don't have debugger option enabled, so only fastboot commands work, adb commands not working. Tried to unlock OEM, flash custom recovery etc: and nothing works! (Next time first thing I'll do with a new phone is enabling debug mode!!)
4. Tried to use Mi account to unlock bootloader but since device is not added into my acount, that also not possible.
5. Tried a bunch of softwares to cast screen to pc or control from pc , but nothing works as debugging not enabled.
I need help if anyone having any other ideas.
One way in my mind is to enable usb debugging just by using an otg keyboard. But this requires help from some one really kind.; to upload a video showing how to open settings and enable debugging only using a keyboard connected via OTG cable ( My phone is running on MiUi 10). I know it's too much to ask..but.. still..
Thank You
Hello,
I am left with a OPX with no ROM, and no bootloader (after trying to upgrade TWRP). It shows the Oneplus icon, and Fastboot mode works.
I'm trying to access the device through adb or fastboot, but my computers can't detect nothing.
I installed Qualcomm drivers, ADB & Fastboot, Oneplus USB drivers. I tried to connect my OPX with Fastboot, and with "volume up" plugging (as shown in the mega unbrick guide), nothing shows up in the device manager.
What can I do ?
Thank you very much.
NOTE : I was not in developer mode on the last ROM installed ...
Since fastboot works it seems that your PC or maybe the conection might be the problem here.
Have you tried different cables, USB ports, different computers or different Operating Systems?
Could your MicroUSB Port be broken?
( You could give Ubuntu a shot. It might take a little time to install, but it's free and if you can save your phone with it it could be worth the time. You can also unbrick your device under Linux once you successfully connect it in EDL mode. )
I am trying to root my old phone Samsung Galaxy core prime G360h so that I can gain some confidence to change the stock rom of my main device. When the phone is on, adb works perfectly and recognise the device. I can even reboot device when the phone is unlocked. But once I go into Fastboot/Recovery mode then ADB fails to find the device and no commands work(.To the best of my knowledge, I have all the necessary drivers. I have tried multiple USB slots, multiple computers (Windows 7 sp1 and Windows 10 latest update), and have searched all around the internet and various forums on XDA for an answer. I've tried manually updating the USB drivers through device manager, installed universal usb driver, but that did nothing. What I don't understand is that how ADB works when the device is on but don't work when it's in Recovery/Fastboot mode. I would have post images to clear things but the site is not letti g me to post imaves
tldr: adb recognize phone when it's on but Adb don't work in fastboot/recovery mode
Thanks in advance for any help, I've tried everything I can think of.
On MediaTek devices you need Preloader VCom Driver so your PC would detect your phone on fastboot but on Qualcomm ( which is your phone chipset ) i don't know what driver is required ...
I own the TV BOX TRANSPEED_H616 (Allwinner H616, Arm Mali-G31 MP2, Android 10, 4/64 GB).
I would like to root but can't. I can't even connect the device to the PC.
When I connect it with the USB-OTG cable, in the device manager it shows "USB device unknown (device descriptor request failed)" and I cannot find the drivers. Can someone help me?
Thank you
i have same problem.
After several attempts I managed to enter recovery mode.
I would like to root the device now but I don't know how to do it.
Can anyone help me?
Thank you
Since no one can help me, I want to try to summarize everything I understand using this device. The first thing to do is to enable the developer option and then check USB DEBUG and USB0. At this point, by connecting the USB cable to the OTG input, the device is recognized by the PC as MPT. By opening the Phoenixsuite or Powershell application from the SDK folder you can send commands to the device, you can access the custom recovery and nothing more. Unfortunately, the bootloader cannot be unlocked, and the firmware cannot be changed either through the PC or even with SD. When entering Bootloader mode the PC loses connection with the device because it changes to an unknown device without drivers. Also with Powershell if you want to unlock the bootloader this is not possible because when you send the command "./fastboot flashing unlock" it returns the message "Failed". By inserting the SD card with the firmware and starting the device with a stick inserted in the AV input and the electrical AC connector, a red indicator lights up on the display and the flashing does not start. Clearly in these conditions it is impossible to think about rooting the device. I hope that in the light of what has been said, someone can give me some research ideas or useful advice. Finally I apologize for my English (from Google)
Hello, recently I bought a transpeed X88 pro s (from transpeed official) , h616, 4gb+128gb with android 10.
But it is a fake, it's a board with hacked firmware (dispute is open) , it only have 64gb ( chip Samsung Klmcg2ketm), it warm so much (more than 90°C) with faults on gpu (changing colors, slowly,...), only way to work is with open box or fan.
Anyway, I'm in the way to root and change firmware too.
It's rooted by default, with supersu 1.82 work well and permit restart to bootloader (with reset button was impossible).
I will inform about progress.