My Nexus S Stuck in X screen and really want to recover all the data from the device before restoring it,
I successfully installed the driver in the computer, and I can access the Recovery mode of the Device.
While I am running adb pull command in my Pc i am getting the error that no device found, this is because my Debugging mode is Off and there is no way to enable it since i cannot access y phone.
I can only access Fastboo commands like
fastboot devices
fastboot reboot
etc...
but none of the adb commands are accessible,
I want to know how can i access adb to backup my data from the mobile phone ?
I desperately want to backup all the images from the Gallery of my phone and really dont care about loosing other data.
is there any alternative way to recover images , or is there anyway to recover it using fast boot.
Yeah... You have a Nexus S and this is the Galaxy Nexus forum, dude.
Whatever, you should be able to access your custom recovery (CWM/TWRP) and access ADB from there, without having USB Debugging enabled.
Sent from Samsung Galaxy Nexus @ CM11
Related
i wiped my cache partition on my gnex in cwm... which then got me into a bootloop. now whenever i hit recovery it goes to twrp and i accidently wiped my system on it. now it cant connect to the computer, my nexus rootkit doesnt detect an adb device and i do not have a backup or rom on my sdcard. my fastboot is working and whenever i boot it normally it is stuck at the google screen with an unlocked bootloader symbol. PLS HELP! thx in advance.
use the adb sideload option in twrp to put a rom into your storage via adb, so you can flash it. dont use the toolkit, use adb from your computer. the command is shown on the screen when you enable the adb sideload option.
Hi XDA,
So I got an Xperia PLAY just the other day. Despite its age, since its capable of running a PS emulator, given the built in controller, I think its rad.
Anyhow, went to install CM10 on it and I screwed up big time.
I actually copied the update.zip file over in USB storage mode instead of adb pushing it.
Phone is now stuck in boot loop.
Here's where I'm at:
-I CAN still access both bootloader and CWRM (I used bootloader to copy the boot.img across)
-I CAN'T get the phone to communicated with adb (no adb device shows up in device manager or "adb devices", the only thing I can see is "MTP Device" which I figure is the problem)
-I CAN'T switch it out of MTP mode (if this is even the issue) as CWRM doesn't offer that option
I have tried:
-Both with and without PC companion to get it to communicate with ADB
-The universal ADB driver.
-I have tried the PC companion "phone repair" but it refuses to help me as it realises I have modified the KERNAL.
Question is:
- Is there anything I can do to copy an update.zip ROM across. A way to make ADB work or any solution other than ADB?
- Am I right in assuming ADB is not working because its set to MTP mode?
Much thanks in advance!
Did you flashed kernel (boot.img file that you extract from zip file)?
What was your previous kernel/rom?
TehKame said:
Hi XDA,
So I got an Xperia PLAY just the other day. Despite its age, since its capable of running a PS emulator, given the built in controller, I think its rad.
Anyhow, went to install CM10 on it and I screwed up big time.
I actually copied the update.zip file over in USB storage mode instead of adb pushing it.
Phone is now stuck in boot loop.
Here's where I'm at:
-I CAN still access both bootloader and CWRM (I used bootloader to copy the boot.img across)
-I CAN'T get the phone to communicated with adb (no adb device shows up in device manager or "adb devices", the only thing I can see is "MTP Device" which I figure is the problem)
-I CAN'T switch it out of MTP mode (if this is even the issue) as CWRM doesn't offer that option
I have tried:
-Both with and without PC companion to get it to communicate with ADB
-The universal ADB driver.
-I have tried the PC companion "phone repair" but it refuses to help me as it realises I have modified the KERNAL.
Question is:
- Is there anything I can do to copy an update.zip ROM across. A way to make ADB work or any solution other than ADB?
- Am I right in assuming ADB is not working because its set to MTP mode?
Much thanks in advance!
Click to expand...
Click to collapse
Go into cwm. Go to mounts and storage. Connect phone to pc and mount the sd and you should be able to connect to adb while in cwm. Copy a rom over and flash or if it was the biktloader and kernel and all that do as per usual
Sent from my R800x using XDA Free mobile app
TehKame said:
Hi XDA,
Flash ftf in flashtool .. go back to rooted Stock !! and carry on from their onwards.
Click to expand...
Click to collapse
I everyone,
I need your help, I tried to install a new rom (AICP : this one) , and somehow forgot to do a backup.
When I boot I only get the swirling logo, never get to fully load.
The phone is not bricked, I can still access the bootloader / fastboot and my recovery, so I could simply flash another rom... but I can't figure how to get the zip file on the /sdcard.
I can't use adb sideload or push, I have HTC sync and android sdk installed, I have no problem to use fastboot commands, so I guess I don't have any driver problem, but adb devices never shows my phone (Tried while off, booted on bootloader, on fastboot, and on recovery, never shows up when I try adb devices)
On windows I get a driver error when plugging my phone while in recovery, but I don't find how to install it.
So... is there a way to mount the /sdcard/ as an external drive in windows or ubuntu ? Or do you have a workaround for adb ?
Thanks a lot !
Vincent
I have a nexus 7 WIFI 2013 (Razor, Flo):
I was trying to get a copy of Nethunter or Kali linux installed on here. I was running CyanogenMod nightly's
Well during one install, I must of wiped the whole tablet clean. It only had dad/media and then subs /0, /obb folders. I'm unable to find any images on the card and nothing else is displayed. I have tried number numerous drivers for my Samsung laptop but when i use my surface it shows nexus 7 and also when i go into bootloader mode it will also show the driver.
I installed droid SDK and also minimal adb and fast boot. I'm unable to push anything to this device. When i run adb devices it shows the device but says unauthorized. I try adb kill-server and adb start-server and still no dice.
I'm looking for any input as to how I can push and image onto this device. I realize I will have to go back to factory and I have all them images. I just cant get it adb authorized yet.
this will only go into recovery mode and boot loader mode. There is no OS if I let it boot it just shows the mod logo and will sit there until the battery dies.
Does anyone have any input on how to get this authorized so I can push files to it. I'm unable to get on the screen and ok the RSA fingerprint and I think that maybe part of my hold up or why it shows unauthorized.
Thanks in advance for all or any input or ideas.
Start TWRP and it will authorize you to push any files anywhere.
I'm unable to get TWRP on this tablet. The main issue is I only have cyodgen mod recovery on the tablet. It will not boot. It will only go into recovery mode/bootloader mode. I'm unable to verify any RSA fingerprints which is causing me an issue getting the tablet authorized for ADB pushes. Does anyone know a way I can get it authorized via ADB without being able to access anything other then recovery mode? I think the RSA fingerprint is whats actually causing me an issue.
cletisvandamm said:
I'm unable to get TWRP on this tablet.
....
I think the RSA fingerprint is whats actually causing me an issue.
Click to expand...
Click to collapse
No need to flash TWRP - just start it directly from RAM:
download twrp-3.0.2-0-flo.img to your folder with fastboot and adb apps
boot the Nexus in fastboot mode (when off press power+vol.dn), connect it to your PC
on PC run: fastboot boot twrp-3.0.2-0-flo.img
when TWRP is up, ADB-push your files, no RSA concerns
Hate to start a new thread, but I don't see what I am running into .
My Nexus 5x is unable to boot past the animation (normally it would ask for my pattern, then boot into the system). I can access the bootloader and I can access TWRP.
But when I try adb commands like adb devices I get no response.
I just use this to sideload the new OTA from google which worked just fine so I know the sdk is setup correctly on this computer (rebooted etc).
With access to the bootloader and even TRWP (3.0.2-2) any clue as to where to go from here?
If I try to use adb sideload in advanced in TWRP, I can't talk to the phone (fastboot command fail)...
Phone Bootloader is: BHZ11g
The version of Nexus should be NRD91N 7.0
Seems I have some access on my phone, but cannot send commands to it via computer.
**Update** while at the bootloader (fastboot mode) I can see response when I use
fastboot devices
00b14a7d39589285 fastboot
Okay, I was able to recover from this by sideloading again the new OTA from google. The phone then rebooted but was wiped.
Will work from there