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
Related
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.
Hope someone might be able to help.
Just got my vega and first thought was to root, backup rom and flash. Im used to doing iit with my desire so thought it would be easy!
so i,m using Visionary to root, first temp then perm. Run titamium backup that should root and backed up a couple of apps no problem. Installed rom back up v3. Back starts by reboot and then sits at android out of the box before i have to switch it off after 10 mins or so. I i still try and flash after this (or before if i miss this stage) with new rom, cant open apps or force close and wifi just says error.
Great device though
Thanks
bRim
Which rom are you trying to flash?
I use the built in applications backup, located in settings/software tool to backup apps, with no problems.
Ive tried the r8 version and one other and ive also used the app backup but wanted to get the whole rom done before a full flash.
On stock rom only Z4 rooted - .07p radio and .340
How can i get to the offical GB?
Also is there anything i can do to backup my apps and settings so i don't have to redownload and reset every app?
There are currently a ton of posts with these instructions. Search next time.
Anyways. Go to the following link and follow the 2 part instruction and it will work perfect and will still be rooted.
www.mydroidworld.com/forums/droid-x...-5-596-release-thread-something-everyone.html
Sent from my DROIDX using XDA App
Is there a method for people that don't have custom ROM managers, like Clockwork recovery? All I ever did was root my phone so I could run Titanium backup. I never installed Clockwork or any other custom ROM's... however, the 2.3 update is failing for me.
I am having the same problem. I defrosted all the apps and unrooted the phone but the update is still failing. Help!!!
version 2.3.340
BP_C_01.09.07P
www.google.com
I've become a fan of the Cyanogen Mod Nightlies, and have enjoyed the benefits of all the hard work the developers have been putting into the daily products. I did, however, encounter a problem that I've been unable to solve. Somewhere after installing 98, I noticed that certain apps where no longer recognizing my phone as being rooted. I downloaded root checker and it confirmed my suspisions. I still have superuser priviledges and programs such as Titanium still recognize my root, but others such as root uninstaller and others do not. I tried rolling back to my previous NAND backup, but didn't fix issue. Anyone else has experienced this issue? I know that several people posted similar comments after ROM 104, but haven't seen further comments. Any suggestions how to fix? I did run the SU. UPDATE.ZIP file as well as the unrevoked zip file and neither worked. Phone (EVO) currently running ROM 105. Thanks.
Jeff
I would first recommend running fix permission from rom manager/recovery. if that doesn't work, backup your apps via titanium, then do a fresh install of the rom.
Ok, will give it a shot.
Jeff
Sent from my PC36100 using XDA Premium App
Download superuser from the market it includes a fix for that issue.
I wasnt sure where or even if I should post this I normally use V.5 as a daily driver but I wanted to try the latest Hydracore OC kernel with latest JB Paranoid Rom. Everything was cool on ParaJB, as it has been in other test drives, except that I kept losing root whenever I flashed Hydracore, and I know thats been reported many times but I couldnt fix it and I started thinking that it might have something to do with the way the PreRooted gb roms are rooted. No idea but anyway heres what I did:
I wasnt sure if I should flash try to SuperSu .96 from CWR to regain root (I think that I should have) so I started over and downgraded to gb via PC Odin using a pre rooted GB rom. I booted, confirmed root then flashed JB Paranoid 2.1 from recovery, booted and updated superuser in market and updated to latest binary in app.
So I try Hydracore again now that I updated the binary confirmed root GB to JB, but I lost root again with HydraCore so I was thinking, based on what i had read, that I probably messed up with Superuser but letting the market update it every time and that I should have downloaded and updated the binary with SuperSu instead. I really dont know why I didnt do that in the first place but I do that carelessness can get you into trouble.
So I flash the pre rooted GB again in PC Odin but this time I get into a bootloop and I cant even boot recovery...soft bricked? Tried to flash it in PC Odin a few more times, its flashing fine wo errors but no change no loop, its just stuck on N7000 logo.
I went back into download mode and did the standard download a stock gb rom, hope 4 the best procedure. This time it got further, it actually played the music, which I took as an encouraging sign that stock recovery would work & it did (I was a little nervous but I worrry 2 much) so I wiped cache, factory reset and finally booted, finally.
I still have no idea what happened and I still have to re-upgrade but I don't anticipate any issues with that. I guess this time I will try to install SuperSu from market before I flash HydraCore and/or flash .96 via CWR afterward I lost root and then Triangle Away.
...I must have flashed a thousand Roms, (counting other devices) but I cant remember ever losing the ability to charge. Only now do I realize why it always says have at least 50% charge, you really dont want to try flashing wo a lot of juice.
OC version of hydracore is not stable for all Notes. Try to reflash everything from Odin, use Speedmod
Sent from my GT-N7000 using Tapatalk 2
TopOfNewYork said:
I wasnt sure where or even if I should post this I normally use V.5 as a daily driver but I wanted to try the latest Hydracore OC kernel with latest JB Paranoid Rom. Everything was cool on ParaJB, as it has been in other test drives, except that I kept losing root whenever I flashed Hydracore, and I know thats been reported many times but I couldnt fix it and I started thinking that it might have something to do with the way the PreRooted gb roms are rooted. No idea but anyway heres what I did:
I wasnt sure if I should flash try to SuperSu .96 from CWR to regain root (I think that I should have) so I started over and downgraded to gb via PC Odin using a pre rooted GB rom. I booted, confirmed root then flashed JB Paranoid 2.1 from recovery, booted and updated superuser in market and updated to latest binary in app.
So I try Hydracore again now that I updated the binary confirmed root GB to JB, but I lost root again with HydraCore so I was thinking, based on what i had read, that I probably messed up with Superuser but letting the market update it every time and that I should have downloaded and updated the binary with SuperSu instead. I really dont know why I didnt do that in the first place but I do that carelessness can get you into trouble.
So I flash the pre rooted GB again in PC Odin but this time I get into a bootloop and I cant even boot recovery...soft bricked? Tried to flash it in PC Odin a few more times, its flashing fine wo errors but no change no loop, its just stuck on N7000 logo.
I went back into download mode and did the standard download a stock gb rom, hope 4 the best procedure. This time it got further, it actually played the music, which I took as an encouraging sign that stock recovery would work & it did (I was a little nervous but I worrry 2 much) so I wiped cache, factory reset and finally booted, finally.
I still have no idea what happened and I still have to re-upgrade but I don't anticipate any issues with that. I guess this time I will try to install SuperSu from market before I flash HydraCore and/or flash .96 via CWR afterward I lost root and then Triangle Away.
...I must have flashed a thousand Roms, (counting other devices) but I cant remember ever losing the ability to charge. Only now do I realize why it always says have at least 50% charge, you really dont want to try flashing wo a lot of juice.
Click to expand...
Click to collapse
Well I am glad that your phone is back to life. In your post I can not see that you have made a full wipe between flashes (GB and the custom rom). Maybe a wipe cache and dalvik could have helped. As you were already told, Hydracore OC version is not for all devices and might behave ramdonly so try to flash the Standard version of it.
iam pretty sure that I got tge wipes right but yea it wasnt a huge deal just strange
You don't want to wipe after you replace supersu either BC then you will lose it right and it will cause some sort of binary issue, is that even possible?
So I am pretty sure it was in fact an issue w supersu vs superuser
BC I am now once again using hydracore 3.4 OC group B wo issue (and its GREAT btw i love it) on paranoid v.5 w full root rights retained...but i dont think i csn factoryvl reset now wo losing root unless I first tell superuser to update ot bibary and retake control of root from Supersu then uninstall Supersu, or something like that, I haven't experimented enough to know what's what
So if u want to flash hydracore u just have to update supersu after you flash paranoid and probably any other Rom thats includes Superuser
From what I have gathered, if you download and update the binary from with SuperSu it replaces super user (as there can only be one at a time) I've found, at least on paranoid rooms, that if before you switch kernels you need to let supersu become the primary root binary and then flash hydracore you will retain root rights...messing around with the wrong binaries or perhaps having 2 might have messed up things when I went back to pre rooted GB and couldnt boot recovery, so I had to go back to stock
Hopefully this helps somebody who might have similar issues
Sent from my GT-N7000