Same old story: I'm new at this, I screwed something up, my phone is unusable and I'd love to undo whatever mistake I've made. I searched all the forums, I have about 50 tabs open in Chrome, and I'm more confused than ever. So I figured I'd post my question here directly. Thanks for any help ahead of time.
My Vibrant is stuck in a system recovery loop. Here's how I got here:
I had upgraded my Vibrant to 2.2 using the official update via Samsung Kies.
Then:
1. I rooted the phone using SuperOneClick
2. I installed Clockworkmod Recovery (using this walkthrough)
3. I flashed the Voodoo Lagfix.
The lagfix seemed to install fine (took a few minutes, apparently was successful), but when the phone was restarted, it booted into Android system recovery <2e>. And I can't get out of it. I'm given these options:
reboot system now
reinstall packages
delete all user data
delete cache data
In addition, I have the following text in yellow:
-- Movi_check Start..!!
checksum confirmation need_checksum[0]
Not need checksum confirmation
-- Movi_check already executed!!...
-- movi_checking done!...
# MANUAL MODE #
-- Appling Muti-CSC...
Installing Muti-CSC
If I select "reboot system now", I get to the same screen.
If I select "reinstall packages", I get to the same screen.
Would appreciate any help. Thank you!
Taking a shot in the blue but have you tried to click reinstall packages then when it brings you to the screen click reinstall packages again. Then this sshould get you into clockwork mod recovery which will give you a choice to reboot now and then it should worK. If it doesnt then do the same thing tthen once in cwr try clicking clear cache..if none oof these work a fresh odin usually does the trick =]
Sent from my SGH-T959 using XDA App
Thanks for your reply. Yes, I've tried doing "reinstall packages" multiple times and it always brings me back to the same screen. Same with clearing cache.
Re: "a fresh Odin" - I'm reading up about this now. I've figured out how to put my phone into Download mode. Is there a stock set of files for Odin that I should be using?
goodcough said:
Thanks for your reply. Yes, I've tried doing "reinstall packages" multiple times and it always brings me back to the same screen. Same with clearing cache.
Re: "a fresh Odin" - I'm reading up about this now. I've figured out how to put my phone into Download mode. Is there a stock set of files for Odin that I should be using?
Click to expand...
Click to collapse
Look at this thread and use the files in here to take you back to stock via Odin....then start over with your rooting, flashing, etc..
http://forum.xda-developers.com/showthread.php?t=848737
I followed the procedures in
http://forum.xda-developers.com/showthread.php?t=848737
The Odin process kept getting stuck on modem.bin... After trying a few times, I'm now unable to trigger download mode. Nor does the [ Phone < ! > Computer ] screen come up. It's all black - I fear the worst. Is there anything else I can try?
I don't want to say the B-word yet, but I don't know what else I can do.
Related
OK. I'll give you two dollars if you can help .
Problem: Phone hangs on blank screen after starting boot through galaxyS screen. Also, when flashing stock .pit and .tar through Odin, on phone is reads "data wipe failed.", then proceeds to the hanging black screen.
Assesment: Realized I tried this (on a friend's phone) that had Voodoo still on. I figured this was the cause. I CAN boot into recovery/download/recognize in adb and odin. I pushed the disable voodoo zip into the voodoo folder from ADB shell, rebooted, re-flashed stock from odin, same problem. I have full access to the phone through adb, and can reach all recovery/download menus, but after I flash this everytime it comes to the "data wipe failed.".
Solution(s): 1.Try to reboot the bionix191_JACS_OCUV_VOODOO.zip via clockwork, encounters a
" E: Failure at line80:
copy_dir PACKAGE:data DATA:
Installation aborted. "
2.Try to reflash T959UVJFD stock, flashes completely in Odin, then on phone reads "data wipe failed." and hangs on black screen after boot-up galaxyS screen.
Any help would be great, because I have to let my friend use my phone until I fix his.
email me [email protected]
There is a Eugene Rom for Froyo that does not brick, did you try that rom?
Else try Nandroid stock rom image and restore the phone.
Solution?
OP,
Have you come up with a solution? I have the exact same issue.
Same "data wipe failed," and no (0.0b) application storage.
chichu_9 said:
There is a Eugene Rom for Froyo that does not brick, did you try that rom?
Else try Nandroid stock rom image and restore the phone.
Click to expand...
Click to collapse
After that Odin back to stock and you can flash anything you want.
First:
Flash the ODIN Rom found here:
http://forum.xda-developers.com/showthread.php?t=740558
(Leave re-partition UN-CHECKED)
Note: This will probably finish and show an error on your phone, that is okay!
Second:
Flash the ODIN Rom found here:
http://forum.xda-developers.com/showthread.php?t=734475
(This time, check re-partition)
Voila. You are no longer bricked and are back to stock JFD.
Okay here was my issue, I know I'm seeing more people trying to get this fixed but there isn't much information on this and it seems to be trial and error for majority of the people.
-- Movi_check Start..!!
checksum confirmation need_checksum[1301305579]
MBR_ChkSum in header : 4.1
MBR checksum : EC0063A432AFDBA2B104C3F0DF52FE3D
MRB Checksum Error
Movinand Checksum Confirmation Fail
-- movi_checking done!...
# MANUAL MODE #
-- Appling Muti-CSC...
Installing Muti-CSC
This error has to do with clockwork recovery from flashing cwr and getting an error. My error was when I flashed CWR and replaced the sd card! This cause me to boot into boot loops. Searching around on this thread and there are a few people with this issue and haven't found a solution.
This is what I did to be able to get past the mbr check sum error. Note I couldn't boot into stock rom with this error nor could I boot any rom besides the following!
Eugene no brick froyo...located on eb productions forum
I updated to Eugene no brick froyo, using Odin 1.7,
pit=512
Pda= eugene
Ran the process, and now you have a semi working rom, note I was unable to install anything or download on this rom. This is where I placed the CWR as and update zip (http://forum.xda-developers.com/showthread.php?t=734164)
Reboot into stock recovery, REINSTALL package, this will locate the CWR "update.zip" was the name I used. It rebooted into stock recovery once again, and then reboot again into Clockwork Recovery. You now have CWR working,
Use the voodoo lag fix
1. CWM voodoo lagfix (http://project-voodoo.org/), placed on sd card and flashed through CWR
2. reboot
3. disable voodoo (disable it you just make a directory called "disable lagfix" wihout the quotes in the Voodoo directory on the SD)
4. Oden "no brick froyo" w/ repariton checked, now I had a working rom where I could down load items from the market.
I downloaded Rom manager, although probably not needed. I flashed the recovery in rom manager, just to see if it would work. It did work and now I can go from rom to rom, however I still have the mbr check sum error when I reboot into recovery.
Hope this helps out with this error, any suggestions in cleaning this post up let me know. THANKS TO ALL
osugsxr said:
Okay here was my issue, I know I'm seeing more people trying to get this fixed but there isn't much information on this and it seems to be trial and error for majority of the people.
-- Movi_check Start..!!
checksum confirmation need_checksum[1301305579]
MBR_ChkSum in header : 4.1
MBR checksum : EC0063A432AFDBA2B104C3F0DF52FE3D
MRB Checksum Error
Movinand Checksum Confirmation Fail
-- movi_checking done!...
# MANUAL MODE #
-- Appling Muti-CSC...
Installing Muti-CSC
This error has to do with clockwork recovery from flashing cwr and getting an error. My error was when I flashed CWR and replaced the sd card! This cause me to boot into boot loops. Searching around on this thread and there are a few people with this issue and haven't found a solution.
This is what I did to be able to get past the mbr check sum error. Note I couldn't boot into stock rom with this error nor could I boot any rom besides the following!
Eugene no brick froyo...located on eb productions forum
I updated to Eugene no brick froyo, using Odin 1.7,
pit=512
Pda= eugene
Ran the process, and now you have a semi working rom, note I was unable to install anything or download on this rom. This is where I placed the CWR as and update zip (http://forum.xda-developers.com/showthread.php?t=734164)
Reboot into stock recovery, REINSTALL package, this will locate the CWR "update.zip" was the name I used. It rebooted into stock recovery once again, and then reboot again into Clockwork Recovery. You now have CWR working,
Use the voodoo lag fix
1. CWM voodoo lagfix (http://project-voodoo.org/), placed on sd card and flashed through CWR
2. reboot
3. disable voodoo (disable it you just make a directory called "disable lagfix" wihout the quotes in the Voodoo directory on the SD)
4. Oden "no brick froyo" w/ repariton checked, now I had a working rom where I could down load items from the market.
I downloaded Rom manager, although probably not needed. I flashed the recovery in rom manager, just to see if it would work. It did work and now I can go from rom to rom, however I still have the mbr check sum error when I reboot into recovery.
Hope this helps out with this error, any suggestions in cleaning this post up let me know. THANKS TO ALL
Click to expand...
Click to collapse
I think supercurio fixed that with his voodoo 5.0.4 release.
good to know, just a helpful fix to my issue which people still have.
Thanks to this post, it helped took me off the loop of not able to restore JFD over it or truly get back to stock. I think I got it all restored as I can now install app and stuff.
It all happened when I took wrong advice or misunderstood and did "Wipe Partition Cache" in CWR. problems...after problems...after problems...
Phone Symptoms: Vibrant S splash screen and noisy bootup sound were there, but it changed to black screen with all four buttons at bottom lit up for a little while then disappeared to all pitch black on phone screen and buttons. I guess you can call it black soft brick? When you odin back using Eugene_2E_JK2_Froyo.tar.md5, it gets your Vibrant in semi-bootable state. If you odin back JFD tar, it brings back to original problem. In the recovery screen you also see "MBR Checksum Error, Movinand Checksum Confirmation Fail"...and when you try to apply update.zip it shows "data wipe failed" somewhere in the screen.
Anyway, here's what I did to get it back where you can flash JFD or Kies mini to recognize your phone for Tmobile update etc. even though "MBR Checksum Error, Movinand Checksum Confirmation Fail" still exist. I can't tell if that is normal or not, but at least Kies upgrade works...and can still install app and no more black soft brick.
Files needed:
* i9000 Froyo file: Eugene_2E_JK2_Froyo.tar.md5 (from http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=3
in the link "Vibrant_Full_Froydin_AND_2E_Recovery_+SD_Fixed"
http://www.multiupload.com/12QAKU043I )
* s1_odin_20100512.pit ( also from same page above but in the pit link )
* T959UVJFD.tar ( from http://www.justanotherdev.slackdev.com/T959UVJFD.tar via http://forum.xda-developers.com/showthread.php?t=734475
* i9000 with cwr to disable voodoo lagfix (ext4) Voodoo-stable-5.2-Froyo-2.2.1-GT-I9000-odin-pda.tar (from http://dl.project-voodoo.org/Voodoo-stable-5.2-Froyo-2.2.1-GT-I9000-odin-pda.tar or whatever new files at http://project-voodoo.org/download for Froyo )
1) Get your phone into download mode, fire up ODIN ( I used 1.7)
2) In ODIN, load s1_odin_20100512.pit into PIT and Eugene_2E_JK2_Froyo.tar.md5 into PDA. Checked or unchecked repartition does not seems to make a difference. Hit start and wait till completion with a pass. Reboot. It'll boot but will you not be able to install ROM Manager or most other apps with error saying something about no diskspace.
3) Copy the Froyo 5.2 Voodoo-stable-5.2-Froyo-2.2.1-GT-I9000-unsigned-update.zip for i9000 to your Vibrant /mnt/sdcard/update.zip via phone file manager or adb push... Then do 'adb reboot recovery' to put the phone into recovery mode or the 3 button push method.
Boot will show i9000 and button will go in wrong direction on your vibrant in recovery mode...ignore the wrong direction...go to voodoo lagfix, disable it, reboot.
4) Go to download mode and fire up ODIN again. Load s1_odin_20100512.pit into PIT and T959UVJFD.tar into PDA. Make sure 'repartition' is selected/enabled. Hit start, reboot, now things back to normal. You can install app...or do Kies...whatever...
PS: Can someone who have normal working phone let me know if you still get "MBR Checksum Error, Movinand Checksum Confirmation Fail" when going to recovery mode?
PPS: Instead of Kies, you get back to official stock froyo via odin with this only file (load to PDA) and NO repartition checked: T959UVKA6_REV05_home_low_CL860813.tar.md5
( from http://www.multiupload.com/GZT6ZYFX46 via http://forum.xda-developers.com/showthread.php?t=919687 )
kobesabi said:
Thanks to this post, it helped took me off the loop of not able to restore JFD over it or truly get back to stock. I think I got it all restored as I can now install app and stuff.
It all happened when I took wrong advice or misunderstood and did "Wipe Partition Cache" in CWR. problems...after problems...after problems...
Phone Symptoms: Vibrant S splash screen and noisy bootup sound were there, but it changed to black screen with all four buttons at bottom lit up for a little while then disappeared to all pitch black on phone screen and buttons. I guess you can call it black soft brick? When you odin back using Eugene_2E_JK2_Froyo.tar.md5, it gets your Vibrant in semi-bootable state. If you odin back JFD tar, it brings back to original problem. In the recovery screen you also see "MBR Checksum Error, Movinand Checksum Confirmation Fail"...and when you try to apply update.zip it shows "data wipe failed" somewhere in the screen.
Anyway, here's what I did to get it back where you can flash JFD or Kies mini to recognize your phone for Tmobile update etc. even though "MBR Checksum Error, Movinand Checksum Confirmation Fail" still exist. I can't tell if that is normal or not, but at least Kies upgrade works...and can still install app and no more black soft brick.
Files needed:
* i9000 Froyo file: Eugene_2E_JK2_Froyo.tar.md5 (from http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=3
in the link "Vibrant_Full_Froydin_AND_2E_Recovery_+SD_Fixed"
http://www.multiupload.com/12QAKU043I )
* s1_odin_20100512.pit ( also from same page above but in the pit link )
* T959UVJFD.tar ( from http://www.justanotherdev.slackdev.com/T959UVJFD.tar via http://forum.xda-developers.com/showthread.php?t=734475
* i9000 with cwr to disable voodoo lagfix (ext4) Voodoo-stable-5.2-Froyo-2.2.1-GT-I9000-odin-pda.tar (from http://dl.project-voodoo.org/Voodoo-stable-5.2-Froyo-2.2.1-GT-I9000-odin-pda.tar or whatever new files at http://project-voodoo.org/download for Froyo )
1) Get your phone into download mode, fire up ODIN ( I used 1.7)
2) In ODIN, load s1_odin_20100512.pit into PIT and Eugene_2E_JK2_Froyo.tar.md5 into PDA. Checked or unchecked repartition does not seems to make a difference. Hit start and wait till completion with a pass. Reboot. It'll boot but will you not be able to install ROM Manager or most other apps with error saying something about no diskspace.
3) Copy the Froyo 5.2 Voodoo-stable-5.2-Froyo-2.2.1-GT-I9000-unsigned-update.zip for i9000 to your Vibrant /mnt/sdcard/update.zip via phone file manager or adb push... Then do 'adb reboot recovery' to put the phone into recovery mode or the 3 button push method.
Boot will show i9000 and button will go in wrong direction on your vibrant in recovery mode...ignore the wrong direction...go to voodoo lagfix, disable it, reboot.
4) Go to download mode and fire up ODIN again. Load s1_odin_20100512.pit into PIT and T959UVJFD.tar into PDA. Make sure 'repartition' is selected/enabled. Hit start, reboot, now things back to normal. You can install app...or do Kies...whatever...
PS: Can someone who have normal working phone let me know if you still get "MBR Checksum Error, Movinand Checksum Confirmation Fail" when going to recovery mode?
PPS: Instead of Kies, you get back to official stock froyo via odin with this only file (load to PDA) and NO repartition checked: T959UVKA6_REV05_home_low_CL860813.tar.md5
( from http://www.multiupload.com/GZT6ZYFX46 via http://forum.xda-developers.com/showthread.php?t=919687 )
Click to expand...
Click to collapse
Thank God, I found this post....just fixed this phone I got from eBay, this was the biggest issue, could not install nothing due to that checksum error thingy now all good. Now I need to figure out why the screen lights up 10 seconds after user presses the power button, thank you!!
Thank you for this, I am trying to help a friend and this was the only procedure that I found that worked.. Thank you, after 5 hrs of work.. its booting from the black screen... Thanks!
@ kobesabi thanks alot...
thanks alot my frnd...
my fone's back in action now..
thanks very much
than you so much!
the link is dead
phone boots now perfectly but i still get checksum error.
I got this error while I partitioned internal SD card for 4 GB data space using subzero 159 kernel. I tried above methods but can't get rid of checksum error. I never have had an issue flashing ROMs. only problem is that I loose baseband version on many kernels using jelly bean and kit kat. although some kernels with fine. my idea is partition internal card to 0 MB using subzero then flash Eugene and rest of process. may it work.
kobesabi said:
Boot will show i9000 and button will go in wrong direction on your vibrant in recovery mode...ignore the wrong direction...go to voodoo lagfix, disable it, reboot.
Click to expand...
Click to collapse
When I get to this step there is no option to disable the voodoo lagfix. Just the normal recovery options like reboot and reinstall packages.
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.
Alright so I just got a fascinate today. Already rooted it and looked on how to get in to recovery. Well I did the install with odin steps and all that jazz and everything appeared to go fine until I go to reboot into recovery in rom manager. It just takes me to the stock recovery and gives me the signature error or whatever it says. I tried doing a factory reset and rooting/odin all over again to no avail. Now what should I do in this situation?
QUOTE=iammclovin804;16065943]Alright so I just got a fascinate today. Already rooted it and looked on how to get in to recovery. Well I did the install with odin steps and all that jazz and everything appeared to go fine until I go to reboot into recovery in rom manager. It just takes me to the stock recovery and gives me the signature error or whatever it says. I tried doing a factory reset and rooting/odin all over again to no avail. Now what should I do in this situation?[/QUOTE]
Unless your on cm7, rom manager is useless to us as of right now....
Recovery gets over written on every boot from the stock kernel , if you wish to get recovery to stick, you must odin recovery and immediately hold up down and power (the three finger salute) until you see the recovery screen...at that point your must flash a non stock kernel at the least, otherwise recovery will be overwritten right then and there.
After recovery is on there permanently, holding up down power is how you will enter recovery....if however you go to cm7 you would choose reboot recovery from the power button menu
Sent from my SCH-I500 using XDA App
iammclovin804 said:
Alright so I just got a fascinate today. Already rooted it and looked on how to get in to recovery. Well I did the install with odin steps and all that jazz and everything appeared to go fine until I go to reboot into recovery in rom manager. It just takes me to the stock recovery and gives me the signature error or whatever it says. I tried doing a factory reset and rooting/odin all over again to no avail. Now what should I do in this situation?
Click to expand...
Click to collapse
Which recovery are you trying to flash? Better yet, which ROM are you trying to use?
If you'd like to try CM7, I posted steps I did that worked flashing CM7 on another thread.
Refer to: http://forum.xda-developers.com/showpost.php?p=16048409&postcount=10
This is installing CM7 after I Odined from Stock.
Hope you find it useful.
If you like the ROM, don't forget to say thanks to JT!
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