Related
Hi All,
My Nexus 7 LTE is rooted with TWRP.
I've downloaded the OTA for 4.4.3 from one of the posts in the forums. It updates my razorg from KOT49H to KTU84L.
After using adb sideload, the update zip file is transferred successfully to my device, but it fails with the error message
Code:
"/system/bin/surfaceflinger" has unexpected contents.
error excuting updater binary in zip '/data/media/0/sideload.zip
Does anyone have any idea what could be causing the update to fail?
I've already restored to a stock kernel (from franco kernel) as well as uninstalled xposed framework.
Thanks!
Install stock recovery and take ota as normal. Then reinstall twrp and reroot.
If you fail update I have a backup I made with twrp you can use. Just need to extract it to your twrp backup folder and restore. It's 100% stock and was made after wiping data. Can't post a link to my Dropbox right now because of my post count but if you need it I an send it to you by other means.
Thanks for that. I think I might have to flash stock recovery and give it a shot, although I have a feeling even if I do that, it might not work as my tablet is no longer stock, since I've installed apps which made changes, such as FKU as well as CF-Lumen.
endlesstrail said:
Thanks for that. I think I might have to flash stock recovery and give it a shot, although I have a feeling even if I do that, it might not work as my tablet is no longer stock, since I've installed apps which made changes, such as FKU as well as CF-Lumen.
Click to expand...
Click to collapse
To get the OTA to work with either a stock or custom recovery the unexpected contents error will have to be fixed first. Somehow the surfaceflinger file was changed, that's a new one for me so I have no idea what could have changed it. I could upload a copy of mine if you want to try it but I do have the wifi version and don't know if they are the same. Otherwise you will need to fastboot flash the system image for the version you are running now for the update to work. Instead of doing that I would download the 4.4.3 factory image and extract the radio, system, and boot images and fastboot flash those. The bootloader did not change so that does not need to be flashed. Before flashing the images I would download the newest supersu zip and put it in your device storage, then flash the images, once that is done do not reboot, boot into recovery instead and flash the supersu zip then wipe cache and dalvik then reboot. Should take less than 15 minutes. ; )
You could also flash the factory image but that will install the stock recovery, lose root and completely wipe your device. If you are using windows you can open the flash-all.bat with a text editor like notepad and remove the -w from the text, that will prevent the userdata image from being flashed which wipes your device.
Thanks for your reply, wantabe.
I guessed as much, that if I couldn't figure out what changed the surfaceflinger, I might as well do a complete flash back to stock, which was what I did. Now it's just a matter of flashing back TWRP, restoring all the apps and waiting for 4.4.4 :good:
I've got an HTC One M9 (Rogers) that I've rooted and installed CM13 (13.0-20160221-nightly-himaul). I'm reasonably experienced with custom ROMs and such having played with all of this stuff on several Samsung devices (Captivate, Galaxy Nexus, SGS3), but this is my first go on an HTC device and first time running TWRP as opposed to Clockworkmod. I attempted to update my TWRP from 2.8.4 to 3.0.0-2 by booting to recovery. Not sure how and where I went wrong in that process but I can no longer boot to recovery, the phone starts up just fine and is usable. I can still access download mode and the bootloader, device is S-on (and has never been s-off). I have since attempted to reinstall TWRP via ADB commands as per the below post. The flash seems to take, no errors but still I'm unable to access recovery. I'm at somewhat of a loss as to what if anything I can try next.
http://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133
the0f said:
I've got an HTC One M9 (Rogers) that I've rooted and installed CM13 (13.0-20160221-nightly-himaul). I'm reasonably experienced with custom ROMs and such having played with all of this stuff on several Samsung devices (Captivate, Galaxy Nexus, SGS3), but this is my first go on an HTC device and first time running TWRP as opposed to Clockworkmod. I attempted to update my TWRP from 2.8.4 to 3.0.0-2 by booting to recovery. Not sure how and where I went wrong in that process but I can no longer boot to recovery, the phone starts up just fine and is usable. I can still access download mode and the bootloader, device is S-on (and has never been s-off). I have since attempted to reinstall TWRP via ADB commands as per the below post. The flash seems to take, no errors but still I'm unable to access recovery. I'm at somewhat of a loss as to what if anything I can try next.
http://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133
Click to expand...
Click to collapse
Are you running 3.x firmware? TWRP 3.0+ only works on firmware 3.x (i.e., the firmware that comes with Marshmallow). Flash TWRP 2.8x using fastboot and it should work just fine.
efrant said:
Are you running 3.x firmware? TWRP 3.0+ only works on firmware 3.x (i.e., the firmware that comes with Marshmallow). Flash TWRP 2.8x using fastboot and it should work just fine.
Click to expand...
Click to collapse
You sir are my hero, that definitely worked. So now to update that firmware so that I can update everything else. By chance do you know of a guide on how to update to that newer firmware version?
the0f said:
You sir are my hero, that definitely worked. So now to update that firmware so that I can update everything else. By chance do you know of a guide on how to update to that newer firmware version?
Click to expand...
Click to collapse
The only way I know how to do it with S-ON is to restore your device to stock (i.e., the version of stock before you flashed CM), take the OTA update, then flash the ROM you want.
efrant said:
The only way I know how to do it with S-ON is to restore your device to stock (i.e., the version of stock before you flashed CM), take the OTA update, then flash the ROM you want.
Click to expand...
Click to collapse
Sorry to be a bother and ask for any form of hand holding, but any idea where I can source the files for the return to stock? Currently have 2.11.631.2 on there (checked in the bootloader). Either that or a way to go S-OFF, I've been unable to find a guide on how to accomplish this without sunshine, which won't work on Cyanogenmod. If that required flashing even to something more similar to stock (IE Android Revolution) that's not the end of the world. Just kind of at a loss as to how to go about that process from where I am now.
the0f said:
Sorry to be a bother and ask for any form of hand holding, but any idea where I can source the files for the return to stock? Currently have 2.11.631.2 on there (checked in the bootloader). Either that or a way to go S-OFF, I've been unable to find a guide on how to accomplish this without sunshine, which won't work on Cyanogenmod. If that required flashing even to something more similar to stock (IE Android Revolution) that's not the end of the world. Just kind of at a loss as to how to go about that process from where I am now.
Click to expand...
Click to collapse
1) Make sure you have an sdcard formatted exfat in your device.
2) Boot into TWRP and back up your boot image to the sdcard. (You are doing this to get TWRP to create the proper directory structure.)
3) Find your back up that you just created and delete the files in the folder, i.e., the boot image and the md5 file.
4) Make sure TWRP has the option to keep system read-only checked (in the mounts menu).
5) Go here and download the three files (boot, recovery, system_image) for 2.11.631.2 and place them in the folder on your sdcard mentioned in point #3 above.
6) Restore the files using TWRP and reboot your device into Android.
7) You'll get an OTA notification. Accept it and update your device. (It'll take a while and reboot multiple times.)
8) Once updated, you'll get a second OTA notification to update you to Marshmallow. Accept it and update your device. (It'll take a while and reboot multiple times.)
9) Once updated, you can go ahead and flash TWRP 3.0+ and do what you want.
http://forum.xda-developers.com/one-m9/general/guide-return-to-stock-canadian-htc-one-t3108236
efrant said:
1) Make sure you have an sdcard formatted exfat in your device.
2) Boot into TWRP and back up your boot image to the sdcard. (You are doing this to get TWRP to create the proper directory structure.)
3) Find your back up that you just created and delete the files in the folder, i.e., the boot image and the md5 file.
4) Make sure TWRP has the option to keep system read-only checked (in the mounts menu).
5) Go here and download the three files (boot, recovery, system_image) for 2.11.631.2 and place them in the folder on your sdcard mentioned in point #3 above.
6) Restore the files using TWRP and reboot your device into Android.
7) You'll get an OTA notification. Accept it and update your device. (It'll take a while and reboot multiple times.)
8) Once updated, you'll get a second OTA notification to update you to Marshmallow. Accept it and update your device. (It'll take a while and reboot multiple times.)
9) Once updated, you can go ahead and flash TWRP 3.0+ and do what you want.
http://forum.xda-developers.com/one-m9/general/guide-return-to-stock-canadian-htc-one-t3108236
Click to expand...
Click to collapse
Thank you again sir, I'll give that a try this evening when I get back home. The help and the hand holding is very much appreciated. I thought that I knew a fair bit about android phones and custom ROMs from my time with my old Samsung devices, and have had to do a lot of learning when it's come to the One M9. Never had a device with the S-ON feature before and have had a lot of trouble trying to find info on what I need to do. I did find that forum post you linked, but wasn't sure if that applied to my device or not. Again VERY much appreciated.
Yup, 6.0 stock is installed and working, TWRP 3.0.0-2 installed and working as well. This time took a system backup and stored it in a safe place (as I expect much the same trouble when Android N or any other major update happens). Thank you again for all of your assistance in getting my phone fixed and updated.
I am on 4.19.617.1 N android S-off and rooted and have TWRP
is there is way to install this ota or bull it from device as flashable zip?
afaik - no, at least regarding to the info on twrp:
https://twrp.me/faq/officialota.html
if anyone know what to do to repack the file, please advise.
shaygia said:
I am on 4.19.617.1 N android S-off and rooted and have TWRP
is there is way to install this ota or bull it from device as flashable zip?
Click to expand...
Click to collapse
Yes... Download from here... https://www.androidfilehost.com/?w=search&s=4.23.617
alegara said:
Yes... Download from here... https://www.androidfilehost.com/?w=search&s=4.23.617
Click to expand...
Click to collapse
It failed for me in Download mode and in TWRP. System partition has unexpected contents (sigh).
I wonder if that images file on AFH has the various partition images, and can be unzipped. I messed around with the full ruu, tried extracting the rom.zip, that's encrypted... I tried the firmware only flash, that was.. annoying (as Firmware/software mismatches usually are).
What bugs me is that Magisk was supposed to prevent this from happening. I never set system r/w... and still it stated that it was modified. sigh.
I even kept stock recovery, and booted twrp through the bootloader to prepare for OTAs. Blah. </rant>
Not blaming anyone but myself. Just grumbling.
was able to do mine using sneakyghost Batch Tool and the nowipe zip listed on his thread for 4.23.617.1 went without a hitch except for the having to do fastboot flash zip twice as it hangs the first time
grandpajiver said:
It failed for me in Download mode and in TWRP. System partition has unexpected contents (sigh).
I wonder if that images file on AFH has the various partition images, and can be unzipped. I messed around with the full ruu, tried extracting the rom.zip, that's encrypted... I tried the firmware only flash, that was.. annoying (as Firmware/software mismatches usually are).
What bugs me is that Magisk was supposed to prevent this from happening. I never set system r/w... and still it stated that it was modified. sigh.
I even kept stock recovery, and booted twrp through the bootloader to prepare for OTAs. Blah. </rant>
Not blaming anyone but myself. Just grumbling.
Click to expand...
Click to collapse
I hate to reply to myself, but yup, HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.23.617.1_Images.zip had boot.img, recovery.img, and system.img, and I could flash those, along with the firmware for 4.23.617.1. Uninstalled Magisk modules & Magisk first, flashed the images & the nowipe firmware. I re-flashed the stock recovery, so hopefully I won't go through this procedure again. I then checked for updates, and the device reported it was up to date.
Installed magisk again, installed supeuser root module, used magisk hide, installed ViperFX-4.1, systemappify, Google Contacts/Dialer, Greenify.. its all working fine. It runs a bit warmer, and battery usage is not as good as 4.19.617.6... so far. I didnt wipe dalvik/cache.
Anyways, its rooted, passes safetynet, Android pay works, Pokemon go works, etc etc. Thank you whoever made the images zip.
Now to wipe that magisk img and grow the size... I've run into issues with it being small. But now I'm way off topic.
T-Mobile V30 H932 20P Stock Collection
Based on OEM 20P KDZ. Extracted and Repacked.
DISCLAIMER
Proceed at your own risk. I am not responsible for any damage to your device.
Flashing LAF WILL REMOVE TWRP from your laf partition and restore stock DL Mode
Bins in these packages are unmodified and you may need to flash no-verity-opt-encrypt and rctd remover after to keep force-encryption away.
REQUIRED
TWRP on LAF or Recovery
Latest Magisk Zip (if performing clean flash)
no-verity-opt-encrypt
rctd remover
FILE BREAKDOWN
None of these Zips flash the Recovery partition.
Besides StockLAF, these Zips DO NOT flash the LAF partition.
If you want to restore DL Mode and Stock LAF, you must flash the StockLAF package separately.
Bootloader: 20p Stock Bootloader ONLY
FullStock: Full 20p Stock Firmware Only (bootloader, modem, boot, system) - Instructions in Section A
FullStock w/Magisk: Full 20p Stock Firmware + Magisk Root - Instructions in Section B
Debloated w/Magisk: Boot+Debloated System + Magisk Root (force enc & dm-verity removed) - Instructions in Section C
StockLAF: Individual LAF image for returning to stock DL mode
Global Instructions
Always make a backup first
If device has been encrypted, see encryption notes at the bottom before continuing.
A - FullStock
If coming from Nougat, Clean Flash is Recommended
Wipe Dalvik, System, Data, Cache... then flash
If coming from previous Oreo versions, Dirty Flash works fine. OS and Apps are updated.
Copy All Zips to SDCard
Flash h932_FullStock.zip
Flash Magisk
Flash no-verity-opt-encrypt
Flash rctd remover
Reboot to system and install Magisk Manager (if not installed)
B - FullStock with Magisk
This zip just cuts out the step of flashing magisk manually.
This zip should be dirty flashed on a system that already has magisk. or Magisk may not flash successfully
If this zip is clean flashed, pay close attention to flash logs. If magisk fails to repack the boot image during flash, flash Magisk again.
Flash h932_FullStock_Magisk.zip
Flash no-verity-opt-encrypt
Flash rctd remover
Wipe Dalvik+Cache
Reboot
C - Debloated with Magisk
Be aware
This ROM does NOT flash LAF, recovery, bootloader or modem firmware directly.
If you are coming from an older version of android, this rom does not include the complete device firmware, which you may want.
For those included above, you should flash FullStock before flashing this to make sure all of your device firmware is up to date.
Boot image has been patched to remove force encryption and dm-verity
This ROM has had several pre-loaded and system apps removed. If someone wants to send me a list of any additional apps that can be safely removed, i can update the rom to include them.
system/app/CloudPrint
system/app/Drive
system/app/Duo
system/app/EditorsDocs
system/app/EditorsSheets
system/app/Gmail2
system/app/GooglePay
system/app/LGAccount
system/app/LGAirDrive
system/app/LGAmazonAssistant
system/app/LGAmazonAttribution
system/app/Maps
system/app/Music2
system/app/Photos
system/app/YouTube
system/priv-app/CloudHub
system/priv-app/CollageWallpapers
system/priv-app/facebook-installer
system/priv-app/LG360VideoWallpaper
system/priv-app/LG360Wallpaper
system/priv-app/LGEasyHome
system/priv-app/LGEmail
system/priv-app/LGExchange
system/priv-app/LGQHelpService
system/priv-app/LGVVM
system/priv-app/NameID
system/priv-app/TMO_MyAccount
system/priv-app/xtra_t_app
system/vendor/app/facebook-appmanager
system/vendor/overlay/com.lge.easyhome
system/vendor/overlay/com.lge.email
system/vendor/overlay/com.lge.exchange
system/vendor/overlay/com.lge.lgworld
system/vendor/overlay/com.lge.qhelp
system/vendor/overlay/com.lge.qhelp.application
system/vendor/overlay/com.lge.qmemoplus
For best results a clean flash is recommended for this package
Format data, and remove any apps installed to external sd. Then wipe system, dalvik, cache, data, internal storage
This will ensure no lingering apps are left behind.
If coming from Nougat, Clean Flash is Highly Recommended
Wipe Dalvik, System, Data, Cache... then flash
If coming from previous Oreo Versions
Wipe Dalvik, Cache, and System, and optionally data and internal storage
If you do not perform a clean flash, you may need to manually remove the apps left behind after flashing
Flash h932_Debloated_Magisk.zip
Reboot
DOWNLOADS
Stable v1.0
Project files are hosted on SourceForge
Bootloader - md5:45d8897c317b2e2e7b02d0766a93556c
FullStock ROM - md5:092585a169b54f067cec27d57b0c041c
FullStock w/Magisk - md5:6854a34ed956e9b30fb8e59c34de6b39
Debloated w/Magisk - md5:5a11334c8e42dfe55f2a71bbb0820612
StockLAF - md5:9090ee8645f2018c6bd88c9169c52c1b
*************************************************************************************************************
Encryption Notes
In Android, a stock device will have it's data encrypted. Often when working in TWRP on an encrypted device, you will be greeted by prompt asking for a passcode in order to decrypt the device. Unless that port of TWRP has been written for your specific device and supports decryption, you will not be able to decrypt the data on your phone. If you cannot decrypt the data, then TWRP cannot mount system and/or other partitions it needs to mount in order to safely flash anything. In order to solve this problem, sadly, you have to format the data partition on your phone (losing all personal data accumulated on the internal storage, so back it all up manually) The steps for this process are Format Data in TWRP, Reboot to recovery (to mount partitions), then flash your rom and root. There are a few tools out there to disable force encryption on your device. See the Required section above for links for this device.
Packages have been successfully tested VIA the methods outlined above.
If anyone has any issues with one or more of these packages, please let me know. Thank you!
-weakNPCdotCom
XDA:DevDB Information
[STOCK] h93220p, ROM for the LG V30
Contributors
weakNPCdotCom
Source Code: https://sourceforge.net/projects/t-mobile-v30-firmware/files/h932/20p/
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
Based On: 20p KDZ
Version Information
Status: Stable
Created 2018-12-20
Last Updated 2018-12-28
would it be possible for you to make a "debloated" stock rom?? all stuff we can "technically" reinstall from play store. Something close to stock android as possible.
This did not work. I used the zip with magisk. Magisk was and is not installed I lost TWRP and download mode doesnt work and just reboots to system after a minute.
Anyway to fix this? It boots fine but i dont have fastboot and download mode shows only the download mode screen then reboots
Andi32790 said:
This did not work. I used the zip with magisk. Magisk was and is not installed I lost TWRP and download mode doesnt work and just reboots to system after a minute.
Anyway to fix this? It boots fine but i dont have fastboot and download mode shows only the download mode screen then reboots
Click to expand...
Click to collapse
Verify that you did download "h93220p_fullStock_wMagisk.zip". It worked fine for me, and I can confirm it has magisk as I was on 17.3 on 20o and magisk manager says I'm on 18.
Also, were you coming from 20o?
[Cruzer] said:
would it be possible for you to make a "debloated" stock rom?? all stuff we can "technically" reinstall from play store. Something close to stock android as possible.
Click to expand...
Click to collapse
Yes, I can make a debloated ROM. Gimme a day or two and I'll try to add one to the OP.
Andi32790 said:
This did not work. I used the zip with magisk. Magisk was and is not installed I lost TWRP and download mode doesnt work and just reboots to system after a minute.
Anyway to fix this? It boots fine but i dont have fastboot and download mode shows only the download mode screen then reboots
Click to expand...
Click to collapse
Sorry M8, but i tested this zip and verified that it flashes all partitions and then flashes magisk all in one go. I think maybe you downloaded the package without magisk by mistake.
This zip does not flash LAF, so if you had TWRP on LAF before flashing this, you should be able to just boot to download mode using the usb cable and reflash TWRP to recovery.
Andi32790 said:
This did not work. I used the zip with magisk. Magisk was and is not installed
Click to expand...
Click to collapse
After further testing, I discovered that after wiping and doing a clean flash of FullStock w Magisk, Magisk failed to repack the boot image. I had to flash magisk a second time for it to complete the process.
I will update the OP. Thank you for bringing this to my attention. I hope you are able to get back into TWRP
weakNPCdotCom said:
After further testing, I discovered that after wiping and doing a clean flash of FullStock w Magisk, Magisk failed to repack the boot image. I had to flash magisk a second time for it to complete the process.
I will update the OP. Thank you for bringing this to my attention. I hope you are able to get back into TWRP
Click to expand...
Click to collapse
No recovery was not in LAF and was overwritten and I don't have fastboot and download mode doesn't seem to work right. Phone works just no root I guess. I should have paid more attention to what was going on when I flashed it.
Andi32790 said:
No recovery was not in LAF and was overwritten and I don't have fastboot and download mode doesn't seem to work right. Phone works just no root I guess. I should have paid more attention to what was going on when I flashed it.
Click to expand...
Click to collapse
Im sorry man. I honestly have no idea why download mode was affected because these zips don't touch it at all. If you go through the root process again, I recommend keeping a copy of TWRP on both LAF and Recovery.
weakNPCdotCom said:
Im sorry man. I honestly have no idea why download mode was affected because these zips don't touch it at all. If you go through the root process again, I recommend keeping a copy of TWRP on both LAF and Recovery.
Click to expand...
Click to collapse
No worries man I still have a phone plus thats why you all add the disclaimer. Idk just looking for a fix at this point.
[Cruzer] said:
would it be possible for you to make a "debloated" stock rom?? all stuff we can "technically" reinstall from play store. Something close to stock android as possible.
Click to expand...
Click to collapse
I'm having an issue with my kitchen, but as soon as I'm able to solve what's going on ill cook up this ROM
Thanks weakNPCdotCom. I dirty flashed over 20o and it's working great.
weakNPCdotCom said:
I'm having an issue with my kitchen, but as soon as I'm able to solve what's going on ill cook up this ROM
Click to expand...
Click to collapse
No worries take your time. Appreciate the work your doing
I just want to make sure if I dirty flash FullStock w/Magisk that I wont loose TWRP because I dont have back up in LAF.
SIMONAK said:
I just want to make sure if I dirty flash FullStock w/Magisk that I wont loose TWRP because I dont have back up in LAF.
Click to expand...
Click to collapse
I just did it and didn't loose TWRP.
It worked thank you.
SIMONAK said:
I just want to make sure if I dirty flash FullStock w/Magisk that I wont loose TWRP because I dont have back up in LAF.
Click to expand...
Click to collapse
Just pay attention to the flash logs and make sure everything flashes properly
[Cruzer] said:
No worries take your time. Appreciate the work your doing
Click to expand...
Click to collapse
Ok, so I cooked up a debloated and deodexed ROM, but when I tested it, it was really laggy and some system apps crashed all the time.
I think I might be able to get away with not deodexing it for better performance, and probably keeping a few of the apps I removed. Id rather not publish it until it's smooth and stable, so I'll keep working on it.
let me know if you are interested in trying the unstable build and ill upload it but it has issues
weakNPCdotCom said:
Ok, so I cooked up a debloated and deodexed ROM, but when I tested it, it was really laggy and some system apps crashed all the time.
I think I might be able to get away with not deodexing it for better performance, and probably keeping a few of the apps I removed. Id rather not publish it until it's smooth and stable, so I'll keep working on it.
let me know if you are interested in trying the unstable build and ill upload it but it has issues
Click to expand...
Click to collapse
Yah I'll wait til you have all the bugs worked out. Side note when I was "trying" to debloat. I removed chrome from system. It broke a few system apps. Maybe that will help. Thanks again for your work
[Cruzer] said:
Yah I'll wait til you have all the bugs worked out. Side note when I was "trying" to debloat. I removed chrome from system. It broke a few system apps. Maybe that will help. Thanks again for your work
Click to expand...
Click to collapse
I did remove chrome in the ROM so ill keep that in mind when I try again tonight. I don't think I'm going to deodex it either unless I get a smooth running build.. I'm not sure the advantage in oreo anyway since it's vdex now. but ill give it another go
LG V30 T-Mobile H932 20r ROM
For U.S. T-mobile H932 ONLY. Do NOT install this on any other V30/V30+/V30S except U.S. T-mobile H932. You will brick your phone.
DISCLAIMER : I do not hold responsiblity for any of the following but not limited to : Bricks due to not reading, nuclear war, cat dying. I will not be held responsible for any damage of any kind due to the result of this zip. It is held under your own risk. This does not mean that i wont help in any way shape or form to recover from anything that may happen at the result of flashing this zip. PLEASE FLASH RESPONSIBLY! PS. This zip has NOT been tested by me!
This Rom is 100% Stock. Most recent TWRP should first be installed. Then you can install this Rom and have Oreo with working TWRP.
This zip is created from the original KDZ. It contains almost the complete 20r firmware, but the partition table rewriting part and recovery image is removed. I changed the system.img, so you do not have to reinstall TWRP (recovery-from-boot.p deleted) when ROM once booted. I also changed the partition size of system.img, so the vendorized people can install this too without having problems because of a too small system partition. This is a continuation of westwood24's idea and work, I've updated it to the newest fw version and edited / advanced it a bit. I followed his idea and made this for users who can not take OTA's because they have Custom Recovery / Root installed.
Features
Stock build made from official KDZ
Stock Build.prop
Unrooted
system.img modified to keep TWRP
System image size shrunk for being able to flash this on a smaller system partition, mainly caused by vendorizing
Removed dm-verity
Removed rctd (LG's root checker tool daemon)
Enabled opt-encrypt, it's your choice now if you want to encrypt your phone, it's no more forced. TWRP now is capable of decryption (both AOSP and stock) since a few versions
Added DTS build prop
Added all lockscreen weather animations build prop
Installation
What you need
Unlocked Bootloader [How to do]
Working TWRP installed (should be installed already, otherwise you wouldn't need this zip )[Link to newest unofficial TWRP]
When you need Root, Latest Magisk [Download]
H93220r.zip [Download]
How to install
When you are still on Nougat,
you should start fresh: Reboot to recovery using button combo or reboot app (needs root; btw, Magisk offers this possibility too: Menu -> Modules -> three dot menu top right - Reboot to recovery)
Then flash this TWRP.img via image flashing function in TWRP, reboot to recovery again (for fully working new recovery) and do a backup, then copy this backup to your PC.
Then initiate a factory reset. Wipe your system partition too in TWRP advanced wiping menu, copy the 20r firmware zip to your SD and install it. Reboot and enjoy
From Oreo:
For clean install: Factory reset and wipe system
You can also keep your data by simply dirty flashing the zip. *Be aware that problems may occure, maybe you need to do a factory reset to start fresh*
Flash the 20r zip, then Magisk zip when you need root, then reboot to System = you're DONE
P.S.: could be, that you first need to boot up your fresh install and set it up before you can flash magisk.
At the first time you boot to system, it can be TWRP says No OS installed. You can ignore it.
If TWRP asks if you want to install SU, hit no (in newest TWRP SU is disabled, and the option to install the TWRP app is disabled too.)
Rom Version
Android Version: 8.0 Oreo
Android security patch level: 2019-1-1
Don´t forget to hit the thanks-button if you like this zip! :good:
You want to help me with a [donation?] Not asking for it, I have fun doing this for you, but feel free...
#RESERVED
Please to anyone who had issues with the zip.....
We have a fix!
Flash this zip
https://www.androidfilehost.com/?fid=1395089523397908552
Then flash a rom from your SD CARD
ONLY FLASH THIS OF YOU HAD A BRICK FROM 20R!!
Zip is live! Enjoy!
your zip name is wrong.. should be h93220r* ( it doesnt matter but i was confused at first)
also, i flashed it and nothing happened. my system is still the same as i was before (20p)
and in the script, i think it says 'model=VS996' or something. since it just words, it may not matter.
but maybe you used the wrong script for h932
In any case, the zip did nothing for me. flashing only took about 10 secs in total, and flashing system barely took a second.
So seems theres an issue with the zip. Maybe upload didn't quite finish as I did it while at work via rdp to my pc at home. Will look into it when I get off work
JohnFawkes said:
So seems theres an issue with the zip. Maybe upload didn't quite finish as I did it while at work via rdp to my pc at home. Will look into it when I get off work
Click to expand...
Click to collapse
Did you remove the file?
Sent from my LG-H932 using XDA Labs
BROKEN1981 said:
Did you remove the file?
Sent from my LG-H932 using XDA Labs
Click to expand...
Click to collapse
For now yes. Everyone was having issues. I'm on my way home from work right now so it'll be back online in probably an hour
JohnFawkes said:
For now yes. Everyone was having issues. I'm on my way home from work right now so it'll be back online in probably an hour
Click to expand...
Click to collapse
Ahh ok, thought I was missing something.
Sent from my LG-H932 using XDA Labs
JohnFawkes said:
For now yes. Everyone was having issues. I'm on my way home from work right now so it'll be back online in probably an hour
Click to expand...
Click to collapse
looking forward to the fix.
I figured people might want these files.
Root-System-Media
Uploading new zip now! figured out all issues
JohnFawkes said:
Uploading new zip now! figured out all issues
Click to expand...
Click to collapse
Awesome thank you!
Sent from my LG-H932 using XDA Labs
BROKEN1981 said:
Awesome thank you!
Sent from my LG-H932 using XDA Labs
Click to expand...
Click to collapse
no problem. should be live in about 15 minutes
zip is live!
Awesome. Woke up this morning to the system update notification. Glad there are still T-Mobile users around here that works to get this stuff out. Downloading now. Will report back after I flash it.
---------- Post added at 07:43 AM ---------- Previous post was at 07:19 AM ----------
BROKEN1981 said:
I figured people might want these files.
Root-System-Media
Click to expand...
Click to collapse
Are these new in this update?
JohnFawkes said:
zip is live!
Click to expand...
Click to collapse
At the end of the flash it looks like it flashed fine but then it tells me it failed to mount everything. When I go to reboot into the system it tells me there is no OS. I was just going to flash the 20p zip I had but then it restarted and now I can't get into TWRP again. Now it just restarts into fastboot mode
UPDATE: I was able to get back into TWRP by going through the factory reset option (Volume down + Power, etc.) I'm now flashing the 20p zip I have.
UPDATE 2: Didn't work. Got into a bootloop. Restoring an old Lineage backup I have. Should have made a backup of my current state before flashing but I wasn't thinking
UPDATE 3: That didn't work either. Everything I flash it tells me failed to mount '/persist-lg' and just boot loops. I guess the next thing to do is try and use LGUP to restore
Same here as above. Doesnt mount system persist cache.
sunmybun said:
Same here as above. Doesnt mount system persist cache.
Click to expand...
Click to collapse
Flashing anything else doesn't fix it either. My phone is chillin' in recovery mode until I can figure it out
im working on fix guys. zip is removed for now. no clue why this is happening. but a fix is being worked on
JohnFawkes said:
im working on fix guys. zip is removed for now. no clue why this is happening. but a fix is being worked on
Click to expand...
Click to collapse
Thanks. Searching around, I see there have been people having issues like this before with other devices. Something to do with the persist.img. Did the last zip include one? Also, I hope whatever it is can be fixed with a new zip. I don't know why restoring a backup or flashing an old full stock zip wouldn't fix anything.
This is basically what I'm getting
http://en.miui.com/thread-467490-1-1.html