Database Users

process com.android.vending has stopped unexpectedly

Im getting this error and force close on one of my Heros when I try installing any of my apps on any of the 2.1 roms. Im coming from Fresh 1.1 and following the same procedure I used on my other Hero on which the market is fully functional. Ive wiped everything over and over and cleared data on anything that looked like it at to do with the market. I also tried fix apk mismatches from recovery. Short of RUU which Id like to avoid if at all possible Ive tried everything else I can think of. In searching I have come across this error code on other android phones, but nothing on the hero and nothing specific to trying to install apps. So has anyone else seen this? And would RUU do anything a full data wipe didnt already?

Reading instructions has its benefits grasshopper...
Download the latest recovery and throw it onto your SD Card, boot into the old version of recovery and flash the new recovery as a .zip update, reboot into recovery again and then wipe your phone again, then install android 2.1, don't reboot yet, make sure your rom either has it's own custom kernal or download one for 2.1 and flash it, open up adb and clear dalvik cache and boot cache, then reboot your phone and you should load without any problems.

Thanks. But I did that from the get go. Aside from flashing a kernal, but Im running Darchtrev2 on the fully functional Hero that I mentioned and thats got a custum kernal built into the rom. So thats what I started with on the second one using the exact same process without success. Does wiping from adb do more than wiping from recovery? Thats one other thing I didnt do after the initial install.... But do understand you correctly that you have seen this specific error before?

Just bumpin the tread in hopes of finding a solution. I dont even mind gettin flamed for asking a stupid question if I could get linked up with a fix! lol I see its getting views, just no ideas I guess... It sucks cuz everything else works fine except the market. I get the list of my downloads, when I tap on one to install I the download button instead of the install button, so Ill tap on it and I get get the progress bar saying its downloading. When it gets to 100% I get the error and force close... Anyone?

I would try wiping again then flashing fresh 1.1 see if that boots and everything works ok then I would redownload the recovery and flash that still running fresh then reboot make sure everyhting is cool, then redownload whatever 2.1 rom you want and wipe and flash.
doing this serves 2 purposes
1. make sure that somewhere along the line none of the files corupted
2. if you still have the same problem then it will let you know where the problem is coming from.
just process of elimination
if you still have problems after that then I would say RUU, yes it is different than just wiping from recovery as it restores a completely stock image and gets rid of everything else. all a data wipe really does is get rid of user data.
just my opinion.
honestley thinnking about it I RUU'd my phone just for giggles then I re-rooted and then flashed DCv1 right from stock and I found that a lot of the little bugs that people where seeing I wasnt so it may not be a bad idea to ruu anyways.

Thanks for the reply and for giving me something different to try. I hadnt thought about trying that. Frustration I guess! It makes sense though. Ill give it shot. Thanks!

Why not see why it fc'd?
Adb with logcat of ...vending....
Find the syntax here: http://developer.android.com/search.html
Just an idea. It may or maynot give you the insight to fix the cause ( like a parameter ...vending... is null fetching on ).

Yeah, Ive been thinking about RUU'n too just to see if making a fresh start would make any difference, but after all the time I spent getting the one Hero working like I want on 2.1 and the troubles Ive had with the second and what Ive read about people bricking trying to RUU or flash recovery Ive been kinda hesitant....

willy900wonka said:
Why not see why it fc'd?
Adb with logcat of ...vending....
Find the syntax here: http://developer.android.com/search.html
Just an idea. It may or maynot give you the insight to fix the cause ( like a parameter ...vending... is null fetching on ).
Click to expand...
Click to collapse
Thanks. I dont know that Im quite that knowledgable though. Im sure I could read a logcat... understanding what the hell I would be reading is something else again. Saving the url though in case I need to dig deeper. Thanks for the reply.

wtphoto said:
honestley thinnking about it I RUU'd my phone just for giggles then I re-rooted and then flashed DCv1 right from stock and I found that a lot of the little bugs that people where seeing I wasnt so it may not be a bad idea to ruu anyways.
Click to expand...
Click to collapse
Sometimes it's just fun to RUU and do everything again

Alright if you're still having problems then just follow these steps:
Boot into recovery and make a nandroid back up just in case something goes wrong.
Download the latest version of your current 2.1 rom and reflash it from Recovery.
Open up adb and mount the /data directory (adb shell, mount /data)
Enter the following two commands in adb: rm -r /data/boot-cache , rm -r /data/dalvik-cache
Go Back to ADB and type the following commands: cd /data/data/com.android.vending , rm -R cache
Fix UID Mismatches using the tool in Recovery and then reboot your phone

regaw_leinad said:
Sometimes it's just fun to RUU and do everything again
Click to expand...
Click to collapse
or NOT!

Thanks again for your help all. I ended up just RUU'in . I'm with fixxer... fun isn't how I'd describe it! Anyway, I got it all working just to find out its got the mms issue now... if its not one thing its another. Oh well, something for me to work on tomorrow! Thanks again for the replies and advice.

HERNANDEZ4LIFE said:
Thanks again for your help all. I ended up just RUU'in . I'm with fixxer... fun isn't how I'd describe it! Anyway, I got it all working just to find out its got the mms issue now... if its not one thing its another. Oh well, something for me to work on tomorrow! Thanks again for the replies and advice.
Click to expand...
Click to collapse
You should have updated to the latest ruu...

wcgbmd said:
You should have updated to the latest ruu...
Click to expand...
Click to collapse
The latest RUU? I used the 1.56..... I did get it working tho. Flashed the mms. fix zip. Just wasn't expecting to have to as I didn't with my other hero. Don't know what the difference is between the two devices. Both are google branded, but the second one fought me every step of the way.

HERNANDEZ4LIFE said:
Thanks again for your help all. I ended up just RUU'in . I'm with fixxer... fun isn't how I'd describe it! Anyway, I got it all working just to find out its got the mms issue now... if its not one thing its another. Oh well, something for me to work on tomorrow! Thanks again for the replies and advice.
Click to expand...
Click to collapse
First, sorry for the bump.
I just started getting this error and wanted to know if you figured out exactly what it was so I didn't have to go through that whole RUUing process. Thanks.

don't know if this is your problem, but i know on sushi rom you have to go to manage applications, market, click on it and then click on uninstall updates.. Then apps. will download and install correctly.

boredmug said:
don't know if this is your problem, but i know on sushi rom you have to go to manage applications, market, click on it and then click on uninstall updates.. Then apps. will download and install correctly.
Click to expand...
Click to collapse
You're the bomb. That worked like a charm.

boredmug said:
don't know if this is your problem, but i know on sushi rom you have to go to manage applications, market, click on it and then click on uninstall updates.. Then apps. will download and install correctly.
Click to expand...
Click to collapse
Cant believe nobody wrote this first

boredmug said:
don't know if this is your problem, but i know on sushi rom you have to go to manage applications, market, click on it and then click on uninstall updates.. Then apps. will download and install correctly.
Click to expand...
Click to collapse
I was having the same problem on DC a couple days ago and that fixed it for me. I was reading this thread wondering why no one had mentioned it yet.

[Q] help with teamblackhat app

ok, i tried to get help in the teamblackhat thread but rec'd no answers.
i have the app and have dl'd 2.3.13 and 2.3.15. i've tried to install both and they both go through successfully (so they say)... i reboot and the system still says its 2.3.9.... i'm mounting the system, the only thing i'm not doing is wiping it... is it necessary to do that? will i lose root? please help, i'd like to have the most up to date froyo. also, just fyi, i dl'd the r2d2 and it went through ok, rebooted and it was installed for sure because it had the new boot animation and all the little quirks it says. BUT the system still said 2.3.9.

brandon2x said:
ok, i tried to get help in the teamblackhat thread but rec'd no answers.
i have the app and have dl'd 2.3.13 and 2.3.15. i've tried to install both and they both go through successfully (so they say)... i reboot and the system still says its 2.3.9.... i'm mounting the system, the only thing i'm not doing is wiping it... is it necessary to do that? will i lose root? please help, i'd like to have the most up to date froyo. also, just fyi, i dl'd the r2d2 and it went through ok, rebooted and it was installed for sure because it had the new boot animation and all the little quirks it says. BUT the system still said 2.3.9.
Click to expand...
Click to collapse
Have you changed the build prop, if you have a new build prop in there then it will keep that build.prop. If you want to have it say 2.3.13 or 2.3.15 you need to format system after you mount the system. My apologies for you not getting assistance in the TBH thread. Hope this helps you.

that does help... just one more thing about the format, will i lose root?

brandon2x said:
that does help... just one more thing about the format, will i lose root?
Click to expand...
Click to collapse
More than likely you will have to re-root your device. But one benefit of not changing the build prop is that you can see the entire market. Beasley has some great build.props for the X. You can download them from rom manager or lexusbrian has a post here that has additional build.props that do quite a bit more than fix just the market. Rest assured though if you installed 2.3.13 or 2.3.15 that is what you have on your device.

great, thanks a lot!!! i don't care if it says it, as long as i really have it...

brandon2x said:
great, thanks a lot!!! i don't care if it says it, as long as i really have it...
Click to expand...
Click to collapse
Glad I could help and once again my apologies for you not receiving help on MDW

Fix the superuser for the Taboonay rom(Also I also fail, with suddenly lost root))

Sorry to start this thread, I find I also lost root suddenly. No clear reason, thought I power down and start many times and didn't lose. Now I have no root.
So adminstrator please close this thread

gave me an error
Tried it again, flashed rom followed by this zip, no go.
Says there was an error in /sdcard/su_mod.zip followed by an installation aborted message....

jamesnmandy said:
gave me an error
Tried it again, flashed rom followed by this zip, no go.
Says there was an error in /sdcard/su_mod.zip followed by an installation aborted message....
Click to expand...
Click to collapse
You wipe or not?

liu2002 said:
You wipe or not?
Click to expand...
Click to collapse
I didnt wipe anything. I can try wiping cache and Dalvik cache but i would rather wait until a fix comes that doesn't require a data wipe as i have things all set up the way i like.

jamesnmandy said:
I didnt wipe anything. I can try wiping cache and Dalvik cache but i would rather wait until a fix comes that doesn't require a data wipe as i have things all set up the way i like.
Click to expand...
Click to collapse
OK, I think the HoneyVillain's files are right. The best way is to replce the both su and superuser.apk directly in the taboonay rom not use the fix package.

liu2002 said:
OK, I think the HoneyVillain's files are right. The best way is to replce the both su and superuser.apk directly in the taboonay rom not use the fix package.
Click to expand...
Click to collapse
Sorry but i ran into the same problem, had root and suddenly no root annymore ive flashed as usual factory reset, format system and after this installed 2.1 so i think someone has to do his homework once again.

henk_j said:
Sorry but i ran into the same problem, had root and suddenly no root annymore ive flashed as usual factory reset, format system and after this installed 2.1 so i think someone has to do his homework once again.
Click to expand...
Click to collapse
The reson is setcpu as they said. Maybe it is.

Fix the superuser for the Taboonay rom
It would appear that the problems can be caused by the installaton of SetCPU

CWM Error

Whenever I try to make a backup with CMW, it gives me an error that says "An error occurred while attempting to run privileged commands"
How do I fix it?

You have S-Off?

estallings15 said:
You have S-Off?
Click to expand...
Click to collapse
Yep fully rooted and everything. It worked before but not sure why it's not working now.

HTC~TwikiE said:
Yep fully rooted and everything. It worked before but not sure why it's not working now.
Click to expand...
Click to collapse
Try reflashing your recovery. Sounds like it's borked.

estallings15 said:
Try reflashing your recovery. Sounds like it's borked.
Click to expand...
Click to collapse
I just tried that and it gives me "An error occurred while downloading your recovery."
How do I do it manually?

HTC~TwikiE said:
I just tried that and it gives me "An error occurred while downloading your recovery."
How do I do it manually?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1242901

estallings15 said:
http://forum.xda-developers.com/showthread.php?t=1242901
Click to expand...
Click to collapse
Just tried that, back to square one. Same error

HTC~TwikiE said:
Just tried that, back to square one. Same error
Click to expand...
Click to collapse
Hmm, I'm getting worried that this may be a hardware problem. Does anybody have any ideas?

estallings15 said:
Hmm, I'm getting worried that this may be a hardware problem. Does anybody have any ideas?
Click to expand...
Click to collapse
The error isn't necessarily hardware; that message could be occurring because of a software problem with the su application that is being used.
- Have you been flashing/nandroiding successfully with CWM in the past?
- Were your su binaries updated recently?
- Did the ROM get an OTA recently that might have updated the su binaries?
- Was this failed backup being done after/before flashing a ROM that wasn't full-wiped?
- EDIT: Why of course you have S-off and anyone who asked after you said so would be a silly fellow.
If all else were to fail, I'd suggest going back to a stock ROM and re-rerooting, and I imagine that your problems would 'go away'. I'm not sure what intermediate methods you could try, though, unless you wanted to try to run your backup commands over adb or re-push your su binaries or .apk.

tuxkamen said:
The error isn't necessarily hardware; that message could be occurring because of a software problem with the su application that is being used.
- Have you been flashing/nandroiding successfully with CWM in the past?
- Were your su binaries updated recently?
- Did the ROM get an OTA recently that might have updated the su binaries?
- Was this failed backup being done after/before flashing a ROM that wasn't full-wiped?
- Do you have S-off?
If all else were to fail, I'd suggest going back to a stock ROM and re-rerooting, and I imagine that your problems would 'go away'. I'm not sure what intermediate methods you could try, though, unless you wanted to try to run your backup commands over adb or re-push your su binaries or .apk.
Click to expand...
Click to collapse
I was under the impression that your recovery didn't need the SU binary to do it's job. The SU binary is used within Android, right?
Edit: Also, he already said that he has S-Off. If you're going to offer help, please pay attention.

I had the same error show up recently. I just went around it and did a backup while in boot recovery.
... now... what to do if that starts to fail... Hmm
Sent from my myTouch 4g using xda app

estallings15 said:
I was under the impression that your recovery didn't need the SU binary to do it's job. The SU binary is used within Android, right?
Click to expand...
Click to collapse
I'm referring to both the Superuser.apk and the general su/busybox binaries (that got installed as part of his rooting process) which I think get used when doing the calls to make backups to your SD card. He's most likely getting the message because either his rooting method has gone awry or whatever his phone thinks is the appropriate way to get elevated privileges is no longer able to do that. The possible causes for that pretty much boil down to either permissions needing fixing or needing to redo the installation of the su "stuff".
I'm not sure how that would _happen_. This goes back to knowing what happened recently to the phone from a software perspective (any new ROM flash lately, potentially to something that doesn't have root perms?). He was able to reinstall CWM, but he may need to re-push the su/busybox stuff in order to get back to full functionality (and maybe do it a few times, just like in the initial rooting process, to make sure it 'sticks').
Edit: Also, he already said that he has S-Off. If you're going to offer help, please pay attention.
Click to expand...
Click to collapse
I'm not sure why I wrote that. I did notice he said it, said 'meh' and wrote it down anyway. -_-

tuxkamen said:
I'm referring to both the Superuser.apk and the general su/busybox binaries (that got installed as part of his rooting process) which I think get used when doing the calls to make backups to your SD card. He's most likely getting the message because either his rooting method has gone awry or whatever his phone thinks is the appropriate way to get elevated privileges is no longer able to do that. The possible causes for that pretty much boil down to either permissions needing fixing or needing to redo the installation of the su "stuff".
I'm not sure how that would _happen_. This goes back to knowing what happened recently to the phone from a software perspective (any new ROM flash lately, potentially to something that doesn't have root perms?). He was able to reinstall CWM, but he may need to re-push the su/busybox stuff in order to get back to full functionality (and maybe do it a few times, just like in the initial rooting process, to make sure it 'sticks').
I'm not sure why I wrote that. I did notice he said it, said 'meh' and wrote it down anyway. -_-
Click to expand...
Click to collapse
No offense, but I'm fairly positive you can perform all the functions in recovery with a completely wiped system partition. If that is the case, then that theory is debunked. S-Off should give you all access/permissions you need. This is why I said that I'm worried about his hardware. If his bootloader was HTC dev unlocked, then I would say he needed S-Off.

estallings15 said:
No offense, but I'm fairly positive you can perform all the functions in recovery with a completely wiped system partition. If that is the case, then that theory is debunked. S-Off should give you all access/permissions you need. This is why I said that I'm worried about his hardware. If his bootloader was HTC dev unlocked, then I would say he needed S-Off.
Click to expand...
Click to collapse
The error message he's getting is from trying to start his backup out of ROM Manager, not recovery--that error usually pops up before going into the backup process. You can verify this yourself by temp unrooting in Superuser, launching ROM Manager, and trying to do something like make a backup or fix permissions. I have a feeling TwikiE could do backups by _booting_ into recovery.
That's why I'm suggesting the need to check the Superuser implementation. ROM Manager doesn't think it has either root permission or privileges. If TwikiE isn't seeing the 'you must be rooted' popup when starting ROM Manager, then the phone is rooted but the app doesn't think it's privileged to send the phone into the backup process. If this the first time TwikiE's tried a backup since his last ROM flash, the ROM might have a bad or incompatible set of root tools, or some other app may have been installed that has bad tools. Or maybe it's as simple as having accidentally hit Deny on a Superuser prompt.
Some things TwikiE could do to try and resolve the problem without rerooting could be:
- Try Fix Permissions out of ROM Manager and see if the same error message appears. If it succeeds, try backing up again. If not...
- Check the Superuser app settings to see if ROM Manager is on the list as allowed or denied. If it's on deny, clear it out. If it's allowed or not there, move on.
- Clear out the application data and cache for both the Superuser app and ROM Manager from the apps menu. Try to backup again and see if the superuser prompt appears.
- If that doesn't work, try uninstalling and reinstalling Superuser and ROM Manager from the Play Store, reinstalling both, then try to backup.
Beyond that comes more drastic steps.

tuxkamen said:
The error message he's getting is from trying to start his backup out of ROM Manager, not recovery--that error usually pops up before going into the backup process. You can verify this yourself by temp unrooting in Superuser, launching ROM Manager, and trying to do something like make a backup or fix permissions. I have a feeling TwikiE could do backups by _booting_ into recovery.
That's why I'm suggesting the need to check the Superuser implementation. ROM Manager doesn't think it has either root permission or privileges. If TwikiE isn't seeing the 'you must be rooted' popup when starting ROM Manager, then the phone is rooted but the app doesn't think it's privileged to send the phone into the backup process. If this the first time TwikiE's tried a backup since his last ROM flash, the ROM might have a bad or incompatible set of root tools, or some other app may have been installed that has bad tools. Or maybe it's as simple as having accidentally hit Deny on a Superuser prompt.
Some things TwikiE could do to try and resolve the problem without rerooting could be:
- Try Fix Permissions out of ROM Manager and see if the same error message appears. If it succeeds, try backing up again. If not...
- Check the Superuser app settings to see if ROM Manager is on the list as allowed or denied. If it's on deny, clear it out. If it's allowed or not there, move on.
- Clear out the application data and cache for both the Superuser app and ROM Manager from the apps menu. Try to backup again and see if the superuser prompt appears.
- If that doesn't work, try uninstalling and reinstalling Superuser and ROM Manager from the Play Store, reinstalling both, then try to backup.
Beyond that comes more drastic steps.
Click to expand...
Click to collapse
Who does anything in ROM Manager? Damn it, OP, reboot into recovery and do it right.

Heh. I didn't want to put it *exactly* that way...
Sent from my HTC myTouch 4g using xda app-developers app

[Q] How do I regain root from accidental update?

My phone kept nagging me to update and I kept exiting out. Apparently somehow I hit install and it updated. I'm on 4.4.4 according to the phone, I don't remember what I was on before I might have been on 4.4.2. I used these files to downgrade from Lollipop previously:
G900VVRU1ANK2_G900VVZW1ANK2_G900VVRU1ANK2_HOME.tar and G900V_NCG_Stock_Kernel.tar
How do I regain root?

Downgrade your Device & root it via previous method,Which you use before.

Bakuryu42 said:
My phone kept nagging me to update and I kept exiting out. Apparently somehow I hit install and it updated. I'm on 4.4.4 according to the phone, I don't remember what I was on before I might have been on 4.4.2. I used these files to downgrade from Lollipop previously:
G900VVRU1ANK2_G900VVZW1ANK2_G900VVRU1ANK2_HOME.tar and G900V_NCG_Stock_Kernel.tar
How do I regain root?
Click to expand...
Click to collapse
Odin the NGC file down in the notes #4 then root with towelroot. Download SuperSU from play store. Update binaries and reboot phone. If you want safestrap as a recovery you must first download busybox from the play store and install it. Then safestrap will install properly.
http://forum.xda-developers.com/ver...w-to-update-to-g900voc4-5-0-keeproot-t3068546
Next time install titanium backup pro and freeze SDM to stop the updates.

[email protected] # said:
Downgrade your Device & root it via previous method,Which you use before.
Click to expand...
Click to collapse
Sounds easy enough.
Tulsadiver said:
Odin the NGC file down in the notes #4 then root with towelroot. Download SuperSU from play store. Update binaries and reboot phone. If you want safestrap as a recovery you must first download busybox from the play store and install it. Then safestrap will install properly.
http://forum.xda-developers.com/ver...w-to-update-to-g900voc4-5-0-keeproot-t3068546
Next time install titanium backup pro and freeze SDM to stop the updates.
Click to expand...
Click to collapse
The note #4 states
4. If you do not already have root access you must first flash the G900VVRU1ANCG_Full_Odin.tar (flash in Odin's PDA slot(AP in Odin v3.09+)), root with Towelroot (this version does not require internet access), then proceed with the above process.
Click to expand...
Click to collapse
When I clicked the G900VVRU1ANCG_Full_Odin.tar it says it is for Galaxy S4? Is that right? Also how does this way differ from the way I originally did it which was seen here

Bakuryu42 said:
Sounds easy enough.
The note #4 states
When I clicked the G900VVRU1ANCG_Full_Odin.tar it says it is for Galaxy S4? Is that right? Also how does this way differ from the way I originally did it which was seen here
Click to expand...
Click to collapse
Yes, this is actually for the S5.
The difference is all the FCs you have to wade through. Also, the one I suggested is a clean and complete reinstall. It will wipe your SD card and you start fresh. Both will work provided you are not on lollipop. If you are on lollipop you should use the method I suggested.

Tulsadiver said:
Yes, this is actually for the S5.
The difference is all the FCs you have to wade through. Also, the one I suggested is a clean and complete reinstall. It will wipe your SD card and you start fresh. Both will work provided you are not on lollipop. If you are on lollipop you should use the method I suggested.
Click to expand...
Click to collapse
Sorry FC's? I am unfamiliar with the abbreviation. Also was confused when you said SDM, what does that stand for so I know what to freeze when I do it? Much appreciated.
Edit: Also is there a particular reason you recommended a full wipe of everything? I only ask because I hate doing wipes and I never did find a good way to back stuff up really.

Bakuryu42 said:
Sorry FC's? I am unfamiliar with the abbreviation. Also was confused when you said SDM, what does that stand for so I know what to freeze when I do it? Much appreciated.
Edit: Also is there a particular reason you recommended a full wipe of everything? I only ask because I hate doing wipes and I never did find a good way to back stuff up really.
Click to expand...
Click to collapse
FC = force close (aka crash)
SDM - Samsung Data Migration (freeze update software)
Not to answer for tulsadiver... but in my opinion wiping ensures you get rid of any stray "orphan" files that may be even a little borked. Has happened to me before so wiping is often a good way to go.

skeeterpro said:
FC = force close (aka crash)
SDM - Samsung Data Migration (freeze update software)
Not to answer for tulsadiver... but in my opinion wiping ensures you get rid of any stray "orphan" files that may be even a little borked. Has happened to me before so wiping is often a good way to go.
Click to expand...
Click to collapse
Alright one last thing, whats the best way to back stuff up so I can hit the ground running if I decide to do a wipe?

Bakuryu42 said:
Alright one last thing, whats the best way to back stuff up so I can hit the ground running if I decide to do a wipe?
Click to expand...
Click to collapse
You could use titanium backup.

Ok so I went ahead and tried to repeat the steps I did the last time I rooted and so far its not going to well. I've done up to #6 in the instructions here, but when I try to install Busy Box it says I am not rooted properly. Towel root said I was rooted sucessfully though? What should I do?

Bakuryu42 said:
Ok so I went ahead and tried to repeat the steps I did the last time I rooted and so far its not going to well. I've done up to #6 in the instructions here, but when I try to install Busy Box it says I am not rooted properly. Towel root said I was rooted sucessfully though? What should I do?
Click to expand...
Click to collapse
Did you install and setup supersu?

mrjiggywiggy said:
Did you install and setup supersu?
Click to expand...
Click to collapse
The instructions say not to till I install safe strap. Then again because I was previously rooted its actually already installed on there... is that a problem?
Btw a root checker app is also claiming I am not rooted.

Bakuryu42 said:
The instructions say not to till I install safe strap. Then again because I was previously rooted its actually already installed on there... is that a problem?
Btw a root checker app is also claiming I am not rooted.
Click to expand...
Click to collapse
You need to install supersu otherwise root won't work.

mrjiggywiggy said:
You need to install supersu otherwise root won't work.
Click to expand...
Click to collapse
Well I followed those instructions last time and didn't have an issue? Also it seems I can't simply uninstall the superSU I have installed already. I installed it through safestrap like the instructions told me.

Bakuryu42 said:
Well I followed those instructions last time and didn't have an issue? Also it seems I can't simply uninstall the superSU I have installed already. I installed it through safestrap like the instructions told me.
Click to expand...
Click to collapse
Open supersu and install what it tells you, then it should work.

superSu wont open it just gives me a black screen

Bakuryu42 said:
superSu wont open it just gives me a black screen
Click to expand...
Click to collapse
See if it will go ahead and install again from the play store.

Tulsadiver said:
See if it will go ahead and install again from the play store.
Click to expand...
Click to collapse
The playstore shows its installed already and uninstall only uninstalled an update. Tried running it after that and still didn't work, reinstalled it again and still nothing. I also have safestrap installed, which is also not working.

You better start over again. Go Odin the NGC retail tar again. You are too jacked up. After towelroot, install SuperSU from play store. Update binaries and reboot. Then download busybox from play store. Install it. Then install safestrap.

Tulsadiver said:
You better start over again. Go Odin the NGC retail tar again. You are too jacked up. After towelroot, install SuperSU from play store. Update binaries and reboot. Then download busybox from play store. Install it. Then install safestrap.
Click to expand...
Click to collapse
Is there a particular reason it has to format the sd card?