Related
So... believe me, I know I'm an idiot for doing this. When trying to install Voodoo for official 2.2.1 I accidentally flashed the 5.5 for GT-I9000 that I forgot to delete when I was first starting to mess around with attempting to install voodoo, before doing much research.
When I tried to reboot it just sat at the I9000 boot screen forever and started to get hot so I pulled the battery.
I rebooted and came to a screen with lots of error messages from CWM on the bottom of the screen and the stock recovery options at the top.
When I try to reboot it just sits at the I9000 boot screen forever.
I tried reflashing 2.2.1 with ODIN as described in this thread http://forum.xda-developers.com/showthread.php?t=881064 That doesn't seem to get very far.
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> All threads complete. (succeed 0 / failed 1)
Did I completely brick my phone or is there some way to get it working again? really desperate here... I don't want to have to go back to my RAZR2 for another year until I can get an upgrade.
Thanks in advance to any golden saint that can help me out!
Never mind, I got ODIN to work (I hastily left out the step loading the tar file) and all seems to be working fine now. Albeit minus a hundred apps or so...
I apologize to anybody who spent time reading this thread.
Fidelis83 said:
Never mind, I got ODIN to work (I hastily left out the step loading the tar file) and all seems to be working fine now. Albeit minus a hundred apps or so...
I apologize to anybody who spent time reading this thread.
Click to expand...
Click to collapse
haha glad you got it working. Hope you had titanium for your apps! If not lesson learned! I thought I trashed my phone a few times thank the Devs for Odin! And boot camp for my mac...haha
droidzach said:
haha glad you got it working. Hope you had titanium for your apps! If not lesson learned! I thought I trashed my phone a few times thank the Devs for Odin! And boot camp for my mac...haha
Click to expand...
Click to collapse
Yep, got Titanium first thing after I rooted.
A million thanks to phidelt82 for the ODIN writeup!
I also flashed Voodoo5.5 to my Epic! Please Help!
I obviously didn't do my homework and flashed the latest voodoo kernel to my epic. I'm running a Rooted Epic w/ Fyoyo and have clockwork mod. So here's how it went: The kernel flashed (said it installed )and phone returtned to clockwork mod. I rebooted and phone stuck in a boot loop just as yours was. I have to pull the battery to shut the phone off. I can get into clockwork mod....where do I go from here? I have the phone backed up with titanium, which is great if I can get it to boot up. Please Help. Thanks.
Cbisk said:
I obviously didn't do my homework and flashed the latest voodoo kernel to my epic. I'm running a Rooted Epic w/ Fyoyo and have clockwork mod. So here's how it went: The kernel flashed (said it installed )and phone returtned to clockwork mod. I rebooted and phone stuck in a boot loop just as yours was. I have to pull the battery to shut the phone off. I can get into clockwork mod....where do I go from here? I have the phone backed up with titanium, which is great if I can get it to boot up. Please Help. Thanks.
Click to expand...
Click to collapse
Flash the correct kernel for your phone, that will fix you up. If you need any more help with that, you should post in the epic forum - since this is the mesmerize forum .
Fidelis83 said:
So... believe me, I know I'm an idiot for doing this. When trying to install Voodoo for official 2.2.1 I accidentally flashed the 5.5 for GT-I9000 that I forgot to delete when I was first starting to mess around with attempting to install voodoo, before doing much research.
When I tried to reboot it just sat at the I9000 boot screen forever and started to get hot so I pulled the battery.
Click to expand...
Click to collapse
You were even then a step ahead of me. Until I read this thread, I didn't even know that was the wrong Voodoo, in spite of it saying GT-I9000, I just figured that was the default behavior of Voodoo. XD I would have gone home tonight, maybe tomorrow, and kept beating my head against it, wondering why it wasn't working. XD
The Newbie Guide from bdemartino doesn't seem to specify---which version of Voodoo did you go with, and where did you get it from? The only Froyo Voodoo kernels I can find on the Project-Voodoo site are the 5.5 ones for the GT-I9000.
If you are on an i500 (fascinate, mesmerize, or showcase) you can flash any of the EC10 based kernels in the fascinate forum here on xda. Just remember that if you are on a touchwiz based rom (stock, PnP, etc) you need to make sure you use a touchwiz compatible kernel. Off you are running AOSP you must use an AOSP compatible kernel.
Sent from my voodoo froyo Mesmerize
Like the OP, I too flashed the wrong Voodoo kernel, the one for the GT-I9000. When I flashed it, I got the robot voice, and then it wouldn't complete the boot process.
So I panicked. I followed the instructions in the post titled "Files to get your Mesmerize back to stock 2.1 and 2.2.1", with the exception of disabling lagfix.
Everything seems to be working okay now, with one exception. I can't get the correct Voodoo lagfix working. I can get the kernel installed, but I never get the robot voice for the conversion.
I have BLN working so it seems like voodoo is installed, but my quadrant scores seem to indicate that it is not.
Help?
If that were me, and I'm certainly no expert, I'd start by taking a Titanium backup of all your apps. Next I'd boot into recovery and disable lagfix if you still can; even if the actual lagfix itself isn't working, just turn the setting off. Then I'd try to flash the stock 2.1 (or 2.2.1 as you prefer) with stock kernel and stock recovery, to treat it like a brand new phone (not sure if you did that or grabbed the stock + custom recovery). Then, just start the customization process over from scratch. Finally, once you've got it tweaked, load up Titanium again and bring over all your apps.
That is IF I understand it all correctly; if I'm telling him wrong, someone please chime in and correct, or confirm. XD (jrusch, I might wait till someone can confirm or deny my instructions, but I figured I'd least give you some food for thought)
I just can't get it to work. I disabled lagfix (even though it didn't seem to be running), and then I used Odin to flash the stock 2.2.1.
I tried a few Voodoo kernels (EC10_ulv_voodoo.zip, TW_kernel-0327-2.zip, and ec10_voodoo.zip) all with the same results. They install, I get the goofy startup screen with the flashing "android" in the middle, but no robot voice announcing the conversion process. After installing the Voodoo kernel I verify it creates the Voodoo folder in the root of the phone's memory and on the sdcard and no disable_lagfix folder exists.
jrusch said:
I just can't get it to work. I disabled lagfix (even though it didn't seem to be running), and then I used Odin to flash the stock 2.2.1.
I tried a few Voodoo kernels (EC10_ulv_voodoo.zip, TW_kernel-0327-2.zip, and ec10_voodoo.zip) all with the same results. They install, I get the goofy startup screen with the flashing "android" in the middle, but no robot voice announcing the conversion process. After installing the Voodoo kernel I verify it creates the Voodoo folder in the root of the phone's memory and on the sdcard and no disable_lagfix folder exists.
Click to expand...
Click to collapse
I'm pretty sure your system is either still in EXT4 or it thinks it is, and that's why disabling voodoo through CWM isn't doing anything for you - what has worked for me in the past is injecting the empty file named "disable-lagfix" into the clockwork folder on your SD Card, then rebooting. It should then disable it, then I would do a clean odin flash to make sure everything is working properly, then you should be able to pick up where you left off (adding voodoo, custom ROM etc.)
This has happened to me in the past when I've forgotten to disable lagfix and tried using odin to go to stock (this returns your kernel to stock and gives you issues because the internal file system is still formatted in EXT4 but the odin flash tries with the stock RFS format, and that's where the problem occurs.)
I used Root Explorer to create a new file named "disable-lagfix" in the clockework folder and rebooted. I then did a clean odin flash, etc.
I still can't get voodoo lagfix to work. When I boot to recovery (CwM Voodoo Lagfix Recovery v2.5.1.x) the voodoo menu shows:
Voodoo lagfix is actually: disabled
next boot: enabled
But at the next boot it doesn't do the conversion.
jrusch said:
I used Root Explorer to create a new file named "disable-lagfix" in the clockework folder and rebooted. I then did a clean odin flash, etc.
I still can't get voodoo lagfix to work. When I boot to recovery (CwM Voodoo Lagfix Recovery v2.5.1.x) the voodoo menu shows:
Voodoo lagfix is actually: disabled
next boot: enabled
But at the next boot it doesn't do the conversion.
Click to expand...
Click to collapse
I don't know if creating the file with root explorer will work, I had to create an empty file in my linux box and renamed to "disable-lagfix" (no quotes) once that file is in the clockwork folder and you reboot you should hear the sound of it being disabled - if you don't hear the voice then something is wrong with the file or where you put it.
right now you're stuck with it enabled, if you have the voodoo control app you can check to see if using the toggle in that app will work, but I'm guessing you're going to have to do it the manual way as stated above.
I still can't get it to work. I created the "disable-lagfix" file on a linux box and then copied the file to the sd card into the clockwork folder. I still can't get lagfix to disable/enable.
When I boot a voodoo_log.txt file is created, does this give any clues:
2011-04-12 13:03:18 model not detected
2011-04-12 13:03:18 manage fat.format in /sbin
2011-04-12 13:03:18 fat.format wrapper installed in /sbin
2011-04-12 13:03:18 fat.format renamed to fat.format.real & symlink created to fat.format_wrapper.sh
2011-04-12 13:03:18 running init !
I was trying to install the Voodoo kernel. I had the stock+froyo one installed just fine using Odin3. Then I went to their main page, and saw the 5.5 version. Titled Voodoo lagfix for Froyo stable. I used Odin to install it from the Download Mode. everything went fine till the voice said something about not enough space on the partition.
Then the T-Mobile pink screen appears, then the Samsung Vibrant S screen, then it goes black. Nothing happens after that except the bottom lights come on if I touch them. Odin3 still sees my phone as plugged in. I have a really hard time trying to get into the Recovery screen, but when I do, I have no idea what to do once I'm there.
I've tried using Odin3+Download Mode to reinstall the stock+voodoo-froyo-t959-UVKA6.tar which worked fine the first time, but I can never get back to the main home screen.
Any advice would be much appreciated, I'll be online for the next few hours refreshing this page, so my responses should be fairly quick. Thank you in advance.
Update: I tried searching for solutions, came across a post in the samsungvibrant.c o m forums with a youtube video.
I followed the instructions, everything worked as intended, until after the S screen, I just got a black screen. Never went to the home screen. This where I am currently at.
rtekbillabong said:
I was trying to install the Voodoo kernel. I had the stock+froyo one installed just fine using Odin3. Then I went to their main page, and saw the 5.5 version. Titled Voodoo lagfix for Froyo stable. I used Odin to install it from the Download Mode. everything went fine till the voice said something about not enough space on the partition.
Then the T-Mobile pink screen appears, then the Samsung Vibrant S screen, then it goes black. Nothing happens after that except the bottom lights come on if I touch them. Odin3 still sees my phone as plugged in. I have a really hard time trying to get into the Recovery screen, but when I do, I have no idea what to do once I'm there.
I've tried using Odin3+Download Mode to reinstall the stock+voodoo-froyo-t959-UVKA6.tar which worked fine the first time, but I can never get back to the main home screen.
Any advice would be much appreciated, I'll be online for the next few hours refreshing this page, so my responses should be fairly quick. Thank you in advance.
Update: I tried searching for solutions, came across a post in the samsungvibrant.c o m forums with a youtube video.
I followed the instructions, everything worked as intended, until after the S screen, I just got a black screen. Never went to the home screen. This where I am currently at.
Click to expand...
Click to collapse
WTF? Do you even have a Mes/Showcase?
Sounds like someone didn't check which forum they were in after they Googled.
You probably need to look around in this forum instead.
To all i500 users.... don't go to the project voodoo site looking for voodoo kernels. Those are generic or made just for OTHER phones. Any and all voodoo kernels you flash should be found either in this forum or the fascinate forum. This goes back to the old DO NOT FLASH PACKAGES FROM OTHER PHONES…
just trying to be helpful.
Sent from my SCH-I500 using XDA App
I have a question regarding Voodoo flashing methods, specifically relating to Odin & CWM. The Voodoo website (which contains the INCORRECT kernels for our I500s, I DID gather that already ) recommends placing the file directly onto the SD card, renaming it "update.zip" and using stock recovery to flash it. I have noticed that this sentiment is not reflected here are all - everyone seems to recommend using CWM Recovery and/or flashing everything with Odin. What gives?
If someone with a stock EC10 ROM just wanted the benefits of the Voodoo conversion, and isn't really interested in flashing a new ROM, is it really necessary to install CWM and Odin, or will the stock stuff work? From what I've gathered, this is all the OP was really trying to do from the start.
BTW, yeah, it's my first post, and yes I've been reading a lot, but definitely not nearly enough. I'm very impressed with the level of assistance forum members are willing to provide, but I, like many others, want to make sure I have it 100% correct before I turn my phone into a very fancy, very worthless piece of silicon, glass and plastic. Thanks, everybody!
Background. Was using 2.2 for the longest time, loved Firefly. Went ahead and bit the bullet and decided to go to 2.3 and use Gingerbread. Solid week of great success. However I started notcing my antenna saying no signal. Several Reboots and still nothing worked. Decided I would One-Click Back to 2.1 and start fresh. Well I never had issues with Odin 1 Click before, but now I get in a boot loop (ATT SPlash Screen) I have noticed when its unloading the package after , the last thing i see is CSC and that it boots into the loop. Would love to get my phone back to stock so i can see if its a hardware or software issue with my antenna. I have looked at this link, http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36 but was afraid I possibly might still have GB bootloaders on my phone. I would think not if Odin finished, but I just want to double check with the community so I dont brick.
Thanks guys.
Can you get into DL mode? IF so, i would try and Odin again. ALthough I looked at the link in your OP, unless your heart is set on 2.1JH7, i would use the Odin3 one click downloader. That will restore your phone to 2.1JF6 as well as flash the correct bootloaders. I have gone back and forth from continuum to cm7 a few times now using that method.
Thanks for the quick reply. however this is the 3rd time trying Odin-1 Click tonight and I still end up in a boot loop. I have redownloaded the file just to make sure I didnt have a corrupt one. I just want a stock system and see if the constant antenna issues continue. (Trust me Ive tried different modems and all those possibilities.) Is it safe with that link? I noticed when i do Odin they flash a sbin and bootloader. I am assuming that puts it back on 2.1
which Odin are you using? Are you using the one click program that gives you stock firmware... JF6 firmware?
It is here:
http://www.megaupload.com/?d=SBSMALFJ
Yup thats what I have. It looks like it doesn't load the android system. Soon as it says installing Multi-CSC its done and rebooting. It would seem like its not unpacking the files. I have no status bar at the bottom. I have no idea why its doing this. Here is the crazy part. If i go back to the ginberbread stock, its not a problem to get to boot.
while I'm no expert.. seems like a bootloader thing. Try downloading it again from the link i put up and see if it was maybe a corrupted download.
The bootloaders are the first thing flashed in odin. It stopped after that then you have stock bootloaders. Also if all you see is the white AT&T screen and then it reboots, that indicates stock bootloaders as well. The gb bootloaders have a black galaxy s I9000 screen as the param.lfs image.
I would bet money you have stock bootloaders, use that link you posted that work be perfect. If you go back to gingerbread and want to return to stock bootloaders you'll have to use one click again even though you got a problem from it this time, if you get the same problem you know this worked to fix it.
And lastly usually problems with cell signal are modem related ... Which one were you using, did you even try another one? That would've been my first move instead of going all the way back to stock.
Hey studacris,
I have been using Mosaic (Love the work you guys do over there). I did try and use the other method to get back to Stock Last night and it did the same thing. Just a bootloop. If its plugged into the USB cable it goes directly to the Battery Symbol, if its not the Att 3G bars loop. I can flash to Gingerbread stock and then apply Other Roms. I tried GR-2 and Mosaic again, but still nothing with the signals. I just dont like the fact I cant get back to Stock with those 2 different methods. What I think is odd is when I load Gingerbread, it seems like items are being unpacked and loaded. When i try to go to Stock, everything happens super quick, making me believe nothing ever gets installed on the Internal Card during the unpacking sequence. I am no pro, but thats just something i noticed. Here was my original post on the Mosaic board. http://forum.xda-developers.com/showthread.php?p=14043766&highlight=Rizz67#post14043766
I don't know what to do next, and I need my phone. I can answer any questions, but I wouldn't know what to start with. Can someone help??
Quick questions to answer:
1. What Rom were you on prior to flashing?
2. What Rom were you flashing to?
3. What do you see on your screen?
4. Do button presses give any reaction?
1. http://forum.xda-developers.com/showthread.php?t=1136128 v5.0, it's Gingerbread.
2. I was flashing to CM7, but it didn't flash, so I did what was probably a mistake and went straight for http://forum.xda-developers.com/showthread.php?t=1625619&page=1.
3. I see "DevilKernel" Samsung Galaxy S.
4. If I hold down the volume and power buttons, the DevilKernal boot screen will flash. If I keep the power button held down it resets, if I don't it just flashes and nothing else.
By the way, thanks.
Ok, here's what happened:
The first bootloop you were seeing with CM7 is actually a normal occurrence. You usually have to flash CM-based roms twice to get them to "take" (the first time sets up MTD over BML, the second time installs the rom).
What you're seeing now is the devil kernel trying to load up the CM9-based system, but not having all the parts in place.
Thankfully, you're not in that bad of a place. The easiest thing to do right now is to grab an Odin- or Heimdall-based one click Gingerbread stock package without bootloaders. There's a sticky in the Development section that has them, or you can grab the one in my signature.
Flash the one-click, go to recovery, and flash either CM7 twice or TWICS twice.
That should fix you up.
When I tried flashing the CM7, it said it failed. I'm not sure what went wrong. The TWICS I planned on flashing twice, but it got stuck.
Hard to say - it could be something as simple as a bad download of the flash file.
But you think if I Odin it and try TWICS again it'll work?
It should. Doing the Odin one-click will reset everything back to a factory state, which should remove all the obstacles that would normally stand in the way of a successful installation.
Hey man, for that ROM, this theme will work, right?
http://forum.xda-developers.com/showthread.php?t=1095911
I don't know anything about themes. Or this, apparently. I also got into Recovery and installed it twice, I don't really know what's going on.
So you're now fully set up with TWICS, or you're saying that it's still misbehaving?
Also, that theme should work - I had a CM7 theme that I was able to use with a CM9 rom's theme chooser. Wasn't 100%, but it generally worked.
I'm not sure WHAT is going on. The ROM seems to be working fine, I am reinstalling my apps from Titanium Backup and a "Low on space" popup is here, but that makes no sense since it's the same phone, it's a smaller ROM, and a 32gig SD Card. I also just got a text message that was "rejected due to low space".
What is going on??
It seems my phone always is unable to continue once Super Monkey Ball 2 tries to be backed up.
Look around in the cm7 thread for the dbdata full issue. I think there were some suggestions for how to deal with it in there.
I was running the latest tweaked ROM yesterday when it rebooted itself into a boot loop. Iets stuck at "Samsung"
I attempted to restore using Odin following the instructions in the how to fix your phone thread. Though i've been successful with that in the past, this time it didn't fix the phone. Its still stuck on Samsung, but will randomly display the stock boot ani with sound, or even get to the lock screen, but then immediately go back to displaying Samsung.
Any ideas would be greatly appreciated, and yes, i've followed all instructions correctly with wipes and loading things in Odin, etc.
Thanks!
Hmm... was there anything going on at the time of reboot? Very curious.
Beyond that - assuming all went as it should with ODIN, if you are still having issues then the problem is a bit beyond the rom. It seems a scapegoat but perhaps a hardware error is underlying things...?
Anyhoo - what file (or files) have you tried to ODIN? There are a few to choose from, and they all can be found here (just be sure to only DL and use the charge-specific ones of course). I would try each one and hope at some point something sticks to where the phone is usable again. Sorry for the troubles!
Thanks for your reply! Phone was just sitting on my desk, I was text messaging...it may have been plugged into a non Samsung charger. I doubt its the fault of your ROM tho, as it had been running great since I installed 2.1 a few weeks ago. Its always run hot so that might have just caught up with it.
I'll try all those files this time on fresh downloads, might have been something corrupted.
thanks again!
UPDATE: Successfully loaded ED1 on, and it boots. I can unlock the phone, begin the setup process, but then it reboots. I'm so confused...
Find the most current OTA file and flash it instead of working your way all the way from Froyo to Gingerbread.
Sent from my SCH-I510 using xda premium
I had something similar happen to me just a week ago. I was on stock debloated deodexed and odined to tweeked and it bootlooped, Odin said successful but nothing was happening just Samsung logo. I knew there was no problem with tweeked cause I used the same file b4 and it worked fine. Tried to Odin back to stock ep4 same Samsung logo Odin still said it was successful. So I changed cable and made shure I was not moving phone or cable while it was doing its thing. It worked. Then updated to fp1, cwm superuser then Odin to tweeked. Everything ok. I figured the only problem of my was that the cable was a bit loose when I plugged it in the phone, the connections in the phone I guess were not getting the full contact as they should have. So try making shure you connect/plug in cable all the way and don't touch it while Odin is doing its job. You might also need to flash the stock ep4 file. Sorry could not help more. This worked for me, now on tweeked 2.2 n no problems.
Sent from my SCH-I510 using xda app-developers app
A few more things you should know before I get into it. First off, this is my mother's phone, and about two days ago, she went to unplug and use her SGS4G after it had been charging overnight, and it wouldn't respond to the Power/Lock Button (It appeared simply stuck). So, naturally, she did a battery pull on it, and tried to turn it back on. After she hit the Power Button though, the Splash came up like it normally does, except instead of progressing with booting, the screen went black for a second and then went back to the Splash and it did/does this indefinitely (An obvious sign of a Bootloop).
Now. What doesn't make sense to me is that this was running the Stock ROM (I don't know if it was Froyo or Gingerbread), yet this still happened. I haven't tampered with the Phone at all, and my mother isn't too fond of the idea of Rooting, so unless the previous owner (Yes, it is a used phone) tampered with it and then restored it to Stock, then I have no idea.
Things I have tried:
Heimdall One-Click For Dummies (With and Without flashing Bootloaders)
Juls317's Noob Guide's "Potential Problems" section (With both Heimdall and ODIN)
A few Kernels (bhundven's Kernel, drhonk's KG4 Kernel)
sygee's ODIN/Heimdall Flashable ROM
hailthetheif's Step by Step Rooting Thread
Also, after I flash anything, whether it be with ODIN or Hiemdall Suite, or Hiemdall's One-Click, if I leave the phone plugged into the computer afterward, it will go to the Splash Screen and then to the Battery Screen (Which doesn't work, it just freezes with the Loading Wheel) and it'll Bootloop with the Battery Screen. If I unplug it after Flashing, it goes back to the classic Splash Bootloop that has been happening since Day 1. It doesn't even get past the Kernel.
I know that at least the Kernel and the Bootloaders can be Flashed however, by how they act on the Device. For example, if I flash certain Gingerbread Bootloaders, I can only get into Download Mode with PWR + VOL-, whereas on the Froyo Bootloader (Includes Stock), you use VOL+ + VOL-. With the Kernel, for example, if I flash a TeamAcid Kernel, their Logo comes up on the Splash Screen, but it still does the Splash Bootloop no matter what.
One final thing, if I flash a Kernel/ROM that includes a Recovery Mode, I can't access it at all (PWR + VOL+). I couldn't/can't access the Stock Recovery at all either.
One final thing, if I flash a Kernel/ROM that includes a Recovery Mode, I can't access it at all (PWR + VOL+). I couldn't/can't access the Stock Recovery at all either.
Pull the battery, hold power& both volumes, drop the battery back in. Should bring you to recovery (gb, not sure, can't remember froyo same or not). Wipe data & cache etc.
On the heimdell, awesome threads that you quoted. Follow directions and it should get you there. Kj6.. you may have to flash it twice to get the bootloaders for gb(it's setup that way so you can't fubar it without trying really hard). You would have to check the load boot loader box on second flash.
I just had this same exact issue. No matter what I flashed, it wouldn't work. Just kept with the boot loop. Now the difference with my issue was, I was still able to get into CWM and/or Download mode. (I was running custom rom). Heimdall wouldn't work for me because it was a driver issue. Odin, well, all the links I found for Odin were dead..
Anyway, when you're working with Heimdall, does it recognize your phone and flash? I had to flash it over twice for it to get to work. It is possible she was on Froyo and you're trying to flash it over with a GB stock rom could be causing an issue. Someone correct me if I'm wrong.
I'd say try sourcing a Heimdall to Stock Froyo ROM and see what happens from there.
This thread helped me out the most:
http://forum.xda-developers.com/showthread.php?t=2042927&highlight=frozen+at+boot
LiangChi said:
I just had this same exact issue. No matter what I flashed, it wouldn't work. Just kept with the boot loop. Now the difference with my issue was, I was still able to get into CWM and/or Download mode. (I was running custom rom). Heimdall wouldn't work for me because it was a driver issue. Odin, well, all the links I found for Odin were dead..
Anyway, when you're working with Heimdall, does it recognize your phone and flash? I had to flash it over twice for it to get to work. It is possible she was on Froyo and you're trying to flash it over with a GB stock rom could be causing an issue. Someone correct me if I'm wrong.
I'd say try sourcing a Heimdall to Stock Froyo ROM and see what happens from there.
This thread helped me out the most:
http://forum.xda-developers.com/showthread.php?t=2042927&highlight=frozen+at+boot
Click to expand...
Click to collapse
It does recognize the phone, and it does Flash (As far as I know). I used Zadig, so there shouldn't be an Driver problems. I flashed it several times with a lot of different things, however, I just now flashed it twice with the Heimdall One-Click again to see if that made any difference. It did not. I'm still stuck in that Splash Bootloop.
Also, what did you mean by, "I'd say try sourcing a Heimdall to Stock Froyo ROM and see what happens from there."? I haven't ever seen that suggested anywhere, and I have no idea where I would find a Stock Froyo ROM that is flashable via Heimdall.
Able to get in to recovery and wipe? Wipe data & caches. Got cwm? Which one click? Eilleo(sorry for the spelling) put out a one click that was to be used as stepping stone to ics only.
WinterPhoenix96 said:
It does recognize the phone, and it does Flash (As far as I know). I used Zadig, so there shouldn't be an Driver problems. I flashed it several times with a lot of different things, however, I just now flashed it twice with the Heimdall One-Click again to see if that made any difference. It did not. I'm still stuck in that Splash Bootloop.
Also, what did you mean by, "I'd say try sourcing a Heimdall to Stock Froyo ROM and see what happens from there."? I haven't ever seen that suggested anywhere, and I have no idea where I would find a Stock Froyo ROM that is flashable via Heimdall.
Click to expand...
Click to collapse
I'm honestly not to sure if a Froyo ROM for Heimdall exists. I do believe seeing one for Odin, though. Not sure if that link is still alive. I'll see if I can find it again.
We do have a Froyo One-Click but if KJ6 One-Click is not working for him I do not know why you think the Froyo One-Click will.
lumin30 said:
We do have a Froyo One-Click but if KJ6 One-Click is not working for him I do not know why you think the Froyo One-Click will.
Click to expand...
Click to collapse
I figured if the phone was still running on the Stock Froyo when this happened, that it may work as opposed to forcing the phone to accept a new ROM while it's still clashing with itself.
It's worth a shot at this point.
Stuck on Froyo
LiangChi said:
I figured if the phone was still running on the Stock Froyo when this happened, that it may work as opposed to forcing the phone to accept a new ROM while it's still clashing with itself.
It's worth a shot at this point.
Click to expand...
Click to collapse
I hate to hijack this thread but it describes my current situation and symptoms perfectly and I never saw a conclusion / fix.....
I just got a used phone from ebay (verified SGH-T959V in battery compartment) and have run into the same exact problems described in the start of this posting. Phone was running Froyo and I attempted to upgrade to Gingerbread with Heimdall One-Clicks. I was actually successful at one point but then it crashed when I tried to install boot loaders to get rid of rainbow screen at startup.
Now all I ever get is a splash screen bootloop whenever I try any of the Heimdall One-Click gingerbread variants. I have also tried Odin and the Gremlin remover with same results of splash screen bootloop (Linda always completes). I was however able to access the new kernel CWM recovery and try to flash other gingerbread ROMs - splash screen bootloops on all attempts.
So I gave up on Gingerbread and tried using CWM recovery from gingerbread ROMS to install CM9 / CM10 / Slim Bean. I was able to upgrade almost perfectly but had same problem for each one of these. Not the bootloop thankfully but instead the headphone speaker (if that is the right description) doesn't work. No sound for phone touchpad, screen selections, and when receiving a phone call (have to switch to speaker phone as back/big speaker works or plugin headset to hear whoever was calling).
All of the other features were great but I really needed to be able to use my phone as a phone! The Heimdall One-Click worked to return me to Gingerbread with same problem of splash screen bootloop (gets to pink welcome letters every once in a while). Then I used the Heimdall One-Click for Froyo (as suggested by LiangChi) and got a perfectly working version of Froyo.
Used Froyo CWM recovery to switch to ICBINB ROM which works fairly decently.... Am I doomed to stay at Froyo though? I tried to follow all of the guides to a T but not sure what I might be doing wrong or if I might have purchased a damaged phone - can't recall ever testing camera and it still doesn't work on current stable Froyo. At various points I tried different cables, SD cards, USB ports, removing/reinstalling drivers, etc... Even tried Kies when I got back to stock Froyo to upgrade - went to Splash Screen Bootloop!
You have so much info here... let's see what we can figure out.
grovernyc said:
I hate to hijack this thread but it describes my current situation and symptoms perfectly and I never saw a conclusion / fix.....
I just got a used phone from ebay (verified SGH-T959V in battery compartment) and have run into the same exact problems described in the start of this posting. Phone was running Froyo and I attempted to upgrade to Gingerbread with Heimdall One-Clicks. I was actually successful at one point but then it crashed when I tried to install boot loaders to get rid of rainbow screen at startup.
Now all I ever get is a splash screen bootloop whenever I try any of the Heimdall One-Click gingerbread variants. I have also tried Odin and the Gremlin remover with same results of splash screen bootloop (Linda always completes). I was however able to access the new kernel CWM recovery and try to flash other gingerbread ROMs - splash screen bootloops on all attempts.
Ok... when you flash the "stock" rom... have you tried to wipe cache, data etc???
Are you letting it boot up before appling any of the kernels??
So I gave up on Gingerbread and tried using CWM recovery from gingerbread ROMS to install CM9 / CM10 / Slim Bean. I was able to upgrade almost perfectly but had same problem for each one of these. Not the bootloop thankfully but instead the headphone speaker (if that is the right description) doesn't work. No sound for phone touchpad, screen selections, and when receiving a phone call (have to switch to speaker phone as back/big speaker works or plugin headset to hear whoever was calling).
All of the other features were great but I really needed to be able to use my phone as a phone! The Heimdall One-Click worked to return me to Gingerbread with same problem of splash screen bootloop (gets to pink welcome letters every once in a while). Then I used the Heimdall One-Click for Froyo (as suggested by LiangChi) and got a perfectly working version of Froyo.
Try wiping data and such, still bootlooping??
Used Froyo CWM recovery to switch to ICBINB ROM which works fairly decently.... Am I doomed to stay at Froyo though? I tried to follow all of the guides to a T but not sure what I might be doing wrong or if I might have purchased a damaged phone - can't recall ever testing camera and it still doesn't work on current stable Froyo. At various points I tried different cables, SD cards, USB ports, removing/reinstalling drivers, etc... Even tried Kies when I got back to stock Froyo to upgrade - went to Splash Screen Bootloop!
Click to expand...
Click to collapse
nope, it sounds like dirty flashes to me...
I would start with entering cwm and disabling lagfix & wiping data & caches.... linda needs to do her thing after the first boot up...
Then, I would reflash the germlin remover, If I remember correctly, you will have to do this twice (second time will allow you to check the add bootloaders)...
After the phone hits the think-pink, then you can battery dump, reenter download and flash the kernel.
Dirty Flashing
Champ - I think you might be on to something...haven't read about dirty flashing but it sounds right. I have been wiping data and caches (even tired reformatting system with a few roms). I do remember running into problems trying to following a few instructions sets that asked to disable the voodoo lagfix - hit option it just doesn't disable. After hitting disable see below Voodoo lagfix is actually: enabled next boot: disabled but even if I reboot back to CWM it is still enabled.
I might try the Odin Gremlin remover again. I was just getting frustrated after several days of failed upgrades. Second opinion on if it might be hardware/memory vs user error. I really didn't understand why even Kies (which everyone disparages) upgrade from stock Froyo also caused same loop.
champ1919 said:
You have so much info here... let's see what we can figure out.
nope, it sounds like dirty flashes to me...
I would start with entering cwm and disabling lagfix & wiping data & caches.... linda needs to do her thing after the first boot up...
Then, I would reflash the germlin remover, If I remember correctly, you will have to do this twice (second time will allow you to check the add bootloaders)...
After the phone hits the think-pink, then you can battery dump, reenter download and flash the kernel.
Click to expand...
Click to collapse
Retry the gremlim remover. Redownload it incase of a bad download.
Lumin30 has a good guide in his signature for the heimdall one clicks.
I use Odin, I have used his one clicks without problems though.
http://forum.xda-developers.com/showthread.php?t=1470716
Sent from my SGH-T959V using xda app-developers app