safestrap describe error - Verizon Galaxy Note 3 Q&A, Help & Troubleshooting

safestrap describe error - Verizon Galaxy Note 3 Q&A, Help & Troubleshooting

I ran the new towlroot today. Installed busy box and su. Granted access to everything. I then downloaded the latest safestrap for my Verizon note 3. After download I tried to install the apk from my file explorer. It states something about describe error, trouble parsing every time. I've researched but the only person to have this issue had to do a factory reset a few times.

cterrell16 said:
I ran the new towlroot today. Installed busy box and su. Granted access to everything. I then downloaded the latest safestrap for my Verizon note 3. After download I tried to install the apk from my file explorer. It states something about describe error, trouble parsing every time. I've researched but the only person to have this issue had to do a factory reset a few times.
Click to expand...
Click to collapse
If you haven't already keep trying. I was getting the same error and after re-downloading 5-6 times it finally installed.

I finally got it. I had to download it to the installer instead of trying to open it uaing a file explorer.

Related

[Q] Cant install su/superser.zip from twrp rcvry

Alright,
I'm running the MF9 stock firmware. this is my second S4 both were L720's. I rooted my first s4 in my sleep with the auto root/stock recovery, with Odin and the .tar file. I kept the files on my computer, since i have vast amounts of space and partially lazy; i didn't delete them. When i got my second s4 the firmware was MF9. So i flashed the tar with Odin, everything seem to work fine. no errors or hangs, when it booted back up to main menu it didn't have super user..
I downloaded the super user app, from the app store, said my binaries are out dated and needed update
okay, go for it.. everything was smooth/green other then the out dated version of superuser. but when it tried to get root access it failed
I used Odin to install openrecovery-twrp-2.6.3.0-jfltespr.tar everything was smooth
used adb to boot to recovery, worked great twrp booted up
i installed the superuser.zip from there
everything was smooth no errors /cleared the cache
rebooted still no super on my desktop/app drawer
I'm trying to avoid flashing stock rom then trying to re-root if any other possible way to root my device
would greatly help.
for all the people that say"google is ur friend" ever link is purple that starts or has the words "root" "superuser" "L720"
it is my friend but people are smarter and more dynamic then Google "my friend"
Thanks,
-L

Solved!! L720 cant install su superuser in recovery twrp/ cant gain root
Ive been working on this for the last two days, seems like all i needed was to post, i work in a support desk. Oddly alot of people have issues when they have been trying to fix, yet when they ask for help, there either figure it out. or it simply fixes its self
Well, i fix this issue my self
i used file manager and went to the /system/apps folder
my plan was to erase all traces of super user and re-install
when i got to super user
it wasn't like the normal icons, this one was different from the ones ive personally installed from the app store
so i installed it
it uninstalled the"app store" super users and installed this one.
(i have uninstalled super user previously before this and tried to flash with no success, hence the deeper clean)
It went about installing, and BAM!! asked me to grant super user control, i agreed to the prompt and opened up busy box
it finally loaded up correctly asked for super user access. I granted it
Issue resolved> idk why this was harder then before, but it works that's what matters, I know no one posted here, but hope this helps at lest one other person then me, Thanks XDA and all the programmers/theme'rs/developers

[Q] Superuser problem

I have a problem with superuser that I can't understand.
So I bought this new Samsung Galaxy Note 3, and I rooted it by flashing my phone with Clockworkmod 6.0.4.5(1116) with Odin, and then installing UPDATE-SuperSU-v1.65.zip through the recovery window.
To be honest the process didn't go ideally smooth. Since I misunderstood how to proceed with the process, I had to reinstall Clockworkmod a few times.
After finishing from that, I started trying to use software that needs root access (like LuckyPatcher), and lucky patcher was hanging at the beginning black screen and not proceeding. And I tried many other programs, and they always don't proceed and stop.
So eventually I went to the Application Manager and select Superuser, and chose to "Uninstall updates", and only then, all those Superuser prompt messages started popping up asking me to grant LuckyPatcher and all other software that tried to access root... and since I chose to Uninstall updates, the phone restarted.
Of course, after the phone restarts, we're back at square 1, but the programs, to whom I granted root access get root access for some time...
I tried updating Superuser from the market, but when the program starts, it says "The Superuser binary (su) must be updated.", and I have a option called "Recovery Install", when I choose it, the phone keeps showing a message saying "Installing Superuser..." and it never finishes. Yesterday I left it and went to sleep, and eventually it gave an error message. I would say that Superuser update itself requires root access which it couldn't get... but that's as far as I know. I tried the "Uninstall updates" trick but it never worked.
Also I have to say I tried to install Superuser versions 1.51, 1.60, 1.65, 1.80 through recovery with a zip file, and it didn't fix it. And I installed CrashROM from here:
http://forum.xda-developers.com/showthread.php?t=2535355
and it didn't help either.
What do you think? How can I repair that and have normal Superuser permission asked normally? Please advise.
Thank you.

Any help, please?

Problem solved
The solution was to specifically install SuperSU from the market and not superuser. That fixed it.

Towel root

Does towel root method work on AN12 update. I have read the root methods for under AN12 but since this update has been out for a while now i thought maybe they got towel root to work.
Thank you in advance.
Sent from my GT-N5110 using XDA Premium HD app

Short answer is yes, however, you will need to ODIN your kernel first then gain root with towel root. Read this thread http://forum.xda-developers.com/showthread.php?t=2784860

Towelroot v3 refuses to install on Galaxy S5 from Verizon.
I'm having problems getting Towelroot v3 installed on my Verizon Wireless, Samsung Galaxy S5 16mb phone.
We were running fine while being rooted under V4.4.4 and Rom *NHA*.
We removed SuperSU, and uninstalled. it.
We installed the update, with no problems.
We rebooted, into Download mode, and flashed Kernel *NCG* .
We copied Towelrootv3 over and attempted to install it... (This is where the problem begins...)
We attempt to install TowelrootV3.apk. We get the popup that gives us the warning, along with the checkbox, we select the checkbox, which allows us to go ahead with the installation... the install begins but then suddenly says, "App not installed". (??????)
I have ensured that we are booted up under the NCG Kernel, and that we have selected:
Settings ->Security->Unknown Sources [ck'd]
Settings->Security->Verify Apps [Ck'd']
Developer Options->USB Debugging [not Ckk'd]
Developer Options->Allow Mock Locations [Chk'd]
No matter how many times that we try to install it, with different settings etc.... it fails with "App not installed!"
What could possibly be the reason that it refuses to install when we are using the *NCG* kernel?
I removed the NCG kernel and put the NK2 Kernel back in, and rebooted for the time being. It's working well, I just cannot get TowelrootV3 installed so that I can install SuperSU.
I've rooted another S5, using the very same procedure, and had absolutely no problems.
What am I doing wrong on this phone? It's driving me crazy, and I don' t have too far to go...:silly:
Thanks in Advance!
Please Help.
Stone.

stonecoldxlh said:
I'm having problems getting Towelroot v3 installed on my Verizon Wireless, Samsung Galaxy S5 16mb phone.
We were running fine while being rooted under V4.4.4 and Rom *NHA*.
We removed SuperSU, and uninstalled. it.
We installed the update, with no problems.
We rebooted, into Download mode, and flashed Kernel *NCG* .
We copied Towelrootv3 over and attempted to install it... (This is where the problem begins...)
We attempt to install TowelrootV3.apk. We get the popup that gives us the warning, along with the checkbox, we select the checkbox, which allows us to go ahead with the installation... the install begins but then suddenly says, "App not installed". (??????)
I have ensured that we are booted up under the NCG Kernel, and that we have selected:
Settings ->Security->Unknown Sources [ck'd]
Settings->Security->Verify Apps [Ck'd']
Developer Options->USB Debugging [not Ckk'd]
Developer Options->Allow Mock Locations [Chk'd]
No matter how many times that we try to install it, with different settings etc.... it fails with "App not installed!"
What could possibly be the reason that it refuses to install when we are using the *NCG* kernel?
I removed the NCG kernel and put the NK2 Kernel back in, and rebooted for the time being. It's working well, I just cannot get TowelrootV3 installed so that I can install SuperSU.
I've rooted another S5, using the very same procedure, and had absolutely no problems.
What am I doing wrong on this phone? It's driving me crazy, and I don' t have too far to go...:silly:
Thanks in Advance!
Please Help.
Stone.
Click to expand...
Click to collapse
Check enable USB debugging and see if it works.

Problem fixed... working now, successfully Rooted
Well,
I found that if you do not copy the towelroot.apk to your internal memory, it will not allow you to install towelroot.
Instead of Downloading towelroot.apk from the website from the phone itself, I downloaded it onto my PC. Then connected my phone to my pc, and placed it into "Access Picture" mode so that you can upload and download pictures into the phone's internal memory. I used that mode to copy towelroot from my pc to the phone.
I used Odin3 to load up NGC Kernel.
Then I disconnected from my pc, rebooted the phone, and was able to install towelroot with no further warnings.
Once that was done, I was able to use Odin3 again to load back up the NK2 original Kernel. I then rebooted again,
and then I could "Make it Rain". After a nice summer rainstorm, I was able to install SuperSU from Google Playstore and install it.
I sure hope that when 5.0 comes to our Verizon Android S5 phones, it's equally as easy to get root access as it has been for 4.4.4. I would surely be hindered without it as my phone relies upon a lot of apps that require root access. Unless Verizon changes their ways, this will be the last Samsung Galaxy I will ever purchase, so that I can move over to a Nexus device.
Thanks to everyone who has stepped up and helped us keep our phones productive and rooted.
Cheers,
-Stone
:good:

Apk Parse Error

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.

[HELP] There was a problem parsing the package

Hello there,
I am on 7.1.1 rooted with bootloader unlocked.
Everytime I try to install an apk file I get this message "There was a problem parsing the package"
Unknown sources is on!

I found on 6.xx when I turned on unknown sources I had to do a full reboot first and quickly open solid explorer to get the install done. Have you tried that yet?

Can you post a link of one apk failing?

rchtk said:
Can you post a link of one apk failing?
Click to expand...
Click to collapse
Sorry I can't.
I've not seen that exact error or actually any error toast installing an apk from my sd. In the installer the install button would not depress for me unless I did that re-boot and acted quickly. Not used 7.1 yet but hopefully I'll be able to use fdroid on it. I can on 7.0 after the initial install of PureNexus since "unknown sources" checked comes with the rom I've been able to install what I want. I turn if off after that and some updated apks are tricky to get done.

Database Users

welcome