so who wants the .56 update. hmmmmm want root back see here?

[kaos420]

ok not tested yet as i am already rooted . but i pulled every single file from my device including boot images and kernels everything that is in the .57 build.every single file but from a .56 system. replaced all files in the signed .57 update with that of .56 so basically created a .56 update zip. any takers wanna try see if it will let you roll back from .57 to .56. of the image should already be rooted as well.

my self and androidtablets.net take no responsibility if you brick your device. if it grows wings. or if it racks up internation charges calling 1900 numbers.

directions
ok so if someone will test attemp 2. let me know. rppr what about using adb.

adb push zImage /sdcard/zImage
adb shell dd if=/dev/block/mmcblk0p8 of=/dev/block/zImage

adb push /dev/block/mmcblk0p1 of=/dev/block/ramdisk.img

adb push /dev/block/mmcblk0p6 of=/dev/block/u.boot.bin

adb push /dev/block/mmcblk0p12 of=/dev/block/sm0

http://www.mediafire.com/?wybpyca329qdldp

is the 4 files someone try with adb.

 

[mui]

Where would one place this file.

 

[kaos420]

Where would one place this file.

added to op. please post results here. should be rooted as it was a backup of mine after first boot nothing on it just out the box and rooted right away then dumped. if not as long as its reverts you . you can root. remember to freeze updater from vizio after.

 

[mui]

It got to " Failed to verify update..." something and rebooted, no change

 

[Tcsviz77]

Tried this however it stated unable to verify signature and rebooted system. So this FAILED. Better luck next time.

Sent from my PC36100 using Android Tablet Forum

 

[kaos420]

weird it still shows signed . lets see if we can get some more devs in on this all the files are there we just need away to implement them.

 

[rprr]

The problem is that the Vizio public verification key is fused into the hardware/CPU. This means that any file you want to push must be signed by the Vizio private key.

 

[kaos420]

The problem is that the Vizio public verification key is fused into the hardware/CPU. This means that any file you want to push must be signed by the Vizio private key.

heres what i did though. i adb pulled my system. adb pulled zimages , sm0, u-boot.bin and zImage. made sure permissions were root. then added thn replaced the same files in the signed update for .57. right now im redoing the .57 zip just with the 4 files i mentioned above and .57 system structure see what happens. will add to op.

op updated with attempt 2

 

[rprr]

heres what i did though. i adb pulled my system. adb pulled zimages , sm0, u-boot.bin and zImage. made sure permissions were root. then added thn replaced the same files in the signed update for .57. right now im redoing the .57 zip just with the 4 files i mentioned above and .57 system structure see what happens. will add to op.

It's certainly worth a try but I suspect that this won't work. The reason is that you will need to sign the all the files with the Vizio private key.

 

[kaos420]

im on .56 already rooted with cmw with your method. just trying to help others . im open to all ideas. what about chaging our key on the cpu some how editing it. ya we wont be able to take official updates.. but we get root who needs official.

 

[Tcsviz77]

Yet another signature fail.

Sent from my PC36100 using Android Tablet Forum

 

[kaos420]

ok so if someone will test attemp 2. let me know. rppr what about using adb.


adb shell dd if="/dev/block/mmcblk0p8 of=/dev/block/zImage

adb push /dev/block/mmcblk0p1 of=/dev/block/ramdisk.img

adb push /dev/block/mmcblk0p6 of=/dev/block/u.boot.bin

adb push /dev/block/mmcblk0p12 of=/dev/block/sm0

http://www.mediafire.com/?wybpyca329qdldp

is the 4 files someone try with adb.

 

[rprr]

ok so if someone will test attemp 2. let me know. rppr what about using adb.

adb push zImage /sdcard/zImage
adb shell dd if="/dev/block/mmcblk0p8 of=/dev/block/zImage

adb push /dev/block/mmcblk0p1 of=/dev/block/ramdisk.img

adb push /dev/block/mmcblk0p6 of=/dev/block/u.boot.bin

adb push /dev/block/mmcblk0p12 of=/dev/block/sm0

images.rar

is the 4 files someone try with adb.

I don't understand what you are trying to do here.

 

[kaos420]

thats the locations i used adb to pull the corresponding files from. wondering if someone on .57 who can still access adb could possibly push them.

last lines of .57 update script.
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...");

so i used those . .

 

[rprr]

In order to get back to .56 it is not necessary to upload the zImage, ramdisk, sm0, and u-boot.bin. The only thing needed is to modify the system partition. Unfortunately, it is a read-only file system by default.