Hey all,
Everytime I root my 1.2 device with manual nooter 4.5.6 (haven't tried .18), I get one download out of the Android Market. After that the Market.apk disappears from the system/app directory and I can no longer download apps. The end result of this is that I'm pretty much hosed. I've tried putting SU File Manager on to sideload apps, but it can't installed BusyBox because of the market problem, so no luck with that. I've reproduced this issue at least half a dozen times, using CWR to delete all the user data, re-registering the stock install, and then rooting again.
At this point I'm staying stock until I feel confident I can download more than one app from the market on a rooted device.
So, has anyone else experience anything like this, and if so, is there a solution?
I have this same problem. No solution yet.
It may be related to a download directory bug which has been fixed. I updated to MN4.5.18 over 4.5.6. Everything worked well untill a recent update to 4.5.25. The market crashed again. This issue seems not solved yet. So I had to flash back 4.5.18.
Same here - .18 works very well once you figure out you have to uninstall the apps that want to update and then reinstall clean to remove the chance of bootloops. I was considering doing a complete wipe again and flashing .25, but I've decided to stick it out with .18 until they get squared away.
Overall, MN4.5.18 kicks ass for all intents and purposes, and I'd suggest moving up to that.
mjbelknap said:
.18 works very well once you figure out you have to uninstall the apps that want to update and then reinstall clean to remove the chance of bootloops.
Click to expand...
Click to collapse
Can you elaborate on this?
Can ANYONE elaborate on this
Hi all,
I'm new to this forum and tried to find the answer before posting this but couldn't find the answer.
The problem is that my phone keeps restarting on custom roms.
It happens on various custom roms i tried cm12.1 and a couple of others. When i first install the custom rom it all seems fine. Even after a couple of restarts it all works okay untill the moment that i install all my apps that i use.
After a number of installed apps the launcher app trebuchet keeps crashing and after that my phone is in an endless boot loop.
Does anyone else know of this problem or have a solution to this weird problem?
Ps. When i revert back to an twrp backup of my old 4.4.2 system all is fine and no bootloops anymore.
I also tried installing nova launcher instead of trebuchet because i tought it was trebuchet related but that didn't work. (I uninstalled trebuchet completely).
Please let me know if you need more info from the phone.
Thanks
Dennis
Dennis312 said:
Hi all,
I'm new to this forum and tried to find the answer before posting this but couldn't find the answer.
The problem is that my phone keeps restarting on custom roms.
It happens on various custom roms i tried cm12.1 and a couple of others. When i first install the custom rom it all seems fine. Even after a couple of restarts it all works okay untill the moment that i install all my apps that i use.
After a number of installed apps the launcher app trebuchet keeps crashing and after that my phone is in an endless boot loop.
Does anyone else know of this problem or have a solution to this weird problem?
Ps. When i revert back to an twrp backup of my old 4.4.2 system all is fine and no bootloops anymore.
I also tried installing nova launcher instead of trebuchet because i tought it was trebuchet related but that didn't work. (I uninstalled trebuchet completely).
Please let me know if you need more info from the phone.
Thanks
Dennis
Click to expand...
Click to collapse
Did you consider that one of the apps you install is causing the problem?
Try installing apps one by one, and be aware that some apps designed to work in Android KitKat or less may not work on Android 5 or higher.
And some apps have multiple versions for each android version, so it's better to install your apps by downloading them from the play store.
I have a rooted LG Stylo 2 Plus (T-Mobile model). I recently encountered a problem where when I sideload some apks I get "App not installed. The package appears to be corrupt" and when downloading and then installing apps through the Google Play Store, I would get error 507. The apk work on other devices, and some apk will install, but there is other ones I need to install. I have tried clearing the cache of the package installer and Google play store and services. What should I do?
I have the exact same problem, same model (lgms550) running 7.0 (rooted, twrp and supersu, otherwise stock). Mine initially started when I installed xposed. When I flashed the uninstaller zip the package installer worked again (for a while...) Now every package throws "appears corrupt" and Playstore gives the 507 error. I've transferred the apps to my other phone (gs5) and they install fine so they're not bad downloads. Frankly I'm stumped and after hours of combing google for answers this is the first post that matches and oddly it's the same device. Maybe it's the ms550?
Fixed this by reflashing system from twrp.
First off, I feel it necessary to say WITHOUT THE CREW WORKING ON TWRP THERE WOULD HAVE BEEN DOZENS OF ANDROIDS BEING USED FOR SKEET SHOOTING BY MYSELF! A huge thanks. Thank God I took the time to do a quick backup with twrp before starting anything stupid. I still am unsure as to the original cause, it was only noticed after installing xposed but I've done any number of changes to this phone. If needed i can reset, make a backup, and upload for flashing in twrp for whoever wants it.
Seems like I had same or close to same with my T-Mobile Stylo 2 plus. (now unlocked on metro PCS)
A while back I had a weird issue where my default package installer would not install qpks. I downloaded another app from playstore and worked fine. I didn't pay much attention to it as I resolved the issue using a different app to install qpks.
Sent from my ph2n using XDA Labs
SM210 said:
Seems like I had same or close to same with my T-Mobile Stylo 2 plus. (now unlocked on metro PCS)
A while back I had a weird issue where my default package installer would not install qpks. I downloaded another app from playstore and worked fine. I didn't pay much attention to it as I resolved the issue using a different app to install qpks.
Sent from my ph2n using XDA Labs
Click to expand...
Click to collapse
I've traced the problem to having Mod Edit: warez installed. Seems the issue has been resolved with updates to Mod Edit: warez. The problem persisted even when using another app to install.
I removed some stock apps using adb, and something broke my second screen. Everything seemed benign, but I jacked up something. Now my phone keeps displaying "Unfortunately, second screen has stopped." Thanks!
Do you have a Nandroid of your install or backups of any of your apps through TiBackup?
Non rooted with no backup
No.
What model do you have?
Just use one of the unbricking methods here on xda to reflash stock rom and you should be fine. Use LG UP to flash the latest kdz.
https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903
In had this happen many times tweaking things through adb. Never did figure out what I did to disable the screen. I found a simple factory reset fixed it. Assuming your are not rooted and just forced an uninstall of apps via Adb.
I had this happen (on VS995 i.e. Verizon non-rooted on Oreo) after I used adb to uninstall the 3 weather packages (com.lge.sizechangable.weather, platform & theme.optimus) since I don't use the weather widget. Reinstalling from the original apk files fixed the problem; they were listed as Weather, Weather Service (this one fixed it) and Weather Theme. So my guess is one of the packages you uninstalled. I tried disabling them first but couldn't, thus the uninstall. Couldn't reinstall through adb but just running the apk install once I found where they were hiding in the file system fixed me up. Argh!
Hi. I have a Xiaomi MiA1, Lineage 16.0 (I try to update it two or three times per week). It is rooted. I use openGapps.
I have a problem since yesterday: suddenly, my phone got a lot of lag that makes impossible the use. KLWP got closed (it stopped being the default background), Nova Launcher was lagging and restarting several times. Openning any app was impossible, including the settings and system, it freezes and closes, returning to the launcher home screen... I tried to stop, clean data and delete klwp, nova, but i got the same result. The minutes passed and it got worse. Finally, the phone freezed, the clock wasn't working, so the only solution was doing a manual soft reset.
So, yesterday I did a dirty flash, because I didn't have a recent backup. I used SDMaid database feature in the morning so I tought maybe it was bad executed and was the origin of the issue. I tried to rescue some information (to backup some app data) with oandbackups. I cleaned caché and did a Factory reset. It seem to work. and do a clean installation. at first, it seem like it worked. I installed the apps I had by my Google account, and went to sleep. Today, it was ready, I turned it off and charged it, and in the morning: again the crash. So I did a clean installation. Again, it seemed to work. It installed all my apps and... crash again. I fear it could be some launcher issue? any prob with lineage? Any app? How can I know whats happening?
Sorry for my bad english. Any help would be apreciated.
vainille said:
Hi. I have a Xiaomi MiA1, Lineage 16.0 (I try to update it two or three times per week). It is rooted. I use openGapps.
I have a problem since yesterday: suddenly, my phone got a lot of lag that makes impossible the use. KLWP got closed (it stopped being the default background), Nova Launcher was lagging and restarting several times. Openning any app was impossible, including the settings and system, it freezes and closes, returning to the launcher home screen... I tried to stop, clean data and delete klwp, nova, but i got the same result. The minutes passed and it got worse. Finally, the phone freezed, the clock wasn't working, so the only solution was doing a manual soft reset.
So, yesterday I did a dirty flash, because I didn't have a recent backup. I used SDMaid database feature in the morning so I tought maybe it was bad executed and was the origin of the issue. I tried to rescue some information (to backup some app data) with oandbackups. I cleaned caché and did a Factory reset. It seem to work. and do a clean installation. at first, it seem like it worked. I installed the apps I had by my Google account, and went to sleep. Today, it was ready, I turned it off and charged it, and in the morning: again the crash. So I did a clean installation. Again, it seemed to work. It installed all my apps and... crash again. I fear it could be some launcher issue? any prob with lineage? Any app? How can I know whats happening?
Sorry for my bad english. Any help would be apreciated.
Click to expand...
Click to collapse
Keeping in mind the kind of apps you mentioned, I'd go with an app+data backup of those apps you installed and uninstall them completely, check if problem is still there.
I suspect you're facing a compatibility or configuration issue, since both apps are related to home screen.
If problem is solved, first read if those apps are actually compatible with ROM and OS version, then you could try to install just one app, without data, and check if things go well (give it a day), same with the rest until you can confirm OS is working well with apps just installed, no changes made in them yet... In other words, were trying to confirm that problem comes from apps and/or their configurations, so you could somehow report those issues to apps developers. You can use Catalog or other apps to record System logs until app crashes.
On the other hand, if problem is still there, even before you started to reinstall apps, then Dirty flashing isn't a good choice in that case, since it preserves System configurations, no mention your device is rooted, were user changes are present... you are opened to different problems, worse if you use an old Magisk version, or installed modules there, or apps that force your OS to do things it doesn't do in it's original state.
So, as you were so dare to go with a dirty flash, you could better go with a clean flash instead.
Erase any system lock protection (fingerprint, pattern, etc), do a ROM Backup from TWRP, flash latest firmware and make a clean install of the latest version of the ROM of your choice, keeping in mind their own flashing procedure.
As with above reply, if a completely clean install doesnt work, consider going back to a previous lineage release. If it still doesnt work, consider a full EDL stock rom reflash using MiFlash -- then flash your custom rom.
KaaMyA said:
Keeping in mind the kind of apps you mentioned, I'd go with an app+data backup of those apps you installed and uninstall them completely, check if problem is still there.
I suspect you're facing a compatibility or configuration issue, since both apps are related to home screen.
If problem is solved, first read if those apps are actually compatible with ROM and OS version, then you could try to install just one app, without data, and check if things go well (give it a day), same with the rest until you can confirm OS is working well with apps just installed, no changes made in them yet... In other words, were trying to confirm that problem comes from apps and/or their configurations, so you could somehow report those issues to apps developers. You can use Catalog or other apps to record System logs until app crashes.
On the other hand, if problem is still there, even before you started to reinstall apps, then Dirty flashing isn't a good choice in that case, since it preserves System configurations, no mention your device is rooted, were user changes are present... you are opened to different problems, worse if you use an old Magisk version, or installed modules there, or apps that force your OS to do things it doesn't do in it's original state.
So, as you were so dare to go with a dirty flash, you could better go with a clean flash instead.
Erase any system lock protection (fingerprint, pattern, etc), do a ROM Backup from TWRP, flash latest firmware and make a clean install of the latest version of the ROM of your choice, keeping in mind their own flashing procedure.
Click to expand...
Click to collapse
I made a clean flash in the morning, with the same results, so there's when I thought it could be an app the main problem. It worked with Nova a few hours.
I just followed your instructions, I installed the last firmware (the jan one) and the last rom of lineage. I didn't installed the apps in my google backup so I can install them and check how is the behaviour. I will install CatLog so I can check the logs too! I really hope installing the firmware was enough. Thank you very much!
ayunatsume said:
As with above reply, if a completely clean install doesnt work, consider going back to a previous lineage release. If it still doesnt work, consider a full EDL stock rom reflash using MiFlash -- then flash your custom rom.
Click to expand...
Click to collapse
I was planning to reflash the custom ROM but I couln't find the latest one that's compatible with MiFlash. I really hope the clean install is enought... thank you
I was planning to reflash the custom ROM but I couln't find the latest one that's compatible with MiFlash. I really hope the clean install is enought... thank you[/QUOTE]What our partner said was flashing stock (original) ROM.
In any case, if you went with a clean flash, try to leave your system free of user installed apps for a few and check how it goes.