Next book ROMs

[eegorr]

Yep, bought it at Big Lots for I think $79. My kids love the tablet, but there are a few things I want off the Google Play market that I can't access anywhere else I wrote the manufacturer when I saw that they now are going to offer a 7" model with Google Play and asked them if they were coming out with a new ROM to support it, but all they said was that they petitioned Google and have no ETA on the approval of the application. My daughter is non-verbal, so accessing many of these apps to help her learn how to communicate without a voice is ESSENTIAL. I'm desperate, I couldn't afford an iPad.

PS- My Nextbook 8P SE is ICS, not Jellybean

Yeah, same boat here, except for your daughter, of course! If you still have the receipt, you can return the tablet for a full refund up to January 15th - return time is extended because of the holidays.

You got further with the manufacturer than I did - all they would tell me is that Google had not licensed it for Google play, not that it was in the process of being aproved.

As for the app you need, try to contact the developer directly. You can usually see their email address if you find the app on Google play via a web browser. If you explain your situation, they might be willing to send you the apk file for the app. Then it is a simple matter of copying it onto the tablet somewhere and using App Installer to install it.

BTW, all of these newer Nextbook Premium 8SE tablets run ICS, but I would like to be able to upgrade to Jelly Bean.

[eegorr]

Sorry, I should wake up properly before posting.

Way to leave us in suspense. LOL!

[900supersport]

do you have a link to the firmware?

[eegorr]

There's a guide on pulling the image using adb somewhere. I'll see if I can find it.

http://www.FreakTab.com/showthread.php?p=5057

Okay, I got the JDK and SDK installed. I had to install the 'platform-tools' from the SDK Manager, but got that done without error.

I connected my tablet with USB debugging enabled and Windows found a driver for it - it took a while, but the driver downloaded and installed without error.

I was unable to push rkdump to the tablet, though. Here is the transcript from the command window:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>
C:\Windows\system32>cd\program files (x86)/android/android-sdk/platform-tools

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
0123456789ABCDEF device

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push rkdump /data/
failed to copy 'rkdump' to '/data//rkdump': Permission denied

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push rkdump /data (left off the extra '/')
failed to copy 'rkdump' to '/data/rkdump': Permission denied

I disconnected the tablet, waited about 10 seconds, then reconnected it with USB debugging enabled. I retried the push command - same thing happened.

Just for grins, I decided to go ahead and open up a shell:

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
shell@android:/ $ cd data
cd data
shell@android:/data $ ls
ls
opendir failed, Permission denied
255|shell@android:/data $

Am I missing something, or is this thing locking out development access? Is there any way to get around it?

EDIT - Here are the permissions from the root directory:

shell@android:/ $ ls -l
ls -l
drwxr-xr-x root root 2012-12-06 01:31 acct
drwxr-xr-x graphics graphics 2012-09-16 21:31 boot
drwxrwx--- system cache 1970-01-02 09:31 cache
dr-x------ root root 2012-12-06 01:31 config
lrwxrwxrwx root root 2012-12-06 01:31 d -> /sys/kernel/debug
drwxrwx--x system system 2012-11-24 08:49 data
-rw-r--r-- graphics graphics 221 2012-08-21 05:33 default.prop
drwxr-xr-x root root 2012-12-06 01:42 dev
lrwxrwxrwx root root 2012-12-06 01:31 etc -> /system/etc
-rwxr-xr-x graphics graphics 115116 2012-08-21 05:45 init
-rwxr-xr-x graphics graphics 17967 2012-08-21 05:35 init.factorytest.rc
-rw-r--r-- graphics graphics 2344 2012-08-21 05:34 init.goldfish.rc
-rwxr-xr-x graphics graphics 28413 2012-08-21 23:19 init.rc
-rwxr--r-- graphics graphics 1097584 2012-08-21 05:35 initlogo.rle.bak
drwxrwxr-x root system 2012-12-06 01:31 mnt
dr-xr-xr-x root root 1969-12-31 17:00 proc
drwxr-xr-x graphics graphics 2012-09-16 21:31 sbin
lrwxrwxrwx root root 2012-12-06 01:31 sdcard -> /mnt/sdcard
drwxr-xr-x root root 1969-12-31 17:00 sys
drwxr-xr-x root root 1969-12-31 17:04 system
-rw-r--r-- graphics graphics 272 2012-08-21 05:34 ueventd.goldfish.rc
-rwxr-xr-x graphics graphics 5106 2012-08-21 05:33 ueventd.rc
lrwxrwxrwx root root 2012-12-06 01:31 vendor -> /system/vendor
shell@android:/ $

Just looking around, here are the contents of the /etc directory:

shell@android:/etc $ ls -l
ls -l
-rw-r--r-- root root 95001 2008-08-01 05:00 NOTICE.html.gz
-rw-r--r-- root root 173 2008-08-01 05:00 alarm_blacklist.txt
-rw-r--r-- root root 249319 2008-08-01 05:00 apns-conf.xml
-rw-r--r-- root root 1082 2008-08-01 05:00 asound.conf
-rw-r--r-- root root 18766 2008-08-01 05:00 asound.state
-rw-r--r-- root root 3860 2008-08-01 05:00 audio_effects.conf
drwxr-xr-x root root 1969-12-31 17:04 bluetooth
lrwxrwxrwx root root 1969-12-31 18:59 bt_addr.conf -> /sys/clas
s/efuse/mac_bt
-r--r----- bluetooth bluetooth 935 2008-08-01 05:00 dbus.conf
drwxr-xr-x root root 1969-12-31 17:04 dhcpcd
-rw-r--r-- root root 12863 2008-08-01 05:00 event-log-tags
-rw-r--r-- root root 2689 2008-08-01 05:00 fallback_fonts.xml
drwxr-xr-x root root 1969-12-31 17:04 firmware
-rw-r--r-- root root 376 2008-08-01 05:00 fw_env.config
-rw-r--r-- root root 24 2008-08-01 05:00 gps.conf
-rw-r--r-- root root 25 2008-08-01 05:00 hosts
-rwxrwxrwx root root 1304 2008-08-01 05:00 init-pppd.sh
-r-xr-x--- root shell 1755 2008-08-01 05:00 init.goldfish.sh
-r-xr--r-- root root 418 2008-08-01 05:00 install-recovery.sh
-rw-r--r-- root root 7852 2008-08-01 05:00 media_profiles.xml
-rw-r--r-- root root 730 2008-08-01 05:00 mkshrc
drwxr-xr-x root root 1969-12-31 17:04 permissions
drwxr-xr-x root root 1969-12-31 17:04 ppp
-rw-r--r-- root root 1601 2008-08-01 05:00 remote.conf
drwxr-xr-x root root 1969-12-31 17:04 security
-rw-r--r-- root root 2595 2008-08-01 05:00 system_fonts.xml
drwxr-xr-x root root 1969-12-31 17:04 usb_modeswitch.d
-rw-r--r-- root root 4445 2008-08-01 05:00 voicemail-conf.xml
-rw-r--r-- root root 810 2008-08-01 05:00 vold.fstab
drwxr-xr-x root root 1969-12-31 17:04 wifi
shell@android:/etc $

[eegorr]

do you have a link to the firmware?

There is no firmware update available. It is a new product with no online documentation and no updates, either, and I was not able to get an image from tech support - others have been denied, as well.

[900supersport]

Re: Next book ROMs

Those permissions indicate you do not have write access to data. Try pushing to sdcard and running from there.

[verucalise]

Those permissions indicate you do not have write access to data. Try pushing to sdcard and running from there.

OOOO the suspense! Wonder if it will work!

[eegorr]

Those permissions indicate you do not have write access to data. Try pushing to sdcard and running from there.

That much I could tell myself! I tried to change permissions for the data directory with chmod but that didn't work, either. Is there some way to log in as root?

Even though the permissions say I should have access to sdcard, when I try "cd sdcard" or "cd /mnt/sdcard" I get "Permission denied". What's up with that?

BTW, it doesn't seem to matter whether or not USB storage is turned on or off, as long as USB debugging is enabled. Is that right? I would think that as long as I can get a shell I should be okay.

Did you figure out if RKDUMP will even work with an AMLogic processor?

EDIT: Answered my own question - permissions for /mnt are as follows:

shell@android:/mnt $ ls -l
ls -l
drwxr-xr-x root system 2012-12-07 20:23 asec
drwxr-xr-x root system 2012-12-06 01:31 obb
d--------- system system 2012-12-06 01:31 sdcard
drwx------ root root 2012-12-06 01:31 secure
shell@android:/mnt $

NOW WHAT???

[asaddotcom]

Have you tried loading the updated ROM image (netflix fix) that is available on the support website?

If it works with your tablet, that image could serve as the basis for a rooted image, if I understand things correctly. It might even be possible to update the image to Jelly Bean.

Gurus, am I getting this right?

Yeah I have tried that one but didn't solve my display issue... I need the exact chipset firmware if anyone can dump full flash package like RK2918Loader.bin | parameter | misc.img | kernel.img | boot.img | recovery.img | system.img | update.img etc, then please let me know....

[900supersport]

Re: Next book ROMs

That much I could tell myself! I tried to change permissions for the data directory with chmod but that didn't work, either. Is there some way to log in as root?

Even though the permissions say I should have access to sdcard, when I try "cd sdcard" or "cd /mnt/sdcard" I get "Permission denied". What's up with that?

BTW, it doesn't seem to matter whether or not USB storage is turned on or off, as long as USB debugging is enabled. Is that right? I would think that as long as I can get a shell I should be okay.

Did you figure out if RKDUMP will even work with an AMLogic processor?

EDIT: Answered my own question - permissions for /mnt are as follows:

shell@android:/mnt $ ls -l
ls -l
drwxr-xr-x root system 2012-12-07 20:23 asec
drwxr-xr-x root system 2012-12-06 01:31 obb
d--------- system system 2012-12-06 01:31 sdcard
drwx------ root root 2012-12-06 01:31 secure
shell@android:/mnt $

NOW WHAT???

Eegorr

I don't think rkdump will do the job. I suspect it may be time to hit Google for information on dumping amlogic based tabs.

[900supersport]

Re: Next book ROMs

Take a look at this thread on xda developers, looks promissing.

http://forum.xda-developers.com/showthread.php?t=1990415

[eegorr]

Yeah I have tried that one but didn't solve my display issue... I need the exact chipset firmware if anyone can dump full flash package like RK2918Loader.bin | parameter | misc.img | kernel.img | boot.img | recovery.img | system.img | update.img etc, then please let me know....

See my previous replies to you on other threads. I think you are mistaken about which tablet you have. According to Nextbook tech support, they only made two versions of Nextbook Premium 8 SE and both of them have screen resolutions of 800x600, 500MB of RAM, and 4GB of internal NVRAM. I think you have a Nextbook Premium 10. Screen size is measured diagonally, from corner to corner of the display. Measure yours - height, width, and diagonally and report the results back here. Also, you can check your model by going to the "Settings" page, selecting "About tablet", and looking at "Model number". Report that here, and, while you are at it, report the "Android version", too.

[eegorr]

Take a look at this thread on xda developers, looks promissing.

http://forum.xda-developers.com/show....php?t=1990415

Looks to me like they are coming to the same conclusion that we have here - we are screwed without a ROM image from the manufacturer!

What about source code? Could you build a new ROM image if you had their source code? Would we even be able to load it?

Don't they have to provide source code on request, as a condition of using Google's open source Android code?

[900supersport]

Done some rooting about Bob has done ROMs for the Ramos W13 pro which I think is an amlogic based processor. I'll see if he has any tips on extracting a ROM image and working it.

I did notice on that thread that it seems tp be possible to install using adb install, This may give us a root to side load some apps.

[900supersport]

Take a look at this post. If you are up for it then I'll support you.