Related
I think i fix the problem!
Going to Settings/Aplication Manager/Runing/System Info; End this proces and is done! Now i see if the text re apears on normal use or only when it starts up.
Click to expand...
Click to collapse
Well im sorry to post this i see other topics similar but i wasnt able to find a solution...
I have one Sgs2 t989 rooted with Odin and for no reason appears some text on my home screen.
HW : REV0.1
PDA : T989UVMC6
Phone : T99UVMC6
CSC : T989TMBC6
RF cal. Date : 2012.03.24
SMD,PBA : N
Camera : N/A
TSP :0x10
TSK : 0x13
Unique Number: (Large Code)
I tried to restet to fabric, re root , re installed JellyBean 4.1.2 and all but there seems to be no solution thats why im asking help here...
Some one can give me a solution? I downloaded also ES File Explorer to folow some steps to fix it but im stock at the step to enable r/w options. And i my efs folder is empty!
You need a root file explorer(I use es file explorer). Go into settings and enable r/w options. Then you should be able to find the efs directory.
Edit: so I saw your post in the other thread that says you aren't rooted. The only other way that I know to get rid of the text is to flash a different ROM.
Click to expand...
Click to collapse
Im 4 days trying to fix this freaking phone to unlock to other companis (Now is T-mobile) and even the code Tmobile gives to me dosent works....
Please im begin for help!!
same issue for awhile but only on jedi roms other roms are fine
Toddishere21 said:
same issue for awhile but only on jedi roms other roms are fine
Click to expand...
Click to collapse
So i should try other roms? Can u recomend some for google it?
if you like jedi embryo is awesome id recommend it for now http://forum.xda-developers.com/showthread.php?t=2142932&highlight=embryo
Toddishere21 said:
if you like jedi embryo is awesome id recommend it for now http://forum.xda-developers.com/showthread.php?t=2142932&highlight=embryo
Click to expand...
Click to collapse
So once i install that Rom i should have the problem solve? or there is a chance to solve it?
Problem "WILL" be solved
I think i fix the problem!
Going to Settings/Aplication Manager/Runing/System Info; End this proces and is done! Now i see if the text re apears on normal use or only when it starts up
Click to expand...
Click to collapse
OOh imma try this if it works use titanium backup to freeze the process
Edit: your fix is confirmed working thank you soo much for posting on how you did it i froze the process with titanium and it dosnt come back even after restart if you need help doing that let me know
I apologize, I posted this in the wrong forum. Feel free to delete, I can't figure out how (I can only edit when I press the edit/delete button).
--
I have rooted, and I have xposed installed.
What is the upgrade procedure? Do I need to go so far as to remove root? Any advice appreciated.
Thanks!
paulvallee said:
I have rooted, and I have xposed installed.
What is the upgrade procedure? Do I need to go so far as to remove root? Any advice appreciated.
Thanks!
Click to expand...
Click to collapse
Don't update it. More than likely if you have twrp and root it will loop. I did mine this morning and it looped it. I had to factory reset with the lg tool. Just wait it out. The update isn't that serious.
Hey Danon, where did get the LG tool to factory reset? i feel victim to the same damn thing. Need to reset mine now.
paulvallee said:
I have rooted, and I have xposed installed.
What is the upgrade procedure? Do I need to go so far as to remove root? Any advice appreciated.
Thanks!
Click to expand...
Click to collapse
First off, this question belongs in the Q&A not development
BUT. Regarding root, you never want to apply an OTA update, you never know if they could patch any rooting exploit and or lock the bootloader. Someone will most likely pull the update from the device and make us a flashable zip that will preserve root.
So for now do nothing at all
I have no intention of installing this update but how do I get rid of the persistent notification? It's annoying me.
musbdluv said:
Hey Danon, where did get the LG tool to factory reset? i feel victim to the same damn thing. Need to reset mine now.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2799647
Once you get the process down it takes about 7 minutes. I would advise you to do it with Windows 7 if you can.
Nosferatu. said:
I have no intention of installing this update but how do I get rid of the persistent notification? It's annoying me.
Click to expand...
Click to collapse
I know on my S4 i337m when running the Google Play Edition ROM I modified this line in the build prop to the same line from the build prop in that update.
ro.build.fingerprint=samsung/jgedlteue/jgedlte:4.4.4/KTU84P.S001/140602:user/release-keys
I'm assuming it would work on ours too if anyone has their phone updated and can post that (ro.build.fingerprint) line from their build prop.
Is there anyone that maybe posted an update we can flash on our Rooted/Non Stock Recovery phones?
Nosferatu. said:
I have no intention of installing this update but how do I get rid of the persistent notification? It's annoying me.
Click to expand...
Click to collapse
Longpress on notification then turn off notification.
I encountered same problem and used the following to go back to bone stock (reroot required if you did).
http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667
Before entering download mode, make sure you unplug USB cable, remove the battery and put it back in, press and hold the volume button and plug in USB cable, and relax.
This method won't wipe your phone.
Not that big of a change with this update, just 'Wi-Fi Calling Enhancements'
http://support.t-mobile.com/docs/DOC-11935
tarroyo said:
Not that big of a change with this update, just 'Wi-Fi Calling Enhancements'
http://support.t-mobile.com/docs/DOC-11935
Click to expand...
Click to collapse
It's always funny when a small OTA hits... People start claiming all sorts of outrageous things.. From the phone feels smoother to battery life sucks now, the list goes on.
tarroyo said:
Not that big of a change with this update, just 'Wi-Fi Calling Enhancements'
http://support.t-mobile.com/docs/DOC-11935
Click to expand...
Click to collapse
also comes with an updated, much improved...carrier IQ
shook187 said:
It's always funny when a small OTA hits... People start claiming all sorts of outrageous things.. From the phone feels smoother to battery life sucks now, the list goes on.
Click to expand...
Click to collapse
Lol right, Was hoping for a new radio still getting a lot of drops through out the day.
I wonder if it has anything to do with the updates coming to wifi calling?
http://www.androidheadlines.com/2014/09/t-mobiles-un-carrier-7-0.html
The only thing I wish for on this phone is disabling the aux jack auto sense. It's driving me mad!
All i kno is last nite my phone updated the stupid g3 ota update it stuck in a boot loop im running zone rom an twrp. So thx to maxless at lgroot.kom i learrned how to flasg stock rom back on there and disable ota updates i l just googled how do it and got that number to did the wifi ootion disable. Ota updates so guys dont UPDATE lol
I just went into cache folder and renamed the file to .bk and then into hidden settings menu and disabled ota updates
chefp2010 said:
I just went into cache folder and renamed the file to .bk and then into hidden settings menu and disabled ota updates
Click to expand...
Click to collapse
How come my cache folder is empty? I'm using es file explorer and i have my settings set to show hidden files. I even ran a search for the update.zip and the lg .apk someone listed and i can't find either off them.
Im using root explorer and went cache and just renamed the file to .bk
---------- Post added at 04:17 AM ---------- Previous post was at 04:16 AM ----------
Do you have the notification for the update
I installed root explorer and found the file but it wouldn't let me rename or delete it. It said it was successful but didn't actually work.
I have read and fallow many guides,non one is helping to solve mystery. I'm on 20d software, I can root, but no way to install recovery, tried loki, downgrade, etc. after all done tablet is stuck on error with to lines msg. what I'm doing wrong?? I even try root in 2 ways, always checking after for root access, no problem with that. but can go forward after that, any ideas??
are this could be related to laptop problem, ex hard drive??
djcody said:
are this could be related to laptop problem, ex hard drive??
Click to expand...
Click to collapse
Try this I Hope this Help it need root
Click Here
work perfectly thank you
Dear gals and guys,
I have created a video tutorial how to fix ILAPO issue here:
If you follow the step-by-step tutorial properly, you will be able to recover all your important data and even keep using the device.
If you are willing to either keep using the phone or sell it with all 4 cores enabled, please follow second tutorial:
Edit: New revision v8.0 has been released. Enjoy full Marshmallow support
Hey, thanks for that. Maybe I missed something but... what have you done in the 1st video?
That could be useful, but the only thing I got is the phone wasn't booting and the you got that booting.
Thanks!
W.
@maddler - I have only flashed the ILAPO fix using the LGUP, so that all cores but one have been disabled and I was able to get to the home screen once again.
Great work! Thx!
You saved my phone!
The lg rejections the mainboard replace, because unlock bootloader.
Now working perfect L, Is it possible in the future M?
Thx again!
blueeyeblue said:
@maddler - I have only flashed the ILAPO fix using the LGUP, so that all cores but one have been disabled and I was able to get to the home screen once again.
Click to expand...
Click to collapse
If you could, please, add download links and (maybe) a step by step guide could be useful for lesser experienced users too.
Thanks by the way!
Edit: found this http://howtovideoz.xyz/play?m=6c624a5877506d62584663 (which appears to be your too, if I'm not wrong).
I run 4 cores since 4 months now, Im on a custom ROM and just enable them all 4 cores every boot in Device Control by changing frequency. I think I've mentioned that in my notice post but I can't remember. Its good though, that the app for it has been created, some people might know now how to use tools like Device Control. We also might want to think about why you cannot lock the device on AOSP/CM based ROMs with 4 cores enabled... BTW from Wed I'll be free of a bootlooped G4, my OnePlus 3 is comming!
@maddler - Yes, the video tutorial is in the first post.
@Adam Myczkowski - Please try the app and let me know whether or not it works for you.
blueeyeblue said:
@maddler - I have only flashed the ILAPO fix using the LGUP, so that all cores but one have been disabled and I was able to get to the home screen once again.
Click to expand...
Click to collapse
Ok, great job guy, but where is the link to download the fix?
Moreover, if my smartphone is bootloop how can I downgrade from MM to LL? Everyone knows that even by flashing a different ROM, or downgrading, the smartphone does not start again!
@casabato - From where do you got that info? I downgraded from MM to LL without any problem. Model H815.
blueeyeblue said:
@casabato - From where do you got that info? I downgraded from MM to LL without any problem. Model H815.
Click to expand...
Click to collapse
Good to know, thanks. I wanted to say this: my smartphone (H815 too) has MM, but if it is in bootloop how can I perform a downgrade to LL and be sure it was successful?
As far as I know anyone who has suffered a bootloop is unable to restart the smartphone even by flashing a different firmware.
So I should downgrade now that the smartphone works, and not when it is in bootloop (hopefully never!), To be ready to eventualities ..
However, my first question remains: where is the link to download the fix?
blueeyeblue said:
@maddler - Yes, the video tutorial is in the first post.
@Adam Myczkowski - Please try the app and let me know whether or not it works for you.
Click to expand...
Click to collapse
It does work on AOSP as well. Checked, confirmed.
@casabato - Everything is in the first video description.
@Adam Myczkowski - Okay, thank you for the reply.
dolasz said:
Great work! Thx!
You saved my phone!
The lg rejections the mainboard replace, because unlock bootloader.
Now working perfect L, Is it possible in the future M?
Thx again!
Click to expand...
Click to collapse
Really I sent my phone back to LG to fix the board and my bootloader was unlocked and they fixed it and sent it back.
I tried the 7 HD ROM and when I tried to go back to stock LGUP doesn't recognize my device because swversion is changed in 'cust / OPEN_COM /cust_OPEN_EU.prop'. How can I delete that file or edit. I lost the custom recovery and I have access only to fastboot.
@Chosen_on184 - You are the lucky one
@exilod - Did you extract only the system partition and flashed it using the send command utility? It works only for H815.
blueeyeblue said:
@Chosen_on184 - You are the lucky one
@exilod - Did you extract only the system partition and flashed it using the send command utility? It works only for H815.
Click to expand...
Click to collapse
I have the H815. Here is what I tried:
After I encountered the bootloop for the first time I flashed the .tot fix with LGUP(The application could recognize my phone).
Then I applyed the 4 core fix with your app. Then I tried the ROM you recomanded but after some time I wanted to go back to stock L. LGUP says 'Unknown device '(see image) and I can't apply the tot fix again. I think the cust partition where that 7 HD sw information resides is not deleted even after reflashing the kdz. I don't know to use the Send_Command.exe except for connecting to phone and apply command for entering in fastboot mode.
If it's possible to flash with send command I am very interested how.
exilod said:
I have the H815. Here is what I tried:
After I encountered the bootloop for the first time I flashed the .tot fix with LGUP(The application could recognize my phone).
Then I applyed the 4 core fix with your app. Then I tried the ROM you recomanded but after some time I wanted to go back to stock L. LGUP says 'Unknown device '(see image) and I can't apply the tot fix again. I think the cust partition where that 7 HD sw information resides is not deleted even after reflashing the kdz. I don't know to use the Send_Command.exe except for connecting to phone and apply command for entering in fastboot mode.
If it's possible to flash with send command I am very interested how.
Click to expand...
Click to collapse
Maybe you have bad drivers. I had no success doing it under Windows 10, thus I had to switch to Windows 8.1 and install the following drivers: https://www.androidfilehost.com/?fid=95916177934549194
blueeyeblue said:
Maybe you have bad drivers. I had no success doing it under Windows 10, thus I had to switch to Windows 8.1 and install the following drivers: https://www.androidfilehost.com/?fid=95916177934549194
Click to expand...
Click to collapse
I tried on two laptops with windows 10. same problem. I'll try with windows 8.1 but I still think the problem comes from the phone.
@exilod - If you can enter the download mode, then it should be easy to flash the kdz again.
blueeyeblue said:
@exilod - If you can enter the download mode, then it should be easy to flash the kdz again.
Click to expand...
Click to collapse
I can enter download mode, I can flash L kdz file with LG Tools 2014 but LGUP still doesn't recognize my phone.
Hello.
After testing some custom ROMs I've noticed a feature that I thought it was quite cool... the boot animation changed to dark when the dark mode was enabled while running the system.
Decided to investigate this feature and realized that this could have been already implemented on our devices (at least on Android 10 ROMs) if the "media" folder was present on /product instead of /system. Unfortunately it wasn't so I had to come up with a method to get this running on stock ROMs.
The method I've came up with is not "elegant" at all but, hey, it gets the job done, and also, it will work with any light/dark boot animation already released (Pixel, Evo, Havoc, etc...).
How to:
Download both files, present on this thread attachments, and store them on your device (for instance, on Download folder)
Install any root explorer (I'm using FX File Explorer...but you may use any explorer with root permissions)
Install MacroDroid App
Extract the content of Auto_Dark_Based_On_Daylight.zip file in order to obtain Auto_Dark_Based_On_Daylight.macro
Create a backup of your current bootanimation.zip file (just rename it to bootanimation_BKP.zip or something like that, the original file is on /system/media/)
Install Typhus_Themed_Boot_Animation.zip Magisk module and reboot your phone.
Import the Auto_Dark_Based_On_Daylight.macro to Macrodroid (see the Image Tutorial if you don't know how to do this)
Test the Sunset trigger
Reboot your device
Enjoy your dark boot animation while running your system on dark mode and vice versa
NOTES:
1 - As stated, this method will work with any boot animation out there. You just need to replace the zip files inside the "bootanim" folder you will find inside the zip file
2 - Yes, this WILL break OTA since we're mounting system as R/W to do this. I don't mind...I know how to install an OTA when it arrives, so I'm fine with this. Please don't ask here how to install OTA when it arrives...there are a lot of posts and threads here on XDA where people (myself included) already debated that subject.
3 - Didn't understand the method? Need more help? CHECK THIS Image Tutorial!!
Cheers and enjoy!
Does it work only with stock rom?
giacomo_bragagnolo_02 said:
Does it work only with stock rom?
Click to expand...
Click to collapse
No, this will work with any ROM, any device and for any Android version if running AOSP based ROMs.
BUT it's possible that if, your using a custom Android 10 ROM, this isn't needed since it may be already implemented by the developer.
Check if you have a /product/media folder. If you do, then all you have to do is to put the bootanimation-dark.zip file on that folder and it will work without the need to do all the other things.
Cheers!
It works so good but splash is still in white
alvin182 said:
It works so good but splash is still in white
Click to expand...
Click to collapse
Yes, indeed it is. Don't really know where the splash images are stored on Mi A3. They're not on splash.img. If I knew where they were I would change it, obviously.
Really, this is something that I've been wondering about since day one....where the hell are the freakin' splash images stored!!?? Something so simple for almost ALL other devices out there turns to be a riddle on Mi A3....
Typhus_ said:
Yes, indeed it is. Don't really know where the splash images are stored on Mi A3. They're not on splash.img. If I knew where they were I would change it, obviously.
Really, this is something that I've been wondering about since day one....where the hell are the freakin' splash images stored!!?? Something so simple for almost ALL other devices out there turns to be a riddle on Mi A3....
Click to expand...
Click to collapse
hahaha no worries it's good like this im gonna save up too many white pixels in the boot so xD.... thanks for your work!
Most probably the splash image is embedded in the bootloader or kernel
I've made a Magisk Module with the dark one, it's utterly simple, but this way you can do it systemlessly.
bttcp12 said:
Most probably the splash image is embedded in the bootloader or kernel
I've made a Magisk Module with the dark one, it's utterly simple, but this way you can do it systemlessly.
Click to expand...
Click to collapse
First of all, thank you for your contribution.
I know I could have made a Magisk module to do this. But, that way, the boot animation wouldn't change dynamically, it would be always dark and that wasn't my objective.
Of course, if your goal is to always have it dark, then you can use the module to "replace" systemlessly the bootanimation.zip file.
On a side note, I've tried to include this feature on the Pixel Theme, which is a Magisk module, but, unfortunately, it's not possible to symlink files, or folders, from files, or folders, that only exist "systemlessly" marked as read only. That's why this method has to be done like I've explained on the OP.
I've even tried to include a /porduct/media folder with the zip files inside the module....but that didn't work as well. You see, /product is a read-only file system and, for this to work, it had to be mounted as read write at boot time, so that it could be read while booting, and that would have to be made at kernel ramdisk level. Don't think it's worth the trouble just to have a boot animation that changes dynamically.
Tried, as well, to include the files on any other folder that could be symlinked (like /vendor/overlay/media). They were symlinked all right...but Android doesn't read that folder at boot time....so yeah, I've gave up and came up with the method explained here.
Anyway, thanks for your interest and, regarding the splash image....my knowledge isn't enough to figure out bootloader and/or kernel stuff.
Maybe @paul89rulez could help us with this....
Cheers!
Its looking so tough for me. ??
Is there any easier way?
reyad019 said:
Its looking so tough for me. ??
Is there any easier way?
Click to expand...
Click to collapse
Follow the image tutorial. Have you tried that?
bttcp12 said:
Most probably the splash image is embedded in the bootloader or kernel
I've made a Magisk Module with the dark one, it's utterly simple, but this way you can do it systemlessly.
Click to expand...
Click to collapse
Thanks for the module, but for some reason I'm not able to install via Magisk, so I had to flash it via recovery, btw everything works fine (except for the splashscreen ofc), thanks for your help
Just found where the splash images, as well as battery images, etc are stored.
They're on xbl.elf
Just have to figure out how to unpack and repack this safely in order to change the images.
Cheers!!
Good Luck Man, wish you succeed
Typhus_ said:
Just found where the splash images, as well as battery images, etc are stored.
They're on xbl.elf
Just have to figure out how to unpack and repack this safely in order to change the images.
Cheers!!
Click to expand...
Click to collapse
Sorry for the delay, just read the notification.
Glad you found where the images are stored, but be careful xbl its a bad partition to mess with.
You may want to read this article:
https://worthdoingbadly.com/qcomxbl/
Theoretically, with this tool and 7zip you can extrac the xbl, and if you know wich files you have to swap, repack it fastly. But messing with the bootloader its dangerous.
It's worth it?
paul89rulez said:
Sorry for the delay, just read the notification.
Glad you found where the images are stored, but be careful xbl its a bad partition to mess with.
Click to expand...
Click to collapse
Yes, I know. For the time being I just dropped this subject. It's not worth the risk.
Cheers!
it works
giacomo_bragagnolo_02 said:
Does it work only with stock rom?
Click to expand...
Click to collapse
Yes, it works in my stock rom (11.0.15.0)
New method to achieve this feature by using a Magisk module has been added on the OP.
Enjoy.
Cheers!
Typhus_ said:
New method to achieve this feature by using a Magisk module has been added on the OP.
Enjoy.
Cheers!
Click to expand...
Click to collapse
I can't see the magisk file
Thanks for your work
kosmasgr said:
I can't see the magisk file
Thanks for your work
Click to expand...
Click to collapse
It's on the attachments on the first post.
thanks so much... but 1 q. is it eat battery?? macrodroid?