Root Dumps of H631 6.0 update

[TMacgnolia]

Seeing that I am rooted now I was able to pull some dumps of the H63120b ROM for the H631 LG G Stylo. I have the system.img dump, the boot.img dump, and the stock recovery.img dump. If any more are needed post it here and I will pull them and post them here.

System.img

Boot.img

Recovery.img (stock)

 

[androidlover01]

Is there any we can use these to update the metro pcs stylo to mm now?

 

[TMacgnolia]

Is there any we can use these to update the metro pcs stylo to mm now?

Someone will have to put together a flashable zip file for Metro PC devices. But I am not sure if the Metro PC variant will have to have the updated radio or if it can even have the updated radio flashed to it.

 

[androidlover01]

Well the credit goes to (NullaVisus) on xda he has snagged the official mm update.Zip from his t-mobile stylo so maybe this can help create a update.zip for the metro pcs stylo.

LINK to the snagged t-mobile mm update.Zip - https://mega.nz/#!Ukg12aJC!i7B3LZaz0sNwSVT8WNK7Mpi-fdXFvcTQp3QEIASkkgw

 

[TMacgnolia]

Well the credit goes to (NullaVisus) on xda he has snagged the official mm update.Zip from his t-mobile stylo so maybe this can help create a update.zip for the metro pcs stylo.

LINK to the snagged t-mobile mm update.Zip - https://mega.nz/#!Ukg12aJC!i7B3LZaz0sNwSVT8WNK7Mpi-fdXFvcTQp3QEIASkkgw

I don't understand why you say that as anybody that was rooted could have snagged the updat.zip. You just have to copy to internal or external storage from data/cache before you install it.

No more importantly the T-Mobile variant recieved a small update just a week or so before the mm update. In that update there was a radio.img patch file and a boot.img patch file. So I am wondering how this will effect the Metro PC variant.

 

[Bard]

Thank you for the files

 

[HallOfPromise]

Thank you very much!

I am a bit behind on this, though. Are these flashable via custom recovery?

 

[Bard]

Thank you very much!

I am a bit behind on this, though. Are these flashable via custom recovery?

No these are not flashable. These are packed image file of the phone.

Of course you can still flash these via ADB command but don't do it.. you will brick the phone. Developers have to look them, cook them and make flashable .ZIP file.

 

[Josephwv]

What about restoring boot.img and system.img only in twrp? I modified the update.zip and got it to install in twrp but it just goes through bootloop

 

[Bard]

What about restoring boot.img and system.img only in twrp? I modified the update.zip and got it to install in twrp but it just goes through bootloop

You can certainly try but not sure if that will fix your bootloop.

We know that update.zip isn't complete package, it's only 700mb while system.img dump is already 2.2GB.

Since the device is rooted and dump images are available, I think the best & the easiest way is using tmacgnolia's files and cook complete flashable ROM. Then ask users to flash it from Tmobile H63110L version. Wel... this is my guess and what I am trying to do now.

It's only the first day after dump file released so let's see what we can get out from here.

 

[Josephwv]

The issue too is that bootloader gets relocked during the update and causes issues now that we have root for 6.0 cant somebody do a backup in twrp and upload it and we can just restore and have 6.0 already rooted

 

[TMacgnolia]

I am currently away from home for the weekend and will not be back home until late Sunday evening. I plan to look at things more Monday. It may be possible for me to dump the aboot.img for the Metro PCS users to use as the two variants are actually the samr just different certs from what I can tell. So the bootloader should work on the Metro PCS version. But some one with the Metro PCS version will have to be brave enough to fully unlock with "fastboot oem unlock" and fastboot flash aboot.img. There is a risk of fully beicking the de ice by doing this so if it happens it will have to be at the usersbown risk and I will not be responsible for any harm to the device as I have warned of the risk of doing this.

The update.zip released by T-Mobile only has patch files so it os really not usable to flash on it's own. It will have to be a zip made from the full system.img dump and boot.img dump to get it working on the Metro PCS variant. As I said I will look into this more Monday.

 

[antonioblee1]

I am currently away from home for the weekend and will not be back home until late Sunday evening. I plan to look at things more Monday. It may be possible for me to dump the aboot.img for the Metro PCS users to use as the two variants are actually the samr just different certs from what I can tell. So the bootloader should work on the Metro PCS version. But some one with the Metro PCS version will have to be brave enough to fully unlock with "fastboot oem unlock" and fastboot flash aboot.img. There is a risk of fully beicking the de ice by doing this so if it happens it will have to be at the usersbown risk and I will not be responsible for any harm to the device as I have warned of the risk of doing this.

The update.zip released by T-Mobile only has patch files so it os really not usable to flash on it's own. It will have to be a zip made from the full system.img dump and boot.img dump to get it working on the Metro PCS variant. As I said I will look into this more Monday.

The only concern I have with doing this is I have the newer stylo with different screen . are there 2 variations of stylos for the tmo build As well?

 

[Blu8]

So running "fastboot oem unlock" on a metro stylo isn't the problem? Only flashing the T-Mobile bootloader could possibly brick correct?

@antonioblee1 I am pretty darn sure the T-Mobile Stylo is in the same boat with the newer screen business.

 

[TMacgnolia]

The only concern I have with doing this is I have the newer stylo with different screen . are there 2 variations of stylos for the tmo build As well?

This should not matter as the LG devs had to make it work woth both screen types or thwy would have some screwed up devices when they pushed the update. Plus now that I think about it the bootloader of both the T-Mobile and Metro PCS variants should be the same as the both use the T-Mobile network and the Metro PCS can run the T-Mobile ROMs. The Metro PCS variant only has different certs to signify that it is a Metro PCS variant.

So running "fastboot oem unlock" on a metro stylo isn't the problem? Only flashing the T-Mobile bootloader could possibly brick correct?

@antonioblee1 I am pretty darn sure the T-Mobile Stylo is in the same boat with the newer screen business.

Yes only flashing the aboot.img (which is the bootloader) could cause a brick. But I am thinking this is a very minimal risk as the T-Mobile and Metro PCS variants are practically the same device. But there is a risk as you are messing with the bootloader and anytime you mess with the bootloader there is a risk of bricking the device.

 

[HallOfPromise]

The funny thing is, if you pop off the back of the phone, you'll see both model numbers on the phone. Both H631/MS631 is listed in a couple spots. So, it could be the hardware is exactly the same. I mean, it would seem simple for Tmo to order one giant batch for both Tmo and Metro, and just flash their respected versions of the OS.

I did the same thing with the LG F6. I bought the phone from Metro, unlocked it, and flashed the tmo kdz onto the phone to be used on Tmo. And on that phone, it too had both the Tmo and Metro model numbers on the back.

 

[antonioblee1]

This should not matter as the LG devs had to make it work woth both screen types or thwy would have some screwed up devices when they pushed the update. Plus now that I think about it the bootloader of both the T-Mobile and Metro PCS variants should be the same as the both use the T-Mobile network and the Metro PCS can run the T-Mobile ROMs. The Metro PCS variant only has different certs to signify that it is a Metro PCS variant.



Yes only flashing the aboot.img (which is the bootloader) could cause a brick. But I am thinking this is a very minimal risk as the T-Mobile and Metro PCS variants are practically the same device. But there is a risk as you are messing with the bootloader and anytime you mess with the bootloader there is a risk of bricking the device.

Okay probably today I'm going to try making a flashable zip. Thanks

 

[Blu8]

You can always just copy them to your internal storage or sd card and use the "install img" option in twrp, no?

Never mind that was silly of me

 

[antonioblee1]

You can always just copy them to your internal storage or sd card and use the "install img" option in twrp, no?

Never mind that was silly of me

Twrp I think only has option to flash recovery and boot img the system img is going to have to be extracted and converted into a zip. I was just going to use the cm12.1 zip as template and replace the files with the files in the IMG.

 

[TMacgnolia]

Twrp I think only has option to flash recovery and boot img the system img is going to have to be extracted and converted into a zip. I was just going to use the cm12.1 zip as template and replace the files with the files in the IMG.

You can tey that but I am pretty sure it will not work. Well atleast without any tweaks to the updater-script. I am also not aure if the updater-binaries are going to be compatible. But like I said you can try.

Also when you unpack the system.img make sure to remove some of the apps that are in there as it a couple of apps I installed from ttheje play store in the dump. I think it is Tinder(don't judge me), Facebook, Facebook messenger, Evernote, AZ Screen Recorder, Transparent Weather clock, Rootchecker, Tapatalk, amd of course all the Google apps as people will need to flash them seperate to not violate Googles T & S.

 

[Blu8]

Yeah I tried making a zip that just flashed the system and boot images to their partitions and it was a no go lol
TWRP gave me a no os installed warning and when I chose to reboot anyway (zip went through fine) it got stuck on the lg screen for a minute and then proceeded to give me a bsod basically saying something about a subsystem crash and mentioning the modem, I tried lol
And now I'm out and about, had to kdz back to stock as I couldn't even boot into recovery manually.

 

[antonioblee1]

You can tey that but I am pretty sure it will not work. Well atleast without any tweaks to the updater-script. I am also not aure if the updater-binaries are going to be compatible. But like I said you can try.


Also when you unpack the system.img make sure to remove some of the apps that are in there as it a couple of apps I installed from ttheje play store in the dump. I think it is Tinder(don't judge me), Facebook, Facebook messenger, Evernote, AZ Screen Recorder, Transparent Weather clock, Rootchecker, Tapatalk, amd of course all the Google apps as people will need to flash them seperate to not violate Googles T & S.

Yeah I'm pretty familiar with editing the updater-script . the updater binary not so familiar lol. Haha I will take a look at the apps and delete it thanks for your help.

Yeah I tried making a zip that just flashed the system and boot images to their partitions and it was a no go lol
TWRP gave me a no os installed warning and when I chose to reboot anyway (zip went through fine) it got stuck on the lg screen for a minute and then proceeded to give me a bsod basically saying something about a subsystem crash and mentioning the modem, I tried lol
And now I'm out and about, had to kdz back to stock as I couldn't even boot into recovery manually.

Ahh.. So maybe we need the patched radio update that tmac mentioned the tmo version received.

 

[TMacgnolia]

Yeah I tried making a zip that just flashed the system and boot images to their partitions and it was a no go lol
TWRP gave me a no os installed warning and when I chose to reboot anyway (zip went through fine) it got stuck on the lg screen for a minute and then proceeded to give me a bsod basically saying something about a subsystem crash and mentioning the modem, I tried lol
And now I'm out and about, had to kdz back to stock as I couldn't even boot into recovery manually.

Yeah seems like my thinking may be correct. The first small T-Mobile update installed a patch the the radio and the boot.img. then the 6.0 installed yet another patch to the boot.img. Not sure about the radio though as I only had a few minutes to look inside the update.zip for 6.0 before I left for the weekend. Anyway my point being it looks like the bootloader will have to be updated as well as the radio and I feel pretty confident that the two variants uae the same bootloader as ROMs from either one will run on either device. But do to the fact that flashing either aboot or radio partitions come with a risk of bricking I don't want to ask anyone to do that. I am back home now though and got a few rhings I want to try out but got to charge my device some before I can try them.

 

[Blu8]

Do you think you could upload the radio.img as well?

 

[antonioblee1]

Yeah seems like my thinking may be correct. The first small T-Mobile update installed a patch the the radio and the boot.img. then the 6.0 installed yet another patch to the boot.img. Not sure about the radio though as I only had a few minutes to look inside the update.zip for 6.0 before I left for the weekend. Anyway my point being it looks like the bootloader will have to be updated as well as the radio and I feel pretty confident that the two variants uae the same bootloader as ROMs from either one will run on either device. But do to the fact that flashing either aboot or radio partitions come with a risk of bricking I don't want to ask anyone to do that. I am back home now though and got a few rhings I want to try out but got to charge my device some before I can try them.

How can you obtain the patch ? Can you pull the radio or do you have to downgrade via KDZ and copy the update.zip