Anyone know how to get permanent root?What i mean by permanent is when i reboot the phone i still have it.
I usually update to D107 then root phone using one click root method,install magic aosp rom,go to SuperUser(which i placed in /system/app folder) it ask me to update to newest version,i click ok and it works,i get root access in Estrong File Manager and other root apps,i can delete and modify /system folder from Estrong file manager.
After reboot i go to Estrong file manager and it doesnt work any more,SuperUser looses its update and any root app i install after reeboot dont get SuperUser prompt for root access anymore.And if i try to update SuperUser it says that update was successful but at the bottom i don't see new version.I still get root if i adb shell su,but on android i don't get asked for su anymore and i dont think i have root on the phone.Can anyone post step by step instruction for getting "permanent root",Thanx in advance.
I think you do have root, but the issue is that root has to be re-enabled after every reboot (it is done automatically and doesn't require user intervention). Don't ask me why, but that seems to be how root in the Epic currently works with the jk method. The superuser app will work only the after it is installed, and subsequent to a reboot, will loses its ability to control permissions, and any new apps that need (or want) to get superuser status will do so without a prompt from the superuser app, which could be bad depending on the app.
Check this thread where they found a work around: http://forum.xda-developers.com/showthread.php?t=788939
jokarak said:
I think you do have root, but the issue is that root has to be re-enabled after every reboot (it is done automatically and doesn't require user intervention). Don't ask me why, but that seems to be how root in the Epic currently works with the jk method. The superuser app will work only the after it is installed, and subsequent to a reboot, will loses its ability to control permissions, and any new apps that need (or want) to get superuser status will do so without a prompt from the superuser app, which could be bad depending on the app.
Check this thread where they found a work around: http://forum.xda-developers.com/showthread.php?t=788939
Click to expand...
Click to collapse
Thanx man,that definetly looked promising but dint fix the problem.I wondrer if its just certain phones that have this problem because I don't see many people complaining or is it just certain roms and kernels.
lviv73 said:
Thanx man,that definetly looked promising but dint fix the problem.I wondrer if its just certain phones that have this problem because I don't see many people complaining or is it just certain roms and kernels.
Click to expand...
Click to collapse
Hey bro, this is what i did because last night i installed the mix kernel and was getting to many dropped calls even in voicemail.
I re-flashed my epic to complete stock, i then ran the Andro/koush one-click method to get clockwork recovery. Then i flashed the Bub's AOSP Magic rom, now i tried to install Andro kernel to get superuser but this didn't work (couldn't gain root), so then i removed superuser.apk and install fluff kernel power saver one and have perm root.
http://forum.sdx-developers.com/epi...uffkernel-epic-4g-version-1-0-1-2-8-1-mflops/
If i remember correctly those was the steps i did.
mykenyc said:
Hey bro, this is what i did because last night i installed the mix kernel and was getting to many dropped calls even in voicemail.
I re-flashed my epic to complete stock, i then ran the Andro/koush one-click method to get clockwork recovery. Then i flashed the Bub's AOSP Magic rom, now i tried to install Andro kernel to get superuser but this didn't work (couldn't gain root), so then i removed superuser.apk and install fluff kernel power saver one and have perm root.
http://forum.sdx-developers.com/epi...uffkernel-epic-4g-version-1-0-1-2-8-1-mflops/
If i remember correctly those was the steps i did.
Click to expand...
Click to collapse
Thanx man,that fixed my root,you saved me alot of trouble,i guess it was the kernel.Oh and the fluff kernel is probably the smoothest kernel i used so far,now my root is there all the time,thanx again.
I got the OTA this morning, and it soft bricked my phone... so I used Odin and went to JI6 (from the stock ROM). Phone was rooted and unlocked before.
Now when I try to root, I place the update.zip in the root directory of the phone (not the sdcard), reboot into recovery using the volume buttons, it says it flashed.
But, when I go to use any app like Clockwork Mod, that requires root... I get the same error msg every time "The application Superuser Permissions (process com.noshufou.android.su) has stopped unexpectedly. Please try again. [Force Close] button.
I've tried to root repeatedly, same results.
What am I doing wrong? It was so simple the first time around.
Thanks
mtburner said:
I got the OTA this morning, and it soft bricked my phone... so I used Odin and went to JI6 (from the stock ROM). Phone was rooted and unlocked before.
Now when I try to root, I place the update.zip in the root directory of the phone (not the sdcard), reboot into recovery using the volume buttons, it says it flashed.
But, when I go to use any app like Clockwork Mod, that requires root... I get the same error msg every time "The application Superuser Permissions (process com.noshufou.android.su) has stopped unexpectedly. Please try again. [Force Close] button.
I've tried to root repeatedly, same results.
What am I doing wrong? It was so simple the first time around.
Thanks
Click to expand...
Click to collapse
Check to make sure, you have latest release of busy box installed.
Do I need busy box? I didn't need it the first time I rooted.
Did you rename the update.zip file that was already on your internal memory from when you flashed clockwork recovery the first time?
Are you sure you didn't name it update.zip.zip because your pc was hiding the file extension?
Check the general sticky. I odin to ji6 and routed no problem and put my steps in the sticky.
Try the OCLF by Ryan. I used that to re-root my Vibrant after successfully updated to JI6 via Kies Mini last night.
OCLF - One Click Lag Fix. That app is in market and it will root your phone so no pc is needed. You need to run it on your samsung vibrant phone once than reboot it. You should see super user permission icon in your apps.
I was using Visionary to temproot my Shift. I am halfway through the permanent root process (step 6), but Visionary no longer lets me temproot. I read in another thread about issues with superuser and temprooting a second time, so I uninstalled superuser. That didn't fix my problem.
When I try to temproot now, the process starts, runs for 8 seconds, then the phone reboots.
Visionary is not set to temproot at boot. If I try unrooting, Visionary tells me the phone isn't rooted.
One thing which is unusual is that the phone continues to reboot after Visionary fails the temproot. Sense begins to load, then the phone reboots, and it will continue to do this unless I pull the battery.
Ideas or suggestions for completing permroot are greatly appreciated.
You need to uninstall visionary and do a reboot.
powered by the tears of a million orphaned alpacas...
Also, make sure you have airplane mode enabled. I think that is in the instructions though.
Sent from my PG06100 using XDA App
OK, uninstalled Visionary, powered down, pulled the battery, booted, and verified that Visionary was not installed. I then installed it, tried the temproot, and the phone rebooted.
This is crazy....
This is a common issue among alot of us shift users, youll also notice on the reboot on a failed temp root that the phone is superbly slow, etc, try powering down on a failed temp root normally (meaning dont pull the battery actually power it down) wait a few, then power it on. Let it boot, and wait a few seconds after getting into the home screen, one it seems to have fully loaded everything, go ahead and attempt a temp root with visionary, if you are successful continue on with the perma root instructions. I had the same issue,however just so you know I had to make sure that my phone was NOT in airplane mode for the temp root but it needed to be in airplane mode for the Perma root portion, if i tried it any other way it failed, but now i have a perma rooted shift and it works perfectly. Hope that helps.
Yes, I have airplane mode enabled. I have followed the permroot instructions to the letter.
Very frustrating........
RESOLVED
I had to reset the phone to factory defaults, install Visionary, and proceed from that point.
Thankfully I had backed everything up with Titanium Backup before starting the entire process.
Thanks to all who gave suggestions and advice.
Currently Running Miui 2.7.1.3 i believe the numbers are, whichever the latest version of the rom is. It installed no problem, was merely updating to try to fix theme issues from 2.6, and here is where the problem begins:
So i was browsing my phone and realised that i didn't have superuser on there, wondering why because usually every rom i ever ran had it automatically on there, installed it off of another site, the elite version, and from there everything got screwed up, i don't know what happened or why it started but, i could no longer run busybox, TBU, setcpu, nothing that requires root, due to the fact that superuser was denying root. I had no clue why, i've been reading threads for hours similar to "Superuser denying root" and such, and to no avail, the problem is still there, i have set superuser to both prompt and allow when asking for root, and neither worked, so i figured a clean fresh reflash of MIUI would help, however even after wiping and a clean install, root does not work, ive read some articles describing to just unroot and root again however it's been so long since ive rooted a phone, can anyone direct me to the best way to do this without having to do an ODIN and set up my phone allover again, keep in mind that it is still S-Off. What am i doing wrong?
I also have tried to clear data for superuser, as well as install multiple versions, neither have worked.
Any help is greatly appreciated!
ROBLEM SOLVED:
To those with similar problems to this who have ruled out other reasons, described in this thread, abandon Superuser and download SuperSU instead, it fixed my problem.
Odin is for Samsung Phones and if u lost root redownload the rom or Google super user and download the binaries and just flash them.
Sent from my Dark Unicorn Resurrected v.2.5 using Tapatalk 2
I tried all that, anyway im in the middle of a stock restore right now and trying to reroot but stuck at the damn visionary step >.<
I am now stuck with S-on and back in a stock rom, downgraded, and visionary still doesnt work, i give up
Try gfree method
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium
You're very likely doing so much wrong..
MIUI has an option in settings - "allow superuser privileges". You didn't turn it on, and it's off by default. That's it. And from there you went to a whole new level of going the wrong way.
No amount of restoring to stock and re-rooting can help you. Root privileges aren't phone-specific, they're ROM-specific, and relevant only for the ROM currently on the phone. Reflash the ROM with something else - and existence or inexistence of root will depend on this "something else". Thus I fail to understand, what were you looking for when restoring to stock. It was as irrelevant as could possibly be.
Jack_R1 said:
You're very likely doing so much wrong..
MIUI has an option in settings - "allow superuser privileges". You didn't turn it on, and it's off by default. That's it. And from there you went to a whole new level of going the wrong way.
No amount of restoring to stock and re-rooting can help you. Root privileges aren't phone-specific, they're ROM-specific, and relevant only for the ROM currently on the phone. Reflash the ROM with something else - and existence or inexistence of root will depend on this "something else". Thus I fail to understand, what were you looking for when restoring to stock. It was as irrelevant as could possibly be.
Click to expand...
Click to collapse
I believe you got two troubleshootings steps backwards.
After you have searched and exhausted every troubleshooting step you found (which obviously wasn't thorough), you should have posted in the MIUI thread about the problem. They might have scolded you a little before answering, but you would have gotten your answer.
Flashing back to stock is ALWAYS your last resort. It should only be done after scouring the web for answers, then asking for the answer, and when there is no other alternative - FroYo PD15IMG.zip.
Jack is blunt, but as he's as right as always.
I'm not one to deny mistakes, that sure was stupid of me not to look, i guess i just thought there were deeper problems than just the rom having it turned off, anyway i'm doing the downgrade now and it should work, thank you for the help its appreciated
Jack_R1 said:
You're very likely doing so much wrong..
MIUI has an option in settings - "allow superuser privileges". You didn't turn it on, and it's off by default. That's it. And from there you went to a whole new level of going the wrong way.
No amount of restoring to stock and re-rooting can help you. Root privileges aren't phone-specific, they're ROM-specific, and relevant only for the ROM currently on the phone. Reflash the ROM with something else - and existence or inexistence of root will depend on this "something else". Thus I fail to understand, what were you looking for when restoring to stock. It was as irrelevant as could possibly be.
Click to expand...
Click to collapse
Could you point me to this "allow superuser privileges"? I have restored with recovery and have yet to find such a setting.
If you are referring to the permission guard, it allows everything, and there is no setting to simply turn it on
No, not this one. It's been some time since I sold my Nexus One, which was running MIUI back at the time, but I understand that in the newer MIUI there is an app or setting, called LBC guard, which controls both Superuser access and app permissions. Try looking it up.
P.S. I remember CM team member post, saying that the newer CM9 also come with root privileges turned off by default, because they decided it's a safer way.
Right, and the Permission Guard is run by LBC guard, there is no way to set anything different from what i have, i believe its a problem with the busybox binaries and superuser binaries, i'm trying to use this SuperSU instead of superuser to see if that will work. If i remember correctly before all this happened i may have hit uninstall busybox by accident and that may be why its not working, could be that ive never had busybox working and haven't been able to install it due to the SU problem
EDIT: Yes i have solved it now, SuperSU actually makes the prompts for superuser come up now, im using it instead of superuser entirely, must be deeper problems with original superuser
If you had SuperSU installed on the system and additionally installed the regular Superuser, or the other way around - these two are incompatible on binaries AFAIK, and mixing the applications without cleaning up the build and using the correct binary could cause what you were experiencing.
Yes your probably correct only i had two separate versions of superuser that didnt overwrite and that must be where the binaries got messed up
The 1st thing I usually do when I install a new rom, is install SuperSU, update the binaries then I use Titanium to uninstall Superuser.
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium
Drakona.cookie said:
Currently Running Miui 2.7.1.3 i believe the numbers are, whichever the latest version of the rom is. It installed no problem, was merely updating to try to fix theme issues from 2.6, and here is where the problem begins:
So i was browsing my phone and realised that i didn't have superuser on there, wondering why because usually every rom i ever ran had it automatically on there, installed it off of another site, the elite version, and from there everything got screwed up, i don't know what happened or why it started but, i could no longer run busybox, TBU, setcpu, nothing that requires root, due to the fact that superuser was denying root. I had no clue why, i've been reading threads for hours similar to "Superuser denying root" and such, and to no avail, the problem is still there, i have set superuser to both prompt and allow when asking for root, and neither worked, so i figured a clean fresh reflash of MIUI would help, however even after wiping and a clean install, root does not work, ive read some articles describing to just unroot and root again however it's been so long since ive rooted a phone, can anyone direct me to the best way to do this without having to do an ODIN and set up my phone allover again, keep in mind that it is still S-Off. What am i doing wrong?
I also have tried to clear data for superuser, as well as install multiple versions, neither have worked.
Any help is greatly appreciated!
ROBLEM SOLVED:
To those with similar problems to this who have ruled out other reasons, described in this thread, abandon Superuser and download SuperSU instead, it fixed my problem.
Click to expand...
Click to collapse
Anyone else with this problem go in the permissions app and enable root as miui uses its own root for security reasons.
Sent from my T-Mobile MyTouch 4g using xda premium
MIUI uses a customized superuser app. Use it and follow the instructions. Cnote ports the ROM. He knows what he's talking about.
Hello, I am a newbie and looking for a miracle. I am going to apologize for the length of this message in advance. Couple days ago I perm rooted the HTC Glacier Mytouch 4g using the instructions at //wiki.cyanogenmod.org/w/Install_CM_for_glacier . As instructed, I downgraded the software to 1.17.531.2 and then perm rooted with S-Off on the device. Then, I installed the cyanogenMod 7.2.0-glacier (stable version) with the google apps. Everything worked great and was happy.
Right after I installed AdFree from Googleplay, I had issues but problem may not be caused by this app. Googleplay gave me a message of an “error no connection”. I got a message that the “ADWLauncher failed to launch” over and over again which prevented me from doing anything else. I was able to reboot the phone in between the notifications of the ADWLauncher failure. When I was back up and running, I got the same message of Googleplay “error no connection” and ADW failure very quick after start up. I pulled the battery and did a hard power up (volume down plus power button at same time). This is when things got worse. The Hboot starts up and wants to update, which I did but then I could not choose recovery mode to install a backup. If I choose not to update Hboot, then I only have the option to restart the phone. I can see on top of the screen “Glacier PVT SHIP S-OFF” .
Wait – things get worse. I am no longer running the cyanogenmod ROM but am back to the downgraded ROM 1.17.531.2. I still can’t download from googleplay because I get the message “Error no connection”, even though I am running on the old ROM. I can’t download apps from the phone, but I can push apps to phone from my googleplay account. I did push the ROM Manager app to the phone. When I start the ROM Manager, I get the message “You must root phone for ROM to function. Superuser was not found at “/system/bin/su” or “/system/xbin/su”.
I tried to start the recovery through adb using “adb reboot recovery”, but I get a power off symbol (a red circle) and phone freezes. I need to pull the battery to reboot.
Again sorry for the length. I am hoping for a miracle. Since I can’t do anything in the hard power up mode, I need to find a way to fix through adb or fastboot. Does anyone know how to get the Superuser installed through adb or fastboot? Is there a way to flash another custom ROM that has a superuser installed through adb or fastboot?
BTW. Gmail works fine.
thanks
Droid-2 said:
Hello, I am a newbie and looking for a miracle. I am going to apologize for the length of this message in advance. Couple days ago I perm rooted the HTC Glacier Mytouch 4g using the instructions at //wiki.cyanogenmod.org/w/Install_CM_for_glacier . As instructed, I downgraded the software to 1.17.531.2 and then perm rooted with S-Off on the device. Then, I installed the cyanogenMod 7.2.0-glacier (stable version) with the google apps. Everything worked great and was happy.
Right after I installed AdFree from Googleplay, I had issues but problem may not be caused by this app. Googleplay gave me a message of an “error no connection”. I got a message that the “ADWLauncher failed to launch” over and over again which prevented me from doing anything else. I was able to reboot the phone in between the notifications of the ADWLauncher failure. When I was back up and running, I got the same message of Googleplay “error no connection” and ADW failure very quick after start up. I pulled the battery and did a hard power up (volume down plus power button at same time). This is when things got worse. The Hboot starts up and wants to update, which I did but then I could not choose recovery mode to install a backup. If I choose not to update Hboot, then I only have the option to restart the phone. I can see on top of the screen “Glacier PVT SHIP S-OFF” .
Wait – things get worse. I am no longer running the cyanogenmod ROM but am back to the downgraded ROM 1.17.531.2. I still can’t download from googleplay because I get the message “Error no connection”, even though I am running on the old ROM. I can’t download apps from the phone, but I can push apps to phone from my googleplay account. I did push the ROM Manager app to the phone. When I start the ROM Manager, I get the message “You must root phone for ROM to function. Superuser was not found at “/system/bin/su” or “/system/xbin/su”.
I tried to start the recovery through adb using “adb reboot recovery”, but I get a power off symbol (a red circle) and phone freezes. I need to pull the battery to reboot.
Again sorry for the length. I am hoping for a miracle. Since I can’t do anything in the hard power up mode, I need to find a way to fix through adb or fastboot. Does anyone know how to get the Superuser installed through adb or fastboot? Is there a way to flash another custom ROM that has a superuser installed through adb or fastboot?
BTW. Gmail works fine.
thanks
Click to expand...
Click to collapse
I would download a recovery image and use fastboot to install it. Maybe something is wrong with your recovery.
fastboot flash recovery recoveryname.img
Then wipe system, do a factory reset, and wipe dalvik-cache before flashing a ROM. Also, re-download your ROM.
estallings15 said:
I would download a recovery image and use fastboot to install it. Maybe something is wrong with your recovery.
fastboot flash recovery recoveryname.img
Then wipe system, do a factory reset, and wipe dalvik-cache before flashing a ROM. Also, re-download your ROM.
Click to expand...
Click to collapse
Thanks - I will need to try this later