first off i'm an amateur. but i just installed the newest unrevoked flash (v3.3) for my evo. then i downloaded rom manager, and ended up flashing to the cyanogen mod. but, now my phone is stuck in some sort of reboot were the cyanogen mod is trying to load but won't. anyone have any suggestions on how to fix this?
nevermind, thanks though.
Related
I'm trying to get the latest cm (4.2.14.1) working on my g1 but after flashing the rom I have no network or gps (I assume because maps errors out on me). I've tried some older roms as well with 4.2.1 everything seems fine, with 4.2.10 going to setting gives me an error, 4.2.12 leaves me with my phone hanging after cyanogen logo. Does anyone know how I can fix this issue?
I'm using cyanogen 1.4 recovery, hard spl and my radio is *.19.26 (sorry I don't know exactly what the radio is)
When in doubt wipe it out... I had the issue of it hanging like that as well & was able to fix it after wiping.
I gave up on cyanogenmod but found sucess with super donut 1.9.2. But I still have a question, What's the developer 1.6 recovery? Do you just flash once then you got it forever? If not why does cyanogen need it but not super donut?
I gave up on cyanogenmod but found sucess with super donut 1.9.2. But I still have a question, What's the developer 1.6 recovery? Do you just flash once then you got it forever? If not why does cyanogen need it but not super donut?
caliel said:
I gave up on cyanogenmod but found sucess with super donut 1.9.2. But I still have a question, What's the developer 1.6 recovery? Do you just flash once then you got it forever? If not why does cyanogen need it but not super donut?
Click to expand...
Click to collapse
you don't need cyanogen's. You can use amon ra's with cyanogen rom.
hiddengopher said:
you don't need cyanogen's. You can use amon ra's with cyanogen rom.
Click to expand...
Click to collapse
Thank you but that isn't the recovery I was refering to I ment "signed-dream_devphone_userdebug-ota-14721.zip"
The tut I used to setup my phone (http://forum.xda-developers.com/showthread.php?t=563679) says to flash it prior to the rom and I was wondering why cm needed it but not super-d.
Also I have apps2sd setup now and was wondering two things about it. After wiping and putting a new rom on will all my apps still available? And my internal storage still seems to be shrinking as I install apps why is that if there being put on the sd card? (Sd secondary is shrinking to so I know they are)
im trying to search but cant find anything... i rooted my Dinc, clockwork installs fine...then i flashed Sky Raider 2.5.2 and its installed and working fine... i can install and use apps that require root, but if i boot into recovery, it goes back to the stock one, not clockwork.
why is it doing this?
anyone?
im following this guide EXACTLY.
http://forum.xda-developers.com/showthread.php?t=760306
nevermind, im stupid. disregaurd. lol
I just installed RubiXFocused 1.8.6 yesterday. I installed it by booting into Clockwork Recovery (I think that's what it's called) and installing the zip file. It is a brand new ROM for the Droid X and I am very happy with it. The only thing is that it has a white status bar and I think it would look a lot better with a black one.
I looked online and found that the easiest way to do this would be through ROM Manager. So I got ROM Manager and tried to install Blackmodz Black Bar. Everything works until it reboots and tries to install the update. About halfway through I get an error showing a triangle with an exclamation mark inside and the android next to it. And then the phone reboots with no update.
I am in bootstrap recovery when I do all of this. Any help??
That black bar that you are trying to install is not compatible with Rubix at all. Rubix uses a completely different framework. When you try to install that black bar- it is trying to replace the Rubix framework-res.apk. Thankfully you were "unsuccessful".
Might I ask- are you keeping up with the thread on Rubix 1.8 over here...
http://www.droidforums.net/forum/drod2169-x/97764-often-imitated-never-duplicated-focused-1-8-6-a.html
...it is very helpful and you will be able to find modifications that work in this thread. Now that you are running RubiX you must be careful with any mods that you do to your X bc Rubix is using a framework-res.apk that is unique to the Rom and not shared with any of the other roms or the original Moto rom. that means most mods need to be specifically designated for rubix 1.8.
hope that is helpful and didn't come off sounding superior. I hate being talked down to but noticed that inadvertently I can sound that way.
good luck.
Not at all. thank you so much for your help. I had not seen that thread and it is super helpful.
Butterandguns said:
Not at all. thank you so much for your help. I had not seen that thread and it is super helpful.
Click to expand...
Click to collapse
Can someone please let me know rubix 1.8.9 is more stable than 1.8.6 ? I have a rooted droid X running OTA 2.2. I have YET to install a custom ROM, and am a little apprehensive, as I do NOT want to BRICK my phone. Also, can someone please verify the correct procedure to install a custom ROM. I have Clockwork Recovery Manager installed, as well as Koush's bootstrap for DX. I believe I have to boot into Clockwork Recovery and perform - wipe data/wipe cache, and then install zip from SD (once I put the ROM zip file on the SD).then sit back and let install..continue..Am I missing something? Thanks for any help/advice.
I used ODIN to revert back to stock kernel, rooted my vibrant, then I installed rom manager from the market.
However, when I start rom manager and click "Flash ClockworkMod Recovery", nothing actually happens! I don't get prompted to select a phone model or anything. Upon rebooting into recovery, I don't even get to the clockwork mod recovery screen. What gives?
it's driving me nuts and i'm going to set dev's on fire, esp since i just downloaded nero. samsung doesn't seem to be supported with the new update as of the last 24 hours and now i need a new method for getting into clockwork without using terminal or adb of any of that stuff. im not a total noob, but trying to work with that is like trying to read spanish. no comprehendo'
the weird thing is that I was able to use rom manager in the past to go from samsung's stock firmware to Onyx, and again when I went to Nero Beta. I don't understand why it would stop working now.
http://forum.xda-developers.com/showthread.php?p=9869448#post9869448
BAM!!!!! clockwork backdoor confirmed.
installing nero as i type.
^ thanks for sharing the fix. Fyi though, koush has fixed the server issue. All is well.
hello all, i recently installed clockwork3.0 to try out the cm7 rom and did so. afer that i wanted to go back to cm6 but decided to try out a custom baked modaco in between. I went no problems to the modaco vision rom and then tried to go back to the cm6 and thats where i ran into the problem. It seems as if though all i can flash and boot now is the modaco vision and desire roms. i try enomther and cm and after the flash and reboot im always stuck at the HTC boot screen which i know shouldnt be there and cant format boot in cwork3.0 without failure error. Even a nandroid back to cm6 wont work. Im assuming this has something to do with the modaco rom writing some apps to /system during install. If anyone can point out my error or explain why this could happen it would be greatly appreciated. Thanke, veritasaequita
You need to flash back to the old ClockworkMod Recovery using fastboot? You have done that haven't you? CWM Recovery 3 is only for 2.3 roms atm afaik.
Cool, thanks for the input bro. Yes I sure have. I did see in the dev forum a thread titled install cw3.0 easily from phone. Is it possible to go back to the old cw by way of using the phone also? Once again thanks for your help
Sent from my HTC Vision using XDA App
oh yeah, indeed you have hit upon something. Try installing ROM manager via the Market,... then use that to re-install the old recovery.
But if that fails,... then yes, you SHOULD be able to use a Terminal Emulator to flash without using fastboot commands.