[root] rooted uRamdisk for 1.1 update - Nook Touch Android Development

For those who prefer manually rooting their NST with the NookDevs method, here's a modified uRamdisk based on the 1.1 update:
WiFi version:
uRamdisk_1_1_rooted_wifi
USB version:
uRamdisk_1_1_rooted_usb
As always, take your time to do a proper backup first!

ros87 said:
For those who prefer manually rooting their NST with the NookDevs method, here's a modified uRamdisk based on the 1.1 update:
uRamdisk_1_1_rooted
As always, take your time to do a proper backup first!
Click to expand...
Click to collapse
This USB access or Wifi access? If it's USB access I can add it to TouchNooter instead of repacking my own version of uRamdisk

GabrialDestruir said:
This USB access or Wifi access? If it's USB access I can add it to TouchNooter instead of repacking my own version of uRamdisk
Click to expand...
Click to collapse
Added both wifi and usb-only version to OP.

If I use this method can I add nook color tools back to my touch?

ryanpl said:
If I use this method can I add nook color tools back to my touch?
Click to expand...
Click to collapse
root is root, you can adb install / push whatever you want
If you're unsure about doing things manually you should probably wait for GabrialDestruir to release a updated version of TouchNooter.

How is the adb over usb supposed to work? I replaced the uRamdisk with the one with usb for 1.1 after booting with noogie, but when i hook the nook up to my computer with usb and do "adb devices" i don't see anything.

check adb links from http://forum.xda-developers.com/showthread.php?t=1138564
In short: on linux dbus rules (tested, working). on windows you need drivers,

cceerrtt said:
check adb links from http://forum.xda-developers.com/showthread.php?t=1138564
In short: on linux dbus rules (tested, working). on windows you need drivers,
Click to expand...
Click to collapse
Ahha, thank you! Will try with the windows drivers.

nickveldrin said:
Ahha, thank you! Will try with the windows drivers.
Click to expand...
Click to collapse
The usb ramdisk works just fine.
Getting the drivers installed on windows can be a bit of a pain

Yeah, the xboxexpert drivers I installed for ADB over USB just mucked things up for me. Gonna stick to wifi for now, I suppose...
-e
P.S. Yay I can finally post here!
---------- Post added at 07:09 PM ---------- Previous post was at 06:36 PM ----------
A big thank you to ros for this. With the ADB over WiFi uRamdisk, WiFi works again! (As does adb, doy)
-e

hmm...
I have had some amount of success with this, but it doesn't seem to be complete. Followed instructions and copied uRamdisk wifi over, and can get adb to work over wireless, but for some reason superuser is borked. I don't think I actually have root, although when I login through adb shell, it displays the #. Gonna try to do it again.
LastSilmaril said:
Yeah, the xboxexpert drivers I installed for ADB over USB just mucked things up for me. Gonna stick to wifi for now, I suppose...
-e
P.S. Yay I can finally post here!
---------- Post added at 07:09 PM ---------- Previous post was at 06:36 PM ----------
A big thank you to ros for this. With the ADB over WiFi uRamdisk, WiFi works again! (As does adb, doy)
-e
Click to expand...
Click to collapse

vatoamigo said:
I have had some amount of success with this, but it doesn't seem to be complete. Followed instructions and copied uRamdisk wifi over, and can get adb to work over wireless, but for some reason superuser is borked. I don't think I actually have root, although when I login through adb shell, it displays the #. Gonna try to do it again.
Click to expand...
Click to collapse
Not entirely sure what your mean?
If you got adb access with root prompt (#), then the uRamdisk is doing exactly what it should
If you need su and Superuser, then you have to add them to your system manually, this is not related to the uRamdisk.

ah
Yeah, I suppose you're right, that's the problem. I guess I need to upload su and superuser manually. Do you have a link that shows me how to do that? I looked everywhere for a superuser.apk, but can't get market working.

Everywhere? I guess you should try google at the first place. It took me 10 second to find this link.
http://nookdevs.com/NookColor_Installing_su_and_the_Superuser_app
It is actually the same howto I used some time ago.

the secrets of google...
cceerrtt said:
Everywhere? I guess you should try google at the first place. It took me 10 second to find this link.
http://nookdevs.com/NookColor_Installing_su_and_the_Superuser_app
It is actually the same howto I used some time ago.
Click to expand...
Click to collapse
I appreciate the link. I actually did try google, but apparently wasn't successful. Thanks.

Hi, BIG thanks for the file, works like a charm.
Edit (don't want to add meaningless message to this tread)
Thanks for your kindness.

UomoNero said:
I have a strange problem with superuser, apparently installing su mess with my nook; my nook think that the battery is 0% but when i uninstall su and superuser package works fine.
I'm the only one with this problem? Is somehow related to 1.1 update?
Thanks for your kindness
Click to expand...
Click to collapse
That question is better asked in a new thread as it's not related to uRamdisk
fwiw, I pulled su from TouchNooter and Superuser.apk from my phone and it works without problems on 1.1.0.
In your case I'd try Settings->Device Info->Erase and Deregister Device
This will force cache and databases to be rebuilt which often solves strange problems like that.

Can't get this to work... I've installed a fresh 1.1.0 update, changed ramdisk to support adb through usb, changed both adb_usb and android_winusb. After installing drivers when i connect my nook it shows as "Android ADB interface", but adb devices shows nothing
EDIT: Solved! Had to modify android_winusb a little bit more...

ros87 said:
For those who prefer manually rooting their NST with the NookDevs method, here's a modified uRamdisk based on the 1.1 update:
WiFi version:
uRamdisk_1_1_rooted_wifi
USB version:
uRamdisk_1_1_rooted_usb
As always, take your time to do a proper backup first!
Click to expand...
Click to collapse
Multiupload is down...

Googie2149 said:
Multiupload is down...
Click to expand...
Click to collapse
And still is.
Sorry for the necromancy, but can somebody please re-upload those IMG files? thanks!

Related

How to verify your phone is "rooted"

Hi all,
I've recently flashed to MoDaCo 2.2 however I'm just assuming my device got rooted at the same time - but I don't know for sure.
What's the easiest way to verify it has been rooted?
Thanks!
1. use search forum or google..
2. adb shell su
thats it
It keeps saying device not found, but works for my mytouch and G1. Any ideas?
Breakthecycle2 said:
It keeps saying device not found, but works for my mytouch and G1. Any ideas?
Click to expand...
Click to collapse
Have you enabled USB debugging? Settings-Applications-Development
trice1921 said:
Have you enabled USB debugging? Settings-Applications-Development
Click to expand...
Click to collapse
Yup did that too...my other phones pick it up no issues.
I also get the exact same problem (i.e. Device not found) - I guess it is a hint that it isn't rooted maybe (although I assumed it was automatic with flashing MoDaCo 2.2)?
Sound like a problem with your driver. But you should have been able to connect before to install the custom rom?
Download astro file manager and you should be able to see files that you couldn't see before
Sound like a problem with your driver. But you should have been able to connect before to install the custom rom?
Download astro file manager and you should be able to see files that you couldn't see before
robboy said:
Sound like a problem with your driver. But you should have been able to connect before to install the custom rom?
Download astro file manager and you should be able to see files that you couldn't see before
Click to expand...
Click to collapse
OK I got a work around. You need to restore your PC to a point BEFORE you plug in your hero. I did this and now works great.
How I might undo root process?
I think that replace chmod 4755 permision to default in the "su" file, but I don't know how to
No need to do, but I'm intererested in the concept
There is a thread on how to unroot:
Open Windows Console and connect Hero with PC
write this:
fastboot boot cm-hero-recovery.img
adb shell mount /system
adb shell rm /system/app/Superuser.apk
adb shell rm /system/bin/su
adb shell reboot
Click to expand...
Click to collapse
ZenorGR said:
There is a thread on how to unroot:
Click to expand...
Click to collapse
I'm sorry but could don't find ...Thanks!!!
its a sticky.. its really hard NOT to find it
edit: okay it WAS a sticky, but its also on the first site in this subforum.. so no problem to at least SEE it

[Q]Linux Root Issues[libusb errors]

Firstly, I'd like to say hello as I just recently purchased my E4GT and moved over from a HeroC. So far the community has seemed pretty warm and helpful so I'll just go ahead and get down to it: I've searched. I've Googled. I've even Youtubed but nothing seems to have an answer to my problem.
I'm running Ubuntu 11.10, up to date, with Heimdall 1.3.1 installed. My problem is that even though the device is detected in download mode, when I run
Code:
heimdall flash --kernel zImage
I keep coming up with this error
Code:
Initialising connection...
Detecting device...
libusb couldn't open USB device /dev/bus/usb/001/016: Permission denied.
libusb requires write access to USB device nodes.
ERROR: Failed to access device. libusb error: -3
Now I will admit that while I have read and reread the wiki looking for my mistake, I am fresh to the E4GT and Samsung altogether, so if this is some simpleton error I would not be entirely surprised. I'm at my wits end as I have the drivers, verified so with an ADB reboot command, so I'm not sure what my issue is. Any and all advice/help/guidance will be hugely appreciated.
Very simple fix. Follow the steps you would follow to get adb running.
---------- Post added at 08:36 AM ---------- Previous post was at 08:33 AM ----------
Here http://forum.xda-developers.com/showpost.php?p=19446284&postcount=62
CBowley said:
Very simple fix. Follow the steps you would follow to get adb running.
---------- Post added at 08:36 AM ---------- Previous post was at 08:33 AM ----------
Here http://forum.xda-developers.com/showpost.php?p=19446284&postcount=62
Click to expand...
Click to collapse
Thanks for the info, unfortunately adb is already detecting my device. Ran through the setup anyways and still the same error. I'm wondering what's causing libusb to not rw at this point.
EDIT: Gonna reboot, then give it a shot with sudo added to the flash command. May or may not work, but I'm willing to try anything before I give up and hunt down a friend with a windows machine.
EDIT2: That's exactly what it needed! Now I'm officially rooted
Sent from my SPH-D710 using XDA
Will there be any way to solve the exactly same issue but running on Windows? Btw, I am running Windows 10.
Similar problem
malatewodn said:
Will there be any way to solve the exactly same issue but running on Windows? Btw, I am running Windows 10.
Click to expand...
Click to collapse
Same problem with my tablet, trying to install TWRP
Hi. I've installed Android SDK and the API for the device (Android 4.2.2, samsung SMT110 for me, API 17). After, Heimdall was running without any problem.
My system is windows 10

[Q] Kindle Fire with 6.3 Help with Rooting Please

Hi,
I am a total noob. I don't even know the proper expressions for this whole thing.
So this is my case:
I am outside the US and bought the Kindle Fire with a 6.3 firmware, couple of days ago.
Being curious about what it all can do, created a fake account with a test credit card as I read somewhere in the net.
Then downloaded the KFU 0.9.5 and rooted the device, everything went according to the plan, so I thought.
Then I discovered I had to use something called Market Opener to install other apps. But this Market Opener never worked.
So I found out that I had to change permissions. But this cannot happen as I get that message that adb services can not run in production builds etc. whatever that may mean.
So I downloaded Android SDK, followed the instructions installed it but I still cannot get into the root and change folder permissions. Sometimes it recognizes the device, sometimes not and when it does it tells me the same thing as above.
Then I would need some .apk to do the thing on the device but I cannot install those as I don't have the Market Opener or the Google Play and I cannot get those if I don't have superuser permissions to change things in Folders.
Basically I have been spending the last 3 days in searching the net for answers but to no avail.
So, can someone help me please? What I need to do is being able to install some apps including Market Opener / Google Play and being able to watch Amazon VOD. Is this possible?
Please bear in mind that I have no clue of the specific language, i.e. I don't know what flash is and how to do it nor I know how to do a backup and restore or how to reset everything in the original state.
SO if some of you have the patience to help, please advice me with some noob language so that I can understand.
Thanks in advance for the help that will come
Are you looking to put a custom rom on it or just root? If you're looking to keep Amazon services, you can put MoDaCo's rom on it, which is just like your kindle out of the box with a few extra bells and whistles. There are alot of guides floating around on how to get ADB working. There's an excellent beginners guide in the General section that I highly advise checking out.
Noob terms: if you want to keep the Amazon experience, I reccomend MoDaCo. Look for it in the development fourms.
brainchow said:
Are you looking to put a custom rom on it or just root? If you're looking to keep Amazon services, you can put MoDaCo's rom on it, which is just like your kindle out of the box with a few extra bells and whistles. There are alot of guides floating around on how to get ADB working. There's an excellent beginners guide in the General section that I highly advise checking out.
Noob terms: if you want to keep the Amazon experience, I reccomend MoDaCo. Look for it in the development fourms.
Click to expand...
Click to collapse
Thanks for ur answer.
I have read a lot of guides out there but I seem not to be able to get the ADB working as I always get the message I gave in the original post plus the fact that sometimes it recognizes the device and sometimes not.
I have read the beginners guide which was excellent but without the ADB working there is little I can do I suppose.
As I wrote, I want to play with the device to see what it is able to do and want to use the Amazon VOD if possible. I.e. I would like to be able to use Google Play to get apps on will and still keep the Amazon services. Would that be possible with the MoDaCo staff?
Ok. I downloaded the MoDaCo staff.
Must I reset the kindle to the factory settings before I install that? If yes, how?
And how do I flash it?
Make sure you are in fact rooted.
You seem like you know enough about adb to try the following commands.
adb shell
ls /system/xbin
Look for a file called "su" in the list
Then...
ls /system/app
Look for a file called "Superuser.apk"
A lack of either of these means you're not rooted and may be the source of your problems
If you are trying to change system file permissions through adb...
adb root
adb remount
adb shell chmod blah /blah/blah/yadayada
Just don't literally type "blah /blah/blah/yadayada"
Sent from my Amazon Kindle Fire using xda premium
a factory reset won't really help you because you're basically replacing the operating system. pretty sure all amazon services are working with modaco. to install it, look around for a guide on how to install something called firefirefire (FFF) and TWRP. pretty sure that can all be done with kfu in a couple clicks. then copy the modaco zip onto your kindle, go into the wipe menu and clear out system, cache, dalvik cache, and data (factory reset), then go into install and choose the modaco zip. reboot and you should be set.
soupmagnet said:
Make sure you are in fact rooted.
You seem like you know enough about adb to try the following commands.
adb shell
ls /system/xbin
Look for a file called "su" in the list
Then...
ls /system/app
Look for a file called "Superuser.apk"
A lack of either of these means you're not rooted and may be the source of your problems
If you are trying to change system file permissions through adb...
adb root
adb remount
adb shell chmod blah /blah/blah/yadayada
Just don't literally type "blah /blah/blah/yadayada"
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
Thank you for your answer.
I would gladly follow your advice but the adb does not find my device. I don't know whether this is normal and if I must reboot my PC.
The kfu also gives me an offline status...
brainchow said:
a factory reset won't really help you because you're basically replacing the operating system. pretty sure all amazon services are working with modaco. to install it, look around for a guide on how to install something called firefirefire (FFF) and TWRP. pretty sure that can all be done with kfu in a couple clicks. then copy the modaco zip onto your kindle, go into the wipe menu and clear out system, cache, dalvik cache, and data (factory reset), then go into install and choose the modaco zip. reboot and you should be set.
Click to expand...
Click to collapse
Thanks again for the fast answer. I am impressed!
Doesn't the FFF and the TWRP get installed automatically with the kfu?
its most likely your computer. a reboot might help. if not, how did you install the drivers? are you using a mac or pc? try installing the drivers that came bundled with KFU.
if you're using a PC, go into device manager and see if something about android ADB pops up. if not, it's your drivers.
---------- Post added at 07:53 PM ---------- Previous post was at 07:51 PM ----------
GreekCY said:
Thanks again for the fast answer. I am impressed!
Doesn't the FFF and the TWRP get installed automatically with the kfu?
Click to expand...
Click to collapse
haha, no problem .
if FFF was installed, you should see a picture of fire in a caution sign or an android logo over the kindle fire logo when you boot it up. if all you see is kindle fire, then you don't have fff. im pretty sure you need fff to get into twrp. if fff is installed, you should be able to hop into fastboot and install twrp if it's not installed yet.
brainchow said:
its most likely your computer. a reboot might help. if not, how did you install the drivers? are you using a mac or pc? try installing the drivers that came bundled with KFU.
if you're using a PC, go into device manager and see if something about android ADB pops up. if not, it's your drivers.
Click to expand...
Click to collapse
I am using a PC ( a netbook, don't laugh, I'm on vacation!!)
I installed the drivers using the install_bat from the kfu.
In device manager I see Android Phone and underneath Android Composite ADB Interface...
interesting. check my previous post and see if you have FFF installed. adb should be working fine if device manager can find it. if you can, run adb devices into cmd and see if it picks up your kindle. not sure if the stock rom has a development switch in the settings.. if there's an option to enable usb debugging, make sure that is on. if not, just try moving usb ports and running adb devices.
If adb has trouble recognizing your device, it means it's a driver issue. Either Windows, KFU or a combination of the two causes the drivers to fail for some reason.
Uninstall/delete your current drivers in device manager (may require reboot)
Turn your Kindle off
Reinstall drivers
Turn your Kindle on
Retry adb commands
Sent from my Amazon Kindle Fire using xda premium
brainchow said:
interesting. check my previous post and see if you have FFF installed. adb should be working fine if device manager can find it. if you can, run adb devices into cmd and see if it picks up your kindle. not sure if the stock rom has a development switch in the settings.. if there's an option to enable usb debugging, make sure that is on. if not, just try moving usb ports and running adb devices.
Click to expand...
Click to collapse
I have FFF as I see the fire in a caution sign (yellow triangle thing right?)
ADB still doesn't pick my kindle after a PC restart.
No usb debugging available in the stock rom.
I will uninstall and reinstall the drivers from device manager.
Thanks again for your prompt help. I am oblidged!
GreekCY said:
I have FFF as I see the fire in a caution sign (yellow triangle thing right?)
ADB still doesn't pick my kindle after a PC restart.
No usb debugging available in the stock rom.
I will uninstall and reinstall the drivers from device manager.
Thanks again for your prompt help. I am oblidged!
Click to expand...
Click to collapse
that's fantastic... if you have FFF, try pressing the power button a couple times as it turns on and see if you can get into recovery. you shouldn't need adb now. if you can get into recovery, just wipe and flash the new rom. if you don't, you can use fastboot to install it.
brainchow said:
that's fantastic... if you have FFF, try pressing the power button a couple times as it turns on and see if you can get into recovery. you shouldn't need adb now. if you can get into recovery, just wipe and flash the new rom. if you don't, you can use fastboot to install it.
Click to expand...
Click to collapse
Ok...I reinstalled the drivers
now ADB gets the kindle
I do adb shell
then ls / system /xbin
no such file or directrory
the same goes with the
ls / system / app
But if I give su I get
su
#
Now what?
And in which directory should I transfer the MoDaCo Rom?
GreekCY said:
Ok...I reinstalled the drivers
now ADB gets the kindle
I do adb shell
then ls / system /xbin
no such file or directrory
the same goes with the
ls / system / app
But if I give su I get
su
#
Now what?
Click to expand...
Click to collapse
SU (substitute user) in shell is different from the su binary
Make sure you are typing "L"s, not "i"s then /system/xbin
Sent from my Amazon Kindle Fire using xda premium
soupmagnet said:
SU (substitute user) in shell is different from the su binary
Make sure you are typing "L"s, not "i"s then /system/xbin
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I really do type "L"...still ls/system/xbin: not found
modaco can go anywhere in the kindle.. just copy it somewhere. then press the power button a couple times when FFF comes up and see if you can get into twrp.
brainchow said:
modaco can go anywhere in the kindle.. just copy it somewhere. then press the power button a couple times when FFF comes up and see if you can get into twrp.
Click to expand...
Click to collapse
Guys? I just installed ModaCo and it seems it works fine. Google Play seems to work and all my data are still there (I mean the books I uploaded). If this is right then.... THANKS TO ALL OF YOU SO MUCH!!!!
Drinks are on me! Now I go to sleep! Will keep you informed!!!
Thanks again!!!!
GreekCY said:
I really do type "L"...still ls/system/xbin: not found
Click to expand...
Click to collapse
Space between ls and /system/xbin and no other spaces
It IS there, your Kindle wouldn't work otherwise
Sent from my Amazon Kindle Fire using xda premium
GreekCY said:
I really do type "L"...still ls/system/xbin: not found
Click to expand...
Click to collapse
if you want to use adb, should be ls /system/xbin. make sure you put the space after the ls. i would still recommend flashing modaco nevertheless... that shouldn't need adb. just maybe fastboot if your recovery isnt installed.
---------- Post added at 08:59 PM ---------- Previous post was at 08:57 PM ----------
GreekCY said:
Guys? I just installed ModaCo and it seems it works fine. Google Play seems to work and all my data are still there (I mean the books I uploaded). If this is right then.... THANKS TO ALL OF YOU SO MUCH!!!!
Drinks are on me! Now I go to sleep! Will keep you informed!!!
Thanks again!!!!
Click to expand...
Click to collapse
no problem... enjoy
i would still recommend wiping data and the two caches to ensure that it's bug free. but if everything works fine, so be it.
have fun

Mounting SD card in CWM to PC

So I think I am SOL, but I wanted to ask you guys first.
My Nexus wont boot past the Google screen all of a sudden today. So I am going to attempt the toolkit version of returning to stock later. But before I do that, I want to try and salvage my pictures from the internal memory.
Is there a way to mount the internal storage to my PC so I can pull the files off?
I thought not having an SD card was no big deal, til now when im about to lose 500+ pictures.
Am I screwed?
Thanks
threepio said:
So I think I am SOL, but I wanted to ask you guys first.
My Nexus wont boot past the Google screen all of a sudden today. So I am going to attempt the toolkit version of returning to stock later. But before I do that, I want to try and salvage my pictures from the internal memory.
Is there a way to mount the internal storage to my PC so I can pull the files off?
I thought not having an SD card was no big deal, til now when im about to lose 500+ pictures.
Am I screwed?
Thanks
Click to expand...
Click to collapse
You can adb pull the dcim folder to your PC.
Edit: You would also be better served in the long run learning to return to stock yourself instead of using a toolkit.
http://forum.xda-developers.com/showthread.php?t=1626895
JM2C
3rdstring said:
You can adb pull the dcim folder to your PC.
Edit: You would also be better served in the long run learning to return to stock yourself instead of using a toolkit.
http://forum.xda-developers.com/showthread.php?t=1626895
JM2C
Click to expand...
Click to collapse
Thanks JM2C. I thought that I might be able to do the ADB pull. I have no idea how ADB works though...
Thanks for the link on the
It's not too complicated. It is a lot of steps but a developer novice can follow the instructions to install and use adb just to pull a few files. Also that's one reason why I let dropbox sync my photos as I take them, so if something happens I have an auto cloud backup.
Sent from my Galaxy Nexus using xda premium
---------- Post added at 05:56 PM ---------- Previous post was at 05:51 PM ----------
threepio said:
So I think I am SOL, but I wanted to ask you guys first.
My Nexus wont boot past the Google screen all of a sudden today. So I am going to attempt the toolkit version of returning to stock later. But before I do that, I want to try and salvage my pictures from the internal memory.
Is there a way to mount the internal storage to my PC so I can pull the files off?
I thought not having an SD card was no big deal, til now when im about to lose 500+ pictures.
Am I screwed?
Thanks
Click to expand...
Click to collapse
Here is a link to some basic adb instructions:
http://forum.xda-developers.com/showthread.php?t=517874
exportsmedia said:
It's not too complicated. It is a lot of steps but a developer novice can follow the instructions to install and use adb just to pull a few files. Also that's one reason why I let dropbox sync my photos as I take them, so if something happens I have an auto cloud backup.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
So I found a tutorial for setting up ADB for the nexus, but all i can get into is the bootloader and the recovery. I cant get my computer to recognize my phone...even though its plugged in. So how would ADB work?
threepio said:
So I found a tutorial for setting up ADB for the nexus, but all i can get into is the bootloader and the recovery. I cant get my computer to recognize my phone...even though its plugged in. So how would ADB work?
Click to expand...
Click to collapse
If you have a custom recovery you should be able to get adb access. You just need to set up the drivers
I believe the previous link I gave even has a small platform-tools download so you wouldn't have to set up the sdk.
3rdstring said:
If you have a custom recovery you should be able to get adb access. You just need to set up the drivers
I believe the previous link I gave even has a small platform-tools download so you wouldn't have to set up the sdk.
Click to expand...
Click to collapse
So when i go into device manager I have Android 1.0 listed under other devices. But when i try to have windows search for drivers, it doesnt find anything. Is ther a specific driver from samsung that I can download somewhere and then point the driver update to it?
threepio said:
So when i go into device manager I have Android 1.0 listed under other devices. But when i try to have windows search for drivers, it doesnt find anything. Is ther a specific driver from samsung that I can download somewhere and then point the driver update to it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
3rdstring said:
http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Click to expand...
Click to collapse
Ok that worked I now have the android bootloader interface in my device manager....now what? When I open cmd and type "adb devices" nothing comes up
threepio said:
Ok that worked I now have the android bootloader interface in my device manager....now what? When I open cmd and type "adb devices" nothing comes up
Click to expand...
Click to collapse
Boot into recovery (You do have a custom recovery installed?)
3rdstring said:
Boot into recovery (You do have a custom recovery installed?)
Click to expand...
Click to collapse
I have Clockwork mod installed. and still when i try adb devices nothing comes up.
So I got something to work. When I typed adb devices under "list of adb devices attached" i got 0146A5B1301C007 recovery
Is this my phone?
threepio said:
So I got something to work. When I typed adb devices under "list of adb devices attached" i got 0146A5B1301C007 recovery
Is this my phone?
Click to expand...
Click to collapse
yes
now im trying to get the command right.
what is the whole string for adb pull?
*edit*
I found that is---> adb pull <remote> <local>
So I type " adb pull /sdcard/dcim c:\nexus
(i made a file on the root of my c: drive to make it easy to type to pull the files.
but it says /sdcard/dcim does not exist.
threepio said:
now im trying to get the command right.
what is the whole string for adb pull?
Click to expand...
Click to collapse
I've pushed a ROM a few times, never pulled. I would try...
adb pull /sdcard/DCIM c:\
or
adb pull /data/media/DCIM c:\
threepio said:
now im trying to get the command right.
what is the whole string for adb pull?
*edit*
I found that is---> adb pull <remote> <local>
So I type " adb pull /sdcard/dcim c:\nexus
(i made a file on the root of my c: drive to make it easy to type to pull the files.
but it says /sdcard/dcim does not exist.
Click to expand...
Click to collapse
MOTHER EFFING CAPTALIZATIONS! GOT IT WOOOOO pulling all my files as we speak. I wasnt typing the directories with captial letters like they are. I was typing all lowercase. gosh dangit!
THANK YOU THANK YOU THANK YOU
threepio said:
MOTHER EFFING CAPTALIZATIONS! GOT IT WOOOOO pulling all my files as we speak. I wasnt typing the directories with captial letters like they are. I was typing all lowercase. gosh dangit!
THANK YOU THANK YOU THANK YOU
Click to expand...
Click to collapse
Glad you got it working. As was mentioned previously DropBox photo syncing can be a lifesaver. :good:
3rdstring said:
Glad you got it working. As was mentioned previously DropBox photo syncing can be a lifesaver. :good:
Click to expand...
Click to collapse
You know i just got into dropbox. I am going to start using it more.
Now i gotta figure out how to restore the phone. Now that I have the pictures off it, i can toy with resetting it to stock. and starting from the ground up.....fun...
Now I just flashed back to stock using the fastboot from the link posted on page one.
Thanks for your help guys
threepio said:
Thanks JM2C. I thought that I might be able to do the ADB pull. I have no idea how ADB works though...
Thanks for the link on the
Click to expand...
Click to collapse
qbking77 has a great YouTube video walking you thru it. Also has how to return to stock/unbrick
*This Jedi master be a Ninj-ESS*

Can't install drivers.

Ok, this isn't my first rodeo as I've owned many android devices including the old nexus 7. I'm trying to unlock and root this but I can't install the drivers. I tried the device manager method and when I search it can't find anything and I tried a website to manually do it by downloading a zip and choosing it to no avail. Any one have the link to the drivers as that website may not of been accurate or anyone have any other suggestions?
You need to unzip it first.
Username invalid said:
You need to unzip it first.
Click to expand...
Click to collapse
Yes I did that and it only had two folders that showed up while browsing in the update drivers part in device manager. One was AMD86 and the other was i3 something and neither of those matched the picture in the steps but I used the link given within the same tutorial.
http://developer.android.com/sdk/win-usb.html
Username invalid said:
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
Ok I still cannot install the drivers. When I downloaded the file provided in that link, there are no driver options at all. There are only two folders in which I described in my previous post and neither have drivers in them. I'm no noob and have done this plenty of times, I even tried to adb reboot bootloader and it says device not found and yes USB debugging is on so I'm assuming I can't do anything until I some how install the drivers.
Which website guide are you looking at?
Username invalid said:
Which website guide are you looking at?
Click to expand...
Click to collapse
The one on the site. Ok I installed SDK manager and I checked google usb drivers in it and it installed it, but when I do the adb commands it still says device not found -.-
C-4Nati said:
The one on the site. Ok I installed SDK manager and I checked google usb drivers in it and it installed it, but when I do the adb commands it still says device not found -.-
Click to expand...
Click to collapse
If nothing else works, you might consider partitioning your hard drive and installing a secondary OS. Both Windows 8.1 and Ubuntu worked for me no problem.
Code:
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
adb reboot bootloader
fastboot oem unlock
fastboot reboot-bootloader
cd Downloads
fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.img
adb push update-supersu-v1.51.zip /sdcard/Downloads
C-4Nati said:
The one on the site. Ok I installed SDK manager and I checked google usb drivers in it and it installed it, but when I do the adb commands it still says device not found -.-
Click to expand...
Click to collapse
Ok I installed the drivers correctly, I figured it out. Now when I try the adb commands it says device offline when it's clearly not lol...
I've got everything working now and unlocked and rooted. I appreciate all the help you have offered to me. I do not remember it being this difficult with the original Nexus 7 lol.
C-4Nati said:
Ok I installed the drivers correctly, I figured it out. Now when I try the adb commands it says device offline when it's clearly not lol...
Click to expand...
Click to collapse
Fastboot is all you need to root your device.
C-4Nati said:
I've got everything working now and unlocked and rooted. I appreciate all the help you have offered to me. I do not remember it being this difficult with the original Nexus 7 lol.
Click to expand...
Click to collapse
I'm having a similar problem with drivers, why don't you post how you solved it? I am trying on 2 different windows 7 machines. google drivers don't load, asus drivers don't load. Device manager just says "windows could not find driver software for your device."
---------- Post added at 08:15 PM ---------- Previous post was at 08:13 PM ----------
I figured it out, have to turn MTP on, then install drivers - then you can turn MTP back off if you want.

Categories

Resources