Hi
Many people complained last days that they have problem with SuperSU 0.99 app.
They cant update the binary and phone reboots its self after "update failed" message
I got an HTC One S with S4 cpu last week and i got the new Jelly Bean Update 4.1.1
Then i unlocked my bootloader and installed TWRP custom recovery with One_S_All-In-One_Kit_v3.0 tool kit
After that i tryed to Root the phone with SuperSU 0.99.
Seems worked fine until i tryed to update my binary.
I get message "update failed" and my phone restarts.
I tryed to wipe and reflash the root but still same.
I even tryed to remove SUPERSU from System/App but with no luck. It keeps coming back even if i
removing it and revert everything to stock its still in SYSTEM.
Now i found this new Superuser version and flashed it and now my phone works fine and updating binary.
No more phone restart.
Even my SuperSU 0.99 is gone from system.
How TO:
Download superuser from this page http://androidsu.com/superuser/
Superuser-3.2-RC3-arm-signed.zip
Then boot into recovery
Flash Superuser-3.2-RC3-arm-signed.zip
Restart and voila the root works...
Hope i helped you guys.. Good Luck
Version 3.1.3 is reported to work better.
And doubt it really needed a new thread starting its discussed in most rom treads.
I started this thread just because of the issue SUPERSU 0.99 brings to HTC One S with Jelly Bean update.
I hope i can help someone because i didnt find any solution to my problem until i flashed superuser and it solved my problem.
shadowch31 said:
Version 3.1.3 is reported to work better.
And doubt it really needed a new thread starting its discussed in most rom treads.
Click to expand...
Click to collapse
I agree that this adds clutter, but I have been lightly following the threads for the JB ROMs and tried using superuser (though not the rc) without it working (still unable to update system). It's good to have this kind of solution in its own thread but general would probably be a better section.
Sent from my HTC One S Special Edition using xda app-developers app
This doesn't belong in the dev section for multiple reasons
Sent from my HTC VLE_U using xda app-developers app
Im sorry i didnt see that it was Development section. If someone can move it pls do so.
everyone uses SU...... this is very important for everyone using JB... leave it in here...
I feel it belongs here... this is where SU apps are in the development section... SO, this is where it should stay... (that is just my opinion)
I never want to start this thread like an development because im not a developer.
Reason is that i want to share my issue with anyone who is facing the same problem as i did.
Just like i said if someone think this thread doesn´t belong here then admins can move it to right section.
Updated to JB with OTA yesterday night.
Short version:
-Initially rooted with CWM recovery-> flashed MoDaCo stock recovery
-Apply OTA
-Flash CWM recovery
-Used CWM recovery to flash SuperSU 0.99 zip
-Uninstall/reinstall SuperSu from the Market
When starting SuperSU, it asks for update, if agree -> reboot.
BUT
When using root needing apps, like Titanium backup or FX file manager, they ask for root permission through SU and everything runs normally.
So SuperSU seems to work, only the front end app has some bug. I'm staying with that config waiting for an update.
Hi, same problem here on S3 cpu. Is this method works on S3 cpu as well? Thx for replying.
Hi. I think I have a problem with SuperSU (or something else??). I first started SuperSU last thursday (31.1.2013.). It ask me to update binary, I hit OK, and then it took about half hour to restart. System then recovered, and everything seem to be OK, but it's not!
When I connect my HTC One S to PC I only see files created (photos, videos) until 31.01.2013. Also, when I run Settings -> Memory com.android.settings crashes.
What to do?
I'm new to android. Plese help!
bihslk said:
Hi
Many people complained last days that they have problem with SuperSU 0.99 app.
They cant update the binary and phone reboots its self after "update failed" message
I got an HTC One S with S4 cpu last week and i got the new Jelly Bean Update 4.1.1
Then i unlocked my bootloader and installed TWRP custom recovery with One_S_All-In-One_Kit_v3.0 tool kit
After that i tryed to Root the phone with SuperSU 0.99.
Seems worked fine until i tryed to update my binary.
I get message "update failed" and my phone restarts.
I tryed to wipe and reflash the root but still same.
I even tryed to remove SUPERSU from System/App but with no luck. It keeps coming back even if i
removing it and revert everything to stock its still in SYSTEM.
Now i found this new Superuser version and flashed it and now my phone works fine and updating binary.
No more phone restart.
Even my SuperSU 0.99 is gone from system.
How TO:
Download superuser from this page http://androidsu.com/superuser/
Superuser-3.2-RC3-arm-signed.zip
Then boot into recovery
Flash Superuser-3.2-RC3-arm-signed.zip
Restart and voila the root works...
Hope i helped you guys.. Good Luck
Click to expand...
Click to collapse
I'm glad I ran across your thread. It helped me tremendously...
Da Baron
Any idea on how to get SuperSU work instead of SuperUser? I purchased SuperSU in the play store and I think it just looks better...
I have had my phone rooted for about a year. I updated my phone 2 months ago to Quantum kitkat 4.4.2 and I seem to have lost root. I can still reboot into custom recovery, update and install zip files, create backup, etc. yet the phone has lost superuser. I have tried re installing SU via app and zip. It says "the SU binary needs to be updated" Every way i have tried has failed. I have tried rerootin using Framaroot and through terminal emulator using motochopper. none works. When I updated to the newest Kitkat 6.1 kernell yesterday in recovery it said " phone is not rooted would you like to root?" when i said yes it stayed in endless boot loop.
HELP! How can I get root back without factory reset and staying on Quantum kitkat?
Samsung SGH I747
android version 4.4.2
Try this go to settings about phone tao the build 7 times now it should say developer options now enabled go to developer options find were it says root access and make sure it says apps and adb then reboot and try to install SuperSU let me know if that helped
Sent from my lg optimus e980 mega i527 mega gt-i9205 Nexus 5 Nexus 4
Don't forget to check out my custom keyboards and dialers over at the candyshop thread and all the other cool stuff from all the wonderful devs
http://forum.xda-developers.com/showthread.php?p=49380310
Ive recently had my phone rooted (by ROOTANDROID.COM) and ive had problems with the su root. ive factory reset phone by going into recovery mode and re-flashed cf-root several times, and resetting phone and cache and reinstaling & updated su and su pro, along with rom toolbox pro, via google playstore, and it says message on fone screen saying su binary needs updated. do i need to do it manualy ? ive tried thru google play with no success...ive lost my wifi and my device seems slow, my phone is samsung galaxy S5 LTE A G906S RUNNING 4.4.2 KK
ANK1 Update. think its the latest software update.
THANKS FOR ALL THE HELP GUYS,
I SORTED IT MYSELF ;-D
zac
So I downloaded the new Android Pay app last night, but it doesn't seem to work if you have a custom ROM installed. I have a T-Mobile phone and I'm currently on Resurrection Lollipop (CM 12.1 based) and it gives me the error "Google is unable to verify that your device or the software running on it is Android compatible".
This needs to change.
UPDATE - I found a workaround that *may* help out. Go into SuperSU and disable root (or disable however you want), try adding your cards again, and then go re-enable root. This has worked for many people on other phones with this error, but it didn't help on my T-Mobile S4
Let me know if you get it to work on another ROM (or even if it works at all on stock right now) or if you have a workaround for this.
Dowload - http://www.mediafire.com/download/1b..._930000657.apk
is not working on official at&t rom 5.0.2 FC android System
Edgardo Regazzoni said:
is not working on official at&t rom 5.0.2 FC android System
Click to expand...
Click to collapse
Does it give the same error?
As in the title states I have the galaxy tab 2 7.0 and recently I installed CWM and a ROM and everything looked like it went right however after I reloaded my tablet nothing seems different it jus seems to return to stock setting and now I cant do the OTA software update which means now certain apps and games I can no longer uses as it says my device isnt compatible. My goal was to simple update from Jellybean to at Least Kitkat.
Can someone help me. where did I go wrong?
Fleacore210 said:
As in the title states I have the galaxy tab 2 7.0 and recently I installed CWM and a ROM and everything looked like it went right however after I reloaded my tablet nothing seems different it jus seems to return to stock setting and now I cant do the OTA software update which means now certain apps and games I can no longer uses as it says my device isnt compatible. My goal was to simple update from Jellybean to at Least Kitkat.
Can someone help me. where did I go wrong?
Click to expand...
Click to collapse
Go to sammobile and flash the latest stock firmware for your device .
Newyork! said:
Go to sammobile and flash the latest stock firmware for your device .
Click to expand...
Click to collapse
Well after a short research I found a ROM called Resurrection Remix, loaded with 5.0.2 (or Lollipop) however now everything is force closing and I barely got my laptop to see it as MTP again after installing a new Binary (glad that did that trick for that) but I cant get it to boot into CWM Recovery bc I cant access the app the only thing it will let me do right now is change the Binary.
How can I fix this issue?
Edit: Okay so I got that solved with doing a factory reset twice, booted in CWM, loaded up the GApps. Now just wondering if there is away to make it not seen with phone options like the dialer or msgs as its jus a plan old tablet, doesnt take a sim card and has no carrier. I do have the source code but I am not tweaking that til I get a better understanding of it.
After a lot of research and tries (amazingly without bricking) I am now running an even newer version of a CM 13 Marshmellow