Related
Okay. Couple days ago, i got my new Samsung Galaxy S II. Fell in love with it. I previously had a Vibrant, but that met an unfortunate and violent demise. On the vibrant I hadn't been doing anything involving roms and such because i'd tried once, and completely fried the phone. LOL.
I managed to root my phone, and from what I've read, I didn't do the best method. What I did was get an unsecure kernel, and flashed that, then used a 1-click root type thing to root it. So one of my questions is, my clockwork mod isn't working, what's wrong with it? I downloaded ROM Manager, and flashed CWM. But when i reboot into recovery, i get the stock Samsung recovery screen. How can I get this to work?
And another question, is about roms such as Cyanogen mod. I really wanna get it. (I wont until I get CWM working, though.) And I'm just wondering. If I were to just go to ROM Manager, and flash cyanogen, would it work, or do i need to do more to my phone to be able to put on custom roms? I've never understood the concept of roms vs kernels vs firmware vs whatever else.
And if it matters, Samsung Galaxy S II, Android 2.3.3, rooted using SuperOneClick.
P.S Anything else that I should considering doing/putting onto my phone? And thanks in advance for halping.
Gutana said:
Okay. Couple days ago, i got my new Samsung Galaxy S II. Fell in love with it. I previously had a Vibrant, but that met an unfortunate and violent demise. On the vibrant I hadn't been doing anything involving roms and such because i'd tried once, and completely fried the phone. LOL.
I managed to root my phone, and from what I've read, I didn't do the best method. What I did was get an unsecure kernel, and flashed that, then used a 1-click root type thing to root it. So one of my questions is, my clockwork mod isn't working, what's wrong with it? I downloaded ROM Manager, and flashed CWM. But when i reboot into recovery, i get the stock Samsung recovery screen. How can I get this to work?
And another question, is about roms such as Cyanogen mod. I really wanna get it. (I wont until I get CWM working, though.) And I'm just wondering. If I were to just go to ROM Manager, and flash cyanogen, would it work, or do i need to do more to my phone to be able to put on custom roms? I've never understood the concept of roms vs kernels vs firmware vs whatever else.
And if it matters, Samsung Galaxy S II, Android 2.3.3, rooted using SuperOneClick.
P.S Anything else that I should considering doing/putting onto my phone? And thanks in advance for halping.
Click to expand...
Click to collapse
Okay, don't take this the wrong way, but it seems you're a bit lacking regarding knowledge about this phone... It'd pay to do your research beforehand in the SGS2 forum, read the FAQs, etc.
Okay, first off, all I can say is, go back to stock. Go flash a stock Samsung ROM for the device. Then, go into Chainfire's CF-Root Kernel thread, and download the appropriate kernel, and flash it using ODIN. After you've done that, you'll have ClockworkMod, and you'll be rooted. It is recommended that you flash another kernel though, after gaining root, as all the CF-Root kernel does it install ClockworkMod, and root the device. Personally, I recommend SiyahKernel.
If you need more detail or have any more questions, feel free to send me a PM.
Thanks,
screamworks.
screamworks said:
Okay, don't take this the wrong way, but it seems you're a bit lacking regarding knowledge about this phone... It'd pay to do your research beforehand in the SGS2 forum, read the FAQs, etc.
Okay, first off, all I can say is, go back to stock. Go flash a stock Samsung ROM for the device. Then, go into Chainfire's CF-Root Kernel thread, and download the appropriate kernel, and flash it using ODIN. After you've done that, you'll have ClockworkMod, and you'll be rooted. It is recommended that you flash another kernel though, after gaining root, as all the CF-Root kernel does it install ClockworkMod, and root the device. Personally, I recommend SiyahKernel.
If you need more detail or have any more questions, feel free to send me a PM.
Thanks,
screamworks.
Click to expand...
Click to collapse
Alright, I did what you said. I went to stock 2.3.4, used CF-root. And now about SiyahKernel, what are the advantages of it? And is there something wrong with just staying with the CF-Root kernel?
And as of where I am now, with just root and CWM, would i be able to switch ROMs and such?
Gutana said:
Alright, I did what you said. I went to stock 2.3.4, used CF-root. And now about SiyahKernel, what are the advantages of it? And is there something wrong with just staying with the CF-Root kernel?
And as of where I am now, with just root and CWM, would i be able to switch ROMs and such?
Click to expand...
Click to collapse
With a rooted device you'll be able to flash trough Odin or CMW recovery any rom you like.
Siyah kernel gives you a faster and more battery efficient phone and lets you set your own Voltage/ speed the processor has to use see this for the latest info
http://www.gokhanmoral.com/ and
http://forum.xda-developers.com/showthread.php?t=1263838
DirkTeur Velserbroncx said:
With a rooted device you'll be able to flash trough Odin or CMW recovery any rom you like.
Siyah kernel gives you a faster and more battery efficient phone and lets you set your own Voltage/ speed the processor has to use see this for the latest info
http://www.gokhanmoral.com/ and
http://forum.xda-developers.com/showthread.php?t=1263838
Click to expand...
Click to collapse
Alright, so i'm pretty much ready to go? Yayayayay.
And would you recommend any roms for me? XD
Gutana said:
Alright, I did what you said. I went to stock 2.3.4, used CF-root. And now about SiyahKernel, what are the advantages of it? And is there something wrong with just staying with the CF-Root kernel?
And as of where I am now, with just root and CWM, would i be able to switch ROMs and such?
Click to expand...
Click to collapse
SiyahKernel has a lot of advantages and improvements of CF-Root, which provides null, if I'm correct. Go check out the SiyahKernel thread in Original Development for details.
Yes, as stated, you can use CWM by itself to switch ROMs. Just remember that if you're switching ROMs (as opposed to performing a flash to a newer version of the same ROM), to perform a factor reset / wipe data, wipe cache, and wipe Dalvik cache (Advanced > wipe Dalvik cache) in ClockworkMod first.
Gutana said:
Alright, so i'm pretty much ready to go? Yayayayay.
And would you recommend any roms for me? XD
Click to expand...
Click to collapse
For a beginninger, I can't recommend MIUI highly enough. You could go with GalnetMIUI, which is a variant, but I personally prefer the official MIUI build. If you're looking for a more, 'pure' experience, go with CyanogenMod 7.1 stable.
screamworks said:
SiyahKernel has a lot of advantages and improvements of CF-Root, which provides null, if I'm correct. Go check out the SiyahKernel thread in Original Development for details.
Yes, as stated, you can use CWM by itself to switch ROMs. Just remember that if you're switching ROMs (as opposed to performing a flash to a newer version of the same ROM), to perform a factor reset / wipe data, wipe cache, and wipe Dalvik cache (Advanced > wipe Dalvik cache) in ClockworkMod first.
For a beginninger, I can't recommend MIUI highly enough. You could go with GalnetMIUI, which is a variant, but I personally prefer the official MIUI build. If you're looking for a more, 'pure' experience, go with CyanogenMod 7.1 stable.
Click to expand...
Click to collapse
Alright, one more question, sorry for the nooby-ness. Haha.
So going from my phone to for example Cyanogen, I'd backup in CWM, and Titanium backup (Or does CWM backup like, EVERYTHING?) and then factory reset, flash the rom using odin, and then use titanium backup to get my apps and settings back? orwhat.
Gutana said:
Alright, one more question, sorry for the nooby-ness. Haha.
So going from my phone to for example Cyanogen, I'd backup in CWM, and Titanium backup (Or does CWM backup like, EVERYTHING?) and then factory reset, flash the rom using odin, and then use titanium backup to get my apps and settings back? orwhat.
Click to expand...
Click to collapse
CWM backup (called a NANDroid backup), backs up everything. If you perform a NANDroid back, there's no need to perform a backup in Titanium Backup - it creates a full image of your system (the advantage to TB though, is that you can backup all your download apps and settings, then install the new ROM, and restore the backed up apps - If you restore a NANDdroid backup, it'll restore the old ROM, exactly as it was when the backup was made).
So yes, the installation process is, for CWM: copy the ROM.zip to your phone, then boot into CWM recovery. Hit the 'factory reset / wipe data' option, the 'wipe cache' option, and then go to Advanced, and hit the 'wipe Dalvik cache' option. After that, choose 'install ZIP from SDCARD', and choose your ROM.zip. After it finishes installing, just hit 'reboot system now', and you're good to go!
Usually, it's not required to use ODIN to flash a new ROM, unless there's a problem with the recovery.
All that said, it pays to read the thread for the ROM beforehand, as sometimes when moving from ROM to ROM (especially from stock), there's a few small things that may be required, like flashing the ROM twice, or whatever
screamworks said:
CWM backup (called a NANDroid backup), backs up everything. If you perform a NANDroid back, there's no need to perform a backup in Titanium Backup - it creates a full image of your system (the advantage to TB though, is that you can backup all your download apps and settings, then install the new ROM, and restore the backed up apps - If you restore a NANDdroid backup, it'll restore the old ROM, exactly as it was when the backup was made).
So yes, the installation process is, for CWM: copy the ROM.zip to your phone, then boot into CWM recovery. Hit the 'factory reset / wipe data' option, the 'wipe cache' option, and then go to Advanced, and hit the 'wipe Dalvik cache' option. After that, choose 'install ZIP from SDCARD', and choose your ROM.zip. After it finishes installing, just hit 'reboot system now', and you're good to go!
Usually, it's not required to use ODIN to flash a new ROM, unless there's a problem with the recovery.
All that said, it pays to read the thread for the ROM beforehand, as sometimes when moving from ROM to ROM (especially from stock), there's a few small things that may be required, like flashing the ROM twice, or whatever
Click to expand...
Click to collapse
Alright, i got that done. I've tried both MIUI and Cyanogen, and both are working and lookin wonderful. But the problem is I dont get data on either one. I've tried reflashing, rebooting, factory reset. Idunno what else to try. Do you know what could be causing this?
Gutana said:
Alright, i got that done. I've tried both MIUI and Cyanogen, and both are working and lookin wonderful. But the problem is I dont get data on either one. I've tried reflashing, rebooting, factory reset. Idunno what else to try. Do you know what could be causing this?
Click to expand...
Click to collapse
Check your APN settings (should be somewhere in Settings under mobile network or whatever). Look your's up online ('APN settings carrier y, country z), and if they're not correct, add them in.
screamworks said:
Check your APN settings (should be somewhere in Settings under mobile network or whatever). Look your's up online ('APN settings carrier y, country z), and if they're not correct, add them in.
Click to expand...
Click to collapse
Got everything working, thank you very much. Thanked every one of your posts
And I've asked too many questions for one person in one thread, I happen to have one more. How can I get the Android Market on Cyanogenmod? I downloaded build 115, and there wasn't a market, so i'll be using MIUI till I get that fixed. ><
Gutana said:
Got everything working, thank you very much. Thanked every one of your posts
And I've asked too many questions for one person in one thread, I happen to have one more. How can I get the Android Market on Cyanogenmod? I downloaded build 115, and there wasn't a market, so i'll be using MIUI till I get that fixed. ><
Click to expand...
Click to collapse
You're more than welcome
If you've got any other questions, feel free to PM me
With CyanogenMod, there's a bit of a story to it, but basically, they're not allowed to package Market, Gmail, Maps, etc. with the ROM, so you need to download a zip file called Gapps and flash it in CWM Recovery, you can find it here. You don't need to wipe anything when flashing this.
Also, build #115 isn't the latest, build #117 is (in fact, there's another, even more current one, but there's really nothing to it), but I don't believe there's any major changes.
screamworks said:
You're more than welcome
If you've got any other questions, feel free to PM me
With CyanogenMod, there's a bit of a story to it, but basically, they're not allowed to package Market, Gmail, Maps, etc. with the ROM, so you need to download a zip file called Gapps and flash it in CWM Recovery, you can find it here. You don't need to wipe anything when flashing this.
Also, build #115 isn't the latest, build #117 is (in fact, there's another, even more current one, but there's really nothing to it), but I don't believe there's any major changes.
Click to expand...
Click to collapse
Hey, I was having troubles messaging you, since it didn't show anything in the sent box, i assumed it didnt go through. So i guess ill be still asking you on here.
So about Cyanogen, which build is the best? And if i'm going from one build to another, like from 115, to 116, would i still have to do a complete wipe? And any other roms besides MIUI and Cyanogen you recommend? cause MIUI is giving me and couldn't generate md5 errors, and i cant restore to it, and i hate starting off without it set up how i like it. D: and yeah, thanks.
Gutana said:
Hey, I was having troubles messaging you, since it didn't show anything in the sent box, i assumed it didnt go through. So i guess ill be still asking you on here.
So about Cyanogen, which build is the best? And if i'm going from one build to another, like from 115, to 116, would i still have to do a complete wipe? And any other roms besides MIUI and Cyanogen you recommend? cause MIUI is giving me and couldn't generate md5 errors, and i cant restore to it, and i hate starting off without it set up how i like it. D: and yeah, thanks.
Click to expand...
Click to collapse
I only just the message 12 hours ago, if that helps?
Usually, your best bet is to go with the latest build, which you can get here. If it's stability you're looking for, go with the stable build, instead of nightlies.
Personally, out of all ROMs I've tried, I could only ever stand MIUI and CyanogenMod - but even then, MIUI started to annoy me with little things here and there. I think I'll be sticking with CyanogenMod for awhile. So, I'm not really the best authority on that. Just try some different ones, and see what appeals to you the most
Hey all,
I'm very new to Cyanogen, so sorry if this is a very n00b question.
The ROM Manager doesn't appear to work. It keeps telling me I'm not running ClockWorkMod recovery, and cannot connect to the web to download. I purchased the premium version thinking it would solve this (as well as to support the dev), but no luck. Is it just an issue with the nightlies not capable of handling ROM manager yet, or is it a setting of some sort that I'm neglecting? It's not a huge deal, but it looks like such a nice, simple way to stay up-to-date with the nightly builds as opposed to updating through CWM, wiping, etc.
I saw a post mentioning to go into developer tools and enable root access. The closest I found was in settings and I allowed apps and ADB root access, but this didn't help.
Any suggestions would be greatly appreciated, thanks!
I'm a bit confused, Why do you require ROM manager? The CWM that is built in with the ICS Kang releases should be doing everything that is required, then again, your reply would matter.
I think I am having the same issue. When I try to Flash ClockworkMod Touch in Rom Manager it keeps telling me I need to first install ClockworkMod Recovery even though I have Recovery 5.5.0.4 currently installed. It did the same thing when I had Recovery 4.0.0.4 installed.
I even tried to "Flash ClockworkMod Recovery" (First option in ROM Manager) and it does nothing.
Any ideas?
BEcause the same menu is in the CWM recovery lol
I'm following one of the threads that updates the kang build every 3 days, and as opposed to having to boot through CWM, wipe, install, then re-install apps and replace widgets, I thought I could update through ROM Manager instead.
It sounds like Sn0warmy and I are having similar issues.
From what I've heard the ROM Manager doesn't really work for the tab yet. If you want to update without replacing all your apps you can just flash the zip file in CWM without doing a wipe. If it causes problems then you could do a wipe & reflash afterwards.
Dolfan058 said:
I'm following one of the threads that updates the kang build every 3 days, and as opposed to having to boot through CWM, wipe, install, then re-install apps and replace widgets, I thought I could update through ROM Manager instead.
It sounds like Sn0warmy and I are having similar issues.
Click to expand...
Click to collapse
ROM manager works but it's wonky on the ICS kangs. It doesn't do anything that you can't already do in recovery, so there's no real advantage anyways. Oh, and don't use ROM manager to install a new recovery, and CWR touch doesn't work for the GT10.
^You saved me the trouble of insisting Why thank you good sir.
Thanks for the replies. I'll keep updating through CWM.
Coffeebeans, obviously I'm following your thread (thanks for the good work!) and I tried flashing over once but I got a ton of process media FCs so I figured wiping was the best way to go and have done so ever since. Probably should invest in titanium backup at this point so I don't have to reinstall from market everytime I wipe.
Thanks again for the help y'all.
It worked once with 4/17 build of CM9. After that, it has never worked again. It boots into recovery and pretends its flashing, but stops half a second later and restarts.
Something odd happened today when I tried to update. It rebooted and phone locked up and screen went black. I took out the battery and put it back in then held up and power to go into CWM. All of a sudden Rom Manager took over and flashed the rom as well as the additional zips successfully and rebooted. Everything works.
CWM tries to flash from /emmc. Rom Manager tries to flash from /sdcard and fails. It may be due to the swapped mount points on CM9. in CWM they are still swapped, even if you check the use internal storage box and everything shows up properly in CM9.
This is the first time I rooted my phone and I used step 6 on this link in your forum http://forum.xda-developers.com/showthread.php?t=1238070 . Everything went fine but I then downloaded rom manager and when I select flash clockworkmod it only gives me the choice of choosing the samsung epic4g or the samsung galaxyS i9000. It does not give me the option of choosing the fascinate. I selected the i9000 but stopped there because I figured that I should try to fix this situation and be able to select the fascinate, before I move foward. Please help me move foward so I will be able to put a rom on my phone. Any help would be greatly appreciated.
Thanks
lucash312 said:
This is the first time I rooted my phone and I used step 6 on this link in your forum http://forum.xda-developers.com/showthread.php?t=1238070 . Everything went fine but I then downloaded rom manager and when I select flash clockworkmod it only gives me the choice of choosing the samsung epic4g or the samsung galaxyS i9000. It does not give me the option of choosing the fascinate. I selected the i9000 but stopped there because I figured that I should try to fix this situation and be able to select the fascinate, before I move foward. Please help me move foward so I will be able to put a rom on my phone. Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
rom manager is useless for the fascinate...
I also ran into this issue. If your CWM is not "sticky" (it goes to System Recovery <3e> when you reboot recovery), you must flash the appropriate version of CWM with ODIN before a ROM flash. (CWM ALL.tar for bml roms [anything that is not cm7, MIUI, or ICS] or cwm4_fixed_for_cm7.tar for MTD ROM's [cm7, MIUI, or ICS])
MultipleMonomials said:
I also ran into this issue. If your CWM is not "sticky" (it goes to System Recovery <3e> when you reboot recovery), you must flash the appropriate version of CWM with ODIN before a ROM flash. (CWM ALL.tar for bml roms [anything that is not cm7, MIUI, or ICS] or cwm4_fixed_for_cm7.tar for MTD ROM's [cm7, MIUI, or ICS])
Click to expand...
Click to collapse
if the op would of followed the guides instructions correctly, he would not of ran into that issue in the first place...
droidstyle said:
rom manager is useless for the fascinate...
Click to expand...
Click to collapse
But if that's the case, why does Koushik make a ROM for the fascinate and have it available on his site?
(Does the Epic4G simply represent all CDMA phones, and the i9000 GSM? Don't see why that would matter anyway tho)
(I can't post a direct &#% link yet, but it's on his website.
This makes absolutely no sense!? He's got ROMs up there for just about every Android phone on the market, all to be used with ROM Manager.
I wanted to install it via Odin but naturally that would be too simple: it's a zip file and Odin won't recognize anything but tar and 2 others formats.
You can flash any .zip ROM with CWM. There's no need for ROM Manager. BTW, you can post a link if you uncheck "parse links in text automatically."
Nymblz said:
But if that's the case, why does Koushik make a ROM for the fascinate and have it available on his site?
(Does the Epic4G simply represent all CDMA phones, and the i9000 GSM? Don't see why that would matter anyway tho)
(I can't post a direct &#% link yet, but it's on his website.
This makes absolutely no sense!? He's got ROMs up there for just about every Android phone on the market, all to be used with ROM Manager.
I wanted to install it via Odin but naturally that would be too simple: it's a zip file and Odin won't recognize anything but tar and 2 others formats.
Click to expand...
Click to collapse
all you need to do is boot into cwm recovery via the power menu and flash away. the problem with rom manager on the fascinate is getting into the right recovery...causes more problems than its worth on this device. make sense yet? probably not since you have not been down this road yet, but many of us have. so take the advice given or dont and learn the hard way.
Honestly, I am trying to take the advice given but not all of it fit my situation.
I'm definitely something of a noob to Android (Not to linux or IT though). I've had my phone for all of a month and rooted it only days ago.
It's all starting to come together, finally. It's tricky for a noob because there are so many different versions of the phone hardware, versions of Android, this or that kernel that only works with these ROMs, old/newer versions of those, old posts and advice, newer posts with adjusted advice.. etc.. It's been a week long crash course!
Anyhoo, I couldn't flash/upgrade CWM because it didn't stick from the original Odin install. When I rebooted, I'd always return to the stock <3e> recovery. Even after two more installs of CWM via Odin.
I used the cwm-recovery-all.tar in your guide, Droidstyle. (great job BTW)
I followed the directions in Section 6 to the letter. I even printed it out and highlighted key sections.
So you see, I was in a catch-22; I needed CWM to flash CWM? Odin was my only option at that point.
Then I read on another thread here about renaming the /system/recovery-from-boot.p script, and installing CWM once more.
That worked, so now I can finally boot into CWM recovery like a happy man. (I also tried a more specific version of CWM for good measure: cwm4-bml-i500.tar, not really sure if that made a difference)
So I made my first real nandroid backup last night.
Next on my list is a new kernel. Still deciding between KGB, lean, and whatever else is out there.
I still don't get the whole mess with ROM Manager though. I agree with you, DS, I just don't get why he'd have zips for every phone under the sun but his own app doesn't seem to allow them to be used. It's bizarre. The latest reviews on the market are not flattering either.
Nymblz said:
It's tricky for a noob because there are so many different versions of the phone hardware
Click to expand...
Click to collapse
You are on the Samsung Fascinate. If it is Verizon then it is model number i500. If it doesnt say Fascinate or i500 it isn't for your device and you don't need to worry about it. If you flash something that isn't stated as being for the i500 or VERIZON Fascinate then you will have a lovely new temporary paper weight.
Nymblz said:
Anyhoo, I couldn't flash/upgrade CWM because it didn't stick from the original Odin install. When I rebooted, I'd always return to the stock <3e> recovery. Even after two more installs of CWM via Odin.
I used the cwm-recovery-all.tar in your guide, Droidstyle. (great job BTW)
I followed the directions in Section 6 to the letter. I even printed it out and highlighted key sections.
Click to expand...
Click to collapse
You couldn't have followed it to the letter because it is a well known fact that if you boot up with a stock kernel still flashed it will replace your recovery. Droidstyle certainly knows this and certainly accounted for it in his guide. So, you need to either boot directly into CWM or flash a non-stock kernel prior to rebooting the phone.
Nymblz said:
Then I read on another thread here about renaming the /system/recovery-from-boot.p script, and installing CWM once more.
That worked, so now I can finally boot into CWM recovery like a happy man. (I also tried a more specific version of CWM for good measure: cwm4-bml-i500.tar, not really sure if that made a difference)
So I made my first real nandroid backup last night.
Click to expand...
Click to collapse
Yeah it sounds like that will work...not the most elegant way to take care of it...but it sounds like it would be okay.
Nymblz said:
Next on my list is a new kernel. Still deciding between KGB, lean, and whatever else is out there.
Click to expand...
Click to collapse
We already talked about the kernel situation. Consider Geewiz if you want something thats all-in-one and pretty much impossible to mess up. KGB is good. Leankernel always gave me the best battery life but YMMV.
Nymblz said:
I still don't get the whole mess with ROM Manager though. I agree with you, DS, I just don't get why he'd have zips for every phone under the sun but his own app doesn't seem to allow them to be used. It's bizarre. The latest reviews on the market are not flattering either.
Click to expand...
Click to collapse
He showed no interest in helping the devs here get ROM manager working (again) on the phone. If you gave him money, blame him for not providing the support and resources to get it working on this phone. Some people are umm...."lacking in people skills."
Oh, and as great as the Gingerbread ROMs are...the mtd ICS roms blow them out of the water
Is there any chance one of the devs working on this device can get CWM recovery working for it? I've used CWM exclusively on my OG Droid and Inc 2.... I'm hesitant to use a recovery I'm unfamiliar with on my Inc 4G.
The only recovery available is TWRP. I don't know of anything being worked on through other developers. But trust me on this, TWRP is far superior and easier to use. Just an opinion, but wanted to shed some of your fears. I've used TWRP on several phones and it works extremely well.
Do you know if ROM Manager can be used with TWRP? Or would it even be necessary to install ROM Manager?
Sent from my HTC Incredible 4G
RomManager is designed for CWM. I strongly doubt it will work giving recovery commands that reboot the phone. In fact, judging by the comments left about RomManager lately, I don't think it supports much of anything any more.
Pandalero said:
Do you know if ROM Manager can be used with TWRP? Or would it even be necessary to install ROM Manager?
Sent from my HTC Incredible 4G
Click to expand...
Click to collapse
*Madmoose* said:
RomManager is designed for CWM. I strongly doubt it will work giving recovery commands that reboot the phone. In fact, judging by the comments left about RomManager lately, I don't think it supports much of anything any more.
Click to expand...
Click to collapse
rom manager is usually compatible with other recoveries (4ext comes to mind)
i cant speak from experience w/ twrp though
I think Koush kind of got overwhelmed with Rom Manager tbh. Soo many phones out there now...huge damn undertaking. It's slipped a little in popularity. I've read some posts where people were talking about experiences with him and support. Don't know how true they are as I've never spoke with him and everything posted on the interwebz is the gawd-honest troof. But support for new phones I think is seriously lacking at this point.
Whatever you do though, don't force CWM into your phone through Rom Manager though...you could be without a recovery
*Madmoose* said:
I think Koush kind of got overwhelmed with Rom Manager tbh. Soo many phones out there now...huge damn undertaking. It's slipped a little in popularity. I've read some posts where people were talking about experiences with him and support. Don't know how true they are as I've never spoke with him and everything posted on the interwebz is the gawd-honest troof. But support for new phones I think is seriously lacking at this point.
Whatever you do though, don't force CWM into your phone through Rom Manager though...you could be without a recovery
Click to expand...
Click to collapse
Thanks for the insight. My personal experience with Koush and his products have all been good. I was just wary of flashing something I've never used. My main goal right now is to just root my Inc 4G so I can get free WiFi tether. I'm grandfathered into unlimited data, but that doesn't include WiFi Hotspot. Then I'm going to wait for some CM10.
I will not even consider porting CWM. It is the worst available recovery and rom manager is garbage.
CWM was great on older devices like the original Incredible, but on newer devices, it has invited a lot of problems. You're much better off with TWRP. When the time comes to install custom ROMs on this device, consider using Goo Manager instead of ROM Manager--many developers are now supporting their ROMs on Goo.im and Goo Manager can do everything with TWRP that ROM Manager could do with CWM in terms of flashing.
polarimetric said:
CWM was great on older devices like the original Incredible, but on newer devices, it has invited a lot of problems. You're much better off with TWRP. When the time comes to install custom ROMs on this device, consider using Goo Manager instead of ROM Manager--many developers are now supporting their ROMs on Goo.im and Goo Manager can do everything with TWRP that ROM Manager could do with CWM in terms of flashing.
Click to expand...
Click to collapse
Thanks. I'm gonna flash TWRP tonight.
polarimetric said:
CWM was great on older devices like the original Incredible, but on newer devices, it has invited a lot of problems. You're much better off with TWRP. When the time comes to install custom ROMs on this device, consider using Goo Manager instead of ROM Manager--many developers are now supporting their ROMs on Goo.im and Goo Manager can do everything with TWRP that ROM Manager could do with CWM in terms of flashing.
Click to expand...
Click to collapse
Can you explain why CWM isn't so good and TWRP superior? Im really curious?
I have used both, I had CWM on a few phones but only recently got introduced to TWRP when I needed to put a recovery on a tablet (kindle fire I think...). That being said, the Dinc 4G is the 2nd device I put that recovery on, and I guess it works fine, I mean its done everything expected of it without fail, then again, CWM was pretty reliable as well... soo...
JDMpire said:
Can you explain why CWM isn't so good and TWRP superior? Im really curious?
I have used both, I had CWM on a few phones but only recently got introduced to TWRP when I needed to put a recovery on a tablet (kindle fire I think...). That being said, the Dinc 4G is the 2nd device I put that recovery on, and I guess it works fine, I mean its done everything expected of it without fail, then again, CWM was pretty reliable as well... soo...
Click to expand...
Click to collapse
CWM has been associated with bad blocks, failing to fully wipe device partitions, and disabling charging while the phone is off making the phone remarkably difficult to resurrect if the battery dies, among many other device-specific problems (for example, 5.0.2.0 failing to make a nandroid backup with the ext4 mod flashed on the original Incredible). It's also annoyingly proprietary (ironic, when its primary purpose is flashing open-source ROMs...) in the sense that it ties in specifically with ROM Manager and the two are not very compatible with much of anything else (for example, openrecoveryscript).
TWRP is much more open (which is why apps like Goo Manager are able to support it) and has one really crucial brick-proofing feature that sets it apart: a battery indicator. (Some ports of CWM Touch have battery indicators baked in, but CWM Touch has largely been a porting mess and adoption has been very slow.)
I have confirmed that I have root access and that my bootloader is unlocked
I have tried flashing CWM recovery via rom manager and various img files found throughout this site and others.
Despite this, when I boot into cwm I get the android guy with the yellow ball
If I hit vol up and down I get only a few options:
Bgackup and restore, reboot, apply update, whipe data factory reset, whipe cache partition.
No advanced (this is one I've seen mentioned but didn't see on my device)
But as long as I got that far, I went through the steps to install CM9.
I whiped data then cache
Applied the CM9 zip
then rebooted
When my phone came back on I still have moto gingerbread and it just wants me to relogin to blur and sign in to google.
Also tried Another SD card with the same results. CWM couldn't see any zips on the cards after reentering cwm after a reboot. Reformatting the cards and trying again produced the same results.
What am I missing here? I've followed and refollowed letter by letter with all the guides I've been seen.
Thanks for any help and I apologize for any newb stuff as this is my first attempt at android roms.
Well it looks like this is magically solved now.
After TWRP failed earlier I decided to go back into fastboot and did a erase recovery, reboot, then reflash twrp
Then tried booting into it and it worked!
So I went back into fastboot and flashed cwm instead since I'd prefer the non touch recovery.
Thanks for all the tips
Please remember to post questions in the Q&A forum.
I honestly don't know what's wrong. It looks like your doing everything properly.
seem like you're not with CWM installed on your device..
try to put another one like TWRP and see what happens
You are certain your bootloader is unlocked? (you see "unlocked" on the Moto splash screen)
First, try to fix permissions from Rom Manager.
If that doesn't work fastboot flash the most recent recovery. Go here and get the latest version.
I would advise against using ROM manager. It's been known to cause many issues.
ravilov said:
I would advise against using ROM manager. It's been known to cause many issues.
Click to expand...
Click to collapse
Oh ravilov, you and your crazy stories. I've been using Rom Manager since the day I rooted my phone. Never had one problem (well, except for the way koush does the premium license).
Make sure you're choosing "install zip from SD card" not "install update from SD card".
LÄvLab / HostileSlothRecords
ravilov said:
I would advise against using ROM manager. It's been known to cause many issues.
Click to expand...
Click to collapse
ROM Manager is perfectly fine for fixing permissions.
upndwn4par said:
Oh ravilov, you and your crazy stories. I've been using Rom Manager since the day I rooted my phone. Never had one problem (well, except for the way koush does the premium license).
Click to expand...
Click to collapse
It was reportedly the culprit of randomly appearing ".nomedia" files on some ROMs. After that I don't think I'd want to trust it.
Some people also had problems installing stuff through it, no matter what they tried. Once they switched to cmd/fastboot/manual install, everything worked fine.
So I'm not exactly pulling stuff out of my butt here.
I also don't really like it personally, I always remove it if it comes bundled with a ROM. But that's just me. To each their own. If it's working fine for you, by all means keep using it.
ravilov said:
It was reportedly the culprit of randomly appearing ".nomedia" files on some ROMs. After that I don't think I'd want to trust it.
Some people also had problems installing stuff through it, no matter what they tried. Once they switched to cmd/fastboot/manual install, everything worked fine.
So I'm not exactly pulling stuff out of my butt here.
I also don't really like it personally, I always remove it if it comes bundled with a ROM. But that's just me. To each their own. If it's working fine for you, by all means keep using it.
Click to expand...
Click to collapse
If I remember correctly, that was for epinter's and joker's CM10 ROMs. And it was never even close to proven that CWM was the culprit. Doesn't make sense that CWM is to blame for suddenly doing random stuff. Especially since both of those ROMs have had serious media issues since day one.
Anyway, I'm not saying that CWM is perfect - it's not. But RomRacers recovery is unsupported, and I try to never use unsupported software. TWRP is nice, but I don't like touch recoveries and old CWM backups are useless. Anyway, to each his own.
upndwn4par said:
If I remember correctly, that was for epinter's and joker's CM10 ROMs. And it was never even close to proven that CWM was the culprit. Doesn't make sense that CWM is to blame for suddenly doing random stuff. Especially since both of those ROMs have had serious media issues since day one.
Anyway, I'm not saying that CWM is perfect - it's not. But RomRacers recovery is unsupported, and I try to never use unsupported software. TWRP is nice, but I don't like touch recoveries and old CWM backups are useless. Anyway, to each his own.
Click to expand...
Click to collapse
Um...
I'm talking about ROM manager, not CWM. CWM is great, I'm using it too (well, I'm using RomRacer's recovery which is CWM-based).
I don't mind using older and possibly unsupported software if it's this stable and works without any problems and glitches.
I'm going to assume that was a typo and you really meant ROM manager.
But yeah, ".nomedia" files don't appear out of nowhere. People were unable to find their media files and they were indeed blaming the ROM for doing that. Then someone realized it's due to some ".nomedia" files being created randomly. Then people were deleting all such files but the files would appear again. And then someone noticed removing ROM manager made the madness stop. Now I will admit this is not proof enough, but it really seems very likely that ROM manager was to blame. I think nobody had any problems with media files since.
Oh, and as for the problem OP is mentioning... No, this is not related to ".nomedia" files, and frankly I have no idea what's going on there... :dunno:
ravilov said:
Um...
I'm talking about ROM manager, not CWM. CWM is great, I'm using it too (well, I'm using RomRacer's recovery which is CWM-based).
I don't mind using older and possibly unsupported software if it's this stable and works without any problems and glitches.
I'm going to assume that was a typo and you really meant ROM manager.
But yeah, ".nomedia" files don't appear out of nowhere. People were unable to find their media files and they were indeed blaming the ROM for doing that. Then someone realized it's due to some ".nomedia" files being created randomly. Then people were deleting all such files but the files would appear again. And then someone noticed removing ROM manager made the madness stop. Now I will admit this is not proof enough, but it really seems very likely that ROM manager was to blame. I think nobody had any problems with media files since.
Oh, and as for the problem OP is mentioning... No, this is not related to ".nomedia" files, and frankly I have no idea what's going on there... :dunno:
Click to expand...
Click to collapse
Yeah, you know what I meant. :cyclops:
I still think it is more likely that the ROM made RM go wacky than the other way around. Especially with the history of JB ROM media issues.
ravilov said:
Um...
I'm talking about ROM manager, not CWM. CWM is great, I'm using it too (well, I'm using RomRacer's recovery which is CWM-based).
I don't mind using older and possibly unsupported software if it's this stable and works without any problems and glitches.
I'm going to assume that was a typo and you really meant ROM manager.
But yeah, ".nomedia" files don't appear out of nowhere. People were unable to find their media files and they were indeed blaming the ROM for doing that. Then someone realized it's due to some ".nomedia" files being created randomly. Then people were deleting all such files but the files would appear again. And then someone noticed removing ROM manager made the madness stop. Now I will admit this is not proof enough, but it really seems very likely that ROM manager was to blame. I think nobody had any problems with media files since.
Oh, and as for the problem OP is mentioning... No, this is not related to ".nomedia" files, and frankly I have no idea what's going on there... :dunno:
Click to expand...
Click to collapse
I remember this happening when rom manager updated. Then a few days later they put another update distinctly saying "fixed problem of rom manager adding .nomedia to internal and external sd" so yes rav is right that rom manager was the culprit THEN. However that being said, I had tried a jb rom (can't remember which) that added those .nomedia files to my internal and external so you both could be correct in your assumptions.
EDIT: in the changelog for ROM manger here https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager it shows that it did place those .nomedia files.
Yes, I am certain that my phone is unlocked or at least I think I am since it says "unlocked" in the corner when I turn it on
I didn't want to sign back into everything quite yet so I haven't been able to try the rom manager fix permissions thing yet.
I flashed the TWRP recovery instead of the CWM one and got the same result when booting into the recovery so I assume that neither CWM or TWRP was successfully installed.
Shouldn't flashing these with fastboot get them in there? (technically tried installing from rom manager once too)
drsatan316 said:
Yes, I am certain that my phone is unlocked or at least I think I am since it says "unlocked" in the corner when I turn it on
I didn't want to sign back into everything quite yet so I haven't been able to try the rom manager fix permissions thing yet.
I flashed the TWRP recovery instead of the CWM one and got the same result when booting into the recovery so I assume that neither CWM or TWRP was successfully installed.
Shouldn't flashing these with fastboot get them in there? (technically tried installing from rom manager once too)
Click to expand...
Click to collapse
Yes, fastboot should be installing recovery properly.
I see three possibilities:
1) Something happened during the unlock process, so despite seeing "unlocked" you are not fully unlocked.
2) Fastboot is not writing recovery recursively
3) You have a hardware problem
I would try the following first:
1) Check to make sure you have the correct drivers installed on your PC and you have the most recent version of fastboot
2) Erase recovery with fastboot
3) Re-flash recovery with fastboot
Next I would try unlocking your bootloader again
Did you ever solve your problem?
Yes I got it working now.
TWRP booted after I did a fastboot erase and reflashed the recovery.
So I then reflashed CWM and that booted.
When I actually went to install a ROM a few days later it didn't boot again so I reflashed and ran the recovery on the next reboot OK again.
I was able to successfully get Joker's CM10 flahsed and running.
Not sure why I'd have to reflash every time I want to run the recovery but I think that that isn't a big deal for me anymore as this was just a test and this is no longer my primary device.
Thank you all for the help