Nextbook Premium 7 SE w/ ICS

[Randy]

oh yeah

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

Cant wait!

Bob

Android reminds me of linux :-) ... always issues.

So, I cannot change the permissions of rkdump although chmod doesn't complain when I su chmod... permissions don't change to allow it to execute. Even from the dir it was in using ./

On the other hand, following xxjoshxxx's instructions from a previous post in this thread (thanks xxjoshxxx) I was able to create .img's with dd if=/dev/mtd/mtdx...

Which blocks do you need? recovery, boot and system? Do you need misc?

I can upload them soon as I have a destination.

Randy. :-)

[kibmcz]

Android reminds me of linux :-) ... always issues.

So, I cannot change the permissions of rkdump although chmod doesn't complain when I su chmod... permissions don't change to allow it to execute. Even from the dir it was in using ./

On the other hand, following xxjoshxxx's instructions from a previous post in this thread (thanks xxjoshxxx) I was able to create .img's with dd if=/dev/mtd/mtdx...

Which blocks do you need? recovery, boot and system? Do you need misc?

I can upload them soon as I have a destination.

Randy. :-)

I know i'm not the target of the reply but I wouldn't mind a copy of the backup partition for my personal messing (I want to try to see if the next7p12 will work on my next7p) since it contains a full flashable restore image.

PM me and ill get you upload details.

[Randy]

I know i'm not the target of the reply but I wouldn't mind a copy of the backup partition for my personal messing (I want to try to see if the next7p12 will work on my next7p) since it contains a full flashable restore image.

PM me and ill get you upload details.

I'll do a factory reset and make a backup.img over the weekend when we are not out cruising the road :-) Ill pm when it's ready to u/l.

Another ? for Bob, should I create the required .img files after said reset or does it matter?

[kibmcz]

I'll do a factory reset and make a backup.img over the weekend when we are not out cruising the road :-) Ill pm when it's ready to u/l.

Another ? for Bob, should I create the required .img files after said reset or does it matter?

That's great and reset is not needed you just need to image dump the partition marked "backup" (mtd4 on my gingerbread rocking next7p).

[Finless]

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.

There are 2 formats I have seen of RK29 tablets. This one you have has the kernel and a ramdisk inside of boot.img. This is the same format that many rk28 tablets used! It can be converted. e.g. take the kernel out, make boot.img like the 7P and make a separate kernel.img. I have done it for many ROMs now. You need the tools to do it. They are perl scripts, and are the only tools I have found that will do it. It's on a wiki somewhere I do not recall but if you need them let me know. If you want me to convert it for you let me know and I can give you a FTP to upload to on our server. FYI, having the kernel outside of boot makes the system faster and has more memory so I always take it out when I run across a ROM in this old RK28 format.

Randy, I only need update.img (backup.img). If your tablet actually has it. Some do not. It's there but empty. I hope yours does as it makes it easy. If not we will need boot,misc,recovery,system and based on above if there is no kernel.img then it's in boot. I would then have to make the parameter files by hand as that is inside backup.img used for flashing Lets hope you have data in backup.img

Bob

[kibmcz]

There are 2 formats I have seen of RK29 tablets. This one you have has the kernel and a ramdisk inside of boot.img. This is the same format that many rk28 tablets used! It can be converted. e.g. take the kernel out, make boot.img like the 7P and make a separate kernel.img. I have done it for many ROMs now. You need the tools to do it. They are perl scripts, and are the only tools I have found that will do it. It's on a wiki somewhere I do not recall but if you need them let me know. If you want me to convert it for you let me know and I can give you a FTP to upload to on our server. FYI, having the kernel outside of boot makes the system faster and has more memory so I always take it out when I run across a ROM in this old RK28 format.

Randy, I only need update.img (backup.img). If your tablet actually has it. Some do not. It's there but empty. I hope yours does as it makes it easy. If not we will need boot,misc,recovery,system and based on above if there is no kernel.img then it's in boot. I would then have to make the parameter files by hand as that is inside backup.img used for flashing Lets hope you have data in backup.img

Bob

Randy is uploading to my .com i will post download link after i verify it unpacks with rkunpack.

ALso didnt known about the format differences... could you get me the split format after post download link?

[Finless]

If I can get it from that file sharing place. I hate those places. I keep my browser security high and many fo them do not work for me and sorry I wont reduce my security level. BUrned too many times. So I hope that place is OK. If not if someone can upload to our server here?

Yes I will take it apart for you when I get it.

Bob

[kibmcz]

If I can get it from that file sharing place. I hate those places. I keep my browser security high and many fo them do not work for me and sorry I wont reduce my security level. BUrned too many times. So I hope that place is OK. If not if someone can upload to our server here?

Yes I will take it apart for you when I get it.

Bob

Cool its being uploaded to my private .com... same place i host all my rom downloads. i gave Randy temp ftp upload and after test it the file will be moved to my android download public folder.

[Finless]

OK cool... let me know when ready.

I am finishing up my new 2.0 "gingercomb" ROM today and then have to go visit my Dad in the hospital so it maybe later tonight before I can take it apart for you.

Bob

[Randy]

...

Randy, I only need update.img (backup.img). If your tablet actually has it. Some do not. It's there but empty. I hope yours does as it makes it easy. If not we will need boot,misc,recovery,system and based on above if there is no kernel.img then it's in boot. I would then have to make the parameter files by hand as that is inside backup.img used for flashing Lets hope you have data in backup.img

Bob

Bob, this is what there is:

mtd0: 00400000 00004000 "misc"
mtd1: 00800000 00004000 "kernel" kernel.img 8.192mb created
mtd2: 01000000 00004000 "boot" boot.img 16.384mb created
mtd3: 01000000 00004000 "recovery" recovery.img 16.384mb created
mtd4: 1e000000 00004000 "backup" backup.img 491mb created
mtd5: 07400000 00004000 "cache"
mtd6: 20000000 00004000 "userdata"
mtd7: 00400000 00004000 "kpanic" kpanic.img 4.096mb created
mtd8: 1cc00000 00004000 "system" system.img 471.04mb created
mtd9: 89200000 00004000 "user"

The files label created are available to upload as soon as I have a destination.

[matt4129]

Same as Randy and Nandroider (May 18), I bought one of these on-sale at Canadian Tire, trying to get Google Marketplace on it using these instructions:

https://gunnersbarn.wordpress.com/2011/11/04/how-to-install-android-market-to-nextbook-premium-7/

with details from:

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.

I am still stuck, adb devices STILL shows nothing. I have tried the device plugged in to the USB with and without ""Turn on USB Storage"... at the bottom of the screen it flashes: "USB debugging connected" so I am pretty sure the device is properly set:

Settings -> Developer options -> USB debugging (check)
and Allow mock locations (check)

I am running on Windows 7 Home Premium.

I am sure you are still the man Nandroider, but I am more of a newb when it comes to Android. I installed the Android-SDK and it is open. Is there another program I need open ? I have opened a terminal window with and without "run as administrator" to run "adb devices".

I have checked the device manager, more on that in a sec... I have edited C:\Users\username\.android\adb_usb.ini and put in nothing but "0x2207" on a line by itself (no quotes of course). When I open the device manager with my unit installed, at first it was called: "USB Mass Storage Device", but then I told it to upgrade the driver and search for an appropriate driver, it installed a new driver, and now it is called "USB Composite Device" in any case its Hardware_IDS are:

USB\VID_2207&PID_0000&REV_0222
USB\VID_2207&PID_0000

there is no &MI_01 anywhere to be seen. Then I tried using the usb_driver that comes with Android-SDK... (browse for driver on computer) and it said the current driver was up to date.

So I am stuck, perhaps I am missing something more obvious to an experienced SDK / USB user ?

[Randy]

I have enough .apk's from other android devices that not having Google Play (andoid market) doesn't bother me. I am thinking the tablet performs as well as it does becasue none of the google overhead exists. Maybe :-)

Add the lines:

;Nextbook
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0000
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0000&MI_01

to android_winusb.inf under the sections headed, "[Google.NTx86]" and "[Google.NTamd64]"

android_winusb.inf is located in c:\Program Files\Android\android-sdk\extras\usb_driver since you have the android sdk installed.

Uni-install the current driver by plugging in the tablet, open device manager, right click on the device (composite usb device I think is what you said it is called now) then click uninstall.

Unplug and replug the tab, point new hardware found wizard to the same location that you just edited android_winusb.inf in and it should give you an "Android Phone" device with ADB composite device underneath.

Try adb devices again.

Don't give up :-)

Once you get it to list a device, su will work to some extent while using adb shell, just so you know :-)

[Finless]

If I can get your dumps I may be able to fix them. Not the first time some dumps were corrupt. When I say corrupt the data is fine its just it not starting and stopping at the right offsets. Usually I can look through these with a hex editor and fix them, combine them as needed, or trim them and get a dump working again.

So are the links still up somewhere?

Bob

[N4RPS]

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.

Hello!

This worked for ME, TOO! In XP, the path is C:\Documents and Settings\username\.android, but the end result is the same.

It was SO GOOD to see THIS when querying 'adb devices':

C:\ADB>adb devices
List of devices attached
NXM723HRF0123456 device

C:\ADB>

You guys MIGHT want to put this in a sticky, as EVERYONE is going to have to do this as a first step with this pup.

Now that I'm 'in like Flint', how can *I* help you folks out in this effort?

I remember using ADB shell to go in and turn on root permissions on my Velocity Cruz T301. Is the procedure similar for the 7s?

73 DE N4RPS
Rob

[jwhood]

So now will this work on the 7s i hope some one will get us root and play on this tab!!!

Sent from my HTC Glacier using Tapatalk