Database Develop

random reboots after 24A Freedom tool or manual recovery installation

Since the 24A OTA dropped, I have been running the stock OTA, rooted using IOROOT with no issues, and exceptional stability. I have recently opted to make a second attempt at installing a custom recovery on 24A (last time, I used the manual method posted by jackpotclavin in the CM11 based on 24A thread). This time I used the Freedom 24A script.
In both instances, I immediately wound up with an unstable phone (no roms had been flashed at this point, still the stock (rooted) OTA but now with custom recovery installed and the modified aboot and laf partitions. The phone went from being rock solid with no random reboots to experiencing 2-3 random reboots per day.
I've since tested a couple of 4.4.2 ROMS to see if any would be stable on my phone, and so far have not found one. I have tried JackpotClavin's CM11 based on 24A, Beanstalk (may 27 build), C-Rom 6.5 and 6.6 and all exhibit the same random reboots.
What (if anything) can I do to bring some stability to the phone. I can always go back to stock, but I'd really like to cut out some of the bloat and run a stock-ish android ROM.
Any suggestions on what I can do to find out what is crashing the phone?

themortalwombat said:
Since the 24A OTA dropped, I have been running the stock OTA, rooted using IOROOT with no issues, and exceptional stability. I have recently opted to make a second attempt at installing a custom recovery on 24A (last time, I used the manual method posted by jackpotclavin in the CM11 based on 24A thread). This time I used the Freedom 24A script.
In both instances, I immediately wound up with an unstable phone (no roms had been flashed at this point, still the stock (rooted) OTA but now with custom recovery installed and the modified aboot and laf partitions. The phone went from being rock solid with no random reboots to experiencing 2-3 random reboots per day.
I've since tested a couple of 4.4.2 ROMS to see if any would be stable on my phone, and so far have not found one. I have tried JackpotClavin's CM11 based on 24A, Beanstalk (may 27 build), C-Rom 6.5 and 6.6 and all exhibit the same random reboots.
What (if anything) can I do to bring some stability to the phone. I can always go back to stock, but I'd really like to cut out some of the bloat and run a stock-ish android ROM.
Any suggestions on what I can do to find out what is crashing the phone?
Click to expand...
Click to collapse
Strange that jackpotclavins recovery installation method didn't work. That's the same method I used after manually updating to KK and haven't had probs. When you installed recovery using his method, did you use your computer or terminal on your phone? For me, I downloaded terminal from the at store and did all the commands on my phone. Everything installed perfectly. Also, did you make sure to check the md5 on all files after downloading?

[Q] suggestion for update ota and os for vs98012b

hi all, I'm a little lost on what to do. I'm trying to update my phone because I'm not receiving texts out of town (need to reset my phone to get them all every time).
My phone has the following:
android 4.2.2 vs98012b (verizon)
rooted w twrp installed (and I'm guessing some sort of ota block since it hasn't updated)
What I want to do is update my phone so it can get texts out of town so I'm thinking OTA? I've searched and found
VS98024A - OTA manual install + Patched Stock Kernels (http://forum.xda-developers.com/showthread.php?t=2699123), is this the way to go?
Is there a flash I can just use? I don't need the latest OTA or Android OS since I'm fine with what I'm using now (although that would be nice too).
anyways, a point in the right direction would be much appreciated. thanks!

ponso said:
hi all, I'm a little lost on what to do. I'm trying to update my phone because I'm not receiving texts out of town (need to reset my phone to get them all every time).
My phone has the following:
android 4.2.2 vs98012b (verizon)
rooted w twrp installed (and I'm guessing some sort of ota block since it hasn't updated)
What I want to do is update my phone so it can get texts out of town so I'm thinking OTA? I've searched and found
VS98024A - OTA manual install + Patched Stock Kernels (http://forum.xda-developers.com/showthread.php?t=2699123), is this the way to go?
Is there a flash I can just use? I don't need the latest OTA or Android OS since I'm fine with what I'm using now (although that would be nice too).
anyways, a point in the right direction would be much appreciated. thanks!
Click to expand...
Click to collapse
You need to wipe your phone to out of the box stock to use that method, if you're gonna wipe clean, you might as well take the OTA's to the current version of android on our phones.
Another option is this - http://forum.xda-developers.com/showthread.php?t=2715408
You would just need to update your baseband following the instructions in the post then install the rom via TWRP.
Either way you're gonna be wiping your phone clean.

Thank you. I went with the 2nd option and my phone is running great with the update.
Although it took awhile to reconfigure everything back.
mjones73 said:
You need to wipe your phone to out of the box stock to use that method, if you're gonna wipe clean, you might as well take the OTA's to the current version of android on our phones.
Another option is this - http://forum.xda-developers.com/showthread.php?t=2715408
You would just need to update your baseband following the instructions in the post then install the rom via TWRP.
Either way you're gonna be wiping your phone clean.
Click to expand...
Click to collapse

[Q] SYSTEM UI issues; How come I cannot install any "ghost" rom?

PRIMARY QUESTION: I cannot seem to install any "ghost" KitKat or Lollipop ROM on my XT1058. Can anyone please help shed some light on this? I've spent around a combined 12+ hours searching, researching, and tinkering trying to figure this out, but no success. I typically receive a "com.android.systemui" error message or "Unfortunately, System UI has stopped" message. After I acknowledge the message, it pops up again in a second or two. I have to force a shutdown of the phone and recover via TWRP. I've detailed my history and attempts below.
On the CM website, it says something about how "ghost" is a unified OS for every Moto X, except AT&T, since it's not unlockable. With Sunshine, shouldn't I be able to install the "ghost" ROM? Or does it not matter? I hope this isn't a case of, "even though you have an unlocked bootloader, the 'ghost' ROM isn't intended for your version of the phone." If that's true, it looks like all development on the XT1058 has pretty much stopped.
Many thanks, XDA Community, for helping me understand all this!
Secondary Questions:
I recently tried using the feature, "fixing permission" in TWRP thinking it might help with the "ghost" installations. I started getting bootloops when trying to restore to previous ROMs. The only restore that worked was my true original stock backup; the other restore attempts on SlimKat and other stock instances failed. That worries me. While I have successfully restored my phone, does anyone know if I may have screwed up my phone for the long-term?
(Answered by KidJoe; thank you!) Since I unlocked my bootloader at 4.2.2, can I freely upgrade and downgrade stock OSs? i.e., Can I install AT&T's stock 4.4.4 and then downgrade to 4.4.2?
(Answered by KidJoe; thank you!) Why do so many people seem to care to downgrade their stock OS? While I'm sure some may not be happy with some changes that come with upgrades, what could possibly be so "upsetting" that people need to downgrade?
HISTORY
Phone: AT&T Moto X XT1058, non-developer edition
Android: 4.2.2 | No attempt has been made to upgrade the OS beyond 4.2.2
Used Sunshine to unlock the bootloader while still on 4.2.2
Recovery: Installed TWRP v2.8.1.0, and I use TWRP to backup and install old and new ROMs (I think it's version 2.8.3... I never downloaded a version 2.8.1, but that's what the screen says. I'm wondering if the authors just forgot to update the version number in the program.)
Successful ROM installs:
SlimKat build 7 Official, msm8960dt
Cyanogenmod 11 Snapshot M5 msm8960dt (2014-04-05)
Failed ROM installs:
Cyanogenmod 11 Snapshot M12 ghost (2014-11-15)
Cyanogenmod 11 Nightly ghost (2014-12-19)
LiquidSmooth KitKat v3.2 Nightly ghost (2014-10-31)
LiquidSmooth Lollipop v4.0 Nightly ghost (2014-12-20)
Other Notes:
GApps were always installed when available. I also tried not installing them.

cxwong1 said:
Many thanks, XDA Community, for helping me understand all this!
Secondary Questions:
Since I unlocked my bootloader at 4.2.2, can I freely upgrade and downgrade stock OSs? i.e., Can I install AT&T's stock 4.4.4 and then downgrade to 4.4.2?
Why do so many people seem to care to downgrade their stock OS? While I'm sure some may not be happy with some changes that come with upgrades, what could possibly be so "upsetting" that people need to downgrade?
Click to expand...
Click to collapse
I will answer these two....
1. NO you can not. Once you have 4.4.2, 4.4.3 or 4.4.4 on your phone, do NOT attempt to downgrade, even if you have an unlocked bootloader... For more details see what I typed here -> http://forum.xda-developers.com/moto-x/general/4-4-4-downgrade-possibility-t2971847/post57563419 along with the other discussions in that SHORT thread.
2. The older root and write protection disable processes for a Moto X with a locked bootloader (like ATT and Verizon) rely on taking advantage of vulnerabilities in the 4.2.2 w/Camera update rom version, or the 4.4 rom. These processes walk you through downgrading your ROM to 4.2.2 w/Camera update and following a set of steps to upgrade which will keep root and disable write protection. NOTE: It was safe to downgrade from 4.4. to 4.2.2 w/Camera update when following the SlapMyMoto/MotoWpNoMo processes. But that was the only time it was safe!!!!

KidJoe, thank you much!
Does anyone else have any idea about my "systemui" issue?

cxwong1 said:
KidJoe, thank you much!
Does anyone else have any idea about my "systemui" issue?
Click to expand...
Click to collapse
Just got a Moto X 1st gen replacement from Motorola and getting same problem after unlocking/rooting. Have you found a fix for this? Or does anyone know how to fix? Spent all day working on this and its driving me nuts.

syckman said:
Just got a Moto X 1st gen replacement from Motorola and getting same problem after unlocking/rooting. Have you found a fix for this? Or does anyone know how to fix? Spent all day working on this and its driving me nuts.
Click to expand...
Click to collapse
Hey! Nope, I haven't found the answer, unfortunately. I haven't really tried to upgrade my OS since.

cxwong1 said:
PRIMARY QUESTION: I cannot seem to install any "ghost" KitKat or Lollipop ROM on my XT1058. Can anyone please help shed some light on this?
Click to expand...
Click to collapse
I bit the bullet yesterday and paid for the Sunshine bootloader unlock. After replacing the stock bootloader with TWRP and making a backup, I started looking into putting CyanogenMod onto it, as I had just updated a Galaxy Tab 2 7.0 to KitKat (via CyanogenMod 11) last week and it wasn't right that my phone had an older Android build than my tablet. I ran into conflicting information here and elsewhere, but the bottom line:
I have CyanogenMod 11 running on my AT&T Moto X.
More specifically, it's this zipball (remove spaces in next line to bypass the forum's lame link blocking):
https :// download.cyanogenmod.org / get / jenkins / 90775 / cm-11-20141115-SNAPSHOT-M12-ghost.zip
I also tried the latest 12.1 nightly, but while it appears to boot up, it reboots almost as soon as you try to set it up.
One thing that seems to help: before loading any ROM (whether stock, CyanogenMod, or whatever), wipe the flash. I have the ROM and Google Apps files on a flashstick that gets connected through an OTG cable, so I just tell TWRP to wipe everything but OTG storage, restore the ROM, let it boot up, then go back to TWRP to install the Google apps.
(Good thing I had the stock ROM backed up...had to revert to it this morning to back up aCar and Stocard data so I could bring them into CM.)
Starting configuration for my phone: AT&T XT1058, stock 4.4 firmware, rooted with the usual means for doing so, bootloader locked until Sunshine worked its magic.

[Q] Rooted 5.0.1, OTA update to T-mo 5.1 offered, failed. How to proceed?

Hello everyone. My Nexus 6 has been running standard 5.0.1, which I rooted (using WugFresh's Nexus Root Toolkit - very useful software) . SuperSU has been installed, along with BusyBox, with TWRP as the custom recovery. My service is on T-Mobile, and just today my system update informed me that the 5.1 OTA update was ready to download and install. I allowed it the right to download and it claimed to be rebooting to install. Unfortunately, it rebooted into TWRP (I am guessing it expected the standard recovery)? I told TWRP it to simply reboot into the OS, and it appear the update has failed - nothing has changed. I'm still on 5.0.1 as shown in the settings etc.. Furthermore, attempting to check for System Updates again show no updates available; it seems it has "forgotten" that OTA 5.1 exists and/or assumes that it has already been pulled down properly? This is my first time updating a stock, yet rooted, ROM - I'm used to flashing or using another update system included in custom ROMs such as Cyanogen . I had hoped that since the OTA update was offered, it would have worked without the necessity to wipe my data as in a normal flash. I am guessing the error was in using the OTA update at all, or perhaps having TWRP installed? So I guess I am trying to figure out the best path forward from here.
I am to understand that the T-Mobile OTA 5.1 update activates a number of new features ,including VOLTE etc... so I want to be sure I get the correct ROM, as well as any baseband changes that may be necessary. I still have TWRP and the like, so I assume I could flash the update manually, if I was sure it was the right build and I got all the needed files. Now, I have to wonder, it appears that during the original OTA update, it did download the ROM somewhere. Perhaps I could find it on my device and select it in TWRP to update? Or would that not provide all the necessary files , overwrite something, or otherwise cause problems? Anyone point me in the correct direction perchance? Thanks.
Edit: I may have not been prompted for another OTA update because my battery was < 50%. Plugging it in and seeing if this changes anything. I read on Tmo's page that >50% battery is necessary to "qualify" for the update?
Also, according to https://support.t-mobile.com/docs/DOC-18109 - the Tmo 5.1 is "LMY47M". This build is not available yet at https://developers.google.com/android/nexus/images - only the "D" and "E" versions. Does this "M" version include VoLTE calling? I'm seeing discussion about these differing versions, yet very little solid information. I can't believe Google would split the ROM by carrier for a Nexus device! That's insane... having to look for all the custom ROMs that are built with the proper carrier specific build in mind!

a phone that is pure stock can take an ota. a phone that has any files changed, or not pure stock can not flash an ota, doesnt matter how many otas you try. you will have to flash the factory img.

So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.

RanceJustice said:
So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.
Click to expand...
Click to collapse
you cant flash it in twrp. you can flash the factory img via fastboot while youre in the bootloader. or you can flash a 5.1 custom rom, that will be easier.

RanceJustice said:
So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.
Click to expand...
Click to collapse
If you want to take the OTA, do the following:
Download the 5.0.1 factory zip.
Extract all of the files.
To unroot, fastboot flash the system.img.
Fastboot flash the stock recovery.img.
If you are unencrypted, fastboot flash the stock boot.img.

RanceJustice said:
Hello everyone. My Nexus 6 has been running standard 5.0.1, which I rooted (using WugFresh's Nexus Root Toolkit - very useful software) . SuperSU has been installed, along with BusyBox, with TWRP as the custom recovery. My service is on T-Mobile, and just today my system update informed me that the 5.1 OTA update was ready to download and install. I allowed it the right to download and it claimed to be rebooting to install. Unfortunately, it rebooted into TWRP (I am guessing it expected the standard recovery)? I told TWRP it to simply reboot into the OS, and it appear the update has failed - nothing has changed. I'm still on 5.0.1 as shown in the settings etc.. Furthermore, attempting to check for System Updates again show no updates available; it seems it has "forgotten" that OTA 5.1 exists and/or assumes that it has already been pulled down properly? This is my first time updating a stock, yet rooted, ROM - I'm used to flashing or using another update system included in custom ROMs such as Cyanogen . I had hoped that since the OTA update was offered, it would have worked without the necessity to wipe my data as in a normal flash. I am guessing the error was in using the OTA update at all, or perhaps having TWRP installed? So I guess I am trying to figure out the best path forward from here.
I am to understand that the T-Mobile OTA 5.1 update activates a number of new features ,including VOLTE etc... so I want to be sure I get the correct ROM, as well as any baseband changes that may be necessary. I still have TWRP and the like, so I assume I could flash the update manually, if I was sure it was the right build and I got all the needed files. Now, I have to wonder, it appears that during the original OTA update, it did download the ROM somewhere. Perhaps I could find it on my device and select it in TWRP to update? Or would that not provide all the necessary files , overwrite something, or otherwise cause problems? Anyone point me in the correct direction perchance? Thanks.
Edit: I may have not been prompted for another OTA update because my battery was < 50%. Plugging it in and seeing if this changes anything. I read on Tmo's page that >50% battery is necessary to "qualify" for the update?
Also, according to https://support.t-mobile.com/docs/DOC-18109 - the Tmo 5.1 is "LMY47M". This build is not available yet at https://developers.google.com/android/nexus/images - only the "D" and "E" versions. Does this "M" version include VoLTE calling? I'm seeing discussion about these differing versions, yet very little solid information. I can't believe Google would split the ROM by carrier for a Nexus device! That's insane... having to look for all the custom ROMs that are built with the proper carrier specific build in mind!
Click to expand...
Click to collapse
Please take a bug report and find the OTA link inside. Instructions here: https://www.reddit.com/r/nexus6/comments/2zlqid/psa_if_you_receive_the_tmobile_51_ota_update/

[ROM] 5.0.2 Stock-ROM - LG D415 L90

I am not responsible for bricked devices. Follow these steps at your own RISK! :angel:
Flashing this ROM will install the STOCK Android 5.0.2 OS From LG & T-Mobile.
This is only intended for use on the LG L90 D415 (T-Mobile Variant)
I've tested and everything works just fine. Just be sure to flash the SuperSU zip I've also provided. otherwise you WILL lose root!
I ASSUME YOU ALREADY HAVE BEEN FLASHING ROMS ON YOUR DEVICE AND ALREADY HAVE A CUSTOM RECOVERY INSTALLED!
I'm currently running a TWRP flashable version of the Official Lollipop update for the D415 L90 Optimus, or as I call it, the LollipOptimus! LOL
Rooted and all!
In post #3 there are links to my downloads. :laugh:
thanks to: @DevoutDevelopment for advice!
& @shoxxy for twrp!
Thanks to LG for updating this mid-range device!
Thank you to the L90 community! :highfive: You guys ROCK!
XDA:DevDB Information
D415 Lollipop STOKK-ROM [Recovery Flashable], ROM for the LG Optimus L90
Contributors
brossovitch
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: LGE L90 D415 (w7)
Based On: Stock LG/TMO OTA
Version Information
Status: Stable
Current Stable Version: D415-LolliSTOKK
Stable Release Date: 2015-04-15
Created 2015-04-09
Last Updated 2015-04-15

Reserved
For this Rom to flash and function properly you need:
An LG Optimus D415 (T-Mobile USA) which has a custom recovery installed.
As far as the boot loader being unlocked.... I never had the LG bootloader to begin with, only fastboot.
The current functioning ROM is FULL stock. You must flash SuperSU before rebooting or you will lose ROOT!
**************INSTRUCTIONS*****************
First download all three files in the next post. they are:
1. ROM Zip (LG/TMO packed by me.)
2. SuperSU update Zip (Mediafire)
3. TWRP.img (shoxxy)
++Ensure you have TWRP installed.++
Then do this:
1. Reboot into TWRP (CWM works too, I reccomend Shoxxys TWRP)
2. Flash ROM
4. Flash SuperSU zip to keep ROOT
5. Factory reset via TWRP
6. Reboot
You're DONE!
It will take several minutes to begin booting, be patient. You MAY see the LG logo for a minimum of 5 minutes, don't freak out!
************************************************** ************************************************** **************************************************
FRIENDLY HEADS UP:
The Stock ROM file is more than 1GB (1.07gb actually) so you'll need to have enough free space on your SDcard.
YES, I reccomend flashing it from the External SD Card.
******************************************************
Stock LG Lollipop unrooted?
Just follow this simple tutorial:
http://highonandroid.com/android-smartphones/how-to-root-lg-g-flex-2-g2-g3-on-lollipop/
*****************************************
If you need a way to install TWRP from the device and you are rooted I HIGHLY recommend RASHR:
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools&hl=en
Godspeed to you all. PM me if you have issues. But I'm not responsible for your decisions!

DOWNLOADS
*******************************************
LG L90 D415 Lollipop Stock LG ROM​******************************************
***************************************************************************************************************
TWRP by @shoxxy :
https://mega.co.nz/#!w9kjwaxY!xzJUOWd_BErk-F3_mAHAz3JUaVfypy1hFjffBoJOrxQ
(Mirror link on my MEGA account with permission from Shoxxy, you may not do the same..)
Updated: 04/27/2015
______________________________
Shoxxy's TWRP Thread (GO GIVE SOME THANKS):
http://forum.xda-developers.com/lg-l90/development/recovery-twrp2-7-1-0lgl90w7xxshoxx-t2826150
***************************************************************************************************************
SuperSU v2.46:
https://mega.co.nz/#!gotQHIpJ!aFb-3XvJQjav6ASo79G24dEgpVvOpWutnGbmMZWUVS8
***************************************************************************************************************
STOCK ROM:
https://mega.co.nz/#!QhNBjaYS!6H4_HX7wMW5zy7rs2FgNRpvj2eBfZW6OSxLZ3kP9nno
Updated: 04/16/2015 @ 05:23am
There is an issue with baseband coming from KK based ROMs.
There are work arounds.
**************************************************************************************************************
All file access to my L90 folder on MEGA:
https://mega.co.nz/#F!FgVjna7T!DA9yydBcB0PIk9UxeVZXzw
**********************************************************************************************************************
+LG FLASH TOOL THREAD:
> http://forum.xda-developers.com/showthread.php?t=2797190
(o^;^o)

LollipOptimus™
I have put together a modified version of this ROM. It's the stock OS with many changes..
Debloated and trimmed to where it is as MY daily driver..
It's stable, smooth, and functional. There are many things removed, like the quick memo app and quick remote app, I will not put them back in. You could just trial and error debloat the system on your own, like I did this week..
Anyway, here's the ROM:
https://mega.co.nz/#!B4EEXZxZ!40XcuPjeFMUVcW0TpAOeQwVkuZNNCzs9OtH9V-TJVl4
There will be updates made periodically. It's not fully done yet, IMO.
Make a nandroid before flashing this! Just in case!
Let me know immediately if there are any issues!

I'm so ready for this. I can finally have my camera back.

This is gonna be too good. Thanks for all the legwork so lazy bums like myself can enjoy the goodness.

nemesis101x said:
I'm so ready for this. I can finally have my camera back.
Click to expand...
Click to collapse
The Camera works! everything except the baseband for some reason...
I'm going to figure this out.
then provide a link to the ROM and SUPERSU zip to ensure you stay rooted.
I had some problems and the zip I made accidentally flashed the stock boot loader, OH NO!
adb reboot fastboot
then
fastboot flash recovery twrp.img
YAY I learned things today!

brossovitch said:
The Camera works! everything except the baseband for some reason...
I'm going to figure this out.
then provide a link to the ROM and SUPERSU zip to ensure you stay rooted.
I had some problems and the zip I made accidentally flashed the stock boot loader, OH NO!
adb reboot fastboot
then
fastboot flash recovery twrp.img
YAY I learned things today!
Click to expand...
Click to collapse
Baseband
I had this problem with stock kitkat.... I think it was my META file or my ubuntu giving me problems at that time

Razer206 said:
Baseband
I had this problem with stock kitkat.... I think it was my META file or my ubuntu giving me problems at that time
Click to expand...
Click to collapse
How did you fix this problem?

brossovitch said:
How did you fix this problem?
Click to expand...
Click to collapse
I never did somebody had already release deodexe KitKat back last Dec.... So I delete my Lil project
Check your boot img, could be giving problems
What tool did you use to pull systems files from kdz? I will upload mines if you wanna see them

Razer206 said:
I never did somebody had already release deodexe KitKat back last Dec.... So I delete my Lil project
Check your boot img, could be giving problems
What tool did you use to pull systems files from kdz? I will upload mines if you wanna see them
Click to expand...
Click to collapse
I used the LG firmware extraction tool.
I've fixed the issued! Uploading SOON!

Currently debloating. I will release debloated with SUPERSU and busybox preinstalled. I'm not going to deodex, I'll leave that to the individual.
This ROM is amazing. LG is really out doing themselves!
As it stands, my ROM is 1.07GB as a zip. I'm timming it down. Hoping to get somewhere nearer to 700mb..
Keep your eye's peeled. It's coming!

brossovitch said:
Currently debloating. I will release debloated with SUPERSU and busybox preinstalled. I'm not going to deodex, I'll leave that to the individual.
This ROM is amazing. LG is really out doing themselves!
As it stands, my ROM is 1.07GB as a zip. I'm timming it down. Hoping to get somewhere nearer to 700mb..
Keep your eye's peeled. It's coming!
Click to expand...
Click to collapse
You see deodex lollipop is crazy long, and lollipop throwing issues...
. I don't blame you, do the best you can

I'm currently running a TWRP flashable version of the Official Lollipop update for the D415 L90 Optimus, or as I call it, the LollipOptimus! LOL
Rooted and all!
Click to expand...
Click to collapse
Could you do TWRP or CWM flashable version of the Official Lollipop update for the D410 L90 Optimus?

brossovitch said:
Currently debloating. I will release debloated with SUPERSU and busybox preinstalled. I'm not going to deodex, I'll leave that to the individual.
This ROM is amazing. LG is really out doing themselves!
As it stands, my ROM is 1.07GB as a zip. I'm timming it down. Hoping to get somewhere nearer to 700mb..
Keep your eye's peeled. It's coming!
Click to expand...
Click to collapse
I know, that if i will flash twrp on stock lollipop D410 it will be bricked. Are U changing loader to avoid this? Or u create flashable 5.0.2 that working on older loaders?

Andruxa666777 said:
I know, that if i will flash twrp on stock lollipop D410 it will be bricked. Are U changing loader to avoid this? Or u create flashable 5.0.2 that working on older loaders?
Click to expand...
Click to collapse
Nope, none of that.
I will say this, @Quarx has a Lollipop CWM recovery if you're worried about recovery compatibility....
I honestly prefer to use the FLAWLESS TWRP from @shoxxy .........I mean, it's simply the best!
I flashed via TWRP with no problems whatsoever/
I flash the ZIP, then SuperSU.zip, then just to be extra safe I reflashed the TWRP.IMG from recovery.
then I rebooted recovery to ensure TWRP was installed.
then simply rebooted the system...
everything worked great so far.
I just want to test it a few more times and make sure I don't kill anyone elses device. I had a WiFi only phone for a good 7hrs. nobody should have to deal with that.
I bricked this device several times today already, i need to ensure everything is working well before I have someone test.
I currently have a few people in mind to test. if they agree and try it out with no problems, it will be free for the taking!

Should I leave it stock with GApps? or remove all the GApps so users can flash their own..?

I say remove all gapps so we can flash our own.
Might give a little bit of freedom for the users. But I don't really care! I wanna try this out!

brossovitch said:
Nope, none of that.
I will say this, @Quarx has a Lollipop CWM recovery if you're worried about recovery compatibility....
I honestly prefer to use the FLAWLESS TWRP from @shoxxy .........I mean, it's simply the best!
I flashed via TWRP with no problems whatsoever/
I flash the ZIP, then SuperSU.zip, then just to be extra safe I reflashed the TWRP.IMG from recovery.
then I rebooted recovery to ensure TWRP was installed.
then simply rebooted the system...
everything worked great so far.
I just want to test it a few more times and make sure I don't kill anyone elses device. I had a WiFi only phone for a good 7hrs. nobody should have to deal with that.
I bricked this device several times today already, i need to ensure everything is working well before I have someone test.
I currently have a few people in mind to test. if they agree and try it out with no problems, it will be free for the taking!
Click to expand...
Click to collapse
no, i mean that you are creating flashable 5.0.2, that will be flashing from recovery on 4.4.2 phone аnd after flashing recovery still properly working? It is?
But the official firmware via LG Support tool reflashes boot, aboot,laf,recovery,system folder etc. Does this mean that your firmware flashes only kernel, folders systems and data, but first levels of loading(like aboot) stay from older 4.4.2?

Andruxa666777 said:
no, i mean that you are creating flashable 5.0.2, that will be flashing from recovery on 4.4.2 phone аnd after flashing recovery still properly working? It is?
But the official firmware via LG Support tool reflashes boot, aboot,laf,recovery,system folder etc. Does this mean that your firmware flashes only kernel, folders systems and data, but first levels of loading(like aboot) stay from older 4.4.2?
Click to expand...
Click to collapse
No, this ROM will flash all those, then just flash SUPERSU and TWRP right behind it. it typically works. Try it out.
I uploaded a BETA, be careful!