Related
I've been at this for like 3-4 hours and have gotten NOWHERE.
Okay, so I wasn't always rooted, I waited and waited and waited for Froyo, thinking it was going to be awesome - then it OTA'ed to me, and I've had NOTHING but problems. Battery life went down like 1/2 as much (if not more) on a good day, problems with the vibrations, ring volumes, some parts are laggier, the largest problem is that the new radio image SUCKS and the newest thing, there's some texts and calls that it never gets. I've never seen such a failed update in my entire life. /rant
Anyway, I've been searching and searching and searching so pleeeeeeeeeeeease don't tell me to search anymore.
I'm interested in putting the Ultimate KangBang 2.1 on my phone (end result). So that requires 2.0 as it's a patch - fine.
So first, yes, my phone is rooted, I can run su and get a root shell on my phone (if that's proof I guess?).
The clockwork mod is KILLING me, though.
The problem is I have version 3e of the recovery mode thing which is stopping unsigned files. I've been trying to get clockwork mod 3.X installed for easily the last 2 hours and had nothing but dead links or nothing happened.
I thought I found the answer a little while ago, using this write-up on installing the clockwork mod, I downloaded cwm-recovery-ALL.tar, and pushed it to the phone with Odin, unplugged it upon successful flash, restarted it, held vol down and power, nothing. Eventually holding up (I think it was up) and power got me to standard samsung recovery mode (ie. it did jack ****). Never-the-less, I went in and used the ROM manager to install clockwork mod 3.X, it said it worked..but it didn't.
I can't install things via update of root because I have 3E of the recovery, and I can't get clockwork mod to work for the life of me. I've been googling the **** out of everything I can think of to get the clockwork mod to work, but have come up with outdated forums, or broken ass links.
NOTHING WORKS!
The only think that worked (once) was when I used "reboot into recovery mode" from ROM manager, it rebooted into clockwork recovery..but upon reboot again it booted into the standard recovery mode.
How the HELL do I get the clockwork mod on my phone because believe me when I tell you I've searched and I have a plethora of useless ass tabs cluttering my browser all being completely useless.
Please help
Yes, I'm sure this has been covered "many times" before, but I can't find a single one that works.
TIA :'(
Do you have gtalk ?
All you have to do is download (google) odin http://download1422.mediafire.com/ii...din3+v1.83.exe (its a program made by samsung) and a odinable recovery.tar from this site http://dl.dropbox.com/u/36791/CWM3_Voodoo.tar.md5
Then in odin you place the recovery.tar in the pda section dont click any other things NEVER EVER CLICK PHONE then hit start once it says pass on odin you unplug your phone from the usb and exit odin then put the battery back in and boot directly into recovery ( press/hold the buttons volume up+down and power at the same time) then wipe data/factory reset in recovery then flash either a kernel or rom to make the recovery stick.
Make sure you already have a rom or kernel on your sdcard.
I'm not the best at explaining things but i know exactly what you need to do.
abrixxxx said:
Do you have gtalk ?
All you have to do is download (google) odin (its a program made by samsung) and a odinable recovery.tar from this site.
Then in odin you place the recovery.tar in the pda section dont click any other things NEVER EVER CLICK PHONE then hit start once it says pass on odin you unplug your phone from the usb and exit odin then put the battery back in and boot directly into recovery ( press/hold the buttons volume up/down and power at the same time) then flash either a kernel or rom to make the recovery stick.
I'm not the best at explaining things but i know exactly what you need to do.
Click to expand...
Click to collapse
I'm not trying to be a douche, I know you're trying to help, but can you re-read (or initially read) the 8th paragraph in my post? I know the post is a bit long, but I tried slimming the post down a bit :-\.
EDIT:
gtalk as in the voice program? No, it's not installed on my desktop nor my phone - I use Skype for voice/vid and AIM/gmail for chat.
You're liable to get help more quickly (and with less flaming) if you post questions in the correction section -- please see this stickied thread: http://forum.xda-developers.com/showthread.php?t=1038478
As far as your issue goes, your first problem is that you don't actually want to use ROM Manager. Koush's recoveries no longer work with this phone. The working CWMs for the Fascinate are all modded and have to be downloaded and flashed via ODIN (or another modded CWM).
jt's recovery is closer, but that's still an old version. The most functional pre-packaged one right now is at the top of this post: http://forum.xda-developers.com/showthread.php?t=1046905
Just follow the instructions in that post, and you should be good.
Oh, one other thing -- it doesn't sound like you were using the correct key combination for CWM, so that's probably why jt's wouldn't boot. It's all three keys: power+vol up+vol down, not just power+up or down.
Completely forgot to include the phone specs, my mistake:
Recovery Version: 3e
HW Version: I500.05
Model #: SCH-I500
Firmware Version: 2.2.1
Baseband Version: S:i500.05 V.ED04
Kernel Version: 2.6.32.9
Build Number: SCH-I500.ED04
Just a note on that build number, one of the clockwork mod posts had a whole list of CWM's which were like JYX, JYZ, stuff like that, and they were like "pick whichever cwm matches your phone's build #, blah blah" My phone's build # has no J's in it, and I didn't want to brick it.
Did you boot directly into recovery after putting your battery back in ? You can't boot into the OS before going straight to recovery from odin or else it overwrites the custom recovery with the samsung one.
Falcyn said:
You're liable to get help more quickly (and with less flaming) if you post questions in the correction section -- please see this stickied thread: http://forum.xda-developers.com/showthread.php?t=1038478
Click to expand...
Click to collapse
My mistake, I read that when I initially joined, but forgot about it when I posted .
Falcyn said:
As far as your issue goes, your first problem is that you don't actually want to use ROM Manager. Koush's recoveries no longer work with this phone. The working CWMs for the Fascinate are all modded and have to be downloaded and flashed via ODIN (or another modded CWM).
Click to expand...
Click to collapse
So ROM Manager is completely useless now?
Falcyn said:
jt's recovery is closer, but that's still an old version. The most functional pre-packaged one right now is at the top of this post: http://forum.xda-developers.com/showthread.php?t=1046905
Just follow the instructions in that post, and you should be good.
Click to expand...
Click to collapse
I'll take a look at that now.
Falcyn said:
Oh, one other thing -- it doesn't sound like you were using the correct key combination for CWM, so that's probably why jt's wouldn't boot. It's all three keys: power+vol up+vol down, not just power+up or down.
Click to expand...
Click to collapse
Confirmed 3x, holding down power + vol-up + vol-down starts the OEM Android recovery mode (ie. Android system recovery <3e>). From what I understand about the CWM, once it's installed and working, I should never see this screen again, it should always be the CWM boot screen, no?
abrixxxx said:
Did you boot directly into recovery after putting your battery back in ? You can't boot into the OS before going straight to recovery from odin or else it overwrites the custom recovery with the samsung one.
Click to expand...
Click to collapse
I don't recall, actually, I'll try that now before I check out JT's recovery.
Same as above. But also hold all three buttons and wait for samsung logo to turn on off and back on then let go.
Sent from my SCH-I500 using Tapatalk
Most likely you booted into the OS then powered down then did the 3 button method which would make the samsung recovery overwrite the one you odin'd.
Do this odin the recovery.tar I linked then when you put the battery back in hold volume up+volume down then press power as well make sure you're holding all three at the same time no just two of them. If you go to the custom recovery good job if it boots into the OS try again there is no way it should boot into the 3e recovery if the recovery is being flashed via odin and says pass.
Yes ROM Manager is 100% useless for us fascinate users.
Okay, I did that after flashing it with Odin (without letting it boot the OS) and "CwM Lagfix 2.5.X" came up. I then tried rebooting the phone and didn't hold it down and then it went into the OS. I then shut it down, pulled the battery, and held all three buttons again, but it brought up the standard Android recovery system .
From what I understood the clockwork mod was permanent, but everything I've seen on my phone makes it only temporary. Am I doing something wrong?
2.5? That's an even older version. What link did you use? The one I gave you: http://forum.xda-developers.com/showthread.php?t=1046905 is a 3.x.
And yes, ROM Manager is essentially useless for our phone.
EDIT: You could always just ODIN the whole UKB 2.0 package, too, which will get you jump-started with CWM, a new kernel, and obviously the ROM itself:
http://www.mediafire.com/?a63v435opsaq3g3
Falcyn said:
2.5? That's an even older version. What link did you use? The one I gave you: http://forum.xda-developers.com/showthread.php?t=1046905 is a 3.x.
And yes, ROM Manager is essentially useless for our phone.
EDIT: You could always just ODIN the whole UKB 2.0 package, too, which will get you jump-started with CWM, a new kernel, and obviously the ROM itself:
http://www.mediafire.com/?a63v435opsaq3g3
Click to expand...
Click to collapse
Yeah, I first tried it with the package I was working with from the thread I linked to in the OP from here.
Doesn't matter, though, same thing happened. I used the package in the link you gave me, flashed it to the phone, rebooted into recovery, worked fine with 3.X, then rebooted it and let the OS load, then powered it off, then tried to reboot into recovery and I got the standard Android system recovery.
Unless I'm missing something this "Android recovery system <3e>" should never be seen again, but it seems like the CWM flashes I'm doing are volatile on OS loads.
I'll check out that link now.
FINALLY!
I installed UKB 2.0 and CWB worked at first...so then I hit "Reboot" and loaded the OS. The OS loaded (UKB) and then I held the power button, and hit "recovery mode." This restarted it, but it loaded into "Android recovery system" - I was about to kill somebody, but then I noticed it was 2e, not 3e. So I took the CWM 3.0 and flashed it back, and now, whether I hold all three buttons or hit "recovery mode" from the hold power menu in the OS, it boots into CWM 3.0.
I'd like to say I think I've seen the last of the Android recovery system - but I know I haven't .
The only thing I can't figure out is why it has ARS 2e AND CWM on it. Seems like they're direct replacements for one another...I would say the UKB 2.0 ROM shipped with just ARS 2e and that was that - but it showed the CWM 3.0 before I loaded the UKB OS.
Is the ARS sitting "under" the clock work mod? Or are they direct replacements for one another?
EDIT:
Also, which 2.0 ROM was that? I've been using this page as reference. That seems like the official page for that ROM. None of the 2.0 ROMs there are the link you gave me, though. I'm just curious if I should update the kernel or not, as the ROM either A) Didn't update it, or B) Included the same version. While I'm asking a question a second here, what is the PBJ setting and the OTB? I'm assuming OTB means out of the box, but I could be wrong, and I believe PBJ has something to do with power or under/overclocking, but I'm not quite sure..and even with the word android, google turns up lots of results for sandwiches under the query..
I do know that for a time we had to boot into the stock recovery, hit "update.zip," and then we'd reboot into CWM so at least at one time they did run side-by-side... but I honestly don't know if stock recovery is completely replaced now or if it just gets ignored.
Anyways, that was the official UKB/CR 2.0 ROM, but the ODIN file wasn't put together by TSM as it contains all the other components too. landshark68 packaged that up and his packages are all reliable.
As far as the kernel goes, the one included in what you flashed is a non-Voodoo PeanutButta Jelly Time kernel with a -50mv voltage reduction to help with battery life. That's a regular speed (1ghz) kernel.
Only The Brave (at first I thought it stood for Out of The Box too, go figure) is a more customizable kernel that can be both overclocked and voltage-reduced but starts out with neither.
I would recommend sticking with the PBJ kernels, personally, as they're actually good out of the box without having to play around with voltage controls manually.
The only reason you'd really want to switch kernels now is if you want to go to Voodoo... the PBJ kernel that ODIN file set you up with isn't.
The key to making cwm permanent is replacing the stock kernel. You can odin anything you want but if you leave the stock kernel it will overwrite your recovery every time it boots. Any of these custom kernels that are packaged in ukb roms should have the proper cwm included, but it may not hurt to update the recovery as new ones become available.
Sent from my SCH-I500 using XDA App
Syndacate said:
While I'm asking a question a second here, what is the PBJ setting and the OTB? I'm assuming OTB means out of the box, but I could be wrong, and I believe PBJ has something to do with power or under/overclocking, but I'm not quite sure..and even with the word android, google turns up lots of results for sandwiches under the query..
Click to expand...
Click to collapse
^^That's hysterical! Haha, I LOL'D when I saw that. I promise I'm not being an ass. PBJ stands for imnut's peanut butter jelly time kernel, and OTB stands for nemesis2all's Only The Brave kernel. If the package you flashed did not come with either one of those 2 custom kernels, you need to flash one. Either OTB 1.6 for Touchwiz based roms, or one of imnuts' PBJ kernels. Since I usually always use OTB, I'm more familiar with it and I know that it will permanently install CWM 3 for you upon installation and then you should no longer have any problems with stock recovery replacing your custom recovery. I'm pretty sure that PBJ does the same thing, but I dont know for sure as I havent used it. If you want full overclocking/undervolting abilities, you should probably flash OTB.. PBJ is not overclockable, I dont think, but again I could be wrong.. OTB gives you full control of voltage used for each frequency step available using the app "voltage control."
Oh, and voodoo, too. OTB kernels are all voodoo-enabled. Now you can run OTB kernels with voodoo disabled manually in recovery under the voodoo options, but with hiw good and reliable voodoo has become, and considering how much it speeds up your phone, im not really sure why anyone would use a galaxy s phone without voodoo or ext4 formatted partitions at least. But thats just me, as I realize some people prefer standard non-voodoo kernels.
To sum it up, I know for fact that using OTB kernels will replace stock recovery with CWM3 voodoo-enabled recovery, and you wont have it reflashing stock recovery like stock kernels do (which is the reason for the problems you were having).. PBJ might do the same thing, but im not sure because they're not voodoo kernels so I don't know if the PBJ kernels actually replace/update your recovery partition like OTB does. Either way, PBJ will not reflash stock recovery once you have a custom CWM kernel flashed, so as long as you do that you should be good to go.
Anyway, I hope you got it working right by now. I just thought that was utterly hysterical when I read that part about whenever you google for PBJ kernel that it comes up with a lot of results about sandwiches. Hahaha, that's classic.
Tbh this guy if he can't handle this stuff he will eventually brick his phone and cry bloody murder. Their is an all in one which I don't know why you didn't flash that.......
Sent from my SCH-I500 using Tapatalk
abrixxxx said:
Did you boot directly into recovery after putting your battery back in ? You can't boot into the OS before going straight to recovery from odin or else it overwrites the custom recovery with the samsung one.
Click to expand...
Click to collapse
I bet this is the source of much of your frustration.
You need to go straight to recovery and flash a kernel - the stocker is putting the samsung recovery in place before you get to cwm...
Swyped...
Falcyn said:
I do know that for a time we had to boot into the stock recovery, hit "update.zip," and then we'd reboot into CWM so at least at one time they did run side-by-side... but I honestly don't know if stock recovery is completely replaced now or if it just gets ignored.
Anyways, that was the official UKB/CR 2.0 ROM, but the ODIN file wasn't put together by TSM as it contains all the other components too. landshark68 packaged that up and his packages are all reliable.
As far as the kernel goes, the one included in what you flashed is a non-Voodoo PeanutButta Jelly Time kernel with a -50mv voltage reduction to help with battery life. That's a regular speed (1ghz) kernel.
Only The Brave (at first I thought it stood for Out of The Box too, go figure) is a more customizable kernel that can be both overclocked and voltage-reduced but starts out with neither.
I would recommend sticking with the PBJ kernels, personally, as they're actually good out of the box without having to play around with voltage controls manually.
The only reason you'd really want to switch kernels now is if you want to go to Voodoo... the PBJ kernel that ODIN file set you up with isn't.
Click to expand...
Click to collapse
Gotcha, now a Voodoo kernel just has the lagfix and other Voodoo project items bundled into the kernel?
garywojdan81 said:
The key to making cwm permanent is replacing the stock kernel. You can odin anything you want but if you leave the stock kernel it will overwrite your recovery every time it boots. Any of these custom kernels that are packaged in ukb roms should have the proper cwm included, but it may not hurt to update the recovery as new ones become available.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Gotcha, so now it's permanent (yay)
wilshyre said:
^^That's hysterical! Haha, I LOL'D when I saw that. I promise I'm not being an ass. PBJ stands for imnut's peanut butter jelly time kernel, and OTB stands for nemesis2all's Only The Brave kernel. If the package you flashed did not come with either one of those 2 custom kernels, you need to flash one. Either OTB 1.6 for Touchwiz based roms, or one of imnuts' PBJ kernels. Since I usually always use OTB, I'm more familiar with it and I know that it will permanently install CWM 3 for you upon installation and then you should no longer have any problems with stock recovery replacing your custom recovery. I'm pretty sure that PBJ does the same thing, but I dont know for sure as I havent used it. If you want full overclocking/undervolting abilities, you should probably flash OTB.. PBJ is not overclockable, I dont think, but again I could be wrong.. OTB gives you full control of voltage used for each frequency step available using the app "voltage control."
Oh, and voodoo, too. OTB kernels are all voodoo-enabled. Now you can run OTB kernels with voodoo disabled manually in recovery under the voodoo options, but with hiw good and reliable voodoo has become, and considering how much it speeds up your phone, im not really sure why anyone would use a galaxy s phone without voodoo or ext4 formatted partitions at least. But thats just me, as I realize some people prefer standard non-voodoo kernels.
To sum it up, I know for fact that using OTB kernels will replace stock recovery with CWM3 voodoo-enabled recovery, and you wont have it reflashing stock recovery like stock kernels do (which is the reason for the problems you were having).. PBJ might do the same thing, but im not sure because they're not voodoo kernels so I don't know if the PBJ kernels actually replace/update your recovery partition like OTB does. Either way, PBJ will not reflash stock recovery once you have a custom CWM kernel flashed, so as long as you do that you should be good to go.
Anyway, I hope you got it working right by now. I just thought that was utterly hysterical when I read that part about whenever you google for PBJ kernel that it comes up with a lot of results about sandwiches. Hahaha, that's classic.
Click to expand...
Click to collapse
Yeah, I think in PBJ it's set in stone, because there's different PBJ UKB ROM's with +/- voltages, so I'm guessing it's a packaged thing that's compiled into the ROM.
I believe I saw Voodoo in CWM on this Kernel. Guess it's just the OEM version with whatever PBJ fixes, and Voodoo packed into it.
Maybe at some point I'll try OTB, it definitely seems like a nice touch to be able to adjust your clock on the fly. Though I wonder if there was a particular reason why UKB only offered PBJ kernels and no OTB ones :-\.
tonu42 said:
Tbh this guy if he can't handle this stuff he will eventually brick his phone and cry bloody murder. Their is an all in one which I don't know why you didn't flash that.......
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Bite me.
I was "into the rooting game" for like 4 hours before making that post.
It's hard to just "pick up" random tid-bits of information from forum threads - because everybody uses TLA's and if you're new to it, you don't know what all those TLA's mean.
So while it's possible that I brick my phone at some point, that's a risk I'm taking, so in other words I should PM your ass in like a year when my contract is up and I get a new phone and tell it to stick it up your ass sideways.
AND, if you read (which you didn't), you'll see I already flashed the all in one and am running 2.1 perfectly stable now. Why did I not flash the all in one? I didn't know about the all in one. If I had, I probably would have done that a long time ago.
If you're not the one doing the hacking on the ROMs then 80% of the battle of "rooting/hacking android phones" is simply the act of knowing what's out there, different patches, compilations, images made by different people, issues, successes, etc. between different packages. So if you're like me, and busy, and can't always afford to read the latest and greatest, it puts you as a disadvantage.
So in short, shove it.
M00NEY said:
I bet this is the source of much of your frustration.
You need to go straight to recovery and flash a kernel - the stocker is putting the samsung recovery in place before you get to cwm...
Swyped...
Click to expand...
Click to collapse
Yeah, go figure . Didn't think the OS booting re-wrote the recovery partition/sector on boot, from an OS perspective, that's just weird.
I'm begging for someone to help me figure out what's going on with my Vibrant...but first, I've got to start out by admitting that I'm a total noob at this stuff--as much as I TRY to read/learn, I just don't seem to "get" it...I just wanted to make sure to make that clear before I tried explaining what my phone's been doing.
Okay, so, I updated to 2.2 the day it came out (months ago) & I'm rooted...(that's about as far as I've had the guts to go with it--I've never flashed a ROM or do anything else, simply because I was afraid I'd screw something up)...anyways, lately (for probably about 3-4 weeks now) my phone has dramatically slowed down, and now my home launchers (I've tried LPP, ADW, GO, & of course, the stock one) & some of my settings (mainly, the tones on my alarm clock & my ring tones) all keep resetting; my home screen will go blank and it takes several seconds to restart again...
I've done factory reset at least twice, I've uninstalled/reinstalled all the home launchers--even tried uninstalling all the other ones & just using the stock one...keeps happening. I've tried switching out my SD card--(I've got a brand new one in there now)--still nothing...I'm not sure what else I need to do--?
Could anybody PLEASE help me out before I throw my phone out the window--??!! ... THANK YOU!!!
I'd flash a new ROM. Don't be scared. Good luck!
Are you using a task killer? You might be inadvertently killing your launcher
Sent from my SGH-T959 using XDA App
it's being killed. Either from a task manager (boo) or more likely it's just ran out of memory. Are you playing pretty heavy games? Plants vs Zombies makes my ADW EX reset, also the other game from that developer... it does too.
Could just be an app that is a hog. Any certain apps you run often when it happens? Notice any certain apps draining the battery? You could try installing watchdog.. it looks for apps that are using a lot of memory.
if you question certain apps, you could uninstall and see.
when i was on stock 2.2 my notification volume reset itself from full to about half everytime i got a text (or sent 1)
hasnt on any custom rom iv'e been on
id odin back to stock and clear out some memory
I'd flash over CM7. The battery drain issue JUST got solved (nightly 39) so it's battery is on par with 2.2 stock now (or better!). Broken GPS but that's the only bug.
Performance is 3-4 TIMES faster in EVERYTHING. Yes....that's TIMES. It feels like an entirely new phone. Also, it looks much better than anything you'll see from stock....with many customization options for theme. Try it.
Flashing now is SUPER easy. I literally can flash CM7 on your phone in about 2 minutes (provided I download it before).
Simply go on Market and get ROM Manager
Flash Clockwork Recovery from ROM MANAGER.
Download latest CM7
Put CM7 file on phone memory
Reboot into clockwork recovery
Install CM7 from clockwork
Wait till phone boots.
It can be useful to make a backup from Clockwork before you flash so if u **** up, you can go back. No harm done.
I had originally downloaded advanced task killer--but I uninstalled it months ago; I've also uninstalled anything that seemed to be eating up memory...but, it does seem to stay low anyways; I don't have anything that runs in the background, however, that I haven't always had running back when it was working okay--? I'm not sure what I'm missing though...
And, yes--I'm SUCH a chicken about flashing another ROM, simply because everything I've read on here has pretty much "scared" me out of trying it! I've downloaded ROM manager a few months ago, but (and I don't remember exactly which part I had the issue with) I tried to make a nandroid & it wouldn't let me...so I pretty much gave up--but, now that I'm having these problems, I may go back & read everything & (hopefully) try it all again...so, in other words, Stay Tuned--(in case I need some help! haha!)...
Don't be scared.
Nandroid backups are made in recovery. Use ROM manager to flash recovery. In recovery after reinstalling packages and getting green or red recovery use the backup and restore option to create ur back up (that's ur nandroid). This flashing situation is really easy if you read. These are good guys here if you need help they will be more than willing to help you. Good luck!
Task killers are garbage and down with @akaskriller
Sent from my GT-I9000 using XDA Premium App
Yes just post questions if needed. The procedure like I said is really simply and the benefits are huge. But do read some stuff, it's always good to know it
Okaaaaaay...so, I'm just now (yes, a month and a half later) getting some time to sit down and attempt to "fix" my phone... I ODIN'ed back to stock 2.1--but now, I can't get root...?! I've copied update files from XDA into my phone, which, I'm assuming I've done correctly...??--(I told y'all I was a noob)...then, did the whole push the volume keys + power button maneuver--but when I tried to re-install packages, it tells me it's not there or they can't be opened...I've tried re-doing all this MANY times today without any luck...
Now, originally I had used SuperOne Click to get root--but that was after I had updated to 2.2...but everything I've looked at for to get root on 2.1, I don't see anything mentioned about using SuperOne Click...? Help me out guys--I'm getting crossed-eyed over here...
Thank you, thank you, THANK YOU
Sent from my SGH-T959 using XDA Premium App
Here's how to flash.
1. ODIN (You've done that already).
2. Use SuperOneClick to root the phone (read here how to use it) http://forum.xda-developers.com/showthread.php?t=803682. You need Development enabled on the phone and plugged to your computer to do it. READ that topic I listed carefully if you are confused on how to root it.
3. Install ROM Manager from the Market, then flash Clockwork Recovery (select Vibrant (MTD) for Clockwork version). Now you are free to flash ROMs.
4. If flashing to CM7, download the latest nightly
(http://cm-nightlies.appspot.com/?device=vibrantmtd), put that on your phone via the USB cable. Put it on the phone memory, not on ur external SD card.
5. Reboot into recovery (Hold Power + Volume up + Volume down as you reboot the phone). Select re-install packages twice. Now that will get you into Clockwork recovery mod if you did step 3.
6. Select Install from zip card, find the CM7 ROM file you put on your phone and flash it. Wait till done.
7. Reboot phone, you now have CM7. Boot it up and let it sit for 5 minutes (do not touch it, its doing setup stuff).
8. Open the program ROM Manager (its installed by default). For Recovery, select Vibrant MTD 3.0x I think. Then select Download ROM, find the Google Apps package.
9. After downloading the Google Apps package, install it. You can do it straight from ROM Manager, it will ask you for root and then reboot into recovery and do it automatically.
10. You are done, you can now restore apps or set the phone how you like for usage.
OPTIONALLY you can install additional kernels and modems for better battery/coverage. The recommended modem is KB5 for CM7.1 as for kernel, if you want to upgrade, I'd recommend the latest Glitch CM7 kernel beta (fully stable).
NOTE, your GPS likely will not work in CM7. Be ready for that if you go this way.
Wow, seriously--Thaaaank You x110! I'll let you know how it goes!
Sent from my SGH-T959 using XDA Premium App
Here is the udate.zip to root:
http://forum.xda-developers.com/showthread.php?t=723479
(click the QR code and download, thats slick)
That needs to be placed on the internal SD, NOT in any folder, just sitting out on it's own. Open any file manager and make sure its there. At this point find the ROM you eventually wanna flash and place it on the internal SD as well. I like to make a folder named "ROM" and put all my ROM's in there.
After you ODIN when you boot into recovery it should be blue. SWEET!
- Reinstall Packages(do this until you get green recovery)
- apply update zip(do this in green recovery)
- Now flash the ROM you have already placed onto the internal SD. It is important to only flash once you get the green recovery.
Good luck!
okay, for either one of the ways...do i want debugging on or off--? (i'm assuming that "matters"--?)
HA! Nevermind... 0
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
I just rooted my Canadian Note, with some help from some awesome people here on XDA. And I was wondering if I can use Rom Manager, to backup, and restore my Note?
I did backups and restoring on my old HTC Desire HD, but I just wanna make sure that Roms Manager, supports my Note specifically.
If someone can confirm this, I'd be extremely grateful! ت
Model: SGH-I717D
Version: 4.0.4
Kernel: 3.0.8-perf
Adizzzle said:
I just rooted my Canadian Note, with some help from some awesome people here on XDA. And I was wondering if I can use Rom Manager, to backup, and restore my Note?
I did backups and restoring on my old HTC Desire HD, but I just wanna make sure that Roms Manager, supports my Note specifically.
If someone can confirm this, I'd be extremely grateful! ت
Model: SGH-I717D
Version: 4.0.4
Kernel: 3.0.8-perf
Click to expand...
Click to collapse
you can...But
I've always prefered the recovery for a restore of backups, and to create them. Recovery is fool proof, and will provide the type of files it can read. but when using apps to perform a recovery function, the risk goes up.
Rom manager is a good app, but I have had issues with it in the past, and do not use it now....g
So all in all, its better to use CWM for backing up, and restoring, as apposed to using an app like "Rom Manager"?
Thanks again gregsarg. You've been super helpful!
Model: SGH-I717D
Version: 4.0.4
Kernel: 3.0.8-perf
Adizzzle said:
So all in all, its better to use CWM for backing up, and restoring, as apposed to using an app like "Rom Manager"?
Thanks again gregsarg. You've been super helpful!
Model: SGH-I717D
Version: 4.0.4
Kernel: 3.0.8-perf
Click to expand...
Click to collapse
I believe so, yes...:good:
any time you rely on an app, to perform a function, you are relying on the build parameters of the app. and since there are sooooo many variables in software etc. you can get errors.
Recovery is a good choice for creating a solid backup...IMHO
Have you personally tried a back up using CWM on the Galaxy Note i717d? Just out of curiousity.
(⊙~⊙)
Adizzzle said:
Have you personally tried a back up using CWM on the Galaxy Note i717d? Just out of curiousity.
(⊙~⊙)
Click to expand...
Click to collapse
More times than you can count, on the SGH-I717 (ATT) and the N7000 (international) note.
CWM operation is the same for both....and they both run and restore well using this method....g
Everybody flashing the custom rom uses either CWM or TWRP to create backups before they flash.
If you rely on Rom Manager, and a rom goes bad (like they sometimes do), you won't be able to boot and use Rom Manager.
Recovery can be accessed even if your rom flash is bad.
and now you see the method to my madness.....
Use recovery, and life will be "much" better......g
Thanks guys, I'm astounded by how awesomely helpful everyone is here at XDA, you both have my thanks, many times over. ت
Furshizzzle Adizzzle
Adizzzle said:
Thanks guys, I'm astounded by how awesomely helpful everyone is here at XDA, you both have my thanks, many times over. ت
Furshizzzle Adizzzle
Click to expand...
Click to collapse
And I'll say it again. This is a perfect example of what XDA is about in my book. Everyone helping everyone make their devices better than they were when we bought them. :thumbup::thumbup::thumbup::thumbup::thumbup:
Adizzzle said:
Thanks guys, I'm astounded by how awesomely helpful everyone is here at XDA, you both have my thanks, many times over. ت
Furshizzzle Adizzzle
Click to expand...
Click to collapse
Always welcome ....g
Confused.
Okay, all of you here have totally confused me. I have used CWM Recovery for a while now and decided to try ROM Manager. As far as I can tell RM only allows you to flash CWM updates and collect information and input that info into CWM. I will say that the installation of CWM-Touch has an issue but that might be my own doing. I can live with the old version though.
ie: If you want to install a new ROM, you pick if from your SD card and RM boots you into CWM and it does its thing. You want to make a BU...? Just push that button and it boots into CWM and boom...its done. (It also asks you if you want to do the wipes.)
I can still do all this by booting into CWM manually without using RM...so I don't get why some of you say not to use it (ROM Manager.) It does the same thing but as far as I can tell it does not prevent or change Manual operation in CWM in any way.
I don't see the problem here. Please correct me if I'm wrong...and some theory too if you can.
Try running a CWM restore , using rom manager , when your phone won't boot due to a corrupt or incorrect flash....
The point is ...it isn't gonna happen...as rom manager is an onboard app.
And in my opinion, one that users depend on far to much....
We are simply eliminating that potential problem area ...but hey ...use it if you want....I'll use recovery ....g
gregsarg said:
Try running a CWM restore , using rom manager , when your phone won't boot due to a corrupt or incorrect flash....
The point is ...it isn't gonna happen...as rom manager is an onboard app.
And in my opinion, one that users depend on far to much....
We are simply eliminating that potential problem area ...but hey ...use it if you want....I'll use recovery ....g
Click to expand...
Click to collapse
Okay, maybe there is a mistake in terminology here.
My point is that you don't have to use Rom Manager to get into CWM Recovery. You can use it--or not...ie" If I can't get to CWM from the ROM, I just do the volume + - and power as usual. So I don't get "your" point. Once CWM is installed it can be accessed by either method. I have done it both ways with no issues so far. I'm not arguing with you I'm just trying to understand what I might be missing.
When a new samsung phone is released to the public, the first thing developers do is try to change the stock 3e recovery with CWM so they can do the next step -- flash a rooted kernel. Two things we can't live wirhout.
Next, app developers step in and create apps that make the operating system more accessible -- like Rom Manager.
With the note, CWM (and now TWRP) and root came pretty fast after the release because it is very similar to all the Galaxy S phones. But Rom Manager didn't get done for a while, but in the meantime users installed it and borked their phones by overwriting CWM with recovery from other phones. When that got fixed, the nandroid feature didn't work either, so people experemented with roms without realizing they didn't have backups.
There are lots of people who never check a date of a thread and all that old stuff and outdated advice is still floating around causing havoc.
So like all threads helping someone troubleshoot their phone, you eliminate the known causes of trouble one step at a time.
Use what works for you.
Roger_15 said:
Okay, maybe there is a mistake in terminology here.
My point is that you don't have to use Rom Manager to get into CWM Recovery. You can use it--or not...ie" If I can't get to CWM from the ROM, I just do the volume + - and power as usual. So I don't get "your" point. Once CWM is installed it can be accessed by either method. I have done it both ways with no issues so far. I'm not arguing with you I'm just trying to understand what I might be missing.
Click to expand...
Click to collapse
Understood ...
I realize that CWM is accessed by rom manager, and I also understand that the device doesn't need it to access recovery.
As ranger said, it was risky at first to use RM , and it has since been repaired for the note.
My point is, rom manager is a step in the process that can stop folks from getting to recovery through the rom. (If the phone goes wonky) And you would be amazed at how many people can't manually boot to recovery.
My personal time spent with rom manager has caused me to "not " use it. My days on HTC were horrid with that app. And it has corrupted more than 1 recovery for me.
Of course , the choice is yours to use it .....it's okay, but a step that can cause huge problems....
And I encourage new users to learn the traditional method.....g
Many thanks to the two of you,very good answers. Sorry to push this but i have seen posts that say parts of what you said but never a good reason for their comments.
Thanks again.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
I'm glad to explain it. A history lesson is usually helpful.
I started with CWM but then switched to TWRP, they just released an update and you can get it from GooManager App. I like TWRP better.
The only catch is you cannot restore backups created by one recovery with the other. You will have to reflash the recovery who's backups you want to restore.