Well, I've had this phone for a good 3 years, and a few weeks ago it fell out of my pocket and shattered the screen.
Yesterday I've managed to connect to it through adb, although most of the commands weren't working, just kept getting
Code:
/sbin/sh: su: not found
Today, however, I can't seem to connect to it, just keep getting "error:device offline"
So, I thought I'd update my SDK, turns out the one I was using was from 2012.
Updated, but the problem now is this:
Code:
error: device unauthorized. Please check the confirmation dialog on your device.
Of course, as it's a different adb instance, never been authorized. But, as I said, the screen and digitizer are both dead, so no chance of checking that confirmation dialog.
This new adb still works in recovery, so I've already pulled all my files through there.
Now, the challenge is to find a way to bypass this confirmation dialog without access to screen or adb. Then get screencast working. Or this thing:adbcontrol Maybe somehow fix the problem with the old adb and use that to enable the newer one. But better without it. Main reason of doing this is as a learning experience and fun, but also so I can go into an app and get some data out of there (a note app), but that's of secondary importance.
I'm pretty sure USB debugging is enabled, or was last night (maybe that's the reason it stopped working today? Somehow got disabled?)
Phone is rooted, running latest version of SlimKat.
I've been googling for a while now, no leads yet. Anyone got any ideas?
Related
My moto droid's screen died. I have the common right 1/3 sreen dead problem. Because of this I can not open the lock screen. The phone has since been deactivated, so i can do what ever I want with it.
I want to root it so I can use screencast 0.4 to view it to make sure I got everything off it. I can't root it because I do not have USB debugging enabled. I can not enable debugging because I can not get past the unlock screen. But I can not use screencast because it is not rooted. So I am in a pickle. I have read a lot of XDA forums and others and still have not found a solution to remotely view my phone, at least that I can find.
I have Android Developer installed on my PC and I have played with it a little. I am trying to learn more everyday.
I also know that the adb needs to be running, and I have yet to figure out if it is running or not. I have also read that you need to stop and restart adb before screencast will operate properly.
So with all that info, does anyone have suggestions how I can view my phone and interact with it to make sure I know what all my programs were and save any data that are program related.
I have searched for keyboard unlock codes to no success. I also know that my android market library tells me most of what is installed.
So any suggestions??
Darshan
(Win 7 x64, HTC Thunderbolt, 2.2.1)
First of all what did u do to it? Spilled water, dropped it, installed something what?
Nothing!
Absolutely nothing.
I downloaded the lastest update, and about a week later the screen behaved very erratic. 2 weeks later I lost the right 3rd of the screen (touch only, not image) Could still get in by opening keyboard, then swiping the lock. 2 weeks later the swipe no longer works, keyboard open or closed.
This loss of touch response is very common. I have read about several other people with the same problem. It has nothing to do with any updates, as I have read about someone with this problem over a year ago. It has to be electrical. As an engineer, I have inferred that the touch screen has 3 circuits for 3 zones on the screen. 1 circuit must have gone belly up. So my right third does not respond.
Also most victums report erratic screen behavior just prior to loosing some of the screen.
So that is what I know.
D
Hi,
I dropped my phone on the corner and the LCD broke and leaked through the screen. As a result the phone works, but the screen is dead.
I was able to check ADB USB in dev tools prior to the screen leaking through.
Is there any computer way to access and copy over the sms to another droid turbo, or does it make more sense to just replace the screen? The phone is currently turned off, has a pattern lock screen (since digitizer works, i can technically unlock the phone - i think )
Thanks,
Chris
you should be able to make a backup of the entire phone using ADB, But I don't know the exact steps to do it. Ive seen it done on nexus devices
use this
https://play.google.com/store/apps/details?id=com.riteshsahu.SMSBackupRestore&hl=en
I used it to migrate all my messages from my old phone to the new one and it worked good
it was the pro version though
£ngland said:
use this
https://play.google.com/store/apps/details?id=com.riteshsahu.SMSBackupRestore&hl=en
I used it to migrate all my messages from my old phone to the new one and it worked good
it was the pro version though
Click to expand...
Click to collapse
That may be difficult to use with a dead screen.
As for using adb, there's an issue. Although you enabled adb, a confirmation screen will still pop up on your phone the first time you use it. So if you've never used it before, you'll still need to accept that confirmation screen, which is a problem. I'm pretty sure that sms messages are stored in /data/data/com.android.providers.telephony/databases/mmssms.db and /data/data/com.android.providers.telephony/databases/mmssms.db-journal. I'm running RR, so I'm not sure if this is the correct location on the stock rom, but I think it's pretty standardized. If you can get adb working, I think the correct commands would be the following:
adb pull /data/data/com.android.providers.telephony/databases/mmssms.db <path to where you want it to show up on your PC>
adb pull /data/data/com.android.providers.telephony/databases/mmssms.db-journal <path to where you want it to show up on your PC>
There's also a chance that you might need to be rooted to do this, but I think you should be okay. Good luck.
my thought is running it on 2 devices at same time sa to know where to click
Chris
So long story short my Nexus 6 got ran over by a car (maybe multiple...) screen is shattered into a million pieces and completely black. I'm just hoping to try and recover my pictures off of the phone. I am able to boot into the bootloader by holding down the volume/power buttons and my computer will recognize it fine, and everything seems to work from there. TWRP seems to flash successfully but when I try to boot into it weird things happen. Basically if left alone I will hear my computer keep chiming that my phone is connecting in adb mode, then losing connection, and cycling like this every 15 seconds or so. The adb devices command usually lists the the device as attached, but sometimes with the "offline" or "unauthorized" tag. In addition to this, any commands like adb pull or adb shell give me "error: protocol fault (couldn't read status): No error".
Again, the phone will be stable in fastboot, but keep dropping and reconnecting in adb.
Earlier today I was brainstorming how I was gonna hack the NAND chip out of the phone, but was delighted when I got home from work and it actually connected through fastboot. Now just hoping I can actually recover my data. Any ideas?
Never set Google to back up photos?
Sent from my Nexus 6 using XDA Free mobile app
leetonion said:
So long story short my Nexus 6 got ran over by a car (maybe multiple...) screen is shattered into a million pieces and completely black. I'm just hoping to try and recover my pictures off of the phone. I am able to boot into the bootloader by holding down the volume/power buttons and my computer will recognize it fine, and everything seems to work from there. TWRP seems to flash successfully but when I try to boot into it weird things happen. Basically if left alone I will hear my computer keep chiming that my phone is connecting in adb mode, then losing connection, and cycling like this every 15 seconds or so. The adb devices command usually lists the the device as attached, but sometimes with the "offline" or "unauthorized" tag. In addition to this, any commands like adb pull or adb shell give me "error: protocol fault (couldn't read status): No error".
Again, the phone will be stable in fastboot, but keep dropping and reconnecting in adb.
Earlier today I was brainstorming how I was gonna hack the NAND chip out of the phone, but was delighted when I got home from work and it actually connected through fastboot. Now just hoping I can actually recover my data. Any ideas?
Click to expand...
Click to collapse
first off, fastboot only connects to the device in the bootloader mode. ADB NEVER EVER connects to the device when in the bootloader. that sound you are probably hearing isnt "adb" connecting, but just the sound you hear when you connect to the computer.
I know, just didn't word it right. The chime from my computer is just it recognizing the phone, but it coincides with adb losing connection and (I'm assuming) my phone crashing or rebooting somehow...I just need some way to pull files from the sdcard folder and adb doesn't seem to work in my current situation.
If you are lucky and the mobile boot into system then try this http://www.vysor.io/
Sent from my Nexus 6 using Tapatalk
AhmadOkda said:
If you are lucky and the mobile boot into system then try this http://www.vysor.io/
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Interesting app ya linked to, but wouldn't he need to be able to install the app on the device before he would be able to see it on his desktop? Just asking because it said available on Google Play.
Sent from my Nexus 6 using XDA Free mobile app
leetonion said:
So long story short my Nexus 6 got ran over by a car (maybe multiple...) screen is shattered into a million pieces and completely black. I'm just hoping to try and recover my pictures off of the phone. I am able to boot into the bootloader by holding down the volume/power buttons and my computer will recognize it fine, and everything seems to work from there. TWRP seems to flash successfully but when I try to boot into it weird things happen. Basically if left alone I will hear my computer keep chiming that my phone is connecting in adb mode, then losing connection, and cycling like this every 15 seconds or so. The adb devices command usually lists the the device as attached, but sometimes with the "offline" or "unauthorized" tag. In addition to this, any commands like adb pull or adb shell give me "error: protocol fault (couldn't read status): No error".
Again, the phone will be stable in fastboot, but keep dropping and reconnecting in adb.
Earlier today I was brainstorming how I was gonna hack the NAND chip out of the phone, but was delighted when I got home from work and it actually connected through fastboot. Now just hoping I can actually recover my data. Any ideas?
Click to expand...
Click to collapse
Does your Nexus have root access?
31ken31 said:
Interesting app ya linked to, but wouldn't he need to be able to install the app on the device before he would be able to see it on his desktop? Just asking because it said available on Google Play.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I tested dot on my mobile
You only need usb debugging enabled and it will install itself with no action from my side
Sent from my Nexus 6 using Tapatalk
You can do adb commands in recovery. if you can get into recovery you should be good to go.
Miss read OP. Thought you were trying to boot normal and not boot into recovery.
leetonion said:
I know, just didn't word it right. The chime from my computer is just it recognizing the phone, but it coincides with adb losing connection and (I'm assuming) my phone crashing or rebooting somehow...I just need some way to pull files from the sdcard folder and adb doesn't seem to work in my current situation.
Click to expand...
Click to collapse
To help troubleshoot, try holding down power when you think it has booted to feel for a vibration. If it vibrates you know it booted. From there you may need to enter a password through adb (there are guides, I can't remember of f the top of my head how). Once you are in, you can use this to help navigate your phone http://forum.xda-developers.com/showthread.php?t=2786395. There's a learning curve and high latency but, it works. I have been in a similar situation and I was able to pull it off using this method.
As far as it rebooting or crashing, or whatever else, there's not much I can do to help with that across the internet, good luck to you.
And one last thing, try playing with this. http://www.pocketables.com/2014/10/using-twrps-new-adb-interface.html Looks like you can control TWRP through a command prompt, maybe you can get your files.
And one last, last thing. When in the bootloader menu, the options go like this. You cna also get into these optiosn through fastboot but, I figured it couldn't hurt.
START <--- First option you boot into. If you are holding it's possible to go down one extra though, be careful.
RESTART BOOTLOADER
RECOVERY MODE
POWER OFF
FACTORY MODE
BARCODES
BP TOOLS
QCOM
BOOTLOADER LOGS
Ok ladies and gents,
I've been on a mission to root my Note 5 N920I for months now.
My problem is no computer will read/recognise the device. The Mac's seem to not even recognise it's plugged in, with Windows, no matter which driver I install it keeps telling me the "device descriptor failed blah blah blah". I managed to root my S4 very easily on Mac with Jodin3 so I know that it ain't no user error.
I've Googled and Googled ways to root without a computer or installing a custom recovery without root, but from what I understand I can't flash TWRP as recovery without a computer and therefore cannot root without a custom recovery.
I've Googled ways to fix the USB issue by making the xml file and putting it into the correct folder, but for that I need to be rooted. Right?
When she's plugged into a computer with USB debugging on or off nothing comes up in my notifications except for charging. I tried using the toolbox which I found on here (sorry can't remember the name) though it seemed like I was getting close, I couldn't get close enough before my temper got the better off me.
If my memory serves me correctly the OTG function worked when i first got the phone but didn't after the first update. My mate's Note 5 also has the same issue. I Googled it and seemed it was common issue on these phones.
I've tried to learn some Terminal/Command Prompt to see if I can fix it that way through Debian or whatever, only got as far as understanding it, kind of. Big ups to all you coders/programmers out there it really is an artform.
So PLZ PLZ can y'all help me, there has to be a way aside from setting this thing alight and getting a new phone.
My next mission, which I only embarked on a couple nights ago is unbricking my dad's Note 4 (N910G) that just hit the **** one day after spazzing out for a few days then would not turn on. I'm getting close though I haven't put much effort into that yet.
Any advice will be greatly appreciated, thanks in advance. ?
Forgive me if I've posted this thread in the wrong area
Tl;Dr - my pixel 5a5g got the black screen of death a few months ago. Last night, I tried using the flash tool to try to flash it back to Android from GrapheneOS - so that Google would be willing to fix it maybe. Flashing seemed to fail. Unsure what to try or do next.
---------------
My Pixel has had the black screen of death for a few months now. I'm assuming it is from falling a few feet to the ground. It had a custom ROM - GrapheneOS - on it. Unless I can reflash to stock Android, it sounds like Google/ubreakifix won't look at it, and thus - no chance of repairing it for free or a smaller charge.
The other night, I tried attaching an OTG keyboard to the phone to log in to it. Since the display is black, I'm not sure it worked. I also tried several times to press where I thought the numbers for logging in would be - on my completely black screen. Somehow, I was eventually able to get my PC and Google's flash tool to recognize the phone. However, I might have messed up on some steps - because I think it might be bricked now.
I think I forgot to remove the grapheneOS key via their Web installer before trying to flash android. I used minimal abd tools to unlock the bootloader (and it still says it is unlocked)... When I tried flashing back to stock android using the android web tool, it went through the motions, but then said something like it needs to detect the phone again after flashing. And it wouldn't detect the phone again. Even if I unplugged then replugged the phone. The directions said I shouldn't/wouldn't need to press any keys on the phone for this step, but it just wasn't progressing further... So, I ended up holding the power button and volume down button - and it went into fastboot(?) again - or whatever that does.
I can repeat the steps of going thru the motions of flashing the device now, but now it gives an error saying something like it can't lock the device.
Being that the 5a screen is completely black, I have no idea what is going on - or what to do from here. I've reached out to some local repair places, but honestly, if I can't flash it myself to stock so that Google/ubreakifix would look at it, then it probably isn't worth sinking money into.... There's decent condition used ones around $120 or something out there... And ubreakifix would probably charge between $160 and $200 for screen replacement + labor - and I'm assuming that's not including a motherboard replacement - if necessary.
Ubreakifix said that they would be willing to look at it, but they can't actually do any repairs to it if it isn't running stock Android. They'd charge for the labor, and they'd temporarily use a screen to look at what it is doing/not doing... But wouldn't actually do the screen repair. I'm assuming the phone never flashed completely, but I'm hoping they can tell me if their diagnostic tools work on it - since I imagine it should work -- IF stock Android is actually installed again on it.
I've also looked into doing something like getting a displaylink adapter + display link app so that I can see the screen on the computer... But even after my multiple attempts of logging in to the phone, I can't send app downloads to the phone. Google Play store shows that the phone was "last seen" months ago... And even if I could push the app download, GrapheneOS still requires manual approval from the user to accept/finalize install of the app... Which would be pretty hard to do without seeing the screen. And obviously since I've tried flashing the phone several times last night, i have no idea what the phone is looking like. Probably app downloads are out of the question now.
Apparently you can't normally do display out of any sort with Pixel phones. The rumor I've seen on here and/or reddit is that Google got rid of it years ago, maybe so that they can sell more Chromecasts...
Does anyone have any further suggestions? I could try using scrcpy or whatever it's called, but I probably should have tried to use that before attempting to flash the phone... It's sure hard to give up on something that I spent good money on. I'd like to think there's something I haven't tried yet that I can do to save it...
You could probably try these steps:
1. Open up Device Manager on PC
2. Connect your phone
3. Hold Power + Volume Down
If you have new device in Device Manager, you can do everything with your device like flashing or try "to remove the grapheneOS key".
Edit: I'm dumb and didn't notice that part where you tried this. You should just boot into fastboot and remove that custom AVB key with fastboot erase avb_custom_key, and then reflash the phone on flash.android.com. Hope that helps!