[roebeet]

I do not have a black PDN, so these are just suggestions which, tmk, are untested.1) Patch to the latest firmware. As far as we know, ADB access might be enabled in this new firmware (at least it seems to be, as per the init.rc). So that in itself might be the fix. Also, you'd want to test the firmware update anyway, as that would be your backout plan while doing any hacks. If you can get ADB access, then try the old volume hack to see if that works + an alternate launcher.2) Alter the "root.tgz" in the firmware file to use as a way to get an alternate launcher added, via a firmware update. I'm thinking that you could alter /system to add the vanilla launcher, or alter /data to add a third-party one. That's assuming Pandigital isn't checking md5sums, but you might be able to alter that as well. You'd also need to figure out how to re-zip it properly. In Ubuntu, I see the following:

file polaris_update.datpolaris_update.dat: POSIX tar archive (GNU)file polaris_update.dat.gzpolaris_update.dat.gz: gzip compressed data, from Unix, last modified: Sun Aug 22 21:51:43 2010

Lastly, keep in mind that this is Android 1.5, so you'd need a launcher that supports it. Good luck!

 

[derelicte]

Before you even update it, just plug it in and share the usb vendor and device ids with us. It could be as simple as updating the windows driver inf file.

 

[eski15]

I just picked up the black unit at BJ's and tried to get ADB access with no luck. When I ask for ADB devices it returns list of devices with nothing listed. The Device ID is as follows usbvid_0525&PID_A4A507044033FAB0I called the PD customer support line and they told me that the black PDN is running Android 2.1. I asked the person i was speaking to to double check and he put me on hold, checked and confirmed itAny ideas how I can get ADB access to root this thing?I had a white one but returmed it because of too many problems. I have a rooted Gentouch thats running well, but like the 4:3 aspect better than the 16:9, so if we can root this one it would be greatThanks

 

[derelicte]

well, that is a different usb vendor and device id than the white, so the adb driver won't load. you can try changing the inf to reflect the new values.

 

[derelicte]

wait a minute, can't adb connect to a device via tcp (i.e. over wifi)?

 

[derelicte]

the other option would be to flash it with the image on pd's site. dis-assembly of the image indicates adb is enabled.

 

[eski15]

I already flashed it with the update 8/18

 

[clockworx]

If you give me a second, I'll upload an updated inf version that you should be able to use to install.Aaaaaaaaaaand here:Just unzip that inf to wherever your adb files are (assuming you're using the "Hack The Novel" folder), and it should work. Just point to that file when it asks for drivers.

 

[eski15]

Great, just please let me know where the file needs to be installed. As I said I am new to android and it's been many many years since I used the command line.

 

[clockworx]

Well, how did you try to get adb access before? We'll need to know what you know now in order to figure out where to start off from. If you go into Windows device manager, you see no items with a yellow triangle and/or yellow question mark?

 

[eski15]

I tried to install the driver but got the following, "the specified location does not contain info about your hardware" When i plug the PDN into my computer it does not ask for a driver it just mounts the PDN as two drives. Is there a driver I need to delete first? I was trying to change the driver for the USB Mass storage device.

 

[eski15]

I went into ADB thru the command line. I copied all of the Hack the novel files into the root C: drive of my laptop, ran cmd, changed dir and typed in adb. When adb came up I typed in adb devices and none were listed.BTW, Thanks for your help with this!

 

[clockworx]

You don't want to change the driver for the USB storage. There's multiple devices associated with the USB connection (2x USB drivers, adb connection,etc). Did it ever prompt you for a driver, like when you plugged it in for the first time?Again, I would suggest going into device manager and looking for any unassigned devices (question mark or triangle). That may be the missing connect for the Android ADB driver.

 

[clockworx]

roebeet kind of jumped in on your other thread, and since he's done this before with the white, I'm going to shoot some suggestions with him. If we get anywhere you'll be the first to know

 

[eski15]

I saw that and think that that is the way to go as he seems to know what he is doing and I DONT!!!Thanks Again

 

[roebeet]

I actually purchased a black Novel two days ago, as curiosity got the better of me. I managed to get ADB access over WiFi this morning, using clockworx's excellent suggestion. But I haven't been able to change the launcher (yet). KB hack doesn't seem to work, either - might be using different keys.

 

[clockworx]

If you just pull the same file as the keyhack file off of the device, you should be able to see what is different and change it. It's pretty well documented within the file.

 

[jackbox]

I just got my Black PDN in the mail today. I can connect via ADB over Wifi but I cannot remount the system as writeable and there is no shell access. So far I cannot figure out how to root this little guy. I am using Android Mate as the home screen as I haven't found a genuine launcher that works without force closing yet. This is on the stock firmware that came with the unit.

 

[Mark Adams]

[quote author=jackbox link=topic=6033.msg128072#msg128072 date=1296134045]
I just got my Black PDN in the mail today. I can connect via ADB over Wifi but I cannot remount the system as writeable and there is no shell access. So far I cannot figure out how to root this little guy. I am using Android Mate as the home screen as I haven't found a genuine launcher that works without force closing yet. This is on the stock firmware that came with the unit.
[/quote]
Wow, you're kidding, right? You were doing this by telepathy man. You did retrace Roebeet's steps in the other thread, right?