Jump to content


Photo

FVIEW 7" PRO tablet Rooting and FW discussion


  • Please log in to reply
91 replies to this topic

#1 Aiah

Aiah

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 106 posts

Posted 10 August 2011 - 03:49 AM

In the Netherlands the fview 7" pro is sold by the toy shop "intertoys" (dutch link: http://www.intertoys...ack-579738.html)
It is based on a RK2918 chip running @ 1008Mhz
The offical provided firmware upgrade will give it android 2.3.1

** Warning flashing modified or the incorrect firmware will invalidate you waranty and can brick your device **

I take no responsibility if anything goes wrong with your tablet, i am simply providing my experience to help others, but will not be held responsible if anything happens to your tablet.
Also Slatedroid will take no responsibility for anything bad happening with your tablet.



These are te steps i followd to get root on my fview pro 7"

step1)
- download the official firmware update tools & firmware (http://www.tabletsup...read.php?tid=34) (download link and upgrade instructions)
- i used version 20110704

step2)
- install/flash the firmware as discribed on the above link and check if your tablet is runnng the nieuw version correctly

step3)
- download and unpack the Rk29xx ImageTools V2.1 created by wendal
http://www.slatedroi...imagetools-v21/ (link to telecast forum, with some more info and download link)

step4)
- copy the official firmware file "FVTablet PRO update 110704.img" and save it as wendal.img in the directory where you unpacked the wendal rk2918 tools

step5)
- run the wendal tools (runme.bat)
* select 1 (and RETURN when asked)
this wil unpack the the system.img from the firmware image, and add the root access to the filesystem

info: it will
- unpack system.img (witch is a cramfs filesystem containing the device /system content)
- extract the files from the cramfs filesystem
- add su and superuser.apk to the /system/bin and /system/app directory

NOTE: you will get 2 errors over JM_CE.DCT and MGCT_EE.DCT i ignored them.

info: These .DCT files are larger than 16MB and cramfs filesystem does not allow files larger than 16Mb
I have no qlue how they managed to get these files into the cramfs filesystem.
As far is i could find out these DCT files contain proprity voip audio codecs, and as the tablet
does not conain any phone or voip software i'm assuming there not used.
I also found out that on an unrooted device the *.DCT files are inaccesable anyway

* select 2 (and RETURN when asked)wendal_new.img
this will recreate the system.img / cramfs with the added root programs, and rebuild the firmware image file

* select 3 (to exit)

NOTE: If you get any other error than the .DCT once discriped your probably out of luck.

You should now have a modified firmware image called wendal_new.img

step6)
- install/flash the modified firmware via the same method as descriped in step2
but instead of using "FVTablet PRO update 110704.img" use the modified image file wendal_new.img

step7)
- enjoy your root access (and be carfull not to brick your device by misuseing root....)


All credit goes to wendal for creating the Rk29xx ImageTools.

#2 Aiah

Aiah

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 106 posts

Posted 11 August 2011 - 05:40 AM

I found the following apk files in the /system/app folder (these files are also in the original rom)

- teclast_map.apk 2729469bytes MD5:03adaa8399b2181be105cd21d774e3d0 (looks like some navigation app)
- teclast_rwglq.apk 85286bytes MD5:34b08b74243ffb87f3ecb1b86c4dd8c8 (looks to be the taskmanager app)

Could it be that this fview tablet is a rebranded or cloned teclast tab ?

#3 JohnyRingo

JohnyRingo

    Member

  • Jr. Member
  • PipPip
  • 12 posts

Posted 12 August 2011 - 08:50 AM

I found the following apk files in the /system/app folder (these files are also in the original rom)

- teclast_map.apk 2729469bytes MD5:03adaa8399b2181be105cd21d774e3d0 (looks like some navigation app)
- teclast_rwglq.apk 85286bytes MD5:34b08b74243ffb87f3ecb1b86c4dd8c8 (looks to be the taskmanager app)

Could it be that this fview tablet is a rebranded or cloned teclast tab ?


The screen resolution is different from the Teclast T760 which has the same Rockchip 2918 but has a 1024x600 screen.

#4 Aiah

Aiah

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 106 posts

Posted 12 August 2011 - 09:02 AM

Not happy at all ... :(

In my quest to buils some kernel modules i keep failing...

According to /proc/sys/osversion / osrelease it 2.6.32.27 kernel gcc 4.4.0 #284 <-- i dont realy know what the #284 indicates..
According to vermagic string in wlan.ko ik is 2.6.32.27 PREEMPT Armv7

AS i seems that rockchip isn't willing to supply kernel sources / headers
I started with the stock 2.6.32.27 version...
After some major experimenting and tweeking make menuconfig....

* An empty "hello world" type module compiles and loads fine and unloads file
[looks like 2.6.32.27 is a good bet]

* pl2303 module compiles, loads, registers as ttyUSB0 fine
but first access to /dev/ttyUSB0 freezes the system
[skipped for now]

* Kernels supplies HCI BTCORE
so lets try BTUSB (to get my dongle working)

- btusb compiles
- btusb loads with a oepss / stacktrage somewhere in btusb_probe()

adding some debuggin and it look like:

- btusb_probe sets hci->open / hci->close / hci->destruct
- the call to hci_register_dev(hci) returns -22
according to hci_core source
-22 is returned if any othe the hci->open, hci->close, hci->destruct not set.
bt_usb just assigned them ????

by disassempling the hci_register_device kernel i now suspect that
the hci_dev structure are different..
why i think so:
in official 2.6.32.27 the offset between hci->pkt_type and hci_open is 0x3dc bytes
in the fview kernel the offset between hci->pkt_type and hci_open is 0x340 bytes
this would also explane why bt_usb_probe assings the open/close/etc pointers but hci_register_device thinks otherwise..

seems like im out of luck..


Question to anyone with some android kernel experience:

is it common practis to mix kernel versions ? ... like using 2.6.32.27 one part but using 2.6.26 for other ??
or could i be that then use an other version but are fakeing the release number ?

Edited by Aiah, 24 August 2011 - 02:19 PM.


#5 Aiah

Aiah

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 106 posts

Posted 15 August 2011 - 08:38 AM

After dumping all code and starting with a clean 2.6.32.27 and reapplying config settings

- hci_device_register is accepting the call from btsusb_probe
- seems like the used hci_device structure are identical with stock 2.6.32.27 afterall
- after activating btusb by bttest enable
the tablet is still crashing/freezig with any debug info / stacktrace or kernel oeps

no success yet, altough im one step further...

Edited by Aiah, 24 August 2011 - 11:22 AM.


#6 Aiah

Aiah

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 106 posts

Posted 24 August 2011 - 02:16 PM

My first try at an customized rom for the fview 7" pro

(original firmware source 110704.img same as earlier post)
Changes:
- rooted
- added support for trust 16593 wireless keyboard+mouse (with usbdongle) (other sunplus based wirless kb might also work)
- removed some system apps (facebook/twitter/youtube/apkinstaller/Ebookreader/new&weather)/calculator/EStaskmanager)
you can always... install market version
- added some system apps (systempanel-lite,RealCalc,HackersKeyboard)
- added some symlinks to busybox (cp,clear,more,grep,find,tar)
- changed default language to UK/US

p.s. because of the added hackerskeyboard input it is now also posible to disable that pesky wisky keyboard
fully disable of wiskey keyboard only seems to work when a usb keyboard is attached :(

As always ymmv and I take no responsibility if anything goes wrong with your tablet
link https://rapidshare.c...4-aiah02.img.gz

Edited by Aiah, 30 August 2011 - 07:26 AM.

  • Pavel_NL likes this

#7 Pasqual

Pasqual

    Newbie

  • Jr. Member
  • Pip
  • 3 posts

Posted 29 August 2011 - 09:53 AM

My first try at an customized rom for the fview 7" pro

(original firmware source 110704.img same as earlier post)
Changes:
- rooted
- added support for trust 16593 wireless keyboard+mouse (with usbdongle) (other sunplus based wirless kb might also work)
- removed some system apps (facebook/twitter/youtube/apkinstaller/Ebookreader/new&weather)/calculator/EStaskmanager)
you can always... install market version
- added some system apps (systempanel-lite,RealCalc,HackersKeyboard)
- added some symlinks to busybox (cp,clear,more,grep,find,tar)
- changed default language to UK/US

p.s. because of the added hackerskeyboard input it is now also posible to disable that pesky wisky keyboard

As always ymmv and I take no responsibility if anything goes wrong with your tablet
link https://rapidshare.c...4-aiah02.img.gz

When the guarantee of my tablet has gone (bought him 29-07-2011 in Bladel-The Netherlands) then I will try this certainly. Thank you, however for your work. Sorry for My English, I speak unfortunately only Dutch.
Pasqual

#8 Pasqual

Pasqual

    Newbie

  • Jr. Member
  • Pip
  • 3 posts

Posted 31 August 2011 - 10:24 PM

It works fine for me. Thanks.

#9 TYZ

TYZ

    Newbie

  • Jr. Member
  • Pip
  • 4 posts

Posted 16 September 2011 - 07:23 AM

hi all,

i just bought a fview 7" pro.
downloaded the new firmware and rooted it with wendals tool.
thanks for that great tool wendal.
made rooting the device as easy as it can be.

i am trying to run backtrack and ubuntu both arm version an this tablet.
no succes yet think there is something wrong with the loop and or block device.
is someone else looking in to this?

some help would be nice

gr, tyz

#10 Aiah

Aiah

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 106 posts

Posted 16 September 2011 - 09:26 AM

hi all,
... snip ...
i am trying to run backtrack and ubuntu both arm version an this tablet.
no succes yet think there is something wrong with the loop and or block device.
is someone else looking in to this?

some help would be nice


Better create a new topic for the backtrack/ubuntu experiments to keep this thread on the original subject of modding the original fw.

#11 Aiah

Aiah

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 106 posts

Posted 26 September 2011 - 08:16 AM

... double post... i posted the original in the wrong place....

Attached File  init_system_rw.sh.zip   1.18KB   70 downloads

This scripts makes /system writable
- requires root
- no other firmware mods required (see notes)
- only tested it on fview 7"
- work in progress...

notes:
Changes to /system are semipermanent on, reboot the system will use the standard cramfs /system untill you run the script again

And with a small change to init.rc (does require firmware mod) you can have the script start automaticly (as early as possible)
init.rc mod (place is right after the service ueventd /sbin/ueventd critical entry)

service init_system_rw /init_system_rw.sh
user root
oneshot

Edited by Aiah, 28 September 2011 - 11:50 AM.

  • Pavel_NL likes this

#12 jkpjj

jkpjj

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 130 posts

Posted 28 September 2011 - 06:12 AM

Thanks - though for whatever reason, your attachments appear to be gzipped multiple times, making them needlessly hard to extract. The kernel modules you posted were gzipped twice, but this one requires running gunzip three times on it to get to the script.

... double post... i posted the original in the wrong place....





#13 Aiah

Aiah

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 106 posts

Posted 28 September 2011 - 11:54 AM

Thanks - though for whatever reason, your attachments appear to be gzipped multiple times, making them needlessly hard to extract. The kernel modules you posted were gzipped twice, but this one requires running gunzip three times on it to get to the script.


Verry strage, i did a test

echo "test" > textfile.sh
gzip testfile.sh
upload & post testfile.sh.gz
download testfile.sh.gz

And it is gzipped 3times...
Must have something to do with gz support in brouwers or maby in the forum backend.

I reupped the init_script.sh post als a zip file, that way there is no problem.

#14 Aiah

Aiah

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 106 posts

Posted 18 October 2011 - 12:07 PM

My second customized rom for the fview 7" pro

(original firmware source 110704.img same as earlier post)

Update to 110704-aiah02.img.gz (see post #6)
Changes
- minor modifications
- /system directory "semi" writetable (using the method discriped in post #11)

With the writeble /system partition it wil be much easyer to make updates in the future, so small updates wont require a full firmware update.

link: https://rapidshare.c...-aiah03.img.zip
  • Pavel_NL likes this

#15 Darkwing_de

Darkwing_de

    Newbie

  • Jr. Member
  • Pip
  • 8 posts

Posted 27 October 2011 - 05:16 AM

I try the script.
copy to sdcard
open terminal
$ su
# ./init_system_rw.sh
permission denied

# sh init_system_rw.sh
[: not found
[: not found
[: not found
[: not found
[: not found
[: not found
[: not found

Edited by Darkwing_de, 27 October 2011 - 05:17 AM.


#16 Aiah

Aiah

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 106 posts

Posted 31 October 2011 - 08:43 AM

I try the script.
copy to sdcard
open terminal
$ su
# ./init_system_rw.sh
permission denied

# sh init_system_rw.sh
[: not found
[: not found
[: not found
[: not found
[: not found
[: not found
[: not found


first:
init_system_rw.sh can only be run from a filesystem that was mounted with the excecutable flag enabled (sdcard is default noexec)
you also need the busybox version of sh to make it work

second:
I only tested this init_system_rw.sh with the fview 7" rom version.
It might work on other roms, but i cant give any guaranties.


If you still want to, you could try the following:
(option 1)
# busybox sh init_system_rw.sh

(option 2) remount sdcard with exce flag
mount -o remount,rw /pathto/sdcard
cd /patchto/sdcard
. ./init_system_rw.sh

#17 Darkwing_de

Darkwing_de

    Newbie

  • Jr. Member
  • Pip
  • 8 posts

Posted 31 October 2011 - 09:26 AM

THX

i found a way to unpack and repack the Boot.img and copy the busybox + init_system_rw.sh to the root of the boot.img
change filelist and init.rc and .... working.

Next Step is find a way to change the Kernel.img or better.
I faound a tread of a other RK2918 http://www.slatedroi...dk-20-firmware/ based System with a custom rom they have no Kernel.img... only the standard boot.img with included Kernel and the complete system ist on a ext3 partition.

#18 Pavel_NL

Pavel_NL

    Member

  • Jr. Member
  • PipPip
  • 14 posts

Posted 12 November 2011 - 04:43 AM

My second customized rom for the fview 7" pro


Many thanks for the investigations/work you done.

Could you post the current status, pls?

Most interesting for me is what NOT working for you so far...

Do not have much time to help you, sorry.

#19 Aiah

Aiah

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 106 posts

Posted 12 November 2011 - 11:44 AM

Status kernel modding fview 7" pro tables

Working
- rooted rom
- trust wirless keyboard and mouse
- semi writable system directory

Working, but still in experimental status
- BTUSB based bluetooth dongles
* I got a simple sitecom usb bluetooth dongle working
- GPS using an external bluetooth gps device
- the external bt-gps device must support NMEA and rfcomm serial protocol
* i have a adapt bt=gps devices working
- GPS usering an external USB-gpsmouse
- the external gps mouse must use a pl2303 usb-serial converter and must start in NMEA mode by default
* I have a DG100 sattracker / gps mouse working

Wat is not working
- BTUSB power draining (even when tap is switched off)
- Device startup with BTdognle attached

What not working
- mounting external sdcard in other spot than /mnt/storage/sdcard
- fully disableing wiskey soft keyboard
  • Pavel_NL likes this

#20 Aiah

Aiah

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 106 posts

Posted 12 November 2011 - 02:14 PM

Any fview owner interested in the (experimental) BT or gps parts