You will find all downloads related to this port on http://codex.xiaoka.com/pub/meego/streak/
See the README file for installation instructions.
NOTE: Most current port information is on Wiki: http://codex.xiaoka.com/wiki/streak:meego
Current status:
booting Dell kernel release (2.6.29) configured for MeeGo
working image of MeeGo trunk
working MSM framebuffer console
working USB Eth networking
working WiFi connectivity
MSM X11 video driver crashes if xserver is running with root privileges
No MeeGo UI
No 3D acceleration
MeeGo ConnMan does not detect BCM4325 driver as WiFi capable
After booting plug the USB cable and issue the following commands (under Linux) to get shell access:
Code:
$ sudo ifconfig usb0 192.168.2.14 netmask 255.255.255.0
$ ssh [email protected]
[email protected]'s password: meego
[[email protected] ~]#
WOw this is good.
smokku said:
Finally made it boot.
http://www.youtube.com/watch?v=Bttgm1LwvzA
http://www.youtube.com/watch?v=RO2VV9c5t9c
Click to expand...
Click to collapse
Not to seem skeptic, but... that's it? I mean, I could probably make a bootscreen that looks like that... Could you tell us the source other than the Youtube video?
Awesome! Pure win!
egzthunder1 said:
Not to seem skeptic, but... that's it? I mean, I could probably make a bootscreen that looks like that... Could you tell us the source other than the Youtube video?
Click to expand...
Click to collapse
I would be skeptical as well but seeing as how its from smokku I trust him. Check out his site, he got ubuntu on the steal as well
Sent from my Dell Streak using XDA App
What is smeego?
Sent from my Dell Streak using XDA App
Taken from their site:
"MeeGo is an open source, Linux project which brings together the Moblin project, headed up by Intel, and Maemo, by Nokia, into a single open source activity. MeeGo integrates the experience and skills of two significant development ecosystems, versed in communications and computing technologies. The MeeGo project believes these two pillars form the technical foundations for next generation platforms and usages in the mobile and device platforms space."
So its Nokia's and Intel's rival to Google's Android using Linux....am I right? I've only just heard about meego myself
Basically MeeGo is a Linux distribution targeted for mobile devices.
If maemo is anything to go by..meego rules all..Only let down compared to android I had was solely lack of development and apps..Multi-Tasking was gods work on my n900..
I've been working hard on porting Dell (Qisda) changes to Qualcomm android-msm-2.6.35 tree for last weeks and it finally paid out:
Code:
MeeGo release 1.0.90 (MeeGo)
Kernel 2.6.35-rc6+ on an armv7l
localhost login:
with working USB Ethernet gadget:
Code:
$ lsusb | grep Eth
Bus 001 Device 037: ID 0525:a4a2 Netchip Technology, Inc. Linux-USB Ethernet/RNDIS Gadget
$ dmesg | tail
[12099.324219] usb 1-3: new high speed USB device using ehci_hcd and address 40
[12104.461572] usb 1-3: configuration #1 chosen from 1 choice
[12114.186244] usb 1-3: USB disconnect, address 40
[12133.508174] usb 1-3: new high speed USB device using ehci_hcd and address 41
[12133.652463] usb 1-3: configuration #1 chosen from 2 choices
[12133.660464] cdc_subset: probe of 1-3:1.0 failed with error -22
[12133.663265] usb0: register 'cdc_ether' at usb-0000:00:1a.7-3, CDC Ethernet Device, 3e:e8:79:e1:5b:f4
[12144.164055] usb0: no IPv6 routers present
$ ifconfig usb0
usb0 Link encap:Ethernet HWaddr 3e:e8:79:e1:5b:f4
inet6 addr: fe80::3ce8:79ff:fee1:5bf4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:384 (384.0 B) TX bytes:1528 (1.5 KB)
This should finally kickstart my MeeGo development.
Kernel is available at: http://gitorious.org/streak/kernel
That's awesome. Big ups.
Great work smokku! Keep it up.
gotta ask. is it meego for handsets or for tablets? i think the tablet version would work pretty well on our Streaks
http://codex.xiaoka.com/pub/meego/streak/ some stuff I'm working on.
Do not attempt this @home!!! - unless you know what you're doing.
smokku said:
http://codex.xiaoka.com/pub/meego/streak/ some stuff I'm working on.
Do not attempt this @home!!! - unless you know what you're doing.
Click to expand...
Click to collapse
Looks like the boot.img will allow a dual boot? For sure we're loading the OS from SD card. If no dual boot, it would just be a matter of reflashing a "stock" boot.img to get back to where we started, yes?
undrwater said:
Looks like the boot.img will allow a dual boot? For sure we're loading the OS from SD card. If no dual boot, it would just be a matter of reflashing a "stock" boot.img to get back to where we started, yes?
Click to expand...
Click to collapse
No dual boot (yet).
To get back to android you just need to reflash stock android boot.img.
Great job smokku..
smokku said:
No dual boot (yet).
To get back to android you just need to reflash stock android boot.img.
Click to expand...
Click to collapse
Awesome! Will try this upcoming weekend.
I just drastically simplified "installation" procedure.
No SD-Card repartitioning is required anymore.
Great work Smoku, congratulations; i don't have a clue, but does it come with a gui? is there something left to do to make it work completely?
id really like to see MeeGo running on streak, even just in video or photos for now ...
would it be possible for someone to build this driver for the SGSII
http://android.serverbox.ch/?p=285
ftdi_sio.ko
and
usbserial.ko
can someone compile these for me plese
i want to use the sgsII as my dashboad for my car but it connects via serial port to the ECU, i have chroot ubuntu 10.10 running on the sgsII so now all i need is the FTDI.ko file.
thanks in advance
You do run Ubuntu on SGS 2?
Emblema
Correct I have a working ch root I modified from a dell sterak one. Ill host it at some point with instructions.
The driver you asked
I got to compile those, for lite'ning 6.1 (android 2.3.4, kernel 2.6.36-11 ninphetamine 2.0.5+)
The modules loads with insmod:
{{{
# lsmod
ftdi_sio 25196 0 - Live 0xbf176000
usbserial 20872 1 ftdi_sio, Live 0xbf147000
dhd 245100 0 - Live 0xbf029000
j4fs 66440 1 - Live 0xbf013000 (P)
Si4709_driver 14444 0 - Live 0xbf00a000
bthid 2832 0 - Live 0xbf004000
vibrator 5408 2 - Live 0xbf000000
}}}
However from a console (I did not install ubuntoo), I plugged the device and still got in dmesg:
{{{
<6>[ 4367.754254] usb 2-1: new full speed USB device using s3c_otghcd and address 2
<3>[ 4367.771009] usb 2-1: device v0403 p6001 is not supported
<3>[ 4367.776871] hub 2-0:1.0: unable to enumerate USB device on port 1
}}}
I compiled the modules from https://github.com/Ninpo/ninphetamine/commit/2d1ffbcb9521299fdb53f681f65e7fe1230e0b32
If you still need those ko files, I attach them. I don't trust 100% my compilation (I had to cheat the versionmagic "+" in ninphetamine 2.0.5+), but they load OK according to lsmod and dmesg.
Please come back to me if you get some FTDI device to show in lsusb, or even better appear as ttyUSB device, I need that myself.
See http://forum.xda-developers.com/showthread.php?p=18081882#post18081882
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to Q&A
working usbserial.ko and ftdi_sio.ko
Thanks to siniy and many others, I have now been able to plug a FTDI USB device and get corresponding ttyUSB0, on a kernel based on ninphetamine. You will need a kernel and can't just do with a driver (the kernel must be compiled to accept that familly of devices).
Hey guys.
Note: I use Linux, and I've been trying to figure out how to copy stuff to my phone without Microsoft's crap called Zune Software.
So I was playing with my new Lumia 800 and I discovered Nokia's diagnostic app (available via dialing ##634#). In settings, it offers the possibility to switch the phone's USB connection to serial mode instead of Zune (after a reboot).
It seems indeed it does exactly that... Now my laptop shows a different USB vendor/product ID:
Code:
Bus 002 Device 005: ID 0421:05ed Nokia Mobile Phones
(This used to tell me it was a Microsoft device).
Unfortunately no driver claims this device ID (using kernel 3.0.9), but usb-devices shows that the phone now provides 4 interfaces:
Code:
...
T: Bus=02 Lev=02 Prnt=02 Port=01 Cnt=01 Dev#= 6 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0421 ProdID=05ed Rev=00.00
S: Manufacturer=Nokia
S: Product=RM-801|NOKIA Lumia 800
S: SerialNumber=xxx-xxxxxx-xxxx-xxxxxxx-xxxxx
C: #Ifs= 4 Cfg#= 1 Atr=c0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 1 Alt= 0 #EPs= 3 Cls=02(commc) Sub=ff Prot=ff Driver=(none)
I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
It seems the second one is a modem(-like) interface. Indeed, if I manually pass the ID to the usbserial module:
Code:
% sudo modprobe usbserial vendor=0x0421 product=0x05ed
It creates /dev/ttyUSB[0-4], and ttyUSB1 works as a serial modem, I can issue AT commands. E.g.
Code:
atz
OK
ati0
Manufacturer: QUALCOMM INCORPORATED
Model: 197
Revision: M7630A-AAEQMWZM-1.6.002479T 1 [Sep 16 2011 14:00:00]
IMEI: xxxxxxxxxxxxxxx
+GCAP: +CGSM,+DS,+ES
OK
This seems to be coming from the baseband... Probably the phone could now be used as a modem (I haven't bothered to do so yet).
The best would be of course if we could figure out how to use the other interfaces, and eventually get access to the storage of the phone.
this sounds interresting, did you nake more progress ?
interesting.
what does
sudo fdisk -l
Click to expand...
Click to collapse
show you?
Interesting...
Mind if I ask, what firmware is on your phone?
Hello,
Currently i'm working on a personal project to integrate my GS3 into my car display and audio. Well this was easy with the help of a MHL or Allshare Cast Dongle.
My next goal was to install a 4 wire resistive touchscreen on my car display and use it as an external touchscreen control. I bought a 7" 4 wire resistive touchscreen with a USB module build around the CYPRESS CY7C63723C chip. I hooked up the touchscreen with OTG to test if there any initial reactions from my GS3, needless to say there wasn't any (no surprise there).
After a little digging around I came up with the conclusion that I need to create a custom "Input Device Configuration Files" for my touchscreen based on the following links
http://source.android.com/tech/input/touch-devices.html
http://source.android.com/tech/input/input-device-configuration-files.html
My initial question before I start plugging away with some codes is how would I name the files, the documents states "Input device configuration files are located by USB vendor, product (and optionally version) id or by input device name." How would I find the product ID or the input device name for the touchscreen? I'm sure this can be done thru terminal or something but I am new to android development so cut me a little slack here
Also if you know of any Input device configuration files dealing with touchscreen please post it.
After digging thru dmesg I found this:
<6>[ 626.370303] hub 1-0:1.0: USB hub found
<6>[ 626.370334] hub 1-0:1.0: 1 port detected
<6>[ 626.684205] usb 1-1: new low speed USB device number 2 using msm_hsusb_host
<6>[ 626.844071] usb 1-1: New USB device found, idVendor=0eef, idProduct=0001
<6>[ 626.844132] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
<6>[ 626.844254] usb 1-1: Product: USB TouchController
<6>[ 626.844284] usb 1-1: Manufacturer: eGalax Inc.
Thus meaning my Input device configuration files should be named
USB_TouchController.idc or 0eef_XXXX_0001_XXXX.idc right? Anyone?
Either I have the name of the file wrong or my code is wrong I can not get any reaction from my Galaxy S3
Code:
device.internal = 0
touch.deviceType = touchScreen
touch.orientationAware = 1
cursor.mode = navigation
cursor.orientationAware = 1
touch.size.calibration = area
touch.size.scale = 28
touch.size.bias = 0
touch.size.isSummed = 0
touch.toolSize.calibration = area
touch.toolSize.areaScale = 22
touch.toolSize.areaBias = 0
touch.toolSize.linearScale = 6
touch.toolSize.linearBias = 0
touch.toolSize.isSummed = 0
touch.pressure.calibration = amplitude
touch.pressure.scale = 0.0125
touch.orientation.calibration = vector
Can anyone help me
hi,
i want to do the same (sort off)
i want to make a padphone only for gs3.
:laugh:
keep up the work:good:
Thanks, still no progress on this can anyone help?
hechen said:
Thanks, still no progress on this can anyone help?
Click to expand...
Click to collapse
Hey mate, did you ever make any headway on this? I'm desperately trying to integrate ANY android device with GPS into my V36 skylines touch screen :'(
Im working on the same thing I got a 7inch touch kit with hdmi and 12v av trigger for reversing camera
The touch screen driver bord is cy7c63723c /e galaxy
Trying to run with android pc mk809iii
Should be a good carputer if I can get it to work
Any help would be good
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.