EDIT: For some reason, after several attempts, ROM Manager successfully flashed recovery. Should be able to figure this out now.
After going Cyanogen free for awhile, I decided to download the newest kang. Problem is, GAPPS wasn't included.
It seems that ROM Manager isn't allowing me to download ClockworkMod Recovery; perhaps because I am not logged in? Not sure, it simply doesn't seem to want to download. No errors, it just doesn't do anything when trying to flash it.
I try to reboot into recovery, but it just loads the ROM. Attempting to hold the volume up while booting gets me stuck at the folder with the arrow screen.
I'm pretty sure that it is highly recommended that you don't use the fake CWM via rom manager. It installs it to your sd card or something of the sort. The easiest way to install CWM I know of is using the tool this guy madeLink Here. I think that will take care of your problems, of course I'm a little intoxicated on the net so I could be reading it wrong <<---Alcoholic Disclamer
Related
I have just rooted my phone recently on my Droid X using Z4root and it worked fine. Then I backed up my phone using Titanium Backup, which also worked fine also. Then I installed ROM Manager and then flashed ClockworkMod Recovery within ROM Manager. When I click on Backup Current ROM the phone reboots fully without going into recovery. So I open ROM Manager and click "Manage and Restore Backups" and there is no file there.
I tried clicking "Reboot into Recovery" to see if I could select it there and the phone just reboots back to android without going into recovery. So then I turned off my phone and held down the home+power to go into recovery which works. When I'm there it doesn't have an option to backup my ROM. I don't want to flash this ROM I want to try until I can backup my current stock ROM, in case something goes wrong.
When at the blue recovery screen I notice at the bottom in yellow a message is displayed "E: Can't open /cache/recovery/command. Wondering if this is my issue. I also notice in recovery it gives me an option to "apply sdcard:update.zip" but I don't see an update.zip on my sd card, so I'm not sure if I should select this before being able to backup my stock ROM. I'm afraid to flash the ROM before knowing this current problem. Can anyone help me with this issue? I am new to the whole root and ROM hacks, but have been researching in depth and taking all precautions so I'm trying hard not to brick my phone. Thanx in advance.
First off update.zip is just an update.zip package. Could be anything thats an update and can be flashed. Yeah...not sure why rom manager doesnt work for you but all the same your better off doing it from recovery anyway. You can make backups in recovery you don't need rom manager just use rom manager to manage your backups it will see them no matter what! It will allow you to rename them as well so they are easily identifiable also. If your rom manager works youll be able to name the backup before hand! If you ask me rom manager doesnt update the roms fast enough anyway they are usually like 2 days behind! Good tool either way but not so good at replacing roms as recovery does a better job. I have never had one problem using recovery but I've had a problem every time I try to flash a rom using rom manager!
Okay I figured out that the ClockworkMod Recovery must not have flashed properly or something bc I was just at the dev's site and the picture of the recovery is different than mine bc it's green and has many more options to choose from. Plus it says ClockworkMod Recovery on the recovery screen and mine doesn't. It's blue and says android recovery at the top. When I open the ROM Manager it says that I have the ClockworkMod Recovery but I don't. I even tried reflashing but it didn't work either. So how do I get the ClockworkMod Recovery to flash correctly?
I am having same problem but I just use bootstaper and it works fine
I tried downloading the bootstrap from the creator of ClockworkMod Recovery but the link seems to be broken. What bootstrap are u using?
I found the bootstrap for the Droid X on the market and that fixed the issue I was having. Wish I would have known from all the other posts/articles I read that it was a requirement for the Droid X to have the bootstrap to run recovery
So I flashed Paranoid-Android Jellybean and it just screwed up my phone. I had to use Odin to bring it back to stock. Now I've got it almost back to where I want it but I can't for the life of me get CWM recovery onto my phone. Its got super user on it and I can go into the CWM app and tell it to flash CWM and it says it was successful but upon booting into recovery I'm getting the Android 3e recovery with signature verification. I've tried to replace the recovery file with the modified one but if I reboot my phone it just hangs at the Samsung screen. I tried to install SGS kernel flasher as well but its failing to download/install it. Hopefully someone can point out what I'm doing wrong because I don't remember ever having this much trouble.
You can use this to get your recovery back -thanks and credit to qkster and Entropy512
http://forum.xda-developers.com/showthread.php?t=1524081
Questions, let me know and I'll try to help.
Alright, downloaded and used that program. It went through and flashed perfectly fine and was easy to use; only issue is my recovery didn't work any better. I was able to boot into recovery but when I did it was just a scrambled mess of colors. I then used Odin to flash back and now I'm back at the Android 3e recovery again. I've tried to replace the recovery file and boot into recovery but it just hangs at the Samsung logo and if I replace the update.zip it won't flash because its not signed correctly. I've also tried to flash via Rom Manager and it says it went through and was successful and has my "latest version" set as the version I just flashed.
I'm lost as to what I'm doing wrong.
Ok- it may be a process but I am willing to help you figure this out. Once you learn, as long as you are going to be flashing roms, it will come in handy in the future. Couple of questions:
Have you used Heimdall before?
Did you also flash the kernel (Entropy's Daily Driver) in post 2?
Ok didn't even notice there was a way of installing the kernel that way. Did it and now I have a working recovery!!! Thank you so much. I've bricked my phone before but odin fixed it no problem. I'll keep this in mind next time. Saved me a lot of time.
Glad to hear this - nice work.
So. I'm sorry to say, but this phone has given the biggest headache. Here's the background:
I really only use this phone for entertainment and stuff. BUT I decided to root and unlock the bootloader, somehow or another the phone apparently lost root a few times (According to some users here) but never lost SuperUser or anything. I've never been able to flash a rom on this thing. Then a few weeks ago the phone just encountered an error of some sort and would only get to the ICS boot animation and loop over and over. I just gave up on it. Then one day I decided to play with it. I got it into fastboot and then into recovery, (Not CWM Recovery) and was able to get it all set up again. So I figured I'd give it one more shot. I downloaded CWM and downloaded recovery, and a custom rom. tried to flash through fastboot>recovery but it's still the stock recovery, not CWM recovery. So I factory resetted it etc and started from scratch. Now if I download CWM it WILL NOT download recovery. It gets about 99% of the way and tells me: "An error occurred while attempting to run privileged commands!" If I download it from a link I can't open the file....... Someone help I just want a good JellyBean Rom. :crying:
Edit: I've Googled as much as I could stand and still haven't come across anything entirely helpful. Please explain so I could understand. Pictures help if needed lol
Anyone?
You can't use clockworkmod app to flash recovery without root.
Get the fastboot image of cwm recovery ( not the app). Or twrp. Flash it with fastboot.
Boot directly into it and flash what you want. If you boot up a stock os it overwrites the custom recovery on boot.
clockworkmod app sucks IMHO and should never be used for anything period. Not fond of the recovery itself either.
So I've been play with Android for a few years now and I love it. Got the Samsung Galaxy Note 10.1 in the fall of 2012 and had a custom rom installed not long after. Periodically I check XDA to see if there is a new custom ROM I want to try. Finally there is, OMNIRom. It says I need a recovery image that can handle the new SELinux. After poking around for an easy way to update I findout that the goo.im has a new recovery that it will install. And that's where things go south. I installed the new TWRP v2.6.3.0 via the goo.im and then reboot into the recovery. I go to flash the new ROM and it fails. I try downloading the ROM again and flashing it. It fails again. Okay, shouldn't be a problem... I'll just flash my prior rom. It too fails. Uh-oh.... If I try to boot normally, it just loads directly to the faulty TWRP. If I try to boot to the bootloader so I can use Heimdall to flash over a new recovery, it boots to TWRP....
I found a new recovery in a ZIP format finally and tried to use that, but it fails too.
Any advice? Suggestions? Please help.
Hi Guys,
I have an AT&T One X that I unlocked and flashed TWRP recovery on. I have been using this for quite some time with a stockish HTC Custom ROM. However I wanted to see what the latest Cyanogenmod was like. So I flashed the latest snapshot after first flashing the specific recovery software linked on the cyanogenmod page. So far so good. Device booted up and was ready for use.
I wanted to install Gapps afterwards so I went to OpenGapps to download the aroma installer. However the Cyanogenmod recovery software doesn't seem to support this. So I wanted to go back to TWRP. Instead of doing the usual flashing in the recovery I decided to use the TWRP Rommanager since it seemed like a quick fix. Ooh how wrong I was.
After installing the recovery through TWRP manager I accepted the request of TWRP manager to reboot to recovery. However my phone greeted me with a black screen afterwards. Up till now I haven't seen anything pop up onscreen anymore and I tried numerous things. The only strand of hope I still have left as that when connecting to my pc I'm still able to see the phone is in fastboot mode.
However when trying to execute a new flash of my recovery partition my phone keeps saying "fastboot error; remote not allowed". I've searched through numerous articles without a solution up till now. Is my phone too far gone to revive?
Doesn't seem like a straightforward fix as no responses are coming in. Maybe an indication if there would be a fix is appreciated as well.