There seems to be a bit of confusion on what recovery we should be using. Most threads indicate CWM 3.x
This post is often referenced as the most current recovery for our needs:
http://forum.xda-developers.com/showpost.php?p=13128524&postcount=1
It can be seen being referenced here:
http://forum.xda-developers.com/showpost.php?p=14892705&postcount=1
Then there is this:
http://forum.xda-developers.com/showpost.php?p=14940474&postcount=202
I have not seen many references to CWM 4.x recovery. Is this for gingerbread roms?
Please understand I am not trying to "shake the bees nest" or anything. I just want to make sure we are doing things correctly. I have been doing some research since the above post was made and have come up with conflicting resulsts, looking for clarification. Thanks.
I sent ti a pm asking about this myself - still waiting to hear back.
Another Fascinating post by my XDA app...
Hmmm 74 views, either no one knows or no one is talking! The mystery grows....
Sent from my SCH-I500 using XDA Premium App
I have been unsuccessful at finding a v4 recovery for anything but CM/AOSP for our phones.
Of course, I have not dedicated much time to the search as my current one seems to be fine.
PhoenixPath said:
I have been unsuccessful at finding a v4 recovery for anything but CM/AOSP for our phones.
Of course, I have not dedicated much time to the search as my current one seems to be fine.
Click to expand...
Click to collapse
I thought my current DINOSAUR recovery was fine too. . .someone out there must know.
Perhaps he was just kidding? or wrong and now does not want to talk about it?
(putting on beekeeper suit)
Just use 4.x
https://github.com/imnuts/android_bootable_recovery
nunyazz said:
Just use 4.x
https://github.com/imnuts/android_bootable_recovery
Click to expand...
Click to collapse
when I downloaded this, it was recovery-clockwork-3.0.0.8-fascinate, so what is 4.x about it? My recovery is the yellow 3.2.0.0 - any available upgrade?
i dunno, it said "CWM Voodoo Lagfix Recovery v4.0.0.1 " in the description. Mine is yellow also, works for all the roms I've tried.
nunyazz said:
i dunno, it said "CWM Voodoo Lagfix Recovery v4.0.0.1 " in the description. Mine is yellow also, works for all the roms I've tried.
Click to expand...
Click to collapse
So I guess we can assume that 4.x is fully backwards compatible with older roms?
I just don't understand how we could be snipped at for not using CMR 4.x when it is not even on his own recovery page (or widely referenced anywhere else).
Don't half tell us something then not back up your claims. It seems this stupid GB leak did nothing but make people crabby! (from day one)
I'm on CM7 with CWM4. I would think CWM3 is fine with TW roms if it still flashes everything and last I know it did. If CWM4 was something you should have there would probably be posts for it in the dev section.
Keithn said:
I'm on CM7 with CWM4. I would think CWM3 is fine with TW roms if it still flashes everything and last I know it did. If CWM4 was something you should have there would probably be posts for it in the dev section.
Click to expand...
Click to collapse
Ummm... that's my point. Did you follow the links in the OP? especially the last one. That is where the confusion came from.
Sent from my SCH-I500 using XDA Premium App
I guess I'd have to look into it but I didn't know of any major differences such as those between CWM2 and 3. So I don't know why it would be a huge deal to use CWM3 if I figure anything out I'll post.
CWM 3.0 may be responsible (but probably isn't) for the sd cards being borked by some of those who've flashed the EC09 GB leak or the early ROMs based on it. That might be why times_infinity made his dinosaur post. That said, it's more likely that the SD card issue is strictly an EC09 issue having nothing to do with which recovery you use. I suggest going on IRC to find your answers (I think either #samsungfascinate or #teamsbrissenmod or maybe #tsm).
Another Fascinating post by my XDA app...
nunyazz said:
Just use 4.x
https://github.com/imnuts/android_bootable_recovery
Click to expand...
Click to collapse
The idiot needs help (that's me). Does anything need to be done to the files after download? I assume you can't just flash the .zip, it couldn't be that simple.
Related
I feel like this is a pretty big deal for us, or perhaps I am reading this wrong? It looks like last nights big 6.1 update for the Cyanogen mod now supports the Samsung Fascinate! Anyone tried it yet?
http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Samsung_Galaxy_S_(Fascinate)
NOTE: ClockworkMod Recovery is currently not available for the Samsung Fascinate.
Last update October 9th.
Sorry... You must have missed these parts.
PhoenixPath said:
NOTE: ClockworkMod Recovery is currently not available for the Samsung Fascinate.
Last update October 9th.
Sorry... You must have missed these parts.
Click to expand...
Click to collapse
Ugh, I'm an idiot, anyway to delete this thread?
tlogank said:
I feel like this is a pretty big deal for us, or perhaps I am reading this wrong? It looks like last nights big 6.1 update for the Cyanogen mod now supports the Samsung Fascinate! Anyone tried it yet?
http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Samsung_Galaxy_S_(Fascinate)
Click to expand...
Click to collapse
If you read a little further down:
Flashing CyanogenMod
NOTE: As of right now CyanogenMod is not available for the Samsung Fascinate. Please check the wiki or the Samsung Galaxy S sub-forum for updates.
So far, only root instructions seem to be there.
Clockwork Mod Recovery
I am confused?? I follwed the instruction and d/l Rom Manager and flashed recovery. I am able to enter into clockwork mod recovery just fine, I have made several Nandroids using this. ??? Am I misreading this post??
denonlake said:
I am confused?? I follwed the instruction and d/l Rom Manager and flashed recovery. I am able to enter into clockwork mod recovery just fine, I have made several Nandroids using this. ??? Am I misreading this post??
Click to expand...
Click to collapse
No, you are not. The issue is that Clockwork can't read (and therefore wipe or backup) the ext4 partition that voodoo puts our data in. It might not be able to read RFS as well, I am not sure.
Sent from my Fascinate using the XDA app
suppliesidejesus said:
No, you are not. The issue is that Clockwork can't read (and therefore wipe or backup) the ext4 partition that voodoo puts our data in. It might not be able to read RFS as well, I am not sure.
Sent from my Fascinate using the XDA app
Click to expand...
Click to collapse
So since im voodooless im good? Still running stock woth only bloat removed , bing removed And google added
Sent from my SCH-I500 using Tapatalk
denonlake said:
So since im voodooless im good? Still running stock woth only bloat removed , bing removed And google added
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
I doubt that is the case, but I as well do not fully understand what Jesus here is trying to say, I will leave it up to him for further explanation.
As a side note, I would be thrilled if they released Cyanogen for the Fascinate, that would be fantastic.
The issue is that Cyanogen is based off 2.2 (Froyo) and the Fascinate does not have a 2.2 kernel yet.
I was on their wiki last night and almost made the same mistake until I read that part. I was all excited and was thinking, "How did no one see this"
then I punched myself in the face
Whoa -
As near as I can count, you guys are talking about three different things:
1) Clockwork Recovery is definitely available for the Fascinate, and has been for a while.
2) Clockwork Recovery and Cyanogenmod are different things.
3) The issue with Clockwork Recovery not reading Nandroid backups ONLY applies if Voodoo is installed and enabled. Supplysidejesus covered this correctly.
Martian21 got it right in that Cyanogenmod 6.* is based on Android 2.2, so we won't be seeing it until Samsung pushes a 2.2 update.
The good news is that Koush has expressed a willingness to work on the CM port when there is some Froyo source to work from.
Good things will come in time!
Zennmaster said:
The good news is that Koush has expressed a willingness to work on the CM port when there is some Froyo source to work from.
Good things will come in time!
Click to expand...
Click to collapse
I don't think I would get too excited on that one..
Being a former Droid Inc user, I would personally rather get another CM guy on it.
Koush does SO MUCH for the community that I think he's spread too thin to give this device the full attention that it will need. I am not knocking him, he's awesome and done a ton. With his new company he works for and all the rom manager items and things for clockwork recoveries, I just don't see him working on this one.
what would be great is if a team of devs worked on the CM part when the time comes instead of a one man show.
dnoyeb said:
what would be great is if a team of devs worked on the CM part when the time comes instead of a one man show.
Click to expand...
Click to collapse
That would be great. It sucks that there are so many people out there eager to help, but no way to *quickly* get the skills it takes to help? I wish it was as easy as watching a youtube video on what to do - I know there are some, but it seems like something's missing?
PhoenixPath said:
NOTE: ClockworkMod Recovery is currently not available for the Samsung Fascinate.
Last update October 9th.
Sorry... You must have missed these parts.
Click to expand...
Click to collapse
It also say's "NOTE: ClockworkMod Recovery is currently not available for the Samsung Fascinate. Please check the wiki or follow clockwordmod on Twitter for updates.", but i am running 2.5.1.0 via rom manager as we speak? Very intersting...
...
Recovery doesn't require 2.2.
I don't know anything about developing but I just read on wesgarner's twitter that the source for the galaxy s CM6 is now available, does that mean anything to us fascinate users?
Sent from my SCH-I500 using XDA App
adianlorenzana said:
I doubt that is the case, but I as well do not fully understand what Jesus here is trying to say, I will leave it up to him for further explanation.
As a side note, I would be thrilled if they released Cyanogen for the Fascinate, that would be fantastic.
Click to expand...
Click to collapse
Not sure how else to explain it, but I will try.
By default, Samsung places the /data/ partition of the phone in a file system called RFS. It is slow and inefficient, so the guys over at the Voodoo project created the lagfix which converts the partition to ext4, which is a MUCH faster file system, and makes accessing and using our apps much more efficient.
The only problem with this and Clockwork Recovery is that Clockwork does not have the capability to READ the ext4 partition that the Voodoo lagfix creates. So, when you do a nandroid with Clockwork, it will backup everything it is supposed to backup EXCEPT the ext4 data partition. That is the issue we have with Clockwork. Until Koush adds support for ext4, we are kind of dead in the water for a complete nandroid backup.
That's all I was saying.
Like I said, I'm also not sure if Clockwork can read the default RFS partition - someone would have to confirm or dis-confirm that for me.
Wish I was knew more. I have a lot of the infrastructure info down, I think, just no good with code and programming.
Bleh.
Clockwork can backup the /data partition on a stock Galaxy S. That is why you have to diable Voodoo in order to do a full Nandroid then you can re-enable it.
As was stated earlier Koush has said that he will port CM6+ to the Fasinate once 2.2 source is availalble. to try to work from 2.1, while possible, would be a wasted effort with 2.2 so close. All Koush needs to do is lay the foundation for CM6, there are dozens of other talented devs who can take that work and build on it. Don't fear - CM6 will come and will be actively suported by many devs. I'd be willing to bet that once Voodoo is officially released for the Fascinate Koush will add support in ClockworkMod recovery.
dnoyeb said:
what would be great is if a team of devs worked on the CM part when the time comes instead of a one man show.
Click to expand...
Click to collapse
The contemporary users of open source software are so weird.
"A Team" - show 'em the money!
Holy thread resurrection bat man!
Sent from my SCH-I500 using XDA App
So I flashed nero v3 a few days ago. How would I go about flashing to v5. Would I have to odin back to stock then go to v5 or can I just flash straight from v3.
newageoutlaw said:
So I flashed nero v3 a few days ago. How would I go about flashing to v5. Would I have to odin back to stock then go to v5 or can I just flash straight from v3.
Click to expand...
Click to collapse
I never odin back and have never had issues. You can just flash over it. If there are a lot of bugs you can flash or odin back to stock and then flash the new Rom. Just be sure to disable voodoo if you go back to stock. Also, make sure any time you flash a new Rom to let it sit for 10 min then reboot to eliminate bugs and smooth it out. Hope this helps.
Sent from my SGH-T959 using XDA App
DCrozier28 said:
I never odin back and have never had issues. You can just flash over it. If there are a lot of bugs you can flash or odin back to stock and then flash the new Rom. Just be sure to disable voodoo if you go back to stock. Also, make sure any time you flash a new Rom to let it sit for 10 min then reboot to eliminate bugs and smooth it out. Hope this helps.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
+1 except for the never Odin back part. Not that DCrozier28 is wrong but I always do it. The developers will usually tell you if it's necessary or not. For the most part dev to dev is pretty safe but for instance V5 was written purely based on KA5 so it might have some bugs flashing over V3 which was designed before KA5 was released.
To some Odin is an unnecessary step to me it's more peace of mind and an extra 5 minutes.
I have also found I have WAY more success to on the letting the ROM sit after 1st boot then reboot. Some roms and phones don't immediately load and situate everything, a good 10-15 minutes then reboot ensures everything is where it needs to be before you start loading stuff back up.
I had this same question, glad I found this post.
Also whats the best way to backup sms? I am just assuming use titanium and then restore once the new rom is there?
One thing I missed about my Touch Pro 2 was microsoft my phone. It was a easy backup and sync. I am still fairly new to android but there has got to be something similar.
tecjunkie said:
I had this same question, glad I found this post.
Also whats the best way to backup sms? I am just assuming use titanium and then restore once the new rom is there?
One thing I missed about my Touch Pro 2 was microsoft my phone. It was a easy backup and sync. I am still fairly new to android but there has got to be something similar.
Click to expand...
Click to collapse
I have never used titanium but there is a free app in the marketplace called SMS backup and it had always worked for me. Hope this helps...
Sent from my SGH-T959 using XDA App
tecjunkie said:
I had this same question, glad I found this post.
Also whats the best way to backup sms? I am just assuming use titanium and then restore once the new rom is there?
One thing I missed about my Touch Pro 2 was microsoft my phone. It was a easy backup and sync. I am still fairly new to android but there has got to be something similar.
Click to expand...
Click to collapse
i use Go SMS app and it has an option to backup all your current sms in xml format which can be restored.
If it wipes every thing is there really a need to odin?
I never have and haven't had an issue.
Sent from my SGS Vibrant
ender0506 said:
I have never used titanium but there is a free app in the marketplace called SMS backup and it had always worked for me. Hope this helps...
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
which sms backup do you use? I see so many.
tissimo said:
If it wipes every thing is there really a need to odin?
I never have and haven't had an issue.
Sent from my SGS Vibrant
Click to expand...
Click to collapse
Like post above it could be Rom specific. Some debate may say to odin to stock but they will probably list it. I have flashed different roms over another with out ever odin to stock and never had an issue. Or at least issues that really bothered. Seems like its all about personal experience and opinion/preference.
Sent from my SGH-T959 using XDA App
tecjunkie said:
which sms backup do you use? I see so many.
Click to expand...
Click to collapse
I used the one from michele valentini
Sent from my SGH-T959 using XDA App
newageoutlaw said:
So I flashed nero v3 a few days ago. How would I go about flashing to v5. Would I have to odin back to stock then go to v5 or can I just flash straight from v3.
Click to expand...
Click to collapse
hmmm. maybe start by reading the first post in the nero v5 thread. you know where it has the download link for nero v5 and tells you how to flash it....
tissimo said:
If it wipes every thing is there really a need to odin?
Click to expand...
Click to collapse
no, but logic has never stopped people from being redundant before....
blizzard1017 said:
+1 except for the never Odin back part. Not that DCrozier28 is wrong but I always do it. The developers will usually tell you if it's necessary or not. For the most part dev to dev is pretty safe but for instance V5 was written purely based on KA5 so it might have some bugs flashing over V3 which was designed before KA5 was released.
Click to expand...
Click to collapse
i'm sorry, but that's not a good reason. sure, v3 (jl5) was written before ka5 was released, but you know what else was? jfd and ji6. the rom wipes, so it doesn't matter what the previous version was.
funeralthirst said:
i'm sorry, but that's not a good reason. sure, v3 (jl5) was written before ka5 was released, but you know what else was? jfd and ji6. the rom wipes, so it doesn't matter what the previous version was.
Click to expand...
Click to collapse
It's been stated it's a matter of personal preference and opinion unless the developer states otherwise. I personally don't mind taking 5 extra minutes to do the to make sure everything is wiped. The above was just one of hundreds of reasons, I can pick another. I have also PERSONALLY flashed ROM over ROM and had issues. If you have not then you are the almighty among us and I worship thee and will build a golden shrine in your honor.
Every single ROM posted has a disclaimer about it messing up your phone. So in allll due respect to the truly talented developers; these ROM are consistently not perfect ports of official releases and cannot be confirmed as a perfect flash overs once they hit the masses.
My SUGGESTION to a nooby(no disrespect just a fact) person that wold even ask this question is to YES Odin back and start fresh. "Why?" because it will keep the forum cleaner since there will be less room for error and extra, "I flashed V5 over V3 and now I am in a boot loop" or "is my phone screwed???" threads...
blizzard1017 said:
It's been stated it's a matter of personal preference and opinion unless the developer states otherwise. I personally don't mind taking 5 extra minutes to do the to make sure everything is wiped. The above was just one of hundreds of reasons, I can pick another. I have also PERSONALLY flashed ROM over ROM and had issues. If you have not then you are the almighty among us and I worship thee and will build a golden shrine in your honor.
Every single ROM posted has a disclaimer about it messing up your phone. So in allll due respect to the truly talented developers; these ROM are consistently not perfect ports of official releases and cannot be confirmed as a perfect flash overs once they hit the masses.
My SUGGESTION to a nooby(no disrespect just a fact) person that wold even ask this question is to YES Odin back and start fresh. "Why?" because it will keep the forum cleaner since there will be less room for error and extra, "I flashed V5 over V3 and now I am in a boot loop" or "is my phone screwed???" threads...
Click to expand...
Click to collapse
every rom has a disclaimer so if you mess up your phone you realize it's not their fault (i.e. you probably did something wrong). it's not because they think their roms are going to break people's phones. the exception being oc kernels that explicitly say (and is obviously typically ignored) not all phones can handle the oc.
you can enjoy wasting your time using odin, but just because you probably messed something up flashing between roms, doesn't mean everyone should follow your silly odin ritual. as you have pretty much summed up, you have no real reason or evidence why someone should odin between roms.
again, all vibrant roms wipe, so odin 'back to stock' will do nothing for you. if someone can't be bothered to read the instructions on flashing a rom (i.e. disable all lagfixes), then they either shouldn't be flashing their phone, or may actually learn from their mistake.
Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
funeralthirst said:
every rom has a disclaimer so if you mess up your phone you realize it's not their fault (i.e. you probably did something wrong). it's not because they think their roms are going to break people's phones. the exception being oc kernels that explicitly say (and is obviously typically ignored) not all phones can handle the oc.
you can enjoy wasting your time using odin, but just because you probably messed something up flashing between roms, doesn't mean everyone should follow your silly odin ritual. as you have pretty much summed up, you have no real reason or evidence why someone should odin between roms.
again, all vibrant roms wipe, so odin 'back to stock' will do nothing for you. if someone can't be bothered to read the instructions on flashing a rom (i.e. disable all lagfixes), then they either shouldn't be flashing their phone, or may actually learn from their mistake.
Click to expand...
Click to collapse
Riiggghhttt good talk chief, must do it again sometime...............
blizzard1017 said:
Riiggghhttt good talk chief, must do it again sometime...............
Click to expand...
Click to collapse
awwww. how cute. you can't explain why you do something so you try to play it off with sarcasm.
lol...
but seriously, all jack assery aside, what exactly is it you think odining back to jfd does for you that formatting /data and /system don't?
No, u don't need to do anything, tw's said that if u go from nero to nero, you can, just flash right over it.
U don't even need to disable voodoo.
Also, listen to funeral, he knows more than that, blizzard guy
funeralthirst said:
awwww. how cute. you can't explain why you do something so you try to play it off with sarcasm.
lol...
but seriously, all jack assery aside, what exactly is it you think odining back to jfd does for you that formatting /data and /system don't?
Click to expand...
Click to collapse
Theres nothing wrong with going odin to stock re-root then flash a rom. It may be a comfort level with some people. TO EACH HIS OWN! Don't be butthurt because someone doesnt do it YOUR way.
Hey folks,
I just bought the white international SGS II and i'm loving it!
I previously had an Infuse 4g, so I am pretty experienced with flashing/backing up/ restoring...but I have questions/concerns regarding the I9100.
I am about to try out the CM9 Unstable, so I backed my current stock ROM up using CWM Manager 3.0 (I am on CF-Root 5.0) onto my Internal SD, as I do not have an external SD card.
Now, I have had bad experiences with CM7 with Infuse and ended up not being able to restore due to many problems like MD5 mismatch, different CWM version, and problems while restoring ( I think it said something like devblock??)
So I'm pretty worried about not being able to restore back to the backup i just made.
So correct me if I'm wrong folks,
1) Go into CWM, flash CM9(once? twice?), Gapps, Faceunlock,
2) Data wipe/factory reset
3) Reboot
and should I choose to restore back to the stock Rom backup,
just go into CM9's recovery and restore..?
will this method give me problems restoring? will I have different versions of CWM recovery from the one I have currently? Is there any way to check if my back up was made properly?
Thanks a lot folks! Appreciate it!
Edit: "Make sure you're already running ICS bootloader (if not, go to SamMobiles and flash XXKP2 bootloader)". Is this necessary? Cus I have seen some folks say that they've not and was fine installing CM9.
First the procedure:
1. Wipe
2. Install CyanogenMod 9
3. Reboot
4. Install CyanogenMod again
5. Install gapps and face-unlock
Worked for me every time.
Your backups should work unless there were errors while creating them.
If you want some more safety, you can create a new backup after flashing the Siyah-kernel. The latest version uses the same version of ClockWorkMod as CyanogenMod 9.
Whether you need to flash the bootloader or not, depends on whether you already have it or not. I'm running galnet-MIUI and already had the bootloader installed. I don't know how to tell if you have it.
Sent from my GT-I9100 using XDA App
Ok...
I did further research and found out that Nandroid backup backs up everything EXCEPT the kernel.
I'm pretty sure that CM has its own kernel...but will it be CWM 5.0.2.7(the one i made backup in.)?
If it's not, the correct steps for me to restore my nandroid back up is to
1)boot into download mode from CM9,
2) put the cf-root kernel that i used in the ODIN PDA, flash,
3) turn off phone, reboot into CWM, then restore my nandroid back up right??
Can anyone please confirm this method??
I only have this phone and I cannot risk soft-bricking or hard-bricking this beautiful device.
Thanks in advance!
Also, i made a back up in blue recovery of CWM 5.0.2.7..does that matter?
TheSniperFan said:
First the procedure:
1. Wipe
2. Install CyanogenMod 9
3. Reboot
4. Install CyanogenMod again
5. Install gapps and face-unlock
Worked for me every time.
Your backups should work unless there were errors while creating them.
If you want some more safety, you can create a new backup after flashing the Siyah-kernel. The latest version uses the same version of ClockWorkMod as CyanogenMod 9.
Whether you need to flash the bootloader or not, depends on whether you already have it or not. I'm running galnet-MIUI and already had the bootloader installed. I don't know how to tell if you have it.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
thanks for the reply,
so I must have the ICS bootloaders in order for CM9 to work?
ooo siyah kernel method... that makes it easier! haha thanks so much!
I will proceed to do that!
btw, how is CM9 working for you?
do you think you'll be able to use it as a daily driver now that NITZ is gone??
1. Afaik cwm backs the kernel up and restores it too. (afaik = 99.9% sure, in this case)
2. CyanogenMod ships with its own kernel.
3. The kernel is not cwm. ClockWorkMod is just the recovery that is integrated into the kernel. CyanogenMod 9 has cwm-recovery 5.5 (Siyah too btw)
4. You don't need to use download-mode to restore.
Sent from my GT-I9100 using XDA App
You must have ICS-bootleggers. He did not say that for fun xD.
Is it suitable as daily driver for me?
Nope.avi
Why?
Accelerometer is unresponsive, so it takes forever to flip your screen.
Battery drainage is horrible.
Camera isn't working properly.
And the biggest no-go for me:
The device gets way to hot when using it.
Sent from my GT-I9100 using XDA App
TheSniperFan said:
You must have ICS-bootleggers. He did not say that for fun xD.
Is it suitable as daily driver for me?
Nope.avi
Why?
Accelerometer is unresponsive, so it takes forever to flip your screen.
Battery drainage is horrible.
Camera isn't working properly.
And the biggest no-go for me:
The device gets way to hot when using it.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
alright,
thanks for the information!
I'll flash the Siyah kernel
Btw,
Flashing CM9 Zip does not flash the ICS bootloader right?
so then if I want to restore to my GB 2.3.5, would I need to flash GB bootloaders before restoring via Odin??
If the zip would flash the loaders, he wouldn't have mentioned it.
They're backwards-compatible.
Sent from my GT-I9100 using XDA App
If you need to make a post in the Q&A forums about flashing CM9, then you are definitely not the sort of person who should be flashing it. It is in very much a beta stage and there is a very high possibility it will **** your phone up even if you have done nothing wrong. If that happens you need to be the sort of person with enough experience to solve the problem by themselves. If you are asking questions before you've even flashed it then really, it's not for you. Use CM7, at the moment it's better than CM9 in every single way.
postfatal said:
If you need to make a post in the Q&A forums about flashing CM9, then you are definitely not the sort of person who should be flashing it. It is in very much a beta stage and there is a very high possibility it will **** your phone up even if you have done nothing wrong. If that happens you need to be the sort of person with enough experience to solve the problem by themselves. If you are asking questions before you've even flashed it then really, it's not for you. Use CM7, at the moment it's better than CM9 in every single way.
Click to expand...
Click to collapse
It's not thaaaaaaaaat bad. I mean, he won't be able to brick the device through cwm.
If he doesn't ask, he will never learn and it's always better to ask twice than to break something.
Sent from my GT-I9100 using XDA App
Thank you sniper =) really appreciate the support.
Ive been flashing and restoring before with my infuse 4g. Just sometimes ran into problems with restoring with diff CWM versions and stuff. This phone is very precious(expensive) so i thought i would learn it for sure before i attempted anything.. thanks anyways for sharing your opinion!
Sent from my GT-I9100 using XDA App
TheSniperFan said:
It's not thaaaaaaaaat bad. I mean, he won't be able to brick the device through cwm.
If he doesn't ask, he will never learn and it's always better to ask twice than to break something.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
I couldnt agree more... i think people here on XDA need to stop trying to be all hot **** saying Oh you asked a question your a noob... in reality most ppl here want to ask the same question but dont because afraid of getting *****ed out... and when someone else asks... try to be badass and put the person down...
Iv used a Galaxy S and a Moto Atrix and now a S2... flashed the life out of each phone along with all kinds of stuff and mods... yet i would have wanted to ask these same questions before flashing hence googled and found this thread... So thanks to those that replied as well... i was about to flash ics till i read this and guess imma hold back now even more...
But again i think people here need to calm the hell down... a person asks a question in the thread and you call them a 'noob' and what not... a person asks a question in the Q&A section and again you tell them off... stop being such anal retentive trolls...
DrunkFuX666 said:
I couldnt agree more... i think people here on XDA need to stop trying to be all hot **** saying Oh you asked a question your a noob... in reality most ppl here want to ask the same question but dont because afraid of getting *****ed out... and when someone else asks... try to be badass and put the person down...
Iv used a Galaxy S and a Moto Atrix and now a S2... flashed the life out of each phone along with all kinds of stuff and mods... yet i would have wanted to ask these same questions before flashing hence googled and found this thread... So thanks to those that replied as well... i was about to flash ics till i read this and guess imma hold back now even more...
But again i think people here need to calm the hell down... a person asks a question in the thread and you call them a 'noob' and what not... a person asks a question in the Q&A section and again you tell them off... stop being such anal retentive trolls...
Click to expand...
Click to collapse
Most people should not flame some one as long as they show they have at least tried to look for an answer first. Yes we were all new at one time but we all learned.
Like you said you Googled and found your answer. Not that hard.
Think it's bad now. Should have seen it a few years ago. Lol clutter up the threads with questions that the answers were found with a search. You got warned. Do it twice and you went on vacation for a few days to learn how to search. So the next time you think people are being too hard. Remember it is not as hlbad as it was.
When I search for the answer, I ended up here.
are these considered ICS bootloaders? If not, when would you flash them, because they are completely unmentioned in any of the instructions or FAQs
CWM flashable Modems:
XXKP8 Modem: http://www.multiupload.com/64J2P1MZL6
XXKP4 Modem: http://www.multiupload.com/NYUYFOT1ST
I personally think that a bunch of people who come across custom roms for their 4.0 galaxy players ask themselves this question, "why aren't there very many roms for my device that are simply flashed through clockwork recovery?" Is it because this device is not very popular? Is it because not very many people know how to put a custom rom in a cwm package? In no way do I want to sound rude, but when I have to flash multiple things onto my device from my computer in order for the tomorto work right as well as not brick my device, it just ruins it for me. There is nothing wrong with roms that require a computer to install, but I personally think that with all those instructions that might not be too clear on what you are support to do, something is bound to go wrong.
Sent from my YP-G1 using xda app-developers app
NATO556 said:
I personally think that a bunch of people who come across custom roms for their 4.0 galaxy players ask themselves this question, "why aren't there very many roms for my device that are simply flashed through clockwork recovery?" Is it because this device is not very popular? Is it because not very many people know how to put a custom rom in a cwm package? In no way do I want to sound rude, but when I have to flash multiple things onto my device from my computer in order for the tomorto work right as well as not brick my device, it just ruins it for me. There is nothing wrong with roms that require a computer to install, but I personally think that with all those instructions that might not be too clear on what you are support to do, something is bound to go wrong.
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
This is not that it can't be done, but it the case of ics for the 4.0, it's a bug in the kernel that force us to flash a kernel from heimdall. If this bug was not here, the rom would be simply flashed with cwm. So the answer is it's not because dev don't want to do it like this, it's because they can't.
Couldn't they fix it?
Sent from my YP-G1 using xda app-developers app
NATO556 said:
Couldn't they fix it?
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
They don't fix it because they don't know what is broken, this is not a choice. This is not that easy to find what is causing a bug and to repair it. You should be a little more thankful of what you already have because without them there would be no custom rom and no recovery. If you really want it so bad just go ahead and fix it then share it with the dev and they will include it.
ti-pich said:
They don't fix it because they don't know what is broken, this is not a choice. This is not that easy to find what is causing a bug and to repair it. You should be a little more thankful of what you already have because without them there would be no custom rom and no recovery. If you really want it so bad just go ahead and fix it then share it with the dev and they will include it.
Click to expand...
Click to collapse
The problem is that the param.lfs isn't getting updated, probably because their kernel isn't compatible with Samsung's proprietary param.ko (so the bootloader still thinks you're in recovery). If it's not, there's nothing that can be done about it. If it is, they should include that module in the ramdisk. and insmod it with init.rc, and the recovery bootloop will be gone.
Mevordel said:
The problem is that the param.lfs isn't getting updated, probably because their kernel isn't compatible with Samsung's proprietary param.ko (so the bootloader still thinks you're in recovery). If it's not, there's nothing that can be done about it. If it is, they should include that module in the ramdisk. and insmod it with init.rc, and the recovery bootloop will be gone.
Click to expand...
Click to collapse
You seem to know what your're talking about, maybe you could explain this to zaclimon, the last time I tried to help him he was trying to change the onenand driver so the device have the good partirion layout. It would be nice to get rid of that bootloop.
ti-pich said:
You seem to know what your're talking about, maybe you could explain this to zaclimon, the last time I tried to help him he was trying to change the onenand driver so the device have the good partirion layout. It would be nice to get rid of that bootloop.
Click to expand...
Click to collapse
Well, that's part of it too. I think on the 4.0, the problem may be more complicated than that, due to it's storage layout, (I have the 5.0) but rest assured the devs are working on it.
Please let me know when they fix this bug what I need to do from there.
Sent from my YP-G1 using xda app-developers app
Mevordel said:
The problem is that the param.lfs isn't getting updated, probably because their kernel isn't compatible with Samsung's proprietary param.ko (so the bootloader still thinks you're in recovery). If it's not, there's nothing that can be done about it. If it is, they should include that module in the ramdisk. and insmod it with init.rc, and the recovery bootloop will be gone.
Click to expand...
Click to collapse
There's this but mostly because we change the partition (we completely ditch the j4fs support). Also the bootloaders expect to run BML/STL partitions so the bootmode isn't cleared. The thing that teamhackung made is that they created a partition named reservoir that would handle all the bad blocks. This partition is used to flash the boot partition which is the kernel one. This is still an undergoing experimentation for me but I'll try to compile a CM9 with this new type of flashing. An example of the partition layout is here:
https://github.com/CyanogenMod/andr...ung-3.0-ics/drivers/mtd/onenand/samsung_gsm.h
I may miss some things too but this is the things simplified.
Also NATO I do know how you feel about it and I'm trying to do my best (with han and oisis gone) to solve everything as soon as I can. (Don't forget that I have school too )
Sent from my Nexus 7 using Tapatalk HD
Actually most of the GB ROMs for the 4.0 are CWM flashable zips,
http://forum.xda-developers.com/showthread.php?t=1834375
http://forum.xda-developers.com/showthread.php?t=1718339 (older versions)
http://forum.xda-developers.com/showthread.php?t=1821860
http://forum.xda-developers.com/showthread.php?t=1895629
http://forum.xda-developers.com/showthread.php?t=1884557
http://forum.xda-developers.com/showthread.php?t=1719685
http://forum.xda-developers.com/showthread.php?t=1759949 (several ROMs)
http://forum.xda-developers.com/showthread.php?t=1825281
there are 2 or 3 more ROMs that are CWM zips but there based on the OLD CM7 port and with no deep sleep there not worth the time IMO (not the Porting DEVs fault, it was a known issue of the CM7 base).
NOT ENOUGH FOR YOU?
The ones that aren't are because of data corruption issues.
As for ICS, well thats been covered.
Thank you guys for all you do. I really am thankfull to have a website like this one to turn to for help.
Sent from my YP-G1 using xda app-developers app
As soon as the glitch is fixed please let me know. Another question, will there ever be an official CWM release on the player? And will Tardis_Balor update the Terra Silent Kernel once the glitch is corrected?
Sent from my YP-G1 using xda app-developers app
Also, why is hanthesolo's ethereal tomorrow not on this list?
Sent from my YP-G1 using xda app-developers app
rom*
Sent from my YP-G1 using xda app-developers app
BTW, the link for v2.0 of Icy Fusion is dead.
Sent from my YP-G1 using xda app-developers app
Okay so I have a Samsung galaxy s2 gt-i9100. I have rooted the phone and I thought to have installed cwm (which came with the root)
but I still boot into stock recovery (even though Rom manager tell me I have cwm 5.x.x installed or something along those lines).
I know now that the kernel resets to stock recovery. So i am running 4.1.2 and my build number (found in 'about phone') is JZO54K.I9100XWLSW.
I have downloaded 'philZ-cwm6-XWLSW-XEU-5.06.1.zip' from his XDA thread, and was wondering is this the right one for me. And since I am already rooted and all that I was also wondering if installing this will clash with my root and mess up everything- thanks in advance, I really appreciate the help.
You got the right one and are good to go.It won't "mess" anything,you'll basically get a stock kernel+cwm+root in a single flash.Good for starters if I may.
This is the exact method I used to root, and now I'm happily running my (probably) 30th different custom rom.......
Sent from my GT-I9100 using XDA Developers app
Don't use ROM Manager on S2. Ever. It's a sure way to screw things up. For some reason it seems to end up corrupting recovery on S2.
Why are n00bs so attracted to Rom Manager ? It's **** on any device. Only lazy people use it on the devices it actually works properly on.
MistahBungle said:
Why are n00bs so attracted to Rom Manager ? It's **** on any device. Only lazy people use it on the devices it actually works properly on.
Click to expand...
Click to collapse
Your not very nice, to be fair how am I supposed to know that it breaks the recovery. Everyone has to start somewhere
LiamFlannery said:
Your not very nice
Click to expand...
Click to collapse
There was nothing 'not nice' about what I said. Rom Manager is a POS. Lazy people use it. You weren't specifically mentioned in my post, you were lumped in with all the other n00bs. There's nothing special about you in that regard.
See ? That last sentence was somewhat 'not nice' *adds you to my ignore list*
okay thanks everyone for the helpful replies, also I was just wondering whats the difference between XWLSW-OXX and the one I am going to use which is XWLSW-XEU? just out of curiosity -thanks
LiamFlannery said:
okay thanks everyone for the helpful replies, also I was just wondering whats the difference between XWLSW-OXX and the one I am going to use which is XWLSW-XEU? just out of curiosity -thanks
Click to expand...
Click to collapse
Philz's kernel OP has answers to all your questions.
We should all do this on playstore.