Has anybody tried the zergRush exploit for rooting the Nook Tablet?
It is able to root Android 2.3 devices with a locked boot loader (as the Nook Tablet seems to have).
See e.g. http://forum.xda-developers.com/showthread.php?p=18805560
The source of the exploit is on github: https://github.com/revolutionary/zergRush/blob/master/zergRush.c
This is also the exploit used to root the Kindle Fire.
Do not have a Nook Tablet here in Europe, so I cannot try this.
Hope this helps to root the Nook Tablet.
If I recall correctly, it needs ADB...which we dont have.
adb (Android Debug Bridge) is part of the standard Google Android SDK. If you have the SDK, you have adb.
But I believe the NT does not have what is needed (at least by initial apprearance) for ADB to to work. The binary / file needed is MIA at the moment....correct me if I'm wrong?
There was one post that ADB is not at the standard location on the Tablet. It may have a different name, or not be there at all.
moved to general.
Not related to development ..
Thread moved to general section.
Related
Hi there,
I'm wondering, has anyone managed to use the toshiba tablet as a rooting machine - as in connecting other devices and rooting them using the tablet?
I'm currently shopping for a tablet/notebook, and thought that it would be nice if i could connect another android device to the folio and root those devices using the folio.
Is this achievable and has anyone tried this?
It *might* be possible. Ubuntu seems to be running quite well by now, so you would need to compile the needed binaries for arm. I don't know if the adb source is availlable, but cross or even native compilation of fastboot should work. Then you cold flash stuff and use adb.
But to be honest, many devices can easily bee rooted with a sufficiant app like z4root.
In the whole it will be a lot more work than just getting a netbook, but it could be fun to try
mblaster said:
It *might* be possible. Ubuntu seems to be running quite well by now, so you would need to compile the needed binaries for arm. I don't know if the adb source is availlable, but cross or even native compilation of fastboot should work. Then you cold flash stuff and use adb.
But to be honest, many devices can easily bee rooted with a sufficiant app like z4root.
In the whole it will be a lot more work than just getting a netbook, but it could be fun to try
Click to expand...
Click to collapse
Interesting... I'm not a developer, so it does sound daunting and intimidating to try...
I'm just looking to buy a device that can help me root - i did think about a netbook, but i want my next purchase to be an android tablet, so i was wondering if i could kill 2 birds with one stone...
Use SuperOneClick
Sent from my Folio 100 using Tapatalk
Moved to proper forum.
My Nook Tablet just updated to the dreaded 1.4.1 version which makes sideloading pretty difficult.
I was reading this article which has steps to sideload apps onto the 1.4.1 NT without rooting it, and pointed to downloading this script on the XDA forums which will push the apk onto the plugged in tablet, as long as the apk is in the same folder as the Sideload script files.
So, steps 1 to 5 weren't a real problem but its Step 6 that I'm stuck on.
There is a Sideload BAT script which seemed to run (its disclaimer is that it will only run if it finds an Android device -- which is a clear indication that it could find and recognize that my Nook Tablet is plugged in). It even says C:\Sideload>adb wait-for-device. However, when I try to tell it to install the apk via Command Prompt (I type in: adb install Amazon_Appstore-release.apk ), it returns "error: device not found" .
Just for good measure, I also type in C:\Sideload\adb devices and it returns: List of devices attached .
I'd greatly appreciate if somebody could help me with this--I really have it up a wall and would just like to put this problem to bed. Thanks!
i'm having the same exact problems here! are there any specific drivers to install?
Yep, I was still fairly a noob at this when I first posted but have learned a lot ever since. Here's what you want to do:
(btw, I factory resetted to 1.4.0--you may need to as well):
When it says "no device found", it's corresponding to this command line : adb install whatevernameofapp.apk . I interpreted "no device found" to mean that it does not know what "adb" means in the command.
For it to recognize all "adb" related commands, you have to have the USB drivers installed. Look for tgps_launcher.apk on this link: http://forum.xda-developers.com/showthread.php?t=1354487. That will set you up with having you Nook to accept third party applications + having it on UBS debug mode.
Then, install the drivers (I saw this YouTube walkthrough because it is NOT intuitive and you want to be sure you're doing it right , it's not the way you would traditionally update drivers for a mouse or keyboard; here: http://www.youtube.com/watch?v=ZtGveN7jbzs )
After that, I followed the instructions on this article, made a folder in C:, called it sideload, and also pasted an .apk. Now, when I do the Commant Prompt, it says this: http://img23.imageshack.us/img23/2914/cmdnookadb.jpg . While, the transfer was successful, I haven't been able to see the app on my tablet. Does anyone know where I can find this (data/local wasn't found when I connected the tablet to my PC either, and it wasn't on my SD or so). Is it because I'm still on 1.4.0?
Let me know if you get it working all the way!
I followed all those directions exactly. I had received the No Device Found error. I followed the Youtube directions to add drivers and it seems like I did it correctly. I am seeing the android device on the device manager.
I tried running the script again and got the same error! I'm now stuck!
I had the amazon marketplace already installed and was using it successfully until my nook updated to 1.4.2. I thought I had ES File Explorer downloaded but for some reason I can't find it! So I now I am trying to sideload ES File Explorer this way but it wont work!
0x2080
^ put that in %userprofile%\.android\adb_usb.ini
Can you give me more specific instructions on how to do that?
FYI - I have ver 1.4.2 and I am NOT rooted. I have already enabled unknown sources and downloaded the amazon market. I was installing 3rd party apps fine before the update.
[HOW-TO] Use ADB tool | Android Debug Bridge
You need to revert to stock 1.4.0, there are easier and faster ways to do that now > check development section. Basically you need to have CWM booting from sdcard then flash stock ROMS posted >> Albert and I have posted 1.4.0 stock ROMs.
~ Veronica
Moved To Q&A
Hello All,
So there is very little documentation on the PX102 online as of yet, let alone AOCOS products in general (at least on english sites which I have scoured). First off, I'm currently using OSX 10.6.8 and have the current Android developer tools package that was downloaded from their site about three hours ago (just to be clear). The PX102 is running 4.1.1 and the tablet is a fresh restore (I had a number of apps downloaded but considered that some may have been interfering...).
I will be attempting to root via psneuter exploit from SuperOneClick v2.3.3, however in the terminal when I execute "adb devices" it returns "List of devices attached" with blank space underneath...
I have tried to kill/restart server, run "adb usb", and a couple other small things to no avail.
Yes, usb debugging mode is enabled as well.
I would really like to attempt/execute this all via OSX, however name an OS and I have it at my disposal...
I admit- I am a noob in various ways, especially to android as this is my first android device. Hoever, I also consider myself to be rather self sufficient in terms of sourcing knowledge and troubleshooting, which is why I humbly ask for guidance in this endeavor.
Also, feel free to ask me any questions about the PX102 (via PM only please! I dislike threads being fuddled with asides...).
I'm not seeing too many people claiming to have these tablets though there is quite a bit of interest in them.
Anyone?
For windows you can try rkbatchtool v1.5 to get the correct drivers
Rooted mine
I rooted mine, wasn't easy though.
First problem, you need a adb driver that works on this rockchip tablet that doesn't have a built in ADB driver. Also I didn't have much luck on the chinese language AOCOS forum.
The only way I found to get one is:
1) download and install the morborobo phone manager software from moborobo.com. Yes this is a risk to your pc. God knows what else it did to my pc.
2) let IT find a driver. It will download and install two unsigned drivers.
3) those drivers aren't enough. You need to generate adb_usb.ini in c:/Users/%username%/.android/adb_usb.ini (if you're on windows 7)
Installing the SDK does that automatically otherwise you need to run "android update adb" or something to generate it
4) put the vendor id at the end of adb_usb.ini in the case of AOCOS the vendor is 0x2207
I tried using a premade adb_usb.ini with all of the vendor ids. That didn't work. It worked when I put the right on only.
NOTE, that vendor ID exists nowhere online. I had to find it by reading it directly from the device using USBVIEW from http://digital.ni.com/public.nsf/allkb/335A90747734097886257070006415B9
5) Now you should have a working adb driver. Plug the machine in and type "adb devices". It should see yours
6) now comes the rooting.
Follow the instructions here:
http://forum.xda-developers.com/showthread.php?t=1886460
The script is here: http://uploaded.net/file/0fpyh5c5
the videos showing how are here http://forum.xda-developers.com/showthread.php?p=33470626#post33470626
Note there IS a hacked adb driver that doesn't need a vendor ID, BUT it doesn't work for rooting, it's too old to have the restore feature you need for a jelly bean root.
The PX102 is cool, but mine has some problems:
1) the keyboard charge connector is bad, I have to send it back
2) the battery sucks... I'm sending back the tablet too, hopefully that will fix it
3) never drop one of these, mine only fell a couple feet and it's flaky now. :/
4) the camera is fake. It's not the 2mega pixels it says. It's super low quality and maybe vga. They put in bull**** fractal interpolation software to try to fake higher res
The keyboard is no where near as nice as a transformer, the tablet only rests on the keyboard and can fall off.
Still it's a nice machine. I have my memory cards formatted ext2 (from a previous tablet). I can mount them but the machine won't boot with an ext2 card plugged in. I have to take the card out, boot the machine, then plug it in and mount it.
I even managed to install GNU Gcc/ gnu tools
You can also try this: http://www.androidtablets.net/forum/rockchip-rk3066-tablets/46964-root-your-rockchip-3066-a.html
Or this: http://valentijn.sessink.nl/?p=382
HEllo,
I'm actually trying to hack THOMSON THBK1-10 tablet (also know at VOYO A1).
This is a dual boot system with Android 4.4.2, and Windows 8.1, based on Bay Trail (Atom Z3720) CPU. Running kernel is 3.4.43
After a long fight, i gained accesses to /system and /data partitions.
I have so copyed su binary, and changed the access mode to ugo+rx. Good !
Sadly, this is not enough to gain root access. everytime i'm issuing su command i got into a $ prompt.
I must mention i only have ADB wireless for this device: the USB is acting as an USB host, it is not possible to plug it into a PC/MAC.
My question is what i must check, do, to gain root accesses ? What should i look, try, dig ?
Thank you !
Self reply: you only need to have SU installed, as i mentionned.
I've seen some news spamming the internet that ADB was removed from marshmallow. Can anyone confirm or deny this for stock roms? I run CM13 so no stock roms to see. Wouldn't make sense for ADB to be removed.
What seems to have been removed is the on-device ADB binary. I discovered this myself, today, as I have an Asus TF300T which I regularly use with other Android tablets at work for debug purposes, that I over the weekend upgraded to 6.0. Much to my surprise, no longer am I able to adb from my tablet. I did some quick research on it, and found a few people posting about it, but no solutions as of yet.
USB Debugging
Artemis-kun said:
What seems to have been removed is the on-device ADB binary. I discovered this myself, today, as I have an Asus TF300T which I regularly use with other Android tablets at work for debug purposes, that I over the weekend upgraded to 6.0. Much to my surprise, no longer am I able to adb from my tablet. I did some quick research on it, and found a few people posting about it, but no solutions as of yet.
Click to expand...
Click to collapse
isnt there a usb debugging thing?
I have g3 before i had to set it to mtp for debug and adb now i have to set it to ptp but its there and it works
ReliantFever735 said:
isnt there a usb debugging thing?
Click to expand...
Click to collapse
USB debugging is for connecting a device to another device, ie an Android device to a PC. It does not, however, give an Android device the ability to run ADB locally to connect to another Android device. My situation is, I have a TF300T which is a tablet with a dock, the dock has an actual USB port and functions like a USB OTG adapter. I used to be able to connect other Android devices to the USB port on my tablet and, using a terminal emulator, run ADB commands to the external Android devices. Since upgrading my tablet to 6.0 however, I discovered that I could no longer perform that task. Some quick Googling turned up a couple of places asking about this exact function, and someone on stackexchange posted a question about that exact issue, however they never got any response.
Why Google felt it was necessary to exclude the ADB binary from 6.0 is beyond me. Sure, it's something that is probably rarely used by users, but for those of us that -do- use it, it's not cool that it's suddenly gone.
I wonder if it wouldn't be trivial to extract the binary from a 5.0 device and see if it would just work under 6.0...
Hi
did you find a solution? I'm on CM13 would love to be able to use my tablet as adb client again...
Regards
Kip
I ran across this thread the other day. I haven't had a chance to try it yet but this might be what your'e looking for.
http://forum.xda-developers.com/showthread.php?t=2239421
http://forum.xda-developers.com/attachment.php?attachmentid=3685519&d=1458155113
ElwOOd_CbGp said:
I ran across this thread the other day. I haven't had a chance to try it yet but this might be what your'e looking for.
http://forum.xda-developers.com/showthread.php?t=2239421
http://forum.xda-developers.com/attachment.php?attachmentid=3685519&d=1458155113
Click to expand...
Click to collapse
Works for me. Thanks a lot!
Gesendet von meinem LG-V500 mit Tapatalk
Guys please help me how to get adb in the Android 6.0 and above I Googled about this but I didn't find it I hope here I can get the solution
Artemis-kun said:
USB debugging is for connecting a device to another device, ie an Android device to a PC. It does not, however, give an Android device the ability to run ADB locally to connect to another Android device. My situation is, I have a TF300T which is a tablet with a dock, the dock has an actual USB port and functions like a USB OTG adapter. I used to be able to connect other Android devices to the USB port on my tablet and, using a terminal emulator, run ADB commands to the external Android devices. Since upgrading my tablet to 6.0 however, I discovered that I could no longer perform that task. Some quick Googling turned up a couple of places asking about this exact function, and someone on stackexchange posted a question about that exact issue, however they never got any response.
Why Google felt it was necessary to exclude the ADB binary from 6.0 is beyond me. Sure, it's something that is probably rarely used by users, but for those of us that -do- use it, it's not cool that it's suddenly gone.
I wonder if it wouldn't be trivial to extract the binary from a 5.0 device and see if it would just work under 6.0...
Click to expand...
Click to collapse
I suppose google removed adb from android, is probably because it poses security threats. I am doing a seminar on a paper published in 2017, called SMAShed. It can manipulate android sensor data with only internet permission. As a matter of fact, apps installed using adb are granted all permissions by the OS without notifying the user. You can find the demo at androidsmashed.wordpress.com/demos/ .