So I recently decided to try to flash the stock firmware onto my galaxy tab SM-T700 again, however, since it didn't boot I flashed TWRP onto it again and tried to push a custom rom onto the device.
The tablet however shows up as an MTP USB device in the device manager instead of an android device like it used to. My OnePlus 2 works perfectly fine in recovery, so it can't be those drivers.
Does anyone recognize this problem? Help would be much appreciated.
Thanks in advance, Rintse.
Reinstall the adb drivers while in recovery mode.
Right click, update driver.
Related
Hi guys,
Just got my new note 2 (international-n7100). I first updated to jb 4.1.2.
Then rooted the phone after several tries to detect drivers (install/uninstall etc).
After that installed rom manager and ROM toolkit pro.
I never achieved to boot in cmw through ROM manager or by using the 3 keys combination, I keep getting the default android boot.
Tried everything to reflash cmw with adb or Odin but now my PC says drivers are not recognized because of a "corrupted attempt to connect the device before" (use win 7, changed usb ports, tried different pc).
I uninstalled every drivers, kies and reinstall either directly from Samsung or using toolkit for note 2.
Nothing...
Please help, I need to get my phone conected to the PC so that I can boot in cmw and backup my ROM.
Thanks
I have only recently got a tab pro 8.4 wifi only version SM-T320, I have had Samsung phone for 6 years and have not had problems accessing recovery through ADB but this tab is causing me a problem as once in recovery mode the Tab is not recognized by ADB.
When the tab is in normal operating mode ADB works fine but as soon as you boot into recovery no device is shown as connected, can anyone tell me which driver should be installed to access the adb when is in recovery mode.
Or have Samsung blocked adb from working when the tab is booted into recovery.
install to driver ADB when the tablet mode recovery
Alexey71 said:
install to driver ADB when the tablet mode recovery
Click to expand...
Click to collapse
Translated: put the device in recovery mode, plug the usb lead in and your pc should prompt for driver install.
Sent from a stolen phone!
Alexey71 said:
install to driver ADB when the tablet mode recovery
Click to expand...
Click to collapse
shivadow said:
Translated: put the device in recovery mode, plug the usb lead in and your pc should prompt for driver install.
Sent from a stolen phone!
Click to expand...
Click to collapse
Thanks for the reply guys but that isn't the problem the one it automatically installs doesn't see the tab. It works with my S5 and S3 but the tab is not visible as soon as I boot into recovery no device is identified.
Tried to install the driers manually but I don’t get any ADB driver options from the list, it insists the driver is Google Nexus ADB Interface, this is the one that works with the S3 and S5 perfectly well but not with the Tab.
Its frustrating as it will make changing the white theme and testing the changed apk’s a long process, was hoping someone had it working and new which drivers to use as the default SDB one doesn't
Was hoping someone had their TAB working and visible in recovery mode on their computer that could tell me which drivers they were showing as being installed..
ag4751 said:
Thanks for the reply guys but that isn't the problem the one it automatically installs doesn't see the tab. It works with my S5 and S3 but the tab is not visible as soon as I boot into recovery no device is identified.
Tried to install the driers manually but I don’t get any ADB driver options from the list, it insists the driver is Google Nexus ADB Interface, this is the one that works with the S3 and S5 perfectly well but not with the Tab.
Its frustrating as it will make changing the white theme and testing the changed apk’s a long process, was hoping someone had it working and new which drivers to use as the default SDB one doesn't
Was hoping someone had their TAB working and visible in recovery mode on their computer that could tell me which drivers they were showing as being installed..
Click to expand...
Click to collapse
twrp or cwm?
Alexey71 said:
twrp or cwm?
Click to expand...
Click to collapse
Already have TWRP that works fine, thanks for the though, its the computer that can't see the tab when it is connected in recovery mode, but it can see my S5 with exactly the same diver set up.
Hi folks,
I previously managed to get Cyanagenmod installed on my HTC One X but since made a mess of it trying to get a stock ROM on there (to unlock my SIM). I have since given up on getting a stock ROM back on there and am now trying to get Cyanogenmod back on there, but I have hit some problems.
I have CWM on there and my PC can see the phone in Fastboot, but not via ADB (which I am trying to use to 'push' the ROM on there so I can install it). My PC (Win 8.1) is giving me a "device descriptor request failed" when connecting to USB when on the boot menu, and is showing up just as "One" in device manager when I load CWM. However neither of these situations are allowing my computer or ADB to recognise the SD card.
I have tried 'mounting' it in CWM, updating drivers through device manager, installing Sync (and uninstalling/reinstalling it), installing HTCDriver_4.10.0.001.msi all to no avail.
Does anyone have any advice to get my PC to recognise my phone or otherwise get a customer ROM installed (if there is another way.)
Thanks in advance all.
Bglamb said:
Hi folks,
I previously managed to get Cyanagenmod installed on my HTC One X but since made a mess of it trying to get a stock ROM on there (to unlock my SIM). I have since given up on getting a stock ROM back on there and am now trying to get Cyanogenmod back on there, but I have hit some problems.
I have CWM on there and my PC can see the phone in Fastboot, but not via ADB (which I am trying to use to 'push' the ROM on there so I can install it). My PC (Win 8.1) is giving me a "device descriptor request failed" when connecting to USB when on the boot menu, and is showing up just as "One" in device manager when I load CWM. However neither of these situations are allowing my computer or ADB to recognise the SD card.
I have tried 'mounting' it in CWM, updating drivers through device manager, installing Sync (and uninstalling/reinstalling it), installing HTCDriver_4.10.0.001.msi all to no avail.
Does anyone have any advice to get my PC to recognise my phone or otherwise get a customer ROM installed (if there is another way.)
Thanks in advance all.
Click to expand...
Click to collapse
Flash Philz 5.15.9 recovery use it to mount sd card then to copy the rom you need then flash recovery for your rom for CM12 is one for CM11 is other and for Sense is third. For sense rom you can use Philz 5.15.9. And for the new layout is fourt recovery
Thanks!
I couldn't find it so I downloaded a newer version, but it didn't work, so I looked for longer and found a version, but that wouldn't even boot. In the end I used openrecovery-twrp-2.1.7, which did let me mount the SD and install the ROM.
Then I got stuck on the loading screen, but I discovered I needed to just flash a boot.img (which wasn't in either of the guides I was following, for some reason?!) and now I'm all up and running.
Thank you kind sir!
Ok so i have a Samsung Tab s t705 lte and its right now in a bootloop. So I rooted it and flashed twrp. Then i flashed xposed framework. Flash successful but it entered a bootloop. I tried uninstaller but it still remained in the bootloop. Then i restored a nandroid backup but it still is in a bootloop. I tried clearing cache and dalvik Cache and wiped data too. Still a bootloop. Now im trying to flash stock samsung rom ( i got it at sammobile) through Odin 3.09. Ive got the appropriate drivers and everything installed. Only problem is i dont know how im supposed to enable USB debugging when im in a bootloop. If you have any solutions..please let me know.
PS- Its not deodexed nor is the bootloader unlocked. Also, im an adb noob so ill need help with the commands.
Thanks in advance!
You dont need to enable usb debugging or adb. Not sure what makes you think that?
Just install the Samsung USB drivers, put your device in download mode, put the stock firmware in the AP slot of ODIN and hit start.
Not able to install drivers
ashyx said:
You dont need to enable usb debugging or adb. Not sure what makes you think that?
Just install the Samsung USB drivers, put your device in download mode, put the stock firmware in the AP slot of ODIN and hit start.
Click to expand...
Click to collapse
No the point is that I tried installing the drivers but it said installation failed, please connect device to computer to install successfully. And when i connected my device to the computer, since the drivers werent installed it couldnt recog it. and also, i dont really know much about drivers for samsung. i just downloaded smt i found off google called USB DRIVER FOR SAMSUNG auto installer. Im using a HP laptop, with a intel i5 process, windows 7, radeon graphics card. Thanks
Just download drivers from Samsung website all they do is enable your laptop to communicate with the tab......then download a older version of Oden and a rom that matches your device from update.com there you will also find a how to gide.
I have an old Samsung Galaxy Nexus which I rooted and loaded with CWM V6.0.5.1 and an earlier version of Cyanogen some years back. I'd like to replace the old CWM with the latest TWRP and then load LineageOS to give the phone a new lease of life. The process of swapping Recoveries I found on the net involves using 'Platform Tools' including adb.exe, fastboot.exe etc etc. Adb can see the phone and act on it but Fastboot cannot. The problem seems to be that when I put the phone into Fastboot Mode it is recognised by Win10 Device Manager as a new device called "Android 1" but the driver for this new device is not loaded. I think this missing Android USB driver is the problem. Win10 cannot find the driver on line.
The procedure I was trying to follow said that you could find this driver by installing Android Studio and going through some steps with SDK Manager. I cannot get Android Studio to install properly. It seems to install and then starts downloading additional components but never finishes. There is discussion of this problem in other forums.
Does anyone have a link to the Android USB driver I am missing (which will allow fastboot to detect the phone)? Is there a simpler way to swap CWM for TWRP? Thanks for any assistance.
erich_vogt said:
I have an old Samsung Galaxy Nexus which I rooted and loaded with CWM V6.0.5.1 and an earlier version of Cyanogen some years back. I'd like to replace the old CWM with the latest TWRP and then load LineageOS to give the phone a new lease of life. The process of swapping Recoveries I found on the net involves using 'Platform Tools' including adb.exe, fastboot.exe etc etc. Adb can see the phone and act on it but Fastboot cannot. The problem seems to be that when I put the phone into Fastboot Mode it is recognised by Win10 Device Manager as a new device called "Android 1" but the driver for this new device is not loaded. I think this missing Android USB driver is the problem. Win10 cannot find the driver on line.
The procedure I was trying to follow said that you could find this driver by installing Android Studio and going through some steps with SDK Manager. I cannot get Android Studio to install properly. It seems to install and then starts downloading additional components but never finishes. There is discussion of this problem in other forums.
Does anyone have a link to the Android USB driver I am missing (which will allow fastboot to detect the phone)? Is there a simpler way to swap CWM for TWRP? Thanks for any assistance.
Click to expand...
Click to collapse
I used Odin and TWRP in a .tar file. This seemed to work ok but on rebooting the phone now gets stuck on the Google logo. I assume it is a boot loop. The solution to this according to various threads is to either re-flash a stock image or to flash with a custom ROM. I'll try the latter.
I don't think this is going to work. Odin requires .tar, .bin or .tar.md5 files and all the ROMs I can see are in .zip format. Anyone got any ideas?
erich_vogt said:
I don't think this is going to work. Odin requires .tar, .bin or .tar.md5 files and all the ROMs I can see are in .zip format. Anyone got any ideas?
Click to expand...
Click to collapse
I found some stock ROMs for the G-I9520 that were in .tar format and installed one using Odin. This seemed to work fine. I have to use Odin because the phone appears to be soft-bricked in that neither adb nor fastboot can detect it. Then I used Wugfresh's very excellent Nexus Tool Kit to try to sort out the driver issue, unlock, root and install TWRP. Again this all seemed to go fine. I how have a rooted stock G-I9250 and can boot into TWRP.
In Windows 10 Wugfresh's driver tool appeared to be saying that standard drivers included in his tool would not work properly and that it would be necessary to install drivers manually and disable "driver signature enforcement" on Windows 10. This requires booting Windows 10 into trouble shooting mode. Again this appeared to go fine although it was not clear from the choice of drivers that Windows 10 could see exactly which ones I should install. Anyway, I now have no exclamation marks in Device Manager but there are STILL problems.
I think I installed a suitable MTP driver and an adb driver which appear in different parts of Device Manager. The MTP driver says it "requires further installation". The other driver seems OK. The problem now with the phone is that in MTP mode I can see all the default folders in the internal storage but I cannot copy anything into them. Either, I guess, I do not have permission for some reason, or, the MTP driver is at fault and will not actually fully access the internal storage. So I can't download a copy of Lineage 13 onto the phone for TWRP to install. This is probably a common problem but not one I know how to fix. Any help would be appreciated.
erich_vogt said:
I found some stock ROMs for the G-I9520 that were in .tar format and installed one using Odin. This seemed to work fine. I have to use Odin because the phone appears to be soft-bricked in that neither adb nor fastboot can detect it. Then I used Wugfresh's very excellent Nexus Tool Kit to try to sort out the driver issue, unlock, root and install TWRP. Again this all seemed to go fine. I how have a rooted stock G-I9250 and can boot into TWRP.
In Windows 10 Wugfresh's driver tool appeared to be saying that standard drivers included in his tool would not work properly and that it would be necessary to install drivers manually and disable "driver signature enforcement" on Windows 10. This requires booting Windows 10 into trouble shooting mode. Again this appeared to go fine although it was not clear from the choice of drivers that Windows 10 could see exactly which ones I should install. Anyway, I now have no exclamation marks in Device Manager but there are STILL problems.
I think I installed a suitable MTP driver and an adb driver which appear in different parts of Device Manager. The MTP driver says it "requires further installation". The other driver seems OK. The problem now with the phone is that in MTP mode I can see all the default folders in the internal storage but I cannot copy anything into them. Either, I guess, I do not have permission for some reason, or, the MTP driver is at fault and will not actually fully access the internal storage. So I can't download a copy of Lineage 13 onto the phone for TWRP to install. This is probably a common problem but not one I know how to fix. Any help would be appreciated.
Click to expand...
Click to collapse
I went back to Device Manager and changed the MTP driver to the other alternative which now exists in the system. It's called "MTP USB Device" and is a Microsoft driver. This seemed to improve the situation and allowed me to see all of the contents of the folders in the phone's Internal Storage. I discovered by a process of trial and error that now I could copy files into all the folders except the folder called !ReadyToFlash. I believe this folder may have been created by TWRP when it installed. All the other folders are now behaving sensibly. I copied the Lineage 13 zip into the Downloads folder and booted the phone into Recovery Mode. TWRP 3.0.2-0 was able to install Lineage and everything seems to be working correctly although I haven't tested all the functions yet.
I notice that although the radio can see my 5GHz 802.11ac wifi it seems to be unable to connect and can only connect to the 2.4GHz wifi. I don't know if this a hardware limitation arising from the original modem or a software limitation of the Lineage modem driver. This thread, although it's just me, might give another noob attempting to reconfigure their old Galaxy Nexus a few pointers.