After a failed attempt to flash Galaxian Kernel (got stuck in bootloops), I flashed back to the chainfire root kernel. After having booted my phone, all of my apps seem to have lost root access. Superuser is still there and it listed all of my apps with access. I told it to forget them all but that did not remedy the situation. So I think I may have lost root access. CWM works, although I tried reinstall super user via a zip update but that was also unsuccessful. CWM was unable to extract it. Reinstall from the market also did not help.
My question is, would the best way forward be for me to flash stock kernel and then reflash Chainfire to regain access root (all via odin)? Any risk associated with this?
Thanks for any help
go to recovery mode and use the option advanced-->fix permissions.. this should help u..;D
Thanks for the tip unfortunately it did not seem to fix the problem Wondering if busy box got broken or something.
hmmm then try this:
1. use lippol94's ultimate cleaning script( i attached it for u)
2. flash cf kernel
3. fix permissions.
this should fix the problem...
Hey,
Followed your instructions and the script executed successfully. Reflashed CF but still the same problem unfortunately! Not sure what's going on! Thank you though
Have you got busybox installed??? If not try to dl from market, install and reboot.
S.U.R.F.A.C.E 2.something
Just tried that but thought the kernel already included it. When I attempted to install it it said that root access was denied and it could not get access from superuser.
Maybe try terminal emulator and type su?
Or fugu root?
I'd probably just clash the kernel again though.
S.U.R.F.A.C.E 2.something
Tried the emulator. Permission denied.
Would Fugu require me to flash back to stock?
I have reflashed cf twice now, no luck. Maybe reflashing back to stock Kernel (I don't have to do pda/modem files right?) would work.
Just flash kernel as pda.
S.U.R.F.A.C.E 2.something
Cheers for all the help. In the end, nothing worked. Repartitioning and reflashing stock ended up doing the trick.
Thanks again
Related
I am in the UK. I wanted to root my G1 so I did the 1Click Root method. I had no problem at all except that I didn't get internal root only the external root needed for updating the Rom.
When I updated my Recovery with Rav.1.2.0g it gave me an excellent menu (that also helps with SD Partition) that was overwritten. I again updated the revovery wit Rav.1.2.1g and that to has been over written with the standard recovery. Perhaps I should have wiped first?
A few points that might help. I used quick format and the Dreaimg was not high case and there was no problem. The main problem I see is finding an RC7 or RC29 image that is not corrupted possibly during download.
I am unable to run apps that require root so how do I now get internal root. I am happy to go through the 1Click method as it is so good and easy.
Isn't Ra's recovery image for Magic 32A's? If so, you need to 1-click root again and keep your Cyanogen 1.4 recovery image, as that's what gives you good root.
Please this in the correct area(Q&A).
prettyboy85712 said:
Please this in the correct area(Q&A).
Click to expand...
Click to collapse
Moved to Q&A
Ra's recovery does work on the g1, I believe it is meant for the 32b's like the mytouch. Anyways....did you flash to a custom rom, if not than the stock update or roms will cause you to lose root by putting the security back on and rewriting the stock recovery. If you are on a modded rom, you should have superuser, to check if you have root go into terminal and type su, if it says permission denied than you don't have root, if you get a # than you do
Permission Denied
gridlock32404 said:
Ra's recovery does work on the g1, I believe it is meant for the 32b's like the mytouch. Anyways....did you flash to a custom rom, if not than the stock update or roms will cause you to lose root by putting the security back on and rewriting the stock recovery. If you are on a modded rom, you should have superuser, to check if you have root go into terminal and type su, if it says permission denied than you don't have root, if you get a # than you do
Click to expand...
Click to collapse
As I recall after doing the 1Click method I did check su and its was permission denied. That was why I did not update the Rom until I found out more about internal and external root. I did try the SuperUser app but it would not work on a non rooted G1.
As for the Rav Recovery image. Part of the unlockr 1Click states to ignore the recovery image supplied and use the Rav one as it is compatable with future updates.
My problem now then is how to back up what is on the phone?
Follow the guide in my sig for one click root ,if you have a g1/dream.
I have never used the one click but what what I hear, it does somehow overwrite the security so after you use it than go right into recovery and flash a custom rom right than and there or you will lose root<just my understanding from what I read and what I do know already> so reuse the recovery flasher again, make sure you got a rom ready to go and give it another shot, I would keep cyan's recovery or al least put it back on after you use ra's just so you have a terminal to cover your ass
ClockworkMod: An error occurred while attempting to run privileged commands.
i've tried everything...that i know of or have read of so far...
i just cant get cwm to install
d1 rooted and unrooted thru super one click and z4root, rom manager uninstalled and redownloaded and reinstalled, wifi connected or 3g
su is current and shows list of other apps, tried permisions fix in rom manager too, just stuck w/ that same lousy error and cant install any roms...
some one please help me!!
-n
nutiket95 said:
ClockworkMod: An error occurred while attempting to run privileged commands.
i've tried everything...that i know of or have read of so far...
i just cant get cwm to install
d1 rooted and unrooted thru super one click and z4root, rom manager uninstalled and redownloaded and reinstalled, wifi connected or 3g
su is current and shows list of other apps, tried permisions fix in rom manager too, just stuck w/ that same lousy error and cant install any roms...
some one please help me!!
-n
Click to expand...
Click to collapse
You prolly fixed this already but in case someone else has this issue. Try installing Busybox from the market.
Same issue and won't boot into clockworkmod recovery
nutiket95 said:
ClockworkMod: An error occurred while attempting to run privileged commands.
i've tried everything...that i know of or have read of so far...
i just cant get cwm to install
d1 rooted and unrooted thru super one click and z4root, rom manager uninstalled and redownloaded and reinstalled, wifi connected or 3g
su is current and shows list of other apps, tried permisions fix in rom manager too, just stuck w/ that same lousy error and cant install any roms...
some one please help me!!
-n
Click to expand...
Click to collapse
I rooted my phone with eclair installed and used clockworkmod recovery with no issues until I one day wanted to go back to stock and attempted a restore of the backup I made right before flashing the OverStock ROM. The phone wouldn't boot, so finally got the Overstock to go back. Phone worked fine for the most part, but from then on to get into recovery mode, required shutting down and using button presses (Up/down vol/PWR button) and it would go in fine. Could never get Clockworkmod to go into recovery mode with a click. Saw that (finally) Samsung has published a Froyo update, so took back to stock eclair using ODIN3 so I could use Kies mini to update. Did a factory reset to remove all old info directories and data. Update went perfect, but want the option to use the rooted apps (Titanium backup and ClockworkMod--purchased apps) to play with my phone as I see fit. Used SuperOneClick to root phone and verified I can get superuser with using terminal emulator, successfully executing "su" command. Problem is I can't get into CWM recovery. Only get "Android system recovery <3e>". Tried uninstalling CWM and reinstalling. Re-Flashed CWM recovery and it lists version 2.5.1.2 as current and latest.
I obviously need CWM recovery to flash different ROMS, but wanted a current backup before starting. Can't get any further until I figure this out. Any help would be appreciated. I was a noob, just a month ago, but was feeling pretty confident until this happened. Guess I'm still a noob, but just a little more dangerous now. Thanks in advance.
Just noticed that I wasn't in a phone specific thread, so here's my phone details... Samsung Vibrant (T-Mobile).
CWM issues with Milestone
In the last update of the RomManager was added support for version ClockWorkMod 3.x for Milestone - but still unable to use the CWM as standard recovery.
Using another recovery as OR1.4 you can start CMW from the SD card - but that does not solve the problem of RomManager stay with completely limited functions.
The Rom Manager is having updates constantly and I think we have a working version for Milestone soon - but in part I'm upset to see that the Milestone is listed as a supported device - when in fact it is not.
I bought the full version of Rom Manager because I believe it is a great tool and I hope someday I can use all its functions.
I have the same problem. I use OpenRecovery for Sholes to do those things. I hope we can use those tools like a normal user even a day.
so I have the exact problem like the guy in thread
http://forum.xda-developers.com/showthread.php?t=1305953&highlight=convert+rfs+to+ext4
now, I lost my root capability too, how to fix everything up? I am at semaphore kernel btw, tried reflash semaphore kernel, failed, what should I do now? flash XXJVT using odin again? or?
The guy in that thread fixed the issue by making more space in /system. Now if you lost root it will not be possible for you to do that. If you tried reflashing kernel and it didn´t work, then flashing stock JVT may be the solution.
thanks for the tips!! is that the only way? it is possible to flash to other kernel? such as galaxian? is it safe?
edit: and that guy lost his root too, how do he fix is in the end?
You can try to flash other kernel, like Galaxian, and later with Titanium backup, delete useless system apps like allshare, aldyko, to empty space in /system and then move to ext4. Anyway I think it is better to start from scratch, clean flash stock JVT, flash a kernel to have root and CWM, and then (you will be bloatware-free) move to ext4.
I've already flashed a kernel from Chainfire>>>http://forum.xda-developers.com/showthread.php?t=788108
still, in About Phone, the kernel changes, but still there is no root permission, will try galaxian now and see how
not working too, will flash xxjvt now using odin
Artest113 said:
not working too, will flash xxjvt now using odin
Click to expand...
Click to collapse
OK, everything should go fine now.
Facing big problem:
- Over a stock phone: flashed SGN_XX_OXA_KJI using PC odin.
- Flashed CF root kernal + CWM using BAT file. (KJ1)
- Phone was rooted and CWM installed.
- When it says flash CF kernel by placing on SD card, it think i did a mistake and using mobile odin I flashed KJ1 kernel again (I dont know which kernel to be flashed and where to get that).
- Seemingly phone got bricked and wont boot.
Somehow I managed to access the download mode.
- Flashed stock firmware GTN-7000_CPW_Blah
- Phone came back to life
- flashed SGN_XX_OXA_KJI using PC odin again
- Flashed CF root kernal + CWM using BAT file. (KJ1)
- Phone was rooted and CWM installed.
- Straightaway rebooted to CWM, did a full wipe and installed ICS stunner 1.4.19
- Phone booted.
Now the problems:
- Can't access root. No mobile odin, no CWM.
- Can't copy files to int/ext card. Phone hangs/PC hangs.
- Am able to access the download mode though.
- Please help. In case someone from India can share his phone number with me and guide me how to come out of this.
rockstar1630 said:
Facing big problem:
- Over a stock phone: flashed SGN_XX_OXA_KJI using PC odin.
- Flashed CF root kernal + CWM using BAT file. (KJ1)
- Phone was rooted and CWM installed.
- When it says flash CF kernel by placing on SD card, it think i did a mistake and using mobile odin I flashed KJ1 kernel again (I dont know which kernel to be flashed and where to get that).
- Seemingly phone got bricked and wont boot.
Somehow I managed to access the download mode.
- Flashed stock firmware GTN-7000_CPW_Blah
- Phone came back to life
- flashed SGN_XX_OXA_KJI using PC odin again
- Flashed CF root kernal + CWM using BAT file. (KJ1)
- Phone was rooted and CWM installed.
- Straightaway rebooted to CWM, did a full wipe and installed ICS stunner 1.4.19
- Phone booted.
Now the problems:
- Can't access root. No mobile odin, no CWM.
- Can't copy files to int/ext card. Phone hangs/PC hangs.
- Am able to access the download mode though.
- Please help. In case someone from India can share his phone number with me and guide me how to come out of this.
Click to expand...
Click to collapse
Follow this to the dot !!
http://forum.xda-developers.com/showthread.php?t=1614443
Flashed rooted stock odex GB
Now root checkers are confirming that phone is rooted
But can't copy any file in system folder
shall i go ahead and patch the abyss kernel?
Edit:
Was able to copy files in system folder using x explorer after granting r/w rights to the system folder.
Shall I proceed ahead to patch abyss kernel.
abyss kernel patched successfully with CWM. Installed latest stunner. But cant get tablet functionality. :-(
Please help.
Never ever ever ever trust root checkers. The only way to know for sure if you really have root access is to try and paste a file into /system folder. If you can do it, you have root. If you cannot, you have no root, it's as simple as that.
This means that you never had GB root in the first place, hence you ICS root problems.
chasmodo said:
Never ever ever ever trust root checkers. The only way to know for sure if you really have root access is to try and paste a file into /system folder. If you can do it, you have root. If you cannot, you have no root, it's as simple as that.
This means that you never had GB root in the first place, hence you ICS root problems.
Click to expand...
Click to collapse
...totally agree...that is one of my first mistake flashing the first cooked rom
giogroove said:
...totally agree...that is one of my first mistake flashing the first cooked rom
Click to expand...
Click to collapse
I was able to copy paste in system folder in gb after granting rw permission. Now in pics able to do the same. Anyways can someone summarize the entire steps that I should take from scratch that will bring the desired functionality. Do post the file links along. I ll really appreciate.
So I've rooted my Z3c using dual recovery method, and later on flashed the Rectify mod, and everything seemed to be working well until I wanted to flash a file in recovery (I know I had CWM working at one point) but it is not working. I found the little NDR tool in the Rectify mod and tired the various recovery options (previously I would just use up on volume key). Well this is when I started noticing it not working and so I tried the manual volume key approach and still it is not working. I installed busy box and have found that can sometimes cause problems with NDR/Recovery however I attempted to uninstall was going to try different location but that's broken now too... I think.
So anyway, my problem is, if I re-install DualRecovery it still does not go to recovery.
Please help me get to Recovery mode so I can reflash rom.
Thank You
Have you installed a different busybox, most others aren't compatible with XZDR and will cause this kind of issue.
I'll tell you what I did, I downgraded firmware using flashtool, followed the dualboot method to upgrade while re-rooting and confirming recovery along the way (this seems to work) then as soon as I install rectify (making sure to flash dualboot flashable zip file before reboot) I'm no longer able to access recovery, not manually or using NDR. I also didn't intall busybox yet.
Oh boy what now, I'm back to square one.
I'm an idiot, what's the rectify mod? Point me to a download link and I'll see if there's something in it that's causing issues with XZDR.
Edit : I see its rectify rom. Well it most likely includes it's own version of busybox, hence the issue.