To all vibrant devs here,
i make a new thread so i can find a clue to my vibrant which is getting stuck in recovery mode <3e>. i searched for all stuck in recovery mode thread, but it seems i can't find any clue there.
here is the situation:
i have a t-mobile vibrant in t959uvkb1 baseband, was using bionix 1.3.1 rom, and overstock kernel.
i updated the kernel accidentally to cwm7 kernel (cwm v3.0.2), then my vibrant went in bootloop. i couldn't even get back to bionix and overstock.
i was using odin to flash the vibrant back to stock (t959uvjfd.tar), and somehow i didn't uncheck the re-partition, so it became totally blank.
then i found t959uvkb1.tar in this vibrant forum, i flashed it again with odin, and now my vibrant get stuck in recovery mode <3e>
i see there are 5 choices only:
reboot system now
reinstall packages
delete all user data
delete cache data
format internal sd-car
everytime i reboot, it come to this recovery mode again
i try to reinstall packages, it says E: failed to open /mnt/internal_sd/update.zip (no such file or directory).
i have bionix 1.3.1 rom and overstock kernel files stored in internal sd-card though.
my question is:
which rom is suitable with this recovery mode?
is there any way that i can downgrade to 2e?
need help from anyone.
thanks in advance.
update:
i managed to find eugene's froyo that doesn't brick file (t959uvjk2).
i used the file with odin, and i have my vibrant back to normal.
just curious, the baseband was t959uvkb1, and now it's jk2.
thanks to xda forum.
update 2:
everytime i reboot the device, flight mode always activated. i have to deactivate flight mode in order to get the signal.
i tried to flash the device back to t959uvkb1 and use odin to flash, my baseband goes unknown.
what should i do?
i need help desperately.
thanks.
no one answered yet??
need help desperately.
Might try Odin flashing all the way down to JFD? If you have a pit file and a full image (like JFD), repartitioning shouldn't be a problem. I always do it when flashing down to stock. Edit: Do be careful though!
Sent from my SGH-T959 using XDA Premium App
inconceeeivable said:
Might try Odin flashing all the way down to JFD? If you have a pit file and a full image (like JFD), repartitioning shouldn't be a problem. I always do it when flashing down to stock. Edit: Do be careful though!
Click to expand...
Click to collapse
@inconceeeivable,
thanks for the reply.
i've done flashing this vibrant so many times, with jfd, kb1, jk2, again and again.
everytime i flash it with jfd, it always stuck in vibrant logo.
when i try to flash it with eugene's froyo that does not brick (jk2), the baseband is there. but everytime i reboot the device, the baseband become unknown again.
i am confused now.
it's just the same when i updated the device with bionix 1.3.1, that changed my baseband to t959uvkb1.
do you know what i should do next?
That's strange that JFD is not working.
So wait... the baseband is disappearing with Bionix as well?
Have you tried flashing a modem on top of either of those?
Sent from my SGH-T959 using XDA Premium App
Related
First of all im new to xda and i wanna say thanks to all u guys out there that put in so much work to help those like me who mess up phones.
So i decided to root my phone an apply axura 205 and it work pefectly. Then i tried to apply the VooDoo lagfix and my phone said it was complete an then it booted into recovery mode an everytime i boot it it goes into recovery.
So then i ran odin wit the tar file an the 512 pit file. An now when its installing my phone says wipe failed. It restarts angoes to the samsung galaxy s logo then black. So now im stuck. Can anyone help please
Put the phone in DL mode and re-flash it again.
Are you in download mode or recovery
Sent from my SGH-T959 using XDA App
You need to flash eugenes no brick file first then flash the stock rom tar and pit file.
okay, I have been on here several days trying to find a solution to this..., I know I am the one that borked it, now I am asking for help in understanding what I need to do to fix it... here is a list of things that I know happened...
A. I rooted the phone, added CWM, created a backup.
B. installed ROMManager
I had seen things on the MUINE ROM, saw it in the list for the vibrant so what the heck right?
C. installed the MUINE from the ROMManager app, rebooted, found that it could not "See" T-Mobile...
D. checked here on issues with the current version of MUINE ROM issues... didn't see anything, so I made sure that it was in USB debug mode, and tried to restore the backup I had made earlier... now comes the problem... , I think that when I tried unsuccessfully to do that with CWM, I tried ODIN, and the re-partition box was ticked... and wiped the internal SD and the update.zip etc, and put it into usb debugging off...
since then, I have tried the revert to stock and root thread, the update that does not brick etc... the AIO Vibrant toolbox tells me that USB Debugging is off, and here is the info on the recovery screen...
Android system recovery <2e>
-- Movi_check Start..!!
checksum confirmation need_checksum[1636849899]
MBR_Chksum in header : id
MBR checksum : 4206DE4BFAA052703D8107823C7EDDAF
MBR Checksum Error
Movinand ChecksumConfirmation Fail
--movi_checking done!...
# MANUAL MODE #
-- Appling Muti-CSC...
Installing Muti-CSC
any help is appreciated...
So you have successfully reverted it back to stock jfd? And you are trying to root and it is giving you those msgs on recovery screen? If yes use one click root then download Rom manager and download the recovery again.
Alex9090 said:
So you have successfully reverted it back to stock jfd? And you are trying to root and it is giving you those msgs on recovery screen? If yes use one click root then download Rom manager and download the recovery again.
Click to expand...
Click to collapse
I am just trying to boot... it goes through the vibrant splash, the galaxy s splash, the tmobile sound and pink splash, and then black... if you touch the capacitive keys, they light up and stay that way... other than that unresponsive... ODIN shows no errors when trying to flash it too... but when it tries to boot after, it comes up to that recovery... I have also from the <2e> recovery screen tried "reinstall packages" but to no avail...
Flash Eugene's froyo that doesn't brick then without rebooting immidietly flash jfd stock and you should be good. Check out this thread if you need links. http://forum.xda-developers.com/showthread.php?p=14960217
Sent from my Transformer TF101 using Tapatalk
Alex9090 said:
Flash Eugene's froyo that doesn't brick then without rebooting immidietly flash jfd stock and you should be good. Check out this thread if you need links. http://forum.xda-developers.com/showthread.php?p=14960217
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
okay, so, load Eugenes rom, and turn off auto reboot, then when Odin is done, reset to the JFD .pit and pda, and turn auto reboot back on for that one?
okay, got it... the load JFD after the no brick without rebooting is what did it, THANKS!!! it probably should be noted when doing this to turn off the partitioning in odin, and the auto reboot and once odin has completed, then remove battery and USB, then bring it into download mode without letting it power up into no brick first... that was the step I was missing, thank you so much for the quick response!!!
Seannon
Well, I was previously running Comm rom, and i decided to switch to CM7 7/13
This didn't go so well. I Odin'd DL09 with atlas and repartitioned then installed Cmw and still Status 7 when I try to install. Then I tried installing 7/4 and it would just say something like "Checking BML" Or something, i forgot... and it would just reboot into cwm. I was running JT's cwm fix, and i tried with cwm all... I don't know what to do. Now my fascinate won't install comm rom, and every rom install just leads up to booting up in cwm.. no samsung logo.. Help??
Edit: Phone is now in "Manual mode"
i guess samsung recovery? but it wont boot. It just reboots into the same recovery after i press "reboot system now"
please? :'(
Just do this
after fighting with my phone yesterday trying to get it running this is what i did
Step one may be unnecessary but this is what i did.
1) Odined ED01 image let it boot. then Odind CWM3 3 finger salute. Flashed CommRom 2.0 when that was done i booted into CWM and disabled the VooDoo rebooted when the conversion was done.... i did step 2
2) in the OP of cm7 flash or odin the cwm
then flash the 07/04...
once that is up use the shutdown menu to access the Orange [cwm 4.0] cwm.
if you do a three finger salute it takes you to the RED [CWM 3.0] cwm.
Then flash the updates.
And suspect there was an issue with the Voodoo even though it said it was disabled. Good Luck
xwhofarted said:
Just do this
after fighting with my phone yesterday trying to get it running this is what i did
Step one may be unnecessary but this is what i did.
1) Odined ED01 image let it boot. then Odind CWM3 3 finger salute. Flashed CommRom 2.0 when that was done i booted into CWM and disabled the VooDoo rebooted when the conversion was done.... i did step 2
2) in the OP of cm7 flash or odin the cwm
then flash the 07/04...
once that is up use the shutdown menu to access the Orange [cwm 4.0] cwm.
if you do a three finger salute it takes you to the RED [CWM 3.0] cwm.
Then flash the updates.
And suspect there was an issue with the Voodoo even though it said it was disabled. Good Luck
Click to expand...
Click to collapse
That's the thing... It wont boot to anything i install on it.. But it sure as hell boots to ANY cwm i install... and it also boots to normal recovery in the absence of a cwm....
Can you get back to stock using odin? If you can try flashing a custom kernel after you flash the cwm recovery.
Sent from my SCH-I500 using XDA App
garywojdan81 said:
Can you get back to stock using odin? If you can try flashing a custom kernel after you flash the cwm recovery.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I can flash the DL09 with odin... but ive been there... 20 times. I havent tried a kernel but it probably wouldnt work seeing as it only boots back into cwm. I'm desperate...
EDIT: flashed EB01 voodoo... still boots into CWM... omg.
jamespweb1503 said:
I can flash the DL09 with odin... but ive been there... 20 times. I havent tried a kernel but it probably wouldnt work seeing as it only boots back into cwm. I'm desperate...
EDIT: flashed EB01 voodoo... still boots into CWM... omg.
Click to expand...
Click to collapse
Have you tried flashing the official vzw eb01..(not dl09 and not eb01voodoo) file with pit and repartition checked? If not do that and let it boot completely. You need to do this to make sure your ext4 partition is formatted to remove voodoo.
After you odin official vzw eb01 with the pit file and repartition checked let it boot fully.then odin 3-30 recovery and immediately boot to cwr...if it boots up fully you will have to re odin recovery.
At this point wipe everything and flash com rom 2.0 that will give you root, recovery and the rom....from there you can go to com rom 2.1or whatever your want but your phone should be up and running
Sent from my SCH-I500 using XDA App
efan450 said:
Have you tried flashing the official vzw eb01..(not dl09 and not eb01voodoo) file with pit and repartition checked? If not do that and let it boot completely. You need to do this to make sure your ext4 partition is formatted to remove voodoo.
After you odin official vzw eb01 with the pit file and repartition checked let it boot fully.then odin 3-30 recovery and immediately boot to cwr...if it boots up fully you will have to re odin recovery.
At this point wipe everything and flash com rom 2.0 that will give you root, recovery and the rom....from there you can go to com rom 2.1or whatever your want but your phone should be up and running
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I love you <3
My vibrant is in a boot loop after I attempted to flash a new kernel, I used Odin to try to go back to stock and it is still looping can anyone hep me?
Try to flash stock jfd using odin. Can u be able to get download mode?
Sent from my vibrant using xda premium
I did flash the jfd with Odin , and I can get to download mode just fine, I hope I didn't irreparably damage the boot loader
Doubt the boot loader is toast - you wouldn't be able to get to recovery/download if its shot.
When you Odin'd to JFD did you repartition?
al the videos and tutorials ive read said to NOT repartition.....should i?
i clicked the repartition box and i get the same result.....could my tar file be bad? or my pit?
If you Odin to JFD you can hit repartition. Thats the only way to get back to a stock setup from CM7 or ICS.
If at first boot it loops from and error when the kernel loads (forget the wording on it) you may need to flash Eugene's froyo that does not brick to clear it out.
There maybe somthenig wrong with your package. Try to download stock rom from samfirmware or vibrant bible. If you are not sure about your bootloader then flash the stock froyo bootloader using odain. Then try to flash stock jfd froyo. If still you have the same problem there may be a hardware issue or not assamble the circuit propely. try to deassamble and reassamble again. Once i got kind of problem, Whenever i give some presure to phones backside phone restart automatically. So i deassamble the phone and reasmble again. After that problem was solved.
www.samfirmware.com/
forum.xda-developers.com/showthread.php?t=771111
Sent from my GT-I9000 using xda premium
This happened to me the first time i flashed to ICS Passion.
Per the instructions in that post, try this:
Remove battery. Hold Vol Down + Home + Power Key. You will enter new recovery mode. Flash the ROM again.
Some users (having Froyo Bootloader) need to press Vol Up Key instead of Home Key to get in Recovery.
Maybe this helps?? Worked for me.
if it makes any difference i was rooted with the stock rom....i never installed a different rom.....
Based off your Youtube vid its looks like you got a bootloop compounded with rainbows. What kernel did you flash with kernel manager? Im betting it was a GB kernel and that is why you 1) have rainbows and 2) have boot loops.
You have 2 Options that come to mind.
1) Try and flash via Odin the overstock Froyo kernel. HERE
In ODIN Un-check Re-Partition - Auto Reboot and F. Reset Time can be checked here, you are justs flashing a kernel.
Click the PDA button and select the Overstock Kernel from the desktop
Boot the phone - does it work?
Option 2 - the dangerous route
Now DO THIS AT OWN RISK - This is what I would try if #1 fails but its up to you to try it.
Flash back to the Froyo boot loaders - if you do this uncheck auto reboot in odin. Cause if it errors when flashing bootloaders and reboots - you are screwed. If you flash them and it says sucess - you can always hold the power button for 10sec to manully reboot it.
Froyo / Ginger Boot loaders thread
(If you flashed a GB kernel via kernel manager that means you already have the Froyo boot loaders, but the general thinking is if you flash back to JFD it may be a good option to flash the Froyo boot loaders first. I have never done that.)
After you load the Froyo boot loaders then try to flash back to JFD with partition check as intructed here (under #4):
http://forum.xda-developers.com/showthread.php?t=1307637
You can get JFD from above thread too.
Hope it works out.
UPDATE! boot loop went away....now its just froze at the boot screen!...lol fu** my life
holy mother of pearl....i called samsung and they said they would reflash it for FREE.....thanks for all your help moped guy.
the guy just probably wrote the servie order for a reflashing and didnt tell them why.....lol yay for waranties!
So my vibrant won't boot up. I've tried odining it back to stock, and no matter what I do, it will almost get to the galaxy S screen (freezes as it is forming the S). Download mode and recovery mode both work.
Pull the battery, boot into recovery and wipe factory reset, wipe cache, and advanced->wipe Dalvik. The reboot. Will take longer b/c it has to rebuild Dalvik but it should work out fine. I had the same thing happen the two nights ago coming off ICS.
Don't forger you won't have CWM and it isn't in the market for 2.1 anymore. You can download it from my signature. Put Update.zip in internal and hit reinstall packages twice (that is if you want flash or restore).
Are you able to "Reinstall Packages" from recovery or does that fail?
Did you check re-partition when converting to stock?
You may have corrupted your internal SD
Sk3tchy said:
Are you able to "Reinstall Packages" from recovery or does that fail?
Did you check re-partition when converting to stock?
You may have corrupted your internal SD
Click to expand...
Click to collapse
The reinstall packages fails. It says: "can't open /sdcard/update.zip" (no such file or directory).
Woodrube said:
Pull the battery, boot into recovery and wipe factory reset, wipe cache, and advanced->wipe Dalvik. The reboot. Will take longer b/c it has to rebuild Dalvik but it should work out fine. I had the same thing happen the two nights ago coming off ICS.
Don't forger you won't have CWM and it isn't in the market for 2.1 anymore. You can download it from my signature. Put Update.zip in internal and hit reinstall packages twice (that is if you want flash or restore).
Click to expand...
Click to collapse
I don't have the option of wiping the Dalvik in recovery. I think its because it went back to the default "Android system recovery <2e>"
I tried wiping everything, but when it boots, it goes to the vibrant screen, then to the tmobile screen (the boot sound works), but then, the screen turns black and it goes back to the vibrant screen again (and it just keeps looping).
Maybe try ka7 or kb5 instead of jfd? Investigate /mnt/efs and the copies in /sdcard/backup? Don't know much about eds, might be worth a look. Reflash SBL for good measure?
cashmundy said:
Maybe try ka7 or kb5 instead of jfd? Investigate /mnt/efs and the copies in /sdcard/backup? Don't know much about eds, might be worth a look. Reflash SBL for good measure?
Click to expand...
Click to collapse
So I flashed ka7, and it gets past the S logo now, but then it turns black and now it says "Kernel Panic" upload mode:
RST_STAT=0x4
PMIC_IRQ1=0x0
PMIC_IRQ2=0x0
PMIC_IRQ3=0x0
PMIC_IRQ4=0x0
PMIC_STATUS1=0x40
PMIC_STATUS2=0x2C
Go to the dev section and download the Toolbox. It is stickied. It has drivers, Odin and the Pit/Tar files to get you back to stock. Get back into download mode and re-run Odin with those files.
Don't forget that you don't have to see the DL mode on your screen as long as the COM box is yellow in Odin.
Also check out this thread.
Woodrube said:
Go to the dev section and download the Toolbox. It is stickied. It has drivers, Odin and the Pit/Tar files to get you back to stock. Get back into download mode and re-run Odin with those files.
Don't forget that you don't have to see the DL mode on your screen as long as the COM box is yellow in Odin.
Also check out this thread.
Click to expand...
Click to collapse
I tried using the toolbox and reflashing the stock rom, but it just gets to the t-mobile "stick together" screen, then screen turn black, then it goes to the battery charging screen.
If you're doing Odin right, with a good rom and pit file, and still have trouble, I guess you could flash the SBL. I had a rom flash (via zipfile) do something unknown which made it nearly impossible to get into download mode. Once I did, I flashed the SBL and I was fine. No idea what happened. I even had a nandroid backup, not a restore, hose my phone once. When the other Phone Gods turn against you, Odin is your friend.
cashmundy said:
If you're doing Odin right, with a good rom and pit file, and still have trouble, I guess you could flash the SBL. I had a rom flash (via zipfile) do something unknown which made it nearly impossible to get into download mode. Once I did, I flashed the SBL and I was fine. No idea what happened. I even had a nandroid backup, not a restore, hose my phone once. When the other Phone Gods turn against you, Odin is your friend.
Click to expand...
Click to collapse
But I can get into download mode. And which sbl should I flash?
Probably the closest-to-stock Froyo SBL you can find.
I'm using a GB SBL from this thread, and he has Froyo also:
http://forum.xda-developers.com/showthread.php?t=1117990
I got stuck in this loop a few months back flashing back to stock from CM7 when Odin froze.
I could get to Download Mode and Stock recovery but had the same error when attempting to "Reinstall Packages" from recovery. The internal SD partition had corrupted.
I flashed Eugene_2E_JK2_Froyo with Odin, which fixed the Internal SD.
If you follow the write up on unbricking when you have the little triangle and phone error on your screen it will get you out of this one.
Your bootloaders are not the issue here. 2e Recovery isn't seeing the Internal SD Card and that it what is causing the hangup on boot.
Yeah, probably just flashing a decent kernel would fix you up, but unless you can find an Odin kernel file, you need to do the whole rom.
BTW, with Linux, you can use
tar -tf <rom file> if you want to see what's in a rom.
You can download the Odin flashable Overstock Kernel which contains the red recovery and flash it. That would give you the ability to format the internal SD and then Mount it to your PC through recovery and copy a Rom over to flash.
Otherwise the Unbrickable Froyo I mentioned before will also work.
The only thing you can do when stuck in a boot-loop, if the previous suggestions don't work, is to just reflash it. You can flash back to stock easily using Heimdall One-Click. http://forum.xda-developers.com/showthread.php?t=1278683
We're missing some info here. What ROM were you using before you flashed back to stock? Did you use a pit file in addition to the pda file in ODIN?
If you were using an ICS (android 4.0.x), flashing back to stock and didn't use a stock pit in addition to stock pda, it would definetly be giving you problems. ICS uses a different partition scheme then does stock (which is on android 2.1). The pit file tells odin how to partition your phone.If you're flashing from Froyo, then this should not be relevant as it uses same partition scheme as stock.