I've flashed CM9 with the glitch kernel, works perfectly. Only problem is that I have no root access. Already tried reflashing cm9 and the kernel multiple times after wiping and clearing everything but it al turns out the same, I still have no root access.
Can somebody please help me?
nicolas_cage said:
I've flashed CM9 with the glitch kernel, works perfectly. Only problem is that I have no root access. Already tried reflashing cm9 and the kernel multiple times after wiping and clearing everything but it al turns out the same, I still have no root access.
Can somebody please help me?
Click to expand...
Click to collapse
Have you installed Superuser?
Superuser came preinstalled with cm9.
I fixed it! If anyone encounters the same problem, basically what you have to do is flash back to an official firmware (I used froyo 2.2). Then start over from there. It's a hassle but at least it solves the problem.
Related
hi all,
Loving XDA.
I have updated to 2.3.3 then 2.3.4 using:
http://forum.xda-developers.com/showpost.php?p=13424911&postcount=19
I still have SU. all programs work EXCEPT any system menus i get FC. e.g. when trying to select USB Debugging or trying to change Wifi networks.. Any loading of these menus cause FC
http://i54.tinypic.com/2nlb57t.png
Can anyone help me?
Thanks in advance
-Ernie
any help available? sorry to bump
First thing I would try would be fix permissions (you can find this option in ROM manager) and if that doesn't work then I would just do a clean install.
I had the same problem, bad blocks and FC's. I spent hours trying everything I could to fix it. My phones been half busted for about 2 months. Someone suggested that I try this and it worked.
http://forum.xda-developers.com/showthread.php?t=717870
I didn't think it would but it did. It brought my phone back to stock 2.1. I grabbed z4root to root it, then reflashed hboot, radio and went back to CM7 nightly. All is well with the world again.
Good luck.
Hello,
I keep losing root after reboot, tried several kernels like Semaphore and CF-Root but after rebooting my phone i don't have root anymore, how can i fix this?
I have Faryaab deodexed JVS ROM
Thanks
if you keep losing root, I would suggest that you need to do a complete clean and then re-install.
Copy anything important onto your PC, do a Titanium backup of your apps and copy that to your PC then do a complete clean and reinstall either using stock firmware or use the cleanse option with Tornado (use google)
After you should flash first your kernel with root and a stock firmware to confirm the problem is no longer present and only then flash a custom rom. If you again lose root then you will know it is not the kernel at all but the rom that is the source of your problems. Only then install back your apps.
Thanks
Already solved the problem by wiping and installing Dark Core kernel but i think the wipe was not necessary.
Now i am just afraid of changing kernel because of losing root again, oh well
I keep loosing root even just after using Kingroot , which is the only rooting apk that seems to work on my SGH-i337Z 4.4.2 .
I run Kingroot and have root and I wanted to make a back up of it so when I install Skyfall ROM or another ROM I can restore to the back up if things go south or I just don't like the new ROM.
Right after doing the back up and I reboot . . . . . root is gone.
I have been searching the forum but have yet to find the reason why I loose root and or a " fix".
I can't seem to do back ups or reboot of any kind and still retain root.
Any ideas ?
Thanks,
Hey all,
I installed CM10 Helly Bean (DerTeufel) port for Captivate V10 with full wipe.
It seemed to be working fine... fooled around a bit, tried out Google Now, etc.
Was restoring apps (not data) w/ Titanium Backup.. forget if it had finished or not...
Didn't try to run any of these programs or anything, just tried to unlock and the touchscreen was not responsive... Tried wiping cache+dalvik + fixing permissions... tried reinstalling ROM and GAPPS...
All are in a non-responsive bootloop.
I'm starting over now with another factory wipe... as of now it is stuck on "Welcome" Screen and touchscreen is not responding... AND.. it just restarted
Any ideas as to the problem... Was it Titanium Backup related? Should I resist running that again (assuming this ever works)?
I would post this on Development thread but I still don't have my 10 posts, heh, mostly a long-time lurker...
Thanks!
Worse than I thought!
So It's worse than I thought... I gave up and re-flashed slim (ICS)... and the same problem still exists... boots up, looks normal, can't touch anything.... eventually it reboots....
Suggestions?
Would ODIN flash do anything different? I9000 bootloaders?
ScruffMcG said:
Hey all,
I installed CM10 Helly Bean (DerTeufel) port for Captivate V10 with full wipe.
It seemed to be working fine... fooled around a bit, tried out Google Now, etc.
Was restoring apps (not data) w/ Titanium Backup.. forget if it had finished or not...
Didn't try to run any of these programs or anything, just tried to unlock and the touchscreen was not responsive... Tried wiping cache+dalvik + fixing permissions... tried reinstalling ROM and GAPPS...
All are in a non-responsive bootloop.
I'm starting over now with another factory wipe... as of now it is stuck on "Welcome" Screen and touchscreen is not responding... AND.. it just restarted
Any ideas as to the problem... Was it Titanium Backup related? Should I resist running that again (assuming this ever works)?
I would post this on Development thread but I still don't have my 10 posts, heh, mostly a long-time lurker...
Thanks!
Click to expand...
Click to collapse
sorry I'm just going to post twice so I can post to development...
yeah... 10char
What I can suggest is, go back to GB. Download a one click Odin w/ bootloaders, you can search that in the dev forum. After that flash it with a corn kernel so you can have a working CWM. And then Go to recovery, have a full wipe (data,cache,dalvik) TWICE and flash this--
Slimmed Down V10 by cbalt
Wipe Data/Factory Reset/Wipe Dalvik
Flash http://www.mediafire.com/?9p212pempybwnj3
Then Flash http://www.mediafire.com/download.php?bdjabcmobz6aw6k
Then Fix Permissions
Then Reboot
Click to expand...
Click to collapse
I can recommend you that one because it's the one the I'm currently using right now and I can say that it's working like a charm.
The method above is the one I'm using everytime I flash a ROM. I always do a full wipe so I won't be encountering any issues or whatsoever.
About TiBu, I am not sure if that's where the issue coming from because I've been using TiBu for a long time and haven't encountered that. Just always remember, if you are using backup using TiBu, just backup the User Apps+Data, DO NOT INCLUDE THE SYSTEM APP. Goodluck!
So you think w/bootloaders will help?
I have flashed every odin w/o bootloaders that I have access too and all get me stuck at ATT bootscreen....
Little hesitant to reflash my bootloaders since I was/am already on GB bootloaders, but if it might help I may have to do it...
I actually was on that JB version (but with the normal gapps b/c I wanted google now...)... now I'm on no version of anything hahah
takeoutttt said:
What I can suggest is, go back to GB. Download a one click Odin w/ bootloaders, you can search that in the dev forum. After that flash it with a corn kernel so you can have a working CWM. And then Go to recovery, have a full wipe (data,cache,dalvik) TWICE and flash this--
I can recommend you that one because it's the one the I'm currently using right now and I can say that it's working like a charm.
The method above is the one I'm using everytime I flash a ROM. I always do a full wipe so I won't be encountering any issues or whatsoever.
About TiBu, I am not sure if that's where the issue coming from because I've been using TiBu for a long time and haven't encountered that. Just always remember, if you are using backup using TiBu, just backup the User Apps+Data, DO NOT INCLUDE THE SYSTEM APP. Goodluck!
Click to expand...
Click to collapse
I met a problem. I do not know wether or not it is common. The phone will reboot by itself sometimes.
Do you have the same problem?
same here
seems as though many of the problems experienced by one are shared by the other
this is logical as they share many common points including the same partition and both jellybean derivations
I was having issues... accelerometer and audio issues.
All came out right as rain after flashing back to stock and reflashing
ScruffMcG said:
yeah... 10char
Click to expand...
Click to collapse
All of a sudden S Memo has stopped working. I have already tried a few things like deleting app data and cache, uninstalling the app and restoring a backup, making S Memo a user app... So far nothing has helped. I know I could reflash the rom but since I use the app very seldomly reflashing the rom seems to me like shooting with canons at birds. Any ideas? By the way, S Note and editing screenshots taken by the S Pen method works just fine.
My rom is LRQ and the kernel is PhilZ 2.5. Rooted, busybox installed, CWM too. Could it be the kernel? No it is not the kernel, I just tried cf-root to no avail.
Sent from my Galaxy Note running ICS
altae said:
All of a sudden S Memo has stopped working. I have already tried a few things like deleting app data and cache, uninstalling the app and restoring a backup, making S Memo a user app... So far nothing has helped. I know I could reflash the rom but since I use the app very seldomly reflashing the rom seems to me like shooting with canons at birds. Any ideas? By the way, S Note and editing screenshots taken by the S Pen method works just fine.
My rom is LRQ and the kernel is PhilZ 2.5. Rooted, busybox installed, CWM too. Could it be the kernel? No it is not the kernel, I just tried cf-root to no avail.
Sent from my Galaxy Note running ICS
Click to expand...
Click to collapse
Hi there, if you uninstall the app then restore the backup, you are essentially just replacing the same app? If there was an issue with the app then its possible that there is an issue with the backup? It may be an idea to fully uninstall the app, but rather than restore it, get an apk (its easy to find) and install the apk using a File Manager. If the system persists then it could be a problem with the Samsung Apps. If this is the case, then a reflash may be the best option.
I hope this helps. Please hit Thanks if it did.
I gave up and just reflashed the rom. There was also another issue and I came to the decision that it would be the best to simply reflash the rom. Seems like Linux based os are no better than Windows when it comes to suddenly appearing issues that can only be solved by reinstalling the os
Sent from my Galaxy Note running ICS
altae said:
I gave up and just reflashed the rom. There was also another issue and I came to the decision that it would be the best to simply reflash the rom. Seems like Linux based os are no better than Windows when it comes to suddenly appearing issues that can only be solved by reinstalling the os
Sent from my Galaxy Note running ICS
Click to expand...
Click to collapse
yeah I wouldn't disagree with that. After flashing a new ROM, I tend to Fix Permissions in Advanced Recovery, it seems to resolve any potential FC issues before they occur. Glad it's sorted though.
Hi,
I wish to revert back to cm 7.2 from cm10. I wasn't able to find a conclusive thread which could help with the same. I tried wiping and flashing cm7.2 using CWM but later realized it only flashes update packages. Since cm10 is more updated, nothing happened except a format. Kindly help me with this. I am having lots of trouble with cm10 and its affecting my work
princegoyal88 said:
Hi,
I wish to revert back to cm 7.2 from cm10. I wasn't able to find a conclusive thread which could help with the same. I tried wiping and flashing cm7.2 using CWM but later realized it only flashes update packages. Since cm10 is more updated, nothing happened except a format. Kindly help me with this. I am having lots of trouble with cm10 and its affecting my work
Click to expand...
Click to collapse
I think the smartest way is get back to a stock GB rom using smartflash so you can root, mount a cwm and flash cm7.2 based on that old bootloader