Hi...
My Gnex began to reboot randomly after a long rock solid life (always stock rom with ota upgrades + cwm), so I decided was the time to refresh it installing cm11-m5. During adb shell access to cwm I was warned by several buffer io error on /sdcard but was luckily able to pull my existing files and push the cm11 image, and a new cwm (required by cm11) and finally I was able to flash and boot.
Then my intent was to hack a bit with cwm to do an fsck on /sdcard and eventually some check for badblock, mkfs. etc. etc. but the devices is no more recognized in adb (if full booted with usb debug enabled or in cwm). The devices does not charge anymore but... it charges when powered off and it is recognized in fastboot!
I flashed several versions of stock images thinking it was due to the cm/cwm kernel but the problem is still there.
Usb ports and cable on my several linux boxes works fine (as i see another android phone without problems in mtp/adb/fastboot etc.).
Any help will be apreciated.
Niko
Related
T-Mobile Galaxy S3 SGH-T999
Rooted
Latest TWRP recovery
CM 10.2 (Nov 6 nightly- Android 4.3.1)
I am trying to fix the storage issue that the multiple user profiles created when going from Android 4.1 to 4.2, where symlink folders are created and multiple instances of every installed app trick the phone into thinking more storage is being consumed than it actually is.
I found a video (Google: youtube how to fix htc one storage) which is specific to HTC One but figured it would work fine for me.
The video basically tells you to do a full factory wipe from TWRP and then ADB Sideload your ROM of preference.
My issues:
A. I installed Android SDK on my home PC (Windows 7 64-bit) as well as the Android USB drivers. I enabled android debugging and did the kill-server and start-server and can get my PC to recognize my Android phone as an 'authorized device' upon entering 'adb devices' on the command line. However, once I wipe the card in recovery, my device ceases to appear in the cmd line. The list is empty. I need to understand why that happens.
B. Even though I've done a 'factory wipe' in recovery, if I reboot my phone, it goes to the CM setup screen and guides me thru initial phone setup.
Looking for some advice on the above issues. Clearly I'll need for my PC and phone to be able to communicate via ADB sideload first, then I can worry about issue B.
I'm not super experienced at this, but appreciate any help someone could provide. Alternatively, if there's a solution to fix the 4.2 storage issue without a full wipe and clean flash (via ADB), then that would be ideal. I've searched for answers on this specific topic to no avail.
Hi. I currently have root access and had attempted TWRP tethered recovery while on a stock ROM. I can get to the part with the open Android and can select Recovery Mode, but that brings up nothing.
A stupid decision to integrate dalvik with ROM had messed up my system that led me to do a factory reset. That sort of works, though Asus Dialer is sporadic now. I'd ideally want Cyanogenmod 12.1 on it, but at the moment, plugging via USB to multiple systems (Linux and Windows 8) only results in charging (USB debugging is enabled). What options do I have in reflashing either stock or Cyanogenmod, and what apps with easily available apks can I get?
Thank you in advance, I hope not to need a used Moto E as a backup.
does the stock recovery supports OTG? like for installing rom through usb drive
since mine apparently got corrupt because OTA update, and now just having bootloop with dm-verity error
it doesn't get detected to PC at all, volume up holding, fastboot, adb sideload, none even detects in PC (not even new device connected in device manager)
though it might be the usb port itself that's busted (although it still can charge just fine)
but i'd like to know first if the stock recovery supports installing from OTG or not, since OTG would be cheaper if it's possible
Hi so i installed twrp and rooted my pixel with magisk. everything went fine.
saw the sultan kernel decided to flash but my phone does not recognize any computer with any cable as a computer but as a powersource. Adb and fastboot not working on any laptop or desktop (except the desktop on which i unlocked my bootloader and rooted my device) tried to connect over usb (adb fastboot filetransfer) on Linux Windows and MacOs. all unsuccesfull.
dev options is on:
oem unlock toggled
usb debug toggled
phone is running stock rom stock kernel. (Edit: kernel is the sultan kernel on stock rom)
once i connect the phone sees it as a pc pops op usb options then blacks it out because it sees it as a powersource.
whats wrong with it i cant figure it out...
Nightfall41 said:
Hi so i installed twrp and rooted my pixel with magisk. everything went fine.
saw the sultan kernel decided to flash but my phone does not recognize any computer with any cable as a computer but as a powersource. Adb and fastboot not working on any laptop or desktop (except the desktop on which i unlocked my bootloader and rooted my device) tried to connect over usb (adb fastboot filetransfer) on Linux Windows and MacOs. all unsuccesfull.
dev options is on:
oem unlock toggled
usb debug toggled
phone is running stock rom stock kernel.
once i connect the phone sees it as a pc pops op usb options then blacks it out because it sees it as a powersource.
whats wrong with it i cant figure it out...
Click to expand...
Click to collapse
I'm in very much the same situation. I've seen several USB connectivity threads roll through here recently so I'm not sure if anything larger is going on or not. Basically, I always do updates with full factory images w/o wiping. I was able to install the April update (in early April) just fine. I went back in late April to try to use fastboot and couldn't connect via USB for file transfer, ADB, or fastboot. I updated all my platform tools and the Google USB driver which made no difference. I tried on 3-4 Windows 10 desktops/laptops and 1 MacOS laptop. Nothing. I opened a support ticket with Google (and went through extensive troubleshooting steps) which was then escalated. It has been over a week and they have not responded. I even checked back yesterday to make sure it wasn't lost in the shuffle, and I was assured that it was still active and assigned to the proper team.
Just for giggles, I tried connecting to a Win7 desktop w/ only USB 2.0 and the phone immediately connected MTP (we had made this the default USB mode during the troubleshooting process). Since I was still running a modified (root) kernel, I went ahead and tried flashing the stock boot image with fastboot (both slots) and it worked! I figured since I had already wiped the phone for troubleshooting, I would try pushing the entire April image (w/ wipe). It flashed bootloader, radio, and maybe boot image (can't remember), but then lost connectivity when trying to push the system image. Fortunately, the phone booted right back up. Since then, connectivity is possible, but sporadic, on that machine. Being 100% stock, with no other options, I knew the only way to get an entire factory OTA pushed to the phone would be to opt into the beta, install the beta, then opt out, which pushes the latest non-beta and wipes the phone. I did this, but, again, it resolved nothing.
BTW, for me, this issue affects all devices that pass data through the port including USB OTG flash drives and game controllers. It's also not cable specific as I have tried a factory Google USB-A to C cable, factory Google USB-C to C, and several other USB-A to C cables (the ones I always use for ADB and fastboot commands). There does not appear to be any physical damage to the port and I cleaned it extensively with compressed air and a plastic dental pick.
Sorry I don't have a solution at this point, but I wanted to pass on the steps that I have taken.
Hi All, sorry this is a fairly long post.
i recently "Upgraded" my SM-P605 to Android 9 and it has been working fine.
i have, however, been experiencing connectivity issue with file transfer via USB.
i have tried several cables (3 Genuine) including a brand new "Generic" cable and keep getting the "device descriptor request failed" error.
i have also tried multiple PC's, loaded all recommended Samsung drivers and finally relented and replaced the USB port in the tablet itself, which still did not fix the problem.
Convinced after all of this it must be software related, i then decided to re-install and earlier version of Android which i copied over to the Tablets internal memory.
i logged into TWRP and wiped the tablet ready to reinstall Android 7. and when i tried it says the zip file is corrupted.
i now have a tablet that wont load the zip file i have, wont read from an SD card in the tablet or OTG (via TWRP) and is unable to connect to a PC via a usb cable..
if anyone could offer any suggestions i would be extremely grateful as i dont want to "Dump" this tablet as i use it daily for work..
Why it does not read the SD card? I would expect that should work and should be the safest bet here...
-Maybe the zip file really is corrupt, which can be easily told by unpacking via pc.
-If the tablet can still charge the battery usb is most likely okay.
-Sdcards can fail by becoming read-only. Most easy to tell by unsuccessfully trying to format them in the tablet or pc , but e. g. under Windows you seemingly can successfully delete and copy stuff, everything as it should even after forced refresh via F5. But after reinserting the card or rebooting the previous state is back.
-ADB has been enabled in developer settings? Then you normally get a notification where you can modify usb mode. Charge-only won't work, but most of the rest should do (Dcim/mtp/msp...) .
-And all the time Windows has to recognize the device via PnP and auto-install drivers for the current usb mode. Besides the aforementioned storage drivers for flashing and communication a modem driver and virtual COM ports must be auto-installed.
In this department i had lots of trouble with a phone based on an old TI OMAP SoC under any Windows newer than seven. Only Download mode invoked on the phone itself was still working and only zseful to restore stock rom, while in the more flexible Fastboot mode the phone wasn't recognized by Windows.
Samsung devices seem to support Fastboot only, but call it Download mode.
To come to an end, if everything fails i'd recommend to install stock rom in "download recovery" (Fastboot?) mode via Kies. If this also fails try to put the P605 manually into Download mode (Power and Volume minus or plus), no need to press home button, as often advised. After this, work your way back to Twrp, custom rom and root.
@crwzar80
Try connecting the tablet to a Windows 7 PC/laptop, making sure it's on an Administrator account (so it can autoload/download needed stuff). Not Windows 10 or even 8.1, but Windows 7.
I had the same problem a while back ago; if your attempt with this method succeeds then report back; I had an unconfirmed hypothesis about this issue.