Hey there,
I just wanted to update to another ROM and put the .zip file on my device and then rebooted to recovery and wiped my cache etc.
Somehow the .zip file is missing as well now though, I'm not sure why but it seems to have been deleted when I cleared the cache, etc.
Now I'm left without a .zip file to flash and a totally wiped system without a ROM :/
Is there a way to copy data from PC to the Nexus 7 device while in recovery mode? I tried connecting it via USB but it doesn't show up...
edit: Well after a lot of reading it looks like fastboot is the only option for me. Google USB drivers don't seem to be compatible with Windows 8.1 64bit and therefore I cant get my device to show up in "adb devices". Luckily "fastboot devices" works and I guess I'll just try flashing the stock recovery image now.
That's why I have bought an OTG cable (B letter inscribed on the cable, the others I've tried (4 models) without that B, didn't work with my flo, dunno why) and I have an USB strick to get files like zips from my PC. Or get a stick with both micro USB and USB connections.
Related
The USB connector on my SGS seems to have stopped working properly. Charging works fine but data comms doesn't.
When I connect the device to Windows machine (tried vista and win7 32 and 64) I get the "USB Device Not Recognized - One of the USB devices attached to this computer has malfunctioned...". My linux box doesn't see the device either and I have tried Odin + voldown, home power. When I hold the connector cable in place at an angle it sometimes gets to the point where the phone brings up the menu options for mass storage, however as soon as I let it go it disconnects. *Conclusion: bent pin or faulty connector.
So my dilemma, I am currently on a rooted JPC rom, need to send the phone in for RMA, how can I get back to stock rom without USB connectivity? ROM manager fails to install clockwork properly so I am stuck with the stock recovery?
*#1234#
PDA: I9000XXJPC
PHONE: I9000XXJPC
CSC:I9000OXAJPC
Any ideas?
asdthe1 said:
The USB connector on my SGS seems to have stopped working properly. Charging works fine but data comms doesn't.
When I connect the device to Windows machine (tried vista and win7 32 and 64) I get the "USB Device Not Recognized - One of the USB devices attached to this computer has malfunctioned...". My linux box doesn't see the device either and I have tried Odin + voldown, home power. When I hold the connector cable in place at an angle it sometimes gets to the point where the phone brings up the menu options for mass storage, however as soon as I let it go it disconnects. *Conclusion: bent pin or faulty connector.
So my dilemma, I am currently on a rooted JPC rom, need to send the phone in for RMA, how can I get back to stock rom without USB connectivity? ROM manager fails to install clockwork properly so I am stuck with the stock recovery?
*#1234#
PDA: I9000XXJPC
PHONE: I9000XXJPC
CSC:I9000OXAJPC
Any ideas?
Click to expand...
Click to collapse
try removing the existing usb drivers and/or kies, reboot, reinstall drivers
Hi thanks, I have tried on a number of machines. A clean windows 7 install without kies installed. Also when I put the phone into mass storage mode even my linux box doesn't recognize the phone. Have tried new cables as well.
Since you mention cwm, i presume you have a stock cwm image. I also presume you have wifi. In that case:
1) download and install adbwireless from the market.
2) download cwm recovery from here
3) Connect adb on your desktop to adbwireless (start adbwireless, on desktop type adb connect ipaddress:5555 or whatever adbwireless reports as the connection ip)
4) rename the cwm recovery on your desktop to update.zip and push to your sdcard - command is adb push update.zip /sdcard/
5) reboot into 2e - run cwm
6) Restore cwm image that you have of stock
ashwinds said:
Since you mention cwm, i presume you have a stock cwm image. I also presume you have wifi. In that case:
1) download and install adbwireless from the market.
2) download cwm recovery from here
3) Connect adb on your desktop to adbwireless (start adbwireless, on desktop type adb connect ipaddress:5555 or whatever adbwireless reports as the connection ip)
4) rename the cwm recovery on your desktop to update.zip and push to your sdcard - command is adb push update.zip /sdcard/
5) reboot into 2e - run cwm
6) Restore cwm image that you have of stock
Click to expand...
Click to collapse
Thanks, was not aware that one can do adb over wifi. This will help.
Two things, I do not have 2e flashed only stock recovery. this doesn't seem to work on JPC. When I try Clockwork's update.zip from stock recovery I get:
Code:
E: failed to verify whole-file signature
E: signature verification failed
Hmmm dont really know how to switch to 2e from 3e without Odin...will let you know if i find out.
Silly question but?
You use a new usb cable?
Already happened to me
Dont have the details, This maybe of use to you. Once on 2e, you can flash any update.zip - with adbwireless + adb - you should be set.
Having problems with SIM not being read on 4.2.2 CM rom (I bought the phone with said ROM installed). Decided to try to dowgrade to 4.1.1 official Stock rom. Problem is my phone will not be recognized with any USB cables. I have tried 3 cables and will try more (though I know these cables work fine) and will try a different PC tomorrow,.. but this PC is not the problem, I can tell you that.
I have tried installing the drivers provided in the toolkit and the phone is still not recognized. Have also tried installing Kies, and device is still not recognized. Have tried rebooting phone and PC and still not recoginizing. ADB in developer options is enabled.
When I say not recognized, I don't mean that Windows is popping up saying "device not recognized" - my PC is not even finding the device. There is nothing in Devices and Printers, nothing in Device Manager, nothing in My Computer... I also tried doing factory reset / cache wipe / dalvik cache wipe. Still nothing. Is there any way to flash back to stock rom using CWM restore menu via a ZIP? I can drop the file on a microSD card and restore it from there, but I don't know if there is any way to do that from CWM.
I'm totally lost, I have tried everything in the world to get my Nexus 7 2ed gen to get out of a self inflicted boot loop. It all started when I wanted to upgrade it from 4.4.4 to 5.0.2. It was rooted and I have TWRP recovery installed, I wiped the data and chose the wrong thing to do. I instead of a simple wipe, wiped the entire OS and everything.... So now i'm stuck with a rather nice paperweight.... I can boot into recovery (TWRP) and Fastboot. But regardless of what i do I cant get the damn thing to be seen on my computer via ADB or fastboot, so I can't install the stock OS onto it. I've tried re-installing the drivers for The tablet and ADB/fastboot, a countless number of times and nothing works. I've tried it on other computers, that doesn't work, and from how I see it It should.... Anyone out there know what I did to screw this up and how to fix it?
Get an OTG cable and load a ROM onto a flash drive. Then flash the ROM and your choice of gapps.
Sent from my LG-D850 using XDA Free mobile app
^That would be the easiest but still why would fastboot not work?
If adb can't see it in twrp or fastboot on the bootloader screen it's gotta be a driver or connection issue right?
You've probably done it but try different cables/make sure the usb ports are clean.
I'm guessing you flashed twrp with fastboot and know how to use fastboot. If not make sure you're in the fastboot directory before typing the commands in the command prompt.
Only thing left that you already tried is reinstalling everything. Uninstall any fastboot/adb/drivers anything related to android really.
Install the sdk. Install the google usb driver from the sdk manage in the sdk folder.
Boot the tablet to the bootloader screen and plug it in, driver should install automatically. Open a command prompt in the platform-tools folder in the sdk folder and type fastboot devices.
If that doesn't work I have no idea. Oh you could try reinstalling java.
Ok I went ahead and ordered an OTG cable. I also tried installing all the drivers and such another time, but this time when I plugged it in, while it was in bootloader mode, the driver didn't install? I tried several cords, could it be that the tablets port itself is the issue?
Dug my old 2013 wifi 7 out to use on a project. Running a stock ROM, not sure of the version, rooted and unlocked bootloader. I screwed up something installing a new ROM and ended up wiping the system and data partitions. I'm trying to get a ROM onto the device so I can flash it. I can boot into fastboot and TWRP 2.8.6.0. Of course with no system it showed up as an unknown device. While doing the driver uninstall/install dance trying to get the naked driver set to work the tablet just stopped showing as connected to my windows 10 pc. Not like "unknown device" etc, no devices connected at all. Nothing shows on usbdview either. Tried plugging into a windows 7 pc, same thing, even tried a ubuntu live cd boot, nothing. Tried toggling MPT in TWRP on all these attempts. I can't mount USB OTG from TWRP I think its too old of a version. The tablet will charge so I don't think the usb port died. I'm out of ideas. Any suggestions before throwing in the towel?
Get the stable ROM for Flo. Stick Ubuntu on a decent laptop. Get a USB cable that's good for data and look at this instruction: https://itsfoss.com/restore-android-factory-nexus-7-2013-linux/
You want to Root look at this one and follow exactly: https://itsfoss.com/root-nexus-7-2013-ubuntu-linux/
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.