Latest Nexbook 9P stock ROM as of Nov. 2012

[Finless]

He folks, I have not been keeping up with all the Nextbook stuff lately. However when a new stock ROM becomes available because a user spent the time to dump it from thier tablet, I try to make sure it is available to help folks.

Give a hand to FreakTab user James Cozzby for taking the time to dump the ROM from his tablet for all you to enjoy.

I assume this is the latest ROM from Nexbook as this is what is shipping on new 9P's.

He dumped backup.img not his system etc. So this is infact untouched and is just like a stock ROM that would be supplied from the manufacturer. This allows you to flash to stock like the day you bought it. It is not rooted or touched in any way shape or form.

What I have done is taken apart backup.img and turned it into a flashable ROM kit. Flash instructions are in the kit although I am not sure how accurate they are for getting your 9P into flash mode.

So enjoy!

ROM ->Nextbook 9P latest ROM as of Nov. 2012 (215 megs)


Bob

[Silicon Orb]

What I have done is taken apart backup.img and turned it into a flashable ROM kit. Flash instructions are in the kit although I am not sure how accurate they are for getting your 9P into flash mode.

Any chance you can post the original image? Some tools need to operate on it directly.

Thanks!

[Finless]

Any chance you can post the original image? Some tools need to operate on it directly.

Thanks!

This is backup.img split apart using Wendal tools. So why would you need the original backup.img? If you want to make that, use the standard rockchip AFPTool to make update.img.

Bob

[Silicon Orb]

This is backup.img split apart using Wendal tools. So why would you need the original backup.img? If you want to make that, use the standard rockchip AFPTool to make update.img.

*edit*

Nevermind, I got the original. Thanks James,

[Silicon Orb]

BTW, is it me or is the kernal.img missing in your package?

[Finless]

Kernel on stock ROM is in boot.img. It can be extracted and made into a seperate kernel.img which would have to happen to make a rooted ROM.

Bob

[Silicon Orb]

Kernel on stock ROM is in boot.img. It can be extracted and made into a seperate kernel.img which would have to happen to make a rooted ROM.

Bob

Strange. When I attempted to flash my NEXT9P with the package as instructed, and without changing any of the parameters, the unit didn't re-boot at the end, and wouldn't even wake up. I was thinking it might be bricked, but I re-flashed with another firmware and it recovered

I needed to use the kernel.img from James' previous dump posting, and checked the box next to it. After that, it booted and is working fine on 4.0 (well, as fine as it did out of the box). Sounds like something might still not be quite right with the package. Either that, or it didn't flash right the first time. The process completed properly, though.

Anyone else try it and get a different result?

[Finless]

Nexbook is notorious for changing hardware mid stream which makes some kernels work and others not. I do not have a nexbook so cannot test any of these ROMs. But I can tell you that ROM dump was perfect!

Now understand something about rockchip and the kernel
1) If kernel is in boot.img it will ALWAYS be used to boot even if kernel.img exists.
2) If kernel is in recovery then IT will be used anytime recovery is booted.
3) If kernel.img exists, it will ONLY be used by boot or recovery if kernel is not inside either.

So if you used your kernel.img but with this ROM dump boot.img, then you booted using the kernel inside boot.img NOT the kernel you think you flashed. Based on this fact, I think your first flash failed or something.

FYI, if you did not erase NAND (IDB), then all bets are off! Make sure you do this anytime you are flashing a new kernel or boot with kernel!

Bob

[Silicon Orb]

Thanks for the info. I'm obviously still learning about this stuff.

No explanation for why it happened. I did follow the instructions, erased NAND, etc. I panicked a bit when it went unresponsive and didn't want to try it again. But I did just flash the tablet back to your 1.5a rom, and then back to the 4.0 stock just as supplied. It worked fine this time.

I guess the moral is "don't panic, just re-flash"

After going back to the 4.0 rom, it's really apparent how much smoother everything is with it. If it weren't for the lack of the Play market and the often crashing out of the browser problems, it wouldn't be too bad. Time to start trying to get this thing rooted, I guess.

[JamesCozzby]

How Install ADB Driver, Root, and Install Google Play

Here are the steps used to install the adb driver, root the tablet, and install google play.
Also, i have confirmed this working on two of my Nextbook 9 tablets.

As a note: if you already have facebook, facebook messenger, or youtube installed (and possibly other apps as well) before you follow these steps, once you have google play installed, they will force close and will not work. All you have to do is uninstall them, and reinstall them through Google Play and they will work. Simple as that.

-----You do not have to do the following 3 steps, but they are just incase you want to try to do more customization with your tablet

Installing SDK tools
1. First of all you would need download the adb tools, necessary to perform most work on android, if you do not already have them. You can download them from this link if you are using a windows computer: http://dl.google.com/android/install....3-windows.exe
2. Then when you are done downloading this file, go to this site for the instructions on how to install it: http://developer.android.com/sdk/installing/index.html
3. Once you have completely installed android sdk tools, you will want to install the driver for your device.
------

------------------------------------------------------------------------------------------

START HERE

Installing the adb driver for the Nextbook 9:
Vista and Win7
1. You can do this by plugging your Nextbook 9 into your computer using the cable that came with it.
2. Then on the nextbook 9, you want to make sure USB Debugging is enabled. You can do this by going to settings on the nextbook 9, then to development. Then make sure there is a check mark next to USB Debugging. (Windows might complain that it was un able to install the driver software. If so, you can close the windows that popup)
3. Next, on your computer download the file named "Nextbook 9 driver.zip" that can be found here: http://www.mediafire.com/?naz9jarl3u09aus
4. Once the download is completed, go to your downloads folder, and unzip the folder named "Nextbook 9 drivers"
5. Next, go to start, then type device manager.
6. Then click on device manger once it shows up.
7.0 Then it can be one of two options, once device manager loads:
7.1 If there is a device listed with an yellow triangle, right click on it and then go to properties, then go to details, and in the drop down menu select hardware Ids, and check to see if it lists "USB\VID_2207&PID_0000&REV_0222&MI_01" and "USB\VID_2207&PID_0000&&MI_01", if not, check to see if there is another device with a yellow tringle, and check it. If none of these match then go to step
7.2 If you do not find your device listed with a yellow trianlge, then it has been installed as a Universial serial bus controller. Click on "Universal Serial Bus Controller" to open the devices installed in that category, and scroll to "USB Composite Devices" If there is more than one, then you have to right click on each one and go to properties, then go to details, then in drop down menu, select Hardware Ids, and find the one that lists "USB\VID_2207&PID_0000&REV_0222&MI_01" and "USB\VID_2207&PID_0000&&MI_01" as its hardware id.
8. Now, once you have found your device in the device manager, you want to right click on it, and choose to "update driver software" then choose "browse my computer for driver software"
9. Then click on the browse button and navigate to where you unzipped the folder called "Nextbook 9 driver" (probably in your downloads folder if you did not change it), and select the unzipped folder called "Nextbook 9 driver" then press ok.
10. Now press next, and the driver software should install. Windows will warn you that it cannot verify the publisher of this software. Choose to "Install anyway" (I only updated the setup information, i did not create the software. I obtained this software from a post by domrad through this this website. i downloaded the software from this link: http://www.freaktab.com/showthread.p...sing-ADB-guide )
11. If it finishes with no errors, move on to rooting.
12. If it does not install, start from step 1 again.

Win XP
1. You can do this by plugging your Nextbook 9 into your computer using the cable that came with it.
2. Then on the nextbook 9, you want to make sure you USB Debugging enabled. You can do this by going to settings on the nextbook 9, then to development. Then make sure there is a check mark next to USB Debugging. (Windows might complain that it was un able to install the driver software. If so, you can close the windows that popup)
3. Next you want to download the file named "Nextbook 9 driver.zip" that can be found here: http://www.mediafire.com/?naz9jarl3u09aus
4. Once the download has completed, go to your downloads folder, and unzip the folder named "Nextbook 9 drivers" (Make sure the tablet is still plugged into the computer, or plug it in now)
5. Now, press start and go to control panel. Then open "Add Hardware"
6. Now press next and it will search for software. Now there are two possibilities
7.1 If it finds it at this point, good. Just choose to "Install from a list or specific Location (Advanced)" and press next. Then press browse, and go to the unzipped "Nextbook 9 Driver" folder and press ok.
OR (you can skip to step 8 if your device has installed)
7.2 If it does not find it automatically, it will ask you "Have you already connected the hardware to your computer?" select "Yes, i have already connected the hardware" and press next.
7.2.1 It will then bring up a list, and you need to scroll all the way down to the bottom of it and select "Add new hardware device" then press next.
7.2.2 It will then ask you "What do you want the wizard to do?" select "Install the hardware that i manually select from a list (Advanced)" then press next.
7.2.3 Now select "Show All Devices" and press next.
7.2.4Now it will bring up options to choose "Manufacturer" and "Model" ignore these and press "Have Disk"
7.2.5Now press "browse" and go to the unzipped "Nextbook 9 Driver" folder, double click it and select a file named "android_winusb.inf" then press "open"
7.2.6Now press "OK" Then press next, then press next again.
7.2.7 It will now install the driver. When it finishes it will say "The following hardware was installed: %ADB_INTERFACE% and it will also say "The software for this device is now installed, but may not work correctly. The device cannot start. (Code 10)" This is just fine do not worry.
7.2.8 Now press finish.
7.2.9 Now i want you to open device manager. (You can do this by pressing start, right clicking on my computer and going to properties, then go to hardware and click device manager)
7.2.10 Once device manger is open, you will see a category called "android phone" with "%ADB_INTERFACE%" listed under it with a yellow circle and an exclamation point. Right click on "%ADB_INTERFACE%" and select "scan for hardware changes" Your device should now install.
7.2.11If not try restarting your computer and then open device manager and see if there is still a yellow circle next to "%ADB_INTERFACE%"
8. Now in Device Manger, open the category named "Android Phones" then right click on "%ADB_INTERFACE%" and then go to properties, then go to details, and in the drop down menu select hardware Ids, and check to see if it lists "USB\VID_2207&PID_0000&REV_0222&MI_01" and "USB\VID_2207&PID_0000&&MI_01" if so, your ADB Driver is now installed.

Now you need to root your Nextbook 9:
1. In order to root this tablet, you need to download a one step tool called "Bin4ry" yo your computer, use this link to do so: http://uploaded.net/file/h44f6vni once the page is loaded, click on the free download button, and wait for the timer to count down. then type in the capatcha, and the download should begin.
2. Once you have finished downloading, go to your downloads folder and unzip the folder named "Root_with_Restore_by_Bin4ry_v15".
3. Make sure your nextbook 9 is still plugged into the computer (or plug it in now), and go to the settings on the nextbook 9, then go to storage, and in the upper right corner click the menu button, then click USB Computer Connection.
4. Now on your computer, open the unzipped "Root_with_Restore_by_Bin4ry_v15" folder, and double click the file called RunMe
5. It will open a new window (a type of command prompt)
6. Now type 1 and press enter.
7. Now follow the instructions it will give you (such as "unlock device and press restore" or something like that, it does not get difficult, and should only take 2-5 minutes to complete. And as a warning, when it tells you to press restore on your device, all it is doing is resetting some of your settings, for example your wallpaper. It does not reset anything such as saved accounts, wifi setting, sound settings, etc. and it does not remove any applications. Also, it will reboot your device atleast twice, so do not try to do it yourself when it says "rebooting device", just wait and it will complete).
8. When the program is done and your nextbook 9 is fully rebooted, you can close the bin4ry window.

Installing Google Play:
1. On your Nextbook 9, open your browser, and go to:

http://download.estrongs.com/app-es-file-explorer.html

2. If it asks you to save then save it. Once the download is complete, install it. This will install ES file explorer. When done installing, press done.
3. Now on your computer, download the file named "Play For Nextbook 9.zip" that can be found here: http://www.mediafire.com/?at464o0s985ucp4
4. Once it is done downloading, go to your downloads folder, and Unzip the folder "Play For Nextbook 9" and open the unzipped folder (keep this window open)
5. Now make sure your Nextbook 9 is still plugged into your computer (if not, then plug it in now), and turn on USB storage.
6. Now on your computer, open my computer and navigate to your nextbooks internal storage. Make a new folder, and leave the name as "new folder", or what ever you like. Open it.
7. Now copy everything from the unzipped "Play For Nextbook 9" folder to the "new folder" folder on your nextbook.
8. Now eject your nextbook from your computer. Then turn off usb storage on the nextbook.
9. FOLLOW THE NEXT STEPS CAREFULLY. Now open ES file explorer on your nextbook 9.
10. Press the menu button (or option button as some might call it), and go to settings. Then scroll down to root settings. Put a check mark next to "Root Explorer" and a window will pop up asking to deny or grant. CHOOSE GRANT. Then put a check mark next to "up to root" and "mount file system"
11. Now press the back button twice.
12. Open the folder named "sdcard" then find the "new folder" folder or what ever you had named it and open it (if you can't find it there, press the back button once, and go to the folder named "external_sd" and look there).
13. Now at the top off the screen there is a options bar, with options such as "favorite" "select" "search" etc. Press the "select" option.
14. Now tap each of the files in the "new folder" folder once, so that each one's font has turned green.
15. Now on the options bar press "copy"
16. Now press the back button three times.
17. Now open the folder called "system" then open the folder called "app"
18. Now on the options bar press "paste"
19. Once it has finished (should take about 10 seconds) press the home button and restart your nextbook 9. When it loads YOU WILL HAVE GOOGLE PLAY. (may take a minute for it to show up)
20. Open google play and setup your account.

If you need any help or trouble shooting, send me a message.

James

[JamesCozzby]

Can't figure out the browser problem

If it weren't for the lack of the Play market and the often crashing out of the browser problems, it wouldn't be too bad. Time to start trying to get this thing rooted, I guess.

Thats now the most annoying bug i have found... I dont know why the browser crashes, or what could be a fix. I tried many, many different browsers and they all do this. I saw at one point that the fix was to turn off java script, but the crashes continue. Ill keep my out for a solution to the browser issue. But as far as google play, thats all working now

[Silicon Orb]

Thats now the most annoying bug i have found... I dont know why the browser crashes, or what could be a fix. I tried many, many different browsers and they all do this. I saw at one point that the fix was to turn off java script, but the crashes continue. Ill keep my out for a solution to the browser issue. But as far as google play, thats all working now

At this point, I wish that was my only issue. I've had a nightmare scenario playing out with my tablet (ok, no bricks, but it's driving me crazy). The first issue I had was getting ADB to see the tablet. Thought it was a driver problem and re-installed about a dozen times in different ways. Nothing helped. So my solution to that one was creating an adb_usb.ini file in my .android folder on the PC. Inside the file is a single line with the USB VID for the tablet. If anyone needs to do this the line is "0x2207', without the quotes. After I added this file, ADB picked it right up and rooting was no problem.

Everything else went fine, ES explorer, root setup, Google Play install, no problem. That is, until I re-booted. Now, I'm in some awful loop with the Startup Wizard, which seems to come up only after the Play installation. It tells me to click on the Android, which I do, and the app crashes and restarts, effectively locking me out of the tablet. I can get to settings, etc. but can't run any apps. Tried stopping just about every running process, but this thing keeps coming back. I've probably reflashed and rooted the thing 7 times, and every time it's the same story.

I have one more thing to try before I get stumped. The next time I flash the bugger, I'll look in the "About Tablet" section at the "Startup Wizard" setting. Hopefully, I can turn it off from there before re-booting, but if not, I am screwed. Is there a system configuration file somewhere which can be modified to keep this from auto-executing?

Also, does anyone know of a list of apps which can be safely deleted from Android without buggering the important functions of the system? Looks like there is a lot of stuff to be cleaned out of this thing, and the additional memory could help to keep the browser from tanking so often.

Thanks again for all the help and info!

[JamesCozzby]

hmmm

once you have google play installed an configured, you can delete the setup wizards apk file from the system/app using ES file manager, then reboot. I have not encountered this problem, but i am sorry to hear you are having such difficulties.

[Silicon Orb]

once you have google play installed an configured, you can delete the setup wizards apk file from the system/app using ES file manager, then reboot. I have not encountered this problem, but i am sorry to hear you are having such difficulties.

UPDATE: Finally got past the issue. You are probably correct that this issue wouldn't arise if google play was configured and signed into after being placed into the system/app folder, before a reboot, but the instructions said to restart it. This step may not be necessary, as the Market showed up on it's own after setting up the WiFi.

The way I got around the problem was to re-flash and then move everything but the SetupWizard.apk from the Play folder to the system/app folder. Seemed to work fine without it, so I recommend that folks who don't need the software hand-holding do the same. If they run into the same issue with this, a re-flash will be in their future.

Maybe there is a minor hardware difference with my tablet, or maybe the gods hate me . Hopefully my trials will help others out if they find themselves in similar situations.

Thanks again.

[JamesCozzby]

Thanks for the update!!

I will make a new folder that does not contain the setup file! Thanks for the update!

James

UPDATE: updated the link in my procedure, and it now does not contain the setup apk