Develop Bugs

[Q] Package File Signature Error help

Hello my name is Sean and I have recently rooted my phone (captivate glide) and installed a custom ROM. Whenever I try to update apps like the AT&T Code Scanner, Qik Video Lite, Andoid Keyboard, or even Google Play itself I receive this error message:
"Package file was not signed correctly. Uninstall the previous copy of the app and try again."
Also when I run certain apps like Spot Hero or Clash of Clans I get the following message:
"Google Play services, which some of your applications rely on, is not supported by your device. Please contact the manufacturer for assistance."
I have searched the forums and found a few instances with similar problems, but the issue was either never resolved or didn't match the problem I was experiencing. I've Googled the problem and a few folks suggested using Titanium Back Up to uninstall the app in question and then re-install, but I have read some users say that they are then unable to re-install the app. I don't want to lose any functionality, so I haven't tried that.
Here is a step-by-step of what I did to my phone:
1) Shutdown my phone and rebooted into download mode with Odin 3.04 running
2) Flash CLOCKWORK MOD RECOVERY 6.0.1.2 (found here)
3) Reboot in download mode
4) Flash stock ICS ROM (found here)
5) Flash Superuser 3.2-RC3-arm-signed.zip (following the instructions found here)
5) Flash GApps.zip for 4.0.4 (found here)
6) Reboot and the phone says it's upgrading Android and optimizing applications
7) Once the phone is booted up and the SD card is done scanning I run into the problem described above
Has anyone encountered this problem before? If so, please share your insights.
Thanks for reading and if you have any suggestions I would welcome the help.

hello
i remember i had same problem when i was using ics, i think you shoulr flash anotherics gapps from diferent source. I do not remember where i downloaded mine

I tried some different gapps and I got some apps like Hangouts to update, but now I receive this message when I try to install Google Play Services:
"Incompatible with other application(s) using the same shared user ID."

I did some further looking into this and found that if I wiped my /system data and reflashed my gapps.zipp that seems to work. I installed Youtube first (since it requires Google Play Services) and that took care of everything.
Unfortunately I have lost any progress I may have made in my game apps and have to download/update everything from scratch and reset my ring tones and such, but at least I have a fully functional, rooted phone.

Actually I take that back. Google Play Services seems to be cooperating, but now I'm getting the package file signature problem again.

I resolved the issue by starting over and following Rawr0w0's guide half way down this thread.

SM-P607T stuck in 4.4.2

Hello everyone,
i bought the SM-P607T during my deployment in Afghanistan over Ebay USA . Spending my time there i tested the device and installed all updates etc. Back in Germany just my wife used it. Some weeks ago i noticed that an update to Lollipop should be avaible so i took the device to bring it up to date and i noticed some problems.
(Please note that i am just a noobie to flashing and rooting android and just follow guides to get to my goal.)
1. Device only loading while shut down. (After rooting and installation of TWRP it strangely started to load while on again even on PC USB connection)
2. Its not possible to connect the device with any PC.
3. OTA updates stop at around 27% and fail (KitKat 4.4.4)
[In TWRP shown
"E: Error executing updater binary in zip /data/fota/update.zip
E: Error installing zip file /data/fota/update.zip"]
Strange enough that the update info shown in android is Chinese Version
Tried to get some support with Samsung Europe but unfortunately they say US device US problem......
So what did i do in the meantime
1. Tried different loading devices frome Samsung and 3rd party companys. No changes.
2. Tried several different data cables to connect to 4 different PC. Even the one wich worked good with my Honor7 or the Galasy S4 mini dont do with the 607
3. My last try to fix this problem was to change the USB charging dock completely. Also didn´t change anything.
4. Now the step where i am currently stuck. I managed to root the device and install TWRP(v2.8.7.0) . Now tried to install Version P607TUVUBOI2 via SD Card.
Just followed diffenrent Guides on youtube and forums but im stuck at this.
Here is the message i got in TWRP recovery:
"Installing /external_sd/1/TMB-P607TUVUBOI2-20510930112901.zip
Checking for MD5 file....
Skipping MD5 check : no MD5 file found
Error flashing /external_sd/1/TMB-P607TUVUBOI2-20510930112901.zip
updating partition details......
Checked the *.zip on my PC there was just this file in: P607TUVUBOI2_P607TTMB1BOI2_P607TUVUBOI2_HOME.tar.md5
Downloaded the file from a different source again with same result
It would be very nice if someone is capable to help me with this and give me a hint what i possibly did wrong (Please do not mention not to buy in the US). For me it doesnt matter if i got a rooted or not routed version to install my main goal is to get rid of 4.4.2 . The problem with the not working USB connection is the biggest show stopper for me.

[email protected] said:
Hello everyone,
i bought the SM-P607T during my deployment in Afghanistan over Ebay USA . Spending my time there i tested the device and installed all updates etc. Back in Germany just my wife used it. Some weeks ago i noticed that an update to Lollipop should be avaible so i took the device to bring it up to date and i noticed some problems.
(Please note that i am just a noobie to flashing and rooting android and just follow guides to get to my goal.)
1. Device only loading while shut down. (After rooting and installation of TWRP it strangely started to load while on again even on PC USB connection)
2. Its not possible to connect the device with any PC.
3. OTA updates stop at around 27% and fail (KitKat 4.4.4)
[In TWRP shown
"E: Error executing updater binary in zip /data/fota/update.zip
E: Error installing zip file /data/fota/update.zip"]
Strange enough that the update info shown in android is Chinese Version
Tried to get some support with Samsung Europe but unfortunately they say US device US problem......
So what did i do in the meantime
1. Tried different loading devices frome Samsung and 3rd party companys. No changes.
2. Tried several different data cables to connect to 4 different PC. Even the one wich worked good with my Honor7 or the Galasy S4 mini dont do with the 607
3. My last try to fix this problem was to change the USB charging dock completely. Also didn´t change anything.
4. Now the step where i am currently stuck. I managed to root the device and install TWRP(v2.8.7.0) . Now tried to install Version P607TUVUBOI2 via SD Card.
Just followed diffenrent Guides on youtube and forums but im stuck at this.
Here is the message i got in TWRP recovery:
"Installing /external_sd/1/TMB-P607TUVUBOI2-20510930112901.zip
Checking for MD5 file....
Skipping MD5 check : no MD5 file found
Error flashing /external_sd/1/TMB-P607TUVUBOI2-20510930112901.zip
updating partition details......
Checked the *.zip on my PC there was just this file in: P607TUVUBOI2_P607TTMB1BOI2_P607TUVUBOI2_HOME.tar.md5
Downloaded the file from a different source again with same result
It would be very nice if someone is capable to help me with this and give me a hint what i possibly did wrong (Please do not mention not to buy in the US). For me it doesnt matter if i got a rooted or not routed version to install my main goal is to get rid of 4.4.2 . The problem with the not working USB connection is the biggest show stopper for me.
Click to expand...
Click to collapse
I really confused about your description? you using twrp to flash a .zip rom? then you mentioned about .md5 rom on your pc? how did you flash? With .md5 rom you need to use Odin to flash. Can you boot into download mode (hold down volume down + Home buttons then press power button)? If you able to boot to download mode, your pc should able to see the device and you would use Odin to flash the .md5 rom from your pc to the device. Also where did you download the .zip rom?

Stuck in setup wizard after factory reset

Alright, hello everyone,
I'm having a pretty weird issue here. I've flashed my DUK-L09 and the C432B183 EU Firmware, everything was running fine.
I couldn't make a backup of the /data/ partition though, someone told me to wipe the data to decrypt it, but nothing came good after this.
So I tried to flash back the old recovery image by extracting it, flashing it via fastboot, as I would normally do; enter the factory reset, run it.
Everything is good, it goes up to 100% pretty fast, less than 2 minutes. I then enter the setup wizard the NFC is acting weird. It keeps activating
and deactivating illogically. So, ignoring this issue, I kept up configuring the phone then once I'm logged in Google and sync'd, pops a Huawei ID
logging page really really fast then goes back to the EMUI menu at the beginning of the Setup, in an infinite loop.
Useful information to let you help me better:
- Many firmwares. Currently trying to flash back to B120a and NoCheck from OldDroid and Morph. (Edit: Didn't work)
- Phone unlocked, TWRP accessible.
- Getting a weird "Error 9" when trying to run Update.zip from TWRP.
- Sideload working, but not transferring anything.
- Cannot find any B182 or B130 stock firmware. Everything seems to be gone from Huawei's servers.
- The loading logo isn't Honor anymore but Android, for a reason I can't yet understand.
- Restoring a clean backup (without /data/, since I couldn't back it up) did not fix the problem.
- Trying to update with the 3 buttons do not work, even with the right firmware (C432B183) (Software install failed)
- Factory reset works with the right ROM, but gets me to the setup loop issue.
- The loop occurs when I am supposed to see the Huawei ID setup page. If I do not put any SIM card, or WiFi
I am prompted to choose which way to restore data; if I skip this step, it blinks and doesn't do anything.
- I tried to restore via WiFi (Google's cloud stored data from my account), but it does the same thing as mentioned
earlier. It blinks multiple times rapidly the "Huawei ID" setup page then goes back to the first Setup screen w/o
me being able to do anything about that.
I'll be glad if you knew the answer to this, because I'm all lost right now.
Greetings, Kameyuu.

UP !
After many tries and a LOT of hard work, and spent an entire night (was about to spend the second night on this), I found the culprit and now I know what the issue is, it sounds completely legitimate.
So here are the reason and the solution to this issue:
Actually, my CUST was somehow broken. I never flashed it back because no one told me to flash the CUST.img back. They told me to flash BOOT, SYSTEM, and RECOVERY only.
So, after I downloaded a software called HUAWEI Multi-Tool (From hwmt.ru) I noticed they were also asking for the CUST.img and USERDATA.img (<- this one was apparently optional)
So, trying my luck I flashed it. Did a factory reset, and all, it acted weird and failed, then I tried again and it succeeded. So, with all my hope I booted the phone to the system, started configuring... And it worked !
I was able to set up the phone. For a -yet- unknown reason, some apps look missing and the NFC is still blinking on and off repeatedly and randomly, but I'm investigating that.
If you have any question on the precise steps feel free to send me a PM or ask in the thread directly I'll be glad to sort your issue out.

[EDIT]
Sorry, double post I don't know why my message was posted twice. Feel free to delete this message @moderators

[SOLVED] Soft brick (?) on Z1C-based ZPG handheld

SOLVED: I figured out the issue. As mentioned in this thread, downgrading to an older version of flashtool successfully got me past the bundle mismatch error, allowing me to flash stock US firmware onto the device. Still not exactly sure why that's the case, but it worked for me.
Hey folks,
Hope you're all doing well! I have a bit of an odd situation. I recently picked up a Z-Pocket Game, a handheld built using the internals from a torn down Z1 Compact.
A few days ago, I decided to see if I could poke around and install a custom ROM onto the device, given how many are available for the source hardware (Z1C). The device already came pre-installed with XZDualRecovery and was running a custom ROM in Chinese built off Lollipop.
I'm a novice when it comes to flashing and custom ROMs, so I tried to learn more about the process before getting started. Evidently, however, I'm in over my head - fully my responsibility, of course, but over my head nonetheless.
Long story short, I tried to install Lineage OS 17.1 onto the device via the version of TWRP already installed on the device. As per the installation instructions detailed here, I did an advanced wipe before attempting the install, selecting "Dalvik," "System," "Cache," and "Data." When I actually attempted the process, however, it errored out almost immediately, leaving me with a wiped system and no ROM (TWRP warned me about this prior to rebooting).
When I now power on the device, it's stuck on the "Sony - XPERIA" screen, and the LEDs don't light up at all. I can't seem to access TWRP or Philz on the device with the normal key presses. I can force the device off by holding Power and Volume Up, and it also seems able to enter fastboot mode (with a solid blue LED) and flash mode (the LED flashes green, then turns off). I've tried a number of different things to try and fix it, but all of them haven't worked in one way or another. Providing a brief overview to the best of my recollection here, but happy to try again and give more detail if needed:
Using fastboot via the command line to flash a new recovery onto the device gives me an error indicating I can't write the file to the device, and things just end there.
Trying to flash a stock US ROM to the device via flashtool gives me an error indicating the device does not match the bundle, and things just end there.
Trying to restore the device using Xperia Companion first gives an error requesting permission to access the device, then when I select "My Device Cannot Be Detected or Started" and follow the instructions, it tells me that "an error occurred while repairing this device," and provides this small blurb of device info:
UEGetPhoneInfoMissingInfo
Z-POCKET GAME 3579 1279-6978 R2D 14.6.A.1.236
2.11.6.0 / Windows 10 64 bit / Win32 / US / /
So I'm a bit stumped. It seems as though enough of the device is working to get everything back into a workable state, but I'm not sure of how to go about that. Any thoughts or leads would be greatly appreciated!

edit_duplicate said:
SOLVED: I figured out the issue. As mentioned in this thread, downgrading to an older version of flashtool successfully got me past the bundle mismatch error, allowing me to flash stock US firmware onto the device. Still not exactly sure why that's the case, but it worked for me.
Hey folks,
Hope you're all doing well! I have a bit of an odd situation. I recently picked up a Z-Pocket Game, a handheld built using the internals from a torn down Z1 Compact.
A few days ago, I decided to see if I could poke around and install a custom ROM onto the device, given how many are available for the source hardware (Z1C). The device already came pre-installed with XZDualRecovery and was running a custom ROM in Chinese built off Lollipop.
I'm a novice when it comes to flashing and custom ROMs, so I tried to learn more about the process before getting started. Evidently, however, I'm in over my head - fully my responsibility, of course, but over my head nonetheless.
Long story short, I tried to install Lineage OS 17.1 onto the device via the version of TWRP already installed on the device. As per the installation instructions detailed here, I did an advanced wipe before attempting the install, selecting "Dalvik," "System," "Cache," and "Data." When I actually attempted the process, however, it errored out almost immediately, leaving me with a wiped system and no ROM (TWRP warned me about this prior to rebooting).
When I now power on the device, it's stuck on the "Sony - XPERIA" screen, and the LEDs don't light up at all. I can't seem to access TWRP or Philz on the device with the normal key presses. I can force the device off by holding Power and Volume Up, and it also seems able to enter fastboot mode (with a solid blue LED) and flash mode (the LED flashes green, then turns off). I've tried a number of different things to try and fix it, but all of them haven't worked in one way or another. Providing a brief overview to the best of my recollection here, but happy to try again and give more detail if needed:
Using fastboot via the command line to flash a new recovery onto the device gives me an error indicating I can't write the file to the device, and things just end there.
Trying to flash a stock US ROM to the device via flashtool gives me an error indicating the device does not match the bundle, and things just end there.
Trying to restore the device using Xperia Companion first gives an error requesting permission to access the device, then when I select "My Device Cannot Be Detected or Started" and follow the instructions, it tells me that "an error occurred while repairing this device," and provides this small blurb of device info:
UEGetPhoneInfoMissingInfo
Z-POCKET GAME 3579 1279-6978 R2D 14.6.A.1.236
2.11.6.0 / Windows 10 64 bit / Win32 / US / /
So I'm a bit stumped. It seems as though enough of the device is working to get everything back into a workable state, but I'm not sure of how to go about that. Any thoughts or leads would be greatly appreciated!
Click to expand...
Click to collapse
Glad that you find out yourself.
And thanks for sharing!

PLZ HELP: Android System keeps stopping.

I have a Magisk Rooted, Samsung Galaxy Note 10+ (SM-N975F), stock ROM running Android 10.
When I am booted in Root mode I try to open a file in the "My Files" app and I keep getting the error "Android System keeps stopping" but when I try in un-Rooted mode it works perfectly fine.
Is there a way around this issue that does NOT involve me having to wipe all my data and files because I believe this has something to do with anti-root implementations or something of the sort since the files open fine when I boot un-Rooted but throw the error "Android System keeps stopping" when I boot with Root.
I can provide more device information if needed, I mostly understand what I am doing but I am by no means a "Rooting Pro", I would consider myself intermediate at best.
Thanks in advance for any help that can be given.