Related
A malware in form of many apps have been identified lurking in android market. A patch is available for existing users and ROM cooks. More details here
http://forum.xda-developers.com/showthread.php?t=977154
Sent from my LG-P500 using XDA App
but if the exploit is based on rageagainstthecage method why it works on android 2.2.1 or 2.2.2?
I'm not sure. I've read around other forums and some have tried and gotten success with RATC using their PC. I'm not sure if 2.2.1 and 2.2.2 only breaks S1C and Z4
I'll rather be safe than sorry
If the exploit roots the phone and does bad stuff, what if the phone has already been rooted? Will superuser still prompt us that the specific program is trying to gain root access? I'll try installing a "bad app" that was listed on the thread link you gave xD
that was good... if you can find affected apps... it was completely removed from the market the 2nd day of its release.
i sure do want to try this too... just to test the waters
i guess a complete flash will kill the malware on the other hand *lol*
i thought 2.2.2 was created just to implement this patch?
well thats what wikipedia told me
10 charact
..........
Also reserved please
This sounds like something that can kill a lot if time while I'm in the office.
What are we looking for when doing this?
Sent from my DROID BIONIC using xda premium
ROB281 said:
This sounds like something that can kill a lot if time while I'm in the office.
What are we looking for when doing this?
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Well, I'll get to the point soon. still modifying the post. but basically the gist of it is to check ALL of motorola's update servers for updates, not just the one that comes programmed into the device. If we're lucky and we find a hidden update, we may be able to get an unlocked bootloader (or other goodies?), which will allow us to use our device as we please (new kernels, better mods, etc)
Thanks for writing this up, I've been hesitant to try it since some of the paths/files in other posts did not exist on the Bionic.
Sent from my DROID BIONIC using XDA App
karthakon said:
Thanks for writing this up, I've been hesitant to try it since some of the paths/files in other posts did not exist on the Bionic.
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Well, I was bold and basically just created the files. When I ran the *#*#4636#*#* test, I found that it did indeed change my could update server.
also the com.motorola.blur.setup was in /data/data/ and not the system/etc/motorola.
Thank you.
Sent from my ADR6400L using xda premium
Thank you for this. The previous directions were based on the Atrix so there were a lot of files listed that I never saw so I felt unsafe just making them up and moving things around. I'll get on this sometime in the very near future.
K.AuthoR said:
Thank you for this. The previous directions were based on the Atrix so there were a lot of files listed that I never saw so I felt unsafe just making them up and moving things around. I'll get on this sometime in the very near future.
Click to expand...
Click to collapse
I actually have been testing some methods that may not even req a wipe in between or possible before
Sent from my DROID BIONIC using Tapatalk
Apparently someone found an update somewhere. Good sign. I'm going to check it out in an hour or two. Don't have my hands on it yet.
Sent from my DROID BIONIC using Tapatalk
Looking at these right now. I'll go ahead and update the main thread with your corrections. Thank you for figuring it out!!!!
kennethpenn said:
Looking at these right now. I'll go ahead and update the main thread with your corrections. Thank you for figuring it out!!!!
Click to expand...
Click to collapse
when I hit the server, it says it's a 5.5.886 -> 5.5.891 update
phydo said:
when I hit the server, it says it's a 5.5.886 -> 5.5.891 update
Click to expand...
Click to collapse
Just so everyone can see it: the update label will always be for the build ID that the zip is supposed to be installed over. That means if you've got an update:
Blur_Version.1.XT875.Verizon.en.US.zip --> This means the zip should be installed over devices running Build number "1."
Blur_Version.5.5.886.XT875.Verizon.en.US.zip --> This means the zip should be installed over devices running Build number "5.5.886."
Was anyone ballsy enough to attempt to install the update? It doesn't have a bootloader inside, but it may still be dangerous.
P3 flashed it and it does absolutely contain a bootloader update.
The critical pieces are the mbm.bin, mbmloader_hs.bin and mbmloader_ns.bin.
HS and NS refer to Hardware Secure and Non Secure parts and both are included in these updates because both types of hardware are present in the test groups or whomever is the intended recipient of these files.
There is not an unlock, per se, but both secured and unsecured mbmloaders are present and the updater script has a check for the ro.secure status and loads the appropriate file for the target device.
The D3 update and assumedly this file as well cannot be reverted to stock release version, so this file must be regarded very carefully and assessed before any decision to flash or not is made.
There is a LOT more discussion we need to have about these files and OMAP SoCs I think regarding the differences between them and the Tegra II SoCs and fuse arrays!
Edit: This breaks the djrbliss root method using the tcmd exploit. We need to look further and discuss with him other possibilities for root. Reverting has not been established yet and may brick since we dont have a complete XML.zip.
WARNING!!!! This is a very dangerous file to flash at this stage!!! Please do not rush into testing it yet!!!
Thanks to those who got the file and thanks to P3Droid for guinea pigging.
Oh and I have to add that clarified cheescake is an oxymoron...you garnish cheesecake with wonderful things!
cellzealot said:
P3 flashed it and it does absolutely contain a bootloader update.
The critical pieces are the mbm.bin, mbmloader_hs.bin and mbmloader_ns.bin.
HS and NS refer to Hardware Secure and Non Secure parts and both are included in these updates because both types of hardware are present in the test groups or whomever is the intended recipient of these files.
There is not an unlock, per se, but both secured and unsecured mbmloaders are present and the updater script has a check for the ro.secure status and loads the appropriate file for the target device.
The D3 update and assumedly this file as well cannot be reverted to stock release version, so this file must be regarded very carefully and assessed before any decision to flash or not is made.
There is a LOT more discussion we need to have about these files and OMAP SoCs I think regarding the differences between them and the Tegra II SoCs and fuse arrays!
Edit: This breaks the djrbliss root method using the tcmd exploit. We need to look further and discuss with him other possibilities for root. Reverting has not been established yet and may brick since we dont have a complete XML.zip.
WARNING!!!! This is a very dangerous file to flash at this stage!!! Please do not rush into testing it yet!!!
Thanks to those who got the file and thanks to P3Droid for guinea pigging.
Oh and I have to add that clarified cheescake is an oxymoron...you garnish cheesecake with wonderful things!
Click to expand...
Click to collapse
So I decided that I just couldn't sleep not knowing if the root patch had been fixed. So I decided to flash the update.zip. And what I expected to happen, happened, it zapped the local.prop exploit.
So here I sit on the new build unrooted and stock. I'm fairly certain that if I try to revert back to the OG build I will have a paper weight on my desk until a full xml fastboot file can be found. I would suggest you all wait and don't flash this yet.
jimmydafish said:
So I decided that I just couldn't sleep not knowing if the root patch had been fixed. So I decided to flash the update.zip. And what I expected to happen, happened, it zapped the local.prop exploit.
So here I sit on the new build unrooted and stock. I'm fairly certain that if I try to revert back to the OG build I will have a paper weight on my desk until a full xml fastboot file can be found. I would suggest you all wait and don't flash this yet.
Click to expand...
Click to collapse
thats what i call takin one for the team!!! thanks bro!!! You'll be rooted again in no time, maybe even s-off!!!
Enzopreme said:
thats what i call takin one for the team!!! thanks bro!!! You'll be rooted again in no time, maybe even s-off!!!
Click to expand...
Click to collapse
S-off doesn't apply to Moto products...
Sent from my DROID BIONIC using xda premium
cellzealot said:
P3 flashed it and it does absolutely contain a bootloader update.
The critical pieces are the mbm.bin, mbmloader_hs.bin and mbmloader_ns.bin.
HS and NS refer to Hardware Secure and Non Secure parts and both are included in these updates because both types of hardware are present in the test groups or whomever is the intended recipient of these files.
There is not an unlock, per se, but both secured and unsecured mbmloaders are present and the updater script has a check for the ro.secure status and loads the appropriate file for the target device.
The D3 update and assumedly this file as well cannot be reverted to stock release version, so this file must be regarded very carefully and assessed before any decision to flash or not is made.
There is a LOT more discussion we need to have about these files and OMAP SoCs I think regarding the differences between them and the Tegra II SoCs and fuse arrays!
Edit: This breaks the djrbliss root method using the tcmd exploit. We need to look further and discuss with him other possibilities for root. Reverting has not been established yet and may brick since we dont have a complete XML.zip.
WARNING!!!! This is a very dangerous file to flash at this stage!!! Please do not rush into testing it yet!!!
Thanks to those who got the file and thanks to P3Droid for guinea pigging.
Oh and I have to add that clarified cheescake is an oxymoron...you garnish cheesecake with wonderful things!
Click to expand...
Click to collapse
I suppose I was looking for the wrong things. On other devices, "ap20bl.img" was responsible for bringing such goodies as an unlock capability.
Hello,
Here is developed a small software who work on Windows called NexusLight, which allows you to create a ROM for your needs from the flash.
He was appointed NexusLight because I have only tested on the Nexus, but it should work with all phones / roms if the signature verification is disabled in the recovery.
This is actually an adaptation of the software GaospLight (frandroid forum) I had created for the Galaxy's first name.
It allows you to remove applications from the ROM but also to add.
The software interface is in French but in English except for description of the applications (in fact it is the language depending on the language of the OS)
Moreover a video presentation is often better than a thousand words I have made a video where you see the software in operation:
http://www.youtube.com/embed/eNXXEGTUnQA
Download Link
The program will automatically update itself if a higher version available.
Warning: Some antivirus software can detect as malware.
But it is totally wrong is due to the UPX compression when compiling software.
GalaxyUser
NB: I can't post un dev' forum because i'm a new member
Isn't it easier to use 7-zip or WinRAR to open the zip and add/remove any apks you want?
Does Zipping Unizpping Works ? Never tried it to asking ?
So...wow...
Umm?
Sent from my Nexus S 4G using XDA App. Developer of brickROM, and OP of XDA Thread of The Year 2011.
wpxbox said:
Does Zipping Unizpping Works ? Never tried it to asking ?
Click to expand...
Click to collapse
You don't have to actually unzip the package. Just open it and add/remove apks from there. Though I think unzipping and re-zipping should work too
I agree this app is sort of silly since you can easily do the same thing with winrar/7zip. It might be useful if more features were added to it (e.g. change the kernel, change the boot animation, etc), until then...
7zip.
One zip to rule them all.
Sent from my SGH-T959 using xda premium
Hi,
Here is CM-11 (Android 4.4.4) for the kindle fire hdx 7" (THOR). You need a rooted hdx 7" (Thor) device with a firmware < 3.2.4 (3.2.3.2 ideally) and a signed recovery.
Todo
Bluetooth not working
Wifi won't correctly load when disabled at boot, a reboot is required
Minimal headphone volume too loud -> fixed
Incorrect color format in some scenario's ? (YouTube) -> fixed
Changelogs/Downloads
cm-11-20150226-UNOFFICIAL-thor.zip
Updated to amazon 4.5.3 binaries
Fully disable radio for now (thanks Andy-Voigt)
Fix twrp fstab (enabling twrp was breaking system rom to boot)
CM sources updated to 20150226
cm-11-20150219-UNOFFICIAL-thor.zip
CM sources updated to 20150219
cm-11-20150219-UNOFFICIAL-thor.zip
fix minimal video/media volume too high (youtube...)
switch back to tablet build
CM sources updated to 20150110
cm-11-20150108-UNOFFICIAL-thor.zip
Fix thermal engine (should give better battery life and performances)
Fix a lot of proprietary services (proprietary logs, acdb-loader, ril loading ...)
Set media volume steps to 100 instead 15 (allow finer volume control essentially for jack output)
Lowered minimal screen brightness
CM sources updated to 20150108
cm-11-20150107-UNOFFICIAL-thor.zip
Build without "hacks" (add Cuber signing and custom updater-script generation)
CM sources updated to 20150107
Enable telephony (will probably not work)
cm-11-20150101-UNOFFICIAL-thor.zip
use patched boot/recovery, thanks to @vortox
fix wrong color format ! (major bug resolved)
switch to kernel sources
cm-11-20141218-UNOFFICIAL-thor.zip
minors fixes
cm-11-20141217-UNOFFICIAL-thor.zip
fix wifi not reloading
fix overlay/rotation screen tearing
cm-11-20141216-UNOFFICIAL-thor.zip
updated binaries to amz 4.5.2
properly use precompiled kernel and headers (amz 4.5.2)
fix minimal audio volume too high
add safestrap compatibility
Sources
android_device_amazon_thor
android_device_amazon_hdx-common
hardware_qcom_display-caf-hdx
hardware_qcom_audio-caf-hdx
hardware_qcom_media-caf-hdx
I'm sure the community here respects all of the work that you do. My post in the other thread was not intended to "get you in trouble". There are a set of rules that every user has to follow, regardless of their contributions to the community. That being said, when I was a newer member, I accidentally broke the rules a couple of times (nothing major) and didn't want the same to happen to someone else. (I never contacted @Divine_Madcat about your other thread, in case you were thinking I did.)
r3pwn said:
I'm sure the community here respects all of the work that you do. My post in the other thread was not intended to "get you in trouble". There are a set of rules that every user has to follow, regardless of their contributions to the community. That being said, when I was a newer member, I accidentally broke the rules a couple of times (nothing major) and didn't want the same to happen to someone else. (I never contacted @Divine_Madcat about your other thread, in case you were thinking I did.)
Click to expand...
Click to collapse
Yep i was tinking to that... so I'm also sorry. The thing is i spent a lot, lot of time on this port, and Divine_Madcat didn't even give me the time to update the first thread with the needed files/informations and ignore my pm which was an offense to me. Well i have to complies to the rules too but was a little chocked on how the thread got mad. Well, let's hope it won't be the same here. So that said i have no problem with you !
Cpasjuste said:
Yep i was tinking to that... so I'm also sorry. The thing is i spent a lot, lot of time on this port, and Divine_Madcat didn't even give me the time to update the first thread with the needed files/informations and ignore my pm which was an offense to me. Well i have to complies to the rules too but was a little chocked on how the thread got mad. Well, let's hope it won't be the same here. So that said i have no problem with you !
Click to expand...
Click to collapse
While i am sorry you are upset, it was not a slight at you at all. While i do try to keep an eye on XDA while at work, my job does come first and foremost, and i was unable to handle anything here yesterday (what can i say, 12 hour work days suck). As it was, i have literally nothing against you; to be frank, the report on the thread was the first i had even seen.
From my perspective, we had a placeholder thread, which is not allowed, so it was closed. I fully intended to reopen it, but gave my reasons above...
Anyway, i do wish you luck, and i really dont have any ill will to you...
So....
Do we have unlocked bootloader or a root exploit for amazon firmware 4.5.2 soon? And do you have plan to release another for Apollo?
Thanks
tuanda82 said:
So....
Do we have unlocked bootloader or a root exploit for amazon firmware 4.5.2 soon? And do you have plan to release another for Apollo?
Thanks
Click to expand...
Click to collapse
Nobody knows. But there are a few people working on "unlocks" (at least booting an unsigned kernel). Maybe also jcase releases his unlock (which I doubt because of legal issues).
Hi!
I have rooted Kindle Thor. How do I install this nice piece of software?
Like the Nexus rom? Currently I am on 3.2.7...
Thanks
URBANsUNITED
URBANsUNITED said:
Hi!
I have rooted Kindle Thor. How do I install this nice piece of software?
Like the Nexus rom? Currently I am on 3.2.7...
Thanks
URBANsUNITED
Click to expand...
Click to collapse
You need to be on 4.5.2 and rooted.
cyablo said:
You need to be on 4.5.2 and rooted.
Click to expand...
Click to collapse
Mmmmmhhh
Than this rom is basically usless
Who has a 4.5.2 Base and Rooted??? I would do it if I'll get the tools, no fear of a brick
Too bad. But Nevertheless Many thanks for the work and effort!
URBANsUNITED said:
Mmmmmhhh
Than this rom is basically usless
Who has a 4.5.2 Base and Rooted??? I would do it if I'll get the tools, no fear of a brick
Too bad. But Nevertheless Many thanks for the work and effort!
Click to expand...
Click to collapse
There are a few Users which do have an unlocked Bootloader, this Rom is only for these Users, as stated in the first Post.
I decided to make the rom available in case i loose interest in this device (or if i ever die soon). This way when (if) a root exploit is available then you'll be ready to use it.
Ok... So if there IS a possibility to unlock the actual fireos, please give some hints, instead of publishings Roms that one or two users can install, the rest is completely helpless...
Sent from my Nexus HDX 7 using XDA Free mobile app
openWeb74 said:
Ok... So if there IS a possibility to unlock the actual fireos, please give some hints, instead of publishings Roms that one or two users can install, the rest is completely helpless...
Sent from my Nexus HDX 7 using XDA Free mobile app
Click to expand...
Click to collapse
Sharing hundreds of hours of work is helpless/useless for you ?
You know what ? I actually spent the whole day on porting cm-10 to current exploitable kernel for YOU :/
Everybody chill , @openWeb74, i see your point @Cpasjuste , first let me thank you for all your work, I'm pretty sure its a great Rom!
What openweb said was that maybe we should concentrate our efforts in unlocking the bootloader so even greater support can come.
Unfortunately we, the rest of us common mortals (with locked bootloaders) cannot use it.
As you said, this would work if somebody would release the bootloader-unlock , so lets play the waiting game...
The thing is I'm a common mortal like you :/ Like its said on first post, unfortunately, I do not have the tools nor the knowledge to reproduce the unlock, so I share what I can.
I really have to say sorry, if you dont know how to reproduce the hack... Mea culpa. It sounded like the hack is known, but cant be made public because of copyright issues or something like that... Then we have to wait. Nothing is secure when the right person gets a hdx... I have to say, that my actual hdx was rooted with towelroot, even easier than the nexus (less button combinations ) so i didnt expect amazon to be such a **** with newer firmwares.
Sent from my LG-D802 using XDA Free mobile app
Cpasjuste said:
The thing is I'm a common mortal like you :/ Like its said on first post, unfortunately, I do not have the tools nor the knowledge to reproduce the unlock, so I share what I can.
Click to expand...
Click to collapse
Sorry for nagging you about it, but — genuinely asking — how did you do it on your device in the first place?
dear Cpasjuste, thanks for your great work, and how to install this Rom ? I am newbie, so..
OK... So you are a newbie in reading too?
Sent from my Nexus HDX 7 using XDA Free mobile app
I may eventually move to another tablet as I'm loosing interest in this device (because cm is working fine [emoji14]). Would someone be interested to get my device (not for free )?
Hi all,
Today, I proudly present GomdoLight KitKat for KOREAN LG G / G2 / G3 / G3A / G3cat6 / Gflex / GK / Gpro / Gpro2 / LTE3 / Vu2 / Vu3 / Gpad7LTE, one of the most widely used (with 20,000+ users approximately) stock-based custom firmware in South Korea.
GomdoLight is more than 3 year old already (first version released on 19th December 2012), and is very mature.
Technically speaking GomdoLight is NOT a complete ROM, but rather a large-scale patch, which modifies official stock firmware to remove all the unnecessary components preloaded by operator/manufacturer, and reorganizes key system parts to 'basic' Android OS with manufacturer's flavor. For some devices GomdoLight's own specialized tool 'GomdoLight Sideloader' can make it possible to install GomdoLight directly over the stock firmware, even without rooting or flashing custom recovery!
GomdoLight is compatible with the following devices (BOLD indicates GomdoLight Sideloader support - no root required)
LG Optimus G: LG-F180S, LG-F180K, LG-F180L ("G")
LG G2: LG-F320S, LG-F320K, LG-F320L ("G2")
LG G3: LG-F400S, LG-F400K, LG-F400L ("G3")
LG G3A: LG-F410S ("G3A")
LG G3 Cat.6: LG-F460S, LG-F460K, LG-F460L ("G3")
LG G Flex: LG-F340S, LG-F340K, LG-F340L ("Gflex")
LG GK: LG-F220K ("GK")
LG G Pro: LG-F240S, LG-F240K, LG-F240L ("Gpro")
LG G Pro 2: LG-F350S, LG-F350K, LG-F350L ("Gpro2")
LG Gx: LG-F310L, LG-F310LR ("Gx")
LG Optimus LTE3: LG-F260S ("LTE3")
LG Optimus Vu2: LG-F200S, LG-F200K, LG-F200L ("Vu2")
LG Vu 3: LG-F300S, LG-F300K, LG-F300L ("Vu3")
LG G Pad 7.0 LTE: LG-V410 ("Gpad7LTE")
A very thorough and extensive (probably, the most extensive on entire xda) manual is provided at the download page, which contains literally everything you need to know to install GomdoLight. FAILURE TO READ THIS DOCUMENT BEFORE INSTALLING WILL ALWAYS LEAD TO VARIOUS UNEXPECTED PROBLEMS. PLEASE READ CAREFULLY. Needless to say, I WILL NOT ANSWER ANY QUESTIONS ALREADY ADDRESSED IN THIS DOCUMENT.
Due to xda forum's limits (in functionality) I am posting a link to the separate (external) DOWNLOAD PAGE. There is no way I can link to each section in the document in xda posts, since xda does not support HTML tag. However some portions of the document are also introduced here.
▶ GomdoLight Download / Manual Page
GomdoLight TUTORIALS:
Want to read the built-in user manual again?
Need help using GomdoLight Flag functions?
Installing an EasyMod package? (Sorry the tutorial is in Korean, but screenshots will help)
XDA:DevDB Information
GomdoLight KitKat, ROM for various LGE devices
Contributors
juniecho
ROM OS Version: 4.4.x KitKat
ROM Firmware Required: STOCK FIRMWARE (Firmware compatibility table available)
Based On: STOCK FIRMWARE
Version Information
Status: Stable
Current Stable Version: 4.0
Created 2015-02-26
Last Updated 2015-12-31
CHANGELOG for older versions
Version History:
2015. 12. 31. - Wave 4, initial release
UPDATE LEVEL: MAJOR / IMPORTANCE: VERY HIGH
CHANGELOG:
Oh god, have I abandoned this thread this long? So many changes, sorry, I can't list them all.
A lot of things are now even better than ever. Trust me.
[#GLKITKATCOMMONUPDATE]
EMERGENCY NOTICE, etc.
For some unknown reason I cannot access my DevDB variables at this time. Though G Flex is not on the list of supported devices right now, it IS supported.
* For those who have waited for a long time, sorry for being late, and thank you very much.
Will we see a port to d959 ever? If so and you need a tester pm me!
EDIT: For those wanting to try it did install, but very few bloat was actually removed and no gomdo apps were installed.
dmifsud44 said:
Will we see a port to d959 ever? If so and you need a tester pm me!
Click to expand...
Click to collapse
I'm not sure yet, but it may not be necessary. Because gomdolight is a large-scale patch mainly focusing on script-driven features, just three of system apks are overwritten:
- /system/framework/framework-res.apk
- /system/priv-app/LGSystemUI.apk
- /system/priv-app/LGCameraApp.apk
Camera should be compatible for all variants, and only the FRAMEWORK RESOURCE and the SYSTEM UI might have compatibility issue.
You can first take a Nandroid backup, and try installing GomdoLight all the way to the end over your stock firmware, and see if it boots (and operates without crashes)
For model selection just choose LG-F340K.
1) If it works well: CONGRATULATIONS! You have fully-working GomdoLight.
2) If it fails: Restore Nandroid, and reinstall GomdoLight. However this time choose the 4TH option for battery percentage indicator. (Do not change) This options leaves both framework-res and SystemUI unchanged, so it will work 100%.
juniecho said:
I'm not sure yet, but it may not be necessary. Because gomdolight is a large-scale patch mainly focusing on script-driven features, just three of system apks are overwritten:
- /system/framework/framework-res.apk
- /system/priv-app/LGSystemUI.apk
- /system/priv-app/LGCameraApp.apk
Camera should be compatible for all variants, and only the FRAMEWORK RESOURCE and the SYSTEM UI might have compatibility issue.
You can first take a Nandroid backup, and try installing GomdoLight all the way to the end over your stock firmware, and see if it boots (and operates without crashes)
For model selection just choose LG-F340K.
1) If it works well: CONGRATULATIONS! You have fully-working GomdoLight.
2) If it fails: Restore Nandroid, and reinstall GomdoLight. However this time choose the 4TH option for battery percentage indicator. (Do not change) This options leaves both framework-res and SystemUI unchanged, so it will work 100%.
Click to expand...
Click to collapse
Wheres the download?
podagee said:
Wheres the download?
Click to expand...
Click to collapse
in the download/manual page. section 10. (see the first post) be sure to read the installation guide.
I installed in my d-958, well, some force closes in the settings, app manager and gallery sometimes, but everything else, at least the main functions, works well
Maikeu Locatelli said:
I installed in my d-958, well, some force closes in the settings, app manager and gallery sometimes, but everything else, at least the main functions, works well
Click to expand...
Click to collapse
do they CONSISTENTLY force close by certain actions? or just randomly?
I'm downloading now and will test it for the D95920s firmware. T-Mobile D959 on the latest KitKat 4.4.2 D95920s. Will report back later. I need my phone till at least 4pm central time so I can reach my son but I'll flash after that.
This intrigues me. Sprint supported? I don't feel like dealing with force closes mentioned in previous post in different variant.
Sent from my LG-LS995 using Tapatalk
mattwheat said:
I'm downloading now and will test it for the D95920s firmware. T-Mobile D959 on the latest KitKat 4.4.2 D95920s. Will report back later. I need my phone till at least 4pm central time so I can reach my son but I'll flash after that.
Click to expand...
Click to collapse
good luck. if it crashes revert to stock via nandroid backup and reinstall gomdolight, this time choosing the 4th option (do not overwrite the status bar) with battery percentage indicator.
felacio said:
This intrigues me. Sprint supported? I don't feel like dealing with force closes mentioned in previous post in different variant.
Sent from my LG-LS995 using Tapatalk
Click to expand...
Click to collapse
probably. the script set is practically compatible with all current LGE devices with JB or KK. only few apks should be troublesome.
if not sure, choose not to change the status bar during installation. then it will not overwrite both framework-res and systemui.
Gonna try it on my d950
---------- Post added at 01:31 AM ---------- Previous post was at 01:17 AM ----------
Mahh nothing different.... install went perfect,so far no force closes. What is this supposed to be? I dont see any difference. I used the f340u+. Nothing special going on with this. Restoring my back up now.
podagee said:
Gonna try it on my d950
---------- Post added at 01:31 AM ---------- Previous post was at 01:17 AM ----------
Mahh nothing different.... install went perfect,so far no force closes. What is this supposed to be? I dont see any difference. I used the f340u+. Nothing special going on with this. Restoring my back up now.
Click to expand...
Click to collapse
Don't you see messages like 'GomdoLight: System starting up'?
You usually don't see visible differences after installing GomdoLight, especially on non-Korean firmware, since it does not know what apps to debloat. You would have to debloat the system yourself. However its extensive startup script set provides very unique and useful functions. These functions are explained in the simplified user manual that is automatically displayed after installing. If you did not see the manual opening, and if you do not see the startup messages either, probably something is wrong.
juniecho said:
Don't you see messages like 'GomdoLight: System starting up'?
You usually don't see visible differences after installing GomdoLight, especially on non-Korean firmware, since it does not know what apps to debloat. You would have to debloat the system yourself. However its extensive startup script set provides very unique and useful functions. These functions are explained in the simplified user manual that is automatically displayed after installing. If you did not see the manual opening, and if you do not see the startup messages either, probably something is wrong.
Click to expand...
Click to collapse
I seen all the startups and everything. Gomdo warning of superuser, a major lag on my phone for abot 3-5 minutes of lag. It only uninstalled vutalj. I honestly havent noticed anything special. I even tried it with that status bar selection and it went through fine.
podagee said:
I seen all the startups and everything. Gomdo warning of superuser, a major lag on my phone for abot 3-5 minutes of lag. It only uninstalled vutalj. I honestly havent noticed anything special. I even tried it with that status bar selection and it went through fine.
Click to expand...
Click to collapse
gomdolight's optimizations are not much visually noticable, without drastic changes. if you expect a whole new experience this is not your type of rom.
or, you could install another stock-based rom that will bring significant changes, and install gomdolight over it (without status bar selection) to further aid with its performance.
think gomdolight as a special tool to streamline and 'properly' reorganize the stock firmware (or, stock-based roms). changes are not noticable at first sight, but they surely benefit the user somehow in the long run, and give you better control and (sometimes) superior disaster handling capabilities.
anyway, thank you for letting me know that selecting LGU+ model increases compatibility with non-Korean firmwares.
juniecho said:
gomdolight's optimizations are not much visually noticable, without drastic changes. if you expect a whole new experience this is not your type of rom.
or, you could install another stock-based rom that will bring significant changes, and install gomdolight over it (without status bar selection) to further aid with its performance.
think gomdolight as a special tool to streamline and 'properly' reorganize the stock firmware (or, stock-based roms). changes are not noticable at first sight, but they surely benefit the user somehow in the long run, and give you better control and (sometimes) superior disaster handling capabilities.
anyway, thank you for letting me know that selecting LGU+ model increases compatibility with non-Korean firmwares.
Click to expand...
Click to collapse
Okay. I will reinstall again and run it for a while to see its benefits. Thanks
podagee said:
Okay. I will reinstall again and run it for a while to see its benefits. Thanks
Click to expand...
Click to collapse
the built-in user manual explains some of its advantages... take a look at it, especially the section for what is called gomdolight flags.
UPDATE - Wave 2, revision 3
UPDATE LEVEL: MEDIUM / IMPORTANCE: HIGH
UPGRADE INSTRUCTIONS:
One-touch upgrade via 'Upgrade/Repair' option
CHANGELOG:
Improved GomdoLight Engine scripts
Faster boot time, reduced processor load during boot
Improved GomdoLight operational status notifications
Slightly improved battery efficiency
'Update Center' components updated