Hello,
My galaxy S2 fell and my digitizer is apparently non-working - I can see the screen sort of, but there is no touch response.
Anyway, I can't let just about anyone who I take it to have access to my data, since my contacts are stored on the google cloud, I have them all anyway, but I either need to:
1. Access the phone via PC and wipe the data by emulating the screen on my PC.
I tried using Kies air to do it - it recognizes the phone, but I can't open it through it because my phone is locked and it won't give me access otherwise. Of course I can't unlock it since the digitizer is dead.
I tried using software like droid-at-screen, installing the proper SDK components, BUT the phone never got recognized. It is my deduction that I have to enable USB debugging, which, again, I can't do since I don't have the touch interface.
2. The other solution would be to wipe all data manually, which I assumed was done holding the 2 volume buttons + power button, but all that ever got me to was the lock screen along with a "safe mode" in the corner.
I posted this in the android Q&A, since I feel this is more of an android rather than model related issue. Thank you.
If you can still see the screen enough, I think with USB OTG you can connect a computer mouse and use that to navigate to the wipe data screen
Sent from my DROID2 using xda premium
gagdude said:
If you can still see the screen enough, I think with USB OTG you can connect a computer mouse and use that to navigate to the wipe data screen
Sent from my DROID2 using xda premium
Click to expand...
Click to collapse
Thanks for the reply.. I don't think any of those are available where I can get them though :/
Posklapenzi said:
Thanks for the reply.. I don't think any of those are available where I can get them though :/
Click to expand...
Click to collapse
use adb
adb pull
adb pull /sdcard/ or pull /data and datadata
xsenman said:
use adb
adb pull
adb pull /sdcard/ or pull /data and datadata
Click to expand...
Click to collapse
Thank you. I assume this is some kind of cmd that I run from adb.exe once I install it through the SDK?
Posklapenzi said:
Thank you. I assume this is some kind of cmd that I run from adb.exe once I install it through the SDK?
Click to expand...
Click to collapse
yup, you can get a guide from My Guides and Manuals for ADB knowledge and just use a adb.exe
xsenman said:
yup, you can get a guide from My Guides and Manuals for ADB knowledge and just use a adb.exe
Click to expand...
Click to collapse
Thank you, just one question - do I need degugging turned on for this as well? Because like I said, I am unable to do that.
Posklapenzi said:
Thank you, just one question - do I need degugging turned on for this as well? Because like I said, I am unable to do that.
Click to expand...
Click to collapse
yup, adb will only work with debugging enabled, just try you might have left it enabled
xsenman said:
yup, adb will only work with debugging enabled, just try you might have left it enabled
Click to expand...
Click to collapse
Turns out I do not.. is there any hope for me left? Somehow wipe the entire memory manually?
Posklapenzi said:
Turns out I do not.. is there any hope for me left? Somehow wipe the entire memory manually?
Click to expand...
Click to collapse
I'm in the same position, so I'll be watching to see if there is hope
loopism said:
I'm in the same position, so I'll be watching to see if there is hope
Click to expand...
Click to collapse
Bumping this, I've yet to find a solution..
Posklapenzi said:
Bumping this, I've yet to find a solution..
Click to expand...
Click to collapse
Are you sure there are no USB OTG cables available for you? They're like $5 online
Sent from my DROID2 using xda premium
Related
I have changed the build.prop of my rooted TF201 to play the gameloft games.
After changing the TF201 got stuck in a bootloop. I tried the hard reset but it is still not starting.
I read that it is possible to push the orginal build.prop to the TF201 via APX-Mode but i dont now how to do it.
My computer recognizes the TF201 as a Asus Transformer Prime APX mode or in MTP when i start it regular. Unfortunatly i can not get any access to the Data of my TF201.
Is Asus able to see the root and that i changed the build.prop if i sent it to RMA?
Would be so happy if anybody could help me.
Thank you.
(And i know it was stupid to change the build.prop but didnt expected to brick it http://media.xda-developers.com/images/icons/icon9.gif)
Hi there.
I had a week of the same problem. I hadn't deleted anything but mine was in the boot loop too. After trying everything I managed to reinstall the OS by:
1. Downloading firmware from Asus site (it must be same or later version as installed already and must be the one for your region - if you don't know your current version, the small text described in step 4 below will tell you and step 4 can be done multiple times)
2. Freshly formatting a micro SD card with FAT
3. Placing the ZIP file (the zip inside the zip that Asus provide) in the root of SD CARD
4. Restarting the tablet by holding power and volume down until small text appears at top of screen at which point press volume up
Your tablet will boot from the SD card and reinstall your OS.
ALL DATA WILL BE LOST but you'll have a working tablet.
Cheers.
Sent from my Transformer Prime TF201 using xda premium
stf996 said:
Hi there.
I had a week of the same problem. I hadn't deleted anything but mine was in the boot loop too. After trying everything I managed to reinstall the OS by:
1. Downloading firmware from Asus site (it must be same or later version as installed already and must be the one for your region - if you don't know your current version, the small text described in step 4 below will tell you and step 4 can be done multiple times)
2. Freshly formatting a micro SD card with FAT
3. Placing the ZIP file (the zip inside the zip that Asus provide) in the root of SD CARD
4. Restarting the tablet by holding power and volume down until small text appears at top of screen at which point press volume up
Your tablet will boot from the SD card and reinstall your OS.
ALL DATA WILL BE LOST but you'll have a working tablet.
Cheers.
Sent from my Transformer Prime TF201 using xda premium
Click to expand...
Click to collapse
Thank you for answering!
Unfortunatly did not work for me.
The androidfigure showed up with a red triangle on it and after a minute it restarted into the bootloop.
Any other ideas?
clmz88 said:
Thank you for answering!
Unfortunatly did not work for me.
The androidfigure showed up with a red triangle on it and after a minute it restarted into the bootloop.
Any other ideas?
Click to expand...
Click to collapse
Can't you push the original build.prop via ADB Shell when it's almost booted up?
Code:
adb mount -o ro,remount /dev/block/mmcblk0p1 /system
adb push c:\...\build.prop /system/
Turge said:
Can't you push the original build.prop via ADB Shell when it's almost booted up?
Code:
adb mount -o ro,remount /dev/block/mmcblk0p1 /system
adb push c:\...\build.prop /system/
Click to expand...
Click to collapse
I tried it and got the message "can not find device" although my systems shows Android MTP Device in the device manager...
clmz88 said:
I tried it and got the message "can not find device" although my systems shows Android MTP Device in the device manager...
Click to expand...
Click to collapse
Mine shows up, but only when "Camera (PTP)" is selected instead of "Media device (MTP)" in the "Settings >> Storage >> USB computer connection" section.
But of course, that won't help you in this case since you can't change this setting.
I can't find anything about having to switch to PTP for ADB to work so you may want to post a question about it in the Q&A forum.
A guy had the exact same problem here last week after changing the build.prop for the exact same reason. He was able to recover his problem using the same method that the root scripts use for writing to data. Let me try and find the thread and you can try to contact him.
EDIT: Here you go.
http://forum.xda-developers.com/showthread.php?t=1480428&highlight=bricked
Now don't go doing such stupid things again.
Turge said:
Mine shows up, but only when "Camera (PTP)" is selected instead of "Media device (MTP)" in the "Settings >> Storage >> USB computer connection" section.
But of course, that won't help you in this case since you can't change this setting.
I can't find anything about having to switch to PTP for ADB to work so you may want to post a question about it in the Q&A forum.
Click to expand...
Click to collapse
Ok. Thanks though.
I would be happy about some other ideas
Doktaphex said:
A guy had the exact same problem here last week after changing the build.prop for the exact same reason. He was able to recover his problem using the same method that the root scripts use for writing to data. Let me try and find the thread and you can try to contact him.
Click to expand...
Click to collapse
I already got that thread and asked for his solution.
Im unfortunatly not able to sent him a private message because i am a new member.
clmz88 said:
Ok. Thanks though.
I would be happy about some other ideas
Click to expand...
Click to collapse
EDIT: I'll see what I can do for you, give me some time.
Doktaphex said:
EDIT: I'll see what I can do for you, give me some time.
Click to expand...
Click to collapse
Thank you!!!
clmz88 said:
Thank you!!!
Click to expand...
Click to collapse
I've sent him a PM for you asking for his solution. I've linked him to this thread.
What software version are you on? .11 .13 or something else.
EDIT:
Do you know how to use ADB?
Does ADB see your device?
Doktaphex said:
I've sent him a PM for you asking for his solution. I've linked him to this thread.
What software version are you on? .11 .13 or something else.
EDIT:
Do you know how to use ADB?
Does ADB see your device?
Click to expand...
Click to collapse
I actually dont know what version is on my Prime. I did the official update two weeks ago. So it is probably V9.4.2.11.
I have a app called "adb made easy" on my pc and this on can not find my device.
Does your device constantly reboot or does it stay at the boot animation?
Doktaphex said:
Does your device constantly reboot or does it stay at the boot animation?
Click to expand...
Click to collapse
It stays constantly in the boot animation.
and adb made easy doesn't have your device listed?
What if you "open CMD for ADB commands" and then in that window type "adb devices" without the quotation marks?
Also what does windows device manager show with regards to android devices?
EDIT: unplug and plug back in a couple of times, does windows make it's usual connection noises?
Doktaphex said:
and adb made easy doesn't have your device listed?
What if you "open CMD for ADB commands" and then in that window type "adb devices" without the quotation marks?
Also what does windows device manager show with regards to android devices?
Click to expand...
Click to collapse
adb made easy and cmd dont show any adb devices.
the devices manager shows
mobile devices: Asus Android MTB Device (could not be started)
windows is always making the pluggingsound
Wierd, ADB should still see the device as it seemed to when the other guy screwed his build.prop
If I reboot, ADB picks up the device during the boot animation and lets me start interacting straight away.
EDIT: Unfortunately, without ADB, I'm not gonna be able to help any further. Hopefully the guy how recovered his from this state will pop in and be able to help you out.
When and where did you get the device from. If you're still in your return window and feel like being dishonest, then you could take it back to the shop and ask for a replacement. However, if it has to go back to ASUS, I'm fairly certain that they would pick this up straight away, I could be wrong though. They may just look at it see it doesn't boot, reflash it and then test it and send it back.
Doktaphex said:
Wierd, ADB should still see the device as it seemed to when the other guy screwed his build.prop
If I reboot, ADB picks up the device during the boot animation and lets me start interacting straight away.
EDIT: Unfortunately, without ADB, I'm not gonna be able to help any further. Hopefully the guy how recovered his from this state will pop in and be able to help you out.
When and where did you get the device from. If you're still in your return window and feel like being dishonest, then you could take it back to the shop and ask for a replacement. However, if it has to go back to ASUS, I'm fairly certain that they would pick this up straight away, I could be wrong though. They may just look at it see it doesn't boot, reflash it and then test it and send it back.
Click to expand...
Click to collapse
Is yours setup for PTP or MTP?
Sent from my Transformer Prime TF201 using xda premium
Turge said:
Is yours setup for PTP or MTP?
Sent from my Transformer Prime TF201 using xda premium
Click to expand...
Click to collapse
I think it is setup for MTP but im not sure about it...
I didnt find a way yet to get access to the prime via usb.
Already tried different drivers, adb, apx but nothing is working.
Hey guys,
So I've scoured the internet to no avail, perhaps someone smarter than me can be of some use here. Here's my problem:
I have an S3, when plugging it into ANY PC with one of four USB cables, it starts charging, and does nothing else, the PC does not pick it up at all. I know there's no problem with the cable or the PC because I've tried it with another S3 which is detected immediately by windows.
I've tried multiple codes, setting it to Modem and PDA mode, I even did a factory reset which brings me to my second problem: I lost the data I thought I'd backed up.
So I'm not worried about recovering this data, I'm fairly certain I'll be able to get it back if I can get this USB working, but I'm out of ideas. I know it's not my drivers, because 3 different PC's manage to detect the other S3 without a hitch.
I've removed the battery, the sim card, rebooted, booted in download mode. Still nothing.
Any ideas?
PS: First post FTW. I'm not one to ask for these things unless I've exhausted all other resources, so if there is actually a working solution I've missed, I apologise in advance.
Treeofl1 said:
Hey guys,
So I've scoured the internet to no avail, perhaps someone smarter than me can be of some use here. Here's my problem:
I have an S3, when plugging it into ANY PC with one of four USB cables, it starts charging, and does nothing else, the PC does not pick it up at all. I know there's no problem with the cable or the PC because I've tried it with another S3 which is detected immediately by windows.
I've tried multiple codes, setting it to Modem and PDA mode, I even did a factory reset which brings me to my second problem: I lost the data I thought I'd backed up.
So I'm not worried about recovering this data, I'm fairly certain I'll be able to get it back if I can get this USB working, but I'm out of ideas. I know it's not my drivers, because 3 different PC's manage to detect the other S3 without a hitch.
I've removed the battery, the sim card, rebooted, booted in download mode. Still nothing.
Any ideas?
PS: First post FTW. I'm not one to ask for these things unless I've exhausted all other resources, so if there is actually a working solution I've missed, I apologise in advance.
Click to expand...
Click to collapse
Did you try flashing another stock rom..
tallman43 said:
Did you try flashing another stock rom..
Click to expand...
Click to collapse
Hmm I'd give it a try if I could actually connect it to a pc... There's no way to flash anything straight from the phone, correct?
Treeofl1 said:
Hmm I'd give it a try if I could actually connect it to a pc... There's no way to flash anything straight from the phone, correct?
Click to expand...
Click to collapse
Use mobile odin
tallman43 said:
Use mobile odin
Click to expand...
Click to collapse
Ok thanks will give it a try
Another question, in terms of recovery. I made xml and vcf backups onto the internal storage, thinking they'd stay on the device. Should the USB mode not work, is there any way for me to recover these files from the device? The apps I've seen so far, only recover images. Which is great, but not completely helpful.
Treeofl1 said:
Ok thanks will give it a try
Another question, in terms of recovery. I made xml and vcf backups onto the internal storage, thinking they'd stay on the device. Should the USB mode not work, is there any way for me to recover these files from the device? The apps I've seen so far, only recover images. Which is great, but not completely helpful.
Click to expand...
Click to collapse
Use PhilZ recovery there is a odin compatible version in his thread you can flash and also a Aroma installer add on where you can browse and copy files in recovery. Look in his thread >> http://forum.xda-developers.com/showthread.php?t=2201860 << post three explains Aroma and how to use.
Treeofl1 said:
Hey guys,
So I've scoured the internet to no avail, perhaps someone smarter than me can be of some use here. Here's my problem:
I have an S3, when plugging it into ANY PC with one of four USB cables, it starts charging, and does nothing else, the PC does not pick it up at all. I know there's no problem with the cable or the PC because I've tried it with another S3 which is detected immediately by windows.
I've tried multiple codes, setting it to Modem and PDA mode, I even did a factory reset which brings me to my second problem: I lost the data I thought I'd backed up.
So I'm not worried about recovering this data, I'm fairly certain I'll be able to get it back if I can get this USB working, but I'm out of ideas. I know it's not my drivers, because 3 different PC's manage to detect the other S3 without a hitch.
I've removed the battery, the sim card, rebooted, booted in download mode. Still nothing.
Any ideas?
PS: First post FTW. I'm not one to ask for these things unless I've exhausted all other resources, so if there is actually a working solution I've missed, I apologise in advance.
Click to expand...
Click to collapse
Use the motherboard usb ports. They are at the back of the cpu.
Sent from my GT-I9300 using xda app-developers app
JellyYogurt said:
Use the motherboard usb ports. They are at the back of the cpu.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I'm failing to see what your post is trying to accomplish. You're a senior member here. Did you read my post at all, beyond the title?
JellyYogurt said:
Use the motherboard usb ports. They are at the back of the cpu.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Are you having a off day
Treeofl1 said:
I'm failing to see what your post is trying to accomplish. You're a senior member here. Did you read my post at all, beyond the title?
Click to expand...
Click to collapse
I think JellyYogurt was having a off day he usually gives good advice
Did you manage to sort your problem out?
tallman43 said:
Are you having a off day
I think JellyYogurt was having a off day he usually gives good advice
Did you manage to sort your problem out?
Click to expand...
Click to collapse
Lol, I assumed as much. I deduced that the microUSB port must have had some form of internal breakage. Which is fine, I'll get that repaired if I can. I failed to mention it's a family member's phone. So I'm a bit weary of doing too much hacking/flashing, etc.
I did manage to root it with that Aragorn rooting app, I forget the name. I then installed DiskDigger and recovered some images, a good start. I'm still somewhat lost as to how I can recover XML and VCF files, as DiskDigger doesn't seem to support such formats. Those were my SMS and contact backups.
PS: I appreciate all the help so far Tallman, many thanks
Treeofl1 said:
I'm failing to see what your post is trying to accomplish. You're a senior member here. Did you read my post at all, beyond the title?
Click to expand...
Click to collapse
Sry. I suppose ur thread means tat ur pc will not show ur phone? Like there is no pop up for the phone connected and view the files? If so, connect the usb wire to the back of the cpu and it might work. If u dun mean tat, I am sry i misunderstood.
Sent from my SM-N9005 using xda app-developers app
JellyYogurt said:
Sry. I suppose ur thread means tat ur pc will not show ur phone? Like there is no pop up for the phone connected and view the files? If so, connect the usb wire to the back of the cpu and it might work. If u dun mean tat, I am sry i misunderstood.
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Lol not exactly dude, but thanks anyway. I did try multiple USB ports initially.
i apologize if this is already covered on this ( immense) forum but i couldn't find anything that related,
i have root access, and full adb, but i cant get fastboot even with adb commands.
i attempted to flash a faulty a20 tablet i had via sd install. and i obviously had a damaged flash, anyhow it wiped the tablet clean, the backlight still lights up. i can turn it on and off, and i can boot the boot loader.
is there anyway out of this, i want to install a recovery, but with no flashboot.......
please help! how do i get out of this?
hear is what i have done, i have looked around and there is some suggestion that my driver could be preventing fastboot seeing my tablet, so i have downloaded pdanet, and am using those drivers, no joy, exept that if i go to adb and reboot bootloader i loose my adb conection so i have to manually set the tablet again.
any idea why i cant access fastboot?
chriss2.0 said:
hear is what i have done, i have looked around and there is some suggestion that my driver could be preventing fastboot seeing my tablet, so i have downloaded pdanet, and am using those drivers, no joy, exept that if i go to adb and reboot bootloader i loose my adb conection so i have to manually set the tablet again.
any idea why i cant access fastboot?
Click to expand...
Click to collapse
I don't even know what tablet you are talking about. What is an a20?
Lgrootnoob said:
I don't even know what tablet you are talking about. What is an a20?
Click to expand...
Click to collapse
my apoligys
http://www.ebay.co.uk/itm/351019060457?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1439.l2649
cheap and cheerful chinese thing
chriss2.0 said:
my apoligys
http://www.ebay.co.uk/itm/351019060457?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1439.l2649
cheap and cheerful chinese thing
Click to expand...
Click to collapse
I'm sorry to say that I won't be that helpful in this discussion because I'm not sure of the workings of this tablet through hands on experience.
So your out of luck. :/
But I can say, if the flash is faulty. Then how would a reinstall fix anything?
Lgrootnoob said:
I'm sorry to say that I won't be that helpful in this discussion because I'm not sure of the workings of this tablet through hands on experience.
So your out of luck. :/
But I can say, if the flash is faulty. Then how would a reinstall fix anything?
Click to expand...
Click to collapse
ah well thanks for looking. i wonder if sd boot still works
Hey guys
I got root, but then I changed the build prop to the one given in this thread: http://forum.xda-developers.com/showthread.php?t=2782159
However it didn't boot properly,i.e. only the grey logo showed up, then black screen. No bootloop.
Then I thought factory reset would fix it?
no. now the pc doesn't recognise it. Please help! Same grey logo stuff but no PC recognition.
Edit:
No luck yet, but I remember a way I did before.It's not quite the same situation but...
I left the kindle on for a long time, and pressed the power button beyond the point from where it showed out of battery screen. It had like no batterypower at ALL. Yhen i plugged back up to PC and...
I'm trying it out now, if anyone is in the same position as me do the same!
Remember,charge only about 1-2%,if it doesn't work!
Thank you guys a LOT for support! I am in process of getting adb and stuff to work on linux...
let's see how it goes...
ferrouskid said:
Hey guys
I got root, but then I changed the build prop to the one given in this thread: http://forum.xda-developers.com/showthread.php?t=2782159
However it didn't boot properly,i.e. only the grey logo showed up, then black screen. No bootloop.
Then I thought factory reset would fix it?
no. now the pc doesn't recognise it. Please help! Same grey logo stuff but no PC recognition.
Click to expand...
Click to collapse
Does adb work ?
Patrick4 said:
Does adb work ?
Click to expand...
Click to collapse
No, unfortunately!
Patrick4 said:
Does adb work ?
Click to expand...
Click to collapse
No,
well
ferrouskid said:
No,
Click to expand...
Click to collapse
That sucks..I didnt try to swap my whole prop build though.. I just modified my mine..I did it with rommanager lite...I do remember a permission problem if u did swap files or used file manager instead of propbuild editer...has any one got brave enough to try the fastboot option one row under the root option in chinese app?
jimyv said:
That sucks..I didnt try to swap my whole prop build though.. I just modified my mine..I did it with rommanager lite...I do remember a permission problem if u did swap files or used file manager instead of propbuild editer...has any one got brave enough to try the fastboot option one row under the root option in chinese app?
Click to expand...
Click to collapse
Man any ideas?
Thanks
Hashcode and I have talked about it. There IS a working fastboot, but you can't get to it with a fastboot cable, and it's very buggy and not too useful. So it sounds like you are SOL. Sorry. :/
Sent from my Amazon Tate using Tapatalk
?
ferrouskid said:
Man any ideas?
Thanks
Click to expand...
Click to collapse
Fastboot system files?
jimyv said:
Fastboot system files?
Click to expand...
Click to collapse
Wait I know android cowboy had the same problem some time ago. I'll ask him.
ferrouskid said:
Wait I know android cowboy had the same problem some time ago. I'll ask him.
Click to expand...
Click to collapse
If anyone is in the same situation as me,I'm trying stuff out. First things first,I remember I bricked the kindle a while back. I made sure it was out of battery and then charged it a LITTLE and tried. doing that now.
http://forum.xda-developers.com/showthread.php?t=2588608 QUOTE=ferrouskid;53393803]If anyone is in the same situation as me,I'm trying stuff out. First things first,I remember I bricked the kindle a while back. I made sure it was out of battery and then charged it a LITTLE and tried. doing that now.[/QUOTE]
Hi,
I was in the same situation. Luckily, the Kindle was semi-recognized with Linux (adb devices shows ??????? with no permissions), I just had to add the udev rules to allow the device listed in lsusb and then I was able to chmod build.prop to get everything back to work.
Hope it helps
Ptiwee said:
Hi,
I was in the same situation. Luckily, the Kindle was semi-recognized with Linux (adb devices shows ??????? with no permissions), I just had to add the udev rules to allow the device listed in lsusb and then I was able to chmod build.prop to get everything back to work.
Hope it helps
Click to expand...
Click to collapse
HI, you did the factory reset, too?
ARUSTORI said:
HI, you did the factory reset, too?
Click to expand...
Click to collapse
I didn't, though you should try my solution (I'd got a black screen after the grey logo).
I'm sorry but I won't try the factory reset to see if it works
I have the same problem currently, I'll use ubuntu and see if my kindle can get recognized, the cable I'm using also has a light on it so atleast we know its not dead lol.
Ause said:
I have the same problem currently, I'll use ubuntu and see if my kindle can get recognized, the cable I'm using also has a light on it so atleast we know its not dead lol.
Click to expand...
Click to collapse
I'll be over the moon if this works, adb is installed, now waiting for flat kindle to charge...
Ptiwee said:
Hi,
I was in the same situation. Luckily, the Kindle was semi-recognized with Linux (adb devices shows ??????? with no permissions), I just had to add the udev rules to allow the device listed in lsusb and then I was able to chmod build.prop to get everything back to work.
Hope it helps
Click to expand...
Click to collapse
Please expand on that. Thank you so much.
Ptiwee said:
Hi,
I was in the same situation. Luckily, the Kindle was semi-recognized with Linux (adb devices shows ??????? with no permissions), I just had to add the udev rules to allow the device listed in lsusb and then I was able to chmod build.prop to get everything back to work.
Hope it helps
Click to expand...
Click to collapse
Can you please give the commands that you used?
That would be very helpful...
Thanks a lot for the help though
ferrouskid said:
Can you please give the commands that you used?
That would be very helpful...
Thanks a lot for the help though
Click to expand...
Click to collapse
Connect your device to your computer.
By typing "adb devices", you should get this output :
Code:
List of devices attached
???????????? no permissions
Then type "lsusb" and note the ID of the Google Device (Should be 18d1:0001, but I'm not sure you will get the same).
Edit the file "/etc/udev/rules.d/51-android.rules" and add the following lines (If the file doesn't exists create it). Replace 18d1 and 0001 with the values you get in lsusb :
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666"
SUBSYSTEM=="usb",ATTR{idVendor}=="18d1",ATTR{idProduct}=="0001",SYMLINK+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="18d1",ATTR{idProduct}=="0001",SYMLINK+="android_fastboot"
Run "sudo chmod a+r /etc/udev/rules.d/51-android.rules".
Restart your computer and you should be access your device using "adb shell".
Follow this post to restore your device : http://forum.xda-developers.com/showpost.php?p=53388919&postcount=23
Crap. I dont have access to a linux OS..ill have to call amazon i think.
Sent from my LG-D800 using XDA Premium 4 mobile app
Please forgive my ignorance I am very new to this. I just want to flash the new firmware to the nexus 9 manually. I have downloaded minimal adb and fastboot but it doesn't find my device. I have enabled developer mode and allow usb oem ect but nothing when I type the commands it says waiting for device and nothing happens, obviously I am missing something obvious, but if you could please help me out I would be grateful.
Did you let your device RSA footprint be recognised?
Did you run adb commands at the right directory?
AjunNg said:
Did you let your device RSA footprint be recognised?
Did you run adb commands at the right directory?
Click to expand...
Click to collapse
Not sure what the first question means??, I think I ran the adb commands at the right directory??
anobium said:
Not sure what the first question means??, I think I ran the adb commands at the right directory??
Click to expand...
Click to collapse
Means when you connected the device to the PC with USB debugging, there should have been a pop up asking you if you'll let the device blah blah.
You need to press OK.
AjunNg said:
Means when you connected the device to the PC with USB debugging, there should have been a pop up asking you if you'll let the device blah blah.
You need to press OK.
Click to expand...
Click to collapse
No never had a popup, asking me toconfirm???.
Unplug it and replug it until it does.
Uncheck USB debugging and recheck it until it does.
AjunNg said:
Did you let your device RSA footprint be recognised?
Did you run adb commands at the right directory?
Click to expand...
Click to collapse
AjunNg said:
Unplug it and replug it until it does.
Uncheck USB debugging and recheck it until it does.
Click to expand...
Click to collapse
Think ive found my problem in device manager on my computer the android device has a yellow exclamation mark saying no a driver present, were do I get the android driver for windows??
Use Wugfresh's Nexus toolkit, and use the full driver installation.
anobium said:
Think ive found my problem in device manager on my computer the android device has a yellow exclamation mark saying no a driver present, were do I get the android driver for windows??
Click to expand...
Click to collapse
Right click on it. Go to where it lets you pick from a list on your computer. Choose android adb interface driver, or something along those lines
Sent from my Nexus 9 using XDA Free mobile app
AjunNg said:
Use Wugfresh's Nexus toolkit, and use the full driver installation.
Click to expand...
Click to collapse
This program is the bollocks, for a newbie like me, went through the steps and it recognised my device, only 1 question do I need to root to update stock firmware as I cant see option to update without rooting.
By bollocks I mean brilliant.
No root needed to update.
anobium said:
This program is the bollocks, for a newbie like me, went through the steps and it recognised my device, only 1 question do I need to root to update stock firmware as I cant see option to update without rooting.
By bollocks I mean brilliant.
Click to expand...
Click to collapse
oh you silly English person.
the toolkit will get you back to stock. wug is working on a revision that will properly format the data partition to decrypt the tablet. the tool is best for force flashing and renewing your device as if you just unboxed the device with no root. the option to install a recovery and root the device is used after you are happy with the first boot and freshness of your devices. other tools included are just simplified press of the button commands that save you the time of opening a cmd shell.
key things to remember about the n9, absolutely make sure you enable the OEM unlock in developer options. and to my understanding NEVER uncheck it. there is a thread here about that "feature"
Sent from my Nexus 9 using Tapatalk
Migamix said:
oh you silly English person.
the toolkit will get you back to stock. wug is working on a revision that will properly format the data partition to decrypt the tablet. the tool is best for force flashing and renewing your device as if you just unboxed the device with no root. the option to install a recovery and root the device is used after you are happy with the first boot and freshness of your devices. other tools included are just simplified press of the button commands that save you the time of opening a cmd shell.
key things to remember about the n9, absolutely make sure you enable the OEM unlock in developer options. and to my understanding NEVER uncheck it. there is a thread here about that "feature"
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
And what's wrong with fastboot? No need for a tool kit
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
And what's wrong with fastboot? No need for a tool kit
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Ok i get to flashing the image and it goes to quick and comes up with errors saying I have different firmware image on my device?, I thought that was the idea im going from lrx21r to lrx22c, do I have to put I already have the 22c in the option list??.
jd1639 said:
And what's wrong with fastboot? No need for a tool kit
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
there is nothing wrong with ADB, or fastboot, if you use it exclusively, good for you.
as the OP title sais, it is not expected for a new user, and even some experienced users, to have such a firm grasp of the ways of the mighty command line, and the fact that the toolkit gathers all of the files in one convenient place, is not without its bonus. i dont know, nor do i really care who started the whole elitist "toolboxes are for lamers", or whatever. toolboxes are nothing more than their name suggests , tool-boxes, to help when we need it. they are nothing more than an interface to commands, much like you running a GUI on top of your OS, or are also running command line only for your primary computer. xda, is designed and expected to be help for all who want to know, not a pond of elitists that would rather brag they have overclocked their device, water cooled it, but can still make a grilled cheese sandwich on their CPU. i have email accounts older than many of the forum members here, so not too much impresses me in that 1337 area. im here to help if i can, and learn if i need to., so since im here alot, im always learning.