Heya, the N1 is my first phone so a lot of this is brand new territory for me
Anyhow I had a problem with a metamorph theme so i used nandroid to restore back to an update i made this morning (After i rooted N1). However now apps that require root access (Metamorph, N1 torch etc) are now all running into errors such as cannot access LED, cannot extract files (Even though all partitions have at least 40% free space).
Any ideas guys? Thanks!
EDIT: One of the root programs i tried to run stated that it can only run in read-only mode, is this familiar to anyone? Thanks!
your answer is in other parts of the forum but you still have root just dont have su permission anymore. you can flash a custom rom or flash the cyanogen add-on. pm if you need help
Ah right, is this common after a nandroid backup? Could someone perhaps post the link to the cyanogen add-on? I'm currently running the latest cyanogen for the nexus one, thanks
As far as I know the Cyanogen add-on is the Cyanogen rom. It is not a completely standalone rom, just sort of a patch for the stock rom.
I just re-flashed the rom and everything is sweet again. This is my first android phone never mind first rooting experience so all this is new Cheers guys
http://forum.xda-developers.com/showthread.php?t=634986
I need help rooting my HD2. I have MDJ's CyanogenMod 7 (v. 2.5) A2SD+. Thank you.
Should already be rooted. I'm also pretty sure he states as much in the first three or four posts.
Sent from my HD2 using XDA App
z4root will do the job for you. Here you go matey...
http://forum.xda-developers.com/showthread.php?t=833953
I am currently running that ROM and can confirm it is rooted.
But every time I use an app that is only for rooted phones it says that my phone needs to be rooted. (The app I want to use is Wifi Password in the market)
Weird... I just downloaded that app and tried to run it. The Superuser screen comes up, I clicked allow and then I get the same message. Everything else I've tried needing root has worked.
Edit: Reading the comments, I see other people have the same issue. There is something fishy (in my semi-paranoid mind) about an app that needs root access to remember wifi passwords and is as large as it is (890kb).
There have been issues with root in MDJ's rom, I've had it myself too. A reflash should fixit. If you're on cwm, do factory reset and dalvik wipe before reflashing.
So just flashing it again is the solution?
Yes, it should be.
OR you could try z4root like the guy a few posts up suggested. It's fixed all my root issues in the builds I've used that have had root issues.
Ok I did it guys thank you!
Something strange has happened with my Desire HD
I've had CM7 installed and fine for a while, I tried to install the latest Nightlies i got an error about scripts not being able to run. Thought it was just a problem with the nightly and ignored it.
But since then i've noticed problems with other apps that require root privileges.
it seems like i've lost root access some how. it must have happen recently but I can't remember having problems with any apps, but the backup i made before I tried to install the nightly has the same problem.
Anyone had something like this happen before?
I've tried a factory reset but problem remains.
I'm going back to a backup I made 4 weeks ago and see if that fixes it!
Hope I don't have to go through the process of rooting my phone again!!
s0litaire said:
Something strange has happened with my Desire HD
I've had CM7 installed and fine for a while, I tried to install the latest Nightlies i got an error about scripts not being able to run. Thought it was just a problem with the nightly and ignored it.
But since then i've noticed problems with other apps that require root privileges.
it seems like i've lost root access some how. it must have happen recently but I can't remember having problems with any apps, but the backup i made before I tried to install the nightly has the same problem.
Anyone had something like this happen before?
I've tried a factory reset but problem remains.
I'm going back to a backup I made 4 weeks ago and see if that fixes it!
Hope I don't have to go through the process of rooting my phone again!!
Click to expand...
Click to collapse
Have you updated your Recovery to one of the 5 releases? Seems to be reports of losing root when restoring backups on the Thunderbolt
check this link about the recovery issues
https://plus.google.com/103583939320326217147/posts/VSdhDWoA59Z
Thanks I was on recovery 5.0.1.0
Could not update to 5.0.2.0
But my older backup had an earlier version of recovery. Managed to update to 5.0.2.0
Things seem to be fine now...
*Whew* ^_^
s0litaire said:
Thanks I was on recovery 5.0.1.0
Could not update to 5.0.2.0
But my older backup had an earlier version of recovery. Managed to update to 5.0.2.0
Things seem to be fine now...
*Whew* ^_^
Click to expand...
Click to collapse
Pleased to hear you are sorted.
I think you can check if you have root by opening terminal (or adb shell ):
" ls -l /system/xbin/su "
If 'su' command have suid bit "-rwsr-sr-x) (4755) - then you still have root
Hello
Ive just installes taboonay 2.1. It was working great until i reboot. Then superuser didnt want to allow apps such a setcpu and other even if their superuser status are still authorised
please help
the infamous taboonay 2.1 root problem... I had the same problem and restored to 2.0... only I still don't have root back? I'm confused
The same here
I had the same issue with taboonay 2.0, i thought it would be solved with 2.1, but as far as i know it's a common issue with new version of ROMs taboonay and honeyvillain.
I think it's a SU problem in general. Maybe it needs an upgrade or a new binary.
I'm using honeyvillain 1.2 and i have SU problems when apps try to get SU permissions at boot only. If i open them, they get SU permission immediately.
Ive found this and it worked
I don't know whether my way is useful to you or not.
I flash the rom, reboot fail to get the root. Then re-flash the rom and flash beta4 superuser as they given. Also fail after reboot.
Then I think why I flash the HoneyVillain rom but never lose root. It is also a HC3.2 rom. So I decide to mod the beta4 superuser zip file. I replace the both su and superuser.apk with the same files extracted from HoneyVillain rom and signed it. I fully wipe and re-install the rom and flash the su_mod.zip that I made and wait it ran. Ok! went into system and It got the root, then power down and started it again. Cool! still got the root. Tested by root explorer and terminal(command :su root).
Modified superuser, use cwm to install and must re-flash the rom or you will fail.
<a href="http://forum.xda-developers.com/attachment.php?attachmentid=727150&d=1316661095" >su_mod.zip</a>
Sent from my A500 using Tapatalk
reinstalling su 3.0 beta 4 got root back for mein 2.0 but not 2.1... something being restored by titanium backup in 2.1 seems to be causing the problem but with 2 boys under 5yrs old destroying my house as I type, I don't have time to try to figure out what's causing the headaches... so 2.0 for now I guess
oh well i did replace the superuser and still fail.
Now trying something else.
So far ive been booting my iconia more than 5 times and yet im still rooted.
Its weird.
What's your new trial if you don't mind my asking?
I noticed that whenever i ran full apps restore from Titanium Backup, followed by a reboot..my root is gone.
So i did carefully restore my apps. Apps that uses root functions i didnt restore em. E.g SetCPU.
But before my final flashing, these was my steps
1. Wipe steps (data/cache/dalvik)
2.Flash Taboonay 2.1
3.Flash su-3.0-beta4-efgh (from androidsu.com/3-0-beta)
4.Flashed Thor Kernel 3.4 (from tegraowners.com/?p=1005)
I noticed thor kernel 3.5 is out but i havent tested that
Then when restoring, make sure u restore apps that doesnt use root functions.
Here im still playing/customizing/rebooting almost 10 times and still rooted..
Good luck.
and that is without restoring any root apps? Did you fresh install setcpu or anything yet?
yes i didnt restore any root apps nor system apps. just normal apps/games
Root apps that i fresh install and using right now are
Titanium Backup 4.2.1
RootExplorer
RootCheck (to see whether device still rooted or not plus double confirm using terminal *su root)
So far i dont see the need of installing SetCPU since you can O.C through tabootools.
Only profile i need for O.C is when my screenon/off.
Ill keep playing with taboonay 2.1 and see whether i'll get root issues again
thanks ill have to give that a try later... I wasn't sure how well tabootools handled thors crazy new steps
okay dont forget to let me know whether it succeed or not on root issues =]
im wondering if pimp my cpu has the same effect on this as setcpu?
uninstall setcpu, now it will root and su works fine. Use other oc utility.
uninstallng didn't help I had to rewipe and install the rom again and I'm using system tuner... I really miss setcpu though... of course root is more important
ah so i was right after all
I uninstalled set cpu, and now I'm using tabootools for oc. Also I saw there is a final version of SU v3 on the android market and i upgraded my su in my x8 and now everything is fine.
Sent from my E15a using xda premium
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