Related
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 .
Hello all,
I've been lurking the XDA forums for a couple months now. I had a couple posts in the past referring to my phone and my girlfriends phone and was looking for help mainly with hers at the time... Hers is fixed... Perfectly even, despite her phone being a total piece of garbage (an LG Optimus.... *barf*).
I have a SGH-T959V.
I have read the 10 commandments.
I KNOW my phone is NOT a Vibrant OR an i900.
I have read the noob guides.
I have become completely confused.
Here's my details:
I have running the stock GB that I installed with Kies Mini some time ago.
Phone Data:
Firmware Version: 2.3.6
Baseband Version: T959VUVKJ6
Kernel Version: 2.6.35.7-T959VUVKJ6-CL694130
Build Number: GINGERBREAD.VUVKJ6
I rooted my phone with one of the one-click apps after the stock GB update so that I was at least able to overclock it and get rid of the T-Mobile bloatware, etc.
I notice that my phone reboots entirely on it's own completely randomly, has random application hangs, all the bad icky stuff that sucks... (right????)
Anyways, I've looked at some of the Custom ROMs available and I'd like to check out some of them, but I'll be quite honest, I've read the instructions for how to do it, but I'm getting extremely confused as the current instructions seem rather daunting.... It's like information overload...
Now, don't get me wrong, I'm not some kid that really doesn't know what he's doing... I'm 33 and work in IT for The Nielsen Group... so I kinda know what the heck I'm doing MOST of the time. This is something I'm unfamiliar with and am being EXTREMELY cautious about because i don't want to brick my phone....
Question time!:
1. Is there a COMPLETELY SIMPLE step-by-step process/Video Demonstration for the CORRECT method of how to put a custom rom on the SGH-T959V?
2. Does it matter that I ALREADY rooted my phone in respect to me loading a custom rom? (ie. is my already rooted phone going to have issues loading a different rom?)
3. I would like to stay with a GB based rom unless there is absolute NEED to use a Froyo based Rom - Or is this a non-point when using custom roms?
4. If i want to load a custom rom to my phone, do I need to use a specific loader? (Like, does Odin work for everything??? Loading roms and unbricking your phone? Or do I have to have different loaders for the specific roms that I want to load and try out????)
5. Please don't jump down my throat with the "read the guide" responses... I HAVE been... really. As many as I've found... and every time I read a new one, rather than feeling like I'm coming out of the darkness of knowledge and into the light of understanding the correct process for how to do this, I feel like I'm being cast deeper down the confusion pit.
Would someone KINDLY please help me. Really... I don't want to screw up this thing... I'm not worried about the warranty. From what I've read, these things are mostly fixable unless it's an actual hardware issue or if it's totally fried. I just want to do it once, do it right, move on to my next project.... Dig?
First and foremost, we keep the most updated information in the wiki:
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4G
We've been updating it a lot lately so you're better off checking there. I'm sure you'll wanna bookmark it since you know what you're doing already.
1) Specifically you'll want to look at this section:http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4G#Installing_a_ROM
2) If you're using Odin/Heimdall you won't need to be rooted since this bypasses the phone's OS and flashes firmware directly to the phone which may or may not be pre-rooted. The only Odin 2.3.6 KJ6 rom that's out right now does NOT come with root though, it's just the stock version you're already running.
3) For our phone you're either going to use Odin/Heimdall (learn Heimdall, it's much more useful) and CWM Recovery. Most roms available right now are for CWM.
Here's the list of custom GB roms:
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4G_ROMs
4) Honestly the forums are too cluttered and as I stated above, knowledgeable senior members are the ones who update the wiki, so that'll be your most useful resource.
If you already have some experience with computers I'll gladly help you, you're already asking the right questions.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
FBis251 said:
First and foremost,
...
2) If you're using Odin/Heimdall you won't need to be rooted since this bypasses the phone's OS and flashes firmware directly to the phone which may or may not be pre-rooted. The only Odin 2.3.6 KJ6 rom that's out right now does NOT come with root though, it's just the stock version you're already running...
Click to expand...
Click to collapse
When I last played with my phone, I had used Odin on Windows... I have replaced Windows with Linux... I have installed Heimdall and did an initial test. So it is working.
My question is: Is Heimdall a valid replacement for Odin? In other words, I am wanting to use your guide, but it only refers to Odin. Can I go through those steps replacing Odin with Hamdall?
Yes it should work fine. The csc files for kc1 should be extracted over the pda files though
Sent from my SGH-T959V using XDA App
FBis251,
Thank you so much for the quick reply! I had seen it immediately after you responded, but was driving home from work and went right to bed. I'm back at the office now for the evening and perhaps may have some time to look into these tonight... I don't know as of right now.
If you are serious about the offer of some assistance, I would be more than open to it if I honestly felt it was needed. I am MORE than experiences with computers, i'm a full on uber-geek (just not with smartphones...... yet....), so VNC, etc would not be an issue.
I will most certainly get back to you about this in the next few days (perhaps even tonight). Let me see how my work load looks this evening and I will update the thread later.
Thank you again so much!
I'm usually in #teamnerd on freenode if you do IRC.
It doesn't take much to confuse me these days...
Moved my issue into a new question in the Q&A forum...
Hey, just an FYI (even tho I'm sure that ultimately you don't really care - just being realistic, not a douche... ), I haven't had a single moment to look into this beyond briefly skimming the Wiki's you linked up for me. (thanks for that one). I've had a butt-load of server issues at work that have taken a lot of my time. I'm HOPING to be able to look into some of this stuff a little deeper tonight (god willing)....
I will drop a note if I have issues....
Thanks again!
So I've been lurking on the forums for about 6 months and I finally decided to post my problem after not being able to find an answer for it on the forums. So here's my story. My infuse is currently running CM7. I had been running Infused v2.23 and the voodoo lagfix Kernal with it. I was enjoying it a lot when I decided to try out CM7. I had tried it before and decided it wasn't for me and tried to reflash Infused but it's was extremely laggy and the system kept crashing to the point where I couldn't do anything. It then bricked my phone and I had to get a new Infuse from AT&T. So I did this again because I thought it would be different and a change of pace. I'm not a huge fan of CM7 and I would like to go back to Infused but I'm afraid I will brick my phone again. So here's what I was thinking of doing. If you guys could tell me if this would work I would greatly appreciate it. I was thinking of wiping my system and cache and then formating the /system and then flash the voodoo lagfix Kernal. From there I would flash Infused again . I'm sorry if this is a nooby question. I just want some extra opinions before I do it. I use a Mac so I can't use Odin or the ultimate unbrick if something goes wrong. Thank you so much for answering in advance. I really appreciate any help you can give.
AnthonyBogucki said:
So I've been lurking on the forums for about 6 months and I finally decided to post my problem after not being able to find an answer for it on the forums. So here's my story. My infuse is currently running CM7. I had been running Infused v2.23 and the voodoo lagfix Kernal with it. I was enjoying it a lot when I decided to try out CM7. I had tried it before and decided it wasn't for me and tried to reflash Infused but it's was extremely laggy and the system kept crashing to the point where I couldn't do anything. It then bricked my phone and I had to get a new Infuse from AT&T. So I did this again because I thought it would be different and a change of pace. I'm not a huge fan of CM7 and I would like to go back to Infused but I'm afraid I will brick my phone again. So here's what I was thinking of doing. If you guys could tell me if this would work I would greatly appreciate it. I was thinking of wiping my system and cache and then formating the /system and then flash the voodoo lagfix Kernal. From there I would flash Infused again . I'm sorry if this is a nooby question. I just want some extra opinions before I do it. I use a Mac so I can't use Odin or the ultimate unbrick if something goes wrong. Thank you so much for answering in advance. I really appreciate any help you can give.
Click to expand...
Click to collapse
You do have recovery, Anthony.
It's call heimdall - one click "unbrick" back to stock works on mac.
Read this thread..it will help you get started.
http://forum.xda-developers.com/showthread.php?t=1523922
check my signature for links too
gl
bricked?
What do you mean by bricked? Was it stuck at the Samsung logo. You could always use Heilmdall or unbrick. i have noticed that most "bricks" are just bootloops.
niral7 said:
What do you mean by bricked? Was it stuck at the Samsung logo. You could always use Heilmdall or unbrick. i have noticed that most "bricks" are just bootloops.
Click to expand...
Click to collapse
you're right, niral.
most of the "brick" here is software related from corrupt file partition or boot loops due to mismatch file system, etc.
The true bricks are rarer.
qkster said:
You do have recovery, Anthony.
It's call heimdall - one click "unbrick" back to stock works on mac.
Read this thread..it will help you get started.
http://forum.xda-developers.com/showthread.php?t=1523922
check my signature for links too
gl
Click to expand...
Click to collapse
This is news to me, and I was wondering about this (I just assumed the recovery tools were all for PC). Anytime I had to go back to stock with odin, I had to seek out a friend with a PC. Thanks qkster. Learn something new everyday!
teknhard said:
This is news to me, and I was wondering about this (I just assumed the recovery tools were all for PC). Anytime I had to go back to stock with odin, I had to seek out a friend with a PC. Thanks qkster. Learn something new everyday!
Click to expand...
Click to collapse
anytime..
here is a direct quote from Adam Outler's 1click page:
"Heimdall One-Click's job is simple; it deploys firmware with one click while keeping the user informed. Heimdall One-Click is an open-source cross-platform(win/linux/mac), dependency installing, easy-to-use, automation tool which can install firmware onto a device in download mode. Heimdall One-Click's operation is very simple from the outside, but the operation is very complex inside. See source code for more information. Heimdall One-Click has several safety features built in which make it the safest method of deploying firmware to any compatible device."
qkster said:
anytime..
here is a direct quote from Adam Outler's 1click page:
"Heimdall One-Click's job is simple; it deploys firmware with one click while keeping the user informed. Heimdall One-Click is an open-source cross-platform(win/linux/mac), dependency installing, easy-to-use, automation tool which can install firmware onto a device in download mode. Heimdall One-Click's operation is very simple from the outside, but the operation is very complex inside. See source code for more information. Heimdall One-Click has several safety features built in which make it the safest method of deploying firmware to any compatible device."
Click to expand...
Click to collapse
Funny how you just get comfortable doing something a particular way even when it is totally inconvenient.. Wish I would have known about this before.
teknhard said:
Funny how you just get comfortable doing something a particular way even when it is totally inconvenient.. Wish I would have known about this before.
Click to expand...
Click to collapse
I stumbled upon Adam's Heimdall 1click Sept/Oct last year. It's simplicity is incredible.
1click flash to restore(2 if you need bl's). 1 click kernel. CWM, flash your rom.
no root, no 3e's, no rom manager, etc...
With this tool, idk why ppl don't use it more.
Hello Canadian users with SGH-T959W!
I spent some time the last few days comparing the kernel source for SGH-T959W and SGH-T959V, and found they are exactly the same (plus a few fixes for us on SGH-T959V from the SGH-T959W source!)!
This is good for you, because we have unofficial cm7, cm9, aokp, et alii... ports for the SGH-T959V.
Maybe a forum admin could update the Samsung Galaxy S 4G forum to also say: SGH-T959V & SGH-T959W
Technically, the only real difference is that the stock roms for the SGH-T959W will have different pre-installed software. The hardware of the SGH-T959W is the same as the SGH-T959V.
Enjoy!
Read this stuff to continue:
http://forum.xda-developers.com/showthread.php?p=28566711#post28566711
BTW, if anyone has an odin or kies tarball, please PM me!
This way I can verify if the bootloaders are different or not, and if they are different, I can make you guys custom Heimdall OneClick and Odin packages.
bhundven said:
I spent some time the last few days comparing the kernel source for SGH-T959W and SGH-T959V, and found they are exactly the same (plus a few fixes for us on SGH-T959V from the SGH-T959W source!)!
Click to expand...
Click to collapse
Sorry to bump this thread, but out of curiosity, what were the fixes you were able to implement after seeing the kernel source for the 959W?
If it's something you'd rather not explain and will just be rolling out in future kernels, no big deal; just curious.
Thanks.
fingolfin14 said:
Sorry to bump this thread, but out of curiosity, what were the fixes you were able to implement after seeing the kernel source for the 959W?
If it's something you'd rather not explain and will just be rolling out in future kernels, no big deal; just curious.
Thanks.
Click to expand...
Click to collapse
The hardware is exactly the same. There is still a problem with the OTA Assert, meaning, how the rom knows if it is able to install on the phone or not during install from cwm. Also how it identifies itself to the play store.
I'm fixing this in the next cm9 unofficial release (coming soon, eta... a few hours, maybe).
The only real difference between SGH-T959V and SGH-T959W is the pre-installed/bundled software on the phone.
Everything else is one-to-one.
I'm still paranoid about bootloaders. So I'm still waiting for someone to post Kies or leaked tar.md5 for the SGH-T959W so that I can diff the bootloaders. If they are different, I will create new Heimdall OneClicks for SGH-T959W so that it is simple for you to go back to stock. See my current Heimdall OneClick thread to get an idea of what I mean.
On the other hand, we have some issues with our SGH-T959V bootloaders, and I have Unbrickable Mod on my phone. So, if the bootloaders are different, I would like to try flashing the SGH-T959W bootloaders to see if they work any better.
Also, there are a few fixes in the SGH-T959W kernel source that I will be incorporating into the current unofficial CM7 and CM9 ports I work on. Not having these fixes shouldn't have any negative impact on SGH-T959W.
I hope this info is informative. If not, ask more!
I have a SGH-T959W which seemed to have a bad flash already (from before.. and I am trying to revive it) on it (seems stuck on the cwm screen, and the system partition doesn't seem to have all the data that it needs to). Is there any way of getting the original ROM for this phone? Even if I install a cm build for the T959V, I don't get errors but its stuck in a cwm loop (keeps coming back to cwm).
When I try any of the one-clicks for the T959V, it succeeds on the kernel upload but always fails on the modem upload.
Where would you look for the Kies tar for this phone? Any possible way of getting the original ROM from a brand new phone? (any instructions for these would be great)
bhundven said:
The hardware is exactly the same. There is still a problem with the OTA Assert, meaning, how the rom knows if it is able to install on the phone or not during install from cwm. Also how it identifies itself to the play store.
I'm fixing this in the next cm9 unofficial release (coming soon, eta... a few hours, maybe).
The only real difference between SGH-T959V and SGH-T959W is the pre-installed/bundled software on the phone.
Everything else is one-to-one.
I'm still paranoid about bootloaders. So I'm still waiting for someone to post Kies or leaked tar.md5 for the SGH-T959W so that I can diff the bootloaders. If they are different, I will create new Heimdall OneClicks for SGH-T959W so that it is simple for you to go back to stock. See my current Heimdall OneClick thread to get an idea of what I mean.
On the other hand, we have some issues with our SGH-T959V bootloaders, and I have Unbrickable Mod on my phone. So, if the bootloaders are different, I would like to try flashing the SGH-T959W bootloaders to see if they work any better.
Also, there are a few fixes in the SGH-T959W kernel source that I will be incorporating into the current unofficial CM7 and CM9 ports I work on. Not having these fixes shouldn't have any negative impact on SGH-T959W.
I hope this info is informative. If not, ask more!
Click to expand...
Click to collapse
phaedrus81 said:
I have a SGH-T959W which seemed to have a bad flash already (from before.. and I am trying to revive it) on it (seems stuck on the cwm screen, and the system partition doesn't seem to have all the data that it needs to). Is there any way of getting the original ROM for this phone? Even if I install a cm build for the T959V, I don't get errors but its stuck in a cwm loop (keeps coming back to cwm).
When I try any of the one-clicks for the T959V, it succeeds on the kernel upload but always fails on the modem upload.
Click to expand...
Click to collapse
This is annoying, sorry you are going through this. It sounds like something dorked your param.lfs.
I've had this happen to me, and it always appends 'bootmode=2' to the kernel command line. Only way to fix it is to flash a new param.lfs from the stock image...
phaedrus81 said:
Where would you look for the Kies tar for this phone? Any possible way of getting the original ROM from a brand new phone? (any instructions for these would be great)
Click to expand...
Click to collapse
...which brings me to this part. Someone told me that they have this image, but when I asked them to post it somewhere, I got no response.
Bug Wind and Samsung for a kies mini or a stock image that you can flash to the phone. Samsung is probably not going to be as helpful as Wind, so I'd try bugging the crap out of Wind.
Hopefully someone will get me the tar.md5 soon, and we can get you guys a one-click with bootloaders (which includes the param.lfs).
If you feel bold/brave, you can try flashing the bootloaders from my Stock oneclick in my signature.
Since it should be the same hardware it should work the same. Granted after flashing your phone will now be a SGH-T959V and not an SGH-T959W.
I hold no guarantee that it will work, and/or that it won't try to shoot you at your favorite new 3d film. <.< ... >.>
Thanks for the info about what might be causing the cwm loop issue
I think I will the one-click with bootloaders a try (will update this thread with the results). At this point I think I have exhausted all other options to revive the device.
bhundven said:
This is annoying, sorry you are going through this. It sounds like something dorked your param.lfs.
I've had this happen to me, and it always appends 'bootmode=2' to the kernel command line. Only way to fix it is to flash a new param.lfs from the stock image...
...which brings me to this part. Someone told me that they have this image, but when I asked them to post it somewhere, I got no response.
Bug Wind and Samsung for a kies mini or a stock image that you can flash to the phone. Samsung is probably not going to be as helpful as Wind, so I'd try bugging the crap out of Wind.
Hopefully someone will get me the tar.md5 soon, and we can get you guys a one-click with bootloaders (which includes the param.lfs).
If you feel bold/brave, you can try flashing the bootloaders from my Stock oneclick in my signature.
Since it should be the same hardware it should work the same. Granted after flashing your phone will now be a SGH-T959V and not an SGH-T959W.
I hold no guarantee that it will work, and/or that it won't try to shoot you at your favorite new 3d film. <.< ... >.>
Click to expand...
Click to collapse
phaedrus81 said:
Thanks for the info about what might be causing the cwm loop issue
I think I will the one-click with bootloaders a try (will update this thread with the results). At this point I think I have exhausted all other options to revive the device.
Click to expand...
Click to collapse
Also, just to make sure you have tried different cables and computers.
Not being able to flash the modem sounds like a cable/computer issue.
If you have that issue while flashing bootloaders, you could hard-brick your phone.
The first time you flash with the oneclick, it will not flash bootloaders. The second time, the option to flash bootloaders opens up, but you still have to enable it.
Don't forget to read all the documentation in my thread before doing anything.
If you have any questions, ask before you do.
The Root Doesn't work. I follow the step and it damaged my phone! T959W
bhundven said:
Hello Canadian users with SGH-T959W!
I spent some time the last few days comparing the kernel source for SGH-T959W and SGH-T959V, and found they are exactly the same (plus a few fixes for us on SGH-T959V from the SGH-T959W source!)!
This is good for you, because we have unofficial cm7, cm9, aokp, et alii... ports for the SGH-T959V.
Maybe a forum admin could update the Samsung Galaxy S 4G forum to also say: SGH-T959V & SGH-T959W
Technically, the only real difference is that the stock roms for the SGH-T959W will have different pre-installed software. The hardware of the SGH-T959W is the same as the SGH-T959V.
Enjoy!
Read this stuff to continue:
http://forum.xda-developers.com/showthread.php?p=28566711#post28566711
Click to expand...
Click to collapse
I try your root process for my T959W now My phone Can't turn on . It turn on and off with the glaxy S 4G logo and T-Mobile . HELP PLS i tried to unroot It does work and It . PLS HELPPPP!!!!!
GMK63 said:
I try your root process for my T959W now My phone Can't turn on . It turn on and off with the glaxy S 4G logo and T-Mobile . HELP PLS i tried to unroot It does work and It . PLS HELPPPP!!!!!
Click to expand...
Click to collapse
Please be more specific as to which 'process' you followed and what you did.
Sorry I've been delayed in responding!
Again, if you can be more specific as to exactly what you did, I will be better prepared to help you.
It does look like it could be a cable/computer issue. I tried different cables and some of them didn't get as far as the modem (failed the kernel upload as well). Haven't got a cable which succeeds in the modem flash yet.
All of the driver stuff on windows makes me nervous though. Is there any way to flash this on linux. Does the one-click package work with fastboot or can fastboot be used to flash the individual pieces?
bhundven said:
Also, just to make sure you have tried different cables and computers.
Not being able to flash the modem sounds like a cable/computer issue.
If you have that issue while flashing bootloaders, you could hard-brick your phone.
The first time you flash with the oneclick, it will not flash bootloaders. The second time, the option to flash bootloaders opens up, but you still have to enable it.
Don't forget to read all the documentation in my thread before doing anything.
If you have any questions, ask before you do.
Click to expand...
Click to collapse
phaedrus81 said:
It does look like it could be a cable/computer issue. I tried different cables and some of them didn't get as far as the modem (failed the kernel upload as well). Haven't got a cable which succeeds in the modem flash yet.
All of the driver stuff on windows makes me nervous though. Is there any way to flash this on linux. Does the one-click package work with fastboot or can fastboot be used to flash the individual pieces?
Click to expand...
Click to collapse
These phones do not have fastboot, but they have download mode.
Yes, you can do this from: Windows, Linux, or Mac OS X
If you still have problems with multiple cables, I highly recommend trying a different computer. I've had this problem myself before. It drove me nuts until I got a friends laptop and everything worked perfectly. My laptop's usb ports had gone bad for some unexplainable reason.
Check out the wiki pages we have written:
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959V
Steps I followed
managed to get my Wind SGH-T959W rooted and up and running with a unofficial CM9 build, but it took a bit of work.
Firstly, I tried just about every one-click solution out there, to no avail. It's possible SOC 1.7 with rattlethecage works, but I didn't have the patience to find out whether I simply had to wait a bit longer.
I followed this guide(whilst clenching every clenchable muscle I could consciously control):
http://www.galaxyforums.net/forum/of...ngerbread.html
The gist is, Odin 1.7, stock+voodoo for T959V, plus some update that I'm not qualified to describe. That should get you rooted and if that's all you're looking for, you'll have to suffer through a little T-Mobile branding on startup.
Once you got it all rooted, you'd think it'd be a good idea to toss sgs-ics on there, right? Well, no. After installing the 4G variant, it promptly set off into a boot loop which I'm again, unqualified to diagnose. The obvious solution was to try another team's version of ICS, which I indeed found here:
http://forum.xda-developers.com/show....php?t=1730954
Barring some missing features, it sounds like a good alternative to sgs-ics. Though I had to go through one additional step, which I really, honestly assure you I was under-qualified to execute. When I tried to load Team Acid's CM9 r3 it gave me an assert on the updater-script, since the hardware didn't match up. Easy. Unzip the package, open up META-INF/com/google/android/updater-script, remove the first check. You know it's the same hardware, you don't need some stinkin' script to tell you it won't work.
So all said and done, I now have a Wind Mobile SGH-T959W running ICS 4.0.4 courtesy of bhundven, the Odin folks, Team Acid, and likely a slew of other contributors.
Thanks folks, and enjoy!
PS, if you want that tarball bhundven, send me a PM with some brief instructions, and hopefully you can help my fellow Winders.
.......(---------THAT WHAT I FOLLOWED .
But I did the first part and They said i should get the stuff I store on my SD Card to pull out a file (``12) In CWM, use your volume up/down positions to navigate, scroll down to "Install Zip From SDcard". Select with a click of the power button. Navigate to where you put sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip (in the root of your SDcard) and select with the power button. Confirm you want to install.
``)
but it doesn't give me the option to go get it on my SDcard and Now my Phone just turns on and off with the samsung galaxy S logo plus T-mobile exclusive logo . The only possitive thing about all the damage is that I can still put my phone on dowload mode and I just think if someone knows how to get my phone back to it state they will need me to put it on download mode. :crying:
:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
Thank you in advance for your Help, for replying and offering to help.:highfive:
I appriciate it. My phone is Mobillicity carrier just like wind .
GMK63 said:
.......(---------THAT WHAT I FOLLOWED .
But I did the first part and They said i should get the stuff I store on my SD Card to pull out a file (``12) In CWM, use your volume up/down positions to navigate, scroll down to "Install Zip From SDcard". Select with a click of the power button. Navigate to where you put sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip (in the root of your SDcard) and select with the power button. Confirm you want to install.
``)
but it doesn't give me the option to go get it on my SDcard and Now my Phone just turns on and off with the samsung galaxy S logo plus T-mobile exclusive logo . The only possitive thing about all the damage is that I can still put my phone on dowload mode and I just think if someone knows how to get my phone back to it state they will need me to put it on download mode. :crying:
:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
Thank you in advance for your Help, for replying and offering to help.:highfive:
I appriciate it. My phone is Mobillicity carrier just like wind .
Click to expand...
Click to collapse
Ok, this is really simple. I've explained it in quite a few threads in the Galaxy S 4G forums in General, Q&A, and the Dev forum. I'm going to explain this, but in a way to be more general. So I'm being verbose in case anyone else with a T959W happens to run across this and has not tried anything yet.
Again, I'm not good with windows at all, and I prefer it that way.
If you're on windows, check out our wiki:
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959V
There is tons of help there for setting up heimdall on windows with all the right drivers and such.
Once you have heimdall setup get AntonX's latest cwm zip for his kernel.
This kernel is a BML kernel, and this guide I am giving you right now will help you get cm9 installed which is an MTD kernel. You can find out more about BML vs. MTD here.
Once you have downloaded AntonX's kernel, extract the zImage from it and open up the terminal/cmd prompt and navigate to the directory you extracted the zImage to.
Put your phone into Download Mode and type the following in the command prompt:
Code:
heimdall flash --kernel zImage
The heimdall program will flash this kernel+initramfs to the kernel partition and reboot the phone. Do not unplug the usb cable until you see the "Galaxy S" screen. When you see that screen, unplug the usb cable and remove the battery from the back.
Assuming you downloaded CM9 and put it on your sdcard already, you can get into recovery by holding the vol+ and vol-, then pressing the power button to turn the phone on. When you see the "Galaxy S" screen, let go of the buttons, and you should be in the recovery now.
This is where things get a little tricky. If you have not tried to do anything to your phone yet. This would be a great time to use the "Backup and Recovery" menu on CWM. Do a full backup.
The "assert 7" error that the previous person got was because the cwm install script (the updater-script) checks the already installed /system/build.prop's data against the "to be installed" build.prop to verify this rom can be installed. If it doesn't exist, then it moves forward.
So the first order of business is to wipe the /system partition. Go to "Mounts and Storage" and format the system partition.
Now go back to the main screen and do "Factory Reset/Wipe Data".
Now go "Install zip from sdcard" -> "choose zip from sdcard" -> and use the volume keys to select the zip file.
After the rom is installed, navigate back to the main screen and "Reboot the system now" if it doesn't reboot by itself.
When the phone reboots, because it is going from BML to MTD, it obviously can't just install the files to what would be an MTD partition if the kernel knows nothing about MTD. So it boots into the newly installed MTD kernel and continues the installation, which in the end will also reboot again.
The first boot is very slow. It is building a cache of all the pre-installed system applications. Let it sit for a while. I know it's tempting to go play with your phone right away, but resist if you can.
The next CM9 release will be on a different kernel, and albeit a much better rom.
I will also be adding OTA Asserts for SGH-T959W so that you will not have to wipe /system before installing the rom, but I do that still just for good measure. But this also means that your phone will work properly with the google play store.
If this still does not work, please let me know what went wrong and I will be happy to assist!
-Bryan
Confused
bhundven said:
Ok, this is really simple. I've explained it in quite a few threads in the Galaxy S 4G forums in General, Q&A, and the Dev forum. I'm going to explain this, but in a way to be more general. So I'm being verbose in case anyone else with a T959W happens to run across this and has not tried anything yet.
Again, I'm not good with windows at all, and I prefer it that way.
If you're on windows, check out our wiki:
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959V
There is tons of help there for setting up heimdall on windows with all the right drivers and such.
Once you have heimdall setup get AntonX's latest cwm zip for his kernel.
This kernel is a BML kernel, and this guide I am giving you right now will help you get cm9 installed which is an MTD kernel. You can find out more about BML vs. MTD here.
Once you have downloaded AntonX's kernel, extract the zImage from it and open up the terminal/cmd prompt and navigate to the directory you extracted the zImage to.
Put your phone into Download Mode and type the following in the command prompt:
Code:
heimdall flash --kernel zImage
The heimdall program will flash this kernel+initramfs to the kernel partition and reboot the phone. Do not unplug the usb cable until you see the "Galaxy S" screen. When you see that screen, unplug the usb cable and remove the battery from the back.
Assuming you downloaded CM9 and put it on your sdcard already, you can get into recovery by holding the vol+ and vol-, then pressing the power button to turn the phone on. When you see the "Galaxy S" screen, let go of the buttons, and you should be in the recovery now.
This is where things get a little tricky. If you have not tried to do anything to your phone yet. This would be a great time to use the "Backup and Recovery" menu on CWM. Do a full backup.
The "assert 7" error that the previous person got was because the cwm install script (the updater-script) checks the already installed /system/build.prop's data against the "to be installed" build.prop to verify this rom can be installed. If it doesn't exist, then it moves forward.
So the first order of business is to wipe the /system partition. Go to "Mounts and Storage" and format the system partition.
Now go back to the main screen and do "Factory Reset/Wipe Data".
Now go "Install zip from sdcard" -> "choose zip from sdcard" -> and use the volume keys to select the zip file.
After the rom is installed, navigate back to the main screen and "Reboot the system now" if it doesn't reboot by itself.
When the phone reboots, because it is going from BML to MTD, it obviously can't just install the files to what would be an MTD partition if the kernel knows nothing about MTD. So it boots into the newly installed MTD kernel and continues the installation, which in the end will also reboot again.
The first boot is very slow. It is building a cache of all the pre-installed system applications. Let it sit for a while. I know it's tempting to go play with your phone right away, but resist if you can.
The next CM9 release will be on a different kernel, and albeit a much better rom.
I will also be adding OTA Asserts for SGH-T959W so that you will not have to wipe /system before installing the rom, but I do that still just for good measure. But this also means that your phone will work properly with the google play store.
If this still does not work, please let me know what went wrong and I will be happy to assist!
-Bryan
Click to expand...
Click to collapse
I have Window 7 and I went on wiki. I don't know what rom or what I am suppose to download to get heimdall . Plus the steps is not for T959W.
GMK63 said:
I have Window 7 and I went on wiki. I don't know what rom or what I am suppose to download to get heimdall . Plus the steps is not for T959W.
Click to expand...
Click to collapse
:facepalm:
Then send your phone back to Mobillicity. Tell them that you don't know what a smart phone is and did something stupid to it. Go get yourself a nice clamshell phone.
I gave you explicit instructions that work for SGH-T959V and SGH-T959W. As a matter of fact, these instructions work on any "Galaxy S" phone, but you shouldn't flash just any other phone's rom to any other phone.
It just so happens that the SGH-T959V and SGH-T959W are the same exact hardware, just pre-packaged with different software and sold in different regions.
THEY ARE THE SAME PHONE!
With that, I am done with this thread. It was not meant for support! It was merely an announcement.
If you need any more help, please check out the Galaxy S 4G forums.
You can find plenty of directions that will work on either SGH-T959V or SGH-T959W on the wiki.
If you are looking for general information, look at the General forum.
If you need help or are asking a question, look at the Q&A (Questions and Answers) forum.
If you are looking to provide constructive feedback and/or logs to help development of ROMs and Kernels, check out the Developer forum. (Note, do not ask questions in the developer forum).
Don't forget the XDA Forum Rules
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.