Hey guys, I i see that JasmineROM has some instructions on updated using an Installrom.sh file or something, when I updated to 23B (SkyDragon 3.0.0 to be exact) I just KDZ'd back to 10c, rooted and flashed a bump'd TWRP and than flashed the SkyDragon 3.0.0 full on top and everything seems to work. I have since tried a few different roms and am now on SlimLP, but I want to know if this is an ok way to upgrade? Is there any reason to use the JasmineROM's creator (I forget his name, sorry) update method with the installrom.sh over this method?
The InstallROM.sh method was for JasmineROM v5.0. 6.0 is just a normal flashable zip. Just flash it from TWRP, doesn't matter what you're on currently.
roirraW "edor" ehT said:
The InstallROM.sh method was for JasmineROM v5.0. 6.0 is just a normal flashable zip. Just flash it from TWRP, doesn't matter what you're on currently.
Click to expand...
Click to collapse
Okay, just to be sure, if I'm on stock 10c but rooted and twrp'd than I can just flash the jasmine ROM 6.0 and everything is good?
r3xx3r said:
Okay, just to be sure, if I'm on stock 10c but rooted and twrp'd than I can just flash the jasmine ROM 6.0 and everything is good?
Click to expand...
Click to collapse
i havent been following this closely, but i didnt think you would be able to flash up ever without installing the base first.
unless something changed, you would need to install the 5.0 base first, then you could flash 6.0, but you should verify, there may have been new developments i wasnt privy to.
r3xx3r said:
Okay, just to be sure, if I'm on stock 10c but rooted and twrp'd than I can just flash the jasmine ROM 6.0 and everything is good?
Click to expand...
Click to collapse
Yes. Honest. Triply sure. @hsbadr is additionally very complete and accurate in his instructions for flashing his ROMs, along with caveats if there were any, which there are none for 6.0.
bweN diorD said:
i havent been following this closely, but i didnt think you would be able to flash up ever without installing the base first.
unless something changed, you would need to install the 5.0 base first, then you could flash 6.0, but you should verify, there may have been new developments i wasnt privy to.
Click to expand...
Click to collapse
6.0 is the new base (of 23C). 5.0 of course, was 23B. 6.0 includes every single .img file from 100% complete stock 23C except it also has the 12B aboot.img and bump'd 23C kernel instead of the originals (for 23C) of those. The 6.0 zip includes all of said .img files and then additionally includes the file/folder structure necessary to modify them to mold them into what becomes debloated and tweaked JasmineROM 6.0.
This is why I was able to simply take the .img files out of his 6.0 zip and use them with his installROM.sh script from 5.0 in order to install complete 100% stock (system) 23C in an all-in-one working manner through TWRP's Terminal Command option in the Advanced menu since I like to debloat and tweak my own way. I manually flashed SuperSU.zip since obviously the stock .img files don't include root, and since I don't use anything from the 6.0 zip except the .img files, and it's the additional files in his 6.0 zip which do all the debloating and tweaking.
Sorry for repeating myself.
It's really great the way he's done it since anyone can (assuming having a reasonably up to date TWRP) get 23C installed.
Personally, I think Verizon is just having fun with us at this point.
roirraW "edor" ehT said:
Yes. Honest. Triply sure. @hsbadr is additionally very complete and accurate in his instructions for flashing his ROMs, along with caveats if there were any, which there are none for 6.0.
6.0 is the new base (of 23C). 5.0 of course, was 23B. 6.0 includes every single .img file from 100% complete stock 23C except it also has the 12B aboot.img and bump'd 23C kernel instead of the originals (for 23C) of those. The 6.0 zip includes all of said .img files and then additionally includes the file/folder structure necessary to modify them to mold them into what becomes debloated and tweaked JasmineROM 6.0.
This is why I was able to simply take the .img files out of his 6.0 zip and use them with his installROM.sh script from 5.0 in order to install complete 100% stock (system) 23C in an all-in-one working manner through TWRP's Terminal Command option in the Advanced menu since I like to debloat and tweak my own way. I manually flashed SuperSU.zip since obviously the stock .img files don't include root, and since I don't use anything from the 6.0 zip except the .img files, and it's the additional files in his 6.0 zip which do all the debloating and tweaking.
Sorry for repeating myself.
It's really great the way he's done it since anyone can (assuming having a reasonably up to date TWRP) get 23C installed.
Personally, I think Verizon is just having fun with us at this point.
Click to expand...
Click to collapse
thanks for explaining.
one question though, where did the unrooted system file come from?
root is required to pull the system, therefore its rooted by default.
just curious,
thanks
Thank you guys for the great explanations. I am still getting used to the G3. My old Galaxy S4 from T-mo was very different. I have another question now. If I want to run an AOSP rom, like SlimLP, would anything be different if I flashed JasmineROM 6.0 than SlimLP?? Do the basebands or anything like that change from 23b to 23c and would they stick between roms??
bweN diorD said:
thanks for explaining.
one question though, where did the unrooted system file come from?
root is required to pull the system, therefore its rooted by default.
just curious,
thanks
Click to expand...
Click to collapse
Anytime! I've wondered the same thing. I definitely didn't have SuperSU in my app drawer before I rebooted to TWRP and flashed SuperSU.zip. I meant to do that anyway but it's just as well I find out for sure that SuperSU wasn't installed. Perhaps the system.img is technically rooted but the SuperSU app was moved from system to data before pulling the image. So binaries, etc are still in the system.img but without the SuperSU app it's effectively not rooted.
But if that were the case, I could've merely installed SuperSU from the Play Store. I didn't try that so I won't know if that's the case until I have time to play with the phone more.
@HolyAngel, can you confirm if this is how the system.img by itself for 23A/B/C doesn't "appear" rooted?
If we had the KDZ, of course, then it would be a different story since we can extract the totally pure system.img as of course you already know (just saying for other reader's benefit).
r3xx3r said:
Thank you guys for the great explanations. I am still getting used to the G3. My old Galaxy S4 from T-mo was very different. I have another question now. If I want to run an AOSP rom, like SlimLP, would anything be different if I flashed JasmineROM 6.0 than SlimLP?? Do the basebands or anything like that change from 23b to 23c and would they stick between roms??
Click to expand...
Click to collapse
You're welcome! I understand. Came from the S3 and S2 before this myself. At least KDZ is reminiscent of Odin, although it sure was easier to get custom recovery and root installed with being able to flash custom recovery from Odin. I've wondered about building KDZ packages of custom recoveries, although it'd have to flash the 12B aboot.img and a bump'd kernel, too. Since we can extract KDZs, hopefully we can create them, too. Don't know how hard it is to get LG Mobile Tool 2014 to flash custom KDZs, though, or for the phone to accept them.
Sorry I digressed. So far, AOSP/CM ROMs need 12B's modem, they won't work with 23A/B/C's modems. You can get the 12B modem from @bweN diorD 's sticky thread in the General section.
So far all 23A/B/C ROMs flash the appropriate modem. Just backup the modem when you do nandroid backups.
Sent from my VK810 4G
roirraW "edor" ehT said:
Anytime! I've wondered the same thing. I definitely didn't have SuperSU in my app drawer before I rebooted to TWRP and flashed SuperSU.zip. I meant to do that anyway but it's just as well I find out for sure that SuperSU wasn't installed. Perhaps the system.img is technically rooted but the SuperSU app was moved from system to data before pulling the image. So binaries, etc are still in the system.img but without the SuperSU app it's effectively not rooted.
But if that were the case, I could've merely installed SuperSU from the Play Store. I didn't try that so I won't know if that's the case until I have time to play with the phone more.
@HolyAngel, can you confirm if this is how the system.img by itself for 23A/B/C doesn't "appear" rooted?
If we had the KDZ, of course, then it would be a different story since we can extract the totally pure system.img as of course you already know (just saying for other reader's benefit).
You're welcome! I understand. Came from the S3 and S2 before this myself. At least KDZ is reminiscent of Odin, although it sure was easier to get custom recovery and root installed with being able to flash custom recovery from Odin. I've wondered about building KDZ packages of custom recoveries, although it'd have to flash the 12B aboot.img and a bump'd kernel, too. Since we can extract KDZs, hopefully we can create them, too. Don't know how hard it is to get LG Mobile Tool 2014 to flash custom KDZs, though, or for the phone to accept them.
Sorry I digressed. So far, AOSP/CM ROMs need 12B's modem, they won't work with 23A/B/C's modems. You can get the 12B modem from @bweN diorD 's sticky thread in the General section.
So far all 23A/B/C ROMs flash the appropriate modem. Just backup the modem when you do nandroid backups.
Sent from my VK810 4G
Click to expand...
Click to collapse
Yea, most likely the su app wasn't system, and you just need to re-install it.
Related
[VK810.4G] [altev] [ViKtory810ROM] official 36B 5.0.2 & 24A 4.4.2 - updated 8/30/2016
First, the thanks:
@AndroidFileHost for the Android File Host website and especially their changes allowing for the reorganization of already uploaded files.
@KyPbP for letting us know it's availability and giving the link to download the VK810 35A_08 KDZ.
@hsbadr for giving me permission to kang his Verizon G3 VS985 JasmineROM 7.0 update script for this use.
@rant for giving a link to the official Verizon PDF detailing this release.
@Chainfire for SuperSU!
@Hnk1 for continued support, advise and ideas, and for experimenting to find out how to root 35A_08 without downgrading. His two updated guides:[VK810][Altev][Guides][Information] Root Recovery Repair [4.4.2][5.02]
[VK810][ROOT][Lollipop][5.02] No downgrade requiredDebloat scripts that you can flash in TWRP or CWM (ClockworkMod Recovery) after flashing the ROM and SuperSU.zip are located in the second post.
Donator's Thanks:
@middle_road
@k3ttle
@JBurch/cry
@habatchaNow
@b52apl
@Protonus
@Carolinaherps
@thvoicwethin
@random.mannix
@raghublr
@megadrive007
Thank you!!!
Just a fair warning, not trying to sound like a you know what, but no Xposed-related comments in this thread. If anyone wishes to post a new thread in General for what Xposed experiences they have under Lollipop, that would be a good idea.
Disclaimer: The usual. I am not responsible for what you do with this nor what happens when you do whatever you do with it.
Instructions to flash:
0. If you haven't previously updated TWRP to the latest version (v2.8.7.0 still as of January 3rd, 2016), do so by:
0A. Download TWRP v2.8.7.0 from http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-7-0-t3150812
Credit and thanks @AndroidUser00110001 !
0B. (in TWRP v2.7.0.1) choosing "Install", navigating to where you downloaded the TWRP v2.8.7.0 zip (probably in internal storage in the Download folder), and choosing to flash the zip.
1. Download my ROM from my section on Android File Host at https://www.androidfilehost.com/?w=files&flid=32160. I use ADM "Advanced Download Manager" from the Play Store at https://play.google.com/store/apps/details?id=com.dv.adm&hl=en, especially for downloading larger files like ROMs.
2. Check the MD5 Hash of the ROM zip:
2A. Copy (to the clipboard) the MD5 hash that I have in the filename of the ROM zip you downloaded in step 1 above.
2B. Install @scary alien 's "AFV File Verifier for Android" from the Play Store at https://play.google.com/store/apps/details?id=sa.afvx&hl=en.
2C. Run the AFV app.
2D. Choose "Input checksum for comparison".
2E. Paste the MD5 hash previously copied to the clipboard in step 2A above.
2F. Choose "Select File".
2G. Navigate to where you have the ROM zip.
2H. Long-press on the ROM zip and choose "Calc MD5 Checksum".
2I. When it's done calculating the MD5 hash of the ROM zip, it'll automatically compare it to the MD5 hash you pasted in step 2E above.
If the hashes match, the downloaded ROM zip is non-corrupt. If the hashes don't match, you have to re-download the ROM zip.
3. Optionally download one or more of my debloat zip files in the third post below. If you don't flash my "no OTA" debloat zip, then don't take any OTAs you get offered if there are ever any more, or you might get soft bricked, which I won't go into recovering from here.
4. (Not needed for 24A KitKat 4.4.2 pre-rooted ROM) Download the latest non-beta SuperSU zip from http://download.chainfire.eu/supersu (XDA thread with this link at http://forum.xda-developers.com/showthread.php?t=1538053) or the latest Beta version from a link in @Chainfire 's thread at http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133.
5. Copy/move anything you want to keep from internal storage like the files you downloaded in the previous sections.
6. I strongly suggest wiping everything from TWRP (Data, Cache, System, Dalvik and Internal Storage). Wiping all of these things, especially if you use my debloat zip(s) will clear up garbage/folders that were left behind by previous bloat.
7. Flash my ROM.
8. (Not needed for 24A KitKat 4.4.2 pre-rooted ROM) Flash SuperSU.zip (downloaded in step 4 above). This step is VERY IMPORTANT on 35A Lollipop 5.0.2 and above if you want to get back into custom recovery without having to re-flash a stock ROM and go through the whole process again.
9. Optionally flash one or more of my debloat zip files. If you don't flash my "no OTA" debloat zip, then don't take any OTAs you get offered if there are ever any more, or you might get soft bricked, which I won't go into recovering from here.
Flashing the debloat zip(s) before the first boot of the ROM will give the advantage of never having the data/cache entries or internal storage folders for the debloated apps created, the latter is why I recommend a wipe of internal storage.
In order to get back into TWRP/custom recovery from rooted Lollipop 35A 5.0.2 or above ROMs (not needed for 24A KitKat 4.4.2 pre-rooted ROM):
1. Download the corresponding "aboot only" (aboot is the bootloader) found in the same place to download as my ROM zip. Corresponding means if you installed the latest 36B VK810 stock ROM, then download the 36B VK810 aboot zip file.
2. Download the 4.2.2 aboot package from http://forum.xda-developers.com/showpost.php?p=54533937&postcount=2
Credit and thanks @paperWastage !
The download link is about three quarters down in that second post.
3. Move this aboot.4.2.2.img file into the top of the internal storage (meaning, not in a folder).
4. In Terminal Emulator type (make sure no typos, or can copy/paste to be sure):
Code:
su
dd if=/sdcard/aboot.4.2.2.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
5. You can now reboot into recovery via your preferred method.
6. Once you're finished in TWRP, you need to re-flash the newer aboot zip downloaded in step 1 above. If you forget, the ROM won't boot. You should be able to long-press the power button to force the device off, then use the manual method to get back into TWRP mentioned in step 22 in the previous section above. Re-flash the newer aboot zip, then reboot from TWRP and the ROM will boot.
You can alternatively dirty flash my ROM zip instead of just the aboot. You'd have to re-flash SuperSU.zip, any debloat zips and Xposed if you had before, too.
Reserved
LG G Pad 8.3 & Verizon LG G3 DEBLOAT SCRIPTS - updated 4-6-2016
These will work with both the VK810 Verizon LG G Pad 8.3 35A through 36B, and VS985 Verizon LG G3 23C up through 47A. They will NOT work on KitKat for debloating apps yet, they will work for various other non-app files I debloat. I'm working on updating them.
Again, thanks to @hsbadr for giving me permission to kang "anything I want" for this use.
Thanks to @abced123 for figuring out the root/sbin/lge_fota file is what was still allowing OTAs even after LGFOTA.apk was removed.
Thanks to @alfadon for making me aware of the two additional files that needed removed (at least on the VS985) in order to stop OTAs.
Thanks to @xdabbeb for his VS985 v2.0 ROM, with which I made a comparison to find things I could still debloat that I hadn't yet. If he didn't already figure out what we could lose without loss of functionality, this wouldn't have been possible.
INSTRUCTIONS: Backup in TWRP or read list of files deleted and make sure you don't mind, first. Debloat scripts that you can flash in TWRP after flashing the ROM and SuperSU.zip are located in my debloat script section on Android File Host.
@joshua70448 was kind enough to make an online tool to automate making custom debloat zips according to what a user selects to debloat:
joshua70448 said:
I put together an online tool that lets you pick exactly which files to remove in a debloat script and builds the flashable ZIP and MD5 files for you (as well as a full list of deleted files). Check it out at LG G3 VS985 (Verizon) and G Pad 8.3 VK810 (Verizon) debloat generator.
Click to expand...
Click to collapse
Please thank him at his original post here and take note of his other Android tools in his signature: http://forum.xda-developers.com/showpost.php?p=66192766&postcount=238.
Note that these are most effective if flashed before booting the ROM for the first time, or after a data/cache/Dalvik/internal storage wipe since the data, etc for them are built on first boot but if you flash the debloat script(s) before booting the ROM, then it never gets a chance to create the data and cache for them.
That said, it's completely fine to flash them any time.
Which package removes what (additionally there is a "all" zip that removes all of these EXCEPT it still has OTA and doesn't remove the apps affected by Xposed - you'll need to flash the "no OTA" zip separately). I remove all except for OTA, so I'm aware when OTAs arrive if I don't see notice about it here first, and so I can capture the OTA files. ):
Amazon
delete_recursive("/system/app/AmazonIMDb");
delete_recursive("/system/app/AmazonKindle");
delete_recursive("/system/app/AmazonMobile");
delete_recursive("/system/app/AmazonWidget");
delete_recursive("/system/priv-app/AmazonAppstore");
delete_recursive("/system/priv-app/AmazonAudible");
delete_recursive("/system/priv-app/AmazonKindle");
delete_recursive("/system/priv-app/AmazonMobile");
delete_recursive("/system/priv-app/AmazonMP3");
Google
delete_recursive("/system/app/Books");
delete_recursive("/system/app/Chrome");
delete_recursive("/system/app/CloudPrint");
delete_recursive("/system/app/Drive");
delete_recursive("/system/app/Gmail2");
delete_recursive("/system/app/Hangouts");
delete_recursive("/system/app/Maps");
delete_recursive("/system/app/Music2");
delete_recursive("/system/app/Newsstand");
delete_recursive("/system/app/NewsstandStub");
delete_recursive("/system/app/PlayGames");
delete_recursive("/system/app/PlusOne");
delete_recursive("/system/app/Street");
delete_recursive("/system/app/talkback");
delete_recursive("/system/app/Videos");
delete_recursive("/system/app/YouTube");
delete_recursive("/system/priv-app/Velvet");
delete_recursive("/system/tts/google/es-es-x-ana-phone-hmm");
delete_recursive("/system/tts/google/es-us-x-sfb-phone-hmm");
LG Apps
delete_recursive("/system/app/elt_test");
delete_recursive("/system/app/GnssAirTest");
delete_recursive("/system/app/GnssLogCat");
delete_recursive("/system/app/GnssPosTest");
delete_recursive("/system/app/GnssTest");
delete_recursive("/system/app/LGHome_Theme_Marshmallow");
delete_recursive("/system/app/LGLW_Feather");
delete_recursive("/system/app/LGLW_PolarBear");
delete_recursive("/system/app/LGLW_Prince");
delete_recursive("/system/app/LGNotebook");
delete_recursive("/system/app/LGSearchWidgetProvider");
delete_recursive("/system/app/LGSpringCleaning");
delete_recursive("/system/app/LGVZWHelp");
delete_recursive("/system/app/LGWernickeManager");
delete_recursive("/system/app/OBDM_Permissions");
delete_recursive("/system/app/WfdService");
delete_recursive("/system/media/shutdownanimation.zip");
delete_recursive("/system/priv-app/BioITPlatform_SDService");
delete_recursive("/system/priv-app/LGActionManager");
delete_recursive("/system/priv-app/LGConciergeBoard");
delete_recursive("/system/priv-app/LGCover");
delete_recursive("/system/priv-app/LGEasyHome");
delete_recursive("/system/priv-app/LGFavoriteContactsWidget");
delete_recursive("/system/priv-app/LGFormManager");
delete_recursive("/system/priv-app/LGLIA");
delete_recursive("/system/priv-app/LGLW_MultiPhoto");
delete_recursive("/system/priv-app/LGMemo");
delete_recursive("/system/priv-app/LGMusicWidget");
delete_recursive("/system/priv-app/LGMyGuide");
delete_recursive("/system/priv-app/LGMyWellness");
delete_recursive("/system/priv-app/LGNLPService");
delete_recursive("/system/priv-app/LGPCSuite");
delete_recursive("/system/priv-app/LGPolarisOffice");
delete_recursive("/system/priv-app/LGQMemoplus");
delete_recursive("/system/priv-app/LGQVoiceplus");
delete_recursive("/system/priv-app/LGThinkFreeViewer");
delete_recursive("/system/priv-app/LGTTS");
delete_recursive("/system/priv-app/LGVoiceCommand");
delete_recursive("/system/priv-app/LGVZWHelp");
delete_recursive("/system/priv-app/LIAInformant");
delete_recursive("/system/priv-app/LIAS4URecommender");
delete_recursive("/system/priv-app/LocationAgent");
delete_recursive("/system/priv-app/Maluuba_QVoice");
delete_recursive("/system/priv-app/SSO_P3");
LG Audio
delete_recursive("/system/media/audio/effects/KeypressDelete.ogg");
delete_recursive("/system/media/audio/effects/KeypressReturn.ogg");
delete_recursive("/system/media/audio/effects/KeypressSpacebar.ogg");
delete_recursive("/system/media/audio/effects/KeypressStandard.ogg");
delete_recursive("/system/media/audio/effects/VideoRecord.ogg");
delete_recursive("/system/media/audio/ui/af_failure.ogg");
delete_recursive("/system/media/audio/ui/af_success.ogg");
delete_recursive("/system/media/audio/ui/Audible_Selection.ogg");
delete_recursive("/system/media/audio/ui/camera_click.ogg");
delete_recursive("/system/media/audio/ui/camstart.ogg");
delete_recursive("/system/media/audio/ui/camstop.ogg");
delete_recursive("/system/media/audio/ui/circle_lock.ogg");
delete_recursive("/system/media/audio/ui/circle_unlock1.ogg");
delete_recursive("/system/media/audio/ui/circle_unlock2.ogg");
delete_recursive("/system/media/audio/ui/circle_unlock3.ogg");
delete_recursive("/system/media/audio/ui/circle_unlock4.ogg");
delete_recursive("/system/media/audio/ui/circlemosaic_lock.ogg");
delete_recursive("/system/media/audio/ui/circlemosaic_touchdown.ogg");
delete_recursive("/system/media/audio/ui/circlemosaic_unlock.ogg");
delete_recursive("/system/media/audio/ui/clear_ram.ogg");
delete_recursive("/system/media/audio/ui/continuous_shot.ogg");
delete_recursive("/system/media/audio/ui/crystal_lock.ogg");
delete_recursive("/system/media/audio/ui/crystal_unlock.ogg");
delete_recursive("/system/media/audio/ui/dewdrop_lock.ogg");
delete_recursive("/system/media/audio/ui/dewdrop_touchdown.ogg");
delete_recursive("/system/media/audio/ui/dewdrop_touchrelease.ogg");
delete_recursive("/system/media/audio/ui/dewdrop_unlock.ogg");
delete_recursive("/system/media/audio/ui/Effect_Tick.ogg");
delete_recursive("/system/media/audio/ui/Email_Sent.ogg");
delete_recursive("/system/media/audio/ui/FullBattery.ogg");
delete_recursive("/system/media/audio/ui/Homescreen_Remove.ogg");
delete_recursive("/system/media/audio/ui/Homescreen_Uninstall.ogg");
delete_recursive("/system/media/audio/ui/hulahoops_lock.ogg");
delete_recursive("/system/media/audio/ui/hulahoops_touchdown.ogg");
delete_recursive("/system/media/audio/ui/hulahoops_unlock.ogg");
delete_recursive("/system/media/audio/ui/ink_lock.ogg");
delete_recursive("/system/media/audio/ui/ink_touchdown.ogg");
delete_recursive("/system/media/audio/ui/ink_unlock.ogg");
delete_recursive("/system/media/audio/ui/KeypressDelete.ogg");
delete_recursive("/system/media/audio/ui/KeypressReturn.ogg");
delete_recursive("/system/media/audio/ui/KeypressSpacebar.ogg");
delete_recursive("/system/media/audio/ui/KeypressStandard.ogg");
delete_recursive("/system/media/audio/ui/LG_Cable_Connect.ogg");
delete_recursive("/system/media/audio/ui/LG_Media_volume.ogg");
delete_recursive("/system/media/audio/ui/light_lock.ogg");
delete_recursive("/system/media/audio/ui/light_touchdown.ogg");
delete_recursive("/system/media/audio/ui/light_unlock.ogg");
delete_recursive("/system/media/audio/ui/Lock_Cover.ogg");
delete_recursive("/system/media/audio/ui/Lock.ogg");
delete_recursive("/system/media/audio/ui/LowBattery.ogg");
delete_recursive("/system/media/audio/ui/mosaic_lock.ogg");
delete_recursive("/system/media/audio/ui/mosaic_touchdown.ogg");
delete_recursive("/system/media/audio/ui/mosaic_unlock.ogg");
delete_recursive("/system/media/audio/ui/particle_lock.ogg");
delete_recursive("/system/media/audio/ui/particle_unlock.ogg");
delete_recursive("/system/media/audio/ui/ripple_lock.ogg");
delete_recursive("/system/media/audio/ui/ripple_touchdown1.ogg");
delete_recursive("/system/media/audio/ui/ripple_touchdown2.ogg");
delete_recursive("/system/media/audio/ui/ripple_touchdown3.ogg");
delete_recursive("/system/media/audio/ui/ripple_touchrelease1.ogg");
delete_recursive("/system/media/audio/ui/ripple_touchrelease2.ogg");
delete_recursive("/system/media/audio/ui/ripple_touchrelease3.ogg");
delete_recursive("/system/media/audio/ui/ripple_unlock.ogg");
delete_recursive("/system/media/audio/ui/shot_snap.ogg");
delete_recursive("/system/media/audio/ui/soda_lock.ogg");
delete_recursive("/system/media/audio/ui/soda_touchdown.ogg");
delete_recursive("/system/media/audio/ui/soda_unlock.ogg");
delete_recursive("/system/media/audio/ui/switchoff.ogg");
delete_recursive("/system/media/audio/ui/switchon.ogg");
delete_recursive("/system/media/audio/ui/Unlock.ogg");
delete_recursive("/system/media/audio/ui/vector_lock.ogg");
delete_recursive("/system/media/audio/ui/vector_touchdown.ogg");
delete_recursive("/system/media/audio/ui/vector_unlock.ogg");
delete_recursive("/system/media/audio/ui/VideoRecord.ogg");
delete_recursive("/system/media/audio/ui/volume_key.ogg");
delete_recursive("/system/media/audio/ui/whitehole_lock.ogg");
delete_recursive("/system/media/audio/ui/whitehole_unlock.ogg");
No OTA
delete_recursive("/sbin/lge_fota_launcher");
delete_recursive("/sbin/lge_fota");
delete_recursive("/sbin/lge_gota_launcher");
delete_recursive("/system/app/LGDMWebViewer");
delete_recursive("/system/app/LGFOTA");
delete_recursive("/system/priv-app/LGDMSClient");
Verizon
delete_recursive("/data/app/air.com.sgn.cookiejam.gp-1");
delete_recursive("/data/app/air.com.sgn.juicejam.gp-1");
delete_recursive("/data/app/com.mapquest.android.ace-1");
delete_recursive("/data/app/com.sgn.geniesandgems.gp-1");
delete_recursive("/data/app/com.verizonmedia.go90.enterprise-2");
delete_recursive("/system/app/LGVZWHelp");
delete_recursive("/system/media/bootanimation.zip");
delete_recursive("/system/priv-app/com.gotv.nflgamecenter.us.lite");
delete_recursive("/system/priv-app/com.verizon.mips.adpt");
delete_recursive("/system/priv-app/ECID");
delete_recursive("/system/priv-app/iHeartRadio");
delete_recursive("/system/priv-app/LGVZWHelp");
delete_recursive("/system/priv-app/MyInfozone");
delete_recursive("/system/priv-app/MyVerizon");
delete_recursive("/system/priv-app/SlackerRadio");
delete_recursive("/system/priv-app/VerizonIgnite");
delete_recursive("/system/priv-app/VerizonMessage");
delete_recursive("/system/priv-app/VVM");
delete_recursive("/system/priv-app/VZCloud");
delete_recursive("/system/priv-app/VZMessages");
delete_recursive("/system/priv-app/VZMobileSecurity");
delete_recursive("/system/priv-app/VZNavigator");
Apps affected by Xposed
delete_recursive("/system/app/LGWeather");
delete_recursive("/system/app/LGWeatherService");
delete_recursive("/system/app/LGWeatherTheme");
For the VK810 only, there are also 7-Zip archives of the apps and files that are removed in case any user needs them located in the "35A_08 debloated apps-files" or "36B_00 debloated apps-files" subfolders of my section on Android File Host. They are virtually identical to the separate packages listed above for which debloat script removes what, with the only two exceptions being self-explanatory.
Enjoy!
Claimed again.
Ok....now I'm excited. Any more info?
ddodge68 said:
Ok....now I'm excited. Any more info?
Click to expand...
Click to collapse
Hi! I added some preliminary info in the OP. Thanks for asking!
Looking forward to it, thank so much for taking this on. My poor G Pad had been feeling neglected for far too long since my Nexus 6 gets all the ROM love
rant said:
Looking forward to it, thank so much for taking this on. My poor G Pad had been feeling neglected for far too long since my Nexus 6 gets all the ROM love
Click to expand...
Click to collapse
Will this be something we can flash right from TWRP ?
rant said:
Looking forward to it, thank so much for taking this on. My poor G Pad had been feeling neglected for far too long since my Nexus 6 gets all the ROM love
Click to expand...
Click to collapse
You're welcome! I was doing some preliminary work before CleanROM was released to release something like this for 24A but I didn't want to bother duplicating the effort once it was released. There's others who are trying quietly to give our tablet more love than I can give it.
Anthony-m said:
Will this be something we can flash right from TWRP ?
Click to expand...
Click to collapse
Yes.
ROM's done uploading for anyone interested. I'll work on a debloat zip, but that'll take longer than a day.
roirraW "edor" ehT said:
ROM's done uploading for anyone interested. I'll work on a debloat zip, but that'll take longer than a day.
Click to expand...
Click to collapse
Sorry for the questions and thanks a lot for making this rom happen for us. I am using the clean rom right now and the TWRP you mention above, do I just flash the rom and then Supersu and I will have rooted stock lollipop correct? Then I would need to follow the directions in your 4.22 aboot image (which I am pretty sure I already did when I installed TWRP the first time)..again thanks for your hard work..
Anthony-m said:
Sorry for the questions and thanks a lot for making this rom happen for us. I am using the clean rom right now and the TWRP you mention above, do I just flash the rom and then Supersu and I will have rooted stock lollipop correct? Then I would need to follow the directions in your 4.22 aboot image (which I am pretty sure I already did when I installed TWRP the first time)..again thanks for your hard work..
Click to expand...
Click to collapse
No problem. Just flash the ROM and SuperSU, and yes you'll have rooted stock lollipop.
You don't need to follow the directions regarding the 4.2.2 aboot image unless you want to get back into TWRP. But if flash the 4.2.2 aboot.img, you won't be able to boot the ROM, only TWRP. You can do it, to make a backup, to flash something else like Xposed Alpha for Lollipop, etc (unsupported by me), then you'll have to flash the 35A_08 aboot.img zip file I also provide from TWRP so that you can boot the ROM again.
I'll try to figure out a way to make this all clearer.
Thanks for the fast replies, you are so damn helpful I really appreciate it. Crap should I do a factory reset from TWRP before flashing this lol..you knew one more question was coming lol
Anthony-m said:
Thanks for the fast replies, you are so damn helpful I really appreciate it. Crap should I do a factory reset from TWRP before flashing this lol..you knew one more question was coming lol
Click to expand...
Click to collapse
Well thank you back! I appreciate it.
Yes wipe system, data, cache and Dalvik before flashing. Just remember to flash the SuperSU.zip after.
Do i have to wipe/factory reset or wiil this update from cleanrom
4218kris said:
Do i have to wipe/factory reset or wiil this update from cleanrom
Click to expand...
Click to collapse
Hello!
Answered a few posts above yours.
roirraW "edor" ehT said:
Hello!
Answered a few posts above yours.
Click to expand...
Click to collapse
Android is upgrading
Damn I installed the rom and it was working perfectly than I did the aboot update and restarted the tablet and it says secure booting error cause boot certification verify and it stays on the LG screen...FML lol...
Anthony-m said:
Damn I installed the rom and it was working perfectly than I did the aboot update and restarted the tablet and it says secure booting error cause boot certification verify and it stays on the LG screen...FML lol...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=60879291&postcount=11
You need to flash the 35A_08 aboot zip file I provided in the same place as the ROM download on AFH in order to boot the ROM. The 4.2.2 aboot is only for getting into custom recovery. Once you flash the ROM, the *only* reason for re-flashing the 4.2.2 aboot is to get into custom recovery. But then you need to reflash the 35A_08 5.0.2 aboot in order to boot back into the ROM.
Never mind *****es, did a factory reset and it went to TWRP and I did the update exactly like roirraW "edor" ehT instructed in his OP and I am all set with the new rooted Lollipop rom and TWRP Nice work brother....
---------- Post added at 05:22 PM ---------- Previous post was at 05:20 PM ----------
Yup I just didn't realize I wasn't going to automatically go into TWRP after flashing the 4.2.2 aboot image, once I got in I applied the 35A_08 aboot zip and all is well...
I have been dealing with this problem for about three weeks now, and nowhere have I been able to find a workable solution to the problem. I've gone the route of wiping cache, dalvik, system and data, let the phone boot to "No OS" then attempt the flash, but so far I have just wasted time and achieved no viable ends from these various means.
Is there anyone who actually know what the problem is with this? The device is a rooted LG G3 VS985. I'm running TRWP v2.8.6.0. I would really like to get to the root of this problem (slight pun intended) so that I can get back to upgrading my ROMs as BlissRom releases them.
MoparOso said:
I have been dealing with this problem for about three weeks now, and nowhere have I been able to find a workable solution to the problem. I've gone the route of wiping cache, dalvik, system and data, let the phone boot to "No OS" then attempt the flash, but so far I have just wasted time and achieved no viable ends from these various means.
Is there anyone who actually know what the problem is with this? The device is a rooted LG G3 VS985. I'm running TRWP v2.8.6.0. I would really like to get to the root of this problem (slight pun intended) so that I can get back to upgrading my ROMs as BlissRom releases them.
Click to expand...
Click to collapse
Most likely you are failing a baseband check that CM based ROMs started doing a few weeks ago. Flash this modem before you try and flash the ROM: https://www.androidfilehost.com/?fid=95916177934553732
It should flash after that. If not, please post a screenshot of your recovery screen(vol down + power at the same time) so we can see the error.
And here's a link to our modems: http://forum.xda-developers.com/showpost.php?p=56005257&postcount=4
If you don't like the 23c modem you can flash whichever one you want after you get your ROM flashed.
startswithPendswithOOH said:
Most likely you are failing a baseband check that CM based ROMs started doing a few weeks ago. Flash this modem before you try and flash the ROM: https://www.androidfilehost.com/?fid=95916177934553732
It should flash after that. If not, please post a screenshot of your recovery screen(vol down + power at the same time) so we can see the error.
And here's a link to our modems: http://forum.xda-developers.com/showpost.php?p=56005257&postcount=4
If you don't like the 23c modem you can flash whichever one you want after you get your ROM flashed.
Click to expand...
Click to collapse
Thank you so much for an intelligent and more important workable solution to my problem. I used your modem, version 23C. It worked great. I can't thank you enough.
startswithPendswithOOH said:
Most likely you are failing a baseband check that CM based ROMs started doing a few weeks ago. Flash this modem before you try and flash the ROM: https://www.androidfilehost.com/?fid=95916177934553732
It should flash after that. If not, please post a screenshot of your recovery screen(vol down + power at the same time) so we can see the error.
And here's a link to our modems: http://forum.xda-developers.com/showpost.php?p=56005257&postcount=4
If you don't like the 23c modem you can flash whichever one you want after you get your ROM flashed.
Click to expand...
Click to collapse
This also worked for me, 23c modem prior to rom and all is well. Thank you!
startswithPendswithOOH said:
Most likely you are failing a baseband check that CM based ROMs started doing a few weeks ago. Flash this modem before you try and flash the ROM: https://www.androidfilehost.com/?fid=95916177934553732
It should flash after that. If not, please post a screenshot of your recovery screen(vol down + power at the same time) so we can see the error.
And here's a link to our modems: http://forum.xda-developers.com/showpost.php?p=56005257&postcount=4
If you don't like the 23c modem you can flash whichever one you want after you get your ROM flashed.
Click to expand...
Click to collapse
Hi all, incredibly noon here. I faced the same error but it's still present after I flashed the modem. Anyone can help? I tried to screencap but I don't think it worked in recovery mode.
help
having same problem after trying to install cm13 on lg g3 verzon tryed flashing modem 23c still no luck please help
lazy445 said:
having same problem after trying to install cm13 on lg g3 verzon tryed flashing modem 23c still no luck please help
Click to expand...
Click to collapse
You probably need the 35b modem to get past the baseband check. But the 35b modem alone may have some issues if you don't flash the whole bootstack with it. So flash this 35b bootstack 1st( https://www.androidfilehost.com/?fid=24052804347843993 ), then flash the ROM & MM gapps.
OR - if you really like the 23c or 24b modem and don't want to use the 35b, you can flash just the 35b modem( http://forum.xda-developers.com/showpost.php?p=56005257&postcount=4) to get past the check, flash the ROM, and then flash whatever modem you prefer. I use the 24b modem/boostack on MM ROMs and it works fine...not sure about 23c.
startswithPendswithOOH said:
You probably need the 35b modem to get past the baseband check. But the 35b modem alone may have some issues if you don't flash the whole bootstack with it. So flash this 35b bootstack 1st( https://www.androidfilehost.com/?fid=24052804347843993 ), then flash the ROM & MM gapps.
OR - if you really like the 23c or 24b modem and don't want to use the 35b, you can flash just the 35b modem( http://forum.xda-developers.com/showpost.php?p=56005257&postcount=4) to get past the check, flash the ROM, and then flash whatever modem you prefer. I use the 24b modem/boostack on MM ROMs and it works fine...not sure about 23c.
Click to expand...
Click to collapse
I got it to work with 35b but don't have data? Any sugestions
lazy445 said:
I got it to work with 35b but don't have data? Any sugestions
Click to expand...
Click to collapse
K...that's a bummer. I'm not on cm13 rt now...I'm on candy6(which is very nice BTW) so if there is a ROM issue that is causing the no data - I would have no idea about it. Best to check the CM threads and see if anyone else has the issue. It could be something simple like changing your apns or whatever normally causes data issues...or maybe you just got a bad build.
But if you think it's a radio issue - did you flash the whole 35b bootstack, or just the modem? If just the modem then try flashing the 35b bootstack as well - or just downgrade your modem to 24b.
If you flashed the 35b bootstack and want to downgrade to 24b you'll need to downgrade the entire bootstack and not just the modem because it will probably give you issues. For ex, as an experiment, I just flashed Temasek cm13 with 35b bootstack and have data working (if you want to try that build instead... http://forum.xda-developers.com/ver...aseks-unofficial-build-lollipop-5-01-t2965501 ) & the 24b boostack also worked normally as well. But if I mix bootstacks and modems(35b bootstack with 24b modem, & vice versa) the phone won't boot past the LG splash screen. You can find the 24b bootstack here if you need it(and read post #2 if you want to know more about bootstacks)... http://forum.xda-developers.com/verizon-lg-g3/development/xdabbeb-s-vs980-2-0-0-t3231279
Personally I find the whole bootstack thing annoying and don't see any significant benefit from using the newer modem which is why I stick with using the 24b modem/bootstack, flash the 35b modem to pass the initial check if I need to, and flash the 24b modem and reboot. It just makes life easier when restoring my nandroid backups. But that's just me & to each his own
startswithPendswithOOH said:
You probably need the 35b modem to get past the baseband check. But the 35b modem alone may have some issues if you don't flash the whole bootstack with it. So flash this 35b bootstack 1st( https://www.androidfilehost.com/?fid=24052804347843993 ), then flash the ROM & MM gapps.
OR - if you really like the 23c or 24b modem and don't want to use the 35b, you can flash just the 35b modem( http://forum.xda-developers.com/showpost.php?p=56005257&postcount=4) to get past the check, flash the ROM, and then flash whatever modem you prefer. I use the 24b modem/boostack on MM ROMs and it works fine...not sure about 23c.
Click to expand...
Click to collapse
startswithPendswithOOH said:
K...that's a bummer. I'm not on cm13 rt now...I'm on candy6(which is very nice BTW) so if there is a ROM issue that is causing the no data - I would have no idea about it. Best to check the CM threads and see if anyone else has the issue. It could be something simple like changing your apns or whatever normally causes data issues...or maybe you just got a bad build.
But if you think it's a radio issue - did you flash the whole 35b bootstack, or just the modem? If just the modem then try flashing the 35b bootstack as well - or just downgrade your modem to 24b.
If you flashed the 35b bootstack and want to downgrade to 24b you'll need to downgrade the entire bootstack and not just the modem because it will probably give you issues. For ex, as an experiment, I just flashed Temasek cm13 with 35b bootstack and have data working (if you want to try that build instead... http://forum.xda-developers.com/ver...aseks-unofficial-build-lollipop-5-01-t2965501 ) & the 24b boostack also worked normally as well. But if I mix bootstacks and modems(35b bootstack with 24b modem, & vice versa) the phone won't boot past the LG splash screen. You can find the 24b bootstack here if you need it(and read post #2 if you want to know more about bootstacks)... http://forum.xda-developers.com/verizon-lg-g3/development/xdabbeb-s-vs980-2-0-0-t3231279
Personally I find the whole bootstack thing annoying and don't see any significant benefit from using the newer modem which is why I stick with using the 24b modem/bootstack, flash the 35b modem to pass the initial check if I need to, and flash the 24b modem and reboot. It just makes life easier when restoring my nandroid backups. But that's just me & to each his own
Click to expand...
Click to collapse
Do you think the 24b boot stack will fix data. If so can you link that. Also if you find apn fixed for cm13 lg g3 data
lazy445 said:
Do you think the 24b boot stack will fix data. If so can you link that. Also if you find apn fixed for cm13 lg g3 data
Click to expand...
Click to collapse
It is already linked in the last post...xdabbebs vs985 thread has 35b, 24b, and 12b bootstack links.
And I don't use cm13(too many bugs) so I'm not familiar, but if you Google Verizon APN settings you'll find what you need.
MoparOso said:
I have been dealing with this problem for about three weeks now, and nowhere have I been able to find a workable solution to the problem. I've gone the route of wiping cache, dalvik, system and data, let the phone boot to "No OS" then attempt the flash, but so far I have just wasted time and achieved no viable ends from these various means.
Is there anyone who actually know what the problem is with this? The device is a rooted LG G3 VS985. I'm running TRWP v2.8.6.0. I would really like to get to the root of this problem (slight pun intended) so that I can get back to upgrading my ROMs as BlissRom releases them.
Click to expand...
Click to collapse
I have LG G3 D858HK (D858HK20e-HKG-XX) and I'm having the same problem when trying to flash Android 6.0 ROM to my phone with TWRP Recovery, anyone knows what's this and how to fix it, please HELP!!!
Dear i have the same problem, my cell fone is LG g3 vs985, it was running on stock Rom 4.4.2 kitkat, then i tried to upgrade it, i managed to upgrade it on Fulmics 6.5, i used it fot month, but it seems that its a bit slow, i checked out for other Custom Roms, LineageOS or Ressurection Remix 7.0 are my choices, but unfortunatly, i could not manage to flash them, i had to downgrade my fone to stock using TOT method, then i installed recovery n root it, as it is required to flash a custom ROm but i get error while flashing n now i m Operationg system less plz some one help....
Sent from my HUAWEI ALE-L21 using XDA Labs
---------- Post added at 12:02 PM ---------- Previous post was at 11:59 AM ----------
ASGH93 said:
I have LG G3 D858HK (D858HK20e-HKG-XX) and I'm having the same problem when trying to flash Android 6.0 ROM to my phone with TWRP Recovery, anyone knows what's this and how to fix it, please HELP!!!
Click to expand...
Click to collapse
Dear i think u must try to flash Fulmics.7.0, its the only ROM which i found to flash with no hurdle, try it its also ful of almost extra features
Sent from my HUAWEI ALE-L21 using XDA Labs
Hey there, I just flashed 35b bootstack on lg g3 vs98510B on stock ROM 4.4.2 just check what impact does it put, I dont see any change on system about page, but I see Sim & data go on & of like its creating some problem with sim, rest is working fine. What do u say shud I it a try n flash cm based MM or N&N ROM. Will it work.
Sent from my HUAWEI ALE-L21 using XDA Labs
Everytime i upgrade to an international marshmallow rom i lose 4g signal and becuz of it i get "cell stanby" draining my battery heavily. I tried flashing all the basebands and bootstacks even backedup my efs from an older rom or marshmallow rom on verizon becuz my data works perfect on verizon roms. The right apns looks to be in tact. I just really want this to work becuz this is the lg g5 rom im on. (Fulmics 5.0) i can also still text and call. Just no 4g and bars.
MonstaSaleens said:
Everytime i upgrade to an international marshmallow rom i lose 4g signal and becuz of it i get "cell stanby" draining my battery heavily. I tried flashing all the basebands and bootstacks even backedup my efs from an older rom or marshmallow rom on verizon becuz my data works perfect on verizon roms. The right apns looks to be in tact. I just really want this to work becuz this is the lg g5 rom im on. (Fulmics 5.0) i can also still text and call. Just no 4g and bars.
Click to expand...
Click to collapse
If it's not specifically for the VS985, I wouldn't flash it. You'll have to either fully TOT or KDZ flash it back to fix all your partitions just to be on the safe side.
You should never flash a non-VS985 ROM on the VS985. If you do, you're taking a risk to brick it.
If this was for the VS985, then my apologies, but you didn't specify which ROM it was and I'm assuming since you're postin ghere in the Verizon G3 forums, you have the VS985 G3 and not some other variety.
iBolski said:
If it's not specifically for the VS985, I wouldn't flash it. You'll have to either fully TOT or KDZ flash it back to fix all your partitions just to be on the safe side.
You should never flash a non-VS985 ROM on the VS985. If you do, you're taking a risk to brick it.
If this was for the VS985, then my apologies, but you didn't specify which ROM it was and I'm assuming since you're postin ghere in the Verizon G3 forums, you have the VS985 G3 and not some other variety.
Click to expand...
Click to collapse
Yes it is for verizon, its fulmicsROM 5.0 i chose vs985 in aroma. Other verizon users are saying thier data works without even touching apns. Mine worked in the bigginning but after a couple hours it just did what it did in the pics and havnt worked since.
MonstaSaleens said:
Yes it is for verizon, its fulmicsROM 5.0 i chose vs985 in aroma. Other verizon users are saying thier data works without even touching apns. Mine worked in the bigginning but after a couple hours it just did what it did in the pics and havnt worked since.
Click to expand...
Click to collapse
When you flashed this ROM, what boot partition to you flash from? I did find one in the generic G3 Development forum so I'm assuming the following link is where you probably found it:
http://forum.xda-developers.com/lg-g3/development/rom-fulmics-rom-1-0-tweaks-ota-v20u-t3232340
You might have flashed it with the wrong boot and modem partition. I believe 12B is the last one that works with the current version of TWRP that is bumped for the VS985. Anything above that will not work as they haven't released a new bumped TWRP for the more recent OTAs.
I would find one of the revert back to stock threads, flash it back to a version such as 10B (via TOT or KDZ) and see if your LTE signal comes back. If so, then you should be able to root from there, flash TWRP and then hopefully flash the fulmicsROM at that point and it should hopefully work. If it doesn't work on 10B, then it sounds like your LTE antenna may be going bad.
Otherwise, I'm not sure what is going on.
Hope that helps!
I have same problem. Seems vs985 is updated to 47a witch there is no bumped boot loader for 47a. That may be our problem.
Sent from my VS985 4G using XDA-Developers mobile app
iBolski said:
When you flashed this ROM, what boot partition to you flash from? I did find one in the generic G3 Development forum so I'm assuming the following link is where you probably found it:
http://forum.xda-developers.com/lg-g3/development/rom-fulmics-rom-1-0-tweaks-ota-v20u-t3232340
You might have flashed it with the wrong boot and modem partition. I believe 12B is the last one that works with the current version of TWRP that is bumped for the VS985. Anything above that will not work as they haven't released a new bumped TWRP for the more recent OTAs.
I would find one of the revert back to stock threads, flash it back to a version such as 10B (via TOT or KDZ) and see if your LTE signal comes back. If so, then you should be able to root from there, flash TWRP and then hopefully flash the fulmicsROM at that point and it should hopefully work. If it doesn't work on 10B, then it sounds like your LTE antenna may be going bad.
Otherwise, I'm not sure what is going on.
Hope that helps!
Click to expand...
Click to collapse
Theres nothing wrong with my data when i flash any verizon rom. So when i go back to it it works perfectly. But when i go to any marshmallow rom for multiple variants my data seems it cant connect. Ive tried the kdz method like 3 times and flashed from there but it didnt work. Im not sure about what you mean by what boot partition i flashed from
MonstaSaleens said:
Theres nothing wrong with my data when i flash any verizon rom. So when i go back to it it works perfectly. But when i go to any marshmallow rom for multiple variants my data seems it cant connect. Ive tried the kdz method like 3 times and flashed from there but it didnt work. Im not sure about what you mean by what boot partition i flashed from
Click to expand...
Click to collapse
Depending on the version of Android you used KDZ'd from, that determines what your modem and boot partition are set up as. In order to flash any Marshmallow ROM, you cannot be on the current 72A boot and modem partitions. They do not work with TWRP for the G3. So based on what you've told me, where your LTE signal is fine on stock, that to me suggests one of two things:
You're flashing the custom ROM with an incorrect modem and/or boot partition (later than 10B)
The ROM itself is bad
So, you have to KDZ or TOT back to 10b and flash your ROM from there. I'm assuming that's what you've done, but I wanted to make sure.
The directions in that thread do not give the specifics for the VS985 version.
Here are directions on downgrading to 10B properly so that you can flash custom ROMs properly:
http://forum.xda-developers.com/verizon-lg-g3/general/lg-g3-downgrade-to-10b-t3354834
Here's another thread on doing the same:
http://forum.xda-developers.com/verizon-lg-g3/general/lg-g3-downgrade-to-10b-t3354834
@iBolski From what I read in the Fulmics v5.0 thread, the 12B bootstack is the one that's necessary to have data working on Verizon (for most people). The OP said he tried all the bootstacks though so no idea there.
roirraW "edor" ehT said:
@iBolski From what I read in the Fulmics v5.0 thread, the 12B bootstack is the one that's necessary to have data working on Verizon (for most people). The OP said he tried all the bootstacks though so no idea there.
Click to expand...
Click to collapse
@roirraW "edor" ehT Thanks! I must have missed that somewhere in the thread.
@MonstaSaleens, there's your answer. Make sure you TOT or KDZ back to 12B (I would flash the entire thing). @roirraW "edor" ehT has links in his sig that can point you to all the correct images and instructions you need. The first two links in his sig are what you want.
iBolski said:
@roirraW "edor" ehT Thanks! I must have missed that somewhere in the thread.
@MonstaSaleens, there's your answer. Make sure you TOT or KDZ back to 12B (I would flash the entire thing). @roirraW "edor" ehT has links in his sig that can point you to all the correct images and instructions you need. The first two links in his sig are what you want.
Click to expand...
Click to collapse
Ive done this multiple times before. I even formated internal storage. Went bakc down to 12b used stump root to root and still no data on fulmics. Ive been had problems with the data on roms that are for all varients and are marshmallow. It just doesnt like my phone. But hey, data is doing the same thing on my brothers g3 when he flashed this rom cuz he wanted the new g5 ui too.
roirraW "edor" ehT said:
@iBolski From what I read in the Fulmics v5.0 thread, the 12B bootstack is the one that's necessary to have data working on Verizon (for most people). The OP said he tried all the bootstacks though so no idea there.
Click to expand...
Click to collapse
Do we have any flashable marshmallow radios yet?
MonstaSaleens said:
Do we have any flashable marshmallow radios yet?
Click to expand...
Click to collapse
Short answer: No.
There's technical reasons why we can't use the 46A and 47A modems, at least if you want to be able to use TWRP. There's nothing to stop you from flashing the modem extracted out of the 47A KDZ, but you won't have a signal or data with the modem alone. The 46A and 47A modem require the 46A or 47A sbl1 partition.
Putting the 46A or 47A sbl1 on the phone when you already have working TWRP will cause a QHSUSB_BULK 9008 mode brick because those sbl1 really don't like the 12B (or older) bootloader, and the 12B (or 11C or 10B) bootloader is required to get into TWRP.
So...you can have either:
1. TWRP along with the 12B bootloader, but only up to 35B sbl1 and modem.
Or
2. The Marshmallow bootloader, sbl1 and modem.
I haven't tried or tested getting rid of TWRP and re-upgrading the bootloader, sbl1 and modem, but that should in theory work, at least on stock 46A and 47A ROMs - don't know about international or CM13 ROMs.
I acquired an lg g3 on 24b. I figured I would make it as a spare incase I lost or damaged my original and use it to test newer versions like marshmallow or nouget.
Here's what I did
1. I I restored factory image using lg flash tool .tot version back to 10b
2. stump rooted it.
3. installed earliey twrp from 2014 with flashify
4. installed twrp 3.0.0
5. did a twrp back up including EFS
6. restored my jasmine9.1 -35b image to it. with EFS checked
7. Noticed my modem/baseband version was "Unknown"
I was going to flash the 35b modem but before that I had some questions.
Questions.
1. what exactly is EFS? ( am asking because I included it when I went from 10b to jasmine9.1 35b I need to know if that's something you dont flash from one phone to another)
2. if I flash my modem file to 35b wil I be able to flip flop back and forth and upwith modem files.?
3. how high can I go with revsions keeping twrp and modem/baseband without have to restore original with .tot if I want to get back to 35b.
I know enough to be dangerous so I'm asking cause I don't know enough! lol
thanks.
EFS is or includes your IMEI. If your 35B backup was from another phone, you don't want to restore EFS from your old phone. Restore your EFS from your 24B backup. You don't normally want to restore your EFS every time you restore a TWRP Backup. I personally do a TWRP back up of just my EFS and save it to Google Drive since sometimes flashing a TOT, KDZ or ROM will wipe the IMEI and without having an EFS backup handy, it's a bigger pain to restore using proprietory Windows software.
Just in case you don't know, never flash a Bootstack BEFORE flashing either JasmineROM 9.x or SkyDragon 6.x. After flashing either ROM, either flash the 24B or 35B Bootstack from @xdabbeb 's VS985 v2.0 ROM thread in the Development (non-original) section. Don't just flash the modem.
If you flash the 35B Bootstack you can certainly flash the 24B Bootstack later if you wish. The Bootstacks contain more than just the modems, but they include the modem too. The modem sometimes requires a newer sbl1 partition which is included, which is why you should flash the entire Bootstack and not just the modem, because the Bootstacks contain the appropriate sbl1. Not having the correct modem/sbl1 combination (for instance, 35B modem but 24B sbl1, or when using an older completely incompatible modem/sbl1 with a newer stock ROM) *might* cause the Settings / About / Status menu to show no IMEI too, but it shows back up after flashing the entire correct Bootstack.
The 35B Bootstack is the highest you can flash no matter what ROM you use on 35B or higher (46A or 47A). I'm not clear on what you were asking "how high can I go with revsions keeping twrp and modem/baseband without have to restore original with .tot if I want to get back to 35b" so if that doesn't answer that, please reword that question. You can flash @xdabbeb 's stock 47A (pre-rooted) firmware if you want to be on the 47A ROM; albeit you still have to use the 35B Bootstack.
I'm glad I saved the EFS from 24b now. (just incase I sell the phone I will restore it... doubt I will though but it's good to have. I don't mind flashing EFS to the second phone cause I will only use one at any given time with my sim card. I flashed xdabeb bootstack-35bmodem file already but I used the orignal not the non-orginal... so I guess I'm lucky cause it works. Thanks. I can't wait to try marshmallow! I got some reading ahead of me cause I want to get all the features I prefer working on marshmallow
like
xposed
wifi tethering with native app.
g3 tweak box (auto call recording feature is nice when your wife says "no I diddn't say that" lol
rp201 said:
I flashed xdabeb bootstack-35bmodem file already but I used the orignal not the non-orginal...
Click to expand...
Click to collapse
There's only one @xdabbeb VS985 v2.0 thread - in the regular Development section (what I call non-original), not the Original Development section. That's what I meant.
The link below is a DEBLOATED flashable zip of the LG V20 10p ROM. I extracted it from the latest 10p KDZ file using kdztools and python 2.7 on Windows. I built the ROM from the extraction using Superrs kitchen version 3 on Linux.
Tons of bloat removed.
I purposely didn't remove WiFi calling, VPN files, and LG Update center in case you want to install some LG apps.
I have added the Google Pixel Launcher because it's so quick. It's optional to use if you want to or not.
I used Superr's kitchen to debloat this plus some manual cut and paste.
READ ALL WARNINGS BEFORE PROCEEDING
This rom is not rooted but you can flash magisk or SuperSU to root it. It does not flash recovery. It does not encrypt.
Using magisk it works with both Samsung and Android [email protected] which is the main reason I built it.
Issues: none i know of but let me know please! Also, see warnings below
TO DO's: you tell me
Flash at your own risk. I'm not responsible if your device gets bricked.
10p Warnings based on what we know:
WARNING #1 You must flash the 10p modem and bootloader for this to work. If you don't you will soft brick.
WARNING #2 Once you go to 10p modem and bootloader you can't go back to previous versions. If you try you will HARD brick your device.
WARNING #3 10P rom only works with 10p modem and 10p bootloader. Any other combo SOFT bricks.
WARNING #4 TWRP backups of previous versions will not restore correctly once you are on 10p. When you restore a previous version (10k and before) you will soft brick. You can unbrick by just installing the 10p ROM, modem, and bootloader over the top of your restore *****Restores and Backups of 10p roms work just fine.
BOTTOM LINE: Going to 10p is a TOTAL commitment and there probably will never be a way to go back. That said, I'm on 10p and so far it works great.
Version 3 changes: fixed a mic issue
ROM Links:
Drive: https://drive.google.com/open?id=0B3y-9RMsaMSbVnZ5eHZDSjhuUUk
Get 10p Modem and 10p bootloader here:
https://forum.xda-developers.com/v20/development/firmware-twrp-flashable-bootloader-modem-t3547268
*****Be sure to thank the OP on that thread!*****
Clean install instructions: twrp backup, wipe, install ROM, install 10p modem, install 10p bootloader, install root of your choice, reboot
Dirty install works fine over Weta ROM or NATF ROM, but not over aosp or lineage roms: twrp backup, install ROM, install 10p modem, install 10p bootloader, install root of your choice, reboot. Note: when you dirty flash you do lose any system apps you had before but your data partition is retained.
Enjoy. Please give thanks if this ROM is helpful for you.
First!
The latest magisk version works? I'm on rooted 10k and i'm going to dirty flash this later.
Sent from my LG-H918 using Tapatalk
peekeesh said:
The latest magisk version works? I'm on rooted 10k and i'm going to dirty flash this later.
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
yes sir. I can confirm that Magisk 13.3 works like a champ for me. Magisk 13.xx has always needed to be reinstalled like once every two weeks for me, no matter what ROM I am on. Samsung and Google [email protected] both work nicely too on this rom.
Note: when you dirty flash you do lose any system apps you had before but your data partition is retained.
peekeesh said:
The latest magisk version works? I'm on rooted 10k and i'm going to dirty flash this later.
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
Remember you need to flash 10P bootloader and modem and there is no going back to 10K afterwards.
Sent from my LG-H918 using Tapatalk
texasaggie1 said:
yes sir. I can confirm that Magisk 13.3 works like a champ for me. Magisk 13.xx has always needed to be reinstalled like once every two weeks for me, no matter what ROM I am on. Samsung and Google [email protected] both work nicely too on this rom.
Note: when you dirty flash you do lose any system apps you had before but your data partition is retained.
Click to expand...
Click to collapse
Ok thanks for confirming..?
Bxlegend, thanks for the reminder.
Sent from my LG-H918 using Tapatalk
bxlegend said:
Remember you need to flash 10P bootloader and modem and there is no going back to 10K afterwards.
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
It's an all out commitment lol
Can you post a list of what you removed?
gig'em!
sdc177 said:
gig'em!
Click to expand...
Click to collapse
Yes sir !!
texasaggie1 said:
The link below is a DEBLOATED flashable zip of the LG V20 10p ROM. I extracted it from the latest 10p KDZ file using kdztools and python 2.7 on Windows. I built the ROM from the extraction using Superrs kitchen version 3 on Linux.
Tons of bloat removed.
I purposely didn't remove WiFi calling, VPN files, and LG Update center in case you want to install some LG apps.
I used Superr's kitchen to debloat this plus some manual cut and paste.
READ ALL WARNINGS BEFORE PROCEEDING
This rom is not rooted but you can flash magisk or SuperSU to root it. It does not flash recovery. It does not encrypt.
Using magisk it works with both Samsung and Android [email protected] which is the main reason I built it.
Issues: none i know of but let me know please! Also, see warnings below
TO DO's: you tell me
Flash at your own risk. I'm not responsible if your device gets bricked.
10p Warnings based on what we know:
WARNING #1 You must flash the 10p modem and bootloader for this to work. If you don't you will soft brick.
WARNING #2 Once you go to 10p modem and bootloader you can't go back to previous versions. If you try you will HARD brick your device.
WARNING #3 10P rom only works with 10p modem and 10p bootloader. Any other combo SOFT bricks.
WARNING #4 TWRP backups of previous versions will not restore correctly once you are on 10p. When you restore a previous version (10k and before) you will soft brick. You can unbrick by just installing the 10p ROM, modem, and bootloader over the top of your restore *****Restores and Backups of 10p roms work just fine.
BOTTOM LINE: Going to 10p is a TOTAL commitment and there probably will never be a way to go back. That said, I'm on 10p and so far it works great.
ROM Links:
Drive: [ https://drive.google.com/file/d/0B3y-9RMsaMSbRWNEUzJMZkwyUk0/view?usp=drivesdk [/url]
Get 10p Modem and 10p bootloader here:
https://forum.xda-developers.com/v20/development/firmware-twrp-flashable-bootloader-modem-t3547268
*****Be sure to thank the OP on that thread!*****
Clean install instructions: twrp backup, wipe, install ROM, install 10p modem, install 10p bootloader, install root of your choice, reboot
Dirty install works fine over Weta ROM or NATF ROM, but not over aosp or lineage roms: twrp backup, install ROM, install 10p modem, install 10p bootloader, install root of your choice, reboot. Note: when you dirty flash you do lose any system apps you had before but your data partition is retained.
Enjoy. Please give thanks if this ROM is helpful for you.
Click to expand...
Click to collapse
Latest version uploaded
So happy to see more love for my beloved v20 going to dirty flash tomorrow and see how things go. One question I have is why for any reason would someone wanna go back to 10k? Does this update have any flaws that would make someone regret updating? New updates are always good right?
If anybody has dirty flashed from MEGAROM with no problems please let us know.
MEGAROM h918 10k
Deodex?
Great job on this, any chance for a deodex version so ee try some of the mods for this masterpiece?
Still_living714 said:
So happy to see more love for my beloved v20 going to dirty flash tomorrow and see how things go. One question I have is why for any reason would someone wanna go back to 10k? Does this update have any flaws that would make someone regret updating? New updates are always good right?
If anybody has dirty flashed from MEGAROM with no problems please let us know.
MEGAROM h918 10k
Click to expand...
Click to collapse
well, the main reason to stay on 10k would be that you're guaranteed to be able to root and TWRP. if you make a mistake and lose TWRP for whatever reason while on 10p, you're fscked. you can wait for root, but I doubt it's coming any time soon
Bluetooth performance seem to be on point in this one as opposed to 10k!
custommsp said:
Any comments on bluetooth pairing and performance? There are pairing issues in 10k with certain devices.
Thanks.
Click to expand...
Click to collapse
So you're on 10K ? Then there's a good chance you flashed the 10K KDZ from lg-firmwares.com, or one of the TWRP zips from xda. The KDZ for 10K is messed up, just look inside it and see. Among other things, it contains a misc.bin (not supposed to be there) which overwrites the one (unique) on you phone, thus erasing your WLAN mac address and other stuff, possibly affecting Bluetooth.
Before I bricked, I noticed this when I used my phone as FTP server, the IP address would change at every reboot. At that time I didn't know why, but assumed it was just some temporary bug with the stock rom.
LG screwed up again.
Edit: OK, @me2151 has just informed me that the problem might not have been caused by wiping misc partition after all. There may been some confusion on the matter. But remains to be seen I guess. @dimm0k may have some input.
Nope seems it it the case like I first said. More info.
need root to try this stuck on 10p sadly
Does xposed work? If so which one is recomended for 10p?
custommsp said:
Any comments on bluetooth pairing and performance? There are pairing issues in 10k with certain devices.
Thanks.
Click to expand...
Click to collapse
what pairing issues are you having and with what devices? I don't recall having any Bluetooth issues when I was on 10k
askermk2000 said:
So you're on 10K ? Then there's a good chance you flashed the 10K KDZ from lg-firmwares.com, or one of the TWRP zips from xda. The KDZ for 10K is messed up, just look inside it and see. Among other things, it contains a misc.bin (not supposed to be there) which overwrites the one (unique) on you phone, thus erasing your WLAN mac address and other stuff, possibly affecting Bluetooth.
Before I bricked, I noticed this when I used my phone as FTP server, the IP address would change at every reboot. At that time I didn't know why, but assumed it was just some temporary bug with the stock rom.
LG screwed up again.
Edit: OK, @me2151 has just informed me that the problem might not have been caused by wiping misc partition after all. There may been some confusion on the matter. But remains to be seen I guess. @dimm0k may have some input.
Click to expand...
Click to collapse
I'm not entirely sure how a messed up misc partition would affect Bluetooth in general, as I'm usually using my phone to connect to headphones or car stereo, but with a messed up misc partition your Bluetooth address is no longer what it was when you first unboxed the device. see my post here if you're curious about the misc partition https://forum.xda-developers.com/showpost.php?p=73439967&postcount=14
De-bloat removes clock app. Without this there's no alarm. Can you add it back?
Sent from my SM-T810 using Tapatalk