Nextbook Premium 7 SE w/ ICS

[ZonaMojo]

Picked one up today for $149 at Canadian Tire, ad said limited quantities, no rain-checks. Sale ends Thursday. Admittedly an unusual place to buy a tablet but it had what I was interested in :-)

Definitely the 7se with ICS.

Model Next7P12
Android 4.0.3
Kernel 3.0.8+
Build v1.0.7IML74k...

Serial YF031210...

Specs appear identical to previous version with Android 2.3, I wonder if current hacks work on it.

I found a Netbook 7" ICS 4.0 for $149 on the site. Not sure if they misspelled Nextbook. But it wouldn't show me any specs. Would be cool if you did the ROM dump. If the specs are the same, ICS should run on the Nextbook P7.

The Nextbook site NOW lists the Nextbook Premium SE for $179 Capacitive Touch & $149 Resistive Touch.

Specs/Features:

• 7” TFT Capacitive Display
• 800x480 High Resolution
• Built-in Rechargeable Battery
• Built-in 4GB Memory Storage
• Built-in G sensor
• Front facing 0.3 camera
• Preloaded with 25 Free eBooks
• Build-in Speaker
• Micro SD Card Slot for Memory Expansion
• MP3 & Photo Viewer
Android Ice Cream 4.0 OS
RK2918 Chipset A8 Cortex 1Ghz

THIS GUY DOESN'T REALIZE HE HAS THE PREMIUM SE. HE THINKS HE JUST HAS THE PREMIUM. THAT'S WHY IT HAS A CAMERA AND MICROPHONE.

[Randy]

still tinkering

Being the stubborn type, I've been going at this problem of getting adb to recognize the Next7P12. No luck yet.

I stuck a spare drive in my notebook and installed linux and got adb working, still finds my other droids no problem but not this one. Perhaps if I had the correct vendor id it may work.

There is a USB mode setting USBHost or USBDevice - tried both. Nothing.

Tried the terminal method - su not available to uid xxxx

I am able to get the rockchip batch tool in recovery mode to recognize a device attached. Don't know if this is useful.

Read through the entire listing created by dmesg for ideas - other than it looks like ext3 fs it was not useful to me.

I'll keep working with my friend google :-)

Any ideas? I'm hoping if I can get a dump off this thing I might end up with a rooted device at some point.

Here's the box anyways.

[Finless]

The drivers used to flash are not the same driver you need to install for ADB. However if your other devices are seen by ADB then you have the drivers.

BTW a divce can show up blank if it does not have an ID. I have seen this before. But you can still talk to it IF and ONLY IF, it is the only device connected. By default ADB will figure that out.




Bob

[Randy]

I considered that as a possibility and tried a shell command while connected, no device.

I emailed Nextbook tech support to see if they have any ideas. I'll see what they say. I'll keep my expectations low and void disappointment :-)

[Finless]

Just to make sure... you DID go into settings > Applications > Development >
and turned on USB debugging correct?

Without that setting it's a no go. You should also turn on Mock Locations to be sure.

Bob

[Randy]

Actually, in ICS they have separated developer option out into its own sub category in setup so its no longer under applications. Mock locations is also on, though I've tried it with it off. This one also has a USB Settings sub category to switch between host and device modes. I don't have an adapter to test host mode though if it works it has possibilities for those with USB devices they would like to use like LTE internet sticks for blazing downloads :-) I'm wondering if this setting is somehow responsible as I have not seen it on any other devices.

I've tried every combination of settings I could think of, plug it in powered on, powered off . . . I'm open to suggestions.

[Finless]

I have seen this in BAD ROMs before so something to check. WHen you change a setting like this it is actually stored in a database in /data/data. It's possible the settings APK is hosed and is not actually making the change to the DB so Android acts upon it. OR it is making the change to the DB in a place the OS is not looking at.... e.g. they screwed up in the coding and each different OS module is looking in the DB for a setting which is not the same as the settings.apk is changing. Again I have seen this happen before.

I think you can view the database without being rooted. You will need a root file explorer and you will need something that will open SQL databases. There is a free one on the market that will allow you to view a database but you cannot edit it. To edit the database SQLite will be needed.

Anyway the database that hold this setting on gingerbread is:

/data/data/com.android.providers.settings/databases/settings.db

The SQL element (field) is
Table=secure
field=adb_enabled > set this to 1

This maybe different on ICS.

Bob

[Randy]

Thanks Bob, sounds like it's worth investigating - especially after the reply I just received from Nextbook tech support. I'll take a stab at it tomorrow if I don't end up working late.

My question was about connecting to the android sdk for developing purposes, specifically adb.exe :-)

"Thank you for the email. The tablet is not
compatible with this format."

I guess they have no clue. We shall see . . .

[Randy]

Permission denied accessing /data/data

Does anyone know what dependencies adbd has on an android device? Currently adbd is running under user shell just like on my other devices. I'm wondering if something else might be missing or configured to prevent the connection to abd. Not much info about the daemon to be found.

Did a fresh WinXP install, modified the .ini to install googles android driver. Cycling debug on and off enables/disables device 'android phone' just as i would expect but still no connection.

How about a temp root method, does this exist? At least I could do a term dump. SU doesnt work.

[Finless]

Permission denied accessing /data/data

Does anyone know what dependencies adbd has on an android device? Currently adbd is running under user shell just like on my other devices. I'm wondering if something else might be missing or configured to prevent the connection to abd. Not much info about the daemon to be found.

Did a fresh WinXP install, modified the .ini to install googles android driver. Cycling debug on and off enables/disables device 'android phone' just as i would expect but still no connection.

How about a temp root method, does this exist? At least I could do a term dump. SU doesnt work.

Try data/local instead and see if that works.

Bob

[xxjoshxxx]

try this

make sure u have drivers installed

http://www.unlockroot.com/

[Nandroider]

Permission denied accessing /data/data

Does anyone know what dependencies adbd has on an android device? Currently adbd is running under user shell just like on my other devices. I'm wondering if something else might be missing or configured to prevent the connection to abd. Not much info about the daemon to be found.

I bought the same tablet at candian tire and have been pulling my hair out for weeks now. Customer support at nextbook was next to useless, same with Yifang who didn't even respond. Kohotech was very helpful although they could not resolve our issue.

Try this
1. Determine the Hardware Ids for your device (Device Manager, properties,details,property)
USB\VID_2207&PID_0000&REV_0222&MI_01
USB\VID_2207&PID_0000&MI_01
2. Add the vendor to adb_usb.ini (C:\Users\username\.android).
In our case, simply type 0x2207, don't copy/paste
3. Add the lines below to android_winusb.inf (AndroidSDK\extras\google\usb_driver) for both x86/64bit.
;Nextbook
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0000
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0000&MI_01

Depending on file location, you may have to save as and replace the file with admin. permissions. Execute adb kill-server before testing. Good luck Randy, the above worked for me and it should for you.

[Randy]

adb success!

Androider! You are the man! (assuming of course you are not female)

I had done both file modifications previously without success. This time around, since it worked for you, I knew at least I was on the right track.

Went back to my fresh XP install drive, installed android sdk rather than using bit's 'n' pieces frome here and there, changed android_winusb.inf so the driver supplied with the sdk would install, added manufacturer code to adb_usb.ini, typed not pasted, kill-server and bada bing bada bang, adb says I do have a device attatched!

I had all but given up after many many hours of trial and error screwin' around.

Thanks a heap Androider!

and . . .

Bob, I am going to attempt that rom dump this weekend. Where should I put the files when done?

Randy.

[Finless]

Let me know when you have the dump and I will give you our FTP sitye to upload it.

Cant wait!

Bob

[kibmcz]

Using the released update for the next8p12 i tried to make it work on my next7p but never got past wont fit on screen picture without touch support.

Owners of the next<version here>12 models it will be EASY to root as its ext3 system (even via the one click root methods).img but its structure makes it not compatible with the old ones.

The unpacked update.img for next8p12 contains:

Image/boot.img
Image/misc.img
Image/recovery.img
Image/system.img
package-file
parameter
recover-script
RK29xxLoader(L)_V2.20.bin
update-script

Furthermore the boot.img is not krnl format it is normal android boot image (looks to have kernel merged with boot too) yet it oddly booted on next7p. Ill mess with teh next7p12 dump after it is obtained tho but that is all from me for now.