If you guys were following my other thread, i'm taking the VV5 cab file, extracted the BIN and injected clockwork recovery.
I have 4 possible files to try as i didn't know the specific offset to inject it into, but I have a hunch that it's offset 3 that will work.
Not sure 100% how to flash it back, i think the BIN can be converted back to KDZ or maybe just flashed directly.
TRY AT YOUR OWN RISK
In theory after flashing, you can boot into CWM, then flash the zip that installs root and superuser.apk (i don't have that zip but i know it's in the forum here somewhere, if u have it please link). Since we have CWM at this point, rooting is trivial. If this works then I can do this for pretty much any new firmware that shows up.
Here's 4 different bin files to try
Unzip them with 7zip first bins are inside.
For those interested, I extracted the BIN from the cab. Found ANDROID! string offsets inside the bin. Made copies named after each offset in order. Then injected the raw cwm image into those offset files.
One last word of confidence. This type of method has worked on the LG-P970's BIN files. I had to change some steps as I had more offsets though.
I have 4 possible files to try as i didn't know the specific offset to inject it into, but I have a hunch that it's offset 3 that will work.
Not sure 100% how to flash it back, i think the BIN can be converted back to KDZ or maybe just flashed directly.
TRY AT YOUR OWN RISK
In theory after flashing, you can boot into CWM, then flash the zip that installs root and superuser.apk (i don't have that zip but i know it's in the forum here somewhere, if u have it please link). Since we have CWM at this point, rooting is trivial. If this works then I can do this for pretty much any new firmware that shows up.
Here's 4 different bin files to try
Unzip them with 7zip first bins are inside.
For those interested, I extracted the BIN from the cab. Found ANDROID! string offsets inside the bin. Made copies named after each offset in order. Then injected the raw cwm image into those offset files.
HTML:
kanaida@kanaida-pc:~/Downloads/KDZ_FW_UPD_EN/CAB_VV5/BIN$ dd if=MS840VV5_02.bin| strings -n 8 -t d| grep ANDROID!
34148071 @ANDROID!
34995760 ANDROID!
37486592 ANDROID!
52166656 ANDROID!
1213696+0 records in
1213696+0 records out
621412352 bytes (621 MB) copied, 7.10332 s, 87.5 MB/s
kanaida@kanaida-pc:~/Downloads/KDZ_FW_UPD_EN/CAB_VV5/BIN$ dd if=cwm.img bs=1 seek=34148071 conv=notrunc of=MS840VV5_02.offset1.bin
5758976+0 records in
5758976+0 records out
5758976 bytes (5.8 MB) copied, 7.41442 s, 777 kB/s
kanaida@kanaida-pc:~/Downloads/KDZ_FW_UPD_EN/CAB_VV5/BIN$ dd if=cwm.img bs=1 seek=34995760 conv=notrunc of=MS840VV5_02.offset2.bin
5758976+0 records in
5758976+0 records out
5758976 bytes (5.8 MB) copied, 7.38104 s, 780 kB/s
kanaida@kanaida-pc:~/Downloads/KDZ_FW_UPD_EN/CAB_VV5/BIN$ dd if=cwm.img bs=1 seek=37486592 conv=notrunc of=MS840VV5_02.offset3.bin
5758976+0 records in
5758976+0 records out
5758976 bytes (5.8 MB) copied, 7.51165 s, 767 kB/s
kanaida@kanaida-pc:~/Downloads/KDZ_FW_UPD_EN/CAB_VV5/BIN$ dd if=cwm.img bs=1 seek=52166656 conv=notrunc of=MS840VV5_02.offset4.bin
5758976+0 records in
5758976+0 records out
5758976 bytes (5.8 MB) copied, 7.35728 s, 783 kB/s
One last word of confidence. This type of method has worked on the LG-P970's BIN files. I had to change some steps as I had more offsets though.