Related
I bought a T-Mobile Galaxy S T959. When it turns on, it says "Samsung Galaxy S GT-i9000", then the screen changes to "Samsung VIBRANT" I reflashed back to stock using odin, but it still shows the same gt-i9000 boot screen.
Does anyone know how to change it back to normal? So far, I have rooted the device, installed clockwork and flashed to the bionix rom, and installed sgs kernel flasher from the market.
I watched some videos online that showed the kernel boot screen changing after flashing a new kernel through sgs kernel flasher, but I dont know much about kernels or which one needs to be flashed.
Does anyone know what needs to be done, or have any ideas I should try?
Thanks
Well theres nothing wrong with that but it seems like it bothers you so which kernel did u used to odin???
Sent from my SGH-T959 using XDA Premium App
This is happening because the phone in the past was flashed with an I9000 based kernel. Eugene I beleive used to make some back before we had Froyo. I also had that bootup screen for a while. I don't have it anymore.
I believe I lost it through one of the many kernel flashes I have done. Just flash some of the latest kernels. It MAY clear this issue for you though it really is not an issue.
It is just the wrong picture stuck in some folder on the phone. There is no harm done to your phone nor is there anything wrong or defective with it. The only thing is that it may bother you. If it does bother you, go on a flashing spree and flash some kernels and roms. I think sooner or later you will get rid of it without even trying when you upgrade your ROM/Kernel.
Thank you, I appreciate your replies.
I bought this phone from someone online, so it was like this when I got it. Therefore I am unsure of which roms/kernels were flashed onto it in the past. I have flashed many roms, but those only seem to change the boot animation. The kernel boot screen is staying the same. Like I said, I dont really know much about kernels.
Would there be one which you recommend I try that might fix it?
I know its not really a problem, but for some reason it just annoys me seeing it say gt-i9000 at startup.
My ultimate goal is to be running the latest build of team whiskey's bionix rom. I have no clue which kernel I should flash or that would work with it.
Any help or advice is greatly appreciated.
Thank you
Try the bullet kernel.
http://edtdev.com/forum/topic/86-kernelbullet-1420ghz-4202011/
It is the fastest kernel for the Vibrant to date (1.42Ghz STABLE on most phones, outstanding battery life, all features and tweaks). It also has a custom boot screen which MAY replace your I9000 one. I'm saying MAY because I am not fully sure. In either case it is either the best or one of the best kernels for this phone to date.
As for ROMs, Team Whiskey quit Vibrant development around late February. They have moved on the the Nexus S and G2X so I'm not sure their latest ROM is the best. It's certainly an amazing ROM but there may be more recent ROMS which have more features or speed. Choice is yours.
You may try flashing some Froyo kernels from Eugene. Since his kernels likely introduced the I9000 boot you have now, flashing newer versions MAY get rid of it...who knows. Alternatively, there is another option if you are SET on getting it out.
If you flash with ODIN and also check repartition, I beleive ODIN will WIPE everything off the phone completely. Yes, all backups...everything will be gone but it should in theory also take that I9000 with it. It's a bit more risky than normal ODIN but the choice is there if you are set on it. Try the other options first and if you decide to do a repartition, READ on how to do it properly first.
@}{Alienz}{
Thank you, I tried to flash a few kernels and it seems to me like what you said about the wrong picture being stuck in the phone is what the problem is.
I Re-flashed with Odin and did a re-partition as well, but the image is still there. After rooting and flashing the bullet kernel, it still shows the gt-i9000 screen and then it switches to the bullet screen instead of the vibrant one it used to be.
After trying a few kernels, they all seem to replace the screen after the i9000 kernel screen.
Im going to keep trying to get rid of it, but i wanted to thank you for your response as I am one step further now.
Ah. Dumb-stuck image problem then huh. I thought the kernels would flash it right out. Well...you can ask someone above me about how to get it out.
Go to the EDT dev website. www.edtdev.com and join their IRC. See if a developer there can help you out with getting rid of it.
Also try the Team Whiskey IRC chat. They have more devs and people in their IRC that may be able to help. Their chat is located here:
http://webchat.freenode.net/?channels=teamwhiskey&uio=d4
I'm sure someone at those IRC chats will help you out.
try flashing the stock "param.lfs" file through odin
Okay I have had this problem and know exactly how to fix it. What happened was whoever had that phone before you flashed an I9000 gingerbread kernel with I9000 gingerbread bootloaders, that's why it shows that every time. Here is what I did to fix it. I don't know if it has to be done this way, this is just how I did it.
Step 1: download both of these files
PDA:http://dl.dropbox.com/u/23420259/Eugene_JK2_Froyo.tar.md5
PIT:http://dl.dropbox.com/u/23420259/s1_odin_20100512.pit
Step 2: Flash those files through Odin, but make sure you uncheck repartition, as I have read that if you leave it checked while flashing those files you might end up with a hard bricked phone. It will boot straight into recovery after it's finished flashing and will have some errors, that's okay just click reboot system now.
Step 3: Odin back to stock 2.1 like normal.
After you do that and Odin back to stock 2.1 wait like 10 minutes and then flash whatever rom you like. After step 2 though you should be rid of that awful GT-I9000 boot screen. I just Odined back to stock 2.1 to get rid of the broken recovery. I don't think you have to do this.
Let us know if this helped you, so that if it doesn't work someone might have an alternate way to fix it.
Oh also before I forget, I have to give credit where credit is due. Those are files are Eugenes files and I am in no way saying that I developed or had a hand in developing them.
Sorry for posting here but this is where I was instructed to post. So I just dl ics v8 last night, which is AWESOME by the way!! Thx for all the hard workers that put this rom together. Im coming from bionix by the way and dont know too much about ICS. So I odined a custom gb bl as instructed and that went fine, I got the pass. I then flashed v8 and let it sit over night and so far so good. I do have a few questions/concerns though for anyone who can help.
1. I did have to mute/unmute during a ph call so it didnt sound like I was in a can...
2. Which root apps can I use with this rom...? ie setcpu, rom manager...? I tried creating a recovery with rom manager and I got a message that "theres no official clockworkmod recovery yet and have I installed a clockworkmod based recovery yet...?" Is this supposed to happen..?? Basically just wondering if I did something wrong along the way...
I think thats it so far, otherwise havent tried gps yet so Im crossing my fingers. Thx again.
Rjevon said:
Sorry for posting here but this is where I was instructed to post. So I just dl ics v8 last night, which is AWESOME by the way!! Thx for all the hard workers that put this rom together. Im coming from bionix by the way and dont know too much about ICS. So I odined a custom gb bl as instructed and that went fine, I got the pass. I then flashed v8 and let it sit over night and so far so good. I do have a few questions/concerns though for anyone who can help.
1. I did have to mute/unmute during a ph call so it didnt sound like I was in a can...
2. Which root apps can I use with this rom...? ie setcpu, rom manager...? I tried creating a recovery with rom manager and I got a message that "theres no official clockworkmod recovery yet and have I installed a clockworkmod based recovery yet...?" Is this supposed to happen..?? Basically just wondering if I did something wrong along the way...
I think thats it so far, otherwise havent tried gps yet so Im crossing my fingers. Thx again.
Click to expand...
Click to collapse
All root apps work. The rom/kernel already has recovery, no need for Rom Manager. You can get to it via the power menu, or the finger boot by now pressing VOL DOWN+POWER. Also VOL UP+POWER will boot in download mode.
Rjevon said:
Sorry for posting here but this is where I was instructed to post. So I just dl ics v8 last night, which is AWESOME by the way!! Thx for all the hard workers that put this rom together. Im coming from bionix by the way and dont know too much about ICS. So I odined a custom gb bl as instructed and that went fine, I got the pass. I then flashed v8 and let it sit over night and so far so good. I do have a few questions/concerns though for anyone who can help.
1. I did have to mute/unmute during a ph call so it didnt sound like I was in a can...
2. Which root apps can I use with this rom...? ie setcpu, rom manager...? I tried creating a recovery with rom manager and I got a message that "theres no official clockworkmod recovery yet and have I installed a clockworkmod based recovery yet...?" Is this supposed to happen..?? Basically just wondering if I did something wrong along the way...
I think thats it so far, otherwise havent tried gps yet so Im crossing my fingers. Thx again.
Click to expand...
Click to collapse
As for the mute / unmute thats a bug thats is well spoken about and as the forum for ICS passion it is a beta stuff is still being worked out just b patient
Rjevon said:
Sorry for posting here but this is where I was instructed to post. So I just dl ics v8 last night, which is AWESOME by the way!! Thx for all the hard workers that put this rom together. Im coming from bionix by the way and dont know too much about ICS. So I odined a custom gb bl as instructed and that went fine, I got the pass. I then flashed v8 and let it sit over night and so far so good. I do have a few questions/concerns though for anyone who can help.
1. I did have to mute/unmute during a ph call so it didnt sound like I was in a can...
2. Which root apps can I use with this rom...? ie setcpu, rom manager...? I tried creating a recovery with rom manager and I got a message that "theres no official clockworkmod recovery yet and have I installed a clockworkmod based recovery yet...?" Is this supposed to happen..?? Basically just wondering if I did something wrong along the way...
I think thats it so far, otherwise havent tried gps yet so Im crossing my fingers. Thx again.
Click to expand...
Click to collapse
ok ROM Manager has Never had Official support for the Samsung Vibrant. If you install Rom Manager the only thing you should be doing with it is "fixing Permissions" other then that you should be rebooting into the preinstalled recovery by pressing and holding power button ---> Reboot ---> Recovery
again do not do ANYTHING other then fix permissions within Rom Manager.
all ICS/Samsung Vibrant Compatible applications are working with this rom. all root functions are working. and OC/UV utilities should work.
Thx peeps for the info. Just waiting for bug fixes. Otherwise great from!
Hey there.
Ok, so don't blame me for sounding stupid or anything because I have just risen from Apple-Hell into the world of Android and I am not at all familiar with kernels, flashing and all that. I plan to read and learn more about it and if someone would be kind enough to maybe post a link to a basic guide or something, that would be great.
Now to my real problem.
I got my SGS3 a couple of days ago and since I don't like the looks of the new UI, I figured I have to root it. So I did, with Odin and now I'm planning to install CyanogenMod's nightly build. BUT, I can't seem to boot into CWM recovery, and instead it boots into the stock recovery. I have googled the problem with no luck. So, I came here in hope that someone has a solution.
If this topic has already been brought up, then I'm sorry, but I'm not really a forum-type of guy
http://forum.xda-developers.com/showthread.php?t=1703488
Thanks for the quick reply, I'll check it out
Not sure about how you did root the phone, but i used the method from Chainfire with CF-Root ... This method puts the recovery manager in place and it should boot into there when using the volume-up, home-key and power button at the same time.
http://forum.xda-developers.com/showthread.php?t=1695238
If this not happens you maybe can try to do this rooting again.
Yes, thank you. That was exactly what I was looking for. It works as it should now
Hello all,
I have a question that has not been answered after many hours of searching. Hopefully I'm just dumb, and my buddy's stock firmware and data isn't hosed. I'm trying to get his stock firmware running again so I can back it up safely.
What I've done:
Tried to flash CWM's update.zip via stock recovery (signature verification failed on the three different zip's I could find in the forums and various links)
Used Heimdall to push "cmenard-T959-CWM" zImage (this worked, and I get a different screen at boot)
The phone boots to the point of the T-Mobile splash screen with the annoying shriek sound, but goes to a black screen after. If i touch any of the soft buttons, they light up and remain lit. It'll stay like that for at least 20 minutes.
Is it possible to re-flash the system partition and not the data partitions using ODIN? Is that even feasible? Like I mentioned above, I'd like to get the stock firmware running such that I can make a good backup of it with all the user data intact. I haven't been able to because the CWM+root wouldn't flash.
Any suggestions or insight would be greatly appreciated.
thanks in advance!
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Toast6977 said:
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Click to expand...
Click to collapse
Thanks for the suggestion, Toast. I don't believe the internal SD has been messed with, and I don't plan to mess with it either. The thread you linked is not quite related to my issue, as far as I can tell.
I am able to get into Download Mode, and the Stock Recovery mode as well. However every time I try to flash an 'update.zip' with the Stock Recovery, I get an error about Signature Verification Failure.
After stepping back from it for a day, I think I've gained some clarity. Since all I've done is flash a different Kernel with Heimdall, I'm going to try to flash a stock kernel then see what happens.
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Toast6977 said:
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
Click to expand...
Click to collapse
Woodrube said:
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Click to expand...
Click to collapse
hahaha poltergeist!
Wow, so I'm glad I asked. I wouldn't have known about this issue, as I do not have any history with this device.
I know that the ROM is currently 2.2, and the Android System Recovery is showing "3e".
If I understand correctly, once I'm ready to flash up to ICS, I'll need to ODIN back to 2.1 to get Android System Recovery "2e", which will let me flash 'update.zip' packages freely. Then I flash an 'update.zip' to get CWM, then flash CM7, then CM9 (and CM9 is my intended destination).
The things mentioned in the thread you linked do appear to apply to my situation.
However I still want to get the stock OS booted and working, then do a Nandroid backup of it. (it's the computer tech/security pro in me. Since I'm new to this device, I -tried- to read up on everything first, and didn't want to make a change without being sure it would work.)
Does anyone happen to know if flashing a stock kernel over the 'cmenard' kernel will harm anything, and hopefully get a successful boot? Again, I'm trying to get the stock ROM booting again in order to verify I have everything I need off of it, then do a nandroid backup. Flashing to CM9 will come afterwards.
Ok, here are some things for you.
Here is a kernel pack that you can use. Read the OP because there are Froyo AND Gingerbread kernels in there.
[KERNELS] Moped_Ryder SGS Kernel Pack v2 [20+ Froyo/GB Kernels]
I really suggest using something like BaliX 1.2 or BaliUV kernels to make your back up. They are smooth, fast and OC/UV-able. To flash just Wipe /cache, /dalvik -> flash kernel -> Wipe /cache, /dalvik (I also fix permissions too bc that is the way that I learned and I just do it that way all the time). Reboot and Bam!! you should be able to get to the point that you can make a backup.
Look in my signature, there are downloads and flashables that are direct download linked. There is also an ICS install guide that can help your journey. Once you have your backup, then use Odin from the Toolbox in my signature and flash back to stock JFD. From there you will be able to follow my guide.
If you need any files, just let me know and I will upload them when I get home (won't be until late though, i have plans right after work).
Using HB, can I choose any theme? I am not so acquainted with the Theme chooser and boot animation of my phone. I flashed a boot animation zip yesterday and it was stuck in "ANDROID" screen. So I have to flash again. I never used any boot animation and themes in my phone yet. I want to know about them.
Sent from my SGH-T959 using xda app-developers app
Wrong thread. Put that question in the Jelly Bean Banter thread. No need to hijack this thread until we get OP up and running.
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
maxpeet said:
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
Click to expand...
Click to collapse
Wrong they are not the same. cwm can do the work without a PC beside you can erase, back up , restore and flash, which make our life easier, heimdall or Odin ," I prefer odin "are the last option when you can't fix it with cwm
To fix your phone use Odin or heimdall and go back to stock don't worry all your files, photo, music, will be safe. Then
1 get root on you , if you don't how ask
2 get cWm
3 do a nandroid back up
4 have fun flashing all roms you want lol
Sent from my SGH-T989 using xda app-developers app
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Toast6977 said:
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Click to expand...
Click to collapse
do no check de re-partition button and use a .pit file follow this tutorial and you will be fine
http://forum.xda-developers.com/showthread.php?t=848737
Ok so I've been unhappy with the 4.0.4 official ATT update and its caused my phone once or twice a day to shut off and I have to pull the battery out. So I got the bright idea to root it. I'm not a stranger to this I had the captivate and infuse before this phone. I had roms on those with no issues. Now I followed this thread http://forum.xda-developers.com/showthread.php?t=1746181 and the phone crashes on bootup saying google account manager has stopped and wont even let me get past it. Then I tried another kernal SGH-I777-ATTGalaxyS2RootStockZedomaxKernel.tar and that just has a yellow ! up and never even gets any further
I've spent 7 hours now in a row reading posts, to be frank, the attitude here SUCKS. Instead of people answering the question they point you off to some post you already read 10 times before, already tried and it doesnt work. I've also tried just putting it back to factory with I777UCKH7-CL503881-No-BL.exe and that doesnt work either
Put your phone in download mode. (power it off, hold down the volume down button and insert the usb cable)
Flash this with Odin in the PDA slot, auto reboot the only thing checked:
http://d-h.st/UWm
So I'm assuming seven hours is a lot for you? I've been reading here for over a year and I'm still learning. Really to root all you would have had to do is flash a kernel in .tar format with Odin (our kernels come with cwm built in remember) obviously you would want one that's compatible with the version of android you're using. There is a lot of information here. But to say the " attitude here sucks" like you did..... Yer wrong. I know sometimes it seems harsh, but we're just trying to get people to do things for themselves and thus learn even more, positively influencing them in the end.
I think I see your problem. Perhaps if you drop the entitlement attitude you might get more help. No one here is obligated to help anyone. The people that do are unpaid volunteers willing to share their expertise. This is NOT the Help Desk. Remember that before you consider making another ungrateful post like this one.
XDA-dev's are free volunteers, first of all.
We are here for the last someyears and we had providing the best help for anyone related to the phones, eventough devs always repeat that dont mirror us, many people do mirror thier works and someone claims tgat they had done it and yet this site is considered as the best resources for android fanboys.
The another thing is that we are professionals who spare our minute free time for the betterment of phones and to.unlock the hidden capabilities of phone.
I could say to you that have patience and patience never makea you sad.....
BE GOOD
Sent from my GT-S5360 using xda app-developers app
If I was a moderator, the last 3 posters would be banned, permanently. Don't you guys have something better to do then to pick at the frustration comments of user who's phone is not working at the moment?
rodimus_prime said:
I've spent 7 hours now in a row reading posts, to be frank, the attitude here SUCKS. Instead of people answering the question they point you off to some post you already read 10 times before, already tried and it doesnt work. I've also tried just putting it back to factory with I777UCKH7-CL503881-No-BL.exe and that doesnt work either
Click to expand...
Click to collapse
Ever hear the expression "you catch more flies with honey than vinegar" ?
Everyone on this forum has been able to load custom firmware using the posts you've been linked to -- everyone except you. So, instead of getting upset with everyone else, take a deep breath and try again.
---------- Post added at 09:47 AM ---------- Previous post was at 09:46 AM ----------
r00t4rd3d said:
If I was a moderator, the last 3 posters would be banned, permanently.
Click to expand...
Click to collapse
Thankfully you're not a moderator.
rodimus_prime said:
Ok so I've been unhappy with the 4.0.4 official ATT update and its caused my phone once or twice a day to shut off and I have to pull the battery out. So I got the bright idea to root it. I'm not a stranger to this I had the captivate and infuse before this phone. I had roms on those with no issues. Now I followed this thread http://forum.xda-developers.com/showthread.php?t=1746181 and the phone crashes on bootup saying google account manager has stopped and wont even let me get past it. Then I tried another kernal SGH-I777-ATTGalaxyS2RootStockZedomaxKernel.tar and that just has a yellow ! up and never even gets any further
I've spent 7 hours now in a row reading posts, to be frank, the attitude here SUCKS. Instead of people answering the question they point you off to some post you already read 10 times before, already tried and it doesnt work. I've also tried just putting it back to factory with I777UCKH7-CL503881-No-BL.exe and that doesnt work either
Click to expand...
Click to collapse
Use the return to stock guide to go back to stock GB. Never go to another site other than ours as the other sites have ad kernels which break wifi or brick phones. Once you flash the GB stock go into 3e recovery and wipe by holding power and both volume buttons. Use the volume keys to move up and down and power to select. If power doesnt work then use home. Once you boot up you can set up or whatever. Next follow the Flash Custom Firmware Without Incrementing Flash Counter. Make sure to use a GB kernel in Mobile Odin. Now you can flash custom roms using CWM if you did it right. If you flash an ICS rom you can use Triangle Away to remove that triangle at boot up. You can also use a jig which is safer and able to be used on any version.
r00t4rd3d said:
If I was a moderator, the last 3 posters would be banned, permanently. Don't you guys have something better to do then to pick at the frustration comments of user who's phone is not working at the moment?
Click to expand...
Click to collapse
You need to be here more than a month to understand where those 3 posters are coming from.
7 hrs wasted. If you want help, shoot me a pm and I'll help you before I get hammered tonight. You have 4 hrs and counting....
jthatch12 said:
7 hrs wasted. If you want help, shoot me a pm and I'll help you before I get hammered tonight. You have 4 hrs and counting....
Click to expand...
Click to collapse
Or PM me cause I won't be hammered. Also reference the guide I posted as well.
I managed to get Serendipity 9.4 loaded on it and its seeming to work however I dont seem to be able to get anything else to not boot loop or fail
I'd be happy with a rooted ICS, dont really need all the fancy stuff but when I try to use this http://forum.xda-developers.com/showthread.php?t=1746181 I cannot get it to load stable, I get bootloops, non stop force closes.
I did seem to fix the power button issue, took it apart and swapped the button with a damaged i777 I had laying around here and thats working now, so really I just need the stock ICS on it and thats the extent of any tinkering I ever want to do with this phone again.
I picked up a Optimus G today as a replacement, god I hate it, the music sounds like garbage and the camera is worse. Theres about zero cases made for it. I have 13 days now to return it so I'm hoping I can resurrect my GS2.
It says to If flashing this from another base, you should perform a wipe data/factory reset before you flash this package, should I flash the package first? Seems like after that I only have 3E recovery instead of clockwork mod, which I need to flash the kernal, or should I do the kernal first? These things are not really detailed
rodimus_prime said:
I managed to get Serendipity 9.4 loaded on it and its seeming to work however I dont seem to be able to get anything else to not boot loop or fail
I'd be happy with a rooted ICS, dont really need all the fancy stuff but when I try to use this http://forum.xda-developers.com/showthread.php?t=1746181 I cannot get it to load stable, I get bootloops, non stop force closes.
I did seem to fix the power button issue, took it apart and swapped the button with a damaged i777 I had laying around here and thats working now, so really I just need the stock ICS on it and thats the extent of any tinkering I ever want to do with this phone again.
I picked up a Optimus G today as a replacement, god I hate it, the music sounds like garbage and the camera is worse. Theres about zero cases made for it. I have 13 days now to return it so I'm hoping I can resurrect my GS2.
It says to If flashing this from another base, you should perform a wipe data/factory reset before you flash this package, should I flash the package first? Seems like after that I only have 3E recovery instead of clockwork mod, which I need to flash the kernal, or should I do the kernal first? These things are not really detailed
Click to expand...
Click to collapse
If you wish to be on stock ICS go ahead and reboot into recovery and factory reset. Next turn off the phone and remove the battery. Plug in the usb to the phone while it's connected to your computer while holding both volume buttons. You should be in download mode now once you press the correct volume button. Now you can use Odin/Heimdall to flash Stock ICS. Note this does contain the EMMC Superbrick bug which is why you factory reset prior to flashing it. If you want a custom rom PM and I can tell you
rodimus_prime said:
It says to If flashing this from another base, you should perform a wipe data/factory reset before you flash this package, should I flash the package first? Seems like after that I only have 3E recovery instead of clockwork mod, which I need to flash the kernal, or should I do the kernal first? These things are not really detailed
Click to expand...
Click to collapse
Seems like your answer is in there already. Kernels can be flashed after with Odin. Use a kernel with CWM if you want that.