• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root MS840/MS840V question

kanaida

kanaida

Android Expert
Hey guys, been away for a little while. I just wanted to clear a few things up after going through some posts.

I noticed there's an MS840 and MS840V, whats the difference?

Also i've seen things like VV3 -> VV5 firmwared, whats up with those and do they work on the plain MS840 without problems? and have any benefits?

I'm still runnin' ZVA rom #2, but waiting for CM10 to get a little more stable before I try it because my job has me on call etc... so I don't want to play with that just yet ;)

I was going to try out, just wondering if it will be better before I try it out and if it will work on my phone:
http://androidforums.com/connect-4g-all-things-root/705507-rom-ms840-vv3-firmware-04-07-13-a.html
 
kanaida said:
Hey guys, been away for a little while. I just wanted to clear a few things up after going through some posts.

I noticed there's an MS840 and MS840V, whats the difference?

Also i've seen things like VV3 -> VV5 firmwared, whats up with those and do they work on the plain MS840 without problems? and have any benefits?

I'm still runnin' ZVA rom #2, but waiting for CM10 to get a little more stable before I try it because my job has me on call etc... so I don't want to play with that just yet ;)

I was going to try out, just wondering if it will be better before I try it out and if it will work on my phone:
http://androidforums.com/connect-4g-all-things-root/705507-rom-ms840-vv3-firmware-04-07-13-a.html
Click to expand...

I kinda messed up my radio with cm 10 0312 build and flashing vv3 baseband so went stock vv3 on the first gen connect and works good this ROM basically does the restoring to vv3 and rooting it for you and it was released after I had already restored with the cab file and rooting it Lil so yea if you want a better faster data connection install this ROM
 
kanaida said:
Hey guys, been away for a little while. I just wanted to clear a few things up after going through some posts.

I noticed there's an MS840 and MS840V, whats the difference?

Also i've seen things like VV3 -> VV5 firmwared, whats up with those and do they work on the plain MS840 without problems? and have any benefits?
Click to expand...

MS840V is the 2nd generation Connect that is Voice Over LTE capable, otherwise pretty much same phone.

Yes they do work, I'm running VV5 on my OG Connect as we speak.

Here ya go:

VV3, I believe was test software for the 840V that was showing up on refurbished Connect 840s. It is rootable, has better battery life over ZV* based firmware, and has updated baseband. My phone doesn't like it. My GPS, Maps and Pico borked on me using this firmware, but I haven't heard of anybody else having that problem. It's the most popular out of the three VV*s, errbody likes having root access LOL

VV4 is the firmware pumped out on the new VoLTE Connect. It is pretty much the same as VV3, with the exception of being unable to root, and a newer baseband. It is VERY easy on the battery, runs smooth and everything works great (for me, anyway).

VV5 Seems to be a mirror of VV4, with yet another baseband update. Great battery life on this as well, connectivity doesn't seem as good as VV4.

I've found that VV4 works best for me. VV4 tripled my home area 4G speed, nurses the battery and runs like butter, all without root. Oh, and ALL of the VVx firmwares come with that nifty LG QuickMemo app that you see on the Motions :D

And lastly, I don't think that flashing this VV* firmware will enable VoLTE for the OG Connect, but oh well...
 
Thanks. So far it's smoother scrolling and speedy.
4G speeds are about the same, not slow.

Battery life the first day after flashing, horrendous. Went from 14Hrs -> 6:44.
After letting it fully die, then fully charge I'm 3:42 so far with 76% left. That should bring me back up to 14 - 15hrs. Just goes to show how much of a difference properly charging a battery makes... sheesh.

Thanks for the info by the way.

I've been thinking about extracting the cab files, seeing if I can inject root and superuser.apk into em before flashing. that would solve our probs with VV4,VV5...
 
kanaida said:
Thanks. So far it's smoother scrolling and speedy.
4G speeds are about the same, not slow.

Battery life the first day after flashing, horrendous. Went from 14Hrs -> 6:44.
After letting it fully die, then fully charge I'm 3:42 so far with 76% left. That should bring me back up to 14 - 15hrs. Just goes to show how much of a difference properly charging a battery makes... sheesh.

Thanks for the info by the way.

I've been thinking about extracting the cab files, seeing if I can inject root and superuser.apk into em before flashing. that would solve our probs with VV4,VV5...
Click to expand...

Need to extract bin file and then put it back together. I can get the bin extracted, but I have no idea how to get it put back together again...
 
sammyz said:
Need to extract bin file and then put it back together. I can get the bin extracted, but I have no idea how to get it put back together again...
Click to expand...

The bin files (at least for the lucid) pad out the image files to the full installed size, so there might be a fix in store. Perhaps one could...

1) extract bin file
2) update the system.img with root
3) find the offset of the img file inside the bin file (last I recalled the bin extractor was just a wrapper that read the header and pulled segments 1-to-1 from the bin to image files)
4) replace the bytes?

Probably wouldn't boot but there's a slim chance that it might. Maybe best to do it on linux by mounting the system.img as a loopfs?
 
Fingers crossed that the bin doesn't have some sort of built in checksum/signing/encrypted stuff going on. I'll play with it when I get home tonite. I'm sure they must have used standard linux tools to make it, so i'll see what I can find by prodding around. As far as you guys know is it basically a partition image, a custom format or a package made up of different files sorta like a tar?
 
kanaida said:
Fingers crossed that the bin doesn't have some sort of built in checksum/signing/encrypted stuff going on. I'll play with it when I get home tonite. I'm sure they must have used standard linux tools to make it, so i'll see what I can find by prodding around. As far as you guys know is it basically a partition image, a custom format or a package made up of different files sorta like a tar?
Click to expand...

The cab/kdz file is built using Windows.
The bin/tot file is inside the cab/kdz file after extraction from the .wdb file.
The partitions are in .img format.

So add root to system.img.
Take ALL the partitions and convert it to a bin file. Use windows to convert the bin back into cab/kdz.

The hardest part will be remaking the bin file. Once that's done, the rest is easy.
 
Ill see if I can mount it in Linux as a loop device muhahahaha... :) the unmount after I copy the files in. By any chance u know the file system type? Can't remember if its etx3/4 or that other funky one for flash... ummm... ? The name escapes me at the moment...
 
I extracted the cab, its got a DLL, wdb and wdh (header + data?) Know how to get the bin out of that?
 
ah.. brings back memories :)

rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p26 on /system type ext4 (ro,relatime,barrier=0,data=ordered)
/dev/block/mmcblk0p22 on /tombstones type ext4 (rw,nosuid,nodev,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p1 on /firmware type vfat (ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/mmcblk0p28 on /data type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/mmcblk0p12 on /persist type ext4 (rw,nosuid,nodev,relatime,barrier=1,nodelalloc,data=ordered)
/dev/block/mmcblk0p27 on /cache type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p29 on /mpt type ext4 (rw,nosuid,nodev,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p23 on /mm type ext4 (rw,nosuid,nodev,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p14 on /system/etc/firmware/misc_mdm type vfat (ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/vold/179:33 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:33 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/dm-0 on /mnt/asec/dragusoft.software.mk9LivingGuide-1 type vfat (ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
 
I just ran it, extracted header ok. but -extract gave wine the people's elbow lol... moving files to windows for the moment to try again
 
In windows I got it extracted... thank virtualbox for that :)

output was:
0-.img (2.5MB)
0-FGG.img (128K)
17-.img (31/32 MB)

kinda funny, unless you account for unused disk image space.

lemme see if I can mount those suckers now.
 
kanaida said:
In windows I got it extracted... thank virtualbox for that :)

output was:
0-.img (2.5MB)
0-FGG.img (128K)
12-.img (31/32 MB)

kinda funny, unless you account for unused disk image space.

lemme see if I can mount those suckers now.
Click to expand...

Nope. The actual files are supposed to have at least system.img, recovery.img and boot.img
 
thump.

If anyone can get me the img files extracted, I can inject the su and superuser.apk files into it, then we can re-pack it.
 
trying from scratch in windows first, i think wine for linux... you need to go home, you're drunk! lol:
[HIGH]C:\Users\user\Documents\bin>LGExtract.exe -wdb MS840VV5_02.SVV5_02.P3032.wdb MS8
40_WD_1_0_4_0.dll
Extracting:
WDB: MS840VV5_02.SVV5_02.P3032.wdb
DLL: MS840_WD_1_0_4_0.dll

File: BIN\MS840VV5_02.bin
File: CAL\LGMS840MSM_NV_002.Ini
File: NVMeta\MS840_NVMetaData.csv
File: PRL\MPCS_AWS_3032.prl
File: SCR\MS840ZVV5_02.scr
File(s) successfully extracted![/HIGH]
 
kanaida said:
trying from scratch in windows first, i think wine for linux... you need to go home, you're drunk! lol:
C:\Users\user\Documents\bin>LGExtract.exe -wdb MS840VV5_02.SVV5_02.P3032.wdb MS8
40_WD_1_0_4_0.dll
Extracting:
WDB: MS840VV5_02.SVV5_02.P3032.wdb
DLL: MS840_WD_1_0_4_0.dll

File: BIN\MS840VV5_02.bin
File: CAL\LGMS840MSM_NV_002.Ini
File: NVMeta\MS840_NVMetaData.csv
File: PRL\MPCS_AWS_3032.prl
File: SCR\MS840ZVV5_02.scr
File(s) successfully extracted!
Click to expand...

That's not the header. Header.bin is created after running binextractor.exe -ebh filename
 
You must log in or register to reply here.
Back
Top Bottom