Greetings, i have an nextbook - model in the back says netx8p12 and i tried to flash in several roms but all have the same problem. the image
dont fufill all the display.
The display is 8inch, in the website of the manufacter is 800x600 resolution so i downloaded the Oma_Odys_Loox_JB_4.1.1_v1.2.2a and flashed
with RKAndroid 1.29, all the files included except the kernel of the kernel_308_neo_x8_odys that belong to the next8p12.
I think i did ok but the problem is that image is like this images i uploaded
can anyone help me on this? like i´m really dumb person?
Big big thanks
joão
just found something.
i´ve downloaded one software from market, lcd resolution and it says:
width :464 dpi
density : 1
resolution : 464x320
Im with you
jfbbms said:
just found something.
i´ve downloaded one software from market, lcd resolution and it says:
width :464 dpi
density : 1
resolution : 464x320
Click to expand...
Click to collapse
If you make any progress let me know!
I bought one on Black Friday and haven't seen a successful flash yet...
Android System Info dump
Ok so let's get some information gathering rolling on this tablet.
Here's the dump:
Code:
OS
Browser UserAgent : Mozilla/5.0 (Linux; U; Android 4.0.4; en-us; Next8P12 Build/IMM76I) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Safari/534.30
Android ID : [Removed]
Uptime : 0 days, 3 hours, 9 minutes, 27 seconds
Uptime (without sleeps) : 0 days, 3 hours, 9 minutes, 27 seconds
Configuration
Font Scale : 1.15
Hard Keyboard Hidden : YES
Keyboard : NOKEYS
Keyboard Hidden : NO
Locale : en_US
MCC : 0
MNC : 0
Navigation : DPAD
Navigation hidden : NO
Orientation : PORTRAIT
Screen Height DP : 1018
Screen Width DP : 800
Smallest Screen Width DP : 600
Screen Layout :
LONG_NO
SIZE_LARGE
SIZE_NORMAL
SIZE_SMALL
Touchscreen : FINGER
UI Mode :
NIGHT_NO
TYPE_NORMAL
BuildInfos
Android version : 4.0.4
Release Codename : REL
API LEVEL : 15
CPU ABI : armeabi-v7a
Manufacturer : YIFANG
Bootloader : unknown
CPU ABI2 : armeabi
Hardware : amlogic
Radio : unknown
Board : M805MC
Brand : MID
Device : Next8P12
Display : V1.0.6.IMM76I.eng.root.20120917
Fingerprint : MID/NXM805MC/NXM805MC:4.0.4/IMM76I/eng.root.20120917.120120:user/release-keys
Host : midcs-desktop
ID : IMM76I
Model : Next8P12
Product : Next8P12
Tags : release-keys
Type : user
User : root
Battery
Charging in progress...
Level : 83 %
Technology : LiFe
Temperature : 30.0 ∞C (86.0∞F)
Voltage : 4007 mV
Memory
Download Cache Max: 128MB/ Free: 110MB
data Max: 440MB/ Free: 92.89MB
External storage: shared
External storage Max: -16384.00B/ Free: -16384.00B
External storage removable: false
External storage emulated: false
Total RAM: 413MB
Free RAM: 74.62MB
Threshold RAM: 41.50MB
Low Memory Killer Levels
FOREGROUND_APP:__ 17.00MB
VISIBLE_APP:_________ 22.50MB
SECONDARY_SERVER: 28.00MB
HIDDEN_APP:________ 36.00MB
CONTENT_PROVIDER: 41.50MB
EMPTY_APP:__________ 50.00MB
Telephony
Data Activity: DATA_ACTIVITY_NONE
Data State: DATA_DISCONNECTED
IMEI(or MEID): 510121043471011
IMEI/SoftVer: null
MSISDN: null
Registered MCC:
Registered MCC MNC:
Registered Operator Name:
Network Type: NETWORK_TYPE_UNKNOWN
Phone Type: PHONE_TYPE_NONE
SIM Country Code:
SIM MCC MNC:
SIM Operator Name:
SIM Serial Number: null
SIM State: SIM_STATE_UNKNOWN
Subscriber ID(IMSI): null
VoiceMail number: null
Roaming: false
No Cell detected
Networks
Background Data Usage: true
type mobile[UNKNOWN]
state UNKNOWN/IDLE
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable false
type WIFI[]
state CONNECTED/CONNECTED
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable true
type ethernet[]
state UNKNOWN/IDLE
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable false
type WIFI[]
state CONNECTED/CONNECTED
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable true
Wifi
State: WIFI_STATE_ENABLED
Current access point: SSID: [Removed], BSSID: [Removed], MAC: [Removed], Supplicant state: COMPLETED, RSSI: -19, Link speed: 65, Net ID: 0, Explicit connect: false
DHCP info: ipaddr 192.168.254.42 gateway 192.168.254.254 netmask 255.255.255.0 dns1 192.168.254.254 dns2 0.0.0.0 DHCP server 192.168.254.254 lease 86400 seconds
Last Scan:
0 SSID: [Removed], BSSID: [Removed], capabilities: [WPA2-PSK-CCMP][ESS], level: -42, frequency: 2412
Configured Networks:
0 ID: 0 SSID: "MCLAREN-DSL" BSSID: null PRIO: 1 KeyMgmt: WPA_PSK Protocols: WPA RSN AuthAlgorithms: PairwiseCiphers: TKIP CCMP GroupCiphers: WEP40 WEP104 TKIP CCMP PSK: * eap: phase2: identity: anonymous_identity: password: client_cert: private_key: ca_cert: IP assignment: DHCP Proxy settings: NONE LinkAddresses: [192.168.254.42/24,] Routes: [0.0.0.0/0 -> 192.168.254.254,] DnsAddresses: [192.168.254.254,]
CPU
Processor ARMv7 Processor rev 4 (v7l)
BogoMIPS 1011.71
Features swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer 0x41
CPU architecture 7
CPU variant 0x2
CPU part 0xc09
CPU revision 4
Hardware AMLOGIC MESON3 8726M SKT SH
Revision 0020
Serial 000000000000000c
Frequency range: 100.0 -> 1000.0MHz
Current Frequency: 650.0MHz
Frequency Stats (time):
Camera
As retreiving camera infos can give the impression that it is taking picture on some device, it is not enabled by default. If you wish to, go in settings menu.
Screen
Resolution: 600 x 764
Refresh Rate: 50.0
X factor for DIP: 0.75
Density: 120 dpi
Pixel per inch X: 160.0 dpi Y: 160.42105 dpi
OpenGL
As retreiving opengl infos can crash some device, it is not enabled by default. If you wish to, go in settings menu.
Sensors
MMA 3-axis Accelerometer: 0.2 mA by Freescale Semiconductor Inc.
Environment
Root Directory: /system
Data Directory: /data
Download Cache Directory: /cache
External Storage State: shared
External Storage Directory: /mnt/sdcard
Medias Directories
Alarms: /mnt/sdcard/Alarms
DCIM: /mnt/sdcard/DCIM
Downloads: /mnt/sdcard/Download
Movies: /mnt/sdcard/Movies
Music: /mnt/sdcard/Music
Notifications: /mnt/sdcard/Notifications
Pictures: /mnt/sdcard/Pictures
Podcasts: /mnt/sdcard/Podcasts
Ringtones: /mnt/sdcard/Ringtones
Features
android.hardware.wifi
android.hardware.location.network
android.hardware.location
android.hardware.touchscreen.multitouch
android.hardware.screen.landscape
android.hardware.screen.portrait
android.hardware.faketouch
android.hardware.usb.accessory
android.hardware.touchscreen.multitouch.distinct
android.hardware.microphone
android.hardware.location.gps
android.hardware.camera.front
android.software.live_wallpaper
android.hardware.sensor.accelerometer
android.hardware.touchscreen
glEsVers=2.0
JavaProperties
java.vendor.url: [Removed, under 10 posts]
java.class.path: .
java.class.version: 50.0
os.version: 2.6.34
java.vendor: The Android Project
user.dir: /
user.timezone: null
path.separator: :
os.name: Linux
os.arch: armv7l
line.separator:
file.separator: /
user.name:
java.version: 0
java.home: /system
Mount points
MountPoint
Name Type Options
- /
rootfs rootfs rw
- /dev
tmpfs tmpfs rw,nosuid,relatime,mode=755
- /dev/pts
devpts devpts rw,relatime,mode=600,ptmxmode=000
- /proc
proc proc rw,relatime
- /sys
sysfs sysfs rw,relatime
- /acct
none cgroup rw,relatime,cpuacct
- /mnt/asec
tmpfs tmpfs rw,relatime,mode=755,gid=1000
- /mnt/obb
tmpfs tmpfs rw,relatime,mode=755,gid=1000
- /dev/cpuctl
none cgroup rw,relatime,cpu
- /system
ubi0_0 ubifs rw,relatime
- /data
ubi1_0 ubifs rw,nosuid,nodev,relatime
- /cache
/dev/block/mtdblock6 yaffs2 rw,nosuid,nodev,relatime
- /proc/bus/usb
none usbfs rw,relatime
I plan on rooting this thing. As soon as I get that sorted out I may post more.
Also we're dealing with a M805MC (Amlogic 8726-M3) chip instead of RockChip RK2918.
I have attached images of both chips.
The mfg is Shenzhen Yifang Digital Technology Co., Ltd. and the build location is Guangdong, China. I'm under 10 posts so that's why no links but I can produce them upon request.
Ok this is sort of important so I will try to get the link in here.
Drum roll please....
Source code:
openlinux.amlogic.com/wiki/index.php/Arm/Platform_Info/Information_for_8726M/Build_system_for_8726M_Howto
If a moderator would like to make that link hot, be my guest .
I also purchased one of these tablets on Black Friday. It was on sale for 80.00 at Big Lots....Unfortunately its missing Google Apps, so rooting it would be nice...Although I really have absolutely no idea what I am doing, I did get ADB working and was able to reboot the device into some type of stock recovery, so with that in mind, please let me know if there is anything I can do to help...
Also either the HDMI port is shot after using it for just a few minutes or I have a bad cable...It was nice while it worked though.
Not having Google Apps is a bummer, but using info I found here: http://forum.xda-developers.com/showthread.php?t=1895040 I was able to get Gmail, Google Voice, Google Drive, Google Music, and Google + working. I also tried installing Google Talk, but ended up doing a factory reset because after I installed it...all the other Google Apps I had installed started crashing and I wanted to just start from scratch.
joelee100 said:
I also purchased one of these tablets on Black Friday. It was on sale for 80.00 at Big Lots....Unfortunately its missing Google Apps, so rooting it would be nice...Although I really have absolutely no idea what I am doing, I did get ADB working and was able to reboot the device into some type of stock recovery, so with that in mind, please let me know if there is anything I can do to help...
Also either the HDMI port is shot after using it for just a few minutes or I have a bad cable...It was nice while it worked though.
Not having Google Apps is a bummer, but using info I found here: http://forum.xda-developers.com/showthread.php?t=1895040 I was able to get Gmail, Google Voice, Google Drive, Google Music, and Google + working. I also tried installing Google Talk, but ended up doing a factory reset because after I installed it...all the other Google Apps I had installed started crashing and I wanted to just start from scratch.
Click to expand...
Click to collapse
I know I already clicked thanks but seriously, thanks again man. I don't think I personally have the skillset to root this thing so I humbly tip my hat to whomever gets it done. I do know that shutdown then vol up + plug usb in puts it in jtag mode . Shows as 'M3-CHIP' in devmgmt.msc (M3 being the CPU revision)
Sent from my Next8P12 using XDA Premium HD app
joelee100 said:
I also purchased one of these tablets on Black Friday. It was on sale for 80.00 at Big Lots....Unfortunately its missing Google Apps, so rooting it would be nice...Although I really have absolutely no idea what I am doing, I did get ADB working and was able to reboot the device into some type of stock recovery, so with that in mind, please let me know if there is anything I can do to help...
Also either the HDMI port is shot after using it for just a few minutes or I have a bad cable...It was nice while it worked though.
Not having Google Apps is a bummer, but using info I found here: http://forum.xda-developers.com/showthread.php?t=1895040 I was able to get Gmail, Google Voice, Google Drive, Google Music, and Google + working. I also tried installing Google Talk, but ended up doing a factory reset because after I installed it...all the other Google Apps I had installed started crashing and I wanted to just start from scratch.
Click to expand...
Click to collapse
I purchased 3 of these on Black Friday and have been unable to root them because of the aml8726-m34 chip. How did you get ADB working? What driver did you use? How did you get into recovery? I didn't think these tablets had any recovery interface.
I'm glad to hear that you did have some luck installing some of the google apps. Thanks for posting!
shaunmt said:
I purchased 3 of these on Black Friday and have been unable to root them because of the aml8726-m34 chip. How did you get ADB working? What driver did you use? How did you get into recovery? I didn't think these tablets had any recovery interface.
I'm glad to hear that you did have some luck installing some of the google apps. Thanks for posting!
Click to expand...
Click to collapse
I got in with the generic Google USB driver pesonally. You won't have root access though. Typing su from shell just gives a message about su not being found in the bin folder. Recovery is vol up + power or you can get there by putting a 3rd party zip on the sd card and then to to the upgrade app. It won't work because it's stock recovery. Oh, and for recovery to even see a .zip file it has to be on an external sd card.
Sent from my Next8P12 using XDA Premium HD app
---
[Update]
I've created a thread here to get people's attention as most people (like I was at first) are confusing this for the Next8SE or other Nextbooks. Hopefully the issue having it's own address will help make the information gathering process quicker.
mascondante said:
I got in with the generic Google USB driver pesonally. You won't have root access though. Typing su from shell just gives a message about su not being found in the bin folder. Recovery is vol up + power or you can get there by putting a 3rd party zip on the sd card and then to to the upgrade app. It won't work because it's stock recovery. Oh, and for recovery to even see a .zip file it has to be on an external sd card.
Sent from my Next8P12 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for the tips! I'll try to get a rom dump tonight!
Anytime. I've shot Yifang/Nextbook an email asking for their source code. Hopefully they will comply as firmware does have software covered under GPL.
Also I brought up Netflix. Several Nextbook devices have a firmware update to address the issue. I'm assuming whatever the bug was, it was migrated inadverently to this device's code. Can I get some confirmation from other users that this is a shared issue? Thanks.
Finally, I noticed there is a Nextbook w/ Google Play so I also inquired about Gapps/Play being included in a future update. I will relay whatever information I recieve.
Sent from my Next8P12 using XDA Premium HD app
shaunmt said:
I purchased 3 of these on Black Friday and have been unable to root them because of the aml8726-m34 chip. How did you get ADB working? What driver did you use? How did you get into recovery? I didn't think these tablets had any recovery interface.
I'm glad to hear that you did have some luck installing some of the google apps. Thanks for posting!
Click to expand...
Click to collapse
I also pretty sure I used the generic Google USB driver. With the tablet turned on and usb debugging enabled I plugged it into the computer and then I updated the driver in device manager and then ADB worked...using the command "adb reboot recovery" got me into recovery...
Also, worth noting I guess, if my memory is correct...I think Windows 7 searched the internet and automatically installed some type of ACER driver. The Acer driver may have also worked, but I got rid of it and went with the generic Google driver(since it obviously wasn't an Acer device)...
Also, I noticed that the OP was able to flash a rom using the RKAndroid update tool, which is used for flashing firmware to a Rockchip based Android tablet. Are we able to confirm what chip the original posters device is running? I ask because it seems, like mascondante pointed out, that the next8p12 has shipped with different chips over time? The black Friday ones running the armlogic M3-chip and the earlier ones being a Rockchip RK2918?
joelee100 said:
I also pretty sure I used the generic Google USB driver. With the tablet turned on and usb debugging enabled I plugged it into the computer and then I updated the driver in device manager and then ADB worked...using the command "adb reboot recovery" got me into recovery...
Also, worth noting I guess, if my memory is correct...I think Windows 7 searched the internet and automatically installed some type of ACER driver. The Acer driver may have also worked, but I got rid of it and went with the generic Google driver(since it obviously wasn't an Acer device)...
Also, I noticed that the OP was able to flash a rom using the RKAndroid update tool, which is used for flashing firmware to a Rockchip based Android tablet. Are we able to confirm what chip the original posters device is running? I ask because it seems, like mascondante pointed out, that the next8p12 has shipped with different chips over time? The black Friday ones running the armlogic M3-chip and the earlier ones being a Rockchip RK2918?
Click to expand...
Click to collapse
All Nextbook 8 Premium SE roms I've found online were for the RK2918 chip using the RKAndroid tool... it might be possible to modify the Rockchip driver to recognize the AML8726-M3 chip, and maybe even flash one of the available roms, but it almost certainly wouldn't boot.
I wonder if the Bin4ry tool from this thread will work on these? It looks like it should work on anything with ADB working.
http://forum.xda-developers.com/showthread.php?t=1886460
shaunmt said:
All Nextbook 8 Premium SE roms I've found online were for the RK2918 chip using the RKAndroid tool... it might be possible to modify the Rockchip driver to recognize the AML8726-M3 chip, and maybe even flash one of the available roms, but it almost certainly wouldn't boot.
I wonder if the Bin4ry tool from this thread will work on these? It looks like it should work on anything with ADB working.
http://forum.xda-developers.com/showthread.php?t=1886460
Click to expand...
Click to collapse
I tried that tool and it didn't work, although it seemed to recognize the device...But I don't think I tried it while the device was actually turned on and booted(I'm not 100 percent sure), rather I think I tried it when I the device was in what i believe was jtag mode...I'll try again later.
EDIT: Crap...I tried while booted and having adb working...No dice...
joelee100 said:
I tried that tool and it didn't work, although it seemed to recognize the device...But I don't think I tried it while the device was actually turned on and booted(I'm not 100 percent sure), rather I think I tried it when I the device was in what i believe was jtag mode...I'll try again later.
EDIT: Crap...I tried while booted and having adb working...No dice...
Click to expand...
Click to collapse
I tried it using option 1 and ended up with a boot loop after the first splash screen. Was able to boot to recovery and do a factory reset.
Tried it with option 2 and it went through the process with several errors and booted ok, but did not achieve root.
I've also tried using recovery to install signed update packages with superuser and busy box, or even just gapps, but it refuses everything, indicating that signatures can not be verified successfully.
I'm currently trying to find a way to get read/write access in ADB or ADB shell, as this seems to be the big issue.
I agree, it also looks like ADB is the prevalent obstacle here. I'd like to at the very least get Android Market and all the crapware off this thing. I told someone this would be a great buy for a christmas present at BigLots as I was under the impression, after reading up on the RK29 devices, that they were rootable and I could get a custom rom onto it for them. I don't want to be the bearer of bad news!
amesfan said:
I agree, it also looks like ADB is the prevalent obstacle here. I'd like to at the very least get Android Market and all the crapware off this thing. I told someone this would be a great buy for a christmas present at BigLots as I was under the impression, after reading up on the RK29 devices, that they were rootable and I could get a custom rom onto it for them. I don't want to be the bearer of bad news!
Click to expand...
Click to collapse
I don't think there is anything we can do with these without an official update.zip from Nextbook.
I'm not talented enough to 'crack this nut' solo but I will keep looking across the web for a potential solution. I've been under the weather; Sorry for not staying mode on top of this.
I'm guessing the jtag mode is the key here. I'll keep looking.
Sent from my Next8P12 using XDA Premium HD app
mascondante said:
I'm not talented enough to 'crack this nut' solo but I will keep looking across the web for a potential solution. I've been under the weather; Sorry for not staying mode on top of this.
I'm guessing the jtag mode is the key here. I'll keep looking.
Sent from my Next8P12 using XDA Premium HD app
Click to expand...
Click to collapse
I got this response from Nextbook today concerning the Netflix update:
Thank you for the email. Please note, we're experiencing Technical difficulty with the
Next8P12 models that have an Android OS system level of 4.0.4. The Netflix Update
was issued for the Android OS systems with 4.0.3 models. Therefore, the configuration
of the update is unable to be recognized by the 4.0.4 OS units. However, we have
contacted Netflix to provide to us a patch for this model. We appreciate your understanding,
patience and apologize for the inconvenience.
When that update becomes available, it will likely be packaged as an update.zip (Like the existing one), which can be modified to give us root access.
Hi
I'm trying to boot up remix OS in HDD on a Toshiba laptop of 2006 with those specification
Intel Celeron M370
ATI Graphics
512 MB of ram
80 GB HDD
After successful installation it normally reboot to boot manager and I can select remix os to boot, and then it says:
Booting 'Resident Mode - All your data and apps are saved'
(hd0,0)
Filesystem type is NTFS, partition type 0x7
[Linux-bzImage, setup=0x3e00, size=0x4f4480]
[Linux-initrd @ 0x1b9d9000, 0x4b65ae bytes]
early console in decompress_kernel
input_data: 0x01556101
input_len: 0x004eb268
output: 0x01000000
output_len: 0x00a30490
run_size: 0x00adc000
Decompressing Linux... Parsing ELF... No relocation needed... done.
Booting the kernel.
Click to expand...
Click to collapse
Then there is a problem, because after 2 seconds it says:
[ 1.959044] intel_powerclamp: Intel powerclamp does not run on family 6 model 13
[ 1.961135] intel_rapl: driver does not support CPU family 6 model 13
Click to expand...
Click to collapse
I know that hardware is much weak, but seems like there are problems with powerclamp and intel_rapl, somethings related to driver.
There is something I can do to boot up Remix OS on this PC?
I have the same problem. But mine says "Cpu family 6 model 23"...
My laptop is a Samsung R430 from 2010.
Core 2 duo T6600 2.2GHz
6GB RAM
I'm trying to run it form usb though.
Sent from my G760-L03 using Tapatalk
Maybe some CPUs families aren't currently supported.
I could boot Remix OS on Intel Celeron 1007U x64 and on an Intel Core i7 2nd generation.
Someone can confirm?
hmm..
I also see this at boot... : intel_rapl: driver does not support CPU family * model * (intel d525)
But RemixOS 32bit is booting/working fine
Its some kind of cpu throtle driver ( to keep heat down ) if I read correctly
https://wiki.ubuntu.com/Kernel/PowerManagement/ThermalIssues
My system.. however.. is running cool (so, the driver is not needed)
A thought::
Try booting with : DEBUG=1
mitchell4you said:
hmm..
I also see this at boot... : intel_rapl: driver does not support CPU family * model * (intel d525)
But RemixOS 32bit is booting/working fine
Its some kind of cpu throtle driver ( to keep heat down ) if I read correctly
https://wiki.ubuntu.com/Kernel/PowerManagement/ThermalIssues
My system.. however.. is running cool (so, the driver is not needed)
A thought::
Try booting with : DEBUG=1
Click to expand...
Click to collapse
Uhm, thanks I'll try.
Where I have to add it?