Database Info

[Q] "Package file is invalid" error on stock ROM & CleanROM Stand 3.0

I was lucky enough to get one of the earlier batches (pre import ban) of the AT&T HTC One XLs and I have enjoyed having it over the past 5-6 weeks. A few weeks back I decided to root my phone and unlock it as I wasn't having any luck upgrading via the OTA update. I believe that soon afterwards I started having a problem installing some larger files and updates, getting a "Package file is invalid" message via Google Play.
At first this only seemed to happen occasionally but a few days back, it started occurring with practically any update or install. I tried cleaning the dalvik and other caches, factory reset, and wiped the SD card without any improvement. Yesterday I decided to make the leap and install CleanROM, both out of curiosity and a hope to resolve my problem. I wiped the system via the recovery bootloader, wiped the cache, wiped the dalvik cache, and wiped the SD card and installed CleanROM. While the install went well and CleanROM is running perfectly, I still get the package invalid method with any install larger than 1mb or so. I am frustrated about this problem as I have enjoyed this phone up to this point. If anyone have any suggestions to resolve this repeated error I would be very grateful. Thanks.

I think you followed almost all the step. But i think there is a issue on your network connection. Try to download new apps over the WiFi. I think you can't use any other mobile network ( i think you have network locked phone).
also check theses things. http://www.thespicygadgematics.com/2011/12/fix-android-package-file-is-invalid.html

Follow-up on suggestion
android addicts said:
I think you followed almost all the step. But i think there is a issue on your network connection. Try to download new apps over the WiFi. I think you can't use any other mobile network ( i think you have network locked phone).
Click to expand...
Click to collapse
Thanks for the suggestion but it turns out exactly the opposite is true. I have been trying to install programs over wifi and they keep failing with the invalid package file message. After reading your suggestion, I turned off the wifi and tried installing several larger programs via the mobile network - they all downloaded and installed without a hitch! Crazy.
So, it looks like my problem might have something more to do with either my wifi network/router or with some aspect of the wifi hardware or software on my phone. Tomorrow I am going to try accessing and installing files from a different network and will post my results then.

[Q] com.phone.android has stopped. Device unusable

Hey guys...today i put the factory ATT ICS from sammobile on my device via Odin. Now, about every 2-5 seconds I get the com.phone.android crash message. I've looked at about 50 or so different threads and can't seem to find a resolution.
I've factory reset, I've reflashed, I've cleared cache data in phone, I've cleared cache data in contacts storage. On the verge of phone smash.
Any ideas?

Try reverting to stock via kies? it sounds like you have a bad flash maybe due to the file. In stock you shouldn't have these issues.

kishke said:
Try reverting to stock via kies? it sounds like you have a bad flash maybe due to the file. In stock you shouldn't have these issues.
Click to expand...
Click to collapse
THanks for the quick reply. Actually I just went into boot/recovery mode (not sure of correct name) and cleared cache a few times and did another full wipe and problem solved. Must have been some strange conflict...

Try fixing permissions if it happens again. That will usually fix FCs without a full wipe (although phone process FCs tend to be a little trickier to get rid of).

Not sure if you tried first time around but I always wipe things a minimum of 3X (usually 4-7 -- call me paranoid).
I'm glad you fixed the issue; I haven't seen/heard this one before.

[Q] Problem with rom

I have recently installed DhdSation Rom v3.1 on my dhd. i found a problem that the touchwiz launcher in it get crash when you open call logs and even when you open messages and sometimes the back button gets hanged. Once i was operating my cell and got a call frrom someone, instead of showing me who it is calling my phone just was vibrating and than the call cutted.
waiting for ur reply thank you

vikramsoni01 said:
I have recently installed DhdSation Rom v3.1 on my dhd. i found a problem that the touchwiz launcher in it get crash when you open call logs and even when you open messages and sometimes the back button gets hanged. Once i was operating my cell and got a call frrom someone, instead of showing me who it is calling my phone just was vibrating and than the call cutted.
waiting for ur reply thank you
Click to expand...
Click to collapse
I have not seen any other users with the same issue. It seems very possible that something went wrong during the install. First of all, verify the MD5SUM of the ROM you downloaded to make sure it is not corrupt. If it is, redownload it, then wipe and reflash.
Did you wipe data & system before installing the ROM? While you do not need to wipe the sdcard portion of data, everything else needs to wiped when changing ROMS or major Android versions. Make sure you did this, if not try reflashing after a proper wipe.
Have you flashed anything else after the wipe, such as a kernel? If so try wiping then reflashing the ROM without anything extra.

Jedakiah said:
I have not seen any other users with the same issue. It seems very possible that something went wrong during the install. First of all, verify the MD5SUM of the ROM you downloaded to make sure it is not corrupt. If it is, redownload it, then wipe and reflash.
Did you wipe data & system before installing the ROM? While you do not need to wipe the sdcard portion of data, everything else needs to wiped when changing ROMS or major Android versions. Make sure you did this, if not try reflashing after a proper wipe.
Have you flashed anything else after the wipe, such as a kernel? If so try wiping then reflashing the ROM without anything extra.
Click to expand...
Click to collapse
During my installation nothing went wrong and yes i wiped my data before installing this rom. I haven't flashed anything after that.
I will try and reflashing again thanks

Please verify md5sum of file u installed.
Sent from my GT-I9100G using xda premium

vikramsoni01 said:
During my installation nothing went wrong and yes i wiped my data before installing this rom. I haven't flashed anything after that.
I will try and reflashing again thanks
Click to expand...
Click to collapse
While you might not have seen an error message, something could have still gone wrong. As a programmer myself, I can attest that it is impossible to detect every error. A zany example: solar flares can cause errors, corrupt data, and even crash applications in spectacular ways.
Definitely start with the MD5 check as that is a fairly common issue. Just today I had one fail to match up. If it matches, reflash, if not redownload then reflash.

Jedakiah said:
While you might not have seen an error message, something could have still gone wrong. As a programmer myself, I can attest that it is impossible to detect every error. A zany example: solar flares can cause errors, corrupt data, and even crash applications in spectacular ways.
Definitely start with the MD5 check as that is a fairly common issue. Just today I had one fail to match up. If it matches, reflash, if not redownload then reflash.
Click to expand...
Click to collapse
Thanks mate for your help.
i have solved the problem.

Unable to receive SMS

I've got a bit of an issue here. Out of nowhere (I've had the latest OTAs for about 2 weeks now) I am unable to receive SMS. When one tries to come through I got a "com.android.phone has stopped". I was bone stock, no unlocked bootloader or anything. Since then, I have tried a couple different ROMs but still seem to be unable to get SMS. MMS come through fine and I can send outgoing messages, but SMS do not work. Data also seems to work fine.
Any ideas would be incredibly helpful.
Thank you!
ETA : On the first boot of a stock + root install, I was able ot send one before getting the error. I don't understand. After the error pops up once, I can not get any more SMS.
ETA 2 : I have flashed the factory CM11 image and still get the issue on CM11. I am at a loss and have no idea what else to do. It seems to be a hardware problem.
ETA 3 : Here is my exact crash report.
java.lang.NullPointerException: Attempt to invoke virtual method 'long com.android.internal.telephony.SmsMessageBase.getTimestampMillis()' on a null object reference
at android.telephony.SmsMessage.getTimestampMillis(SmsMessage.java:625)
at com.android.internal.telephony.InboundSmsHandler.notifyAndAcknowledgeLastIncomingSms(InboundSmsHandler.java:621)
at com.android.internal.telephony.InboundSmsHandler.handleNewSms(InboundSmsHandler.java:510)
at com.android.internal.telephony.InboundSmsHandler$DeliveringState.processMessage(InboundSmsHandler.java:397)
at com.android.internal.util.StateMachine$SmHandler.processMsg(StateMachine.java:966)
at com.android.internal.util.StateMachine$SmHandler.handleMessage(StateMachine.java:789)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.os.HandlerThread.run(HandlerThread.java:61)

I had the exact same problem on my wife's OPO, rooted, stock ROM, though it turned out slightly differently. The update gave the never-ending com.android.phone error. You can go into Airplane Mode to stop the crash. I read through the crash logs, and figured it was something to do with the APN. I deleted the APN, turned off Airplane Mode, and the crash stopped.
Phone and SMS work fine, as does wi-fi. However, I couldn't get any data at all. Not a great solution. I couldn't manually set the APN either, since I got a "APN Settings not allowed for this user" message, and removing the SIM, rebooting without it, then inserting it again, didn't help.
Also, root was removed. I installed TWRP and re-flashed the SuperSU zip file (make sure you go directly into recovery after the fastboot reboot or it'll flash Cyanogen Recover on top of TWRP and you have to start over!).
I did a full Titanium Backup as well as a Nandroid backup to a USB-OTG drive. Next step is to do a factory reset in TWRP and see if that fixes the APN issue.
Synyster06Gates said:
I've got a bit of an issue here. Out of nowhere (I've had the latest OTAs for about 2 weeks now) I am unable to receive SMS. When one tries to come through I got a "com.android.phone has stopped". I was bone stock, no unlocked bootloader or anything. Since then, I have tried a couple different ROMs but still seem to be unable to get SMS. MMS come through fine and I can send outgoing messages, but SMS do not work. Data also seems to work fine.
Any ideas would be incredibly helpful.
Thank you!
ETA : On the first boot of a stock + root install, I was able ot send one before getting the error. I don't understand. After the error pops up once, I can not get any more SMS.
ETA 2 : I have flashed the factory CM11 image and still get the issue on CM11. I am at a loss and have no idea what else to do. It seems to be a hardware problem.
ETA 3 : Here is my exact crash report.
java.lang.NullPointerException: Attempt to invoke virtual method 'long com.android.internal.telephony.SmsMessageBase.getTimestampMillis()' on a null object reference
at android.telephony.SmsMessage.getTimestampMillis(SmsMessage.java:625)
at com.android.internal.telephony.InboundSmsHandler.notifyAndAcknowledgeLastIncomingSms(InboundSmsHandler.java:621)
at com.android.internal.telephony.InboundSmsHandler.handleNewSms(InboundSmsHandler.java:510)
at com.android.internal.telephony.InboundSmsHandler$DeliveringState.processMessage(InboundSmsHandler.java:397)
at com.android.internal.util.StateMachine$SmHandler.processMsg(StateMachine.java:966)
at com.android.internal.util.StateMachine$SmHandler.handleMessage(StateMachine.java:789)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.os.HandlerThread.run(HandlerThread.java:61)
Click to expand...
Click to collapse

Raketemensch23 said:
I had the exact same problem on my wife's OPO, rooted, stock ROM, though it turned out slightly differently. The update gave the never-ending com.android.phone error. You can go into Airplane Mode to stop the crash. I read through the crash logs, and figured it was something to do with the APN. I deleted the APN, turned off Airplane Mode, and the crash stopped.
Phone and SMS work fine, as does wi-fi. However, I couldn't get any data at all. Not a great solution. I couldn't manually set the APN either, since I got a "APN Settings not allowed for this user" message, and removing the SIM, rebooting without it, then inserting it again, didn't help.
Also, root was removed. I installed TWRP and re-flashed the SuperSU zip file (make sure you go directly into recovery after the fastboot reboot or it'll flash Cyanogen Recover on top of TWRP and you have to start over!).
I did a full Titanium Backup as well as a Nandroid backup to a USB-OTG drive. Next step is to do a factory reset in TWRP and see if that fixes the APN issue.
Click to expand...
Click to collapse
Unfortunately nothing has worked. I have fully wiped the phone MANY times. I installed 4 different 5.0.2 ROMs, rolled back to factory 4.4.4 ROM via fastboot, and even tried a 5.1.1 ROM this morning. The only time it crashes is when I receive a text.

Synyster06Gates said:
Unfortunately nothing has worked. I have fully wiped the phone MANY times. I installed 4 different 5.0.2 ROMs, rolled back to factory 4.4.4 ROM via fastboot, and even tried a 5.1.1 ROM this morning. The only time it crashes is when I receive a text.
Click to expand...
Click to collapse
Have you tried flashing a new modem at all? It seems the only thing that would be the same still after flashing all of those various ROMs would be the modem. Seeing as you have issues with the communication, I'd say modem would be a good thing to try..
Try flashing your rom, then the appropriate modem, then boot.
You can get your modem from either here (for OxygenOS) which should work for CM12, 12.1, etc. or here (for CM11/CM11s)

The_Symbiote said:
Have you tried flashing a new modem at all? It seems the only thing that would be the same still after flashing all of those various ROMs would be the modem. Seeing as you have issues with the communication, I'd say modem would be a good thing to try..
Try flashing your rom, then the appropriate modem, then boot.
You can get your modem from either here (for OxygenOS) which should work for CM12, 12.1, etc. or here (for CM11/CM11s)
Click to expand...
Click to collapse
I'm beginning to think T-Mobile had an issue with the OPO devices or something. I was speaking with someone across the country (eliminating a tower problem) that was running Oxygen OS and I had restored to COS12 at the time. Both of our devices suddenly got all the texts that had previously not come in and they started working correctly at the same time. As of right now it seems I'm good to go.

Question Xiaomi Poco X3 Pro is constantly rebooting itself to recovery mode:

Hello,
About two months ago I successfully rooted that phone through Magisk. Now I am facing the told problem. I searched for some problems like mine, but it is not because of updates. I do not remember I have done something dangerous for the system. However, I tried to install this package. When I tried with the Android package installer, I got an error "it could not be installed". Then I tried to do it through this app manager for rooted devices, and it just stayed loading for a while until I just closed it. I entered the custom app manager and I realized that the app was recognized as an installed app, but however, I could not see it in the poco app launcher. I launched the app and it worked fine, but when tried to make f-droid a system app it displayed an error "/ directory could not be remounted as read-write". I left it be and removed that app. Everything fine... But the next morning the phone was asking for the SIM unlocking code. I unlocked both, the SIM and the phone, but after about five minutes it rebooted to MIUI recovery 5.0. If once in recovery mode the phone is inactive for a while, it automatically reboots to system. The rebooting time once unlocked the SIM was decreasing to two minutes. Apparently, it only will reboot if the SIM is unlocked, and the time is five minutes when the phone is cold and it decreases as it is being restarted. The phone it is not too hot when rebooted.
Thank you if you spent your time by reading the text above. Now the question: How can I fix it without losing my data? Regards.
PD: I do not have enough time to make a backup till it is rebooted, at least from system, and safe mode did not solve the issue.

You tried to install an obsolete app for moving apps to system, an app from 2016... no less?! What were you thinking?
Let me be honest and tell you that that move was extremely stupid. Chalk up your mistake to a brain fart, take the loss and try to reflash the firmware without formatting anything prior to doing so. Leave internal storage, dalvik, cache and everything else untouched. You just might make the phone bootable to backup your data, and then do a PROPER flash procedure.

Tomo123 said:
You tried to install an obsolete app for moving apps to system, an app from 2016... no less?! What were you thinking?
Let me be honest and tell you that that move was extremely stupid. Chalk up your mistake to a brain fart, take the loss and try to reflash the firmware without formatting anything prior to doing so. Leave internal storage, dalvik, cache and everything else untouched. You just might make the phone bootable to backup your data, and then do a PROPER flash procedure.
Click to expand...
Click to collapse
So therefore, which partition should I reflash with the stock ROM?

MxtApps said:
Hello,
About two months ago I successfully rooted that phone through Magisk. Now I am facing the told problem. I searched for some problems like mine, but it is not because of updates. I do not remember I have done something dangerous for the system. However, I tried to install this package. When I tried with the Android package installer, I got an error "it could not be installed". Then I tried to do it through this app manager for rooted devices, and it just stayed loading for a while until I just closed it. I entered the custom app manager and I realized that the app was recognized as an installed app, but however, I could not see it in the poco app launcher. I launched the app and it worked fine, but when tried to make f-droid a system app it displayed an error "/ directory could not be remounted as read-write". I left it be and removed that app. Everything fine... But the next morning the phone was asking for the SIM unlocking code. I unlocked both, the SIM and the phone, but after about five minutes it rebooted to MIUI recovery 5.0. If once in recovery mode the phone is inactive for a while, it automatically reboots to system. The rebooting time once unlocked the SIM was decreasing to two minutes. Apparently, it only will reboot if the SIM is unlocked, and the time is five minutes when the phone is cold and it decreases as it is being restarted. The phone it is not too hot when rebooted.
Thank you if you spent your time by reading the text above. Now the question: How can I fix it without losing my data? Regards.
PD: I do not have enough time to make a backup till it is rebooted, at least from system, and safe mode did not solve the issue.
Click to expand...
Click to collapse
flash the stock firmware with miflashtool and select de option "save_user_data" and done, the firmware will be flashed and your data will stay there

tutibreaker said:
flash the stock firmware with miflashtool and select de option "save_user_data" and done, the firmware will be flashed and your data will stay there
Click to expand...
Click to collapse
OK, that flash was successful, the root and the custom recovery were lost, but it is still rebooting. Should I flash all?

MxtApps said:
OK, that flash was successful, the root and the custom recovery were lost, but it is still rebooting. Should I flash all?
Click to expand...
Click to collapse
if you flash all your data will be lost, any way to install custom recovery and save your data from it ?