This is a guide to fix your bricked vizio tablet

[Kato223]

I can still see my external memory ... and if you applied the update in the post you can see what I see ...but I hope that you fixed your device ..

Yep, my device is working, but when I tried it right after recovery it didn't see anything on that one. Interesting enough though, when I just barely tried it again, now it is showing the correct mount. Maybe I missed something when I tried it before.

I guess now I stand corrected!

 

[vinogans]

Yep, my device is working, but when I tried it right after recovery it didn't see anything on that one. Interesting enough though, when I just barely tried it again, now it is showing the correct mount. Maybe I missed something when I tried it before.

I guess now I stand corrected!

well I am happy for you ... I am just curios what bricked your device in the 1st place ... I was playing in the system file and trying to replace 4 files but it didnt work well as I hoped ... so what about you ?

 

[Kato223]

well I am happy for you ... I am just curios what bricked your device in the 1st place ... I was playing in the system file and trying to replace 4 files but it didnt work well as I hoped ... so what about you ?

Well, mainly it was for trying to get applications and data to run on the external sdcard, which I could not make work. The deal breaker was the GPS. I wanted a GPS tablet that I could keep updated by using the NavFree software, but when I downloaded a few maps, it filled up the internal, and I could not find a way to get the maps moved to the external and have the program read it. I called Vizio's tech support, and they were absolutely zero help, and they do not see this as an issue at all. I ended up returning the tablet.

 

[m3doc]

I guess I've done the exact same thing. I rooted my tab so I could "freeze" the friggin update nag. Of course I had to play with it and when my internal storage started to fill up I thought I'd just use my root permission to convert a few system apps and send them to the SD card.....Yeah, well I had it connected to my wireless network at the time and it must have accepted the update without me knowing it and now it just goes to the green triangle of death and hangs. So, what's the conventional wisdom re: what to do now? Vizio said they would send me another tab, but it's going to have the update installed so if that's the case and there's a way to salvage my paperweight with the update then I guess I've answered my own ?.

 

[vinogans]

I guess I've done the exact same thing. I rooted my tab so I could "freeze" the friggin update nag. Of course I had to play with it and when my internal storage started to fill up I thought I'd just use my root permission to convert a few system apps and send them to the SD card.....Yeah, well I had it connected to my wireless network at the time and it must have accepted the update without me knowing it and now it just goes to the green triangle of death and hangs. So, what's the conventional wisdom re: what to do now? Vizio said they would send me another tab, but it's going to have the update installed so if that's the case and there's a way to salvage my paperweight with the update then I guess I've answered my own ?.

you got 2 choices ... install the update (which is provided in this post) in your bricked vtab1008 and dont lose the app and the information and the data you made on the tablet ... but you will lose every tweak you made to the system ...
or get the new vtab1008 with the update with out ur prgs that u spend time installing ...

it`s your choice man

 

[Sonoma]

Thank you for posting this. You mention not to remove anything from the file but would it be possible to add Superuser.apk, su and busybox to the correct locations? Or is this impossible since we would not be able to set the permissions?

Edit: As I look more into the code Symlinks might be an issue.
But maybe we can add them here: "/system/bin/su", "/system/xbin/su"

symlink("toolbox", "/system/bin/cat", "/system/bin/chmod",
"/system/bin/chown", "/system/bin/cmp", "/system/bin/date",
"/system/bin/dd", "/system/bin/df", "/system/bin/dmesg",
"/system/bin/getevent", "/system/bin/getprop", "/system/bin/hd",
"/system/bin/id", "/system/bin/ifconfig", "/system/bin/iftop",
"/system/bin/insmod", "/system/bin/ioctl", "/system/bin/ionice",
"/system/bin/kill", "/system/bin/ln", "/system/bin/log",
"/system/bin/ls", "/system/bin/lsmod", "/system/bin/lsof",
"/system/bin/mkdir", "/system/bin/mount", "/system/bin/mv",
"/system/bin/nandread", "/system/bin/netstat",
"/system/bin/newfs_msdos", "/system/bin/notify", "/system/bin/printenv",
"/system/bin/ps", "/system/bin/reboot", "/system/bin/renice",
"/system/bin/rm", "/system/bin/rmdir", "/system/bin/rmmod",
"/system/bin/route", "/system/bin/schedtop", "/system/bin/sendevent",
"/system/bin/setconsole", "/system/bin/setprop", "/system/bin/sleep",
"/system/bin/smd", "/system/bin/start", "/system/bin/stop",
"/system/bin/sync", "/system/bin/top", "/system/bin/umount",
"/system/bin/uptime", "/system/bin/vmstat", "/system/bin/watchprops",
"/system/bin/wipe");

Then add the permissions (---- -> #?#?)

set_perm_recursive(0, ----, ----, ----, "/system/bin/su");
set_perm_recursive(0, ----, ----, ----, "/system/xbin/busybox");


chmod 04755 /system/xbin/busybox
chmod 06755 /system/bin/su

 

[vinogans]

Thank you for posting this. You mention not to remove anything from the file but would it be possible to add Superuser.apk, su and busybox to the correct locations? Or is this impossible since we would not be able to set the permissions?

it`s impossible to do that @ least now and the version of the update is 1.4 1.9.57 with No root ability ...

 

[Sonoma]

it`s impossible to do that @ least now and the version of the update is 1.4 1.9.57 with No root ability ...

Well, was hoping I could make the changes and load the update.zip. Thanks.

 

[vinogans]

Well, was hoping I could make the changes and load the update.zip. Thanks.

you can try ... i was trying to add or delete a few app from update.zip and I failed ... the winning is in adding the file to the same update.zip with out extract it .. if u succeed in doing that so I dont see any problem in adding su or super user ...

 

[kaos420]

ok so here is my question. i come from the world of xda. i know about rom dumps and so on. i just ordered a refurbished vizio for my wife. of course i am hoping it comes with 1.4 56 on it. if i am correct and it does. if i install cwm recovery. couldnt i dump the rom? so basically we would have a 56 copy that is rootable to use instead of 57 that isnt? just throwing that out there.my plans are when it arrives to check version. if the rootable one. to no connect to net. but root it then cwm recovery it. of course then making a backup. if this is possible and would help us out i am more then willing to do the work woth some direction.

 

[vinogans]

ok so here is my question. i come from the world of xda. i know about rom dumps and so on. i just ordered a refurbished vizio for my wife. of course i am hoping it comes with 1.4 56 on it. if i am correct and it does. if i install cwm recovery. couldnt i dump the rom? so basically we would have a 56 copy that is rootable to use instead of 57 that isnt? just throwing that out there.my plans are when it arrives to check version. if the rootable one. to no connect to net. but root it then cwm recovery it. of course then making a backup. if this is possible and would help us out i am more then willing to do the work woth some direction.

I am lost what is ur question exactly .. well if you was lucky and got 1.9.56 you will be able to root it and install cwm on it ... And basically you can make a rom from what you have but No one have made a custom rom for vtab1008 yet And we cant make a copy and install instead of 57 because it`s got locked boot loader which is being update via update.zip or OTA which is encrypted with vizio key`s ... and for your information ... version 1.4 1.9.56 was root and we got cwm on it ... the problem is in .57 the exploit that rooted .56 was closed so ... I hope All this blah blah answered ur question

 

[kaos420]

Thank you for posting this. You mention not to remove anything from the file but would it be possible to add Superuser.apk, su and busybox to the correct locations? Or is this impossible since we would not be able to set the permissions?

Edit: As I look more into the code Symlinks might be an issue.
But maybe we can add them here: "/system/bin/su", "/system/xbin/su"

symlink("toolbox", "/system/bin/cat", "/system/bin/chmod",
"/system/bin/chown", "/system/bin/cmp", "/system/bin/date",
"/system/bin/dd", "/system/bin/df", "/system/bin/dmesg",
"/system/bin/getevent", "/system/bin/getprop", "/system/bin/hd",
"/system/bin/id", "/system/bin/ifconfig", "/system/bin/iftop",
"/system/bin/insmod", "/system/bin/ioctl", "/system/bin/ionice",
"/system/bin/kill", "/system/bin/ln", "/system/bin/log",
"/system/bin/ls", "/system/bin/lsmod", "/system/bin/lsof",
"/system/bin/mkdir", "/system/bin/mount", "/system/bin/mv",
"/system/bin/nandread", "/system/bin/netstat",
"/system/bin/newfs_msdos", "/system/bin/notify", "/system/bin/printenv",
"/system/bin/ps", "/system/bin/reboot", "/system/bin/renice",
"/system/bin/rm", "/system/bin/rmdir", "/system/bin/rmmod",
"/system/bin/route", "/system/bin/schedtop", "/system/bin/sendevent",
"/system/bin/setconsole", "/system/bin/setprop", "/system/bin/sleep",
"/system/bin/smd", "/system/bin/start", "/system/bin/stop",
"/system/bin/sync", "/system/bin/top", "/system/bin/umount",
"/system/bin/uptime", "/system/bin/vmstat", "/system/bin/watchprops",
"/system/bin/wipe");

Then add the permissions (---- -> #?#?)

set_perm_recursive(0, ----, ----, ----, "/system/bin/su");
set_perm_recursive(0, ----, ----, ----, "/system/xbin/busybox");


chmod 04755 /system/xbin/busybox
chmod 06755 /system/bin/su

have you tried adding them to ?show_progress(1.000000, 32);
format("ext4", "EMMC", "/dev/block/mmcblk0p2");
mount("ext4", "EMMC", "/dev/block/mmcblk0p2", "/system");
package_extract_dir("system", "/system");
symlink("toolbox", "/system/bin/cat", "/system/bin/chmod",
"/system/bin/chown", "/system/bin/cmp", "/system/bin/date",
"/system/bin/dd", "/system/bin/df", "/system/bin/dmesg",
"/system/bin/getevent", "/system/bin/getprop", "/system/bin/hd",
"/system/bin/id", "/system/bin/ifconfig", "/system/bin/iftop",
"/system/bin/insmod", "/system/bin/ioctl", "/system/bin/ionice",
"/system/bin/kill", "/system/bin/ln", "/system/bin/log",
"/system/bin/ls", "/system/bin/lsmod", "/system/bin/lsof",
"/system/bin/mkdir", "/system/bin/mount", "/system/bin/mv",
"/system/bin/nandread", "/system/bin/netstat",
"/system/bin/newfs_msdos", "/system/bin/notify", "/system/bin/printenv",
"/system/bin/ps", "/system/bin/reboot", "/system/bin/renice",
"/system/bin/rm", "/system/bin/rmdir", "/system/bin/rmmod",
"/system/bin/route", "/system/bin/schedtop", "/system/bin/sendevent",
"/system/bin/setconsole", "/system/bin/setprop", "/system/bin/sleep",
"/system/bin/smd", "/system/bin/start", "/system/bin/stop",
"/system/bin/sync", "/system/bin/top", "/system/bin/umount",
"/system/bin/uptime", "/system/bin/vmstat", "/system/bin/watchprops",
"/system/bin/wipe");
set_perm_recursive(0, 0, 0755, 0644, "/system");
set_perm_recursive(0, 2000, 0755, 0755, "/system/bin");
set_perm(0, 3003, 02750, "/system/bin/netcfg");
set_perm(0, 3004, 02755, "/system/bin/ping");
set_perm(0, 2000, 06750, "/system/bin/run-as");
set_perm_recursive(1002, 1002, 0755, 0440, "/system/etc/bluetooth");
set_perm(0, 0, 0755, "/system/etc/bluetooth");
set_perm(1000, 1000, 0640, "/system/etc/bluetooth/auto_pairing.conf");
set_perm(3002, 3002, 0444, "/system/etc/bluetooth/blacklist.conf");
set_perm(1002, 1002, 0440, "/system/etc/dbus.conf");
set_perm(1014, 2000, 0550, "/system/etc/dhcpcd/dhcpcd-run-hooks");
set_perm(0, 2000, 0550, "/system/etc/init.goldfish.sh");
set_perm_recursive(0, 0, 0755, 0555, "/system/etc/ppp");
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
unmount("/system");
ui_print("Writing SM0 partition files...");
package_extract_file("sm0", "/cache/sm0");
write_raw_image_emmc("/dev/block/mmcblk0p12", "/cache/sm0", 0);
ui_print("Writing kernel image...");
package_extract_file("zImage", "/cache/zImage");
write_raw_image_emmc("/dev/block/mmcblk0p8", "/cache/zImage", 0);
ui_print("Writing ramdisk image...");
package_extract_file("ramdisk.img", "/cache/ramdisk.img");
write_raw_image_emmc("/dev/block/mmcblk0p1", "/cache/ramdisk.img", 0);
ui_print("Copying u-boot image...");
package_extract_file("u-boot.bin", "/cache/u-boot.bin");
write_raw_image_emmc("/dev/block/mmcblk0p6", "/cache/u-boot.bin", 1536);
ui_print("Writing bootloader message...");
mrvl_update_firmware("/dev/block/mmcblk0p6", "update-firmware");
ui_print("Rebooting...");
reboot();