T-Mobile V30 H932 30d (Pie) Stock Collection
Based on OEM 30d 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
TWRP 3.2.3-7
Latest Magisk Zip (if performing clean flash)
Magisk
@Zackptg5 Disable_Dm-Verity_ForceEncrypt_08.18.2019
@JohnFawkes AK3 RCTD Remover
Link to thread
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: 30d Stock Bootloader ONLY
Modem: 30d Stock Modem ONLY
FullStock: Full 30d Stock Firmware Only (bootloader, modem, boot, system) - Instructions in Section A
StockLAF: Individual LAF image for returning to stock DL mode
Global Instructions
Always make a backup first
Zip has been tested VIA Clean AND Dirty Flash following the provided instructions
If device has been encrypted, see encryption notes at the bottom before continuing.
A - FullStock
Copy All Zips to SDCard
Boot to TWRP.
Flash h93230d_FullStock.zip
Flash Magisk
Flash Disable DM-Verity Force Encrypt
Flash AK3 RCTD Remover
Reboot to system and install Magisk Manager (if not installed)
DOWNLOADS
Stable v1.0
Project files are hosted on SourceForge
Bootloader - md5:8ae313d033e883c60d8d4fea89f13c4e
Modem - md5:4ebf96eb1c8bafe06d96502d1558c324
FullStock ROM - md5:6bc9c4af2080003ff80587f98c2348e9
StockLAF - md5:799362769b0712a10818c0f26258efc2
*************************************************************************************************************
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.
FullStock has been tested VIA Clean AND Dirty Flash.
If anyone has any issues with one or more of these packages, please let me know. Thank you!
-weakNPCdotCom
XDA:DevDB Information
[STOCK] H93230d, ROM for the LG V30
Contributors
weakNPCdotCom
Source Code: https://sourceforge.net/projects/t-mobile-v30-firmware/files/h932/30d/
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: 30d KDZ
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2019-10-09
Created 2019-10-09
Last Updated 2019-10-09
Official FullStock Zip is now available.
DEBLOATED
I will be working on a debloated zip in the near future (as soon as I can find a few hours to spare IRL).
In the mean time, there is a trick for a "debloated" PIE install.
1. Clean Flash 20r FullStock (unless you are already on it). Do not reboot.
2. Flash 20r Debloated Image.
3. Flash Magisk, and the RCTD Remover, Opt-Encrypt zips in the 20r thread.
4. Reboot to system, (DO NOT UPDATE ANY APPS) and set things up the way you like them. If any system apps get updated, make sure you uninstall any updates for those apps before step 4
5. Dirty flash 30d, Magisk, and the RCTD Remover and Disable DM-Verity zips in the 30d thread.
The removed system apps should not be installed, and you should have a "debloated" version of 30d on your device.
When I dirty-flashed 30d coming from debloated Oreo, my system was still debloated with the exception of a couple google apps like Duo.
KNOWN ISSUES
1. Broken Lock-Screen after Dirty Flash
Solution = TWRP - Advanced - File Manager - data/system -> Delete lock/pattern settings .db files and gatekeeper files. Reboot and set your lock screen again. FP will not be lost.
Special thanks to:
@ChazzMatt
@immns
@JohnFawkes
@Zackptg5
and thanks for all the support from the xda-developers community.
Personal Update
I have traded my H932 in for the OnePlus 7 Pro (which I am pretty happy with). I will continue to help create zip packages for the H932 in the near future. However, I will not be able to test those zips. Going forward, ill need some help with testing when updates come out, but I will do my best to continue creating packages for everyone.
Yay! Thanks for all you do!
Awesome! Thanks for working on getting these packages put together, @weakNPCdotCom!
PUTTING THIS ON THE FRONT PAGE. From a post later in the thread.
For those who want to dirty flash -- if you have no problems, good for you.
If you find you need to clean flash in TWRP, then follow these steps:
TWRP-FLASHABLE NOTES:
Make sure you are using stable TWRP 3.2.3-7 from post #1.
a. Wipe Data – Factory Reset
b. Install – set storage to the External SD (if you have a microSD card) OR drag necessary files over from PC once in TWRP.
c. Flash the full stock zip.
d. Install the latest stable Magisk zip. (This is to give the encryption disabler root privileges)
e. Install @Zackptg5 Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler).
f. Install @JohnFawkes AnyKernel 3 RCTD Remover (root checker disabler); this disables LG's firmware root checks, which may impede performance.
g. FORMAT DATA (Select WIPE, then FORMAT DATA, then select yes.)
Do NOT delete your OS, but you do need to FORMAT your data , not just "wipe" it this time. Otherwise you may get an encryption error when you boot up the first time. If you get any red mount errors, go back to the TWRP reboot menu and select reboot to recovery and try to FORMAT DATA again. Then, after successfully formatting...
h. Reboot – "Reboot Recovery" from TWRP reboot menu (choose to reboot back to Recovery). Now that the data partition has been formatted, TWRP needs to reload the recovery partition for usage. If you skip this step, when Magisk is installed again below, it may think that /data is still encrypted and set "preserve force encryption". This is also a good sanity check that LG encryption has been removed from /data.
i. Re-flash the latest stable Magisk zip again. (This is to make sure, due to Pie changes.)
j. Reboot – to System (NOW you are finally rebooting your phone! Until now this whole section has been done within TWRP.)
STRONG SUGGESTION: After successfully doing all this, when you finally boot back to LG Pie, install an app like this to easily facilitate rebooting to TWRP recovery in the future: Recovery Reboot. Allow it root privileges when asked by Magisk and put icon shortcut on your desktop.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ChazzMatt said:
Yes, we all know what it says!
---------- Post added at 10:55 PM ---------- Previous post was at 10:45 PM ----------
Need to update the encryption disabler and root check remover files, please. We found we needed newer versions for Pie.
Click to expand...
Click to collapse
Thank you for this. I did run into a problem dirty flashing due to Force Encryption, but i have confirmed clean flash works. I will update the package files you mentioned prior to publishing the link.
@ChazzMatt I cannot find a newer RCTD disabler release than 2017.
weakNPCdotCom said:
@ChazzMatt I cannot find a newer RCTD disabler release than 2017.
Click to expand...
Click to collapse
@JohnFawkes recently made root check remover for us.
@Zackptg5made the new encryption disabler.
See attachments at this link for both new encryption disabler and root check remover:
https://forum.xda-developers.com/showpost.php?p=79972563&postcount=107
Also here's @JohnFawkes thread link:
https://forum.xda-developers.com/lg-v30/development/stock-anykernel-3-rctd-remover-t3953692
so people can download themselves if they wish.
In most posts I include both attachment, credit and thread link when possible.
I'm using TWRP version 3.2.3-7. Is there a newer version that is required to flash Pie or is that one fine?
weakNPCdotCom said:
@ChazzMatt I cannot find a newer RCTD disabler release than 2017.
Click to expand...
Click to collapse
How do I download the new update?
Sent from my LG-H932 using XDA Labs
jsgraphicart said:
I'm using TWRP version 3.2.3-7. Is there a newer version that is required to flash Pie or is that one fine?
Click to expand...
Click to collapse
that version is perfect
BROKEN1981 said:
How do I download the new update?
Sent from my LG-H932 using XDA Labs
Click to expand...
Click to collapse
I just updated the FullStock link in the OP
jsgraphicart said:
I'm using TWRP version 3.2.3-7. Is there a newer version that is required to flash Pie or is that one fine?
Click to expand...
Click to collapse
No, that's what is recommended by our TWRP dev -- who also creates TWRP flashable zips.
Iam on liquid now, can I jump to stock via clean flash?
Thanks very much
The smoothest update ever for h932
weakNPCdotCom said:
that version is perfect
I just updated the FullStock link in the OP
Click to expand...
Click to collapse
Thank you!!
Sent from my LG-H932 using XDA Labs
Works great! thanks. There was no need to wipe nor format anything.
Almost done reinstalling all my apps, seems great! Thank you!
Anyone else having issues with pie? I'm getting system UI stops responding non stop.
Want to mention that this happens when first booting up to even when all apps are installed.
Successfully dirty flashed from stock 20s. Just remember to delete gatekeeper/lock database (instruction).
ReddotCleaner said:
Iam on liquid now, can I jump to stock via clean flash?
Click to expand...
Click to collapse
clean install using full stock zip will do just fine. follow #1 page instruction
BROKEN1981 said:
Anyone else having issues with pie? I'm getting system UI stops responding non stop.
Click to expand...
Click to collapse
please provide more information. did you come from stock 20s or other os? dirty/clean flashed? do you have any xposed things?
I did uninstall any xposed module and framework, and even delete all magisk module as I assume they will break on pie due incompatibility.
immns said:
snip.
Click to expand...
Click to collapse
I got everything set up. Don't know what the trouble was. I was clean flashing. I formatted data, reinstalled TWRP, installed 30D over 10 times.
Whatever the issue was, it's fixed now.
HOWEVER!!! T-Mobile hid where they put the boot animations. It's no longer in root-system-media.
If anyone finds the location, please post it.
Sent from my LG-H932 using XDA Labs
Related
I have combined the OnePlus 3 and OnePlus 3T TWRP threads into a single thread for the unified build.
Please visit:
https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391
I apologize for the inconvenience.
XDA:DevDB Information
Team Win Recovery Project for the OnePlus 3T, Tool/Utility for the OnePlus 3T
Contributors
jcadduono, Team Win
Source Code: https://github.com/jcadduono/android_device_oneplus_oneplus3t
Version Information
Status: Stable
Current Stable Version: 3.0.3-1
Stable Release Date: 2017-01-16
Created 2016-11-26
Last Updated 2017-01-22
Reserved
ONEPLUS FULL OTA ZIPS
You can flash these zips in TWRP to update your device or save yourself from a broken or soft-bricked state.
They are official zips distributed by OnePlus.
OxygenOS 3.5.3: https://s3.amazonaws.com/oxygenos.o...8_OTA_027_all_1611222319_884473ff95304c30.zip
OxygenOS 3.5.4: http://oxygenos.oneplus.net.s3.amaz...8_OTA_029_all_1612131737_17e7161d2b234949.zip
OxygenOS 4.0.0: http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_035_all_1612310259_2dc0c.zip
OxygenOS 4.0.1: http://otafsc.h2os.com/patch/amazon...ygen_28_OTA_037_all_1701041831_a2ba632ce9.zip
OxygenOS 4.0.2: http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_039_all_1701140132_400a7.zip
Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing one of the above full OTA zips in recovery.
Now if I have already rooted and installed a kernel will flashing TWRP wipe that stuff? I had to boot TWRP to flash SU and Kernel but did not flash it.
ghettopops said:
Now if I have already rooted and installed a kernel will flashing TWRP wipe that stuff? I had to boot TWRP to flash SU and Kernel but did not flash it.
Click to expand...
Click to collapse
TWRP will only wipe if you ask it to wipe something. OnePlus is using the usual separated recovery partition style which is great so you don't have to worry about TWRP breaking anything by flashing it.
jcadduono said:
TWRP will only wipe if you ask it to wipe something. OnePlus is using the usual separated recovery partition style which is great so you don't have to worry about TWRP breaking anything by flashing it.
Click to expand...
Click to collapse
So that means it doesn't use that new layout which includes dual A/B partitions right? If the only benefit of dual partitions is seamless updates, I guess the traditional layout is fine or even better.
Edit: Both this TWRP thread and the Tyranus kernel thread came out pretty quick, and seem very well documented and professional compared to some of the other Non Nexus device threads. I'm impressed. I just hope the threads stay uncluttered. Thank you.
So that I understand, separate recovery partition means that I can have both TWRP and Oxygen Recovery installed. Allowing me to get updates and install them through Oxygen Recovery while maintaining a TWRP recovery? Also is it just a matter of booting into them via fastboot?
Perhaps, the step between 2 and 3 should be go into the 'system>about' menu, keep tapping 'build number' to enable 'developers option', then go back out and into 'setting>developers option' and turn on 'OEM unlocking'. w/o this option turn on, you can do 'fastboot oem unlock'
And maybe perhaps, before doing anything, why not update the system via OTA first? If the OTA zip is OnePlus official, you should be able to flash it using stock recovery, doesn't it?
side note tip: if you wipe the data partition in TWRP, the default would be ext4, but the OP stock use F2FS. I think it may be wise to change that before wiping the data partition.
someone0 said:
Perhaps, the step between 2 and 3 should be go into the 'system>about' menu, keep tapping 'build number' to enable 'developers option', then go back out and into 'setting>developers option' and turn on 'OEM unlocking'. w/o this option turn on, you can do 'fastboot oem unlock'
And maybe perhaps, before doing anything, why not update the system via OTA first? If the OTA zip is OnePlus official, you should be able to flash it using stock recovery, doesn't it?
side note tip: if you wipe the data partition in TWRP, the default would be ext4, but the OP stock use F2FS. I think it may be wise to change that before wiping the data partition.
Click to expand...
Click to collapse
Done. Should now default to f2fs on data wipes as well. (redownload, I didn't change the version number)
Yes that is an option.
ghettopops said:
So that I understand, separate recovery partition means that I can have both TWRP and Oxygen Recovery installed. Allowing me to get updates and install them through Oxygen Recovery while maintaining a TWRP recovery? Also is it just a matter of booting into them via fastboot?
Click to expand...
Click to collapse
No, separate recovery partition means you can flash kernels and recoveries separately. It means recovery isn't part of the system boot image, which is an idiotic design of the Pixel phones that is hurting custom development for them. See example:
OnePlus 3T (and every other sane device):
boot partition = system boot image
recovery partition = recovery boot image
result = you can use twrp to flash custom roms! any issues = just try in twrp again!
Pixel:
boot partition = boot image with recovery ramdisk that loads system (???)
boot_a partition = the same thing as boot partition (??? again)
recovery partition = nowhere to be found
result = flash a bad custom rom? say goodbye to twrp!
Can't decrypt data so can't flash any files. Just updated to twrp in the op.
charlieb620 said:
Can't decrypt data so can't flash any files. Just updated to twrp in the op.
Click to expand...
Click to collapse
need recovery.log ... i'm guessing this is happening due to changing default partition type for data from ext4 to f2fs, might need to change it back
in the meantime, setting default back to ext4....redownload (again)
in the meantime, anyone crazy enough to test https://build.nethunter.com/test-builds/oneplus/kernel-nethunter-oneplus3t-marshmallow-test1.zip for me?
yes, this device is getting official Kali NetHunter support
Log
http://www87.zippyshare.com/v/7OhpiOv2/file.html
jcadduono said:
in the meantime, anyone crazy enough to test https://build.nethunter.com/test-builds/oneplus/kernel-nethunter-oneplus3t-marshmallow-test1.zip for me?
yes, this device is getting official Kali NetHunter support
Click to expand...
Click to collapse
Woah! Now official nethunter? I can test this Monday when I get the device. I would be surprised if we got copperhead OS too.
Another known issue: I can't get USB-OTG to work. Even in the StockOS, it seem disable by default and have to enable first, otherwise it won't provide power back out to the USB port. Not sure if this is related.
charlieb620 said:
Log
http://www87.zippyshare.com/v/7OhpiOv2/file.html
Click to expand...
Click to collapse
that's stock recovery....enable xda signatures and you will see how to get logs in my signature
someone0 said:
Another known issue: I can't get USB-OTG to work. Even in the StockOS, it seem disable by default and have to enable first, otherwise it won't provide power back out to the USB port. Not sure if this is related.
Click to expand...
Click to collapse
i'll look into it i guess, might be a /sys file we can trigger on init to enable it if you want to do the investigation for me
probably related to dash charge stupidity
jcadduono said:
that's stock recovery....enable xda signatures and you will see how to get logs in my signature
i'll look into it i guess, might be a /sys file we can trigger on init to enable it if you want to do the investigation for me
probably related to dash charge stupidity
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ONEPLUS A3000
---------- Post added at 05:58 AM ---------- Previous post was at 05:25 AM ----------
Ok started from scratch
Have latest twrp, root and net hunter kernel running.
charlieb620 said:
Sent from my ONEPLUS A3000
---------- Post added at 05:58 AM ---------- Previous post was at 05:25 AM ----------
Ok started from scratch
Have latest twrp, root and net hunter kernel running.
Click to expand...
Click to collapse
That screenshot seem like somebody is trying to run adb from within the android shell. I would just
'adb shell'
'su'
'cd /sdcard' or /tmp or whichever directory that's writable.
then run whatever command you need from there. Having another DOS windows open up is also a good idea. That way, one window is always running shell, and another is just DOS. so no confusion and no need to keep exiting shelf and get back in.
Fails to decrypt data. Here is logs from 3t 128gb model.
Black screen
Followed instructions to a "T" (haha)
Everything gets installed, i have root, but when i try to reboot into recovery/twrp - i just get a black screen. I can still turn the phone off, and start up the phone no problems, so its usable - but just not into twrp.
Any thoughts of suggestions?
hawki said:
Followed instructions to a "T" (haha)
Everything gets installed, i have root, but when i try to reboot into recovery/twrp - i just get a black screen. I can still turn the phone off, and start up the phone no problems, so its usable - but just not into twrp.
Any thoughts of suggestions?
Click to expand...
Click to collapse
How did you get root (superSU) installed w/o twrp?
BTW, you may have the same problem I had earlier, which is the stock OS is on version 3.5.1. You need to follow the instruction again, and flash recovery and boot into twrp.img After that, patch your OS to the latest via OTA, I think you need to re-root again after that.
just to be clear. Since I am already rooted am I just flashing twrp and swiping for Mods?
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
* Do NOT update to Pie yet if you wish to unlock bootloader in order to root.
For bootloader unlock/TWRP installation/root, T-mobile H932 users will need to temporarily downgrade to T-mobile H932 Nougat 10d and use @runningnak3d LAFPLOIT Instructions. After that you can update to more current firmware. Read the Root Sticky here if you wish to know more.
* ALSO do NOT update to LG stock Pie yet if you wish to run LOS-16 "Pie" custom ROMs -- at least for now. See REASON HERE. Stock Pie update conflicts with LOS-16 Pie, even if you downgrade back to stock Oreo. After stock Pie update, your phone has been permanently changed/degraded when going back to Oreo for custom ROMs. Using Permissive kernel can overcome some of those issues, but you have been warned.
T-mobile H932 is not (yet) compatible with the new "Android 10" LOS-17 custom ROMs. Those ROMs are still unfinished work in progress.
* If you've already updated to Pie with locked bootloader, either
* see @runningnak3d LAFPLOIT Instructions) for instructions on how to temporarily downgrade to T-mobile Nougat firmware to unlock bootloader, install TWRP and root
OR
* see post #3 to downgrade to Oreo firmware if you don't like Pie.
* If you have no desire to unlock bootloader and root, then see the full image KDZ below.
* OR your bootloader is already unlocked and you have TWRP installed (via @runningnak3d LAFPLOIT Instructions), then see the KDZ-based TWRP-flashable zips (ROM) listed below. If you have TWRP, then flash the TWRP-flashable zips, of course.
NOTE: After installing Pie, if you get weird lag,
* try this fix. Just make a backup in LG Bridge. Nothing else. Somehow CREATING the backup (but not actually using it to restore anything) re-sets some stuff in Pie, so it acts like it should? I know it sounds strange but it works. Thanks to @thefpspower for the tip!
* OR If that doesn't work or you don't have access to PC, try this: go to Settings> Restart & Reset> Reset App Preferences. Thanks to @HoussiLAM for that tip. Both may do the exact same thing, I've not experimented to see.
[H932][STOCK][PIE]LG V30 U.S. T-Mobile H932 H93230d_00_0902.KDZ
3.1GB
ONLY for T-mobile H932 V30 & V30+.
NOT for any other V30 variants! You will brick your phone if you try.
DOWNLOAD LINKS:
* LG Bridge MIRROR
(Thanks to @HueyT)
* Google Drive MIRROR
(Thanks to @xionbunny!)
* Android File Hosts MIRROR
* LG-Firmwares MIRROR
md5: eea31e240d28ee36efb3b3ee9a7533ec
TWRP FLASHABLE VERSION (ROM):
https://forum.xda-developers.com/lg-v30/development/stock-t-mobile-lg-v30-stock-collection-t3980701
(thanks to @weakNPCdotCom!)
ONLY for T-mobile H932 V30 & V30+.
NOT for any other V30 variants! You will brick your phone if you try.
md5: 6BC9C4AF2080003FF80587F98C2348E9
It's just stock KDZ but in TWRP-flashable version. Not debloated nor meant to be updated in the future. It's just a very convenient mechanism to have newer stock firmware instead of using dev patched LGUP to flash partitions, etc.
* Stable TWRP 3.3.1 is recommended by our TWRP dev for Pie.
TWRP-FLASHABLE NOTES:
For those who want to dirty flash -- if you have no problems, good for you.
If you find you need to clean flash in TWRP, then follow these steps:
a. Wipe Data – Factory Reset
b. Install – set storage to the External SD (if you have a microSD card) OR drag necessary files over from PC once in TWRP.
c. Install the Magisk 19.3 zip. (This is to give the encryption disabler root privileges)
d. Install @Zackptg5 Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler).
e. Install @JohnFawkes AnyKernel 3 RCTD Remover (root checker disabler); this disables LG's firmware root checks, which may impede performance.
f. FORMAT DATA (Select WIPE, then FORMAT DATA, then select yes.)
Do NOT delete your OS, but you do need to FORMAT your data , not just "wipe" it this time. Otherwise you may get an encryption error when you boot up the first time. If you get any red mount errors, go back to the TWRP reboot menu and select reboot to recovery and try to FORMAT DATA again. Then, after successfully formatting...
g. Reboot – "Reboot Recovery" from TWRP reboot menu (choose to reboot back to Recovery). Now that the data partition has been formatted, TWRP needs to reload the recovery partition for usage. If you skip this step, when Magisk is installed again below, it may think that /data is still encrypted and set "preserve force encryption". This is also a good sanity check that LG encryption has been removed from /data.
h. Re-flash the Magisk 19.3 zip again. (This is to make sure, due to Pie changes.)
i. Reboot – to System (NOW you are finally rebooting your phone! Until now this whole section has been done within TWRP.)
STRONG SUGGESTION: After successfully doing all this, when you finally boot back to LG Pie, install an app like this to easily facilitate rebooting to TWRP recovery in the future: Recovery Reboot. Allow it root privileges when asked by Magisk and put icon shortcut on your desktop.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also, please make another TWRP backup.
___________
Here's how to flash with LGUP:
----------------------------
UPGRADING T-MOBILE H932 V30/V30+ TO PIE KDZ FIRMWARE WITH LGUP
(This is if you don't care about installing TWRP and rooting.)
1) Go into download mode (power off completely, then hold volume up button while plugging in USB cable)
2) open patched LGUP and flash PIE KDZ either via UPGRADE (to keep your data, but see Note about TWRP) or via REFURBISH or PARTITION DL. If the latter, then in the pop up box "Select All". Use the attached patched LGUP in this post.
* NOTE: YOU CAN NOT USE LGUP "UPGRADE" IF YOU HAVE TWRP CUSTOM RECOVERY. LGUP "Upgrade" is like a manual OTA and is only for pure stock (but you can have unlocked bootloader). If you have TWRP custom recovery and want to use LGUP, then use PARTITION DL OR REFURBISH which will NOT keep your data and will wipe out TWRP and ability to root.
Or use the TWRP-flashable zip (ROM) instead of LGUP, which will keep your data and will keep TWRP.
3) IF your bootloader is unlocked, it will remain unlocked. If it's not unlocked, then you will just be updating to Pie -- but if you ever want root again you TEMPORARILY DOWNGRADE back T-mobile H932 Nougat and use @runningnak3d LAFPLOIT Instructions) to install TWRP -- at which point you would use the TWRP-flashable zips (ROMs) to update to Pie.
_________________
HOW TO INSTALL DEV PATCHED LGUP
0. UNINSTALL any prior LGUP version. Seriously. Go to Programs folder and delete the LGUP folder if you must.
1. DOWNLOAD THIS DUAL VERSION OF DEV PATCHED LGUP, made by @tecknight:
https://androidfilehost.com/?fid=11410963190603845019
(Or use attached file from bottom of this post. Thanks to @tecknight! Please go here and click the THANK BUTTON!)
2. Extract LGUP_DualMode.zip to a folder on your PC.
3. Browse into the folder and launch LGUP_Store_Frame_Ver_1_14_3.msi.
Follow the prompts to complete the install.
4. In that folder, right click and select "Run as Administrator" on "SetDev.bat" to set LGUP to developer mode. READ THAT AGAIN.
5. Launch LGUP using the desktop shortcut. NOT from folder icon!
As mentioned before, use UPGRADE, REFURBISH or PARTITION DL modes. REFURBISH and Partition DL are probably best.
WARNING: In LGUP do NOT go messing with modes not mentioned in these instructions. Especially do NOT use Chip Erase.
I don't care what anyone else tells you. If you listen to them, let them help you recover from messing up your phone.
https://9to5lg.com/lgup-1-15-manual-how-to-unbrick-restore-your-lg-devices-with-lgup/
3) ChipErase: Dangerous, This will erase IMEI/efs, Do not try this if you do not have a NV backup.
Click to expand...
Click to collapse
It's all fairly easy. Most people breeze right through this. But if you have any problems, go through this list:
Make sure you in download mode BEFORE opening the patched LGUP file.
This is at the top of the list as some people forget to do that. The remainder are in no particular order. If that doesn't work,
Try different USB port,
Try different USB cable,
Try different computer.
Reinstall LG mobile drivers on your PC.
Reinstall dev patched LGUP again.
Reboot the computer.
If you ask for help, that's the list of items we are going to give you anyway.
HOW TO DOWNGRADE BACK TO FULL STOCK OREO BECAUSE YOU DON'T LIKE PIE
(and either you don't have unlocked bootloader/TWRP installed and don't care about that OR you no longer want that)
OR to TEMPORARILY DOWNGRADE TO NOUGAT for TWRP Installation and Root.
1) DOWNLOAD FIRMWARE AND DEV PATCHED LGUP
* Download Oreo KDZ you wish to install. (Most recent Oreo KDZ 20s is at the top in that thread)
* For Nougat, download Nougat KDZ you wish to install.
* DOWNLOAD THIS DUAL VERSION OF DEV PATCHED LGUP, made by @tecknight:
https://androidfilehost.com/?fid=11410963190603845019
(Or use attached file from bottom of this post. Thanks to @tecknight! Please go here and click the THANK BUTTON!)
_________________
UNINSTALL ANY PRIOR LGUP YOU MAY HAVE INSTALLED.
2) INSTALL DEV PATCHED LGUP
1. Extract LGUP_DualMode.zip to a folder on your PC.
2. Browse into the folder and launch LGUP_Store_Frame_Ver_1_14_3.msi.
Follow the prompts to complete the install.
3. In that folder, right click and select "Run as Administrator" on "SetDev.bat" to set LGUP to developer mode
4. Launch LGUP using the desktop shortcut.
Choose Process : PARTITION DL or REFURBISH
----------------------------
3) DOWNGRADING T-MOBILE H932 V30/V30+ TO EARLIER OREO or NOUGAT KDZ FIRMWARE
1) Go into download mode (power off completely, then hold volume up button while plugging in USB cable)
2) open patched LGUP and flash OREO KDZ or NOUGAT (depending on your intention) to DL PARTITION mode. In the pop up box "Select All". Use the attached patched LGUP in this post.
You can also use REFURBISH mode, if you wish.
3) Master Reset (See method for Master Reset here); it is different from Factory Reset. Do NOT use anything else from that Frankenstein thread on H932!)
5) DONE.
It's fairly easy. Most people breeze right through this. But if you have any problems, go through this list:
Make sure you in download mode BEFORE opening the patched LGUP file.
This is at the top of the list as some people forget to do that. The remainder are in no particular order. If that doesn't work,
Try different USB port,
Try different USB cable,
Try different computer.
Reinstall LG mobile drivers on your PC.
Reinstall dev patched LGUP again, making sure the files are placed where they need to go (LG Electronics folder, etc).
Reboot the computer.
If you ask for help, that's the list of items we are going to give you anyway.
WARNING: In LGUP do NOT go messing with modes not mentioned in these instructions. Especially do NOT use Chip Erase.
https://9to5lg.com/lgup-1-15-manual-how-to-unbrick-restore-your-lg-devices-with-lgup/
3) ChipErase: Dangerous, This will erase IMEI/efs, Do not try this if you do not have a NV backup.
Click to expand...
Click to collapse
_________________
4) IF YOU NEED TO UNLOCK BOOTLOADER AND INSTALL TWRP (with temporary Nougat), PLEASE READ @runningnak3d T-MOBILE H932 LAFPLOIT INSTRUCTIONS.
Please update to most recent stock firmware IMMEDIATELY after bootloader unlock, TWRP installation, and root! See TWRP flashable zips above.
ROOT Your LG V30!
https://forum.xda-developers.com/lg-v30/how-to/root-v30-t3927154
Sticky everyone should read.
____________
EXTRAS
If you root with stock Pie KDZ (after unlocking bootloader in early Oreo), then you will need to flash Magisk modules or manually edit build prop to get root-enabled DTS, Equalizer, and lockscreen weather animations. Dual Speaker mode gives you audio directed at your face, besides the main downward facing speaker. High Impedance Mode give you more volume.
(NOTE: The TWRP flashable zips already have this, thanks to the devs who make them.)
* Fully enable LG DTS 3D stereo (root needed) + Equalizer
* LG V30 Lockscreen EXTRA Weather Animations Enabler
* DUAL SPEAKER MODE + HIM (High Impedance Mode)
SETTINGS
I know everyone has their own settings, but for new owners who want a reference point for all the various submenus and customization, I'll share screenshots of my settings. You can always change to what you like.
https://photos.app.goo.gl/NCm643Y7prJhDLaS2
Google Drive mirror added.
HueyT said:
http://pkg02.lime.gdms.lge.com/dn/downloader.dev?fileKey=FW47EIB7C2VLAH83E2B262S/H93230d_00_0902.kdz
H932 Pie out !!!!!
Click to expand...
Click to collapse
Downloading now. More mirrors coming.
Finally! Waiting long enough
I should have stock zips ready by tonight. debloated within a couple days.
YES!! FINALLY!! I'll keep an eye out for those flashable zips since I don't want to lose root.
I have an H931 converted to US998, I'm using the TMobile 20s port for US998 from the ROMs section because I'm using MetroPCS and I needed WiFi calling and all that. Would anyone know how I could update to pie without bricking?
dpwguenther said:
I have an H931 converted to US998, I'm using the TMobile 20s port for US998 from the ROMs section because I'm using MetroPCS and I needed WiFi calling and all that. Would anyone know how I could update to pie without bricking?
Click to expand...
Click to collapse
Be very careful!
You are talking about this port for US998:
https://forum.xda-developers.com/lg-v30/development/rom-lg-v30-t-mobile-stock-rom-20s-t3925486
Which @MicroMod777 made.
It was sort of a software port vs firmware (simplistic explanation).
You can probably post in that thread and request an update?
Please do not try to flash anything from a KDZ or TWRP-flashable zip in this thread to anything but T-Mobile H932.
I was just going over the flashing instructions and I'm just curious, why is it recommended to format data? Isn't this just the same as if I'm updating with the official OTA? I wouldn't have to format data to update that way. Also, I see there is a newer RTCD Remover than the one I have used since the beginning of the V30 root. I have always used the rtcd-disabler and no-verity-encrypt zips. Are they basically the same thing? I read that the person who updated without losing data used these files instead of the AnyKernel 3 RCTD Remover
jsgraphicart said:
I was just going over the flashing instructions and I'm just curious, why is it recommended to format data?
Isn't this just the same as if I'm updating with the official OTA?
Click to expand...
Click to collapse
Depends on WHICH flashing instructions you're referring to. You're mixing apples and oranges for some reason.
If you're updating with OTA, you are full stock -- you don't have TWRP custom recovery.
You don't have to reformat data here either if you're full stock. You just flash KDZ via Upgrade mode with LGUP.
Is that the way you wish to update to Pie?
If so, go back to full stock Oreo firmware via Refurbish or Partition DL and then you do NOT have to reformat data when upgrading to Pie. Once back in full stock Oreo firmware, just choose Upgrade mode for PIE.
Of course you'll lose all your data going back to full stock Oreo...
jsgraphicart said:
Also, I see there is a newer RTCD Remover than the one I have used since the beginning of the V30 root. I have always used the rtcd-disabler and no-verity-encrypt zips. Are they basically the same thing? I read that the person who updated without losing data used these files instead of the AnyKernel 3 RCTD Remover
Click to expand...
Click to collapse
Pie is vastly different. There's new Dev Patched LGUP, there's new encryption disabler and there's new root checker remover.
You have to use the ones listed in this thread or they wouldn't be listed.
ChazzMatt said:
Depends on WHICH flashing instructions you're referring to. You're mixing apples and oranges.
If you're updating with OTA, you are full stock -- you don't have TWRP custom recovery.
You don't have to reformat data here either if you're full stock. You just flash KDZ via Upgrade mode.
So, go back to full stock Oreo firmware via Refurbish or Partition DL and then you do NOT have to reformat data when upgrading to Pie.
Click to expand...
Click to collapse
I'm on stock but rooted with TWRP. But I'm still wondering why data NEEDS to be formatted. I'm reading it's an encryption thing. I've personally never messed with encryption so I'm wondering why this is causing issues with some but others appear to be upgrading fine without formatting.
jsgraphicart said:
I'm on stock but rooted with TWRP. But I'm still wondering why data NEEDS to be formatted. I'm reading it's an encryption thing. I've personally never messed with encryption so I'm wondering why this is causing issues with some but others appear to be upgrading fine without formatting.
Click to expand...
Click to collapse
You are not full stock. Please read my reply again.
LG encrypts, not you. We are disabling that. We've always disabled it.
Please quote specific instructions you are referring to and specific examples of these other people you're talking about.
Because you aren't making sense to me. KDZ was released today and there's no TWRP flashable zip yet.
If you flash full KDZ and want to reinstall TWRP yes you have to reformat, just like to did before when you installed TWRP!
Otherwise, wait for the TWRP flashable zip and see what that Dev requires.
ChazzMatt said:
You are not full stock. Please read my reply again.
Click to expand...
Click to collapse
I understand what you were saying. And since I am not full stock, it's recommended I format data, correct? I'm trying to figure out if I really need to wipe everything when flashing and if so, why I need to.
Step F:
f. FORMAT DATA (Select WIPE, then FORMAT DATA, then select yes.)
Do NOT delete your OS, but you do need to FORMAT your data , not just "wipe" it this time. Otherwise you may get an encryption error when you boot up the first time. If you get any red mount errors, go back to the TWRP reboot menu and select reboot to recovery and try to FORMAT DATA again. Then, after successfully formatting...
I just want to know why an encryption error comes up with this. Is it a Pie thing? I don't remember having this issue when updating to Oreo.
jsgraphicart said:
I understand what you were saying. And since I am not full stock, it's recommended I format data, correct? I'm trying to figure out if I really need to wipe everything when flashing and if so, why I need to.
Step F:
f. FORMAT DATA (Select WIPE, then FORMAT DATA, then select yes.)
Do NOT delete your OS, but you do need to FORMAT your data , not just "wipe" it this time. Otherwise you may get an encryption error when you boot up the first time. If you get any red mount errors, go back to the TWRP reboot menu and select reboot to recovery and try to FORMAT DATA again. Then, after successfully formatting...
I just want to know why an encryption error comes up with this. Is it a Pie thing? I don't remember having this issue when updating to Oreo.
Click to expand...
Click to collapse
You reformatted your data when you installed TWRP before. That's always been in the the WTF instructions.
So you have to do it again, since you're installing TWRP again over full KDZ.
The only thing that's changed are the files you are flashing (they're updated for Pie) and the fact you have to flash Magisk twice. Otherwise reformatting has ALWAYS been in the WTF instructions to install TWRP.
These instructions are based on Pie -- yes, but not the Data reformat part. That's always been there when flashing full KDZ and then reinstalling TWRP.
Now when flashing TWRP flashable zip, you can often dirty flash without reformatting data, but Devs still suggest it.
ChazzMatt said:
You reformatted your data when you installed TWRP before. That's always been in the the WTF instructions.
So you have to do it again, since you're installing TWRP again over full KDZ.
Click to expand...
Click to collapse
So the flashable zip will revert the recovery back to stock? Maybe I'm confused and maybe I'm wrong but I don't remember past zips doing that. I thought the devs took that part out. I have always just flashed the update, flashed magisk and the old rtcd-disabler and no-verity-encrypt zips and rebooted.
EDIT: Saw your edit. "Now when flashing TWRP flashable zip, you can often dirty flash without reformatting data, but Devs still suggest it." That's what I was asking because that's what I was planning on doing. But it was still recommended to format data
jsgraphicart said:
So the flashable zip will revert the recovery back to stock? Maybe I'm confused and maybe I'm wrong but I don't remember past zips doing that. I thought the devs took that part out. I have always just flashed the update, flashed magisk and the old rtcd-disabler and no-verity-encrypt zips and rebooted.
EDIT: Saw your edit. "Now when flashing TWRP flashable zip, you can often dirty flash without reformatting data, but Devs still suggest it." That's what I was asking because that's what I was planning on doing. But it was still recommended to format data
Click to expand...
Click to collapse
To maximize success, u better format data
jsgraphicart said:
So the flashable zip will revert the recovery back to stock? Maybe I'm confused and maybe I'm wrong but I don't remember past zips doing that. I thought the devs took that part out. I have always just flashed the update, flashed magisk and the old rtcd-disabler and no-verity-encrypt zips and rebooted.
EDIT: Saw your edit. "Now when flashing TWRP flashable zip, you can often dirty flash without reformatting data, but Devs still suggest it." That's what I was asking because that's what I was planning on doing. But it was still recommended to format data
Click to expand...
Click to collapse
Did you see this in post #2 of this thread? (See attached screenshot)
There's even a link to someone who dirty flashed (EU H930) Pie TWRP-flashable zip. It's just not recommended and if you have problems then you still have to reformat.
LG V30 VS996-30c ROMHi!
This Rom is 99% Stock. 3.2.3-7 TWRP should first be installed. Then you can install this Rom and have Pie with working TWRP.
WARNINGS!!!!!
Only for North American variants -- EXCEPT T-mobile H932. NOT for H930, H930G, H930D, H930DS!
This zip is created from the original KDZ. It contains almost the complete 30c 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 is 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 (only 2 extra lines added for DTS, full weather lockscreen)
Unrooted
System image 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
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]
LATEST ZIP
john-fawkes.com VS99630c.zip [Click to Download]
OLDER ZIPS
AFH ZIPS [Download]
John-fawkes.com [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 30b 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 occur, maybe you need to do a factory reset to start fresh*
Flash the 30c 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: 9.0 Pie
Android security patch level: 2019-09-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
Zip is live
General question for those who might know: is there any advantage (like Volte) for using stock vs996 on a Verizon network? I've got an open market us998 with a vs996 kernel.
Stuckurface said:
General question for those who might know: is there any advantage (like Volte) for using stock vs996 on a Verizon network? I've got an open market us998 with a vs996 kernel.
Click to expand...
Click to collapse
yea if your using verizon then its better to use the vs996 rom as you'll get verzion features such as vowifi volte and the verizon apps if you use any. im on ls998 on sprints network and when i flash the us998 rom i get no volte vowifi and i cant even get lte. it only stays at 3g
My service provider is straight talk and I'm on Verizon towers. I've noticed that I get faster data speeds if I use a Verizon ROM. I'm currently on the us998 ROM 9.0 pie. My data speeds are a little faster since I've updated from 8.0 but it's still not quite as fast as the Verizon ROM. So once you make this Verizon zip available I'll probably install it. Thanks @JohnFawkes
I'm on Total Wireless (VZ towers also)... I also recommend VS996 so that VOLTE and VOWIFI work properly. Not, previously, you could not disable/uninstall MyVerizon, otherwise these features would not work, so be aware of that. I don't know if we still need to do that with this version (someone could test).
I'm getting a, 404 file not found notice when I try to download. No rush.
Thanks for all your hard work.
nnjimmy59 said:
I'm getting a, 404 file not found notice when I try to download. No rush.
Thanks for all your hard work.
Click to expand...
Click to collapse
You must have overlooked the part where he says he's building the zip file now. It's not completed just yet. He'll have it available very soon
Zip is live guys
nnjimmy59 said:
I'm getting a, 404 file not found notice when I try to download. No rush.
Thanks for all your hard work.
Click to expand...
Click to collapse
Well I did say the zip wasn't uploaded yet....
Sorry, reading is hard.
nnjimmy59 said:
Sorry, reading is hard.
Click to expand...
Click to collapse
You must see some of the recent posts asking about WTF instructions.
After telling the one guy to please read the WTF instructions, he kept asking me questions clearly detailed in steps in the instructions.
"Does 3.2.3.7 TWRP work with this early Oreo KDZ?"
If the answer was no, I wouldn't list them together in necessary files to download, would I?
"Please give me link to download that KDZ"
It's IN the WTF instructions!
"Please give me link to the instructions."
OK, you're just trolling me now. He asked most of these questions IN the WTF thread.
____
NOW he says he's unlocked the bootloader and rooted, and wants to upgrade to Pie. I gave him link to Pie KDZ thread for his variant (which also has TWRP-flashable zip) and I've just ignored all follow-up questions, because again he's asking stuff I've written about in detail...
I'm not going to re-write everything because someone wants a "personalized" answer to some already-documented process hundreds of people have successfully completed just, following the written instructions...
I know, i see all the time. I don't know how you can be so patient with some of them.
By the way, thanks again for all your help. Both here and back in the Droid Turbo days.
---------- Post added at 01:56 AM ---------- Previous post was at 01:54 AM ----------
@JohnFawkes
Thank you so much for all your hard work. It's so much easier to have a TWRP zip to flash.
Really appreciate it.
booting up process is very slow. 5 minutes now and still on verizon logo/4 dots loading. Maybe i did something wrong.......i'll give it a little more time before i restore my backup. I flashed from us998 pie, it did the same thing. So i flashed vs996 oreo then fully booted up, then clean flashed this ROM, rebooted, and it seems to be stuck. Any ideas on where i went wrong?
Big_Bad_Beast said:
booting up process is very slow. 5 minutes now and still on verizon logo/4 dots loading. Maybe i did something wrong.......i'll give it a little more time before i restore my backup. I flashed from us998 pie, it did the same thing. So i flashed vs996 oreo then fully booted up, then clean flashed this ROM, rebooted, and it seems to be stuck. Any ideas on where i went wrong?
Click to expand...
Click to collapse
I have the same problem. Probably have to KDZ to VS996-30c REFURBISHED (or PARTITION-DL and select all PARTITIONS) to reset the partitions for VS996-30C (from US998-30B)
HueyT said:
I have the same problem. Probably have to KDZ to VS996-30c REFURBISHED (or PARTITION-DL and select all PARTITIONS) to reset the partitions for VS996-30C (from US998-30B)
Click to expand...
Click to collapse
It's possible but shouldnt be needed since all my flash able zips modify the same partitions
HueyT said:
I have the same problem. Probably have to KDZ to VS996-30c REFURBISHED (or PARTITION-DL and select all PARTITIONS) to reset the partitions for VS996-30C (from US998-30B)
Click to expand...
Click to collapse
do you happen to have a link to the kdz file? i cant find it anywhere
Big_Bad_Beast said:
do you happen to have a link to the kdz file? i cant find it anywhere
Click to expand...
Click to collapse
its in @ChazzMatt thread here on xda
Big_Bad_Beast said:
do you happen to have a link to the kdz file? i cant find it anywhere
Click to expand...
Click to collapse
https://forum.xda-developers.com/lg-v30/development/vs996-lg-v30-vs99630a000704arb00-kdz-t3952254
Has anyone successfully dirty flashed the 30C ZIP over their 20K Oreo? Would rather not try until others verify there aren't problems with this.
Hi all. Hope you are good and safe from Covid-19.
If you like TWRP as your recovery and want to keep root access as well, I am going to show you how to do that. Because if you take the stock boot.img and patch it via magisk, you will lose TWRP as your recovery and if you flash TWRP then you will lose root access. For the advance users, they probably already know how to do this but I haven't seen any guides so I am creating one myself.
Disclaimer:
I am a Textile engineer and do not have the slightest idea about computer engineering but my passion for computers and gadgets has taught me all this.
So, if anything happens to your device, it's not on me. I have done this on my device and it worked, so I am sharing this knowledge with you guys.
Let's cut to the chase and start our work:
Before we start, I am hoping you have your bootloader unlocked and have previous experience on flashing roms.
Step 1: Installing Stock/Xiaomi.EU/Custom rom
Go ahead and install one for your favorite roms from the threads. Luckily, Poco F3 has so many roms to choose from and they're all good.
Step 2: Installing magisk.apk
Install Magisk.apk from here
Step 3: Installing TWRP
Install TWRP from @vasishath's thread. (You'll lose root access if you had any).
Step 4: Backing up your boot image
- Boot into TWRP recovery and select backup.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Tick on boot and untick rest of the boxes.
- This will create 3 files in your TWRP folder on the phone. "boot.emmc.win" is your main file that you want to patch via magisk.
- After creating a backup of your boot image, boot into system normally.
Step 5: Patching the backed up boot image
- Open Magisk app and tap on install next to magisk.
- Now select "Select and Patch a file".
- Go ahead and select the boot.emmc.win file that is in your TWRP folder created earlier via TWRP backup.
- This is patch the boot.emmc.win and name it something like "magisk_patched-23000_randomalphanumeric.img"
- Rename the file via any file explorer to boot.img because something when the phone is plugged into the pc, your pc can't read the file. So, just to be safe, unplug the phone and re-plug to read the drive again.
- Copy this boot.img and take it to the folder where fastboot is installed/saved.
Final Step: Flashing the boot.img
- Reboot your phone to fastboot mode via pressing and holding the volume down + power buttons (or if you have custom roms installed and have the option to boot into fastboot mode directly).
- Once in fastboot mode, type following to flash the boot.img
fastboot flash boot boot.img
Click to expand...
Click to collapse
- once the flashing is done (in about 5-10 seconds), type the following:
fastboot reboot
Click to expand...
Click to collapse
Congratulations! you now have TWRP installed as your recovery and have root access as well. To verify this you should have the below screen in your magisk app
If my guide helped you in any way, please do like it as it motivates me to write more guides to take my time out from my busy work life.
Thanks.
Very detailed and comprehensive guide indeed, however I just unlocked my almost a week now. Initially, I have 3 choices on how I will run my device after unlocking bootloader.
Either I use XiaoMi.EU testing non-root, AOSP non-root or worse can scenario I'll root and run it on stock firmware.
No I do not think that F3 users are lucky, instead I think the reality is the trend of really good coders and programmers have past. You think F3 have a huge variety of custom roms to choose? 90%+ above are based on AOSP, which I don't understand why we have 10+ AOSP roms, with only 1-2 difference. It's such a waste of time. They are only interested in making new custom roms, never in maintaining them. Always abandon project and go missing after a while. This generation is full of "enthusiasts", "wanna-be" developers most noticeable after POCO entered India's market. You can try search in YouTube, poco f3 then you will get 70-80% of tech/mobile influencers with tons of guides. The sad part is, most of them are literally talking about the same stuff, and what I hate the most they love to decorate their website with tons of ads.
Hi,
thanks for your guide I really needed it because I already have custom ROM, root, Magisk... but TWRP I used to start it from the computer every time I needed it.
If I follow your method I don't lose the installed apps and my data, right?
pegasoc said:
Hi,
thanks for your guide I really needed it because I already have custom ROM, root, Magisk... but TWRP I used to start it from the computer every time I needed it.
If I follow your method I don't lose the installed apps and my data, right?
Click to expand...
Click to collapse
No, you won't lose your data.
regedit12345 said:
...
Step 3: Installing TWRP
Install TWRP from @vasishath's thread. (You'll lose root access if you had any).
...
Click to expand...
Click to collapse
Hi,
to be sure I understand correctly, at point 3 where there is to install the TWRP I always started the TWRP from PC I do not have to do it again, right?
pegasoc said:
Hi,
to be sure I understand correctly, at point 3 where there is to install the TWRP I always started the TWRP from PC I do not have to do it again, right?
Click to expand...
Click to collapse
Yeah, once you boot from pc and "install current twrp", you dont have to do it again.
When i have bootloader unlocked how do i flash xiaomi.eu rom without twrp installed?
__halvar__ said:
When i have bootloader unlocked how do i flash xiaomi.eu rom without twrp installed?
Click to expand...
Click to collapse
You have to install TWRP through fastboot, look for a guide, there's a couple
still works like a charm
thank you for the guide!
I already have xiaomi.eu and TWRP installed but my first time installing Magisk on this device.
do I have to wipe /data ?
katcj said:
thank you for the guide!
I already have xiaomi.eu and TWRP installed but my first time installing Magisk on this device.
do I have to wipe /data ?
Click to expand...
Click to collapse
No. Just install magisk.apk and patch the boot image extracted via twrp and go ahead and flash it.
regedit12345 said:
No. Just install magisk.apk and patch the boot image extracted via twrp and go ahead and flash it.
Click to expand...
Click to collapse
PLEASE stop patching the BOOT image
.
.
.
DIRECT INSTALL (Recommendend) is the option on your screen.
that's all you needed.
and your TWRP is OLD
please, use new officel TWRP from
and there you will find the correct instructions for installing TWRP
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
Thank you for taking your time to contribute value to community resources!
There seem to be so many different guides and methods
I followed nebrassy's guide for TWRP
0. miflash latest stock -> flash desired rom
1. fastboot boot twrp.img (3.6 official)
2. advanced -> flash current twrp (now its permanent)
3. flash latest magisk alpha zip (usb otg or put in storage pre fastboot)
4. reboot.. launch magisk app -> update -> direct install -> reboot
5. profit
Hello. Could you help me with rooting my phone, please?
I'm on Xiaomi.eu 21.12.8 (the last android 12 weekly update). I tried flashing Magisk.zip with the TWRP but it didn't work at all.
It's like I never flashed it. So I decided to try your method to see if it would go any different, and it didn't.
I could root Evolution X (android 12), ArrowOS 11 and 12 with this method of flashing Magisk.zip on TWRP but I can't understand why it didn't worked on Xiaomi.eu 21.12.8. I could even root Xiaomi.eu 21.9.17, which was the last android 11 weekly update.
Desperate, I went to the "advanced" section of TWRP and there was an option of "Flash magisk alpha" and it ended up rooting the phone but I don't understand why the previous 2 methods didn't work.
Could you help me understand that?
Root only works with magisk canary in Android 12
Latest Magisk Canary release adds support for Android 12, drops MagiskHide
The newest update on Magisk's "bleeding edge" canary release channel brings in support for Android 12 and the new Zygisk feature. Read on!
www.xda-developers.com
Thank you!!
Using canary worked on xiaomi.eu, although, I still cannot understand why using the magiskv23.apk can root aosp android 12 rom but not xiaomi.eu android 12, if you could explain me, I'd greatly appreciate it.
Also, canary seems to have the magiskhide function removed, is there a way to hide it for certain apps (banks, mostly) with a module or is it disabled permanently now?
Wiilsoonj said:
Thank you!!
Using canary worked on xiaomi.eu, although, I still cannot understand why using the magiskv23.apk can root aosp android 12 rom but not xiaomi.eu android 12, if you could explain me, I'd greatly appreciate it.
Also, canary seems to have the magiskhide function removed, is there a way to hide it for certain apps (banks, mostly) with a module or is it disabled permanently now?
Click to expand...
Click to collapse
yes the new "hide" is zygisk in the options
How do I flash the canary version of magisk though? I have an A12 rom on my F3. I can't flash it in TWRP as I can't mount any partitions to see the file. And I can't flash it via adb sideload as it crashes my TWRP immediately.
Any advice or suggestions? Thanks.
Aceyalone said:
How do I flash the canary version of magisk though? I have an A12 rom on my F3. I can't flash it in TWRP as I can't mount any partitions to see the file. And I can't flash it via adb sideload as it crashes my TWRP immediately.
Any advice or suggestions? Thanks.
Click to expand...
Click to collapse
Either use usb OTG.
Aceyalone said:
How do I flash the canary version of magisk though? I have an A12 rom on my F3. I can't flash it in TWRP as I can't mount any partitions to see the file. And I can't flash it via adb sideload as it crashes my TWRP immediately.
Any advice or suggestions? Thanks.
Click to expand...
Click to collapse
You can use this TWRP.
Download this: twrp-3.6.0_11-v3.2_A12-alioth-skkk.img
From this link: https://androidfilehost.com/?w=files&flid=322193
This one is able to see the internal storage of the phone with android 12. But you need to remove your screen lock to do so, you must not have a password set up so TWRP can see your internal storage, then just flash magisk normally and afterwards set up your screen lock again. Everytime you want to see the internal storage, disable screen lock. Also, you could follow the tutorial in the first post, but instead of making a backup of boot with TWRP, just use boot.image from the desired ROM, patch it with magisk and then flash the boot using adb.
Hope it helps.