Dear experts,
The screen of my HOX (rooted, running on Venom ViperX rom) is broken and before sending it in for repair, I want to pull all my data from the phone and wipe it. Unfortunatelly, I am totally blind on the phone, as the screen does not work at all and also the digitizer is not working, so I even cannot try by guessing to unlock my lock pattern to get an adb connection. On top of that, flight mode is activated so I cannot use my remote access apps. So all I have are the hardware keys. But the phone is working principally because it still sounds the alarm clock and calendar notifications. I think my only chance is to esablish an adb connection somehow. Is there a way to establish an adb connection in the bootloader somehow? If so, you would have to tell me exactly which keys to press as the screen is black.
Thanks.
blaukraut said:
Dear experts,
The screen of my HOX (rooted, running on Venom ViperX rom) is broken and before sending it in for repair, I want to pull all my data from the phone and wipe it. Unfortunatelly, I am totally blind on the phone, as the screen does not work at all and also the digitizer is not working, so I even cannot try by guessing to unlock my lock pattern to get an adb connection. On top of that, flight mode is activated so I cannot use my remote access apps. So all I have are the hardware keys. But the phone is working principally because it still sounds the alarm clock and calendar notifications. I think my only chance is to esablish an adb connection somehow. Is there a way to establish an adb connection in the bootloader somehow? If so, you would have to tell me exactly which keys to press as the screen is black.
Thanks.
Click to expand...
Click to collapse
well, are data stored on sdcard?
not only. but why does this matter?
i just need adb connection. i have read that there is a possiblitiy to establish adb connection on bootloader via fastboot. is this true?
blaukraut said:
not only. but why does this matter?
i just need adb connection. i have read that there is a possiblitiy to establish adb connection on bootloader via fastboot. is this true?
Click to expand...
Click to collapse
Try it, volume down and power.
Adb devices.
I know you can from recovery, but I believe you have to press "adb side load"
Sent from my One X using xda app-developers app
blaukraut said:
not only. but why does this matter?
Click to expand...
Click to collapse
because if you flash a recovery like Philz and move inside it using buttons and orienting via screenshots you'll be able to save at least data n sdcard... i don't think that adb will vork on bootloader, and, as treebill said before, to enable it in recovery you need adb sideload, so you have to touch the screen...
Related
My friend's phone is pretty screwed. None of the buttons are working and the phone only loads into bootloader. I cant select any of the options in the bootloader because the buttons arent functioning. Is there anyway I can load it in adb and reboot it or something?
Try hooking it up to your comp. and try sdk see if it does anything.
Sent from my T-Mobile myTouch 3G Slide using XDA App
I'm having the same problem what do you mean "hook it up to sdk"?
Thx
http://www.youtube.com/watch?v=z-jRRaBRakg
If you have sdk installed on PC already try using adb is what he meant
Sent from my fingertips using Android.
Can anyone go more in-depth on how to use adb?
Having the same issue, not sure you can access ADB without having your phone in usb debugging I thought? I could be wrong. Does anyone know the commands that would be used with to reset the phone with ADB to stock default? I can't use the volume buttons there for when it ask me to press volume down to accept reset I can't do it. Its funny. I may just take the phone apart and see if dirt is in the way of the connection on the volume rocker.
how get in h boot else
as side button because volume button NOT work
hang boot logo from costum firm
any way from desktop
Try using this command in adb: adb reboot bootloader
Source: 1 minute with Google. Seriously. Google exists. Use it.
pls adb close everytime fastly?
abumaha said:
pls adb close everytime fastly?
Click to expand...
Click to collapse
pls help here don´t get it have video pls
Do this: Copy the location of you adb.exe
Open up command prompt
cd [location]
adb reboot bootloader
You need to access the adb via the command prompt, not just open it.
look pls my cmd
where can´t find it
pls can help team viewer
you are not doing it right. once you have downloaded the android skd you need to open the file and go all the way to \Android\android-sdk\platform-tools. then go to the top of the page in the toolbar, and copy the address. then go to the command prompt and the type cd (followed by the location you have just copied) then type adb shell
then type adb reboot bootloader. that should do it.
or! just use this app allowing you have root
https://market.android.com/details?...NvbS5zaXJpdXNhcHBsaWNhdGlvbnMucXVpY2tib290Il0.
hit the thanks button if i helped
problem is cant start phone and can´t get via side button in recovery
device can not found?
hang in bootlogo
problem is phone can´t be detect
simply how can erase all of it
side button not work cant start phone !
abumaha said:
problem is cant start phone and can´t get via side button in recovery
device can not found?
hang in bootlogo
Click to expand...
Click to collapse
this might not end well. has the hardware method ever worked for you? because if adb doesnt recognise the device your stuffed i think :/ are you s-off and stuff?
100% worked before i used with 3 costum rom via rom manager
but last was this **** rom icyfire hang on android logo always
now phone is off red light is on charge but not connecte to desktop
Sounds more like offmode charging bug to me, pop out the battery then replace and try to power on the phone. If it works go back to recovery and flash a new rom or a backup.
Then post here if it works and someone will help you fix it.
Sent from my HTC Wildfire using xda premium
yes think so
no connect to desktop
else i would flash with official ruu like before
i tried like u say but like i showed u hang on boot or just in off bug charge
when i take out batterie wait one moment then back batterie it starts
u see htc logo after u see again android logo hanging all the time
i think theres no way else only via jtag right
Take out the battery then replace, don't power on the phone normally, use volume down and power to get into hboot. If that still won't work your only choice is to use adb to enter recovery,
Do you know how to use adb?
Sent from my HTC Wildfire using xda premium
pls read thereads before cän´t go in recovery
my side button not work damaged!
allready used adb but no connect to desktop
only one sound hear but not else
First, I did read the thread that's why I thought I'd chip in and try to help.
Second, your english isn't too clear so what you're saying doesn't make much sense.
Third, if you have adb setup correctly all you need to do is connect the phone to pc, open a command prompt and type adb reboot recovery then wipe everything in recovery and flash a new Rom or restore a backup..
But if my help is not wanted take your ass over to eBay and buy a new volume button and sort it out yourself.
Sent from my HTC Wildfire using xda premium
abumaha said:
allready used adb but no connect to desktop
Click to expand...
Click to collapse
That's how you use ADB (Per your Screenshot)? Well done. Hopefully this gives you a lesson to not flash stuff randomly in the future and research before messing with your phone.
Anyway, cant help much apart from the battery pull method which Scratch described because applying any working fix WILL need you to boot ATLEAST into HBOOT, if not Recovery. So, if your battery fix doesn't work, get the volume button fixed, then you can be in a position to get it back to life. (Else, JTAG, as you said)
are you sure your side button doesnt work?
sometimes it takes my phone a little time to get into hboot it just depends where you are pressing on the side button... also try holding the side button down first and then just tap the power button
before you say my side button doesnt work at least try it
Ok, a friend of mine dropped my Epic 4G Touch and cracked the screen. Screen is totally black and as far as i can tell, the touch interface doesnt work. The phone turns on fine and i can hear it boot up and receive email, etc, but i cant figure out how to access its internal memory. I know that you have to turn on storage mode to get the usb mount option to work and i have adb installed on my mac, but it never sees the device. I was told I could start the phone in recovery mode by holding the volume up button, then hitting the power button, but it doesnt seem to make a difference and it just boots regularly. Am i missing something? Is there even a recovery mode with the stock firmware/rom from Sprint?
Any help is appreciated. Thanks!
If it is already rooted and usb debugging is enabled. You should be able to use program such as Android Commander to pull the files from the phone. Another option is to odin into an ICS rom, I believe on those MTP is enabled by default on ICS builds and the phone should mount as a drive immediately when you plug it in. It should be possible to odin with just using the power and volume keys.
As i mentioned, its stock, so its not rooted and its using gingerbread since ICS isnt out from Sprint yet for it (not OTA at least). What does ODIN mean? Am i doing the keys wrong to get into recovery mode? I mentioned the method with the volume up key and power and not getting anywhere with that. Did you actually read my entire post?
First off, wrong section but anyways there is a recovery mode when running stock which you can access by 1. Turn off phone 2. Hold volume up and power button at the same time probably for about 5-10 seconds.
Sent from my SPH-D710 using Tapatalk
Woo hoo! Thanks! Guess i just wasnt holding both buttons down long enough. Did a 10 second count and let go. Then waited about 10 seconds and plugged in usb. Then ran "adb devices" and it showed my device. Then i simply ran "adb pull / phonebackup/" and now I have all my files. Thanks again!
MACscr said:
Woo hoo! Thanks! Guess i just wasnt holding both buttons down long enough. Did a 10 second count and let go. Then waited about 10 seconds and plugged in usb. Then ran "adb devices" and it showed my device. Then i simply ran "adb pull / phonebackup/" and now I have all my files. Thanks again!
Click to expand...
Click to collapse
No problem, glad I could help.
Sent from my SPH-D710 using Tapatalk
Shoot, so i guess i cant access the /data folder when in recovery mode? Thats pretty much the most important section as far as i know as that contains text messages and call logs, etc. hmmm. Any suggestions? Is it possible to root the phone from just adb while in recovery mode?
This is what i gest for not having my backup app setup on my phone. I installed, it, just never set it up. Doh!
MACscr said:
Shoot, so i guess i cant access the /data folder when in recovery mode? Thats pretty much the most important section as far as i know as that contains text messages and call logs, etc. hmmm. Any suggestions? Is it possible to root the phone from just adb while in recovery mode?
This is what i gest for not having my backup app setup on my phone. I installed, it, just never set it up. Doh!
Click to expand...
Click to collapse
You probably can using some commands in adb but a bit too much for what I know. I'd suggest going to the e4gt irc channel. Go to webchat.freenode.net channel is #ics-dev-e4gt hopefully a dev is in the channel and can help you out or someone can stop by this thread before then.
Edit: try the command "su" then enter and then "adb devices" see if that helps with anything.
Sent from my SPH-D710 using Tapatalk
Simply odin just the el26cwm kernel only that should be enough to allow root commands since it's an rooted "insecure" kernel. It should not touch your data.
Hello smart people. Hoping someone there has an idea for me...
This morning I dropped my GN and killed the screen. The display kinda-sorta works, but the touch sensor is non-op. OK, no problem, I've got in contact with Samsung and they'll fix it for the same price I can buy a replacement lcd/digitizer assembly anywhere I've found. Only problem: They'll be wiping the phone.
90% of what I need on the phone is synced to the cloud in one way or another, so I'm not too worried, but I WOULD very much like to recover some recent video and pictures that haven't been archived yet (daughter's dance recital). Phone is still working, except that it's pin-locked now (company policy) and I can't see the file tree to pull the stuff out.
Then I thought I'd play with the GN Toolkit. Only problem there is I guess I need USB debugging turned on, or something else I need enabled is disabled and I can't twiddle the menus to enable it.
Let's start with the obvious easy question: Any way to sync to the file system without unlocking via the touchscreen?
Failing that, is there any way to unlock/enable whatever I need to use the toolkit to pull the images out of the media directory?
I have a little time before I need to send the phone to Samsung for repair, so I'm willing to mess with this a bit and learn whatever I need to learn, but I'm not sure if what I need to do is even possible.
Thanks.
Can't just plug the phone in to a computer and it appear as a media device? Should be able to just pull the internal data.
Sent from my sprint galaxy nexus
ÜBER™ said:
Can't just plug the phone in to a computer and it appear as a media device? Should be able to just pull the internal data.
Sent from my sprint galaxy nexus
Click to expand...
Click to collapse
If the phone is pin-locked, the file system shows as empty when you connect as a media device (until you unlock it).
Herbie555 said:
If the phone is pin-locked, the file system shows as empty when you connect as a media device (until you unlock it).
Click to expand...
Click to collapse
Sorry wasnt aware of that. If you cant get it unlocked.. and USB debugging isnt enabled... then your outta luck.
You could get an MHL adapter and plug in a mouse, then use that to enter your pin at the lock screen. You could also go into recovery and factory reset, as that shouldn't touch your /sdcard contents.
Is there another way for enable debugging on Nexus?
I guess we can't enable debugging via adb, right?
If you just find a way around to do that, maybe you can use the line "adb pull"
(If you search for "adb commands" on Google you will find a list commands to use on developer.android.com)
Stadsport said:
You could get an MHL adapter and plug in a mouse, then use that to enter your pin at the lock screen. You could also go into recovery and factory reset, as that shouldn't touch your /sdcard contents.
Click to expand...
Click to collapse
If he's on stock then yeah that will delete his internal. If he's on a custom recovery no.
Sent from my sprint galaxy nexus
There's a plug in for the SDK called screencast which let's you use your computer screen a duplicate screen to your Android device. You can select things with your mouse. We used to use it in the early gingerbread days of my old vibrant when recovery was hidden behind the double rainbow
Sent from my Sprint Galaxy Nexus CDMA using xda premium
mnoguti said:
I guess we can't enable debugging via adb, right?
If you just find a way around to do that, maybe you can use the line "adb pull"
(If you search for "adb commands" on Google you will find a list commands to use on developer.android.com)
Click to expand...
Click to collapse
Debugging has to be enabled for ADB to be able to interact with the phone.
Glad I ran across this thread. I have a colleague in the same situation.
Stadsport said:
You could also go into recovery and factory reset, as that shouldn't touch your /sdcard contents.
Click to expand...
Click to collapse
Ahh, this might be a path to victory. Didn't realize I'd be able to do a factory reset and have stuff stay intact. Might be my best approach...
ÜBER™ said:
If he's on stock then yeah that will delete his internal. If he's on a custom recovery no.
Sent from my sprint galaxy nexus
Click to expand...
Click to collapse
Oops, got excited. Yeah, stock ROM. So a factory reset will wipe everything?
Herbie555 said:
Oops, got excited. Yeah, stock ROM. So a factory reset will wipe everything?
Click to expand...
Click to collapse
Yes. And the only way to get anything to work is to have USB debugging enabled. Screen cast only works with adb enabled.
Looks like I might be boned on this one. Thanks much for everyone who had suggestions. Sounds like leaving USB debugging enabled might be a best practice from now on, eh? (Or at least making sure EVERYTHING syncs to the cloud automatically...)
Looking at the google policy manager, I can remotely: Lock the device (duh), Reset the Pin, make it ring, or "Wipe", which I'm guessing is a factory reset. Might try that as a last resort, but I'll remain hopefull.
I'm sure you've tried this - but if you''re on stock you may be able to boot into recovery using voldown + power (or is it volup+voldown + power? Not sure, can't remember). THEN plug it into your machine and see if it shows up in the toolbox as a connected device...
adb should be enabled in recovery. reboot to recovery [power + vol up and down] mount sdcard and then adb pull whatever files.
ipfreelytech said:
adb should be enabled in recovery. reboot to recovery [power + vol up and down] mount sdcard and then adb pull whatever files.
Click to expand...
Click to collapse
Feel like I'm getting closer. I can see enough screen to scroll through to "Recovery Mode" and hit enter. It seems to reboot at that point, but then I can't see enough of the screen to navigate any additional menus. Should I be able to connect at that point?
Herbie555 said:
Feel like I'm getting closer. I can see enough screen to scroll through to "Recovery Mode" and hit enter. It seems to reboot at that point, but then I can't see enough of the screen to navigate any additional menus. Should I be able to connect at that point?
Click to expand...
Click to collapse
Plug it in via USB and see if the Toolkit picks it up...
thepatman said:
Plug it in via USB and see if the Toolkit picks it up...
Click to expand...
Click to collapse
I've apparently managed to get it mounted in the Bootloader interface and in fastboot mode, but can't figure out how to get it into adb mode, which is apparently what I need to do the pull.
The LCD has gotten worse, I have almost no visibility now. If I knew now many down or up strokes to make at each menu stage, I could probably do it blind...
Herbie555 said:
I've apparently managed to get it mounted in the Bootloader interface and in fastboot mode, but can't figure out how to get it into adb mode, which is apparently what I need to do the pull.
The LCD has gotten worse, I have almost no visibility now. If I knew now many down or up strokes to make at each menu stage, I could probably do it blind...
Click to expand...
Click to collapse
Can't do adb in Fastboot mode. While in flastboot mode. Hit the volume up twice and hit the power button. This will boot into recovery. Then try using the
Code:
adb devices
command. If you get a gibberish code next do device ID. Then your good. Go ahead and
Code:
adb pull /sdcard/
Sent from my sprint galaxy nexus
Need a bit of help here..
I have been playing a bit with my Ouya, installed SuperSU etc, everything worked fine, until I decided to reboot it.
Now it won't boot anymore. When I start it, my TV stays black. I only see some white dots and occasional a greenish flash..
What could I do now?
Dropshots said:
Need a bit of help here..
I have been playing a bit with my Ouya, installed SuperSU etc, everything worked fine, until I decided to reboot it.
Now it won't boot anymore. When I start it, my TV stays black. I only see some white dots and occasional a greenish flash..
What could I do now?
Click to expand...
Click to collapse
Same here any help?
Dropshots said:
Need a bit of help here..
I have been playing a bit with my Ouya, installed SuperSU etc, everything worked fine, until I decided to reboot it.
Now it won't boot anymore. When I start it, my TV stays black. I only see some white dots and occasional a greenish flash..
What could I do now?
Click to expand...
Click to collapse
If adb still connects and assuming you have installed CWM and have a backup, just run:
adb reboot recovery
then flash your backup.
deathknight842 said:
If adb still connects and assuming you have installed CWM and have a backup, just run:
adb reboot recovery
then flash your backup.
Click to expand...
Click to collapse
adb does still connects, but did not yet install CWM..
Dropshots said:
adb does still connects, but did not yet install CWM..
Click to expand...
Click to collapse
I found a fix.. http://forums.ouya.tv/discussion/1380/recovery-mode
This is a hack, an unintended sequence of events that results in recovery mode; what you need to do is crash the startup using sysrq.
For this you'll need a usb keyboard with the sysrq key, this is usually the printscreen button if your keyboard isn't labeled. As the OUYA starts to boot, hold down the alt-sysrq keys and press i, wait a few seconds and then repeat. This key combination is kill-all-tasks; thanks to whoever left this enabled in the kernel. Each time you kill the tasks the init process will restart them, after about 5 or 6 times init will print a warning on the console that one of the processes marked critical has been restarted too many times -- this then triggers an automatic reboot into recovery mode.
Unfortunately it's not always obvious when the ouya is in recovery mode. You might get screen with the ouya logo and a large red exclamation mark, or the screen might be entirely black; usually I got a black screen. Press the home button on the keyboard to bring up the recovery menu; it's actually a toggle so feel free to press the home button repeatedly until you see the menu since the timing isn't otherwise obvious.
Once you get to the recovery menu, the select the second option to update from adb. Download the OTA update from the link at the end of this post, and run the command "adb sideload RC-OUYA-1.0.193-r1_ota.zip" this will reformat the system partition and reinstall the ouya software. You might also want to do a factory reset before rebooting.
Links to download the OTA updates can be found on this xda thread: http://forum.xda-developers.com/showthread.php?t=2266629
Click to expand...
Click to collapse
same here... i posted this -> http://forum.xda-developers.com/showthread.php?t=2318169
but the recovery mode from the post above does not work
when i run adb shell it says error: device not found.. so i guess i am F**KED
Maybe a factorycable can get the Ouya into fastboot like the Kindle fire hd?
Sent from my C6603 using xda app-developers app
Dogie52 said:
Same here any help?
Click to expand...
Click to collapse
when you turn it on, with a usb cable plugged in, will it still pop up as a drive?
When I installed SU/busybox/CWM yesterday I noticed that both fastboot and recovery turn up as different devices in windows from the usual ADB one. I forced windows to install the ADB driver for them and it worked fine then.
This thread is three weeks old, I'm sure they figured something out.
Sent from my GT-P3113 using Tapatalk 4 Beta
muppetterror said:
same here... i posted this -> http://forum.xda-developers.com/showthread.php?t=2318169
but the recovery mode from the post above does not work
when i run adb shell it says error: device not found.. so i guess i am F**KED
Click to expand...
Click to collapse
Try to sideload the newest update. When you are in original recovery there is no way to get a web shell. Had the problem to.
I did the web wireless setup and got stuck on black screen after reboot. The I did the sideload and installed the update and everything works fine again.
Sent from my HTC One using xda premium
is this still happening or is it fixed now?
Dogie52 said:
I found a fix.. http://forums.ouya.tv/discussion/1380/recovery-mode
Click to expand...
Click to collapse
This method worked for me. I had some issues with the key sequence at first, but tried it a few times and I was able to get into stock recovery. Once there I had an issue with adb seeing my Ouya, the trick was reinstalling the Google usb drivers using the "I have disk" method in Windows device manager.
I was able to fully flash the latest ota update through adb sideload and got it working.
Now, onto rooting and cwm.
Best of luck!
Sent from my SCH-I535 using Tapatalk 2