I have a rooted OOS 2.2.0 and twrp 3.
I have used ptg drive using the MI adaptor and otg cable,it works.
But the same wouldn't be recognized in the recovery menu. There, it indicates 0MB in of OTG data and it is disabled to get selected.
Adb push takes a lot of time and energy to do, though i did it last time.
If anything can be changed or any solution exists, share please.
Also suggest some custom ROM's where LAF and fingerprint sensor works.
No such support in exodus and cm13 unofficial still gives me chills ,goes into bootloop once in a while
XDA Visitor said:
I have a rooted OOS 2.2.0 and twrp 3.
I have used ptg drive using the MI adaptor and otg cable,it works.
But the same wouldn't be recognized in the recovery menu. There, it indicates 0MB in of OTG data and it is disabled to get selected.
Adb push takes a lot of time and energy to do, though i did it last time.
If anything can be changed or any solution exists, share please.
Also suggest some custom ROM's where LAF and fingerprint sensor works.
No such support in exodus and cm13 unofficial still gives me chills ,goes into bootloop once in a while
Click to expand...
Click to collapse
Hi
Thank you for using xda assist
May i know what device specifically??
Related
Every thing was fine while my nexus s istalled CM10.
But after I install CM10.1 M2,I lost my USB connection.
I get the following when the cable is connected: "USB device not recognized".
I tried on different computers and usb cables then got same "USB device not recognized".
After I google that, They said install an app called "USB Switcher". Open it and clicked change to mass storage
and reboot. Then my computer still said "USB device not recognized".
I found the cyanogenmod official forum. There was a man got same proble. I post my story.
but did not get reply.
I thought it may be a bug with MTP transfer mod.
But I did got more information about that.
I thought it may be a bug for CM10 ,but now I intalled CM10 MOD from CM10 M2 TO RC5. Still got same thing.
So I come here for help.
Thanks in advance for any suggestions.
Hi there mate,
try this method :
http://forum.xda-developers.com/showthread.php?t=1901617
cheers
That did not help.
eytan123 said:
Hi there mate,
try this method :
http://forum.xda-developers.com/showthread.php?t=1901617
cheers
Click to expand...
Click to collapse
Hi there
That did not help.
The problem happened after I upgraded CM10.1 CM2 from CM10.1 CM1.
What I did is that just wiped data,cache and install CM10.1 CM2. Then I lost USB connection.
No Prompt for USB storage when connected to PC
Hi, I notice that i am having a problem since some days that am not getting the prompt for USB storage when connected to my Laptop.
I tried all possible solutions changing cables, mounting SDcard from boot, etc etc and also chnaged back an older update of the current ROM. But nothing seems to work. Please help
Model - Nexus S
Android Version : 4.2.2
Baseband Version: I9020XXKI1
Kernel Version: 3.0.50-Cynogenmod-gb97752e [email protected] #1
Fri Jun 7 19:30:29 IST 2013
CPU ARMv7 Processor Rev 2(v71)
Memory: 396
Avatar ROM Version: 2.14b- 1029 20130607-crespo
Build Date Fri Jun 7 19:22:06 IST 2013
Build Number : cm_crespo-userdebug 4.2.2JDQ39E 1029 dev-keys
Vijay
[email protected] said:
Every thing was fine while my nexus s istalled CM10.
But after I install CM10.1 M2,I lost my USB connection.
I get the following when the cable is connected: "USB device not recognized".
I tried on different computers and usb cables then got same "USB device not recognized".
After I google that, They said install an app called "USB Switcher". Open it and clicked change to mass storage
and reboot. Then my computer still said "USB device not recognized".
I found the cyanogenmod official forum. There was a man got same proble. I post my story.
but did not get reply.
I thought it may be a bug with MTP transfer mod.
But I did got more information about that.
I thought it may be a bug for CM10 ,but now I intalled CM10 MOD from CM10 M2 TO RC5. Still got same thing.
So I come here for help.
Thanks in advance for any suggestions.
Click to expand...
Click to collapse
i son't think it's rom related, i had the same issue with others rom, i asked here but nobody answered me... anyway i found that if you pullout battery then go in recovery fix permission and reboot it starts working again... i think it's some kind of error in the file system, propably the best solution would be to format the partition deleting all data on SD... i'm not able to understand what caused this, one thing i did, but i don't know if it's related, was using LAGFIX and trimming system and data... u can try to mount USB from recovery and see if that works, what recovery are you using ???
kriout said:
i son't think it's rom related, i had the same issue with others rom, i asked here but nobody answered me... anyway i found that if you pullout battery then go in recovery fix permission and reboot it starts working again... i think it's some kind of error in the file system, propably the best solution would be to format the partition deleting all data on SD... i'm not able to understand what caused this, one thing i did, but i don't know if it's related, was using LAGFIX and trimming system and data... u can try to mount USB from recovery and see if that works, what recovery are you using ???
Click to expand...
Click to collapse
My recovery is ClockworkMod Recovery v6.0.3.1
I got a way from cm forum。 They said pullout the battery and hit power button random then it will work。But that didn·t help。
I tried your method fix permissions. reboot... IT`s did not work. I try to recheck the USB DEBUG MODE。 It's reboot ...
after all. Noting changed...
I will backup my phone. And try to repartition .and install the latest CM 10.1.0 http://get.cm/get/8Li .
that one is the last cwm recovery and usb mount doesn't work in that ... try last philz touch recovery u can find it here http://d-h.st/users/philz_touch/?fld_id=16784#files and try again, try mounting usb from recovery and see if it works, try flashing another kernel and fix permission againg, it may works the second or third time maybe ...
How to use this Philz Touch recovery?
Hi Kriout, I am unable to access my phone from my computer for about a week now. Earlier it was working fine. I tried resetting the usb ports by uninstalling and re-installing them. only once myphone (Nexus s I9020) is recognized as an unknown device but Windows 7 unable to update the drivers or find them for this device.
If I want to even go back to stock rom ( I am currently using Avatar ROM 4.2.2(android) ) as i am unable to access my phone via computer.
I tried going back to older updates of Avatar Rom to see if its the ROM which might be the issue, but that didn't work either.
I tried mounting the USB/SD via the bootloader but no use.
Can you help me please?
Vijay
paydy12 said:
Hi Kriout, I am unable to access my phone from my computer for about a week now. Earlier it was working fine. I tried resetting the usb ports by uninstalling and re-installing them. only once myphone (Nexus s I9020) is recognized as an unknown device but Windows 7 unable to update the drivers or find them for this device.
If I want to even go back to stock rom ( I am currently using Avatar ROM 4.2.2(android) ) as i am unable to access my phone via computer.
I tried going back to older updates of Avatar Rom to see if its the ROM which might be the issue, but that didn't work either.
I tried mounting the USB/SD via the bootloader but no use.
Can you help me please?
Vijay
Click to expand...
Click to collapse
- you should first try to understand if it's a driver problem or a smartphone problem, try to mount USB on other pc
- if they doesn't work you should try to mount it in recovery, use TWRP, an old CWM ( in the last one this function doesn't work) or the philz recovery that u find here http://d-h.st/users/philz_touch/?fld_id=16784#files, try to fix permission, wipe cache and dalvik and pullout battery alos several time if it doesn't work. i found out that for me pulling out battery entering recovery fixing permission, shut down, pull out battery entering recovery and mounting USB often worked... you can try also using different kernel,
- my idea is that the problem is an error in the SD file system so propably the best solution could be formatting the unity from the smartphone itself. i still didn't do it but i made a good cleanup of all folder, even the system file and system folder, leaving jjust music photo and download...
- if everything works in recovery but not in the rom, it could be a kernel or a rom problem, so first change the kernel, if doesn't work make a clean install of something else ... i'm using MIUI v5 with marmite 8.7bigmem and for now everything started working again ...
Thanks
kriout said:
- you should first try to understand if it's a driver problem or a smartphone problem, try to mount USB on other pc
- if they doesn't work you should try to mount it in recovery, use TWRP, an old CWM ( in the last one this function doesn't work) or the philz recovery that u find here....... try to fix permission, wipe cache and dalvik and pullout battery alos several time if it doesn't work. i found out that for me pulling out battery entering recovery fixing permission, shut down, pull out battery entering recovery and mounting USB often worked... you can try also using different kernel,
- my idea is that the problem is an error in the SD file system so propably the best solution could be formatting the unity from the smartphone itself. i still didn't do it but i made a good cleanup of all folder, even the system file and system folder, leaving just music photo and download...
- if everything works in recovery but not in the rom, it could be a kernel or a rom problem, so first change the kernel, if doesn't work make a clean install of something else ... i'm using MIUI v5 with marmite 8.7bigmem and for now everything started working again ...
Click to expand...
Click to collapse
Here's what i Did. I did install Philz touch recovery. Its very useful. I also installed the Nexus Root Toolkit (NRT). Using NRT I launched the USBDeview. Using this i removed all the google related drivers from the system. I then restarted my phone is bootloader mode and restarted my system as well. Now my System was trying to install the nexus S drivers but unfortunately it said that the device in disconnected. But then in bootloader mode i put the phone in Mount USB storage mode and VOILA i was able to see all my files. I did take a quick back up . But still in the normal mode i was not getting the USB Storage prompt. Now i went back to the bootloader and did a factory reset. and then installed the Latest Avatar ROM. and now I am able to access the Phone storage through my computer.
I am not sure if i had deleted some files by mistake or some other issue. And thank for referring the Philz Touch Recovery. Its great.
Now am thinking of installing the Stock ROM for NEXUS S back on to my Phone. Do you think its a good Idea?
Thanks for all the help mate.
paydy12 said:
Here's what i Did. I did install Philz touch recovery. Its very useful. I also installed the Nexus Root Toolkit (NRT). Using NRT I launched the USBDeview. Using this i removed all the google related drivers from the system. I then restarted my phone is bootloader mode and restarted my system as well. Now my System was trying to install the nexus S drivers but unfortunately it said that the device in disconnected. But then in bootloader mode i put the phone in Mount USB storage mode and VOILA i was able to see all my files. I did take a quick back up . But still in the normal mode i was not getting the USB Storage prompt. Now i went back to the bootloader and did a factory reset. and then installed the Latest Avatar ROM. and now I am able to access the Phone storage through my computer.
I am not sure if i had deleted some files by mistake or some other issue. And thank for referring the Philz Touch Recovery. Its great.
Now am thinking of installing the Stock ROM for NEXUS S back on to my Phone. Do you think its a good Idea?
Thanks for all the help mate.
Click to expand...
Click to collapse
i don't think the stock rom is the best rom ... it depends on what you need ... by the way what is your data transfer rate ( into the SD )??? me in recovery get a good speed with a lot of spike, it transfer data at 5 mbs with spike of 15 and sometime go to 0 ... when i mount USB on the rom i get an almost constant 1.5 mbs that is reaaaaaaally slow ... if i test the write speed using the phone it returns me a normal speed...
p.s. when u say u mount USB in bootloader, u mean on recovery ?
Hi,
I've searched and searched, and posted on other forums looking for help. If anyone can help me, I would truly appreciate it.
My mother's phone (Samsung Galaxy Note 3 N9005) recently updated itself to Android 5.0. This somehow broke the phone, and now it is in a reboot loop. Once the phone starts up, it will reboot itself within a second. I can still run it in "Odin" mode, and in recovery mode. Safe mode doesn't work.
Most people would want advice on how to fix their phone, but I've come to accept that it will need a factory reset/flash. However, I would really like to backup the photos on the internal memory. Is there a way?
I have tried:
1) Deleting the cache;
2) Using Odin tools to load different firmware versions on the phone (4.4.2, other 5.0 versions for different carriers);
3) Safe mode.
Nothing has worked so far. All I want to do is have the phone start up and remain on whilst I plug it into a PC and copy the photos. I'm willing to try anything, so if you have any tips, please share them. If there's anymore technical information I can provide to help, let me know.
Thank you.
If you have installed the TWRP you can try to make a backup and then still via TWRP copy it to the PC by using OTG and TWRP file manager, and then open it
Sent by my iPad using Tapatalk
joe2k01 said:
If you have installed the TWRP you can try to make a backup and then still via TWRP copy it to the PC by using OTG and TWRP file manager, and then open it
Sent by my iPad using Tapatalk
Click to expand...
Click to collapse
Thanks. I've heard a lot about TWRP but haven't used it yet. The phone isn't rooted but I can hopefully root it and try your method. Can you please elaborate on OTG a bit? Haven't heard of it, but I'll look it up.
max planck5 said:
Thanks. I've heard a lot about TWRP but haven't used it yet. The phone isn't rooted but I can hopefully root it and try your method. Can you please elaborate on OTG a bit? Haven't heard of it, but I'll look it up.
Click to expand...
Click to collapse
Ok, so you can install the TWRP w/o root using odin. The OTG is a specification that allows any device capable of acting as a host (such as a smartphone ) , to communicate with USB devices, and so with OTG you can copy files from your phone to a usb or viceversa. :good:
Hi all who read this, after I flashed lineage and gapps and magisk,there was some error message for magisk. So I went to the system clearly after that, and I had to root my phone so I went again to the twrp, a weird message said hello to me. It was about modification something so I first time saw that and didn't care for it actually. then I saw that internal storage was totally deleted and everything with it. I couldnt flash any roms because there was none. All I can reach is fastboot and twrp. But, they are not working very well either. Couldn't see my device on pc with command adb devices, couldn't do adb sideload via twrp, then I bought a otg cabel and it didn't work either (my usb port on opo is working). I can't mouth the usb otg choise in twrp. So I was working for it for 2 days for saving my opo but couldn't. Can anyone help me with this problem please?
Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
Edit 2: I'm able to use USB OTG to connect to a flash drive. It's so weird that it won't establish a connection with my PC...
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
This is a very strange issue but have you downloaded and installed the official USB drivers for this phone?
Terkitoez said:
Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
Click to expand...
Click to collapse
Terkitoez said:
Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
Click to expand...
Click to collapse
try cleaning out the port on the phone.
MrSteelX said:
try cleaning out the port on the phone.
Click to expand...
Click to collapse
Gave the port a good couple of blasts with compressed air, but still no luck. What's weird is that it gets picked up by my computer perfectly fine while in EDL mode. Thank you for the suggestion.
amirage said:
This is a very strange issue but have you downloaded and installed the official USB drivers for this phone?
Click to expand...
Click to collapse
Hi amirage, yes I've installed the official OnePlus drivers and the Google ADB drivers, but no luck
Terkitoez said:
Hi amirage, yes I've installed the official OnePlus drivers and the Google ADB drivers, but no luck
Click to expand...
Click to collapse
I have to wait for something in the usb to time out, then it will load. Often more than a minute.
Im having a similar issue, it seems like Win 10 is having issues with the drivers or something cuz I can see my phone on the PC but cant access the storage at all.
It's working now!
Apologies for the silence, but I was able to miraculously get the phone to finally show up in ADB and Fastboot. I'm not exactly sure what triggered the fix or the order of things I did to get it to show up, but I did multiple flashes of Android 9 through the MSMTool and reinstallations of the OnePlus Drivers and ADB drivers in different orders until it eventually showed up on my computer. I flashed latest OOS 10 after that, successfully unlocked the phone, installed TWRP, flashed persist.img (for OP7Pro) to be safe, and installed Havoc OS A10. Sensors and Warp Charging are back and working as they should be. Thank you all for the replies.
Hello all,
I flashed a MIUI test build that was made by a fellow XDA user, but it seems to have destroyed the data transfer on my USB cable. When I still had a ROM booting, USB debugging would only work after I rebooted the device through the ROM to the system. I've installed all the drivers, checked if it was detected, etc.
Moderators, please close this thread; I have solved the issue.
Xryphon said:
Hello all,
I flashed a MIUI test build that was made by a fellow XDA user, but it seems to have destroyed the data transfer on my USB cable. When I still had a ROM booting, USB debugging would only work after I rebooted the device through the ROM to the system. I've installed all the drivers, checked if it was detected, etc.
Click to expand...
Click to collapse
how
Levered said:
how
Click to expand...
Click to collapse
There was a MIUI ROM available on Telegram, and then I used MSMTool to restore my device because it flashed the OxygenOS 12 firmware that my device wasn't compatible with. I was able to have some luck restoring my device when I fixed my drivers and my computer was able to detect my phone.