[Q] What is "There is no Su binary installed"... - Verizon Galaxy Note 3 Q&A, Help & Troubleshooting

I rooted my note 3 and I followed the steps of installing the OTA by checking survival mood and unchecking enable super su. I then updated and it said the phone installed it but when I went to turn super su back on, it said "There is no Su binary installed, and SuperSu cannot install it." My status in my phone still says Custom, what do I do now? Is SuperSu required for my phone to work fine?

Did you try to install Safestrap apk and then boot into safestrap - flash the supersu.zip ?

lmike6453 said:
Did you try to install Safestrap apk and then boot into safestrap - flash the supersu.zip ?
Click to expand...
Click to collapse
I'm a noob at this lol

iEnjoyDriods said:
I'm a noob at this lol
Click to expand...
Click to collapse
That's fine, you described your issue very well :good:
Safestrap is a recovery that you can install from your SD card like any app, can be found via the development section for our phone.
Also download the supersu.zip file and place it on your SD card
Reboot and select recovery to go into recovery and flash the .zip
That's a little vague but gets right to the point^ you'll probably get stuck along the way but don't worry, it's normal and you can research it on here

lmike6453 said:
That's fine, you described your issue very well :good:
Safestrap is a recovery that you can install from your SD card like any app, can be found via the development section for our phone.
Also download the supersu.zip file and place it on your SD card
Reboot and select recovery to go into recovery and flash the .zip
That's a little vague but gets right to the point^ you'll probably get stuck along the way but don't worry, it's normal and you can research it on here
Click to expand...
Click to collapse
Unless I'm missing something, if he doesn't have the SU binaries installed, he will not be able to install Safestrap, which, in turn, will not allow him to boot to recovery and install the SU binaries. He lost root and will need to re-root with Kingo, wait for another method or live without root. I believe that designgears is looking into updating root de la vega to work with the MJ7 update.

:cyclops:
G8orDroid said:
Unless I'm missing something, if he doesn't have the SU binaries installed, he will not be able to install Safestrap, which, in turn, will not allow him to boot to recovery and install the SU binaries. He lost root and will need to re-root with Kingo, wait for another method or live without root. I believe that designgears is looking into updating root de la vega to work with the MJ7 update.
Click to expand...
Click to collapse
Yeah I just noticed I changed from M19 to MJ7. So now, should I just ignore this and wait til a fix released. When my phone boots, it's says custom and everything. With SuperSu missing the binaries, is it going to effect my phone negatively? Should I just unroofed it?

iEnjoyDriods said:
:cyclops:
Yeah I just noticed I changed from M19 to MJ7. So now, should I just ignore this and wait til a fix released. When my phone boots, it's says custom and everything. With SuperSu missing the binaries, is it going to effect my phone negatively? Should I just unroofed it?
Click to expand...
Click to collapse
It shouldn't affect your phone at all and you can't really unroot it since it's not technically "rooted" right now. Not sure why it's showing a custom status though. I would have thought the OTA would have overwritten anything that would make it custom. Some residual files must still be there.
Edit: if you really want the "custom" status to go away until if/when you re-root, you should be able to flash the full MJ7 Odin file and clean it up.
Sent from my SM-N900V using Tapatalk

G8orDroid said:
Unless I'm missing something, if he doesn't have the SU binaries installed, he will not be able to install Safestrap, which, in turn, will not allow him to boot to recovery and install the SU binaries. He lost root and will need to re-root with Kingo, wait for another method or live without root. I believe that designgears is looking into updating root de la vega to work with the MJ7 update.
Click to expand...
Click to collapse
Yeah I was thinking that root might be working for him regardless of the error msg, something quick to try as a root test(installing safestrap)
G8orDroid said:
It shouldn't affect your phone at all and you can't really unroot it since it's not technically "rooted" right now. Not sure why it's showing a custom status though. I would have thought the OTA would have overwritten anything that would make it custom. Some residual files must still be there.
Edit: if you really want the "custom" status to go away until if/when you re-root, you should be able to flash the full MJ7 Odin file and clean it up.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
+1 can always odin it

Related

Little bit confused

I've been looking at the threads but so far I don't believe there's one that tells you what to do if you've actually installed the official OTA update?
I.e. I have an rooted 2.3.4 GT-I9023 with an unlocked bootloader. With no clockwork or anything, as to be honest the last time I used it (on my old HTC DHD) it made my phone unstable (the phone would sometimes boot up of its own accord and stop at the clockwork screen).
Does anyone know how to re-root the NS after it's installed the official OTA update without clockwork?
Thanks
Edit: Downloading the OTA update won't relock the boot-loader will it?
dccxviii said:
I've been looking at the threads but so far I don't believe there's one that tells you what to do if you've actually installed the official OTA update?
I.e. I have an rooted 2.3.4 GT-I9023 with an unlocked bootloader. With no clockwork or anything, as to be honest the last time I used it (on my old HTC DHD) it made my phone unstable (the phone would sometimes boot up of its own accord and stop at the clockwork screen).
Does anyone know how to re-root the NS after it's installed the official OTA update without clockwork?
Thanks
Edit: Downloading the OTA update won't relock the boot-loader will it?
Click to expand...
Click to collapse
You cannot get root back without a custom recovery. OTA will not relock the bootloader, you'll just lose root and custom recovery.
You need to flash custom recovery using fastboot, then flash superuser to get root back. There are plenty of guides in the stickies describing the process.
Ok, so i'm updated to 2.3.6 but of course have lost root (never had CWM to begin with on this phone). Anyone know where I can DL CWM (i'm assuming it needs to be flashed via platform-tools directory in the android sdk per normal) and the latest su file?
EDIT: nvm, I found the latest CWM and successful flashed (my method was correct). However I've not been able to find the latest superuser.zip to flash yet. Also, I don't know why ppl say to use the market as I don't see how that method can work. I've already got superuser installed from before I updated but that doesn't help me get root. Only flashing the zip from recovery (as I understand it) would. Which renders the market useless in this regard.
/confused
The superuser app checks to see if you have the latest superuser binary and will download and instalk it. Or download superuser from within rom manager.
Sent from my Nexus S 4G using xda premium
Ok..the binary update fails (because i don't have root) so it's chicken and egg as far as I can tell.
You where already told. Flash custom recovery via fastboot. Boot into it and flash su.zip Same way it was done prior to update to the ota. Same as it always was and will be.
dccxviii said:
Ok, so i'm updated to 2.3.6 but of course have lost root (never had CWM to begin with on this phone). Anyone know where I can DL CWM (i'm assuming it needs to be flashed via platform-tools directory in the android sdk per normal) and the latest su file?
EDIT: nvm, I found the latest CWM and successful flashed (my method was correct). However I've not been able to find the latest superuser.zip to flash yet. Also, I don't know why ppl say to use the market as I don't see how that method can work. I've already got superuser installed from before I updated but that doesn't help me get root. Only flashing the zip from recovery (as I understand it) would. Which renders the market useless in this regard.
/confused
Click to expand...
Click to collapse
You can find superuser zip here:
http://rootzwiki.com/showthread.php?231-Superuser-2.3.6.3-17-June-2011&
3rd one down, efgh.
Flash in custom recovery.
albundy2010 said:
You where already told. Flash custom recovery via fastboot. Boot into it and flash su.zip Same way it was done prior to update to the ota. Same as it always was and will be.
Click to expand...
Click to collapse
You've misunderstood what i'm after. Thanks for trying to help tho
irishrally said:
You can find superuser zip here:
http://rootzwiki.com/showthread.php?231-Superuser-2.3.6.3-17-June-2011&
3rd one down, efgh.
Flash in custom recovery.
Click to expand...
Click to collapse
Thanks! As far as I can tell you're the first with the link I was after the entire time.
EDIT: Bah, I get a signature verification error when applying the update >.<
dccxviii said:
You've misunderstood what i'm after. Thanks for trying to help tho
Thanks! As far as I can tell you're the first with the link I was after the entire time.
EDIT: Bah, I get a signature verification error when applying the update >.<
Click to expand...
Click to collapse
Turn off signature verification in CWM and try again.
irishrally said:
Turn off signature verification in CWM and try again.
Click to expand...
Click to collapse
Turns out that CWM got overwritten by stock android recovery. Re-flashing CWM and then flashing su did the trick. I'm rooted once more!
Thanks for your help kind sir!
Curious as to how to make CWM stick for next time tho *shrug*
dccxviii said:
Turns out that CWM got overwritten by stock android recovery. Re-flashing CWM and then flashing su did the trick. I'm rooted once more!
Thanks for your help kind sir!
Curious as to how to make CWM stick for next time tho *shrug*
Click to expand...
Click to collapse
You're welcome.
If you stick with a stock ROM then recovery will reflash every time you reboot. To prevent this you can go to system>etc, and change the file install-recovery.init to something else like install-recovery.init.bak.

[Q] gs4 losses root.

Hello.
Im looking to get some help with an issue i have on my gs4 att, stock + root.
My device keeps loosing root access after a while.
I have unrooted and flashed stock 4 times, but i cant figure out the problem and cant find any information on the fourms.
What version stock?
TheAxman said:
What version stock?
Click to expand...
Click to collapse
stock 4.2.2 UCUAMDL
do do you think it ha anything to do with removing stock samsung apps like hub and att [email protected]?
gsr101 said:
Hello.
Im looking to get some help with an issue i have on my gs4 att, stock + root.
My device keeps loosing root access after a while.
I have unrooted and flashed stock 4 times, but i cant figure out the problem and cant find any information on the fourms.
Click to expand...
Click to collapse
Here I did it before and I never got a message says root access has been lost.
1. Odin it back
2. Root by using causal method
3. When phone reboot itself into recovery TWRP
4. Don't back up just reboot into welcome screen
5. It should ask you to install superuser, just install it
6. Finally, reboot into recovery and make nandroid back up.
On step four, I back up by using nandroid before superuser install. When I change rom, message always telling me I have lost root access quite often this way.
LeonKnight12 said:
Here I did it before and I never got a message says root access has been lost.
1. Odin it back
2. Root by using causal method
3. When phone reboot itself into recovery TWRP
4. Don't back up just reboot into welcome screen
5. It should ask you to install superuser, just install it
6. Finally, reboot into recovery and make nandroid back up.
On step four, I back up by using nandroid before superuser install. When I change rom, message always telling me I have lost root access quite often this way.
Click to expand...
Click to collapse
thats usually what i do, i tried 4 times. It doesnt ask me to install su, its already installed.
i might just have to update and wait for new root method.
Download a superuser/supersu zip file and flash it through your twrp/cwm recovery and reboot.when I first rooted my I337 ATT S4
It would loose just as I would enter recovery and my recovery would ask if I wanted to fix it before rebooting. After flashing the supersu zip file
I have had zero issues with root.
jball said:
Download a superuser/supersu zip file and flash it through your twrp/cwm recovery and reboot.when I first rooted my I337 ATT S4
It would loose just as I would enter recovery and my recovery would ask if I wanted to fix it before rebooting. After flashing the supersu zip file
I have had zero issues with root.
Click to expand...
Click to collapse
thanks for the share, do you happen to have link to the file or thread?
Sorry for the late reply I don't get notification for this site.I Google everything and most of the time it will bring u to xda for what u search .I don't post links cause I don't want trouble from nobody thinking I'm try n to take credit if u know what I mean.just helpful words

[Q] Do I have to unroot 4.3 to get the OTA?

I have a rooted (no CWM changed) and unlocked Nexus 4 with JB 4.3.
I did not get the OTA yet and I wondered if it is because the phone is rooted. In addition, I read some problems with people who tried to update to 4.4 with rooted phones and are getting infinite bootloops.
Do I have to unroot my 4.3 for getting the OTA and achieving a successful installation?
Thank you all on advance
gosku26 said:
I have a rooted (no CWM changed) and unlocked Nexus 4 with JB 4.3.
I did not get the OTA yet and I wondered if it is because the phone is rooted. In addition, I read some problems with people who tried to update to 4.4 with rooted phones and are getting infinite bootloops.
Do I have to unroot my 4.3 for getting the OTA and achieving a successful installation?
Thank you all on advance
Click to expand...
Click to collapse
Why do you need OTA update when you can get the stock ROM in flashable zip file? All features are remain the same for stock ROM. Search and download it in the Development sections.
gosku26 said:
I have a rooted (no CWM changed) and unlocked Nexus 4 with JB 4.3.
I did not get the OTA yet and I wondered if it is because the phone is rooted. In addition, I read some problems with people who tried to update to 4.4 with rooted phones and are getting infinite bootloops.
Do I have to unroot my 4.3 for getting the OTA and achieving a successful installation?
Thank you all on advance
Click to expand...
Click to collapse
I am rooted and received the OTA notification yesterday. You 'SHOULD' be able to install if ALL you did was root. However, if you applied any mods that made changes to the system, the OTA will fail.
taodan said:
Why do you need OTA update when you can get the stock ROM in flashable zip file? All features are remain the same for stock ROM. Search and download it in the Development sections.
Click to expand...
Click to collapse
This is your best bet if you want to run 4.4. You'll need to install a custom recovery to flash the zip files. All the files and instructions are here:
http://forum.xda-developers.com/showthread.php?t=2527806
gbarayah said:
I am rooted and received the OTA notification yesterday. You 'SHOULD' be able to install if ALL you did was root. However, if you applied any mods that made changes to the system, the OTA will fail.
This is your best bet if you want to run 4.4. You'll need to install a custom recovery to flash the zip files. All the files and instructions are here:
http://forum.xda-developers.com/showthread.php?t=2527806
Click to expand...
Click to collapse
Will flashing the stock 4.4 wipe my data, or it is like getting the OTA, that I keep my settings...?
gosku26 said:
Will flashing the stock 4.4 wipe my data, or it is like getting the OTA, that I keep my settings...?
Click to expand...
Click to collapse
Did you read the linked post?
First step after installing custom recovery is to wipe data/factory reset, so yes, you will lose your settings.
taodan said:
Why do you need OTA update when you can get the stock ROM in flashable zip file? All features are remain the same for stock ROM. Search and download it in the Development sections.
Click to expand...
Click to collapse
I would like to keep my settings if it's possible.
gbarayah said:
Did you read the linked post?
First step after installing custom recovery is to wipe data/factory reset, so yes, you will lose your settings.
Click to expand...
Click to collapse
What I would like is to update to kitkat without losing my data.
I have the bootloader unlocked and the phone rooted, but when I go to recovery mode I get "No command" screen (is that normal?).
I was thinking of getting the phone unrooted, then update through the OTA, then root it again, just for making sure I don't break anything, but the "No command" screen does not look very good...
On the other hand, Would I lose my data if I "unroot" the phone?
gosku26 said:
What I would like is to update to kitkat without losing my data.
I have the bootloader unlocked and the phone rooted, but when I go to recovery mode I get "No command" screen (is that normal?).
I was thinking of getting the phone unrooted, then update through the OTA, then root it again, just for making sure I don't break anything, but the "No command" screen does not look very good...
On the other hand, Would I lose my data if I "unroot" the phone?
Click to expand...
Click to collapse
To unroot, all you need to do is go into SuperSu, disable root, uninstall the app and then reboot the phone.
If all you have done is root the phone, and didn't modify anything else, then the OTA update 'SHOULD' install without a problem.
You can go to Android Police and download the OTA files and flash them via ADB, or you can just wait for the OTA to be pushed to your device.
If you decide to do it the manual way, there is one additional step you must take to ensure to keep your data I believe.
gbarayah said:
To unroot, all you need to do is go into SuperSu, disable root, uninstall the app and then reboot the phone.
If all you have done is root the phone, and didn't modify anything else, then the OTA update 'SHOULD' install without a problem.
You can go to Android Police and download the OTA files and flash them via ADB, or you can just wait for the OTA to be pushed to your device.
If you decide to do it the manual way, there is one additional step you must take to ensure to keep your data I believe.
Click to expand...
Click to collapse
Thank you for your help gbarayah, I really appreciate it.
One last thing: I'm not pretty sure the only thing I modified was the rooting. I did not install any zip to modify my stock version, but there is something weird. I will explain:
At first I had 4.2.2, then I rooted and installed CWM. When 4.3 was released I got the OTA update correctly but I lost the root, so I rooted it again, this time without CWM.
Is the "No command" screen what is supposed to appear when I go to the recovery mode from fastboot menu? Or I would get a default recovery mode program?
If everything is right I will unroot for getting the OTA, but if not, I'm afraid I will have to flash CWM and the stock version, loosing my settings...
EDIT: Ok, I've just realized to get into stock system recovery I have to press VolUp and Power buttons once I'm in the 'No Command' screen, so I'm pretty sure I don't have problems installing the OTA update. Thank You!!!
gosku26 said:
Thank you for your help gbarayah, I really appreciate it.
One last thing: I'm not pretty sure the only thing I modified was the rooting. I did not install any zip to modify my stock version, but there is something weird. I will explain:
At first I had 4.2.2, then I rooted and installed CWM. When 4.3 was released I got the OTA update correctly but I lost the root, so I rooted it again, this time without CWM.
Is the "No command" screen what is supposed to appear when I go to the recovery mode from fastboot menu? Or I would get a default recovery mode program?
If everything is right I will unroot for getting the OTA, but if not, I'm afraid I will have to flash CWM and the stock version, loosing my settings...
EDIT: Ok, I've just realized to get into stock system recovery I have to press VolUp and Power buttons once I'm in the 'No Command' screen, so I'm pretty sure I don't have problems installing the OTA update. Thank You!!!
Click to expand...
Click to collapse
Glad I could help. In the future, as long as you don't modify the system by flashing any modifications, you should be able to get the OTA update to install. Root doesn't affect this, and if you're worried about it, you can always uninstall it.
I opted to update using the stock zip files that were posted above and it worked just fine for me.

[Q] SuperSu Update Failed Note 3 Verizon 4.4.2

for some reason as of now on verizon note 3 there seems to be no fix for the supersu not updating binary on the new kitkat 4.4.2 im rooted using Towelroot i let it update the binary once and i never opened it again to avoid it asking me to update again then failing ... so to avoid uninstall and reinstall i just let it do its magic once and never touch it again... it will update the first run but once you reboot .. youre f you also want to make sure you delete the file su in system/xbin/su then uninstall and install fresh to get this to update you binary .. but you can never open it again or it will ask to update and fail ... however all apps asking to grant permisson will be granted so apon screen pop up and your prompt to allow ....
Is there any update or possible way to obtain update of binary successfully without having to worry about being asked to update again once you reopen SuperSu ..
if you have safe strap installed, you can download the Su zip file and flash in recovery. you can find it in the Android thread, just use the search. I have done it this way and works like a charm.
phillymade said:
if you have safe strap installed, you can download the Su zip file and flash in recovery. you can find it in the Android thread, just use the search. I have done it this way and works like a charm.
Click to expand...
Click to collapse
im currently running
Safestrap 3.72 SuperSu 2.02 does this matter ? i ask because i had already took the apk su file out of the zip you mention prior and installed via sd card before even having safestrap installed and the su file did the same .. so flashing it will make it work plus do notice there is an update for SuperSu on his site [chainfire}
phillymade said:
if you have safe strap installed, you can download the Su zip file and flash in recovery. you can find it in the Android thread, just use the search. I have done it this way and works like a charm.
Click to expand...
Click to collapse
I just noticed that apon installikng safestrap after having these issues i can actually open SuperSU with out it asking me to update again so i didnt have to flash the zip just install safestrap the proper one for kit kat Hashcode/note3/hltevzw/safestrap/Safestrap-HLTE-3.72-kk-B01.apk search thanks
sure. but be advised, there is an updated version of SS. HLTE-3.72-kkB04. it's in the SS OP. Look for the Crack flasher link. this version has rom slot support.
phillymade said:
sure. but be advised, there is an updated version of SS. HLTE-3.72-kkB04. it's in the SS OP. Look for the Crack flasher link. this version has rom slot support.
Click to expand...
Click to collapse
yes i read about that earlier where you have to use the stock slot to use a rom besides the slot you use for the backup .. so this Su youre talking about fixes those issues .... can you tell me to find it because ive searched Google already and keep coming up empty for that file ... more over looking into roms im seeing ill have to flash a stock rom that will install bootlaoders that i will need before flashing any custom roms ..is this about right ? thanking you in advance @phillymade
for Flashing custom Rom follow this OP, http://forum.xda-developers.com/showthread.php?t=2787627 and you can flash a custom Rom in place of the stock rooted. as for the Su, are you looking for the super user zip or the updated safe strap. I'm a bit confused by the post as to what you are asking
phillymade said:
for Flashing custom Rom follow this OP, http://forum.xda-developers.com/showthread.php?t=2787627 and you can flash a custom Rom in place of the stock rooted. as for the Su, are you looking for the super user zip or the updated safe strap. I'm a bit confused by the post as to what you are asking
Click to expand...
Click to collapse
i noticed after yes the updated safestrap with the slots fixed
I RE read your OP. you are stock root. Did you install busy box? If not, download it from the play store look for busy box installer. this will help with any issues with su and such
i only see this on crackflasher but in thrown off as i dont know what the NC2 is about Safestrap-HLTEVZW-NC2-3.75-B04.apk | hltevzw | Hashcode0f
phillymade said:
I RE read your OP. you are stock root. Did you install busy box? If not, download it from the play store look for busy box installer. this will help with any issues with su and such
Click to expand...
Click to collapse
when you told me about flashing it ., i said let me check the Su since i had previously installed it before safestrap but some how installing safestrap fixed my issue of Su asking to update binary and failing apon reboot so now i just want to basically update safestrap and install a romm thats stable with almost no flaws

Weird semi-root situation.

Hi guys,
Yesterday i have rooted a friend's phone with a laptop using the RootGenius application and all worked perfectly and the root is working good.
EDIT: I've tested other root apps on my friend's phone and it's the same problem. So that app didn't rooted correctly.
After that, i rooted my phone wich is a Samsung Galaxy S4 Black Edition (i9505) and...well, something went wrong there. After the root, all the programs were stopping working. The installed programs were not available and i couldn't open almost any app. I did a factory reset and now it's working fine, but...the root acces it's a little bit f****d up.
If i check the root with Root Checker, it says that i have root access. The superuser app is called KingUser and i never heard of this app.
Now, here comes the problem: if i want to use a root-needed app like GameCIH, for example, i grant the root access, but i can't use the app, it says that i don't have a rooted phone...
I can use the XMODGAMES app wich is also a root-needed app, but i want to use all the root apps, 'cause why not?
I tried to install SuperSU. When i open it, it says that i need to update SU binaries. I press normal, because i don't have a custom recovery and then i grant root acces and then it says: Failed, reboot the phone and try again. I rebooted it a few times and no succes, the same thing.
So what should i do?
Should i unroot it and then re-root it?
If yes, how?
Thanks.
Have a nice day.
Why not just use CF auto-root for flashing. Easiest method and never fails.
Unroot and reroot using CF-Autoroot. Search for the CF-Autoroot thread to learn how it's done.
Be aware however that this will trip the Knox flag.
Strephon Alkhalikoi said:
Unroot and reroot using CF-Autoroot. Search for the CF-Autoroot thread to learn how it's done.
Be aware however that this will trip the Knox flag.
Click to expand...
Click to collapse
Thanks, I will try to do that. But what means that it will trip Knox flag?
We have an entire thread on Samsung's Knox software on the forum, but in short the flag is a means for Samsung to tell the phone's firmware has been tampered with.
Strephon Alkhalikoi said:
We have an entire thread on Samsung's Knox software on the forum, but in short the flag is a means for Samsung to tell the phone's firmware has been tampered with.
Click to expand...
Click to collapse
And so it's bad if i use cf-root?
Cubix202 said:
And so it's bad if i use cf-root?
Click to expand...
Click to collapse
No, it's not.
Lennyz1988 said:
No, it's not.
Click to expand...
Click to collapse
Ok thank you. I have one more question.
So i didn't find anything on how to unroot with cf-auto-root for android 5.0.1....
Can i root it over the root that it has right now?
I mean just root it again by following this post: http://forum.xda-developers.com/showthread.php?t=2219803
Stay away from Kingroot,nothing but trouble,on some devices whitch are difficult to root it can be a sollution ,on Samsung it's Chainfire auto root. And i strongly advice to remove the Kinguser app !!!
ludoke said:
Stay away from Kingroot,nothing but trouble,on some devices whitch are difficult to root it can be a sollution ,on Samsung it's Chainfire auto root. And i strongly advice to remove the Kinguser app !!!
Click to expand...
Click to collapse
This situation is beyond me
How can I remove the KingUser app?
Now i was trying to install CWM Recovery someway to be able to update su binaries trhu it with SuperSu.
Can i add you on Facebook or Steam or Skype or whatever to help me faster?
Or can you send me a detailed step-by-step thing to help me faster..?
Thanks
You can remove King user by clicking on the icon,hold it en move it to the left upper corner ,where it'saing delete app or something like that in Dutch it's "installatie ongedaan maken"
At first root whith Chainfire ,don't use CWM but TWRP 2.6.0.0? Search for it,and dont use TWRP 2.8.5.0.
ludoke said:
You can remove King user by clicking on the icon,hold it en move it to the left upper corner ,where it'saing delete app or something like that in Dutch it's "installatie ongedaan maken"
At first root whith Chainfire ,don't use CWM but TWRP 2.6.0.0? Search for it,and dont use TWRP 2.8.5.0.
Click to expand...
Click to collapse
Damn, i just installed CWM recovery with succes....
I can't uninstall KingRoot or KingUser or KingMaster, whatever is called, it's installed as a system app.
And...i think i just ****ed up my recovery. I can't boot into recovery mode.
Cubix202 said:
Damn, i just installed CWM recovery with succes....
I can't uninstall KingRoot or KingUser or KingMaster, whatever is called, it's installed as a system app.
Click to expand...
Click to collapse
That's why i said it's trouble, the only sollution to remove it is factory reset,root again and custom recovery,use this time TWRP much easier ,just touch and spare the volume rockers
Sorry,didn't know it's removable that way...says enough i think...
The factory reset dont unroot, i factory reseted and the phone is still in that trouble.
And with the recovery? Can i install TWRP now?
Ok so i figured out what i've done: I have installed Philz Recovery which is a CWM recovery 6 with touch version and it works via an app that boots into recovery (root app that fortunattely worked as root). So what do i need to do now?
If i open SuperSu it says that it needs to update the su binary. When i tap normal it fails and then i tap cwm/twrp, it dosen't do anything, even if i boot into recovery mode. Do i need to install a zip SU-BB? I did it and it didn't work. Any other ideas?
ludoke said:
You can remove King user by clicking on the icon,hold it en move it to the left upper corner ,where it'saing delete app or something like that in Dutch it's "installatie ongedaan maken"
At first root whith Chainfire ,don't use CWM but TWRP 2.6.0.0? Search for it,and dont use TWRP 2.8.5.0.
Click to expand...
Click to collapse
Your information is outdated. TWRP is already on 2.8.7.0 and it's the only one that should be used. Do not use old version because it will give you conflicts with Lollipop.
Cubix202 said:
Ok so i figured out what i've done: I have installed Philz Recovery which is a CWM recovery 6 with touch version and it works via an app that boots into recovery (root app that fortunattely worked as root). So what do i need to do now?
If i open SuperSu it says that it needs to update the su binary. When i tap normal it fails and then i tap cwm/twrp, it dosen't do anything, even if i boot into recovery mode. Do i need to install a zip SU-BB? I did it and it didn't work. Any other ideas?
Click to expand...
Click to collapse
What you need to do:
- If you are on the latest Philz just perform a full wipe. Reflash the rom. And do what I told you.
Lennyz1988 said:
Your information is outdated. TWRP is already on 2.8.7.0 and it's the only one that should be used. Do not use old version because it will give you conflicts with Lollipop.
What you need to do:
- If you are on the latest Philz just perform a full wipe. Reflash the rom. And do what I told you.
Click to expand...
Click to collapse
I've bricked my phone.
Cubix202 said:
I've bricked my phone.
Click to expand...
Click to collapse
No you have not.
Lennyz1988 said:
No you have not.
Click to expand...
Click to collapse
Yes i have.
It is stuck at bootlogo SAMSUNG.

Resources