Related
********This is only a ROM. You must have first flashed the EA11 LEAK first.********
********You must have the modified RED CWM recovery to flash this. If you don't already have that installed, go here to get it.*********
*********DO NOT FLASH THIS IF YOU ARE STILL ON 2.1************
As always, I am not responsible for what you do to your phone. Make a backup before you flash anything.
Download the ROM and the addons. (unzip the main addons zip) Decide what addons you want. Put everything on your sdcard and boot into recovery. Flash the ROM first. Flash any addon packs that you have put on your sdcard. Reboot.
I've tried to group the addons so there aren't too many of them. If you want, you can always reconfigure things using 7zip without having to unzip anything. If you don't know how to do this already, it's probably best to just flash each pack seperately.
EA11 Mesmerize Pick-n-Pack ROM
EA11 Mesmerize PnP Addons
Thank you sir very much
Sent from my SCH-I500 using XDA App
Now for some voodoo?
Sent from my SCH-I500 using XDA App
why do we need to flash the original Froyo leak first?
i dont understand this Mez thing about using Odin.
once you have a Rom flashed to your phone and Clockwork working there is never ever ever a need to use this odin program. i have never once used it and have flashed a few roms, one of them your very own pick-n-pak , just not the froyo one.
so can someone explain to me this crazy need to backdoor flash the phone?
the Froyo leak is just a rom, just like this and every other rom. its just a factory flash rom, not a rom you guys built....
so why not just build a rom from it because the odin stuff seems just to be massive unnecessary overkill.
v_lestat said:
why do we need to flash the original Froyo leak first?
i dont understand this Mez thing about using Odin.
once you have a Rom flashed to your phone and Clockwork working there is never ever ever a need to use this odin program. i have never once used it and have flashed a few roms, one of them your very own...[etc, etc]
Click to expand...
Click to collapse
It doesn't seem like a bad idea to have a stock backup solution available.
v_lestat said:
why do we need to flash the original Froyo leak first?
i dont understand this Mez thing about using Odin.
once you have a Rom flashed to your phone and Clockwork working there is never ever ever a need to use this odin program. i have never once used it and have flashed a few roms, one of them your very own pick-n-pak , just not the froyo one.
so can someone explain to me this crazy need to backdoor flash the phone?
the Froyo leak is just a rom, just like this and every other rom. its just a factory flash rom, not a rom you guys built....
so why not just build a rom from it because the odin stuff seems just to be massive unnecessary overkill.
Click to expand...
Click to collapse
This ROM doesn't have a kernel or a modem with it. If you don't have those files, your phone won't work.
The Froyo leak is NOT a ROM it is a recovery system just as the recovery system for 2.1. It has everything in it.
Odin is not overkill. It's just a different way of flashing things. As soon as we have everything in place for a fully flashable ROM including kernel and modem, that will be an option too. My original PnP ROM also did not include a kernel or modem, but you were already on 2.1 so you didn't need to get there. Had you have been on 1.6, you would have had to update.
Also, there is only two of us working on all of this. We can only do so much. We are trying to do what we can, with what we have. If you can help us out, hit us up on irc. We could use the help.
help?
i just flashed and got a boot loop anything?
mesmerbelly said:
i just flashed and got a boot loop anything?
Click to expand...
Click to collapse
Hit the irc channel. I didn't have any problems, and neither did any of the others that flashed. We'll get you fixed up.
duhh
i just needed to wipe everything duhh belly think then ask
could you plz tell me where the bootanimation.zip goes in this...i miss my dancing droid...i got the music to work but no animation
v_lestat said:
why do we need to flash the original Froyo leak first?
i dont understand this Mez thing about using Odin.
once you have a Rom flashed to your phone and Clockwork working there is never ever ever a need to use this odin program. i have never once used it and have flashed a few roms, one of them your very own pick-n-pak , just not the froyo one.
so can someone explain to me this crazy need to backdoor flash the phone?
the Froyo leak is just a rom, just like this and every other rom. its just a factory flash rom, not a rom you guys built....
so why not just build a rom from it because the odin stuff seems just to be massive unnecessary overkill.
Click to expand...
Click to collapse
Over 700 posts here and a thanks meter of 1.. <-- maybe you should just cool off a bit..
Two things:
Number one: Read my reply to your la]st rant. It explains a lot.
Number two: As far as I know, phidelt82 and I are the only ones who own a Samsung Mesmerize and are offering our time up to work on this stuff. Thank God our device is very similar to the other Galaxy S devices so we can dip into the community and share resources where appropriate. I promise you without the resources of the great XDA community, you would have none of this from us.
To answer your burning question I already answered once:
The reason we don't have this in an update.zip form yet is because I am a college student who spends most of his days studying. Every so often I get some *leisure* time to spend working on things I enjoy -- like helping out this community here. I am not as skilled as the prominent Fascinate devs but I am learning. So is phidelt. The refined packages will come.
The fact that you are so worked up about ODIN tells me there are reasons far beyond your understanding as to why we are using it. There is nothing wrong with odin. IT DOES THE SAME THING THAT YOUR RECOVERY PARTITION DOES/CAN DO.. just attached to the computer. I actually think it's more reliable (well at least Heimdall is) and easier to use.
If we were to release a froyo-update.zip and everyone tried it out, without ODIN, they would be potentially stuck in 2.2 land. That would be a big hassle donchathink -- especially because EA11 is not a final release, there ARE some bugs? The current solution for Fascinate users is to flash a froyo.zip from their phone, THEN USE ODIN to flash a <2e> recovery partition so that CWM will work properly. Why not do it all in Odin for the Mesmerize for the time being? Once there is a reliable solution that doesn't need ODIN/Heimdall, I promise you, it will be implemented.
Cool off. I've wasted enough time responding to your ignorance. I am being abrasive now because I already answered you once, and you find the need to ignore the contents of my reply and rant about the same old..
I had some time to put up a new package tonight, but, thanks(?) to you, that's not the case anymore.. =/
you tell him dcow....i like odin...its simple and reliable...cant complain about that
on topic : love this rom...used it on 2.1 and so exited its on froyo now...great work!!!
Yikes, what ever happened to the rule of "If you don't like it, do something about it." ?
For the record, dcow and phidelt, you guys are awesome and I very much greatly appreciate putting your extra time into this!
Amen!
BIG thanks to dcow and phidelt. Without your efforts, I'd still be on stock 2.1. Just wanted you both to know your time and effort is appreciated. Don't know how many of these phones USCC has sold, but it's got to be a small community in comparison to, for example, the Fascinate.
Glad the other devs have been kind enough to help you out where they can...big thanks to them as well.
BakedTator said:
could you plz tell me where the bootanimation.zip goes in this...i miss my dancing droid...i got the music to work but no animation
Click to expand...
Click to collapse
as of right now till we get a custom kernel there is not much you can do. this one uses qmg files in the /system/media folder for the startup animation. you can delete or rename them so its black but i have yet to find any good working qmg. i have actually found one file and it is 4meg and the animation doesn't finish by the time the desktop apears. the stanard one on our phone is only like 2 to 2.5meg
so your telling me i (or someone with the skills) is going to have to learn how to convert the zips into qmg files? or is there a program we could use...imma google it but if you or anyone knows anything about this plz tell me...im willing to learn and try this out
http://forum.xda-developers.com/showthread.php?t=792953
We're going to have to do some research =/, or possibly need a MOD to the rom first.
You guys rock! Back to being bloat-free...and on 2.2
phidelt82 said:
This ROM doesn't have a kernel or a modem with it. If you don't have those files, your phone won't work.
The Froyo leak is NOT a ROM it is a recovery system just as the recovery system for 2.1. It has everything in it.
Odin is not overkill. It's just a different way of flashing things. As soon as we have everything in place for a fully flashable ROM including kernel and modem, that will be an option too. My original PnP ROM also did not include a kernel or modem, but you were already on 2.1 so you didn't need to get there. Had you have been on 1.6, you would have had to update.
Also, there is only two of us working on all of this. We can only do so much. We are trying to do what we can, with what we have. If you can help us out, hit us up on irc. We could use the help.
Click to expand...
Click to collapse
ahhh i see, it is a rom but its a radio-less rom. - so wait.... if its a radioless rom then why are we flashing it with odin... i dont understand.
and yes odin seems nice, but to have to use this instead of just flashing via clockwork seems rather unconventional
On the EVO we had the official and leaked HTC flasher but to use it meant you lost root. the teams just made a flashable rooted rom
i know that isnt the case with the Mez. but it seemed silly to me that since you had the Samsung recovery, and you had your pick-n-pak... then why not just make a flashable rom.
am i mistaken here ? why not jsut make a rom since you have the stock recovery and the necessary files, just make a rom we can flash via recovery.
so i guess i am lost, if its radioless why are we using it and how is anything working if its not a rom, and missing said files.
p.s.
i sure with amon ra would become available for the Mez lol.
bdemartino said:
http://forum.xda-developers.com/showthread.php?t=792953
We're going to have to do some research =/, or possibly need a MOD to the rom first.
Click to expand...
Click to collapse
i will do my best to help in this research (though im still rather new to all this) and help out in any way i can...maybe with the power of 2 (or more) Brains we can get this working too!
Basically all I'm trying to do is get a stock 2.2 Mesmerize that isn't all laggy and stuttery, (and I'd love to get rid of that annoying blue hue to the screen). I read that the Voodoo kernel is the best thing for this.
I started with the official 2.2 update from Samsung, and did the following actions in this order:
-rooted with superoneclick (not sure if this step was necessary)
-flashed Voodoo kernal with Odin as per the instructions here: http://project-voodoo.org/installation
-rebooted, heard the robot voice talking about installing the lagfix, said lagfix was complete. Waited another five minutes, yanked the battery and rebooted, and it gets stuck in the Samsung Galaxy S i-9000 boot screen and never boots
-tried to enter stock (blue) recovery by holding the 3 buttons, and it mentioned a mounting error "e:/ can't mount something or another... invalid argument", which apparently is an error you get if you install the voodoo kernel and then do a reset and attempt to change back the filesystem to stock with voodoo still installed
-So I followed the recovery instructions in this thread and once I re-flashed the stock 2.2 ROM, the phone worked. I did not have to make the "disable lagfix" file. It just worked when I flashed.
-This time, I decided to try the non-ODIN method of installing the voodoo kernel, again, as per the developers instructions; by copying the zip file to the SD card, booting to recovery, and selecting update.zip. This was about 5 minutes ago, and my phone has been sitting on a black screen with a "!" inside a triangle with the android robot doing absolutely nothing. I'm guessing I'm going to have to reflash back to stock yet again...
Can anyone figure out what I'm doing wrong here? How do I know if the "Voodoo lagfix" is active? Would flashing back to the stock ROM somehow disable it? I've combed through these forums and read about a million threads, and it seems like I'm missing something.
Voodoo is just a kernel which is just a piece of code that tells your software how to interact with your hardware, correct? And I can just flash a kernel to the phone without doing anything weird, right? Also, lets say I want to remove the Voodoo kernel entirely and revert back to the stock method of software/hardware interaction. How would I go about doing that?
At the moment, I'm not interested in custom ROM's or anything, I just want a smooth phone. (Former iPhone user)
Any advice is appreciated.
Right now when I boot in recovery, I have the following error:
"E: Can't mount /dev/block/mmcblk0p2
(no such file or directory)"
Not sure if this is relevant. I was able to reboot the phone just fine and it works, but I'm almost certain Voodoo is still not installed... (as is evident by the stock USCellular boot screen and overall crappy, laggy performance.)
Yeah sounds like you've jacked up your phone pretty good. First problem was that you didn't flash a kernel built for our phone. You flashed one for the European Galaxy S so that's why it didn't work. Second, you didn't disable lagfix before using odin to get back to stock, which likely caused additional issues with your phone. At this point, you have screwed it up beyond my knowledge. My suggestion would be to go to the #samsung-fascinate irc channel and see if one of the guys there can help you out. For future reference, read the information here before you just randomly flash stuff not meant for your phone.
akellar said:
Yeah sounds like you've jacked up your phone pretty good. First problem was that you didn't flash a kernel built for our phone. You flashed one for the European Galaxy S so that's why it didn't work. Second, you didn't disable lagfix before using odin to get back to stock, which likely caused additional issues with your phone. At this point, you have screwed it up beyond my knowledge. My suggestion would be to go to the #samsung-fascinate irc channel and see if one of the guys there can help you out. For future reference, read the information here before you just randomly flash stuff not meant for your phone.
Click to expand...
Click to collapse
Ok first of all, I read on THIS FORUM that the voodoo kernels were generic, so I'm not just banging sticks together. I've spent the last couple days reading thread after thread.
http://forum.xda-developers.com/showthread.php?t=1009414&page=2
Secondly, the phone works exactly as it did when I bought it, so there's no need to get all worked up. I'm just asking for input on what I did wrong. You seem to identified the Voodoo kernel as not being the correct kernel?
Is there a proper Mesmerize EC10 kernel that I should be using?
Here was the path of reading that I took before "randomly flashing things," all from this forum:
Mesmerize stock EC10 Voodoo lagfix install made simple
http://forum.xda-developers.com/showthread.php?t=1024279
Which tells you to download the EC10 voodoo kernel here:
http://forum.xda-developers.com/showthread.php?t=1011578
This thread links to a TouchWiz kernel, which I don't want
Which links to the original post by jt1134 here:
http://forum.xda-developers.com/showthread.php?t=1010102
and lists several Voodoo kernels for custom ROM's, which I do not want (I want the stock ROM)
Which links to voodoo's site where I downloaded the kernel, here:
http://project-voodoo.org/lagfix
So again, can you point me in the direction of a proper Mesmerize EC10 Voodoo kernel?
But you see, all of the threads you just posted talk about generic EC10 kernels, and none of the kernels on the Voodoo website say they're generic EC10 kernels. No pro or con, I'm just saying akellar wasn't off the mark in what he said. The threads say generic EC10 voodoo kernels, not generic voodoo kernels. You simply must pay attention.
In continuance of that, you really do have to read what the posts actually say. Those threads you posted aren't trying to direct you from one thread to another, to another, and to another just to give you a kernel. They're giving credit to where the kernel came from, which the OP configured/modified/ported/whatever for our phones. If you keep following the paper trail you will end up with a completely different thing - which is what happened. That Comavolt kernel you posted a link to will be just fine.
The voodoo kernels in the fascinate forums. OTB and Peanut Butter Jelly time work on our phones. I have used both. If you are on stock froyo then u need touchwiz kernels as u are using a touchwiz based ROM. All of the kernels I have found to work have been from the fascinate forums. They are built off The EC10 source. I would post links but I'm doing this from my phone and am kinda short on time. Under facinate development you should be able to find eithet OTB or the Peanut Butter Jelly time. OTB is by nemmisses2all and PBJT is by imunts. Either ome of those touchwiz will work on stock 2.2 mesmerize.
Rockin Heinz 57 w/ Ultimate Honeycomb and OTB Voodoo.
add144 said:
But you see, all of the threads you just posted talk about generic EC10 kernels, and none of the kernels on the Voodoo website say they're generic EC10 kernels. No pro or con, I'm just saying akellar wasn't off the mark in what he said. The threads say generic EC10 voodoo kernels, not generic voodoo kernels. You simply must pay attention.
In continuance of that, you really do have to read what the posts actually say. Those threads you posted aren't trying to direct you from one thread to another, to another, and to another just to give you a kernel. They're giving credit to where the kernel came from, which the OP configured/modified/ported/whatever for our phones. If you keep following the paper trail you will end up with a completely different thing - which is what happened. That Comavolt kernel you posted a link to will be just fine.
Click to expand...
Click to collapse
I get that now; generic EC10 voodoo kernel =/= generic voodoo kernel. To somebody with minimal programming experience, this is kind of like learning to speak Chinese by moving to China... The level of newbie hand-holding is very minimal amongst the programming community.
Nevertheless, I think I figured out why/how I missed the correct EC10 kernel; I did not realize that "Touchwhiz" refers to the default framework. I read the Glossary twice, but I still had it in my head that Touchwhiz was a custom ROM, so I skipped over any mention of EC10 Voodoo kernels for Touchwhiz, because I wanted to keep the stock ROM
scarmon25 said:
The voodoo kernels in the fascinate forums. OTB and Peanut Butter Jelly time work on our phones. I have used both. If you are on stock froyo then u need touchwiz kernels as u are using a touchwiz based ROM. All of the kernels I have found to work have been from the fascinate forums. They are built off The EC10 source. I would post links but I'm doing this from my phone and am kinda short on time. Under facinate development you should be able to find eithet OTB or the Peanut Butter Jelly time. OTB is by nemmisses2all and PBJT is by imunts. Either ome of those touchwiz will work on stock 2.2 mesmerize.
Click to expand...
Click to collapse
Right... That was the key piece of information I was missing which led me to an incompatible kernel. Thanks for the advice, I will check those out.
I'm not expecting it to work, as I see someone else did the same thing I did and hasn't been able to get the Voodoo kernel's working since:
http://forum.xda-developers.com/showthread.php?t=1009146
Although to be honest I'm not quite clear on why you can't flash a kernel that reverts the filesystem back to default, essentially undoing what Voodoo does... Is there no way to remove that kernel completely once it has been installed? Or is the problem simply that when you overwrite it, the filesystems remain changed and there is no software to revert the filesystems back to stock?
The way I always went back to stock was to diasble voodoo by putting a folder named disable_lagfig in the voodoo folder on the sd card. Rebooted. Then after that's was done I placed the stock ec10 kernel on my card booted into CWM 2.5 and flashed the stock. After that and phone was booted. I would delete the voodoo folder off my card. I have done this several times after going through many different kernels and finding the one I liked. I would revert back to stock kernel and flash the one of my choice fresh. The stock ec10 kernel can be found in ths stick titled files to get your mesmerize back to stock. There is a file there that is just the kernel towards the bottom. I would post links but again doing from phone. Sorry. You will need to odin the cwm.recovery.tar file as well to give you the CWM 2.5. That link should be in that sticky as well.
Edit. That sticky is in the developmemt forum for memserize.
Rockin Heinz 57 w/ Ultimate Honeycomb and OTB Voodoo.
scarmon25 said:
The way I always went back to stock was to diasble voodoo by putting a folder named disable_lagfig in the voodoo folder on the sd card. Rebooted. Then after that's was done I placed the stock ec10 kernel on my card booted into CWM 2.5 and flashed the stock. After that and phone was booted. I would delete the voodoo folder off my card. I have done this several times after going through many different kernels and finding the one I liked. I would revert back to stock kernel and flash the one of my choice fresh. The stock ec10 kernel can be found in ths stick titled files to get your mesmerize back to stock. There is a file there that is just the kernel towards the bottom. I would post links but again doing from phone. Sorry. You will need to odin the cwm.recovery.tar file as well to give you the CWM 2.5. That link should be in that sticky as well.
Edit. That sticky is in the developmemt forum for memserize.
Rockin Heinz 57 w/ Ultimate Honeycomb and OTB Voodoo.
Click to expand...
Click to collapse
Ah, thank you. Sounds straight-forward enough. Disable-lagfix file, flash, and delete. I've even already got the stock kernel from that link; I used the 2.1 files in that thread to downgrade to 2.1 when I realized my Mesmerize was missing like 1/3 of the calls that came in
Yeah USCC is supposedly working on a update to fix the missed call issue. I fortantely havent been as effected by this as some. Glad that helped.
Rockin Heinz 57 w/ Ultimate Honeycomb and OTB Voodoo.
scarmon25 said:
Yeah USCC is supposedly working on a update to fix the missed call issue. I fortantely havent been as effected by this as some. Glad that helped.
Rockin Heinz 57 w/ Ultimate Honeycomb and OTB Voodoo.
Click to expand...
Click to collapse
Yeah that helped a lot. I've always understood the basics of the different pieces of software in our phone's OS, but getting basic information is often pretty tough, because everything is in developer-speak, and everything has its own code name with an acronym, both official and non-official releases. Even the so called beginner guides are all in code, like CWM, touchwhiz, "blue" recovery, etc... You literally need a manual to decode all the acronyms
Anyway, thanks.
Can we get like a master thread with all relevant links to downloads? I have 17 Firefox windows open right now, all XDA. It would be spectacular if we could consolidate all the relevant ROMs, kernels, PC programs, guides, etc into one thread for the newbies (like me).
Ntruder said:
I have 17 Firefox windows open right now, all XDA.
Click to expand...
Click to collapse
Its called tabs.
Ntruder said:
Yeah that helped a lot. I've always understood the basics of the different pieces of software in our phone's OS, but getting basic information is often pretty tough, because everything is in developer-speak, and everything has its own code name with an acronym, both official and non-official releases. Even the so called beginner guides are all in code, like CWM, touchwhiz, "blue" recovery, etc... You literally need a manual to decode all the acronyms
Anyway, thanks.
Click to expand...
Click to collapse
See, this tells me I need to polish the Glossary, because if it's not immediately evident to someone who's read it twice and can, in spite of that, form solid sentences in English, then it means I haven't accomplished my goal.
I may add an FAQ section to the 2nd post as well, a collection of "How To" links to point you to any file you may want to download/process you may want to attempt... All in one thread. That's *sort* of there with Bde's How to Customize Your Phone sticky, but that doesn't cover everything under the sun. That said, my "How To" section, while it would cover everything, would only do so briefly, with links to the real threads. No point in me trying to reinvent the wheel, all those guides have been written already.
Thanks for the indirect feedback Ntruder.
add144 said:
Its called tabs.
Click to expand...
Click to collapse
Haha! I meant tabs. I think my mother is the only person alive who doesn't use tabs.
ChromWolf said:
See, this tells me I need to polish the Glossary, because if it's not immediately evident to someone who's read it twice and can, in spite of that, form solid sentences in English, then it means I haven't accomplished my goal.
Click to expand...
Click to collapse
No, the glossary is spectacular, I'm not sure there's much you could do to make it better. I just didn't memorize it all (yet)
I may add an FAQ section to the 2nd post as well, a collection of "How To" links to point you to any file you may want to download/process you may want to attempt... All in one thread. That's *sort* of there with Bde's How to Customize Your Phone sticky, but that doesn't cover everything under the sun. That said, my "How To" section, while it would cover everything, would only do so briefly, with links to the real threads. No point in me trying to reinvent the wheel, all those guides have been written already.
Thanks for the indirect feedback Ntruder.
Click to expand...
Click to collapse
BDE's how to post is pretty comprehensive actually now that I look back at it. What is strangely absent (and everyone under the sun seems to use them) are the voodoo kernels.
Kernels are in the second post here:
http://forum.xda-developers.com/showthread.php?t=1013312
Ntruder said:
BDE's how to post is pretty comprehensive actually now that I look back at it. What is strangely absent (and everyone under the sun seems to use them) are the voodoo kernels.
Click to expand...
Click to collapse
Hey - I covered those
3.)Upgrade Kernel With EC10 brought a new turn of events which thanks to jt has allowed fasicnate users to develop kernels which are compatible on the entire line of this model, so be sure to read phidelt's post on kernel's located here and choose one that is compatible with your rom. AOSP and MIUI require a different kernel, so keep this in mind as if you're restoring you may need to flash the appropriate kernel as the restore does not do this for you.
Click to expand...
Click to collapse
I noticed now that i didn't really reference voodoo in any of that, so I'll make sure to polish that part off when I get a chance. you seem to have some decent general technical knowledge and if you're struggling to understand then my guide isn't doing it's job (to the best of it's ability) .
The problem is most of us have been here for awhile now, so as we update guides and post new things we forget what wasn't obvious to us as a new person, so it's good of you guys to call us out so that we can be made aware of these things .
I'm pretty bugged out that I have to flash multiple things just to get from one ROM to another. Especially when flashing back to stock.
This is a request, there is no reward, I am not forcing anyone to do it, you can pick up the request or not. This is for the entire communities benefit.
Now we have cleared things so no one complains "Oh how rude you are asking our developers to do something, you got some nerve."
Since most of our ROM's are now ICS and some of them require CM9 before flashing, I thought why not a One-Click ICS? It would be beneficial for allot of people.
I would do it myself however I have no Android development experience.
So if anyone has allot of time and has experience with making One-Clicks, you have my respect and probably the entire SGS4G community.
th3controller said:
I'm pretty bugged out that I have to flash multiple things just to get from one ROM to another. Especially when flashing back to stock
Click to expand...
Click to collapse
First, there is no stock ICS for this phone so you'll still need to go back to GB to be "stock". Second, I flash from ICS to ICS to ICS without ever going back to stock or CM9. With most of the new builds there is no need to. The only time I ever have to use Heimdall anymore is when one of Eriks "test builds" completely hoses me.(JK that actually almost never happens).
Im sure as soon as I post this 30 people will post saying they just created a one click to ics. so...
It cant be done. The PIT file needs to be edited to reflect the mtd file system.
Really what needs to be done is these ports requiring you to flash to cm9 first should be using the same install scripts as cm9 so you can flash directly to it from stock. At this point if a rom says flash so and so first I dont try it. Because if they are using the scripts from cm9 there shouldnt be a reason to flash cm9 first. I might sound rude or whatever but its simply a matter of convenience.
Thanks for the awesome, understandable replies guys!
Lol Hechoen I see you taste some of Erik's custom recipe's before anyone does XD
And yes eollie it is for convenience
th3controller said:
Thanks for the awesome, understandable replies guys!
Lol Hechoen I see you taste some of Erik's custom recipe's before anyone does XD
And yes eollie it is for convenience
Click to expand...
Click to collapse
Lately I get to see them even before he does. lol He's got a pretty sweet one coming up that I think people are gonna dig. No ETA's but something about built from source AOSP?
Uh oh... is search broken?
th3controller said:
I'm pretty bugged out that I have to flash multiple things just to get from one ROM to another. Especially when flashing back to stock.
This is a request, there is no reward, I am not forcing anyone to do it, you can pick up the request or not. This is for the entire communities benefit.
Now we have cleared things so no one complains "Oh how rude you are asking our developers to do something, you got some nerve."
Click to expand...
Click to collapse
How rude, wanting convenience. HAHA. Me too! I want that sauce!
th3controller said:
Since most of our ROM's are now ICS and some of them require CM9 before flashing, I thought why not a One-Click ICS? It would be beneficial for allot of people.
Click to expand...
Click to collapse
Why do you need to flash cm9 before flashing other ics roms? Can't you just fix that stuff in the updater.sh and updater-script? Or is that not convenient? <hehe, sarcasm again...>
th3controller said:
I would do it myself however I have no Android development experience.
So if anyone has allot of time and has experience with making One-Clicks, you have my respect and probably the entire SGS4G community.
Click to expand...
Click to collapse
Yea, so here is the thing. The oneclick uses the bootloader to do it's magic. The bootloader only speaks in BML and RFS. It knows nothing of MTD, yaffs2, or ext4. It also gets it's partition information from the Partition Information Table (pit), which is also laid out for BML/RFS.
So basically, Your question is: Make us some new bootloaders!
This is not something I can do overnight, but have been investigating since my phone got unbrickable mod.
There is a lot of information to collect, and I am collecting this information in little chunks everytime we get another feature of cm9/aries working properly.
Unfortunately, my work on a new bootloader for this phone is stalled until I can get a new job (yes, unemployment only pays for me to pay some minor bills and eat.) so that I can afford to buy the equipment I need to do such a thing.
Once we have a new bootloader, we can just fastboot each partition just like the Google phones and HTC devices. Wouldn't that be great. Yea, thats what I was thinking too. Glad we are on the same page now
It's too bad that you didn't search the forums, or you would have found me saying this months ago.
But people keep opening new threads about stuff, and you know we are gullible and will answer, because it is more convenient to ask then it is to search.
Lol bhundven, you even went on the trouble of adding a underline XD
Anyways, yes I do understand the matter and I do understand it is NOT an overnight thing. I'm just hearing (seeing) these things right now, like I said not really experienced. I also try to read as much in the forums as I can.
I also hope I'm not in your bad side
th3controller said:
Lol bhundven, you even went on the trouble of adding a underline XD
Anyways, yes I do understand the matter and I do understand it is NOT an overnight thing. I'm just hearing (seeing) these things right now, like I said not really experienced. I also try to read as much in the forums as I can.
I also hope I'm not in your bad side
Click to expand...
Click to collapse
My post was mostly sarcasm... besides the point about needing new bootloaders.
My bad side is notifying moderators. At the time of this writing, this thread is still open with no one sending abuse reports...
I don't ignore people, because then I see people laughing or getting angry around one of the people I ignore in a thread, and I don't get to understand why it is funny or anger causing.
I'm dearly sorry Bhudven-Sama, I shall not fail you again!
th3controller said:
I'm dearly sorry Bhudven-Sama, I shall not fail you again!
Click to expand...
Click to collapse
lol
th3controller said:
I'm pretty bugged out that I have to flash multiple things just to get from one ROM to another.
Click to expand...
Click to collapse
Sounds like the people that assemble FrankenROMs need to learn how to script the updater. Once you're on MTD, there shouldn't be any reason to do anything but let the supplied installer run.
Flashing back to stock? There is a one-click for that. Takes you from MTD to GB stock. I'm pretty sure that someone even made one with an AntonX kernel, root, and recovery all in one shot.
I hadn't mentioned last night, but I've actually been messing with how to make a one click for ICS roms, particularly AOKP. When the rom gets built from source, we also get a system image file that we SHOULD be able to flash via heimdall. The thing is that there seems to be some kind of limitation of the filesize of this image, and the image flash fails at the exact same spot every time.
I've tried to look up information on how to make heimdall be able to flash the whole file but found nothing promising. Even some of the people from the mozilla boot to gecko team had tried to modify the heimdall source code to allow the file to be flashed but they had no luck either.
Admittedly, I haven't tested to see if an ICS boot.img/system image will flash via Odin.
FBis251 said:
I hadn't mentioned last night, but I've actually been messing with how to make a one click for ICS roms, particularly AOKP. When the rom gets built from source, we also get a system image file that we SHOULD be able to flash via heimdall. The thing is that there seems to be some kind of limitation of the filesize of this image, and the image flash fails at the exact same spot every time.
I've tried to look up information on how to make heimdall be able to flash the whole file but found nothing promising. Even some of the people from the mozilla boot to gecko team had tried to modify the heimdall source code to allow the file to be flashed but they had no luck either.
Admittedly, I haven't tested to see if an ICS boot.img/system image will flash via Odin.
Click to expand...
Click to collapse
Ok, so yea, we can probably make a heimdall flash that will flash bootloaders and kernel for an MTD rom, but you'd have to do some manual things still (which is why I prefer flashing back to stock):
flash back to stock
backup your efs
oneclick cm9/ics rom.
restore your efs manually.
flash cm9/ics rom after the oneclick is done.
so, compaired to:
flash back to stock
reboot to recovery
flash cm9/ics rom
you are just making things more difficult.
The thing is, you shouldn't need to flash back to stock if you are going from cm9 to any other ics/mtd rom.
And you shouldn't need to flash to cm9 if you want to flash any other ics rom.
The developers of those roms are just being lazy (imo) and need to modify their updater.sh and updater-script to work like the cm9 scripts do. Fixed.
When we get new bootloaders, this all changes.
Hey there guys,
I'm a noob so I had to post here. Although I've already read the intro guides to installing ROM's. Right now running the CM 11 nightly on my skyrocket. I'm looking for a better rom that has kitkat and I came across the Hellkat/BlueLightning roms. I wanted to install blue lightning but I have a couple questions before I mess anything up (I've read that being fully informed and taking precautions is a must)
So I wanted to know, if I'm installing this rom: http://forum.xda-developers.com/showthread.php?t=2624875
Can I use the current recovery that I'm using? It's CWM v.6.0.3.7
I read that it's recommended to use a SELinux compatible recovery.
Someone in the thread said to use twrp 2.6.1 but I don't want to change from CWM to twrp.
So can I go ahead and install blue lightning? Do i absolutely HAVE to change to twrp? Or does the newest CWM for my phone work with installing the blue lightning build? (a link would be appreciated!)
Also, a question that I've always had, I don't have to install the first version of the rom right? I can just go ahead and install the zip of the latest build? That's what I've been doing, and when multiple updates come along, I install the latest build and not the builds in between. Can someone clarify this for me? I'm not doing something wrong right?
Thanks in advance for answering my lengthy question and helping me out.
Cheers :good:
svvparakala said:
Hey there guys,
I'm a noob so I had to post here. Although I've already read the intro guides to installing ROM's. Right now running the CM 11 nightly on my skyrocket. I'm looking for a better rom that has kitkat and I came across the Hellkat/BlueLightning roms. I wanted to install blue lightning but I have a couple questions before I mess anything up (I've read that being fully informed and taking precautions is a must)
So I wanted to know, if I'm installing this rom: http://forum.xda-developers.com/showthread.php?t=2624875
Can I use the current recovery that I'm using? It's CWM v.6.0.3.7
I read that it's recommended to use a SELinux compatible recovery.
Someone in the thread said to use twrp 2.6.1 but I don't want to change from CWM to twrp.
So can I go ahead and install blue lightning? Do i absolutely HAVE to change to twrp? Or does the newest CWM for my phone work with installing the blue lightning build? (a link would be appreciated!)
Also, a question that I've always had, I don't have to install the first version of the rom right? I can just go ahead and install the zip of the latest build? That's what I've been doing, and when multiple updates come along, I install the latest build and not the builds in between. Can someone clarify this for me? I'm not doing something wrong right?
Thanks in advance for answering my lengthy question and helping me out.
Cheers :good:
Click to expand...
Click to collapse
Poured your heart out I see. Ill try and clear things up. First of though, you can use either CWM or TWRP recovery's. I actually prefer CWM to. If you are installing Kit Kat though you do need CWM v6.0.3.7 or above! Also you need a Jellybean radio. As for the ROM I am running HellDevs Unofficial CM.11 Built using the Linaro toolchain, Works great! Also No you do not have to install the first versions, Just Wipe data, cache and dalvic. Use any version you want! Hope I helped if you have any more questions id be happy to help.
Thanks!
SighIsAnonymous said:
Poured your heart out I see. Ill try and clear things up. First of though, you can use either CWM or TWRP recovery's. I actually prefer CWM to. If you are installing Kit Kat though you do need CWM v6.0.3.7 or above! Also you need a Jellybean radio. As for the ROM I am running HellDevs Unofficial CM.11 Built using the Linaro toolchain, Works great! Also No you do not have to install the first versions, Just Wipe data, cache and dalvic. Use any version you want! Hope I helped if you have any more questions id be happy to help.
Click to expand...
Click to collapse
Ah, so it's not much different from when I was installing the CM 11. Thanks for the quick reply! :victory:
(P.S. how do you close a thread/mark it as answered?)
svvparakala said:
Ah, so it's not much different from when I was installing the CM 11. Thanks for the quick reply! :victory:
(P.S. how do you close a thread/mark it as answered?)
Click to expand...
Click to collapse
Anytime bub! I actually don't know how to close it. But leaving it up could help other people also.. Who have the same question.
Md5 Checksum?
SighIsAnonymous said:
Anytime bub! I actually don't know how to close it. But leaving it up could help other people also.. Who have the same question.
Click to expand...
Click to collapse
Actually I do have another question I was hoping you might be able to help me out with. I've heard that MD5 checksum is an important step. I downloaded the blulightning build. But when I copied the md5 checksum they had on the goo page, it didn't match the one on the zip file, or the md5 file that i downloaded (if i click on the md5 number on goo) Is something wrong? Or am i messing something up here?
Can't post this as a reply to the blue lightning thread yet, still under 10 posts :silly:
svvparakala said:
Actually I do have another question I was hoping you might be able to help me out with. I've heard that MD5 checksum is an important step. I downloaded the blulightning build. But when I copied the md5 checksum they had on the goo page, it didn't match the one on the zip file, or the md5 file that i downloaded (if i click on the md5 number on goo) Is something wrong? Or am i messing something up here?
Can't post this as a reply to the blue lightning thread yet, still under 10 posts :silly:
Click to expand...
Click to collapse
I usually don't check it. You did it all wrong though. There's a few ways to check the MD5, either through busybox on the phone or a app on the computer. Don't worry I thought the same thing you did when I started.:laugh: But here's a great thread with more information! http://forum.xda-developers.com/showthread.php?p=17065076 Personally though if you are sure you download the file correctly you should be good. Also most the time if something is wrong CWM Will tell you and not even let you flash it. Check that thread though it could maybe clear some things up for you.:angel:
Hi guys,
I'm no dev so I hope that somebody with experience can help me with this.
I need a stock kernel for Optimus 3D P920 v30A EU Open Official rom because after experimenting a little with other kernels after the last one(ibluemind's latest) the phone doesn't boot with any other kernel than ibluemind's.
Now please don't post solutions like flash stock rom etc. because I don't have the time to do all that stuff and the subject here isn't why or how to flash roms or kernels, I just want that stock kernel if it's possible. :fingers-crossed:
Thanx in advance.
Unfortunately, the only way to get the stock kernel back is to flash stock.
You can try something more tedious, if you really can't be bothered flashing back: Extract the kernel from the source.
Download the img of your ROM (v30A EU) and find a way to open it (I'd help you out even more by including a "how to" but unfortunately, I have no experience in meddling with img files). Just search around, it shouldn't take you a whole day to figure out everything you need to do.
And at least, you're on the majority (P920), it's easier to do things because most of the people here are on P920. I'm on SU760 so I have to do a bit more things for the phone.
Noxialis said:
Unfortunately, the only way to get the stock kernel back is to flash stock.
You can try something more tedious, if you really can't be bothered flashing back: Extract the kernel from the source.
Download the img of your ROM (v30A EU) and find a way to open it (I'd help you out even more by including a "how to" but unfortunately, I have no experience in meddling with img files). Just search around, it shouldn't take you a whole day to figure out everything you need to do.
And at least, you're on the majority (P920), it's easier to do things because most of the people here are on P920. I'm on SU760 so I have to do a bit more things for the phone.
Click to expand...
Click to collapse
Thanx for trying to help.
I've been here for a long time and tried almost every single rom from ported ICS to custom version of v30A. That's a lot of wasted time my friend.
Soft bricked my phone many times so it's not a problem for me to flash stock rom , I just don't have the time for setting up everything all over again.
I've got the rom but It's in .kdz form or if I extract it its in .bin+.fls.(rom+baseband).
But even if I convert BIN>IMG I don't know how to extract the kernel.
I don't know what files are related to kernel.
I already said that I'm not a dev.
But making the stock kernel from v30A flashable would really be useful for everyone.
Do you have a recovery? TWRP or CWM?
Try wiping System, maybe that can help.
Noxialis said:
Do you have a recovery? TWRP or CWM?
Try wiping System, maybe that can help.
Click to expand...
Click to collapse
Wkpark bootloaders v1.25 and TWRP 2.1.2.1.
The problem is that I deleted the damn backup of my stock rom.
That would solve the problem but I don't have it.
About wiping the system I really don't follow you. If you wipe the system there is no SYSTEM to boot the phone with. :laugh::laugh::laugh:
What was you point?
It follows, hahaha xD My apologies for making an incomplete statement.
Wipe the system then flash a new one in, although, I think you'd prefer to stay on a stock ROM.
I haven't come across any other kernel besides a v28B, so I really can't help you out with kernel choices (I avoid ones whose dev. has left us). If anything, flash Iodak's kernel and see if it will work. Don't mind the version difference for now.
I got something for you.
Search for the Jeckyll and Hyde kernel by developer "samno" it's great, in fact, it's what I'm using right now on OptimusRS's Simple ICS ROM.
Noxialis said:
I got something for you.
Search for the Jeckyll and Hyde kernel by developer "samno" it's great, in fact, it's what I'm using right now on OptimusRS's Simple ICS ROM.
Click to expand...
Click to collapse
Thanx, I forgot about that one.
I'll try it out. :good: