I am just wondering if whether or not I should or need to be going back to stock when installing new ROMs or if I should just disable Voodoo or if I even need to do that.
It seems with newer ROMs the updates dont require you to disable Voodoo, just flash over. But what if I want to go from Bionix V to Auxura 2.2.9.0? Do I need to go back to stock and then root/flash? Or will just disabling Voodoo work? Or should I just flash and go?
I have searched and see different ways to do things but not a clear answer on if I should be doing that or if its necessary when going between ROMs.
Also if I have overlooked a thread on this I think it should be stickied or in the NOOB guide.
Thanks.
Your going to get different opinions on this. If your going to flash the newest version of the rom your on then there is really no need to odin. If your going to a.completely different rom then yes go ahead and odin. Of course its never a bad idea to start fresh.
Powered by Axura with a dash of Voodoo
If you Odin back to stock you lose all information including titanium backup right? You really are starting from scratch if you do this correct?
se1zure31 said:
If you Odin back to stock you lose all information including titanium backup right? You really are starting from scratch if you do this correct?
Click to expand...
Click to collapse
No. You will still have your files when you odin.
It's safer to disable voodoo then odin then flash custom rom. Well that's what i do, though you can odin without disabling voodoo.
iynfynity said:
No. You will still have your files when you odin.
It's safer to disable voodoo then odin then flash custom rom. Well that's what i do, though you can odin without disabling voodoo.
Click to expand...
Click to collapse
Thanks for the quick reply! I am still new to loading custom ROMs on this. I am coming from the HD2 which was the easiest phone to load custom ROMs on I think.
Another tidbit of advice, if you're updating a rom (e.g. going from Axura 2.2.7.2 to Axura 2.2.9.0) you don't need to disable Voodoo.
Even if you're changing roms (e.g. TW Bionix-V to Axura 2.2.9.0) in theory, you shouldn't need to disable Voodoo, I've done it successfully. This works because both are running Voodoo v5.x and up, and both roms have Voodoo enabled off the bat.
Some older roms running Voodoo V4.x CANNOT be flashed over each other and Voodoo must be disabled before flashing.
There's no real harm in disabling Voodoo and flashing over it, but if you forget, the worse that's going to happen is you'll have to odin back to stock.
I have never odin to stock before applying another rom and have not had any issues. I always disable voodoo and wipe/factory reset before applying a new rom. I think odining to stock to apply a different rom is waste of time and not needed. Look at the directions of installing Flagship and that's the best way to go from rom to rom.
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 wondering how I can get CWM back on my stock gingerbread fascinate now... I used the speedmod kernel to root, which had CWM built in. Then I replace it with stock GB kernel.. which has 3e recovery.
When I run ROM manager now with gingerbread the fascinate don't come up in the list no more.. there are 2 i9000's, one of those is a MTD... and 2 others. 4 in total.
I have the update.zip file which I downloaded from Rom Manager when I was on Froyo. Will that work? I'm afraid to try.
I've also seen methods of ADB pushing the recovery.bin over the current 3e. I just really not to sure which is the best way to do it, and I've done so much reading now it's got me confused.
Thx
Maniac
MrManiacNF said:
I'm wondering how I can get CWM back on my stock gingerbread fascinate now... I used the speedmod kernel to root, which had CWM built in. Then I replace it with stock GB kernel.. which has 3e recovery.
When I run ROM manager now with gingerbread the fascinate don't come up in the list no more.. there are 2 i9000's, one of those is a MTD... and 2 others. 4 in total.
I have the update.zip file which I downloaded from Rom Manager when I was on Froyo. Will that work? I'm afraid to try.
I've also seen methods of ADB pushing the recovery.bin over the current 3e. I just really not to sure which is the best way to do it, and I've done so much reading now it's got me confused.
Thx
Maniac
Click to expand...
Click to collapse
Second that - in the same boat.
As I understand it, it's a bootloader issue to install CM7 on Gingerbread. Downgrade to 2.2 and flash away!
Rabid_Gypsy said:
As I understand it, it's a bootloader issue to install CM7 on Gingerbread. Downgrade to 2.2 and flash away!
Click to expand...
Click to collapse
I don't want CM, I want to get clockwork recovery on my stock gingerbread.
I'm also in the same Boat. It would be nice to get clockwork recovery installed.
I have successfully rooted Gingerbread, part of the process is to flash the the Speedmod kernel first. With the Speedmod kernel, it has clockwork on it which you can boot into but unfortunately your phone cannot normally boot with that kernel.
I'm loving Gingerbread right now, it is so much smoother then 2.2, there is no way I want to go back to 2.2.
iwebsource said:
I'm also in the same Boat. It would be nice to get clockwork recovery installed.
I have successfully rooted Gingerbread, part of the process is to flash the the Speedmod kernel first. With the Speedmod kernel, it has clockwork on it which you can boot into but unfortunately your phone cannot normally boot with that kernel.
I'm loving Gingerbread right now, it is so much smoother then 2.2, there is no way I want to go back to 2.2.
Click to expand...
Click to collapse
Right there with you - so much better than 2.2 EVEN with lagfix running - was very thankful for ROOT but would love CWM recovery back - very useful tool.
I don't know if it was this thread I made the post, but something I did mention that I did was...
When I used the speedmod kernel to root the phone, I made a nandroid backup. Then I flashed the stock kernel back. I'm assuming if I wanted to restore my phone with the backup I could just flash the speedmod kernel back, restore by backup, then flash the stock kernel back again.
I don't know if clockwork is programmed to backup certain partitions, or if its dynamic, but I'm tempted to try my restore, but at the same time I don't want to go through all the updating agan.
Another thing, I have the 3 ODIN CWM file, the purple, blue, and no color ones you find on here. If you extract those you get a recovery.bin file, and there is no zimage (kernel). If you take one of those clockworkmods with no kernel and overwrite the stock recovery.bin in the phone, shouldn't that work?
I'm still new to android, first time I laid hands on one was this june, I'm still new, but I'm a fast learner too, but I want to figure this one out.
-Maniac
MrManiacNF said:
I don't know if it was this thread I made the post, but something I did mention that I did was...
When I used the speedmod kernel to root the phone, I made a nandroid backup. Then I flashed the stock kernel back. I'm assuming if I wanted to restore my phone with the backup I could just flash the speedmod kernel back, restore by backup, then flash the stock kernel back again.
I don't know if clockwork is programmed to backup certain partitions, or if its dynamic, but I'm tempted to try my restore, but at the same time I don't want to go through all the updating agan.
Another thing, I have the 3 ODIN CWM file, the purple, blue, and no color ones you find on here. If you extract those you get a recovery.bin file, and there is no zimage (kernel). If you take one of those clockworkmods with no kernel and overwrite the stock recovery.bin in the phone, shouldn't that work?
I'm still new to android, first time I laid hands on one was this june, I'm still new, but I'm a fast learner too, but I want to figure this one out.
-Maniac
Click to expand...
Click to collapse
Hey MrManiacNF,
Thanks for the idea, I guess it is a work around for now until we are able to get CWM installed on Gingerbread.
I ended up flashing the speedmod kernal back on, booted into CWM and made a full nandroid backup. Reflashed the stock gingerbread kernal back and booted up as normal.
Yea I do the same thing, I mean you can't make a backup without a pc to flash with, but a backup is better then none.
No love from ROM Manager
Saw ROM Manager had a few updates, but still seeing the limited device selection when trying to create a custom recovery, and still fails with the unsigned zip.
Just wanted to post that if anyone was wondering if recent updates corrected anything, as they have not (at least for me).
I can also confirm, actually no new phones added to the list. I've also tried an app call Root Toolbox Pro. It has options to backup your recovery or flash another. I tried flashing the fascinate-3.0.0.8.zip that I had from Rom Manager from Froyo. No luck, just hung at boot. Had to re-flash stock kernel in odin to fix.