Nextbook Premium 7 SE w/ ICS

[rfrayer]

http://video.freaktab.com/?subpath=f...root_gplay.zip

im ggetting Freaktab videos are only available to registered and logged-in users of Freaktab.com
You can Register or Login to our forum to access our video server and our videos.

not sure why ive enabled cookies restarted cleaned cache???

evermind i didnt notice the save password part

[Damo]

im ggetting Freaktab videos are only available to registered and logged-in users of Freaktab.com
You can Register or Login to our forum to access our video server and our videos.

not sure why ive enabled cookies restarted cleaned cache???

When you log in enter your user name password but also click the small box remember me.

Now try again

Sent from Xperia Mini Pro ~ Android 4.0.4 ICS

[rfrayer]

yeah it worked ... i need to pay more attention

[mihai_mx]

I can confirm the ROM is working also with P7SE YF051202590. Only issue so far is with OTA.
Thanks Bob for the great work and it would be great if time allows to make a bloat-free version...

Anyway what is interesting is that on the box if you peel of the YF0512 is anoter label with YF0312 Not sure if the box is reused our what...

[defdylan]

Working on YF04121

Confirmed that the ROM is working on Nextbook Premium 7SE YF04121, same OTA error, fixed after debloat. What I want to know is where is the contacts/people app that usual comes with the android os?

[kaligola]

mine is (was) 'YF0312xxxx and i successfull installed nextbook7p12se_root_gplay.zip but unfortunately decidet to try to get back to original rom and downloaded 7p1 image. now can only see red led if on charging but device cannot connect to recovery tool i always get unknown device and cant recover this on site i see there is only netflix firmware update ohters are for 7p1. any hint for this?
gonna get couple of days at beach hope once back im enaugh lucky to get it back in order
br kaligola

[DocHoppy]

Raw dump

Fin can you either P.M. a link for the dump file that was sent to you for the next7p1n-ics?

[Finless]

Doc, these damn model numbers for nextbook are nuts. So I do not even know really what model your talking about anymore! I just root them as requested. But I also supply the stock versions too. They are all in here

http://www.freaktab.com/forumdisplay.php?96-NextBook-ROM-s-by-Finless-Bob

Bob

[kaligola]

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 :-)

i have 7SE capacitive tablet YF032xxxx with camera and hw volume buttons

with this trick can i root device with unlockroot? because i'm tring to do modding with rk29xx image tools modfied for new roms but i have always error on rooting . even with wendal tool ..

id like to success without do another brick

[auroden]

USB drivers problem on Nextbook 7S

Androider! You are the man! ... 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!
...
Randy.

Hey Randy, I am going through the same problems here, I edited the android_winusb.inf and I got Android Composite ADB Interface listed in My Device Manager but I can't find anywhere the adb_usb.ini file on my Win 7 machine. I can't connect SuperOneClick or UnlockRoot to my tablet, device is not recognized. I have installed Android SDK, enabled USB Debugging, Allowed mock locations and tried USB storage On and Off and it's still a no go. Any ideas? Thanks!

[Finless]

You may have to manually add the device. You need to know your USB device number by looking in device manager.

Then do this for Windows 7.
Go to C:/user/YOUR USER NAME/
and you should see a folder called .android If not create it.
Now in that folder create a text file called adb_usb.ini
Edit that and add your device ID.
For instance my Arnova ID is 0x0e79
So just add that in the file.

It should work then.

Bob

[auroden]

Still Nothing

You may have to manually add the device. You need to know your USB device number by looking in device manager.
Bob

Bob,

Thanks for your prompt reply. However it still does not work for me.
Per your instructions I created a new ini file in C:\Users\MyName\android\adb_usb.ini with the
ID# "0x2207" (no quotes)
The only thing I noticed that you guys always mention the name of the folder with a dot before the name and Windows doesn't allow the dot at all. The error message says "You must type a file name" thinking that that .android is an extension and not a name for the folder. How do you succeed to name the folder like that, if that is after all the reason for all this connectivity problems.
One more thing, you mention a lot the C:\ADB folder and other adb stuff. Is this another application to connect an Android device? I was just trying to use the above mentioned applications (SuperOneClick and UnlockRoot) to have root access. I remember that SuperOneClick kills the ADB server and UnlockRoot keeps trying to install driver without any success although the device is recognized in the Device Manager as an Android device.
I also may want to replace the stock ROM later on but not sure which version will work on mine with all this confusion related to the hardware revisions. Mine is Nextbook 7s, resistive screen with camera and microphone. The earlier model that Big Lots was selling was a capacitive screen without a camera.
Thanks again.

Edit: I actually found the ".Android" folder on the Root Directory of my second HDD, it was already created. I copied it back to the Users folder and it worked. So, SuperOneClick app already have progress and does not freeze. Still haven't done anything useful with it but I just wanted to update my post asap. Thanks for the very useful instructions!

[Finless]

It has to be a .android folder or it will not work.

Make the folder in another area not in /users. Then copy it to /users/myname/
And that should work.

Bob

[auroden]

It has to be a .android folder or it will not work.

Make the folder in another area not in /users. Then copy it to /users/myname/
And that should work.

Bob

Thanks Bob, I got it. I actually found the .android folder installed on my second hard disk so I copied it into the Users folder and it did recognize the tablet immediately.
After that, I was able to root the device with UnlockRoot application easily.
Unfortunately, although I am now able to install GooglePlay application (which I couldn't do it without superuser authority) the app shuts down a few seconds after opening. It is not that I have to have GooglePlay to get apps but this Nextbook7 device won't install any app from any website. I can only install apps manually by copying .apk files onto the microSD card. Unfortunately majority of websites don't have links to download a soft copy of the apps, they would rather install directly on your device which in my case is impossible. When clicking on the link to install, the browser reports the web page unavailable which actually isn't true, it is just a Google crap to prevent these incompatible devices to install any app directly. It seems to me that Google becomes another greedy Micro$oft corporation.
No wonder these Nextbook tablets are so cheap, they are useless being incompatible with most of the Android world. I guess they have to pay big money to join the Google club.
Thanks for all your help here though.

[Finless]

You cannot just install googleplay APK. There are many other files needed. Some of the more important ones go in the /framework folder and in the etc/permissions fiolder.

FInally you have to make sure the files you use are MADE for your SDK version. You cant use gapps from say gingerbread on ics.

Bob