Recover rooted NST with broken LCD? - Nook Touch General

Just checking it there is some way to recover files. I previously rooted it and can't remember if that means there's any way to get at it via ADB or otherwise to recover files before transfering to a new device

Well, if you have ADB working you can just transfer the files.
Or you could use my AdbSync.exe (along with ADB) to backup.
Code:
C:\>mkdir whatever
C:\>adb devices
C:\>adbsync /hcsu /s /v C:\whatever sdcard

ADB doesn’t seem to be working or at least via USB… And I can’t get on it to select a Wi-Fi network. Wondered if there is some way of forcing it to boot in Adb mode or something that doesn’t rely on screen interaction

mrbryan said:
ADB doesn’t seem to be working or at least via USB… And I can’t get on it to select a Wi-Fi network. Wondered if there is some way of forcing it to boot in Adb mode or something that doesn’t rely on screen interaction
Click to expand...
Click to collapse
You're the second person in a week or so that seems to have this issue and it got me curious. There's a message at the beginning of NookManager about starting WiFi if you want to directly connect with the device via SSH(?) or ADB. I've always ignored it but I just tried it to see what would happen. After you elect to start WiFi (your NST must have been known to your network beforehand, password entered, etc.), you are given the option to start either SSH or ADB (the IP address is displayed at the top of the screen).
When I chose ADB I was then able to start up ADB on my PC and connect to the IP address shown on the NST screen. Of course.....if your screen is broken........Maybe you know the IP address of your NST already or could find it by starting WiFi and then consulting your router?
Anyway, the advantage with NookManager is that everything is done with the side hardware buttons. If you can't read your screen at all I can see that even that would be a problem, though. If you have some partial display, you might be able to limp along until you have ADB connected and then handle everything from your PC. Or I could supply you with a button-push sequence to try.
To just get this working you can make a NookManager card--no need to make the updates I described elsewhere.

thanks so much for the suggestion. I'll have to think that through and whether I have my current wifi set up ( edit: in the nook already).
maybe I can hack around in the scripts for nook manager in case I can set it to go right to the ADB on boot and inject a wifi name & key too

Get an image for the old noogie and put it on an SD card.
Boot up, you should have ADB.
Or do the whole OmapLink procedure and boot from there.
Or connect to the 1.8V UART root console inside the case.

Related

[Q] help for nook touch rooting from China

Hi everyone, I've been trying to root my nook2 and I've been over all the steps many times, and I can't achieve ADB over USB or WIFI.
I've used the nooter technique and the device looks rooted, I can log into Gmail and get new mail, but as youtube is blocked in China, I can't login to youtube as i'm supposed to in the process described on nookdevs. (is youtube loging really important?)
I can install apps from the market, but can't use the search field (no results, no matter what I type).
I decided to try adb access from there anyway (before asking for help...), and here's where I'm stuck :
I installed the light sdk combo found here : "hXXp://forum.xda-developers.com/showthread.php?t=910008" and followed all the steps
I can connect to the device using wifi ADB, but the shell cmd doesn't get me anywhere (I get a hash mark and an endlessly flashing underscore)
I can't get adb access over USB, because no matter how many times I try uninstalling the basic drivers in the device manager(all of them), they always come back within 5 seconds when I plug the nook (and yes, I seem to have disabled automatic driver update in Gpedit.msc)
when I try to load the adb drivers manually over the preexisting ones it tells me no suitable drivers where found in my *.inf file (or that it already has the best driver for the device)
I've been over everything (apparently) countless times and I'm still stuck.
do you have any idea what the problem could be?
If I had to guess, it's either :
-It's not completely rooted (for lack of youtube login) so it will always be recognized as a Nook and nothing else in the device manager
-the factory defaults nook drivers are lurking somewhere on my laptop and prevail over the adb_usb drivers.
-there is another move to disable automatic drive install in Gpedit.msc which I haven't attempted yet.
Please if you have any ideas... My nerdy ego is absolutely hurt by this and it's begging for relief.
I've been thinking about this, and if I could just set up the android version of astrill directly in the micro sd (directly set up on nooter) I could then access youtube and finish the job properly.
Do you know if it's in any way possible to do that?
I wonder if you'd be able to use Orbot to be able to gain access to Youtube...
Karibou3 said:
Hi everyone, I've been trying to root my nook2 and I've been over all the steps many times, and I can't achieve ADB over USB or WIFI.
I've used the nooter technique and the device looks rooted, I can log into Gmail and get new mail, but as youtube is blocked in China, I can't login to youtube as i'm supposed to in the process described on nookdevs. (is youtube loging really important?)
I can install apps from the market, but can't use the search field (no results, no matter what I type).
I decided to try adb access from there anyway (before asking for help...), and here's where I'm stuck :
I installed the light sdk combo found here : "hXXp://forum.xda-developers.com/showthread.php?t=910008" and followed all the steps
I can connect to the device using wifi ADB, but the shell cmd doesn't get me anywhere (I get a hash mark and an endlessly flashing underscore)
I can't get adb access over USB, because no matter how many times I try uninstalling the basic drivers in the device manager(all of them), they always come back within 5 seconds when I plug the nook (and yes, I seem to have disabled automatic driver update in Gpedit.msc)
when I try to load the adb drivers manually over the preexisting ones it tells me no suitable drivers where found in my *.inf file (or that it already has the best driver for the device)
I've been over everything (apparently) countless times and I'm still stuck.
do you have any idea what the problem could be?
If I had to guess, it's either :
-It's not completely rooted (for lack of youtube login) so it will always be recognized as a Nook and nothing else in the device manager
-the factory defaults nook drivers are lurking somewhere on my laptop and prevail over the adb_usb drivers.
-there is another move to disable automatic drive install in Gpedit.msc which I haven't attempted yet.
Please if you have any ideas... My nerdy ego is absolutely hurt by this and it's begging for relief.
Click to expand...
Click to collapse
Read this, its all contained on my manual tutos, adb is gained just by changing uramdisk, there is one for wifi and another for usb, please, check which one you are using, then, follow this:
Here there is a list of all the tutos:
http://forum.xda-developers.com/showthread.php?t=1380400
and here the ones you should read:
Setting up adb manually on the nook touch:
Making the manual process LESS PAINFULL
Setting up root access on NST through adb and installing busybox:
Hope it helps.
For the youtube thing, just set adb correctly (when you get it right) sideload an app to use a proxy, or tor, or anything you like, and try to login on Youtube.
I'm really sorry for not responding to this
I managed to get it rooted in the few days after my post, and I didn't any email notifications of your replies (didn't check on control panel, i'm new here, please don't hurt me )
I found a chinese source for rooting (a seller on taobao.com explained it. The Chinese are quite fond of the nook because it's the only foreign e-reader you can use to read Chinese apparently, and Chinese e-readers are both more expensive than the nook AND crappy.
Anyway I painstakingly translated it and got it to work
what you tell me about the proxy is new to me though, I thought android couldn't run a proxy, that's great news not just for youtube but the zillions of website China blocks and that I could use my nook to check, I'll have a go at it when I get near a wifi network.
cheers

need help retrieving files from my broken Vibrant

i just recently dropped my first generation Samsung Galaxy S Vibrant on the ground. most of the screen went black and i am unable to login into the phone. i am trying to figure out how to retrieve my photos off of the phone's on-board hard drive
i installed the Android SDK on my mac (running 10.6.8) and then installed ADB
i am able to put my phone in recovery mode by plugging it onto my mac and using ADB by running "./adb reboot recovery"
but when i run "./adb devices" it does not recognize my device
usb debugging is enabled on my phone.
i also do not have EasyTetherUSBEthernet installed on my mac
any help getting this to work would be much appreciated.
Does "can't log in" mean that you have to enter a pin, and can't because the screen doesn't work? If that's the case, then one option would be to reflash your rom (since Recovery is available) which would remove your pin and then allow you to access the phone sdcard through usb.
I'm just making this up as I go, so hopefully someone will correct if the idea is hopelessly flawed.
If you can get an adb shell running, or if you can manage to get the recovery to make the sdcard available for mounting, it can be done. Failing that, maybe the Odin dump command?
JJMT said:
Does "can't log in" mean that you have to enter a pin, and can't because the screen doesn't work? If that's the case, then one option would be to reflash your rom (since Recovery is available) which would remove your pin and then allow you to access the phone sdcard through usb.
Click to expand...
Click to collapse
"can't log in" means i am unable to unlock my phone via the unlock pattern i set on it.
the data i care about is in the on-board hd and not the sdcard. would reflashing also wipe the on-board hd?
nm... somehow i was able to get it to work. after trying it again i was able to get adb to recognize my device, plus i now realize the difference between "sdcard" and an sd card
You should be all set. You can add an external SD card, then, using adb shell, mount it and do something like
cp -a /mnt/sdcard /<wherever you mount external sd>
You could also use adb pull on the host, but it may be tedious.
Reflashing has never wiped an sd card for me. You could reflash to get what's left of the device sort of usable.

adb unable to connect...

I was to B&N today, read few books in store (on nook)
Came home, tried to connect:
adb unable to connect...
run dropbear - unable to ssh
rebooted nook via terminal
adb unable to connect...
Scratched head…
rebooted nook again via terminal
adb unable to connect...
Did basic adb troubleshooting:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
adb unable to connect...
stop adbd
adbd &
adb unable to connect...
netstat
showed listening (with adbd running)
127.0.0.1:5037
0.0.0.0:5555
rebooted nook via terminal
rebooted PC…
adb unable to connect...
put noogie SD, reboot, check uRamdisk – same size & timestamp
removed noogie, off/on - connected right away!
I’m puzzled…
I saw few times, after 2-3 days of reading adb is unable to connect, but reboot fixed it always.
What was different this time?
“Cold reboot”?
I spend like 30min and feel like an idiot right now…
I was unable to connect over the usb port as well. Without too long investigation I've used adbwireless app on NT and was able to connect.
You might want to refresh server
adb kill-server
adb start-server
then connect using your NT ip address:5555 and you should be done.
In my case, I think, there are too many conflicting drivers installed and NT is not being recognized when connected.
Good luck
Adapt0r said:
I was unable to connect over the usb port as well. Without too long investigation I've used adbwireless app on NT and was able to connect.
You might want to refresh server
adb kill-server
adb start-server
then connect using your NT ip address:5555 and you should be done.
In my case, I think, there are too many conflicting drivers installed and NT is not being recognized when connected.
Good luck
Click to expand...
Click to collapse
I did it as well before every adb connect, thought it not worth to mention.
Naturally, "rebooting PC" should reboot adb server too, right?
But it didn't help either...
If you see this issue again, just try toggling ADB Wireless On/Off and it should reset anything on the devices side. Also I've noticed that sometimes and completely random from what I can tell "USB Debugging" will get unchecked, which will mess with ADB access via USB.
Disabling/Enabling ADBwireless sometimes may help.
Maybe a stupid question: Do you have a firewall running on your pc?
digiflash said:
Disabling/Enabling ADBwireless sometimes may help.
Click to expand...
Click to collapse
won't it be the same as below or it does more?
Code:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
digiflash said:
Maybe a stupid question: Do you have a firewall running on your pc?
Click to expand...
Click to collapse
Always
I did check it too. It was nothing worth to mention.
abd attempted to connect - got nothing back (timeout)
on NST adbd was listening, I was able to access gmail.
I can ssh neither, and dropbear was listening too.
Looks, in fact, like firewall on NST was blocking all incoming connection.
That's why I wrote "Scratched head…" - which means I checked pretty much everything.
Could somebody explain, what is the major difference for NST between:
reboot (hot reboot) & shutdown/start (cold reboot)
Or more precisely for the latter:
insert noogie SD/reboot/remove noogie SD/turn off/turn on
ApokrifX said:
insert noogie SD/reboot/remove noogie SD/turn off/turn on
Click to expand...
Click to collapse
Cannot connect today at all. Cold reboot doesn’t help anymore...
Did some more tests (including ADBwireless):
I cannot ping [nook IP] from my computer
I can ping [nook IP] from router.
From PC
>telnet [nook IP] 5555
Connecting To [nook IP]...Could not open connection to the host, on port 5555: Connect failed
From router:
telnet [nook IP] 5555
Connection didn’t timeout (i.e. it does connect!)
Again, looks like something on Nook blocking connections from all IP, except from default gateway (i.e. router)
Question: Does rooting process unblock connections from other IPs?
About Disabling/Enabling ADBwireless:
Before running ADBwireless
netstat
127.0.0.1:5037
0.0.0.0:5555
netstat -tapn doesn’t work
stop adbd
both above disappear from netstat
start adbd
both show up
run ADBwireless
get message: ADBwireless is off
pushed button, message changed to: adb connect [nook IP]:5555
(adb connct didn’t work)
Switch to terminal,
netstat
127.0.0.1:5037
I.e. no more: 0.0.0.0:5555
Subsequent "stop adbd"/"start adbd" changes nothing:
netstat
127.0.0.1:5037
I was wondering what ADBwireless supposed to do then?
Could somebody check from his nook what netstat shows, please?
Nook can connect to internet (gmail, market) + netstat shows all outgoing connections…
What else can I try?
I guess, I can switch to adb usb…
It might be helpful if you tell what OS you are running on your PC and what did you do with NT. If we can reproduce your case then we can troubleshoot it otherwise you will hear useless guesses and speculations.
I like NT as a reader and nothing else. Web and games are looking awful on it.
Adapt0r said:
It might be helpful if you tell what OS you are running on your PC and what did you do with NT. If we can reproduce your case then we can troubleshoot it otherwise you will hear useless guesses and speculations.
I like NT as a reader and nothing else. Web and games are looking awful on it.
Click to expand...
Click to collapse
One box is XP with Outpost firewall (abd set to full trust).
Another win7 (FW policy – allow outgoing connections + few exceptions).
I’m Win developer/admin and Linux(CentOs) admin.
I’m complete noob when it comes to Linux non-shell related programming.
Router runs DD-WRT.
As of now I switched to uRamdisk_1_1_rooted_usb.
When I run dropbear, I see it listening on 22, but cannot ssh still.
That’s all I guess…
Could you do one test for me please?
If your NST runs uRamdisk_1_1_rooted_wifi:
Could you ping you NST from you box
If not - could you do same from your router/AP?
1. I don't have uRamdisk_1_1_rooted_wifi on my NT and can't test it.
2. adbWireless works on my Win 7 and Mac the same way. Both comps have firewalls running and both are on the same network. I can connect and ping NT.
Just for clarification I will describe how it works on my setup:
- I start adbWireless on NT,
- it asks for root permission if it for the first time and I grant it
- then shows fat button on the screen and says adbWireless is off
- I push the button
- it says adbWireless is on, from your computer run
adb connect 192.168.15.112:5555
At this point I can ping IP address and run adb shell.
I've rooted NT for purposes of software testing and customization. I did it twice with older and newer Nooter and did not find any noticeable differences.
Let me know if you want some other tests or info.
Adapt0r said:
I can connect and ping NT.
…
At this point I can ping IP address and run adb shell.
Click to expand...
Click to collapse
To clarify (trying to get a setup as simple as possible):
We connected NST to our home wireless network and it gets IP.
We didn’t touch adbWireless yet!
Now do two tests, please:
1. From NST we ping gateway or "another device on same network", (providing it let us).
2. From "another device on same network", ping NST.
What do you get?
I thought, adbWireless just configure adbd for IP connection (as opposite for USB one) and starts it - nothing else.
If #1 works, but not #2,
and #2 starts working after you “hit adbWireless button”, than adbWireless does more then I wrote above…
Sorry, I didn't have time to do your test at home. I'll try today.
I think you are correct, adbWireless does configuration of connection by executing something like this:
Turning On:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
Turning Off wifi and start listening on usb
setprop service.adb.tcp.port -1
stop adbd
start adbd
Cheers!
Edit:
Ping NST_ip_address from PC works fine.
Since I don't have terminal installed I could not test reverse pinging.
Ouch…
Just figured out:
1: I press “big red button” in adbWireless.
2: I push back button
And it pushed adbWireless into background.
If it’s the same as turning it (adbWireless) off,
it’s possible, that adbWireless reset adbd service to use USB.
Thus there is nothing listening on 5555 when I run netstat in terminal on NST.
Who’s with me?
Should be east to test:
press “big red button” in adbWireless.
I push back button
try to connect
ApokrifX said:
Ouch…
Click to expand...
Click to collapse
Updated router firmware - I can ping nook and ADB over wireless works too.
Not sure thought, if it was wireless channel problem.
I've read somewhere, some NST firmwares doesn't work on high channels or certain combined modes - like works on A+B, but not A+G
Apparently, NST firmware 1.1.2 was targeted to solve some of these issues.
PROBLEM SOLVED.
I didn't have the proper folder for the adb.exe.
-----
I have a similar problem: I recently rooted my nook simple touch with touchnooter 2.1.31, and all seems well but I can't connect to the adb wireless. IP is 192.168.0.6:5555 according to adb; I can ping from my Win XP computer if I use 192.168.0.6, but not if I add the 5555, but I just can't connect to the ereader. Wireless connections seem fine otherwise. I've tried shutting off and one the wireless adb.
I'm a complete beginner in this. On the reader, the screen has this:
"from your computer run: adb connect 192.168.0.6:5555"
This suggests that I can't simply use a firefox browser to connect? I tried using the windows cmd box, but windows indicates it doesn't know what 'adb' is. Then I found a website about adbwireless: http://theunlockr.com/2011/04/12/how-to-connect-to-your-android-device-through-adb-wirelessly/
and installed Adroid SDK Tools as indicated. When I use the cmd window, go to the proper sdk tools subfolder, and type 'adb connect 192.168.0.6:5555', windows still insists it doesn't recognize 'adb'
Please help!
try adb.exe
Meter 13,
Thanks for the reply. I added a pre-script to my op. I had created a bat file to move to the proper folder but had realized that the adb.exe had been moved to the platform-tools subfolder from its old location in the tools folder. Once I realized this, all worked well - connected to my nook, and used adb to install an apk file.
Bob
Just a note:
Ping isn't the usual TCP/UDP stuff, so there are no (port) numbers on the end.
ping 192.168.1.27
ADB uses TCP and a port number but it usually defaults to 5555
adb connect 192.168.1.27
adb connect 192.168.1.27:5555
You can also telnet to check if you can connect to the nook via TCP and port 5555
telnet 192.168.1.27 5555
(Note: If this works it will tell you that you are connected, but you can't do anything because ADB is a binary protocol.)
I had the same problem, turns out the correct drivers weren't installed. Ive downloaded HTC sync from HTC.com. I installed it and removed HTC sync afterwards. The drivers should stay there. Now reconnect your phone and try "adb devices" Before ADB wouldn't recognize my device but now it does. Tried to "adb backup -all" again, and it worked instantly.
Maybe this solves the problem?
You could try going back to a stock /boot partition.
I run my nstg rooted with the addition of about 8 files (su, xbin, busybox in system, adb wireless in /data plus a launcher) when I first root.
with the nstg, at least, I don't actually need the modified kernels - adb connects from my computers to the nstg, I simply don't have a root shell when I first connect.
This is fixed by doing an
su
once I'm in
Might be worth trying a restore of just partion 1 from your backup?

[Q] Choosing ADB over USB or WiFi, when Rooting

After reading around, I've learnt that MinimalTouch 1.1beta5 is a reliable way to root my new Nook Simple Touch. Since I intend selecting the package version in the beta5 folder, I must choose between the "START" zips: beta5-2 XUFullTouch-PART-1-START and beta5-2 XWFullTouch-PART-1-START. I gather the first zip is ADB over USB, and the second, ADB over WiFi, but have found little documentation on either, except that ADB is a method to connect your home computer to your Nook.
The above link states that all W zips install ADB wireless Uramdisk, and all U zips install ADB USB Uramdisk + ADB widget to enable wireless adb at need. Am I right that ADB over USB is the best choice because both USB and WiFi are available after rooting? If so, would anyone select the ADB over WiFi option?
Can someone please explain how and why one chooses between the two options when rooting the Nook?
On startup the ADB daemon, adbd looks at the property service.adb.tcp.port
If it is set it uses that value as the port number over TCP (presumably over WiFi) to listen for connections.
If it is not set it tries to connect over USB.
I'm not sure how these applications that switch mode work.
They probably kill the daemon and restart it.
The only difference between the two versions of W and U is the line:
Code:
service.adb.tcp.port=5555
Renate NST said:
The only difference between the two versions of W and U is the line:
Code:
service.adb.tcp.port=5555
Click to expand...
Click to collapse
Thanks for your help. I've taken a while to make sense of your post since all this is new to me - I rarely use a mobile phone.
I've just looked at contents of both the "START" zip files and noticed they're the same, except that the file uRamdisk in the folder boot of the WiFi option is marginally bigger. You have shown me the difference lies in the property service.adb.tcp.port in the Java source code, and that property determines whether the rooted Nook tries to connect by WiFi or USB. In other words, the two zips are identical except for ADB connection.
But my opening post, in ignorance, attempted to ask a more trivial question. I know whenever I wish to access any laptop computer from my desktop computer under Windows XP, I can connect the two using a network cable from the laptop to my wireless router/modem or, more simply, by activating WiFi on the laptop. Similarly, I am assuming I can connect the rooted Nook to my desktop either by cabling the Nook microUSB port to a USB port on my desktop, or by activating WiFi on the Nook. I expect to connect every few days. Since the USB "START" zip of MinimalTouch 1.1beta5 provides an ADB widget to enable wireless adb at need, what is the point - for the end user - of a separate WiFi only "START" zip file?
In other words, in routinely connecting my rooted Nook to the desktop computer every few days, why on earth would I or anyone benefit from having had the two "START" zip options available in MinimalTouch 1.1beta5?

Need to bypass lockscreen/gain access to adb - Broken screen

So I have a bit of an issue. Somehow last night, after trying to help my parents with our home theater system, with the device laying on a soft surface, the LCD (not the glass) somehow broke. I am really not sure how this happened, the phone itself didn't fall, it was laying on a bed the entire time. When I went to grab the phone and turn it on, I was pretty surprised. You can see what I mean in the attached file.
Now the problem with this is, while I would normally just walk into the Sprint Store, complain and get a new phone. I am not in the US for another 5 months. In the mean time of trying to figure out what to do, I would like to at the very least, grab any files off my phone, or back up my phones' file structure.
I am able to do a minimal amount of tapping on the phone, only on the upper half of the screen, but I can't see anything, nor does the device respond with any touch data from the bottom half.
I obviously can't access the files if the device is locked, which means I have to bypass the lock screen. I found this guide, but unfrotunately, Method 1 didn't work, and I can't get adb to recognize my phone for Method 2.
I also have tried using CWM (the non-touch version) to backup my data, but I let it sit there for 45 minutes and I couldn't tell if it was finished or not. It didn't appear to actually be doing anything.
Could someone help me navigate around this or provide some assistance in allowing me to just get the files off the phone while I search for a new one?
With that being said, does anyone have some recommendations? I was thinking of getting a Motorola X or Nexus 5.
EDIT: Update:
I have access to terminal via Cerberus shell. I was able to use Method 2 to disable the lock screen (or in this case set it to Swipe). It is still pretty difficult to use the phone but I can at least backup whatever data I still do have on the phone to my laptop.
Would anyone be able to give me some advice as to uninstall applications or XDA xposed modules via shell? Or perform a backup or enable ADB debugging?
You've conntected to your PC at least once so that the ADB has permission, correct? If so, you can get http://forum.xda-developers.com/showthread.php?t=2786395 to get Android Control and view/Control your phone via USB. You need to have Java installed, which most have already. Been controlling my cracked LCD for the past week while waiting for my replacement.
Keep in mind this method is a little slow because of ADB. Hopefully you don't have to type too much.
Darnell0216 said:
You've conntected to your PC at least once so that the ADB has permission, correct? If so, you can get http://forum.xda-developers.com/showthread.php?t=2786395 to get Android Control and view/Control your phone via USB. You need to have Java installed, which most have already. Been controlling my cracked LCD for the past week while waiting for my replacement.
Keep in mind this method is a little slow because of ADB. Hopefully you don't have to type too much.
Click to expand...
Click to collapse
I know I have connected it at least once, but when connecting the phone and the pc together, adb cannot find the phone. I am not sure if this is because of a Cerberus setting (that disables debugging) or something else. I will give it another shot when I get home.
If I can't, is there any way for me to somehow accept the adb permissions on the phone via a command versus touching the screen? Say if I have shell access over Cerberus and adb access from my PC?
slixzen said:
I know I have connected it at least once, but when connecting the phone and the pc together, adb cannot find the phone. I am not sure if this is because of a Cerberus setting (that disables debugging) or something else. I will give it another shot when I get home.
If I can't, is there any way for me to somehow accept the adb permissions on the phone via a command versus touching the screen? Say if I have shell access over Cerberus and adb access from my PC?
Click to expand...
Click to collapse
There's a bit of work to push the ADB acceptance key if you have a spare android phone lying around. Other than that, there probably is but might be more of a headache. I took the ADB key for my desktop from another android and pushed it in through TWRP which accepts ADB commands while in Recovery.
Darnell0216 said:
There's a bit of work to push the ADB acceptance key if you have a spare android phone lying around. Other than that, there probably is but might be more of a headache. I took the ADB key for my desktop from another android and pushed it in through TWRP which accepts ADB commands while in Recovery.
Click to expand...
Click to collapse
I have a sony xperia P that I am using right now until the replacement phone I got arrives. Any idea how I could use that? I have had minimal success with the phone so far in trying to get that phone to flash custom recoveries, to root the device (not sure why, but my laptop just doesn't want to seem to do it, even using automated tools).
Is it better to just wait for the replacement phone to arrive and grab what I need from that and push it? Could you link me to any guide or steps that you used with yours?
Thanks for such quick responses by the way!
EDIT:
Flashing TWRP and booting into recovery with command prompt open and running adb devices / fastboot devices does not show any devices available.
Is there a specific menu setting or other option I need to use to be able to run adb?
When you use TWRP, the phone will be recognized by the PC but the driver doesn't install correctly off the bat. Go to Device Manager and look for your phone. You may need to click the View -> Show Hidden Devices option. Update the driver manually by selecting the one provided by your manufacturer. Some have a dedicated ADB driver for specific functions (bootloader, etc).
The adb key is stored in data/misc/adb/adb.keys -You can pull this file from any other android connected to that PC (or just copy it if you have a root explorer) and push it to the broken one if necessary. This will bypass any ADB authorization issues while the phone is fully booted and let you see the screen.

Categories

Resources