I tried to root my Droid 1 (2.2.1 FR83d) with super one click. Everything seemed to work. I got super user access, TI backup runs (mostly)
From Rom manager I installed Clockwork it said everything work but no recovery mode access (yellow triangle) After reading up here it was suggested to flash SPrecovery and then back to clockwork so I did that bot SP and clock work appeared to run fine but still no recovery mode.
Setcpu seems to be working superuser is working but I cannot make a backup of the phone (nand, ROM manager recovery both fail) TI can't uninstall factory apps, and dose not make a complete backup just apps and restores dose not do a complete restore.
It seems I have half a rooted phone. Any ideas on how to fix this?
Related
Ok, so I rooted my wife's phone using this guide:
http://forum.xda-developers.com/showthread.php?t=583291
I seem to have gained root, however, I am getting this error when trying to use Titanium Backup:
BusyBox works but the 'su' command does not elevate to root....whoami...
I installed BusyBox through Titanium and through the market. I also installed Superuser through the market. Not sure where my error is/was, or how to fix it, does anyone have any ideas?
Everything went fine until the end, it did not reboot into recovery, but rebooted normally. I was able to get to recovery by powering on while holding the home button and was able to create a nandroid backup, so no problems there.
I'd like to be able to backup all of her apps before flashing a new ROM, but can't do so with Titanium before I figure out this error.
Will the issues above cause me any problems if I flash a 2.1 ROM, or will I be good to go, aside from having to re-install all of her apps?
Thanks.
So I had alot of issues rooting but im finally in, all rooted. Downloaded ROM Manager from the market and installed CWM. Says its successful, but when I manually reboot into CWM i get a error, so I cant install the 1.1 fix
Any ideas?
Really no one knows? This sucks!
This normally happens when recovery is not flashed properly. Did you try flashing again via Rom Manager? Also when you flash, does the screen show something like "Rom Manager has been granted super user permissions"?
ya, it flashes successfully through rom manager....
I think the problem is when I was trying to go back to 1.0.1 I flashed a restore through CWM. Then I whiped the /system and /data folders. The directions said to do this but I didnt realize I was supposed to do this BEFORE flashing not after. Basically I had no restore partition left so when I went and let it fail to boot 8x i got a error, and i had no OS. I ended up doing the N/Pwr, it restored, then i got a bootable CWM, booted into it and flashed the 1.0.1. But not everything seems, odd.
I can go into Rom Manager and install CWM fine, it says installation successful. But if I reboot into recovery, I get the error. I really need this fixed but im thinking it may be easier to just use a bootable CWM. Any ideas? I need to get 1.1 on here before I lose root
DroidHam said:
I think the problem is when I was trying to go back to 1.0.1 I flashed a restore through CWM. Then I whiped the /system and /data folders. The directions said to do this but I didnt realize I was supposed to do this BEFORE flashing not after. Basically I had no restore partition left so when I went and let it fail to boot 8x i got a error, and i had no OS. I ended up doing the N/Pwr, it restored, then i got a bootable CWM, booted into it and flashed the 1.0.1. But not everything seems, odd.
I can go into Rom Manager and install CWM fine, it says installation successful. But if I reboot into recovery, I get the error. I really need this fixed but im thinking it may be easier to just use a bootable CWM. Any ideas? I need to get 1.1 on here before I lose root
Click to expand...
Click to collapse
I fixed this by downloading the latest busybox from the market, installed it, then ran the "fix permissions" from Rom Manager. I then reinstalled the latest CWM, and it would allow me to reboot into recovery.
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.
I recently installed a custom ROM (liquid Gingerbread v3.0) onto my Droid 1. But in doing so I lost my root access, and now i can't use ROM Manager to either restore my backups or switch to a different ROM. Some apps say it appears that I have root access but none of the root apps work. I tried using super one click to "unroot" but that froze during step #6. I also tried using it to root and that also froze during step 6. I should also note that the power button on my phone is broke, thus preventing me from booting into recovery mode. What can I do????
I found a way to get into recovery, is there an easy way just to restore stock?
chazm128 said:
I found a way to get into recovery, is there an easy way just to restore stock?
Click to expand...
Click to collapse
Back up and restore. Restore a backup
Sent from my Revolting Revolution. Powered my mtmichaelson.
There's a chance that you may have accidentally denied root access. You could have opened the Superuser app that should have been included with your ROM to ensure that SU requests weren't being blocked that way.
Also, when in doubt learn to use Recovery mode manually. You can't always trust ROM Manager to do everything for you. Sounds like it's best to manually wipe everything you can and install the ROM fresh.
Hi!! I'm new at the forum, I've looking for information and didn't find anything related. I hope this is the
apropiate section
I've a Galaxy Ace with Froyo, so I rooted it with SuperOneClick without any problems. Then I reeboted in stock
recovery and installed a .zip for ClockWorkMod recovery. Afterwards I couldn't boot into any recovery, but the
pone still worked. So I installed Titanium, made a backup, etcetera; everything worked perfectly. I've tried
to reboot into recovery with an app called CWM (same icon as ROM manager). Just opened it and press "Reboot into
recovery". Now the phone is not working. I can enter download mode (yellow letters saynd "Downloading...") but
Odin stucks in Setting Connection (same simpthoms of ROM manager). I hope you have a solution.
Thanks!!