I was tryin to root my g1 succeeded. I was surfing around looking for the newest roms and discovered that I was using an old recovery image and needed the cm-recovery 1.4. So I tried to install the new one and it wouldn't respond. So after a while I decided to just unroot and start again since I had no trouble installing the first time. Now it won't install any image files. I tried using telnet like I did the first time but it won't connect to localhost. Tried using terminal and it says permission denined or something like that after the first command. Tried to do that 1-click root thing but it won't even install the apk file. It will download but not install. I need help please! I'm stuck with RC29 and I'm dying.
http://forum.xda-developers.com/showthread.php?t=442480
read it first, then read it again. then do it.
Permission denied = no root, no superuser access
Please reboot and telnetd again
One click root no = only works on crc1 which is the newest security patch
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
I downloaded the mistakenly flashed android 1.6 recovery image while trying to flash Cyanogen 4.1.999 . And I lost my root . Now I am unable to root my G1 by 1-click rooting process. When I run recovery Flasher, both the i am not able to backup the recovery image and install the new recovery image. Is there any way to root it.
I did a similar thing. You lost your recovery image, yes? I used downgrade-firmware method... DREAIMG.NBH+g1 root in a google search should get you started...or search the forums here sucks you got to start from scratch tho...there may be a way to downgrade to doughnut and try running the 1-click root app to restore a custom recovery image?
That means i need to downgrade to android 1.5 before being able to run Recovery Flasher.
Find a tutorial on the non 1 click root method and reflash a custom recovery image via the rc29 exploit...the power of google is in ur hands or at ur fingertips.
Look through the q&a's there is a pretty straight forward tutorial that gets you back to a rooted state.
you dont need to reroot your phone. look at the last few posts i made in the cyan 4.1.999 installation support thread in this section. it should get you where you need to go. if you need help, post there or pm me
Help me please, I was running eclair 2.1 with the JH7 update rooted and lag fixed. I removed the lag fix and the ext2 files because I wanted to flash to stock (JF6). Everything went well with the stock flash and the Odin master clear. I was preparing to root and then install rom manager to flash Cog 2.2.5.5 but now I cannot re-root my device. I am trying to do so using OCLF from the market, but I click root device and it tells me I need to reboot and click apply the update.zip file. I can no longer get into recovery with the button combos (even though before I Odin'd I could do so) and I also tried some programs from the market that claim to boot your device into recovery. I had previous success with these apps and they no longer work either. I am also unfamiliar with adb commands so someone PLEASE HELP thank you in advance. Hopefully its an easy fix.
Setting up the ADB is simple. Here's a video tutorial along with some great instructions on that. Unlockr
The command you will use to boot into recovery is "adb reboot recovery".
If you want to use TeamViewer I could set it up for you remotely.
Or skip rooting entirely by downloading the "Cognition v2.2 BETA5.5 Odin Flasher" version of Cognition.
Then, follow the instructions this person kindly left:
http://forum.xda-developers.com/showpost.php?p=8...534173&postcount=2277
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.
Hi, everyone.
I am trying to install a rom on a Samsung Captivate and having some, but not total, success.
I used the super one-click method to root, but I may have messed it up; I unplugged it too soon, when it appeared to hang pushing busybox.
However, when I rebooted the phone, it had superuser. I installed both ROM manager, one-click lag fix, and titanium backup from the market, and opened the applications. In all instances, I had no problem granting superuser permissions. In Titanium, it showed I needed to have usb debugging checked (which I had), and third-party applications (which I can't find in the menu).
However, when I ran ROM manager, I flashed Clockwork, and everything seemed to go all right, with no errors or warnings, but it won't actually boot into the Clockwork recovery. I can only get into the stock (blue) recovery, with a handful of options.
Fearful that I messed up the rooting by unplugging, I unrooted and then re-rooted. This time I didn't unplug anything, and it said it had success. The phone has a superuser app icon. It looks like superuser stuck around even after I wiped cache/data. I verified root via root checker, and it seems to be working correctly, and busy box is correctly installed. I installed ROM manager again and reran it and reflashed it, and it requested superuser, which I granted.
But then I reboot into recovery from ROM manager, and I'm pretty sure it's not clockwork. It's five options, all in blue.
I must be doing something wrong. Help, anyone?
Reinstall packages in normal recovery ... If you get an error saying signature verification failed, its because you're on froyo that has 3e recovery, search got 3e signature verification...
Also one click lag fix is pretty outdated and useless...
willentrekin said:
Hi, everyone.
I am trying to install a rom on a Samsung Captivate and having some, but not total, success.
I used the super one-click method to root, but I may have messed it up; I unplugged it too soon, when it appeared to hang pushing busybox.
However, when I rebooted the phone, it had superuser. I installed both ROM manager, one-click lag fix, and titanium backup from the market, and opened the applications. In all instances, I had no problem granting superuser permissions. In Titanium, it showed I needed to have usb debugging checked (which I had), and third-party applications (which I can't find in the menu).
However, when I ran ROM manager, I flashed Clockwork, and everything seemed to go all right, with no errors or warnings, but it won't actually boot into the Clockwork recovery. I can only get into the stock (blue) recovery, with a handful of options.
Fearful that I messed up the rooting by unplugging, I unrooted and then re-rooted. This time I didn't unplug anything, and it said it had success. The phone has a superuser app icon. It looks like superuser stuck around even after I wiped cache/data. I verified root via root checker, and it seems to be working correctly, and busy box is correctly installed. I installed ROM manager again and reran it and reflashed it, and it requested superuser, which I granted.
But then I reboot into recovery from ROM manager, and I'm pretty sure it's not clockwork. It's five options, all in blue.
I must be doing something wrong. Help, anyone?
Click to expand...
Click to collapse
Have you reinstalled package??
If you get signature failed after doing so - means u're on froyo 2.2 and you need 3e recovery fix. If not, u're on eclair 2.1 and flashing will be as easy as stealing from a baby
studacris said:
Reinstall packages in normal recovery ... If you get an error saying signature verification failed, its because you're on froyo that has 3e recovery, search got 3e signature verification...
Also one click lag fix is pretty outdated and useless...
Click to expand...
Click to collapse
OMG really?? you replied the same thing as I did I call JYNX!!
Beat ya! ;p
studacris said:
Reinstall packages in normal recovery ... If you get an error saying signature verification failed, its because you're on froyo that has 3e recovery, search got 3e signature verification...
Click to expand...
Click to collapse
That's exactly the error I'm getting. Searched it and working on it now. Will report back.
Also one click lag fix is pretty outdated and useless...
Click to expand...
Click to collapse
I figured so, but I was attempting to check root against all the sources I could, and I remembered there having been an 'unroot' option. But thanks for the confirmation. I figured it wasn't much use on a Captivate anyway.
Okay.
So I found two threads concerning the 3e recovery.
I tried the one here:
http://forum.xda-developers.com/showthread.php?t=833423
And it started okay but then failed to refind a temporary root and aborted. This was the second temporary root, though; the first time it checked, it was fine.
So I went here:
http://forum.xda-developers.com/showthread.php?t=909213
And extracted the file and downloaded Root Explorer, but my explorer only goes dev/block/delv. There's no other folder besides delv under block, so far as I can see. No st19.
Further help? Thanks so much in advance.
No, that instuction is to how to mount the system to r/w if using a terminal ... With root explorer that is a button on the top right so press that and move on to the next step and put the file in /system/bin. Reboot ... Bam!
studacris said:
No, that instuction is to how to mount the system to r/w if using a terminal ... With root explorer that is a button on the top right so press that and move on to the next step and put the file in /system/bin. Reboot ... Bam!
Click to expand...
Click to collapse
Okay. So, I moved the recovery file to my sdcard from my desktop, so it was on the phone. I ran root explorer, then first went into the sdcard to copy the file. After that, into system, then bin, which I mounted as r/w, and then pasted the recovery file there.
I got so excited I tried to do clockwork before rebooting. Now it gets to the update bit and seems about to work but sticks.
Do I need to wipe everything and retry? Just reboot?
reboot, you might want to paste the file in and reboot just for peace of mind ... also that downloaded update.zip with CWM could be bad, redownload it with rom mananger ... or take this one.
studacris said:
reboot, you might want to paste the file in and reboot just for peace of mind ... also that downloaded update.zip with CWM could be bad, redownload it with rom mananger ... or take this one.
Click to expand...
Click to collapse
Ha! Got it! It looked like it might bootloop for a second, and then it came up as stock recovery, and then I reinstalled packages and it came up with the green!
Wooo!
Thanks so much. Hopefully that'll be the last of the problems. Installing purplicious now. It looks like it's working.