Related
i tried updating to an rooted kitkat version as we as get the Native hotspot going for my Sprint GS4.. however i did something wrong and now. i keep getting pop ups stating "unfortunately, SAE has stopped as well as many other programs.. how can i get this fixed.. i have tried factory reset, and to return to an stock firmware, but i cant get odin to pass. it keeps failing.. I have downloaded all the necessary stock firmware files, drivers etc.. . I can get a recovery to flash,, but the pop-ups for "stopped apps" still appear.. and i cant get pass them.. .
Same issue here
I have tried odin with stock tar and it fails I have no idea where to go next. I am sure it has something to do with the services.jar and services.odex files but how do you get around that.
Dee Bee said:
i tried updating to an rooted kitkat version as we as get the Native hotspot going for my Sprint GS4.. however i did something wrong and now. i keep getting pop ups stating "unfortunately, SAE has stopped as well as many other programs.. how can i get this fixed.. i have tried factory reset, and to return to an stock firmware, but i cant get odin to pass. it keeps failing.. I have downloaded all the necessary stock firmware files, drivers etc.. . I can get a recovery to flash,, but the pop-ups for "stopped apps" still appear.. and i cant get pass them.. .
Click to expand...
Click to collapse
Dude here is your answer use odin and install clockworkmod latest addition... then download stock kit kat zip put it on your sd card and install via clockworkmod. This work for me cause I was having the same issue. Peace out.
Also having this issue. It started before I rooted. First I did a factory reset, (and assuming that would fix the issue on a completely stock unrooted phone) decided if I was doing a reset there would be no safer time for me to root. So I CF-Autorooted and enabled native hotspot. I believe this is possibly somehow related to my phone and the play market because updating or installing apps seemed to be the common element triggering them to start failing. Google Search would fail over and over every half second after I dismissed the notification making the phone all but unusable, so I did another factory reset, and now SAE (presumably samsung account setup?) is what fails without even the half second in between, completely unusable. I'm afraid my last hope is to one-click it.
Hey guys..This website has solved a lot of problems..So I hope it solve this too
My problem started when I flashed Cm12.1 on my s3 neo gt-i9031I
The ROM was flashed and it worked perfectly..And then I installed SuperSu app from the play store
And here the problem comes..the app said that it needs to update Su binary
I tried the normal way but then it said "Installion failed,Please reboot and try again"
And after rebooting several times it keeps saying the same thing
I tried using option twrp (I have twrp recovery installed)
It said that the app will attempt to reboot my phone to recovery..But then nothing happened. didn't reboot or do anything.. I booted into recovery but nothing happened either
Then I saw a YouTube video that has Su bb installer
I downloaded a zip and flashed it via recovery.. And the problem got worser..After I booted..I found that SuperSu icon has changed..To the old version.. The superman icon..When I try to open it...It doesn't open and lags the phone..
Tried to update via play store
Successfully updated but it doesn't wanna open and it made the phone laggy
I had to uninstall updates..Force stop and disable and the phone returned back to normal..No lags
But now I am in unrooted status I think.. can't open the app or remove it cuz it was a system app
I think the problem got worser when I flashed the Su Bb installer which the video said that it works for every phone
I think it was too old..I don't know..please help..Sorry for the too long topic..I am afraid of rerooting cuz I am already rooted but I can open the app..HELP..HELP..HELP
The Su bb installer link that I used
https://www.androidfilehost.com/?fid=9390233485161005747
Don't do anything. Just re flashed CM 12.1 or any CM ROM. before do anything read their instructions carefully. Ok
In all CM based ROMs the root is disabled by default. Go to settings>About Device and click on Build Number 7 times. Return back and you will have Developers options just above About Device menu. Go in there and there you can unable root access. After that do whatever you want.
Bear with me here, tis a long and windy tale!
I'm getting a "Parse Error: there is a problem while parsing this package" whenever I try and install an apk copied to my phone.
Used to work fine until the following:
Have a Galaxy S5, SM-G900F.
Came with carrier firmware when I got it last year, flashed stocked btu, rooted with towelroot, and updated it to 4.4.2
Worked like a charm.
With EE now offering Wifi-Calling, decided to update to lollipop, and that's were **** started to go wrong.
Looked into this, and discovered that FlashFire would keep the root, and update to a newer fimware.
Using the stock btu, did it. Everything went great.
Couldn't find the wifi-calling option
Read up about it a bit more, some places said needed to clear the cache.
Did so, nope.
Tried a deodex firmware: http://forum.xda-developers.com/galaxy-s5/development/rom-t3078179
Still no luck.
Then I came across EE support forums, which said it had to be carrier firmware, to use wifi-calling.
Grabbed the latest version, Used Flashfire to flash it.
Encountered a ton of errors.
Constant "system ui has stopped working" "weather ui has stopped working" errors.
Tried clearing the cache again, no luck.
Didn't factory reset at this point, and probably where I made another mistake.
Flashed it back to ambadasii, decided to follow some instructions by clearing the davlik cache. Bad choice :crying:
Flashed twrp, forgetting that this would trip knox. :silly:
Cleared cache, cleared davlik. Still no luck.
At this point, with knox tripped, there was nothing really stopping me.
So used odin to flash the EE evr firmware to the phone.
Same "ui has stopped working" errors.
Cleared cache, reset to factory default.
All errors stopped.
And finally have the Wifi-calling option (f*cking yay )
Flashed twrp again, installed SuperSu to root it.
And now busy using Titanium backup to restore my apps and settings.
Tl:dr Wanted the new wifi-calling option on lollipop, got impatient and screwed something up during flashing.
Thanks for reading this far!
Edit: Forgot to mention.
Yes it used to install apk's from the phone and sd card perfectly fine before.
Yes usb debugging and allow unsigned apps are both on.
Apk is fine, installs on my nexus tablet fine (5.1)
amaru007 said:
Bear with me here, tis a long and windy tale! [emoji14]
I'm getting a "Parse Error: there is a problem while parsing this package" whenever I try and install an apk copied to my phone.
Used to work fine until the following:
Have a Galaxy S5, SM-G900F.
Came with carrier firmware when I got it last year, flashed stocked btu, rooted with towelroot, and updated it to 4.4.2
Worked like a charm.
With EE now offering Wifi-Calling, decided to update to lollipop, and that's were **** started to go wrong.
Looked into this, and discovered that FlashFire would keep the root, and update to a newer fimware.
Using the stock btu, did it. Everything went great.
Couldn't find the wifi-calling option
Read up about it a bit more, some places said needed to clear the cache.
Did so, nope.
Tried a deodex firmware: http://forum.xda-developers.com/galaxy-s5/development/rom-t3078179
Still no luck.
Then I came across EE support forums, which said it had to be carrier firmware, to use wifi-calling.
Grabbed the latest version, Used Flashfire to flash it.
Encountered a ton of errors.
Constant "system ui has stopped working" "weather ui has stopped working" errors.
Tried clearing the cache again, no luck.
Didn't factory reset at this point, and probably where I made another mistake.
Flashed it back to ambadasii, decided to follow some instructions by clearing the davlik cache. Bad choice :crying:
Flashed twrp, forgetting that this would trip knox. :silly:
Cleared cache, cleared davlik. Still no luck.
At this point, with knox tripped, there was nothing really stopping me.
So used odin to flash the EE evr firmware to the phone.
Same "ui has stopped working" errors.
Cleared cache, reset to factory default.
All errors stopped.
And finally have the Wifi-calling option (f*cking yay )
Flashed twrp again, installed SuperSu to root it.
And now busy using Titanium backup to restore my apps and settings.
Tl:dr Wanted the new wifi-calling option on lollipop, got impatient and screwed something up during flashing.
Thanks for reading this far!
Edit: Forgot to mention.
Yes it used to install apk's from the phone and sd card perfectly fine before.
Yes usb debugging and allow unsigned apps are both on.
Apk is fine, installs on my nexus tablet fine (5.1)
Click to expand...
Click to collapse
Open/install terminal emulator and do "pm install /path/to/application.apk", it will give you aore detailed error about whats going wrong.
Sent from my Tw5ted SM-G900A using Tapatalk
Tried that, and got the following error: Error: java.lang.SecurityException: Neither user 10312 nor current process has android.permission.INSTALL_PACKAGES.
amaru007 said:
Tried that, and got the following error: Error: java.lang.SecurityException: Neither user 10312 nor current process has android.permission.INSTALL_PACKAGES.
Click to expand...
Click to collapse
Ah, try doing su first so you are running as root.
Sent from my Tw5ted SM-G900A using Tapatalk
Okay.
tried with su:
pkg: whatever.apk
Failure [INSTALL_FAILED_INVALID_URI]
Looking like Titanium restore hasn't worked properly either, loads of programs needing to be reinstall again.
Dunno if its connected to this problem or not.
Invalid uri means you did the path wrong, tab complete the path(volup+t i think, if not voldown+t) so you have it exactly correct, it doesnt matter if you are already in the directory containing the apk it needs the full path.
Sent from my Tw5ted SM-G900A using Tapatalk
Ah ok.
With the full path: Failure [INSTALL_FAILED_INVALID_APK]
Funny enough, some apk's install this way some don't.
amaru007 said:
Ah ok.
With the full path: Failure [INSTALL_FAILED_INVALID_APK]
Funny enough, some apk's install this way some don't.
Click to expand...
Click to collapse
So the error is consistently failed invalid apk? The ones that install fine on other devices?
Sent from my Tw5ted SM-G900A using Tapatalk
Did a complete wipe of the phone, dalvik, cache and phone.
Reinstalled all apps from Play store from recovery.
Restored just system and app data with Titanium backup.
Other apk's are now installing fine on this device now, just not this one.
Uninstalled and tried reinstalling the apk on the other device, and it failed.
Looked into it further, seems there's been an update to the apk recently, downloaded it and now it works!
Weird since it worked on 5.0 and 5.1 before on the tablet, but once uninstalled, got the apk parse error on that too.
Thanks for all the help Rakuu.
amaru007 said:
Did a complete wipe of the phone, dalvik, cache and phone.
Reinstalled all apps from Play store from recovery.
Restored just system and app data with Titanium backup.
Other apk's are now installing fine on this device now, just not this one.
Uninstalled and tried reinstalling the apk on the other device, and it failed.
Looked into it further, seems there's been an update to the apk recently, downloaded it and now it works!
Weird since it worked on 5.0 and 5.1 before on the tablet, but once uninstalled, got the apk parse error on that too.
Thanks for all the help Rakuu.
Click to expand...
Click to collapse
No problem, glad you got it figured out.
Sent from my Tw5ted SM-G900A using Tapatalk
I'm wondering what the issue might be where one day APK files are installing correctly then the next day every attempt to install, whether through:
1) a file manager,
2) separate installer program, or
3) via each individual program's update feature,
all fail with the "there was a problem while parsing this package" error.
I used the great suggestion from Rakuu to try via the terminal (e.g. `# pm install /storage/emulated/0/Download/filename.apk`) and like magic, it works (installs successfully) with no error whatsoever.
However, no package file irrespective of source (all tested fine with archive programs and including previously successfully installed apk's) can be installed via the android interface.
Risk3 said:
I'm wondering what the issue might be where one day APK files are installing correctly then the next day every attempt to install, whether through:
1) a file manager,
2) separate installer program, or
3) via each individual program's update feature,
all fail with the "there was a problem while parsing this package" error.
I used the great suggestion from Rakuu to try via the terminal (e.g. `# pm install /storage/emulated/0/Download/filename.apk`) and like magic, it works (installs successfully) with no error whatsoever.
However, no package file irrespective of source (all tested fine with archive programs and including previously successfully installed apk's) can be installed via the android interface.
Click to expand...
Click to collapse
No clue, usually if it errors in the visual installer it will also with command line, maybe try a factory reset? I'm not too sure, that's odd.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Turns out that the inability to install from the user interface coincides with a Cyanogenmod 13 (6.0.1) nightly upgrade. I'll either go back to a snapshot or try another nightly next week and see if that helps things along.
Thanks for your reply.
Hello
Any one know how to root latest nougat release?????
G935FXXU1DPLT
sriszone said:
Hello
Any one know how to root latest nougat release?????
G935FXXU1DPLT
Click to expand...
Click to collapse
Root same way as you rooted marshmallow. Flash twrp, flash supersu 2.79. everything is the same. it will take a while to boot though be patient.
Flash TWRP in Odin
Flash SR3-SuperSU-v2.79-SR3-20170114223742.zip in TWRP
no its not working......After install recovery stuck in Samsung Flashing logo....
TWRP is making the devices get stuck on Samsung logo....
I think what is happening is that when you install only the twrp the encryption of the device conflicts and leaves in bootoolp. When you install twrp and root , root already comes with a tool that takes out the encryption. But if you just want twrp, as was my case, you should, first of all, on your own twrp, wipe data and then flash no-verity-opt-encrypt.
Having root and no encryption sucks. Think I'll wait
Found Some Official Announcement From @Chainfire
Source :- Link
ChainFire Info
I'm not entirely sure what is going on here yet. I've had the stock firmware randomly stop booting even without modifying the boot image (rooting). Others have also reported that just flashing TWRP may trigger a bootloop (which is weird). I have some ideas what the cause may be, but it will be some time before I can properly investigate them.
The only way I seem to reliably get both TWRP and SuperSU working right now is:
- Flash TWRP (3.0.2-5) to recovery
- Immediately boot into TWRP
- If you were encrypted, format /data (ext4) and reboot into TWRP again
- Flash SuperSU v2.79-SR3 in TWRP
- Reboot into Android
The first boot will take a while if you performed that format, but for me it ultimately completes. Note that your device will be running unencrypted at this point!
Of course, if you format /data, you will lose all your data (including contents of internal storage!). Before I flashed the new version, I used FlashFire v0.54-PRE to create a backup of /data and internal storage to the removable sdcard, and restore that backup after flashing DPLT, rooting, and reinstalling FlashFire. This worked fine for me, and all my settings - including fingerprints and system settings - transferred fine. I came from the first Nougat beta, but I've seen others reporting success doing the same thing coming from Marshmallow. As always, your mileage may vary.
Unfortunately, due to this boot-loop issue with DPLT and encrypted data, it is also impossible to use FlashFire to upgrade the firmware itself to DPLT while keeping root if you started with an encrypted device.
I am not sure if the same difficulties exist with other official builds than DPLT, nor if the same problems occur with any of the custom ROMs based on DPLT. The S7 is my daily driver so I don't like to experiment with it too much
Below attach the required Files, I gonna try tomorrow. If anyone tried now please report update.
DOWNLOAD HERE
I did root few minutes ago on my 7.0 but now im not unable to launch s health because knox is disabled.
sriszone said:
Found Some Official Announcement From @Chainfire
Source :- Link
ChainFire Info
I'm not entirely sure what is going on here yet. I've had the stock firmware randomly stop booting even without modifying the boot image (rooting). Others have also reported that just flashing TWRP may trigger a bootloop (which is weird). I have some ideas what the cause may be, but it will be some time before I can properly investigate them.
The only way I seem to reliably get both TWRP and SuperSU working right now is:
- Flash TWRP (3.0.2-5) to recovery
- Immediately boot into TWRP
- If you were encrypted, format /data (ext4) and reboot into TWRP again
- Flash SuperSU v2.79-SR3 in TWRP
- Reboot into Android
The first boot will take a while if you performed that format, but for me it ultimately completes. Note that your device will be running unencrypted at this point!
Of course, if you format /data, you will lose all your data (including contents of internal storage!). Before I flashed the new version, I used FlashFire v0.54-PRE to create a backup of /data and internal storage to the removable sdcard, and restore that backup after flashing DPLT, rooting, and reinstalling FlashFire. This worked fine for me, and all my settings - including fingerprints and system settings - transferred fine. I came from the first Nougat beta, but I've seen others reporting success doing the same thing coming from Marshmallow. As always, your mileage may vary.
Unfortunately, due to this boot-loop issue with DPLT and encrypted data, it is also impossible to use FlashFire to upgrade the firmware itself to DPLT while keeping root if you started with an encrypted device.
I am not sure if the same difficulties exist with other official builds than DPLT, nor if the same problems occur with any of the custom ROMs based on DPLT. The S7 is my daily driver so I don't like to experiment with it too much
Below attach the required Files, I gonna try tomorrow. If anyone tried now please report update.
DOWNLOAD HERE
Click to expand...
Click to collapse
You can root but you have to disable encryption. Not a fan of that personally so I'll wait for another solution. If I lose my phone at least I'll have secure power up enabled. There is no bypassing that. There are too many FRP exploits on Youtube so having no encryption and simply a password isn't enough in my opinion.
---------- Post added at 10:29 PM ---------- Previous post was at 10:29 PM ----------
Mystero said:
I did root few minutes ago on my 7.0 but now im not unable to launch s health because knox is disabled.
Click to expand...
Click to collapse
Since you are rooted, uninstall S Health and install a lower version number which doesn't require Knox.
Galactus said:
Since you are rooted, uninstall S Health and install a lower version number which doesn't require Knox.
Click to expand...
Click to collapse
Hi, i cannot manage to unistall S Health, tried already two apps, after reboot app is still there and if i try to install older version i get corrupted file error.
guys please explain what is encryption and unencription here.... how can i disable ? can we flash this no-verity-opt-encrypt-5.0.zip
sriszone said:
Hello
Any one know how to root latest nougat release?????
G935FXXU1DPLT
Click to expand...
Click to collapse
I got fully working root and TWRP on Nougat G935FXXU1DPLT.
I have installed nougat btu with Odin.
Installed twrp and rooted my device.
So far I have faced couple of issues
s health app is not working
Security log agent keeps popping up (drives me mad)
And my device freezes and reboots after i open lucky patcher
How to fix these issues
cross_312 said:
I have installed nougat btu with Odin.
Installed twrp and rooted my device.
So far I have faced couple of issues
s health app is not working
Security log agent keeps popping up (drives me mad)
And my device freezes and reboots after i open lucky patcher
How to fix these issues
Click to expand...
Click to collapse
Security log will stop after you launch SU application and let SU to disable knox, it takes me always two attempts, disable, keep trying then i restart smartphone and after restart i try to disable knox again and it works, no more pop ups.
About S Health I'm looking for solution, so far should be enough to install older version set it up and update for new one, problem is that i cannot uninstall old version to get new one working.
cross_312 said:
I have installed nougat btu with Odin.
Installed twrp and rooted my device.
So far I have faced couple of issues
s health app is not working
Security log agent keeps popping up (drives me mad)
And my device freezes and reboots after i open lucky patcher
How to fix these issues
Click to expand...
Click to collapse
S Health is now locked down if you have tripped knox. The only solution is to use an older version.
Mystero said:
Security log will stop after you launch SU application and let SU to disable knox, it takes me always two attempts, disable, keep trying then i restart smartphone and after restart i try to disable knox again and it works, no more pop ups.
About S Health I'm looking for solution, so far should be enough to install older version set it up and update for new one, problem is that i cannot uninstall old version to get new one working.
Click to expand...
Click to collapse
SuperSU couldn't disable Knox for me after many tries. In the end I just used Titanium to freeze Knox.
CuBz90 said:
S Health is now locked down if you have tripped knox. The only solution is to use an older version.
SuperSU couldn't disable Knox for me after many tries. In the end I just used Titanium to freeze Knox.
Click to expand...
Click to collapse
What did work for me was try to disable when SU was trying i did restart device and right after restart i did tried that again and it worked. Maybe lucky...
About S Healht how can i use older version if i cannot install one because new one exist, do you know how to remove s health? i Tried two apps for removing system apps without success.
Mystero said:
What did work for me was try to disable when SU was trying i did restart device and right after restart i did tried that again and it worked. Maybe lucky...
About S Healht how can i use older version if i cannot install one because new one exist, do you know how to remove s health? i Tried two apps for removing system apps without success.
Click to expand...
Click to collapse
Try titanium. Backup the app first and then uninstall.
CuBz90 said:
Try titanium. Backup the app first and then uninstall.
Click to expand...
Click to collapse
Sir thank you, i do not know how it is possible that another apps did not worked but titanium did removed new S Health. Afterwards i did install last version of S Health i found before version 5, After launching S Health and connecting account i did update on new S health and everything works.
You really saved me. Thank you
Mystero said:
Sir thank you, i do not know how it is possible that another apps did not worked but titanium did removed new S Health. Afterwards i did install last version of S Health i found before version 5, After launching S Health and connecting account i did update on new S health and everything works.
You really saved me. Thank you
Click to expand...
Click to collapse
i have tried to remove the s health app with titanium but everytime i try to install vesrion 4.8 phone says that i can not install this app beacuse there is a package with the same name
what verison did you install before s health 5 and how did you install it.
and can anyone tell me how do i make lucky patcher to work properly
I did a full unroot of SuperSu to root with Magisk. After I root with Magisk, I get a few 'App has stopped working', I get
Unfortunately Logs Provider has stopped working
Unfortunately Media Storage has stopped working
Unfortunately Contacts Storage has stopped working
Unfortunately TouchWiz Home has stopped working*
Unfortunately User Dictionary has stopped working
Unfortunately Weather has stopped working
*I use Nova Launcher
I usually get them upon boot but sometimes I get them during regular usage
I've Tried
Reflashing correct firmware through Odin
Wiping Cache and Dalvik
Factory Resetting
Unrooting Magisk and Rerooting
How do I fix it, I am Running OS 5.0.2
Edit: Download Manager doesn't work as well when downloading APKs
Reflash it
ghg1 said:
I did a full unroot of SuperSu to root with Magisk. After I root with Magisk, I get a few 'App has stopped working', I get
Unfortunately Logs Provider has stopped working
Unfortunately Media Storage has stopped working
Unfortunately Contacts Storage has stopped working
Unfortunately TouchWiz Home has stopped working*
Unfortunately User Dictionary has stopped working
Unfortunately Weather has stopped working
*I use Nova Launcher
I usually get them upon boot but sometimes I get them during regular usage
I've Tried
Reflashing correct firmware through Odin
Wiping Cache and Dalvik
Factory Resetting
Unrooting Magisk and Rerooting
How do I fix it, I am Running OS 5.0.2
Edit: Download Manager doesn't work as well when downloading APKs
Click to expand...
Click to collapse
U need to flash the factory version of firmware .. I mean firmware that was given when u bought it .. check it sammobile website
Anu Darang said:
U need to flash the factory version of firmware .. I mean firmware that was given when u bought it .. check it sammobile website
Click to expand...
Click to collapse
Hi, I fixed this problem by updating my phone using smart switch on PC, thanks for the suggestion.
ghg1 said:
Hi, I fixed this problem by updating my phone using smart switch on PC, thanks for the suggestion.
Click to expand...
Click to collapse
No problem