Is there any way to fix this? No Usb-Debugging, Bootloop, etc... - OnePlus X Q&A, Help & Troubleshooting

Hello guys,
im starting to lose hope that my phone will ever get to work again. I tried flashing a rom via TWRP, which led into a bootloop. After that I tried flashing another version of TWRP, which let to the fact, that everytime I now press Power + Volume down it also gets into a bootloop and does not show up TWRP. After that I tried connecting it to my PC in Fastboot mode, but since no USB-Debugging is enabled and cant be enabled, it is also not working, even with Universal Adb drivers installed, windows does not recognize any device is connected... so my question is, if there is any hope left or my phone is just dead...
I really hope you can help me.
Leon

[email protected] said:
Hello guys,
im starting to lose hope that my phone will ever get to work again. I tried flashing a rom via TWRP, which led into a bootloop. After that I tried flashing another version of TWRP, which let to the fact, that everytime I now press Power + Volume down it also gets into a bootloop and does not show up TWRP. After that I tried connecting it to my PC in Fastboot mode, but since no USB-Debugging is enabled and cant be enabled, it is also not working, even with Universal Adb drivers installed, windows does not recognize any device is connected... so my question is, if there is any hope left or my phone is just dead...
I really hope you can help me.
Leon
Click to expand...
Click to collapse
Did you tried the Mega unbrick Guide?

Never loose hope buddy we have many devs here to help us
Try this it will help you for sure
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108

faap25 said:
Try this it will help you for sure
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Click to expand...
Click to collapse
Thank you for your help. I was trying to do it with this mega unbrick guide, but at step 4 I connected it to my pc and the device manager didn't show up anything. Do I need to install any drivers before doing that or uninstall the adb drivers I previously installed?

Thank you
Finally it worked! The problem was the usb cable I was using!

Related

Bricked Tablet

I really Need Help! My computer wont recognize my tablet in fastboot mode, and my tablet wont read my micro SD card, also when i turn it on normally it stays at splash screen and when its plugged in to the computer the computer starts installing the drivers and it fails to install each time. I go to troubleshooting options and it states code 10. which states device cannot start.
I Have looked for ways around this, like manually installing the drivers, and my computer wont let me. Also the tablet can go to both: bootloader, and Clockworkmod recovery.
I factory reset my tablet so I cannot install anything, untill i get it to connect to my computer.
I am running Windows 7 64-bit on my computer!
Any help is very much appreciated!
Thanks!
NewDev4IOS said:
I really Need Help! My computer wont recognize my tablet in fastboot mode, and my tablet wont read my micro SD card, also when i turn it on normally it stays at splash screen and when its plugged in to the computer the computer starts installing the drivers and it fails to install each time. I go to troubleshooting options and it states code 10. which states device cannot start.
I Have looked for ways around this, like manually installing the drivers, and my computer wont let me. Also the tablet can go to both: bootloader, and Clockworkmod recovery.
I factory reset my tablet so I cannot install anything, untill i get it to connect to my computer.
I am running Windows 7 64-bit on my computer!
Any help is very much appreciated!
Thanks!
Click to expand...
Click to collapse
Did you install the naked driver from here? http://forum.xda-developers.com/showthread.php?t=1426502 if not do that first once you get that working... then you should be able to fastboot to the pc... next thing I would concider is going to twrp recovery instead of cwm....either go for an older version or go the full gambit of nvflash then install the latest twrp... after that you should be set.....I can comment more on it if you need it....
Bricked Tablet Help
Gage_Hero said:
Did you install the naked driver from here? http://forum.xda-developers.com/showthread.php?t=1426502 if not do that first once you get that working... then you should be able to fastboot to the pc... next thing I would concider is going to twrp recovery instead of cwm....either go for an older version or go the full gambit of nvflash then install the latest twrp... after that you should be set.....I can comment more on it if you need it....
Click to expand...
Click to collapse
I tried installing those drivers but it didnt work
also i used WSG_Unbricker v.1.0.3
my system is wiped
is there any way to install the operating system on it
i need a link for an update.zip
thanks
i can now only go to fastboot mode and wipe data mode.
NewDev4IOS said:
I tried installing those drivers but it didnt work
also i used WSG_Unbricker v.1.0.3
my system is wiped
is there any way to install the operating system on it
i need a link for an update.zip
thanks
i can now only go to fastboot mode and wipe data mode.
Click to expand...
Click to collapse
What do you see in device manager with the tablet plugged into the pc and running in fastboot?
Maybe this helps
I had a similar issue but my tablet couldn't be identified by windows, at first i thought it was my drivers so i tried to install new ones but windows wouldn't let me stating the same code 10. At the end it was a defective usb cable, i bought a new one and everything worked all right the first time i plugged it in. And by the way i was stucked at the CWM loop. Hope this helps and sorry for my bad english.
Bricked tablet
sj010489 said:
I had a similar issue but my tablet couldn't be identified by windows, at first i thought it was my drivers so i tried to install new ones but windows wouldn't let me stating the same code 10. At the end it was a defective usb cable, i bought a new one and everything worked all right the first time i plugged it in. And by the way i was stucked at the CWM loop. Hope this helps and sorry for my bad english.
Click to expand...
Click to collapse
Thanks
Im not sure if it is a bad usb cable, i think it is my computer because my computer doesnt even recognize my iphone and i have itunes installed,
i think it is partially due to a funky computer for me.
BRICKED
Gage_Hero said:
What do you see in device manager with the tablet plugged into the pc and running in fastboot?
Click to expand...
Click to collapse
It says fastboot
I sent my tablet in to asus
just waiting on them to reply

[Q] Bricked my HTC One X+

The titel says it all , and I need some help. I can still go in recovery but adb won't recongize my HTC, but I can still find it in fastboot. I formatted the sdcard, so I have nothing on there. Help would be much appreciated.
vsp33ddyv said:
The titel says it all , and I need some help. I can still go in recovery but adb won't recongize my HTC, but I can still find it in fastboot. I formatted the sdcard, so I have nothing on there. Help would be much appreciated.
Click to expand...
Click to collapse
Oh, trust me that's not your phone being bricked. You guys seriously need to know the correct vocabulary.
Bricking the phone: The phone's only use is to use it as a literal brick. It does not turn on, does not recover, does not charge, does not do anything and it can never be restored.
HOX+ can NOT be bricked unless you are S-Off'ed. Now that we got that out of the way,
you seem to understand that ADB is the solution here, that you need to sideload a rom, the question that you have is the adb does not recognize your phone, so follow these steps:
-Connect the phone using a different usb port, (basically thats the easiest thing), if its 2.0 then try 3.0 and vice versa.
-Restart your computer
-Restart your phone
-If you are on windows Vista and later, open start menu search for "cmd" then right click and run it as administrator, then you need to cd to your adb directory.
Code:
cd C:\Android\sdk\platform-tools
for example. then try adb devices.
Anyway hope you get it to work and have fun
Ghand0ur said:
Oh, trust me that's not your phone being bricked. You guys seriously need to know the correct vocabulary.
Bricking the phone: The phone's only use is to use it as a literal brick. It does not turn on, does not recover, does not charge, does not do anything and it can never be restored.
HOX+ can NOT be bricked unless you are S-Off'ed. Now that we got that out of the way,
you seem to understand that ADB is the solution here, that you need to sideload a rom, the question that you have is the adb does not recognize your phone, so follow these steps:
-Connect the phone using a different usb port, (basically thats the easiest thing), if its 2.0 then try 3.0 and vice versa.
-Restart your computer
-Restart your phone
-If you are on windows Vista and later, open start menu search for "cmd" then right click and run it as administrator, then you need to cd to your adb directory.
Code:
cd C:\Android\sdk\platform-tools
for example. then try adb devices.
Anyway hope you get it to work and have fun
Click to expand...
Click to collapse
The only thing I can do is use fastboot , thx for noticing that I know I need adb sideload If I look in devices on my PC I can see 'ONE' with a yellow triangle next to it ( so this means drivers) I downloaded my HTC drivers and I right clicked on the device and then update from PC , I go to the folder where I installed it and click on search and it says it can't find a driver for this device.
I also tried 4 different USB ports both 2.0 or 3.0 , no result. I also tried to install TWRP instead of cmw but on TWRP my touchscreen doesn't work while on cmw it does. So i went back and flashed my recovery to cmw again ( I tried version 2.6 - 2.7.0.1 , no result )
So my problem right now can be solved once my device can be recognized by my PC. (Have HTC maneger installed , also downloaded drivers formy phone , got fastboot and adb on my PC )
For anyone who knows thanks
vsp33ddyv said:
The only thing I can do is use fastboot , thx for noticing that I know I need adb sideload If I look in devices on my PC I can see 'ONE' with a yellow triangle next to it ( so this means drivers) I downloaded my HTC drivers and I right clicked on the device and then update from PC , I go to the folder where I installed it and click on search and it says it can't find a driver for this device.
I also tried 4 different USB ports both 2.0 or 3.0 , no result. I also tried to install TWRP instead of cmw but on TWRP my touchscreen doesn't work while on cmw it does. So i went back and flashed my recovery to cmw again ( I tried version 2.6 - 2.7.0.1 , no result )
So my problem right now can be solved once my device can be recognized by my PC. (Have HTC maneger installed , also downloaded drivers formy phone , got fastboot and adb on my PC )
For anyone who knows thanks
Click to expand...
Click to collapse
Hmmm. I would say in the device manager right click on the one and uninstall. Then in fastboot mode unplug and replug the device, let it install fastboot again and then try if adb can read it now.
Ghand0ur said:
Hmmm. I would say in the device manager right click on the one and uninstall. Then in fastboot mode unplug and replug the device, let it install fastboot again and then try if adb can read it now.
Click to expand...
Click to collapse
Still can't read it...
This has happened to my phone twice... fixed it the first time by using USB deview to remove all Android/HTC drivers, then reinstalled them with the HTC Sync installer. Couldn't get that to fix it last time though, so I tried another computer and it worked just fine. So my advice would be to find another computer and try it.
911jason said:
This has happened to my phone twice... fixed it the first time by using USB deview to remove all Android/HTC drivers, then reinstalled them with the HTC Sync installer. Couldn't get that to fix it last time though, so I tried another computer and it worked just fine. So my advice would be to find another computer and try it.
Click to expand...
Click to collapse
YES THIS IS WHAT WORKED ONLY I DID SOME OTHER STEPS TOO!!! Now I got adb running again and I can only push , I'll explain later in a full tutorial how to fix this now you guys can help me , I'm trying to download a cyanmod for my HTC because the stock is german and I can't download it , so can anyone upload the cyanmod endeavouru for me I keep getting error 502 bad gateway I almost fixed it !!!!! I need it badly !
OOkay so I thought I had figured it out , I uste TWRP to push files from PC to my Phone , then I installed cmw and tried to install the ROMS , but apperantly my roms were deleted. (I can't use TWRP because I need touch and the touch doesn't work , while in cmw the touch does work)
So if we can fix the TWRP touch I will know how to fix my problem !
I fixed the problem
I fixed the problem , thread how comming soon !
Here is my thread http://forum.xda-developers.com/showthread.php?p=52550145

[Q] Odin/ADB can not see my phone (HELP)

Hello All,
I've been reading posts from here for a long time but this is my first post.
I'm coming here as a last resort to save my Galaxy s2 (SGH-T989) which has a stock ROM.
Here's what happened.
I dropped my phone and then it got stuck in bootloop (it only boots until I see the "SAMSUNG" word animation and stops there).
At that point, ODIN 'sees' that there's a connected device; KIES keeps "connecting...." but can't actually connect; ADB does not show any connected device.
So, what I wanted to do was to factory "reset" the phone. The problem is I can't get the phone into Recovery mode. I believe it's because my volume down button was acting up when the phone was working. However, I can get to "Download Mode" using a USB Jig.
So, the next thing to do is to flash a new stock ROM. However, whenever I connect my phone when it's in "Download Mode", ODIN does not see it.
Yes, I've installed, re-installed, removed, re-installed all drivers and Kies and I've done that so many times you can't even believe it.
The problem is that the device driver "SAMSUNG Mobile USB CDC Composite Device" gives the following error "This device cannot start. (Code 10)", and I don't know why or how I can get rid of that. As mentioned above, I've tried all the device driver installation fixes but none has worked.
I mean, when the phone is not in Download Mode and I connect it to my PC, all device drivers are working fine with no error, but when it's in Download Mode, I get the error mentioned above "This Device cannot start.".
So, my questions:
1) Is there a way to get to Recovery Mode without using the button combinations? (The phone is in bootloop)
2) How can I fix the device driver error mentioned above to get ODIN to see my device?
3) Is there anything else I need to be doing?
This problem is really frustrating and I've been on it for more than 2 weeks and nothing has worked so far. Any help is greatly appreciated.
1. I think you have flashed an bad kernel if you cant get into recovery mode and i dont get it why your volume down acts like up?.
2. http://support.microsoft.com/kb/943104 try to maybe also disable kies and try again.
3. Kies is on, adb doesnt work at samsung/download screen, try to reinstall samsung usb drivers again :/ yes I know but to be sure, disable driver signature or something like that if you are on windows 8.x, try another usb cable.
2weeks dont sound good. I hope these tips could help a bit but I still wonder why your phone got in bootloop when you dropped it !?!? What were you doing at that time and did the battery go out?
wulsic said:
1. I think you have flashed an bad kernel if you cant get into recovery mode and i dont get it why your volume down acts like up?.
2. try to maybe also disable kies and try again.
3. Kies is on, adb doesnt work at samsung/download screen, try to reinstall samsung usb drivers again :/ yes I know but to be sure, disable driver signature or something like that if you are on windows 8.x, try another usb cable.
2weeks dont sound good. I hope these tips could help a bit but I still wonder why your phone got in bootloop when you dropped it !?!? What were you doing at that time and did the battery go out?
Click to expand...
Click to collapse
Thanks for the quick reply, wulsic.
1. No, I did not flash any kernel on this phone, everything on it is stock and was working just fine before it was dropped. I meant that the volume down was not working properly, not that it was acting like up.
2. I tried that but did not work
3. The drivers are working fine when the phone is not in Download Mode, it's only when it's in Download Mode that I get the error and I've tried re-installing drivers and everything, I think the problem is with the device itself not a driver problem.

need help..phone not booting

Hi,
I made a mistake when trying to install custom recovery and now phone isnt starting up anymore
Now when i turn on the phone i get the following message:
[430] fastboot_init
[530] USB init ept @ 0xffe0000
[550] udc_start
I am using linux lite
I can get into download mode
Been looking online for a fix but so far notting. When i plug in usb and hold the volume up button i get into download mode, but then i dont know how to get things fixed.
I made a full system backup with adb before trying to install custom recovery but i have no clue how to get that transferred to the phone .
Thanks in advance for all the help
Here is tutorial how to flash KDZ via Lg Flashtool link
Or here (video tutorial) link
System_F said:
Here is tutorial how to flash KDZ via Lg Flashtool link
Or here (video tutorial) link
Click to expand...
Click to collapse
Hi, Thanks for your answer. I did try it but i keep getting the message that the phone is disconnected and that i need to connect usb cable and press retry.
I tried adb recovery but the phone is detected. Also it isnt detected using fastboot.
I think i really messed things up
TMG1961 said:
Hi, Thanks for your answer. I did try it but i keep getting the message that the phone is disconnected and that i need to connect usb cable and press retry.
I tried adb recovery but the phone is detected. Also it isnt detected using fastboot.
I think i really messed things up
Click to expand...
Click to collapse
1. try to delete and reinstall all drivers
2. try to click "retry", when you will get the message that the phone isn't connected
System_F said:
1. try to delete and reinstall all drivers
2. try to click "retry", when you will get the message that the phone isn't connected
Click to expand...
Click to collapse
Did reinstall drivers several times and been clicking retry for a long time but still no luck

troubleshooting to connect the phone to the PC

Hi all,
by cons for several weeks I've a concern with my redmi Note 2 and I can't find the answer to my problem on the forum or even the Internet.
Since the last update 7.2.2 (global) I have the Recovery MIUI who crushed the TWRP. I changed to test 6.3.17. The update to the .24 went wrong and I don't know why. Since the phone is bootloop. But the problem is that my phone is not recognized by any PC. I tried several PCs, several cables, several drivers, with or without the Fastboot, unable to connect. Therefore impossible to load a new version. I don't think it's material problem because the phone recharge well with a cable to the socket.
Is there another handling or debug decision to restart the phone? I'm in France for information.
thank you in advance if you can point me to a solution !
Hope someone can help me.
Manu
Can the phone boot to miui recovery? If so, you should be able to use miui recovery to flash TWRP (I think you will need one with a signed install zip). You only need to take out the external SD, put it in one of those cheap USB card readers, copy your recovery and ROM to the SD, put it back in the phone, flash TWRP with miui recovery, and then flash the ROM with TWRP (I am assuming that miui recovery can install things from the external SD - if not, then none of this will work).
Hi Bro,
Yes it boot in MIUI recovery but impossible to get access to the SD Card...
I tried to put the file on the SD card but you can't choose the path, I think the recovery will look only in the internal memory ... And as I can't access the internal memory..
I despair !!
Thanks o lot for your help
DarthJabba9 said:
Can the phone boot to miui recovery? If so, you should be able to use miui recovery to flash TWRP (I think you will need one with a signed install zip). You only need to take out the external SD, put it in one of those cheap USB card readers, copy your recovery and ROM to the SD, put it back in the phone, flash TWRP with miui recovery, and then flash the ROM with TWRP (I am assuming that miui recovery can install things from the external SD - if not, then none of this will work).
Click to expand...
Click to collapse
manu33xtro said:
Hi Bro,
Yes it boot in MIUI recovery but impossible to get access to the SD Card...
I tried to put the file on the SD card but you can't choose the path, I think the recovery will look only in the internal memory ... And as I can't access the internal memory..
I despair !!
Thanks o lot for your help
Click to expand...
Click to collapse
Ok - but have you tried the Mediatek SP Flash Tool?
Of course yes but the real problem is that the phone is not recognized by the PC and therefore can't load anything ...
Even changing drivers or cables or PC, nothing to do.
DarthJabba9 said:
Ok - but have you tried the Mediatek SP Flash Tool?
Click to expand...
Click to collapse
manu33xtro said:
Of course yes but the real problem is that the phone is not recognized by the PC and therefore can't load anything ...
Even changing drivers or cables or PC, nothing to do.
Click to expand...
Click to collapse
So, when the battery is removed, and you connect the USB cable, the phone is not even vibrating (and making that weird sound) every couple of seconds or so?
Yes you're right : every 10s the phone vibrate...
DarthJabba9 said:
So, when the battery is removed, and you connect the USB cable, the phone is not even vibrating (and making that weird sound) every couple of seconds or so?
Click to expand...
Click to collapse
manu33xtro said:
Yes you're right : every 10s the phone vibrate...
Click to expand...
Click to collapse
Well, then it is very strange that you can't use the SP Flash Tool. If the phone vibrates, then the device is recognised, and you should be able to flash anything you want with the SP Flash Tool! How exactly were you trying to use the Flash Tool?
I tried so many solutions I really don't know exactly how I used the software.
I will again try everything.
But against any changes when I look in the USB settings of the PC, the phone doesn't appear.
I try again just now, thank you for your help.
DarthJabba9 said:
Well, then it is very strange that you can't use the SP Flash Tool. If the phone vibrates, then the device is recognised, and you should be able to flash anything you want with the SP Flash Tool! How exactly were you trying to use the Flash Tool?
Click to expand...
Click to collapse
manu33xtro said:
I tried so many solutions I really don't know exactly how I used the software.
I will again try everything.
But against any changes when I look in the USB settings of the PC, the phone doesn't appear.
I try again just now, thank you for your help.
Click to expand...
Click to collapse
With the SP Flash Tool, all you need is the correct "scatter" file (MT6795_Android_scatter.txt), and the image(s) that you want to flash. If the phone is vibrating, then the SP Flash Tool should be able to connect to it when you click "Download". Just make sure that you first untick everything that you do NOT want to flash. I would try flashing the boot image (boot.img) first. If that succeeds, then try the TWRP recovery image.
Ok. I'm going to try again with "http://en.miui.com/forum.php?mod=viewthread&tid=196175&highlight=sp%2Btool%2Bflash%2Bredmi%2Bnote%2B2"
DarthJabba9 said:
With the SP Flash Tool, all you need is the correct "scatter" file (MT6795_Android_scatter.txt), and the image(s) that you want to flash. If the phone is vibrating, then the SP Flash Tool should be able to connect to it when you click "Download". Just make sure that you first untick everything that you do NOT want to flash. I would try flashing the boot image (boot.img) first. If that succeeds, then try the TWRP recovery image.
Click to expand...
Click to collapse
Well... Install again drivers MTK but nothing... The phone vibrates well but the PC still doesn't see ... It's late now, I look again tomorrow night.
Thanks again.
manu33xtro said:
Ok. I'm going to try again with "http://en.miui.com/forum.php?mod=viewthread&tid=196175&highlight=sp%2Btool%2Bflash%2Bredmi%2Bnote%2B2"
Click to expand...
Click to collapse
manu33xtro said:
Well... Install again drivers MTK but nothing... The phone vibrates well but the PC still doesn't see ... It's late now, I look again tomorrow night.
Thanks again.
Click to expand...
Click to collapse
Perhaps you might want to describe what exactly happens when do you what exactly?
Hi,
Ok that's what I do with an old PC with Win XP.
- install media Tek USB VCOM drivers for Win XP -> installation complete
- launch SP Flash Tool with administrator rights)
- use scatter file from Redmi Note 2 rom
- use download agent "MTK_AllInOne_DA.bin"
- press download button
- connect phone with UCB cable and waiting... and waiting...
- and I can't see it in device manager !
No way again !
I will try again...
DarthJabba9 said:
Perhaps you might want to describe what exactly happens when do you what exactly?
Click to expand...
Click to collapse
manu33xtro said:
Hi,
Ok that's what I do with an old PC with Win XP.
- install media Tek USB VCOM drivers for Win XP -> installation complete
- launch SP Flash Tool with administrator rights)
- use scatter file from Redmi Note 2 rom
- use download agent "MTK_AllInOne_DA.bin"
- press download button
- connect phone with UCB cable and waiting... and waiting...
- and I can't see it in device manager !
No way again !
I will try again...
Click to expand...
Click to collapse
Strange! I am assuming that when you connect the phone with the USB cable, the battery has been removed from the phone? If so, then it should work.
Perhaps you should try first connecting the phone, and then waiting until it has vibrated once or twice, before clicking the "Download" button?
Yes I removed battery before connect the phone to PC. I tried also with battery and nothing changed.
I even changed the cable to be sure.
Which seems to me most strange is that I see nothing in the device manager, as if the phone wasn't connected. Whatever the installed driver is the same result. I think it should at least have the phone on the COM or USB port ...
I will try again this night to be sure with all steps one by one. And I will also try with ACER tablet I and runs Android 5.1. Maybe it will be recognized.
Otherwise I also tried to pass a Linux PC as a last resort.
Thanks again for your help.
DarthJabba9 said:
Strange! I am assuming that when you connect the phone with the USB cable, the battery has been removed from the phone? If so, then it should work.
Perhaps you should try first connecting the phone, and then waiting until it has vibrated once or twice, before clicking the "Download" button?
Click to expand...
Click to collapse
manu33xtro said:
Yes I removed battery before connect the phone to PC. I tried also with battery and nothing changed.
I even changed the cable to be sure.
Which seems to me most strange is that I see nothing in the device manager, as if the phone wasn't connected. Whatever the installed driver is the same result. I think it should at least have the phone on the COM or USB port ...
Click to expand...
Click to collapse
Yes, it should. The fact that the phone vibrates when connected indicates that the PC and phone are communicating - but it may well be that a low-level driver in the phone has been overwritten (which may mean that this is a lost cause). A final idea - can miui recovery access usbotg?
Hum good question. In fact I don't know. I'll ask the MIUI forum.
I got home late from work so I don't do tests tonight, I'd see it all tomorrow including the connection with my tablet ...
Thanks
DarthJabba9 said:
Yes, it should. The fact that the phone vibrates when connected indicates that the PC and phone are communicating - but it may well be that a low-level driver in the phone has been overwritten (which may mean that this is a lost cause). A final idea - can miui recovery access usbotg?
Click to expand...
Click to collapse
Hi,
I tried to connect with an Acer Tablet with Android 5.1.1 but nothing appends...
I tried also with a Linux PC (Debian) and if I can see a Samsung A3 phone dirrectly, no way for my Redmi Note 2...
There really I despair : I think I can't access any of the phone. Can't do anything !
If you have any other solution but you help me a lot already, and thanks for that.
Can be a micro crack on the USB plug into the phone if it's not a software problem ... Let's go for it apart and look at this ...
Thanks again bro.
Manu
DarthJabba9 said:
Yes, it should. The fact that the phone vibrates when connected indicates that the PC and phone are communicating - but it may well be that a low-level driver in the phone has been overwritten (which may mean that this is a lost cause). A final idea - can miui recovery access usbotg?
Click to expand...
Click to collapse
manu33xtro said:
Hi,
I tried to connect with an Acer Tablet with Android 5.1.1 but nothing appends...
I tried also with a Linux PC (Debian) and if I can see a Samsung A3 phone dirrectly, no way for my Redmi Note 2...
There really I despair : I think I can't access any of the phone. Can't do anything !
If you have any other solution but you help me a lot already, and thanks for that.
Can be a micro crack on the USB plug into the phone if it's not a software problem ... Let's go for it apart and look at this ...
Thanks again bro.
Manu
Click to expand...
Click to collapse
I don't think it is a crack on the USB plug. It seems to me to be a low-level driver problem - ie, the drivers on the phone that are active when the phone is not (fully) booted up. I don't have the right terminology for these drivers, but they are possibly part of the bootloader. If that is the problem, then I don't know how you would solve this problem.

Categories

Resources