My phone is rooted, but I'm still getting the error when trying to flash the ClockworkMod Recovery through ROM Manager
'An error occurred while flashing your recovery'
I originally had an older Clockwork Recovery loaded which I think was one of the reasons it had problems. I tried to use the program to flash to RA Recovery 1.7.0.1 and then back to the latest ClockworkMod, but it wont work.
I located the latest ZIP file for the recovery
recovery-clockwork-2.5.0.1-supersonic.zip
I had the RA-evo-v1.7.0.1 recovery loaded, tried to install the Clockwork zip through recovery mode. Originally it loads up fine, but then when I reboot, it reverts back to the RA-evo recovery. I'm still receiving the same error in ROM Manager as it is forcing me to select the option to Flash the Recovery.
Any help would be great. I apologize if this has already been covered in another thread. I found some people that had issues, but not the exact one I am having.
~J
Sounds like to me that Rom manager is not getting superuser permission. Flash Su 2.1.zip or if u are using frozen eclair with jit. U need to flash 2.2 Su.zip. Has happened to me before.
Sent from my PC36100 while waiting for grout to dry using XDA App
pongoface said:
Sounds like to me that Rom manager is not getting superuser permission. Flash Su 2.1.zip or if u are using frozen eclair with jit. U need to flash 2.2 Su.zip. Has happened to me before.
Sent from my PC36100 while waiting for grout to dry using XDA App
Click to expand...
Click to collapse
When I go to the Superuser Permissions app, BusyBox and Titanium Backup both are shown, but Rom Manager isn't there. Should it be?
I'm still a newbie, so I'm not familiar with SU 2.1.zip, is that a superuser file to install I would assume?
I haven't had an issue with anything else except Rom Manager which is odd. I'm using the free version currently if that matters at all. I wanted to get this working with the free one first, and then if it goes well I was going to donate and get the full version.
~J
Connect to a wifi and try again. That was an issue
for me the other day.
WiFi did it for me..
The above WiFi comment was right in my instance. I kept getting the error message until I enabled WiFi, then it went thru perfectly.
(Strange though...I don't know why that would affect it?)
Just wanted to add that wifi worked for me too. I don't get it either, but I'm happy.
Glad I found this, wifi worked. Strange
Sounds like a server side issue of some kind for which you would have had no control over.
Related
ok so I rooted my g2/vision/whatever you wanna call it.
Went a little rocky on the root, for some reason after the first perma root reboot, I was unrooted. Rebooted again and now have perma root for realz! and my bff becky was lyk omgz.
Ok now serious business time.
I installed clockwork rom manager (2.5.1.2) so I can make a backup before I go do some fun stuff, but here's my issue, everytime I try to reboot into recovery, I get the default recovery screen. When I try to do a backup, I get the default recovery screen. It does nothing but show an icon of my device with the "!" on it.
I've dealt with the clockwork recovery on my g1 before but it always worked no problemo. Dunno if something went wrong or I'm being a noob deluxe. Any input to aid in my troubles is much appreciated.
Just gonna throw this out did u flash recovery after installing Rom manager ?
Sent from my HTC Vision using XDA App
i used the option in clockwork rom manager to flash it. Says current recovery is 2.5.1.2. Latest recovery is 2.5.1.2.
Might as well try it again. I haven't tried the manual method yet though.
EDIT : ROFL, I tried it again just now and I'm looking at the clockwork recovery console. Wow... my phone requires me to do everything twice apparently...
Thanks for the speedy response though T.C.P
New question, how do I get this thread deleted/closed?
Don't worry, I had to do the exact same thing you did.
Root twice.
Flash Clockwork twice.
I believe it's a known issue.
At least that's all we had to do!
kind of a weird issue to have really... wonder how that might affect some mods down the line
please remember, the nand backup could be buggy or corrupted sometimes, backup and restore if you need to, just so you could check if the backup is working
Edit : Nevermind ....
Is anyone else getting the below error when trying to Flash ClockworkMod Recovery on 2.5.1.3? I just updated and this is the error I am getting:
Error while downloading from server. Please make sure that you have a stable internet connection, and that your SD card is inserted and has free space!
Working onwifi, stock rooted via gfree method. Only think I found with search is someone who had this problem disappear after a few hours and his thoughts were a server error with the clockwork servers.
Anyone?
I'm also extremely frustrated with this issue
Mine didn't change even when I connected via wifi
Sent from my T-Mobile G2 using XDA App
Look at here,some users have the same problem.
http://forum.xda-developers.com/showthread.php?p=9869771#post9869771
I`m also getting errors,can`t install the new 2.5.1.8 Recovery!
I am having this problem. I just got a replacement Droid 1 and obtained root through Soup and Root. I can't restore a backup through ROM Manager, I can't do much of anything through ROM Manager. It says I have the current CW as I am using my same SD card from before, but I can't download/ install a new ROM, restore one, or anything. When I tried to flash CW to see if that was the problem I get the same error. I have internet connectivity and my phone is working fine other than that.
I have been going CRAZY over this! I just upgraded my captivate to 2.2 today, rooted it and now I've LITTERALLY been trying to install clockworkmod for the past 3 hours, I have bricked my phone so many times and had to restore back to the default froyo and re-rooted it so many times and I keep getting the same error.
I've been trying to find the clockworkmod manually so I can just install it without ROM Manager, anybody have any clue how I can do this? I have a samsung captivate.
Also, I paid for the Premium version of ROM Manager via PayPal however I have no idea how to "reinstall" the Premium version without re-paying the $3.99, anybody know how?
Ganii said:
I`m also getting errors,can`t install the new 2.5.1.8 Recovery!
Click to expand...
Click to collapse
There is no 2.5.1.8 recovery for Vision, it's a bug in ROM Manager where it shows you versions that are available for all phones.
Yes,now saw your answer at development section
2.5.1.4 also not working,only 2.5.1.3 available at the moment!
Not working for my buddy and I either. Must be a server issue . I have 2.5.1.3
2.5.1.3 is the newest at the moment!
Seems to be back online today...
There have been a few updates to the ROM Manager app overnight to fix some of these issues, try updating via the Market if you've had problems.
Still the same version of Clockwork Recovery for Vision so far though.
Rom Manager doesn't seem to know that I've got CWM installed. When I rooted and installed CWM I didn't do it through Rom Manager originally. Now CWM won't let me use it to manage my backups and keeps asking me if I want to install CWM? I've got Google Wallet installed so I'm a little nervous flashing things needlessly.
Any suggestions?
Thanks
edit: CWM v5.5.0.4
do you try "wipe cache" and "advanced->wipe dalvik cache?"
Thanks, I just tried, it took quite a while to clear the cache. When I booted up it went through a whole Optimizing Apps process, I'm not sure if that was due to wiping the dalvik cache? But it still didn't fix the Rom Manager issue.
Its probably not yet compatible if you have the touch version of cwm installed, so it wants to flash the standard one. Or you could always just let rom manager just reflash cwm overtop and then you may be good to go.
EvanVanVan said:
Rom Manager doesn't seem to know that I've got CWM installed. When I rooted and installed CWM I didn't do it through Rom Manager originally. Now CWM won't let me use it to manage my backups and keeps asking me if I want to install CWM? I've got Google Wallet installed so I'm a little nervous flashing things needlessly.
Any suggestions?
Thanks
Click to expand...
Click to collapse
Maybe it can't detect it? I know we had to set which CWM version we had installed on the SGS.
Maybe try to run the install?
Sent from my Galaxy Nexus using Tapatalk
I don't have the touch version installed (doesn't seem to be the touch version anyway). I should have said this in the first post but it CWM v5.5.0.4.
Herman76 said:
Maybe it can't detect it? I know we had to set which CWM version we had installed on the SGS.
Maybe try to run the install?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Flashing CWM over CWM shouldn't wipe my phone right? It's only the stock bootloader that requires a full wipe?
I installed ROM manager and then CWM via ROM manager last night and its CWM v5.5.0.2 which ROM manager thinks is the latest: perhaps it can't deal with 5.5.0.4 yet...
Clancy_s said:
I installed ROM manager and then CWM via ROM manager last night and its CWM v5.5.0.2 which ROM manager thinks is the latest: perhaps it can't deal with 5.5.0.4 yet...
Click to expand...
Click to collapse
ah, that would probably do it...guess i'll just wait it out a little longer, thanks
I have the exact same issue as this Rom Manager refuses to see I have CWM installed so just keeps telling me I need to install it it also can't download and flash its own version and just freezes after download
So any updates on this or more users experiencing it ?
I think I've found the solution. In ROM Manager tap the menu button at the top and then tap Manual Flash Override. Next it'll ask you if you've flashed CWM manually so tap OK because that's what we've done. Next pick which GN you have and then choose CWM 3.x+. There you have it, it should work now.
Don't use ROM Manager - problem solved!!
Seriously, though, it's a TERRIBLE piece of software
I'm fairly new to using it but it seems decent, why is it so terrible? I had an eris before this and did everything manually through recovery, this seems like it's a lot better than that.
It's just more trouble than it's worth. Why not just manually flash CWM using fastboot and get your head around that as opposed to an app which can - frankly - break things?
Flashing it via fastboot is what causes the above issue. Since you flash it manually rom manager can't see it, that's why I posted the above steps to kind of "force" rom manager to see the manually installed version.
But if you're not using ROM Manager then what's the issue? Copy ROM to SD card, reboot to recovery, flash ROM...where is ROM Manager needed in that equation?
If you're not using it then there is no issue, but this thread isn't about using it or not, it's about getting it to work with the galaxy nexus when you manually flash CWM.
I like it for the backup and restore feature and being able to change the names used to backup
So I used odin to flash the official stock jelllybean rom then I used the Samsung toolkit to flash clockwork mod recovery and root. To root it said to flash a superuser zip in recovery. I did.after I reboot everything is working fine. Apps gain root access the promp pops up but after a few minutes it didn't anymore and I cant open busybox or setcpu because it cant gain access but the apps I already granted can. I updated su binary and it fails on gaining root access.
This happens with both super su and superuser. I also tried starting again by oding rom and rooting again. No luck. Please help
Sent from my SGH-T999 using xda premium
Sent from my SGH-T999 using xda premium
Ok, you can try a few things.
First since you have Root Explorer already granted, go into /system/xbin and make sure that there is a file named su. If not, then go into /system/bin and see if it is there. Follow this: If it is in /system/bin, copy it and put it in /system/xbin, check permissions and reboot. Then try an un-granted app and see if that works. Pay attention to the bin and xbin parts here ok.!?
^^^Edit: While you are in /system/xbin make sure that busybox is there also. Just to be sure it installed properly.
Second. If the above didn't work, the go to the market and ChainsDD used to have an app called SuperUser Updated Fixer or something like that. I remember a long time ago, I was having some trouble updating the binaries (as were tons of other people) and he came out with that handy little app. I have been using it since (whenever I have a ROM that uses SuperUser.apk).
Third: I literally just read over in mrRobinson's thread that ICS likes SuperUser, while JB likes SuperSU. Might be something to look into. Maybe swapping out the two apps, might alleviate the issue.
I tried swapping out to super su but was having the same problem. Instead of trying the root explorer method you posted I thought I would go ahead and clean install yet another time. I just wanted the update and root access to work no errors. So here's what I did to fix it and it worked however there's another problem now.
I factory reset, wiped caches
flashed jb stock firmware (instead of the stock fw i now flashed mr.robinsons prerooted firmware)
rebooted checked and saw super su was working fine with my apps.
flashed clockwork mod recovery
made a nandroid backup
flashed wildchilds stock deodexed jb rom (i needed a deodexed rom thats why i flashed this otherwise i would of just kept stock)
booted up and in the play store theres an update for Super Su however i cant update it, it gives me an error.
error retrieving information from server. cant download.tried wifi on off, mobile data on off, clearing google play data and cache. no luck. restored nandroid and there was no update so i clicked reinstall from playstore in su and when i went to go download it, it gave the same error.
So my previous problem is fixed and i dont seem to be losing root anymore but now I cant update SU anymore.
Never mind I seemed to have linked the two issues just because 1 happened before the other, but that might not be the case.
The Google play error is now happening with other apps that i try to update as well.
Is this happening to you guys too?
sometimes when i power off my phone it doesnt boot anymore it gets stuck on boot loop. for example all i did was fix permissions in cwm and it got stuck on boot loop.
Did you Odin root66?
Yeah I odined the root 66 fw by Robinson. That has fixed losing root. Super user is working fine. The only remaining problem is that I get into a boot loop sometimes when I restart for some reason like when I fix permissions.
Sent from my SGH-T999 using xda premium
Hi guys, I made a mistake while playing with Smelkus (Ra-supersonic-v4.3-smelkusMOD).
While in recovery, I went into the Developer Menu and entered on the "Install eng (unguarded) su" option, which after rebooting, disabled root access from my EVO. Now, every time I try to get root access I get a segmentation fault error.
I'm using MazWoz 4.2.1 Jelly Bean B4.
Short of re-flashing the ROM, Is there anything I can do to regain root access? I really got it working the way I want it, so I don't want to wipe everything if I can avoid it.
Thanks! Oh, by the way, I made no back up ...(I know, my mistake).
Have done the same thing trying to get SU to work properly with a rom. Easiest way is just to restore a nandroid backup.
Edit: Sorry, earlier it was in the dev section.
connman said:
Have done the same thing trying to get SU to work properly with a rom. Easiest way is just to restore a nandroid backup.
Click to expand...
Click to collapse
Unfortunately, I did not make a nandroid backup for this ROM (been using it for only 2 days!).
Anyway, here's what I did so far:
1)I "Pushed" the Superuser.apk found on the MozWoz Rom to my EVO using "adb."
And it did not work. The superuser application installed properly on my device because I can launch it fine from the app drawer, but it does not give me root privileges.
Any other suggestions?
There's gotta be a way to solving this. Exactly, what does the "Install eng (unguarded) su" option on Smelkus do anyway? Does anybody know?
Krazy4evo said:
Unfortunately, I did not make a nandroid backup for this ROM (been using it for only 2 days!).
Anyway, here's what I did so far:
1)I "Pushed" the Superuser.apk found on the MozWoz Rom to my EVO using "adb."
And it did not work. The superuser application installed properly on my device because I can launch it fine from the app drawer, but it does not give me root privileges.
Any other suggestions?
There's gotta be a way to solving this. Exactly, what does the "Install eng (unguarded) su" option on Smelkus do anyway? Does anybody know?
Click to expand...
Click to collapse
http://androidsu.com/superuser/
Download the ARM zip, flash in recovery. You also need the binary and not just the apk. That's why it still didn't work. If it still fails after this then clean wipe and flash ROM again.
Sent from my Galaxy Nexus using xda premium
the.emilio said:
http://androidsu.com/superuser/
Download the ARM zip, flash in recovery. You also need the binary and not just the apk. That's why it still didn't work. If it still fails after this then clean wipe and flash ROM again.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I flashed the ARM zip files with varying results, but none gave me root access.
Anyway, the only way I gained access was to reflash the ROM....
I hope this saves time for any one who's ran into this issue. Nothing but flashing the ROM seemed to work.
Krazy4evo said:
I flashed the ARM zip files with varying results, but none gave me root access.
Anyway, the only way I gained access was to reflash the ROM....
I hope this saves time for any one who's ran into this issue. Nothing but flashing the ROM seemed to work.
Click to expand...
Click to collapse
Glad that you got it figured out.
Like the.emilio said, there are two parts to the SU. You had just downloaded the apk (the app) but that needs the binary (instructions) to work.
I would have thought that the ARM files would have done this.
At any rate, you're back and working, so that's good news. My advice would be to now go make a nandroid backup. That way as you discover and play with this new rom, if you break something, you can easily return to a known "good" state without too much hassle.
Saved my bacon more than once over the years.
connman said:
Glad that you got it figured out.
Like the.emilio said, there are two parts to the SU. You had just downloaded the apk (the app) but that needs the binary (instructions) to work.
I would have thought that the ARM files would have done this.
At any rate, you're back and working, so that's good news. My advice would be to now go make a nandroid backup. That way as you discover and play with this new rom, if you break something, you can easily return to a known "good" state without too much hassle.
Saved my bacon more than once over the years.
Click to expand...
Click to collapse
I barely ran the ROM for 2 days before realizing I had not made a backup -lol!
My guess is that Smelkus was intended to be used with GB, so it created ROM root privileges that were different from later version of su? Maybe Smelkus needs to do a kernel check before enabling certain options?
Anyway, it's great to be back. And yes, I made a backup shortly after getting everything to work.
Krazy4evo said:
I barely ran the ROM for 2 days before realizing I had not made a backup -lol!
My guess is that Smelkus was intended to be used with GB, so it created ROM root privileges that were different from later version of su? Maybe Smelkus needs to do a kernel check before enabling certain options?
Anyway, it's great to be back. And yes, I made a backup shortly after getting everything to work.
Click to expand...
Click to collapse
Hmm. I'm running Smelkus in Provision/Jellyvision, which is a JB rom (great rom, by the way and very stable on our Evo). In fact, smelkusmod was recommended by the developer of Provision/Jellyvision as the recovery. It's based on AmonRA, so should be pretty compatible regardless.
Install unguarded su installs some old superuser hack as the su binary. Not sure what it was for, but it had a purpose at some point. The regular "Install or fix su & superuser" choice installs a normal (but quite old) version of the superuser.apk and binary and sets their permissions. Both should be avoided at this late stage of Evo use. I think Diablo updated to SuperSU on his version, but if you need to install Superuser (koush), SuperSU, or SuperUser it would be better to use the latest version of their respective flashable zips.
Recovery is entirely separate from the ROM and kernel you are running, so it doesn't matter if you have Jelly Bean, ICS, GB or even Android at all for that matter. All recoveries - stock, CWM, TWRP, RA, etc - are basically a mini-OS with their own kernel and init. It boots and runs the program, recovery. Recovery then executes built in commands and scripts included with it. When a ROM developer recommends a recovery, they are just promoting what they like. Any recovery can do the job in their own manner.
In your case, after installing that unguarded su, you could have done any of the following steps to recover:
Flashed a current Superuser zip if it was already on your phone
adb pushed one and flashed
Booted up the ROM, downloaded one, go back to recovery and flash
Flashed the ROM and gapps again, wiped cache and dalvik and rebooted
Restored backup if available