I am currently trying to flash my vibrant back to stock 2.2. My latest attempt was done using the AIO tools. Every method I have tried has lead to the Vibrant boot screen appearing for a few seconds, and then rebooting. Any suggestions?
Have you tried Odin?
Sent from my SGH-T959 using XDA
whatever5 said:
Have you tried Odin?
Sent from my SGH-T959 using XDA
Click to expand...
Click to collapse
Yes, I have tried Odin with and without AIO tools. In all of the threads I have looked at, the answer seems to be flash back to 2.2 stock, but that is what I am trying to do. Thanks.
Try to boot into recovery and factory reset and see if that breaks the bootloop. If not, see below.
*********
Do you have a nandroid backup of the 2.2 you were on an using? If so, I suggest Odin-ing to stock (2.1), then pull the CWR from my signature put it on your internal card and label it Update.zip. Boot into recovery and hit Reinstall Packages. It will cycle through and you'll have to hit it again. It will cycle through again and your stock (blue) recovery will go to CWR (green). From there you can restore your nandroid backup of the 2.2 you last made (or should have).
You can go to 2.1 using the toolbox, as it has the correct pit/tar files to do so.
Woodrube said:
Try to boot into recovery and factory reset and see if that breaks the bootloop. If not, see below.
*********
Do you have a nandroid backup of the 2.2 you were on an using? If so, I suggest Odin-ing to stock (2.1), then pull the CWR from my signature put it on your internal card and label it Update.zip. Boot into recovery and hit Reinstall Packages. It will cycle through and you'll have to hit it again. It will cycle through again and your stock (blue) recovery will go to CWR (green). From there you can restore your nandroid backup of the 2.2 you last made (or should have).
You can go to 2.1 using the toolbox, as it has the correct pit/tar files to do so.
Click to expand...
Click to collapse
I currently can not get into recovery mode. I am holding the power, vol+, and vol- buttons, inserting the battery and then releasing them when the vibrant screen appears. But it just continues to boot cycle.
I flashed the pit and tar that came with AIO tools. No go. Still just boot cycles. Sorry for being a pain.
I do have a backup, but I am not sure what I can do with right now.
Try turning the phone off, plug in USB hold just volume up and power on the phone..... that should put it into download where you can run Odin and flash back to stock
Sent from my touchpad using XDA
related problem (sort of)
Solved: problem solved. I reflashed CM7 over the bootlooping mess, and it took. Then I was unable to get AIO Vibrant Toolbox to recognize that debugging mode was on, even though it was. So I just copied the files over and went through a massive round of forcing the zip files on again and again. I now have Slim 3.5 on my phone, so I can start playing with it.
*****************************************
I'm an extreme noobie, trying to upgrade my T959 to ICS. I've picked Slim 3.5 (latest release version as of this week) as my first attempt (but really any simple but well-functioning ROM will do for me).
I've rolled back to Eclair (from the official Tmo Froyo upgrade way back when), rooted, and numerous times followed various directions to install the zip for Slim -- sometimes trying CM7 as an intermediate step. The CM7 install failed in the same way as the ICS, as described below.
I've done it with and without AIO Vibrant Toolbox. I've used ClockworkMod Recovery 2.5.1.2 to wipe the data, clear both cache partition and Dalvik cache, and format system. I've popped the zip file in various folders and at toplevel, both external and internal SD.
In all cases, it gets off to a good start, and then I'm left with endless bootlooping: Vibrant logo, Mod logo, a textblock of about 15 lines, repeat. I've always been successful after that in using Odin3 v1.81 to get back to Eclair.
I got sucked into a tech vortex until 4:30 am last night trying again and again, and I'm way way too old for that!
Any thoughts?
Related
I have successfully been able to root and install everything on my Mytouch4G just fine, however, when I tried to install my wife's Vibrant, I am stuck. Here is what I have done:
1) I rooted successfully using superoneclickv1.9.1
2) I installed ROM Manager and also downloaded the Auxora ROM to get ready to install
3) When I flash CWM recovery, it says current and latest recover is 2.5.1.2 (concern here that my mytouch says 3.0.2.4 - do different phones install differently with CWM?). When I look at all CWM recoveries I also notice there is two seemingly more current versions available 2.5.1.3 and 2.5.1.4. I have left it at .2 but wondering why all the versions.
4) When I reboot into recovery, I always get the stock recovery and have not been able to get CWM recovery so I am unable to flash my Auxora ROM. I ran update packages numerous times, and get a signature verification error. I have tried a recovery 3e patch that does not work either. I also gave a try at downloading and SDK, but received temp root errors (phone is already rooted).
After reading many posts, I cannot seem to get a direct answer on what I should do to get CWM to actually boot properly, so I can flash a ROM. Someone said to flash the stock JDK rom, but if I can't boot into recovery, how can I flash anything.
Any help would be greatly appreciated.
You need to get a program for your pc called odin to get back to stock. you can find that and instructions on how to use it if you search for the daily updated vibrant bible its GREAT
http://forum.xda-developers.com/showthread.php?t=849028
going to stock eclair heres a a great guide
So going back to stock eclair will then allow me to install CWM recovery then load roms?
Every once n a while I haft do the install packages thing twice before it gives me clockwork green
. Hope this helps.. o n btw u should look at some of the other roms in the bible before u try auxora
yes u should go back to stock eclair for every rom, in my opinion. Then after that do the 3 button combo and install packages and u will have to do it twice and then the green screen will kick in and ready to rock a new rom.
i hope this helps
What is your current firmware?
I see you posted over in the "NOOB GUIDE" thread, you should really try to root using the method posted there and not any one click root apps.
This should be the root method everyone uses:http://forum.xda-developers.com/showthread.php?t=723479
After root your phone recovery should be blue. Choose "reinstall packages" gives you green recovery(this may need to be repeated multiple times to work possibly including flashing CwMRecovery with ROM manager. I recently did it 5 times b4 i got green recovery)Once you access green recovery chose "apply sdcard:update.zip" go into advanced and choose "reboot recovery" This should give you red recovery. Do a nandroid backup and flash away. Good luck!
Another option you could do is to download SGS kernel flasher from the market and flash a voodoo injected kernel with that app. Then when you boot into recovery you will have red voodoo recovery and you can flash away.
Odin to stock the best way to flash a new rom
Sent from my SGH-T959 using XDA Premium App
jman531 said:
So going back to stock eclair will then allow me to install CWM recovery then load roms?
Click to expand...
Click to collapse
The stock 2.2 that Samsung distributed with their Kies tool has a recovery that checks signatures. Everything earlier does not check signatures. So either use something earlier to get CWM running, or use a ROM that doesn't have the stock 2.2 recovery in the first place, or mod your recovery using the method described in http://forum.xda-developers.com/showthread.php?t=833423
Using Odin to go back to stock Eclair between your flashes of modded roms has the benefit of taking care of this, and also can clear up left over bits and pieces that may interfere with the proper function of your new ROM.
ok, i followed the instructions and am back to eclair, however, whenever I install packages, it just reboots the phone, not even back into stock recovery. I use the 3 key method and get into recovery, run install packages, and the phone just boots back up...its like it isn't running the update.zip file...
UPD: When i load rom manager and try to reboot into recovery, it says the application superuser permissions has stopped unexpectedly and keeps force closing now....titanium backup wont run now either, my root permissions seem whacked after going back to eclair?
UPD2: I followed instructions to unroot and reroot here: http://forum.xda-developers.com/showthread.php?t=739300
It removed superuser, then added it back again, but I still get the unexpected error and it appears my root is not in place. I am back to eclair, and now need a certain way to get my root fixed, so I can try and flash CWM recovery. Without root working, it is not letting me. My wife hates me now for doing this to her phone, so those of you that are married, I would appreciate your assistance to get back on her good side...before Mother's day...please? =)
Ok, thanks for all the help, however, I am really back where I started. I can only get stock recovery, and for the life of me, cannot get CW recovery to load. I used ODIN to go back to eclair on the vibrant, have a good root on the phone now, and no matter how many times i reinstall packages i cannot get clockworkmod recovery to load, ever. Any more thoughts out there?
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
starkiller86 said:
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
Click to expand...
Click to collapse
thanks...It is rooted, but not sure about busybox...the stock recovery is 2e now since I went back to eclair, so not sure i should follow that link as it talks about modifying 3e and making it backwards compatable. I did use that process before I went back to eclair, and it didn't work for me. I have uninstalled rom manager, and reinstalled...and it is different in that it shows a flashed recovery 2.5.1.2, and never asks me for my phone type anymore...it used to ask me and i had to select vibrant....is the recovery supposed to be 2.5.1.2? when I show all recoveries it lists .1, .2, .3, .4 so wondering if I should use .3 or .4...why does it stay at .2?
starkiller86 said:
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
Click to expand...
Click to collapse
OK>>> I GOT IT... Thanks to everyone who helped...Here is what was needed:
1) Install ODIN, install back to eclair
2) uninstall ROM Manager, reinstall
3) I needed to select the 2.5.1.2 recovery from the list again (this was important as it somehow knew of the previous load, but files were missing, or something was just wrong.) It finally loaded properly, and asked for phone type again, so selected vibrant
4) I rebooted into recovery, and instead of install packages, i rebooted once, as starkiller suggested
5) After reboot, went back into recovery from rom manager, and this time installed updates, and it showed that it replaced the recovery with CWM.
6) It rebooted into stock recovery however, so I once again selected install updates, and it went right into CWM recovery, and now I am flashing happy!!!
Thanks again everyone...this was soooooo different than my mytouch4g!
If you have the Kies update of Froyo, the 3e mod will sometimes not work. I've gotten to CWM though , but its best to downgrade then flash a ROM from there.
I just wanted to bump this thread because it really helped me.
I've messed around with numerous android phones, and I've never had thie issues I've had with this phone getting into recovery to flash ROMs
Thank you!
I went from stock Froyo 2.2 to MIUI v3 using the following link.
http://forum.xda-developers.com/showthread.php?t=992251
Now when I startup my phone...
For one, it won't connect me to a network so I can't get phone calls or texts etc.
Also my volume up button is switched with my volume down button.
Trying to make a phone call it says "Mobile network not available".
Does anyone have any information to help me fix this problem? I am stuck.
Yea flash the miui version made for the vibrant in our development section
http://forum.xda-developers.com/showthread.php?t=992302
The one you flashed is for the International galaxy S
bfranklin1986 said:
Yea flash the miui version made for the vibrant in our development section
http://forum.xda-developers.com/showthread.php?t=992302
The one you flashed is for the International galaxy S
Click to expand...
Click to collapse
Ok sooo...
I downloaded
kernel-cm-7-INITIAL-Vibrant-signed.zip
renamed it to update.zip
copied the update.zip along with the MIUI 1.5.20 english pack one to the root of my SD card (internal sd root)
Went into recovery mode, and tried to flash update.zip. It gave me some assert error right away. Now my phone is in a cycle of rebooting where it reboots into the flashing thing, tries to load real quick and then reboots itself.
Any tips? I'm kinda scared.
Odin back to stock and then try again, this guide by s15274n has all the files you need and step by step instructions.
http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
The vibrant files you flashed probably weren't compatible with the I900 kernel/recovery you had flashed.
GTASouthPark said:
Ok sooo...
I downloaded
kernel-cm-7-INITIAL-Vibrant-signed.zip
renamed it to update.zip
copied the update.zip along with the MIUI 1.5.20 english pack one to the root of my SD card (internal sd root)
Went into recovery mode, and tried to flash update.zip. It gave me some assert error right away. Now my phone is in a cycle of rebooting where it reboots into the flashing thing, tries to load real quick and then reboots itself.
Any tips? I'm kinda scared.
Click to expand...
Click to collapse
odin jfd, root, flash recovery then start over with the cm7 kernel then mui.
I'm having a problem following the guide...
Under 2 - Download 3 files..
Mount your phone and move the rom to the internal
AND the UPDATE.ZIP << DOWNLOAD
file if you wiped both internal/external or need to root.
Power down the phone, or pull the battery.
Click to expand...
Click to collapse
I don't know how I can get my phone mounted. Whenever I plug my phone into my computer (with the battery in), it automatically reboots itself and starts the crazy reboot thing. I also can't get back to recovery or downloading mode, it automatically goes back into the reboot thing.
And then in step 3 where it says start Odin, plug in your usb cable. With the battery out of your phone hold both volume buttons for a couple seconds and then plug in your USB cable. That doesn't take me to downloading mode.
EDIT:
Okay I figured out how to get it into downloading mode again. I need to do what it says above by holding the volume buttons with the battery out etc. Then you add the battery.
Hi guys. I got Odin to work. got back to stock.
Then got back into recovery mode to flash the cm7 kernel...
It is the same error as last time. Here's the actual error this time.
-- Installing: /sdcard/update.zip
Finding update package...
Opening update package...
Installing update...
assert failed: is_mounted("/mnt/sdcard")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
GTASouthPark said:
Hi guys. I got Odin to work. got back to stock.
Then got back into recovery mode to flash the cm7 kernel...
It is the same error as last time. Here's the actual error this time.
-- Installing: /sdcard/update.zip
Finding update package...
Opening update package...
Installing update...
assert failed: is_mounted("/mnt/sdcard")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Are you going under install zip from sdcard or just pressing reinstall packages? Instructions say to select reinstall packages after you rename it update.zip
bfranklin1986 said:
Are you going under install zip from sdcard or just pressing reinstall packages? Instructions say to select reinstall packages after you rename it update.zip
Click to expand...
Click to collapse
I boot into recovery mode. It takes me to the stock recovery mode. Then (with the update.zip and the miui zip in the root) I hit reinstall packages. It takes me to the clockwork recovery. Then I do install zip from sdcard. Trying to install the update.zip or the miui at this point gives me an error and then any kind of restarting will throw it into the reboot cycle.
EDIT:
When do I remove the battery? I do reinstall packages, and then after about a second or two it goes to the clockwork recovery, and then I removed the battery like it said. After I booted into recovery again and it took me to the clockwork recovery again, and then I tried to load the miui and again an error flashing.
EDIT 2:
For some reason Odin back to stock changed my phone to 2.1.. I upgraded it to version 2.2.1 (not using keis). I was able to get much further than normal when flashing the miui.zip.
My phone tries to startup, it gets to the Samsung loading image (which says i9000 under the samsung logo).
After that the screen goes (and stays) black. When I hit any of the buttons on the bottom, they glow white so I know that it is turned on.
I can't see anything on the screen, but I must be able to get it into downloading mode because I can get it to say 'added', and get try to start loading things, but then it starts never actually connets, it just hangs. Any ideas? Getting it back to stock right now would be fine so that it is usable again.
EDIT 3:
Ok, now I can see things again. For those who are wondering...
I had downloaded the 'Galaxy One Click Root' thing to try to root my phone before installing miui like it says. Well there's also a unroot button. I clicked that and I got it to go back into this custom recovery image. Once I did that, I navigated around a little and found something that said switch to Downloading mode. I did that, and then was able to use Odin to get back to stock. The screen is working, and so does the radio. It's back to 2.1 though. hmm..
ok so lets try this from the beginning
go ahead and odin to stock jfd (2.1)
now let phone boot as normal
no worries about letting it sit 10 mins or anything.
ok so you have the cm7 initial kernel as an update.zip correct?
3 button into recovery reinstall packages twice that should load you into clockwork
(orange clockwork menu)
1 Mounts and storage menu
Format system/cache/data (do all 3)
+Go Back+
wipe data/factory reset
Pull battery Or just press and hold all vol up + down + power
back in recovery.
install zip from sd Card
Install the Miui ROM reboot system.
lemme know how it goes.
boystuff said:
ok so lets try this from the beginning
go ahead and odin to stock jfd (2.1)
now let phone boot as normal
no worries about letting it sit 10 mins or anything.
ok so you have the cm7 initial kernel as an update.zip correct?
3 button into recovery reinstall packages twice that should load you into clockwork
(orange clockwork menu)
1 Mounts and storage menu
Format system/cache/data (do all 3)
+Go Back+
wipe data/factory reset
Pull battery Or just press and hold all vol up + down + power
back in recovery.
install zip from sd Card
Install the Miui ROM reboot system.
lemme know how it goes.
Click to expand...
Click to collapse
I was back at stock (which I'm not sure is 100% stock because when I turn on my phone, it has a samsung GT-i9000 image on the screen for a second or two before saying vibrant).
I have the update.zip and the miui on my internal sd root.
To get into recovery it's just the 2 button combo (volume - and power) for me.
I only have to hit reinstall packages once, and it takes me into clockwork.
I format the things you said and did the factory reset....
Pulling the battery and then trying to get back into recovery mode put my phone into a reboot cycle. (screen where it looks like after you do wipe data/factory reset) and then I have to odin back to stock.
The three button combo does the same thing. I can't get to the next step.
EDIT:
After the reboot cycle thing. I was able to get back into recovery mode even after it started its reboot cycle deal. Then I was able to install the miui rom. My phone has been on the Samsung Cyanogenmod boot screen for about 5-10 minutes. Not sure if it is trying to boot up miui or just stuck. I'll let it sit for another 15 minutes before thinking its stuck.
EDIT2:
Yep, It's been about half an hour. My phone is stuck on the cyanogenmod boot screen. I can't get it back into recovery or downloading either.
EDIT3:
After some serious playing around. I was able to get it back into recovery mode. Wipe everything, apply the update.zip again... and then was able to get back into downloading mode and reflash it to stock.
Does anyone know how to get to true stock, so I don't have the Galaxy-S GT-i9000 Samsung boot screen. I think that this has to do with why it is failing.
After searching around a lot more...
accidentally flashing an i9000 rom flashed the boot.bin and sbl.bin.
The files to odin back to stock jfd doesn't include the boot.bin or sbl.bin so that's why I get the extra boot screen, and why I 'brick' my phone everytime I try to flash another rom.
Apparently I will brick my phone anytime I try to flash a rom from now on, and that I need to find a boot.bin and sbl.bin combo for the vibrant if I want to be able to flash anything again or get any update past 2.1.
If anybody has any info on how to get this boot.bin and sbl.bin combo could you let me know. I can't find the files anywhere.
why can't i flash rom's no more.
When i flash a new rom(froyo, toxic) i get :
formating update
formating system
formating data
deleting files
copying files
and then instalation complete en then it reboots and this is whithin a minute. And ofcourse the rom do not work correctly so i have to odin back to stock. I wipe and reset to factory, tryed other roms( zen, biwinning) same thing happens. Olso my nandroid backups will not work, they all hang at bali kernel screen(palmtree). So now i am stuck with stock waiting for a solution. thanks
After you ODIN to JFD... can you explain what steps you are taking?
The more detail, the better.
after i odin back to stock, i root the phone, install rom manager, flash clockworkmod recovery. If i do a nandroid restore i get samsung screen followed by bali screen with a female robot voice saying something about paritioning 2 min and counting then it hangs. I also do a wipe before the restore. If i flash a rom in rom manager or in recovery mode i only get wat i mention above, i do not get a loading bar. Thank you for the reply
Don't restore, your nandroid has voodoo enabled, likely causing issues.
Try this:
Odin to jfd (assuming you have no issues, if you do, try my )
download my option b update.zip (from noob guide) - this allows you to avoid ROM Manager/cwr.
Download a good ROM, I would suggest miui revamped or birgertime's cm7 build (my preference)
Download Bali for cm7/miui
Move all 3 to internal sd
Hold in both volumes + power (can be done with phone on after going to jfd and moving files to phone)
Release at vibrant screen
This is stock 2e recovery, reinstall packages (2x maybe)
Should be in cwr now
Flash ROM
Flash Bali
Reboot phone (don't do anything else)
After it boots, wait 10, reboot
Restore ONLY non-system apps, reboot
Enjoy bad ass phone.
Let me know...
Ok I will try this tomorrow, I will let know, thanks again.
For the roms you mention I do not need bootlaoders right.
Correct. That's about the most dangerous thing you can do also.
I flashed ss-6 miui. So far everything works, calling, sms/mms, even gps and wow this is a really nice rom. I am really happy now, stock is so boring and slow. But leaves me wondering why i could not flash froyo roms. Thanks and greetings from a happy island(aruba) i got a lot of custumizing to do so cheers
Glad you are up and running with my guide. You could repeat those steps with froyo roms, no problem
Sent using the XDA app.
Hi everyone,
I have a big problem going to gingerbread.
I'm currently on axura 2.3.12 (froyo 2.2) with stock kernel (the one that came with the rom).
And when i follow the instructions here to upgrade to gingerbread, it doesn't work. I've tried both methods and both doesn't work. The rom manager method doesn't even go into CWM, it just goes into regular recovery.
as for the recovery method, it will install, reboot, and get stuck in a boot loop.
the vibrant logo comes up, then the cyanogenmod, then it shows some installation terminal lines and reboots and starts this process over again.
I'm installing cm7 because I want to upgrade to ICS Passion
Thank You
Also, before this, I went through this whole big process of odin my phone back to jfd stock because of a mistake i made. After going to stock, the 3 button recovery mode method doesn't work anymore. I have to use adb reboot recovery to get into recovery when I was in stock.
Here's how to bypass the boot-looping issue:
N00B_IN_N33D said:
It should start flashing and then enter a bootloop (Vibrant [Splash Screen] > Galaxy S Cyanogen(MOD) > CWR > Repeat). After it does this loop a few times do a battery pull.
Reboot into recovery, which will now be blue (Hold both volume buttons and power. Release power once the Vibrant logo is up).
Go to “install zip from sd card”, select zip from sd...
Click to expand...
Click to collapse
...and then re-flash the rom.
You could just flash lidroid through odin then move on to passion from there its gingerbread and has the gb bootloader included
http://forum.xda-developers.com/showthread.php?t=
Sent from my SGH-T959 using xda premium
Hello wonderful people of the S. Vibrant community. I come to you in order to diagnose and hopefully fix a problem with a friends samsung vibrant.
Basically here's the backstory... He wanted to root his Vibrant (2.2 i believe) to ICS so i sent him the AIO Vibrant toolbox and told him explicitly to read the instructions of the tool and any potentials roms he wants to put on his phone. Lo and behold! I proceed to take a 2 hour map and my phone is bombarded with text messages saying that he 'messed up' and the phone is 'looping' upon boot.
I absolutely do not know what the hell he did and he was intentionally vague on what steps he took and what roms he downloaded etc. He mentioned something about reformatting and downloading a new kernal ...
Anyways. As I'm an owner of a Sprint SGS2; i know that sammys are literally the hardest devices to hard brick so i proceeded to search up these forums and odin a stock tar so i can get this thing booted up.
I followed this guide
http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/ and proceeded to odin back the pit and tar and it was a success.
Then it rebooted and bam still a boot loop. I tried a KA6 tar and still the same results. So I'm stuck here on how to get this phone out of the boot loop and am wondering if you guys can direct me to where I can hopefully fix this problem.
Side note. AIO Vibrant toolbox says the phone has USB Debugging mode off... (SMFH!!!!).
Thanks guys!
Download the bionix V fish man ROM. Its froyo, its good and it has an Odin flashable file. It comes with Bali kernel.
May help you on your way.
http://forum.xda-developers.com/showthread.php?p=21324042
Even though its boot looping, if you can get into recovery, you may be able to flash about any ROM you want. Wipe data/factory reset, clear cache and dalvik, and flash a good solid ROM. I've gotten out of the situation using both of the options I've listed.
May the force be with you.
I'll try and see if this will work and report back.
Well i odin'd the rom according to instructions and it's on the bali screen now for 5 mins... How long does the first boot take
lilotimz said:
Well i odin'd the rom according to instructions and it's on the bali screen now for 5 mins... How long does the first boot take
Click to expand...
Click to collapse
It does take a while. I'd let it go at least another few minutes. Then update me.
---------- Post added at 11:51 PM ---------- Previous post was at 11:46 PM ----------
If your still stuck, pull battery and boot into CWM recovery. Find Voodoo lagfix in the options. Disable it and reboot the phone. That's most likely why its hanging on the first start.
After you get it booted the first time you can go later and reenable voodoo lagfix.
tried using adb reboot recovery cmd and still no dice...
I assume froyo bootloader, hold both volume buttons and power until you see Samsung text and let go. May take a couple tries.
there is no samsung text. It goes white screen then Bali screen and repeat... (boot loop i guess.. again)
Update : Flashed the second odin tar and it seems to be somewhat working now... got into recovery mode and wiped data / cache... rebooting now
Excellent. If that doesn't boot all the way go back to recovery and disable voodoo lagfix.
Well i got into samsung recovery and deleted user data & cache data.
It does indeed go white screen then Bali screen for some reason... same.
Boot loop. No option to disable voodoo lagfix. Recovery is not CWM but samsung recovery... ?!!
lilotimz said:
Well i got into samsung recovery and deleted user data & cache data.
It does indeed go white screen then Bali screen for some reason... same.
Boot loop. No option to disable voodoo lagfix. Recovery is not CWM but samsung recovery... ?!!
Click to expand...
Click to collapse
Hmm. If you have the update.zip on your phone you can click reinstall packages and it will be CWM recovery.
here's what it says...
Update media:
E: Can't mount /dev/block/mmcklk0p1
(no such file or directory)
E: copy_dbdata_media; Can't mount SD card:
your storage not prepared yet.Please use UI menu for format and reboot actions
E:Copy_dbdata_media:format SDCARD:
formatting Sd card:...
E: Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E: copy_dbdata_media: Can't mount SDCARD:
your storage not prepared yet,please use ui menu to format and reboot actions
copy default media content failed
Your internal sd has been destroyed. Your only option is running the entire os off of an external microsd card. http://forum.xda-developers.com/showthread.php?t=1580902
At least it seems like this is the case. I also had this happen to my phone, but eventually it fixed itself after odining about 20times and installing other roms. Good luck. Heres what I did http://forum.xda-developers.com/showthread.php?t=1665123)
Didn't work for some people, so the fact that mine came back might have just been luck.
le sigh...
I guess i'll try some more tomorrow. Guess he did the unthinkable and 99.9% killed a sammy. Poor galaxy s...
I finally managed to follow your instructiosn and i installed CM9 for the first time and it's now boot looping. Your instructions state to reboot into recovery mod and install it again but I for my life cannot discover how to reboot this thing into recovery mod. What are the steps and buttons again if I may ask?
lilotimz said:
I finally managed to follow your instructiosn and i installed CM9 for the first time and it's now boot looping. Your instructions state to reboot into recovery mod and install it again but I for my life cannot discover how to reboot this thing into recovery mod. What are the steps and buttons again if I may ask?
Click to expand...
Click to collapse
Pull the battery and replace it, hold vol up, vol down and power until you see screen come on then release. That should take you to recovery.
sent from the depths of helly bean