Jump to content


Photo

M70007t Hybrid ROM


  • Please log in to reply
49 replies to this topic

#1 WesB

WesB

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 43 posts
  • LocationGeorgia

Posted 04 May 2011 - 09:49 AM

With Roger's permission I am posting this hybrid ROM I created with the original ROM and Roger's 1.1.5 Vestinious Build. I tried Rogers M70007t build and I was having problems with the touchscreen working correctly, so I created this build. Mainly I compared the ROMS and using mostly Roger's build I was able to create a ROM that works with my tablet. THIS BUILD IS ONLY IF YOU HAVE PROBLEMS WITH ROGER'S BUILD. Please understand Roger did most of the work - I just tweaked it for my tablet. This ROM removes most of the bloatware installs google app market and I am pretty sure that it is rooted (still haven't verified this). You can look at the Vestinious build info to find out the particulars as I believe most everything is there (may not be exactly) LOL. Please let me know how this works out for you and remember this is my first!



My tables says it is a M70007t, WM8650 with a green LED and vibrates when booted.

YOU TAKE RESPONSIBILITY FOR USING THIS ROM.

Without further ado:
Hybrid ROM http://www.filesonic...WesB_Hybrid.rar
Original ROM http://www.filesonic...007T_V1.2.1.rar

THANKS ROGER!

Edited by WesB, 04 May 2011 - 09:57 AM.

  • Coresect likes this
Always have your stuff when you need it with @Dropbox. 2GB account is free! http://db.tt/uoZhg0e

#2 WesB

WesB

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 43 posts
  • LocationGeorgia

Posted 06 May 2011 - 07:32 PM

Wow. 22 downloads and not the first reply if it works or not. It would be helpful to know what this is doing for you. At least for future testing and builds.
Always have your stuff when you need it with @Dropbox. 2GB account is free! http://db.tt/uoZhg0e

#3 Christopher Armstrong

Christopher Armstrong

    Newbie

  • Jr. Member
  • Pip
  • 3 posts

Posted 06 May 2011 - 08:28 PM

Yep, this works well for me. I am writing this on the tablet. Thanks for assembling this.

I'm looking forward to the next version as it is a bit slow and drains the battery quickly.

#4 classicalguy

classicalguy

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 390 posts

Posted 06 May 2011 - 08:34 PM

My tablet is still somewhere between china and new york (probably closer to china). Can't wait for it to arrive so that I can join in the fun. Until then, I have to enjoy the rom adventures vicariously.

#5 Roger Calver

Roger Calver

    Firmware Dev

  • Global Moderators
  • 2,737 posts
  • LocationUK

Posted 08 May 2011 - 07:34 AM

Good to hear some feedback as its vital for us to know if things are working and what we need to fix in next builds.

Cheers to WesB for modding the build for the M7007T !
Slatedroid Singularity

#6 gsprings43

gsprings43

    Member

  • Jr. Member
  • PipPip
  • 21 posts

Posted 08 May 2011 - 08:38 AM

ok,i have a green led 8650 tablet,after i pull out the memory card for it to reboot with this rom after going through the update process it starts up and goes into the loading screen,but will go no further,it does the same thing with the uberoid rom to which is a v1.2.2 rom, any suggestions,these are the only 2 roms that i could actually get to go through the update process,but like i said,they get stuck on the loading screen,i would wait over ten minutes for it to load??????????

#7 classicalguy

classicalguy

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 390 posts

Posted 08 May 2011 - 02:19 PM

We need to do this scientifically to find a solution. There appear to be different green LED tablets, because WesB was unable to install 1Onyx's firmware. One difference noted in some of the earlier boards is whether the tablet vibrates on bootup. I believe WesB's does, does yours?

Here are my suggestions:

1. Try WesB's factory firmware. If it doesn't install, then you know WesB's Vestinious version is not going to work.

2. Try 1Onyx's firmware. If it works, then we should be able to fashion a new Vestinious version using his video drivers.

3. If neither WesB nor 1Onyx works, then try the old Vestinious version for the M7007T, the Viapad V7 and the Merimobles Mid V7.

If none of the above work, then I think you're going to have to get your original factory firmware from your vendor, and you can then play with the video drivers with Vestinious.

Lastly, it's possible you don't have a true 8650 based tablet (even though it looks the same). You may need to open it and check the chip.

#8 Christopher Armstrong

Christopher Armstrong

    Newbie

  • Jr. Member
  • Pip
  • 3 posts

Posted 08 May 2011 - 08:09 PM

We need to do this scientifically to find a solution. There appear to be different green LED tablets, because WesB was unable to install 1Onyx's firmware. One difference noted in some of the earlier boards is whether the tablet vibrates on bootup. I believe WesB's does, does yours?


For the record, the hybrid ROM was successful on mine. I haven't tried Roger's or 10nyx's firmware.

My tablet is most likely a M70007T (the manual says so). It is a green LED and it DOES vibrate upon startup.

#9 WizzKid

WizzKid

    Member

  • Jr. Member
  • PipPip
  • 12 posts

Posted 09 May 2011 - 06:51 PM

look forward to update

#10 desihero

desihero

    Newbie

  • Jr. Member
  • Pip
  • 2 posts

Posted 09 May 2011 - 08:17 PM

can't wait to test the build! will report later...

#11 WizzKid

WizzKid

    Member

  • Jr. Member
  • PipPip
  • 12 posts

Posted 10 May 2011 - 05:39 AM

WesB would be great if you got the 1.3.2 update out, and explained how its done so more of us can help out :)

#12 Roger Calver

Roger Calver

    Firmware Dev

  • Global Moderators
  • 2,737 posts
  • LocationUK

Posted 10 May 2011 - 05:46 AM

Ive just sent him a message and the link for 1.3.2
Slatedroid Singularity

#13 WesB

WesB

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 43 posts
  • LocationGeorgia

Posted 10 May 2011 - 06:06 AM

Sorry for not being here the last couple of days. I have other things more pressing to work on (my tractor - now fixed!). Anyway I will try to get this downloaded and work on it this coming weekend - I am busy at work so I can't really work on it there. It is helpful to know what is taking place with the builds especially since there are different versions of the tablet floating around. I have noticed on my build that the battery drains pretty fast, and I am looking to fix that. I'm up to 43 downloads on my hybrid ROM! WOW I am impressed that it took off so well for my first try! I hope to have a new and improved version soon!
Always have your stuff when you need it with @Dropbox. 2GB account is free! http://db.tt/uoZhg0e

#14 classicalguy

classicalguy

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 390 posts

Posted 10 May 2011 - 11:19 AM

It sounds like we have a green light with vibrate that works with WesB's firmware, and a green light without vibrate that works with 1Onyx's version. I think we need to figure out how to make WesB's and 1Onyx's modifications to Roger's latest blue light version.

#15 Roger Calver

Roger Calver

    Firmware Dev

  • Global Moderators
  • 2,737 posts
  • LocationUK

Posted 10 May 2011 - 11:23 AM

If there are the 1.3.0 builds available for green LED tablets it should be easy to do.
All of the changes made to Vestinious are in the Android base and so can be ported straight out to the green base factory OS.
Slatedroid Singularity

#16 classicalguy

classicalguy

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 390 posts

Posted 10 May 2011 - 11:59 AM

Roger: It may be easier to change the video drivers/settings in your blue light version than to find a version of the official firmware for the green leds. That's what both WesB and 1Onyx did in the earlier versions, I believe.

#17 scumball

scumball

    Member

  • Jr. Member
  • PipPip
  • 19 posts

Posted 11 May 2011 - 03:40 AM

On another site they state that changing the Blue LED env_uboot to the below makes the ROM work on the Green with Vibrate - obviously YMMV

setenv memtotal 212M
setenv mmcid 0
setenv lpj AUTO
setenv ipaddr 192.168.0.2
setenv serverip 192.168.0.1
setenv gatewayip 192.168.0.1
setenv netmask 255.255.255.0
setenv kernelargs \
setenv bootargs mem=${memtotal} root=${filesystem-NAND_mtd} noinitrd rootfstype=yaffs2 \
rw console=ttyS0,115200n8 lpj=${lpj} ${android_bootargs} ${platform_bootargs} \
quiet

setenv bootcmd \
nandrw r ${kernel-NAND_ofs} 0x1000000 ${kernel-NAND_len}\; \
if iminfo 0x1000000\; then \
run kernelargs\; \
bootm 0x1000000\; \
fi\; \
echo No kernel found

setenv logocmd \
nandrw r ${wmt.nfc.mtd.u-boot-logo} ${wmt.display.logoaddr} 10000\; \
nandrw r ${wmt.nfc.mtd.u-boot-logo2} ${wmt.display.logoaddr2} 40000\; \
nandrw r ${wmt.nfc.mtd.kernel-logo} ${wmt.kernel.animation.addr} 80000\; \
display init force\; \
decompanima -f ${wmt.display.logoaddr2} 0x3000000; \
decompanima -f ${wmt.display.logoaddr} 0x3000000

setenv wmt.display.logoaddr2 550000
setenv wmt.audio.i2s vt1603:f1:f2:ff:ff:100
setenv wmt.io.pwbn 100:0:2000
setenv wmt.display.logoaddr 500000
setenv wmt.kernel.animation.addr f600000
setenv wmt.eth.param 1
setenv wmt.gpi.bat [0:0:00020000:d8110040:d8110080:d8110000:d8110480:d81104C0][1:0:00000020:d8110040:d8110080:d8110000:d8110480:d81104C0][2:1:00010000:d8110040:d8110080:d8110000: d8110480:d81104C0]
setenv wmt.gpo.cmos 1:0:7:D8110040:D8110080:D81100C0
setenv wmt.gpo.wifi 6:1:6:d8110040:d8110080:d81100C0
setenv wmt.gpt.gsensor 3:8:d8110040:d8110080:d8110000:d8110480:d81104c0:83000000:d8110300:8:d8110320:6
setenv wmt.io.bat 3:2:1000:db1:b6d:db1:d77:d3d:d03:cc9:c8f:c55:c1b:be1:ba7:b6d
setenv wmt.io.gsensor 1:3:4:0:1:1:-1:2:-1
setenv wmt.sys.keypad commonboard:1:rc_1:4:c0_73:c1_72:r0_9e:r1_8b
setenv wmt.pwbn.param 100:0:500
setenv wmt.ui.storage 7
setenv touchic true
setenv touchirq gpio0
setenv touchcodec uor615x
setenv wmt.io.touch 1:uor615x:0:800:480
setenv wmt.bus.i2c i2c0:1:1:i2c1:1:1
setenv bootdelay 1
setenv wmt_ui_hibernation 1
setenv wmt_sys_powerhold 0
setenv wmt.gpo.vibrator 1:1:28110040811008081100C0:1
setenv wmt.camera.param 0:0
setenv android_bootargs init=/init
setenv platform_bootargs wmtvo=2:1:24:800:480:60
setenv wmt.display.param 2:0:16:0:0:0
setenv wmt.display.tmr 40000:0:10:46:800:20:10:23:480:10
setenv wmt.display.pwm 0:25:50:99
setenv panelres.x 800
setenv panelres.y 480
setenv wmt.model.no 7inch_std_vt1603 
setenv wmt.io.ts.2dcal -3 -17438 67608023 11859 10 -5362731 80387



Edited by scumball, 11 May 2011 - 03:41 AM.


#18 WesB

WesB

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 43 posts
  • LocationGeorgia

Posted 11 May 2011 - 06:16 AM

There are changes to the env_uboot file although I am not so sure that it is just a Green LED/vibrate issue. My screen has a multi-touch screen and I am thinking that there in lies part of the complication. I made a new hybrid build last night and it works pretty well - I am pretty sure I saw a small enhancement of speed and the touch screen seems to respond better (no change in battery life tho). The issues I am having with it as it stands are when you go to a website that has flash it pops up a box that says evaluation version (flash) and if you go to the about screen it does a force close. I will try to work on these issues and get a new hybrid build out there soon.
Always have your stuff when you need it with @Dropbox. 2GB account is free! http://db.tt/uoZhg0e

#19 bigd5783

bigd5783

    Newbie

  • Jr. Member
  • Pip
  • 9 posts

Posted 11 May 2011 - 09:02 PM

I can verify that this works. Leave your tablet to boot for at least 5 min though. I used the 1.3.3 base and it works but the touchscreen is very difficult to press. You have to press very hard to get it to register. Is there a way to correct this.

On another site they state that changing the Blue LED env_uboot to the below makes the ROM work on the Green with Vibrate - obviously YMMV

setenv memtotal 212M
setenv mmcid 0
setenv lpj AUTO
setenv ipaddr 192.168.0.2
setenv serverip 192.168.0.1
setenv gatewayip 192.168.0.1
setenv netmask 255.255.255.0
setenv kernelargs \
setenv bootargs mem=${memtotal} root=${filesystem-NAND_mtd} noinitrd rootfstype=yaffs2 \
rw console=ttyS0,115200n8 lpj=${lpj} ${android_bootargs} ${platform_bootargs} \
quiet

setenv bootcmd \
nandrw r ${kernel-NAND_ofs} 0x1000000 ${kernel-NAND_len}\; \
if iminfo 0x1000000\; then \
run kernelargs\; \
bootm 0x1000000\; \
fi\; \
echo No kernel found

setenv logocmd \
nandrw r ${wmt.nfc.mtd.u-boot-logo} ${wmt.display.logoaddr} 10000\; \
nandrw r ${wmt.nfc.mtd.u-boot-logo2} ${wmt.display.logoaddr2} 40000\; \
nandrw r ${wmt.nfc.mtd.kernel-logo} ${wmt.kernel.animation.addr} 80000\; \
display init force\; \
decompanima -f ${wmt.display.logoaddr2} 0x3000000; \
decompanima -f ${wmt.display.logoaddr} 0x3000000

setenv wmt.display.logoaddr2 550000
setenv wmt.audio.i2s vt1603:f1:f2:ff:ff:100
setenv wmt.io.pwbn 100:0:2000
setenv wmt.display.logoaddr 500000
setenv wmt.kernel.animation.addr f600000
setenv wmt.eth.param 1
setenv wmt.gpi.bat [0:0:00020000:d8110040:d8110080:d8110000:d8110480:d81104C0][1:0:00000020:d8110040:d8110080:d8110000:d8110480:d81104C0][2:1:00010000:d8110040:d8110080:d8110000: d8110480:d81104C0]
setenv wmt.gpo.cmos 1:0:7:D8110040:D8110080:D81100C0
setenv wmt.gpo.wifi 6:1:6:d8110040:d8110080:d81100C0
setenv wmt.gpt.gsensor 3:8:d8110040:d8110080:d8110000:d8110480:d81104c0:83000000:d8110300:8:d8110320:6
setenv wmt.io.bat 3:2:1000:db1:b6d:db1:d77:d3d:d03:cc9:c8f:c55:c1b:be1:ba7:b6d
setenv wmt.io.gsensor 1:3:4:0:1:1:-1:2:-1
setenv wmt.sys.keypad commonboard:1:rc_1:4:c0_73:c1_72:r0_9e:r1_8b
setenv wmt.pwbn.param 100:0:500
setenv wmt.ui.storage 7
setenv touchic true
setenv touchirq gpio0
setenv touchcodec uor615x
setenv wmt.io.touch 1:uor615x:0:800:480
setenv wmt.bus.i2c i2c0:1:1:i2c1:1:1
setenv bootdelay 1
setenv wmt_ui_hibernation 1
setenv wmt_sys_powerhold 0
setenv wmt.gpo.vibrator 1:1:28110040811008081100C0:1
setenv wmt.camera.param 0:0
setenv android_bootargs init=/init
setenv platform_bootargs wmtvo=2:1:24:800:480:60
setenv wmt.display.param 2:0:16:0:0:0
setenv wmt.display.tmr 40000:0:10:46:800:20:10:23:480:10
setenv wmt.display.pwm 0:25:50:99
setenv panelres.x 800
setenv panelres.y 480
setenv wmt.model.no 7inch_std_vt1603 
setenv wmt.io.ts.2dcal -3 -17438 67608023 11859 10 -5362731 80387



Edited by bigd5783, 11 May 2011 - 09:44 PM.


#20 WesB

WesB

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 43 posts
  • LocationGeorgia

Posted 12 May 2011 - 06:25 AM

I can verify that this works. Leave your tablet to boot for at least 5 min though. I used the 1.3.3 base and it works but the touchscreen is very difficult to press. You have to press very hard to get it to register. Is there a way to correct this.


This is the exact issue I was having hence the hybrid. I somehow overcome the screen issue with my edits. I wish I could pinpoint the exact change but I made so many that I don't exactly know which one "fixed" the problem.
Always have your stuff when you need it with @Dropbox. 2GB account is free! http://db.tt/uoZhg0e