[Q] What am I missing? stuck in recovery. - Vibrant Q&A, Help & Troubleshooting

I was loading a 2.2.1 rom (Dead Horse kernel and darky's ROM). all appeared to load, but when it went to reboot, it went into 3e recovery. Vibrant screen comes up, then it goes into recovery with the following error.
E:Can't mount /dev/block/st110
E:copy_dbdata_media Can't mount DBDATA
I have tried odin 10+ times, always the same. I have used differant DL'd 512 and jfd and a couple others.
I disabled voodoo prior to doing all of this.
I searched, all threads said to odin back. I even loaded a voodoo kernel, it took me to the red recovery..
What am I missing?
Any links advice...
Yes I can get into download, and yes odin see's my phone.
Would bootloader update hurt or help?

The original JI6 files always works for me. Have done a wipe and erased everything? Try it with repartition checked? Can't hurt at this point.

I think I tried that, but will try again. I have odin'ed a few times in the past, never ran into this.

FIXED:
I used AIO tools to load it all for me and it worked. It did have repartition checked. I know I had done that once before.

Related

[Q] Flash Stock using Odin, phone boots fine, but stuck on black screen lights

Hello,
I tried to recovery my phone by using Odin3 to install the stock 2.1 vibrant rom. I am using the rom from the official sticky about fixing a bricked phone.
Odin3 1.0 did not work and it would always freeze on a process even after trying it over and over again at least 5 times. So, I changed to use Odin3 1.7 which I found a link to on xda. This one installed successfully and went through the whole process and my phone rebooted. When it rebooted I saw the Samsung Vibrant Screen, then the T-Mobile screen then the Galaxy S screen fine like normal. But once it got passed the S screen a black screen would come up and all the button lights stay lit up and nothing happens for hours. I tried installing the rom several times, tried different links to the offical JFD stock rom, but everytime I try to install the same thing would happen. What do you recommend I should do to fix this problem?
wipe cache partitin , factory reset in rrecovery ?
Yes, I did. I wiped cache and data, but it still is is still stuck at the black screen.
Your using the JFD.tar in PDA and 512.pit in PIT and Repartition is NOT checked?
Yes, I made sure it was not checked and It was checked automatically the first time and I didn't realize that odin checks that automatically, so I unchecked it and did it a second time. The phone still gets stuck at the black screen with light up buttons.
I am trying the Eugene's Unofficial Froyo rom right now because what initially bricked my phone was installing 2.2 from Kies and that failing. When that failed I unplugged the phone and got the computer to phone icon screen and could no longer boot, so I went to install the stock rom.
The problem I am having with Eugene's Unofficial Froyo rom I am having now is that I have 0 space for applications and cannot install applicants even after doing a wipe and factory reset. Does this have to do with accidently setting it to re-partition and if so, how can I fix the no application storage issue so that I can install applications?
Thanks
I was thinking he designed this ROM just specifically to help bricked vibrants...I think you just use it as a means to reflash another ROM or back to stock or whatever.
I did what you had phone ! PC.. last night to my wife's phone....left it on that screen and plugged into pc with ODIN open..it showed a COM port so I flashed it like that and it boots right up.
I wonder if it has anything to do with Voodoo? I had a Voodoo Lagfix installed prior to doing the upgrade to Froyo 2.2 using the official method. May be why it failed. so I decided to flash back to stock. When I flashed stock 2.1 the phone would boot up then show the Vibrant Screen then the T-Mobile intro then the Galaxy S intro but once it got passed that the screen would go black and the buttons would stay lit up. I flashed Eugene's unofficial 2.2 ROM (no longer posted on xda, but it is on his website). That booted up perfectly, but the problem was that I now had 0 application storages and apps could not be installed on internal memory (could still install apps on SD card, I used this to install Rom Manager to the SD Card to flash Clockwork Recovery just in case)
Today, I tried flashing the Stock 2.1 rom back onto it (Phone was currently running Eugene's rom), but I have the same result with the black screen and lit buttons.
I looked at the FAQ for removing Voodoo and added a folder named "disable lagfix" in the Voodoo folder on the internal SD card. I ran this, but the problem still persisted, so I decided to flash again to see if it would be fixed. Still the same thing occured.
If this is a Voodoo problem, is there another method for removing Voodoo that I could try? I need to make sure that it is restored to the default RFS file structure that came with the phone and flash stock 2.1
Hmmm...odin back to eugenes froyo & unmount ur internal sd & format...go ahead and remove ur microsd & sim also...& then try to odin just the. Tar for jfd no pit ...no repartition..try to use ka6 instead of a 2.1..
Sent from Bionix V powered Vibrant
flash back to JFD eclair from bible with 512 pit and repartition ticked .
just for record JFD.zip goes in to pda
ViralCipher said:
I wonder if it has anything to do with Voodoo? I had a Voodoo Lagfix installed prior to doing the upgrade to Froyo 2.2 using the official method. May be why it failed. so I decided to flash back to stock. When I flashed stock 2.1 the phone would boot up then show the Vibrant Screen then the T-Mobile intro then the Galaxy S intro but once it got passed that the screen would go black and the buttons would stay lit up. I flashed Eugene's unofficial 2.2 ROM (no longer posted on xda, but it is on his website). That booted up perfectly, but the problem was that I now had 0 application storages and apps could not be installed on internal memory (could still install apps on SD card, I used this to install Rom Manager to the SD Card to flash Clockwork Recovery just in case)
Today, I tried flashing the Stock 2.1 rom back onto it (Phone was currently running Eugene's rom), but I have the same result with the black screen and lit buttons.
I looked at the FAQ for removing Voodoo and added a folder named "disable lagfix" in the Voodoo folder on the internal SD card. I ran this, but the problem still persisted, so I decided to flash again to see if it would be fixed. Still the same thing occured.
If this is a Voodoo problem, is there another method for removing Voodoo that I could try? I need to make sure that it is restored to the default RFS file structure that came with the phone and flash stock 2.1
Click to expand...
Click to collapse
When you do the disable lagfix are you rebooting and letting it convert the filesystem back to rfs or are you just powering down and going to d/l mode and trying to ODIN? You need to reboot the phone and let Linda do her thing and power up, then power down etc etc..
jmcghee1973 said:
When you do the disable lagfix are you rebooting and letting it convert the filesystem back to rfs or are you just powering down and going to d/l mode and trying to ODIN? You need to reboot the phone and let Linda do her thing and power up, then power down etc etc..
Click to expand...
Click to collapse
Yes, I rebooted after applying the disable lagfix, but it booted normally and didn't seem like it was doing the Linda thing....I wasn't sure if it worked or not. How would I know if it is back to using the RFS system?
I tried different roms and I had no luck. The KA6 Rom that flashes via odin installs fine, but it goes to the Recovery Screen the E3 one I think, and when it tries to mount DATA and other partitions it fails to do so, and somethings fail to be wiped. It doesn't boot.
When I run the JFD odin, when it goes to recovery for the first time it has one error where it fails to wipe DATA. Not sure if these are the reasons why I am having problems though.
I formated all partitions including the internal sdcard. Still no luck.
So far the only ROM that I got working is Eugene's 2.2..but I can't install applications with that one.
I tried installing the Bionix V Rom via ClockWork Recovery, but once it begins to Copy Files it errors out with an Error on line 13 and copy's out an error log. I posted a response to the thread about this ROM. I redownloaded to ensure it wasn't corrupted.
*****If you need more information on the EXACT Rom I installed prior to the brick here is the thread to the rom I installed. Maybe that will help you help me more ******
This is the rom I had before attempting to upgrade to Froyo:
http://forum.xda-developers.com/showthread.php?t=791478
I installed the Stock Recovery version.
Edit: I know this rom above is a kernal mod. I did flash the stock Vibrant kernel prior to installing the JFD ROM from this link: http://www.justanotherdev.slackdev.com/kernel-vibrant-stock.tar.md5.tar
crap dude do yo uhit repartition when u flash ka6 ? if so dont do so if its only update , dont check partiton if you flash just an update , hit partitoon if u flash offical release .
yes go back to jfd repartiton update to ka6 withou repartiton
bartek25 said:
crap dude do yo uhit repartition when u flash ka6 ? if so dont do so if its only update , dont check partiton if you flash just an update , hit partitoon if u flash offical release .
yes go back to jfd repartiton update to ka6 withou repartiton
Click to expand...
Click to collapse
When I install the JFD with or without repartition I get passed all the boot screens, but it screen goes black and buttons light up..Sorry if I am being a noob and missing something obvious...but I followed those instructions, and I did it multiple times as well.
FIXED!!!
I fixed it wohooo!!!! I flashed Eugene's Froyo that doesn't brick version then flash back to stock JFD and its working perfectly! Thanks XDA! Found out that a lot of people with this issue after having Voodoo installed and installing a different rom, and that this rom was made to fix the Voodoo brick. Funny thing is the Eugene's rom fails on recovery with errors in this case, but it still unbricks the phone lol
Ahhh see lagfix didnt disable..glad you got it working..
Thanks for your help. I now am using the Bionix-V Rom with the Dragon-Kernel Voodoo and let me tell you I love this phone even more now with this Rom. Loving the Gingerbread theme and it runs super fast. Stock is too slow for me lol Anyway, this is resolved no more offtopic posts lol...
ViralCipher said:
I fixed it wohooo!!!! I flashed Eugene's Froyo that doesn't brick version then flash back to stock JFD and its working perfectly! Thanks XDA! Found out that a lot of people with this issue after having Voodoo installed and installing a different rom, and that this rom was made to fix the Voodoo brick. Funny thing is the Eugene's rom fails on recovery with errors in this case, but it still unbricks the phone lol
Click to expand...
Click to collapse
would you please tell all the steps you did to make it work

Not enough internal space to install anything?

Well I was one of the people with issues with that Kernal. I just got back to stock by ODINing to (I think) the samsung JKL/a voodoo kernal. Something like that.
Anyhow. Now I was trying to install the one-click-root, when it informed me I have too little internal space. I can't download form the market either. My phone has NOTHING on it.... help? I seem to remember this being an old problem.
Really, thank you everyone who takes the time to help. I'm super-thankful for the excellent support XDA members offer.
Oxirane said:
Well I was one of the people with issues with that Kernal. I just got back to stock by ODINing to (I think) the samsung JKL/a voodoo kernal. Something like that.
Yea i had the same issue with that Kernel. seems that if you unmount the sd in the settings menu you can install apps again. Whitehawx (i think) suggested it in the vibrant 4g rom thread. so far it works for me.
good luck!
Click to expand...
Click to collapse
dwa_jeff said:
Yea i had the same issue with that Kernel. seems that if you unmount the sd in the settings menu you can install apps again. Whitehawx (i think) suggested it in the vibrant 4g rom thread. so far it works for me.
good luck!
Click to expand...
Click to collapse
No such luck here....
Thinking I may have to mess around a bit more with ODIN tomorrow, bleh.
If anyone knows how to get a recovery mode working, that'd be great too. I just want my apps and custom roms back! D:
i have just recovered from this same problem today
but unfortunately i cannot say exactly what i have done to remedy the issue
but i will try , hopefully someone more knowledgeable can enlighten...
1st i rooted and then flashed bionix v! with the voodoo and it was great
2nd saw kernel with voodoo sound and thought that would be awesome
since i am noob, this went fubar
i think i interrupted the "process", and i certainly didn't disable the lagfix, oh and the kernel was from i9000, idunnoifthatmatters....
at any rate the phone booted but there was 0 space for apps, and the volume buttons were inverted, lol
so i reflashed the original kernel and the buttons were good again but the apps still had no space and 'linda' kept saying, "creating partition, zero space on partition" on boot up and shutdown.
in clockwork recovery mode i learned that it was data drive that would not mount
the error message was cant mount dev/block/mmcblk0p1 (file exists)
using clockwork recovery i tried to format the data 'drive' to no avail
i also turned off all options for voodoo lagfix
then i tried to reflash the boinix-v, that crashed out quick, and at last the phone would not boot!! it really took some effort
finally i tried to flash a non-voodoo rom over all this stuff, which seemed to go through, but i still could not boot the phone, stuck at the vibrant screen.
it is at this time that i finally get the drivers to work and odin registers the device, i downloaded the ADK and i am ready to use some shell commands, so i am going to reboot into download and give ODIN a shot, but my fingers slips and i am in stock recovery mode? i have no idea where clockwork has gone but now
but this is immed executed upon entering stock recovery
-- Movi_check Start..!!
checksum confirmation need_checksum[0]
Not need checksum confirmation
--Movi_check already executed!!...
-- movi_checking done!...
update media, please wait
update media, finished
# MANUAL MODE #
-- Appling Muti-CSC...
Installing Muti-CSC
install default apk-files, please wait
install default apk-files, finished
ASR also has an option to format the internal sd, and to delete cache, i did all of that!
and attempted to reboot the system, and to my surprise the **** did!
It booted to that last no voodoo rom that i flashed and the application partition is functioning!?!
i lost all data that was on the internal sd however, but i am back up and running, although i am not sure why
Thanks gqs, I'll try that later....
Thing is, my clockwork disappeared. :/ Supposing I'll try to odin another rom and see if that works, any roms in particular that may fix this?

[Q] Samsung Screen only...Red Clockwork not coming up!

I thought I had this down and well, I guess not....
I had a great running Superclean v2.6 nonvoodoo running on my DL09 and I did a factory reset from inside the settings. I was trying to setup my Google account so my Google Voice would work right. I had made a backup using red Clockwork so I thought I'd be okay. The phone rebooted and hung on the Samsung screen.
I've been able to Odin the new cwm-recovery-ALL.tar to the phone but it still hangs. I tried using the old version CWMrecovery.tar and it boots in the factory recovery (2e) and won't allow me to apply the update.zip file since it can't mount the drive.
Um, is there a way out? I thought I saw a tar file for the DL09 and that would take me back to stock and then I could install the red recovery and restore my back up. Any help would be appreciated. Thanks!
Error in factory recovery (2e):
E:Can't mount /dev/block/vold/179:9
Can't mount SDCARD:update.zip
Installation aborted.
You can flash to EB01 with all the stuff in this post:
http://forum.xda-developers.com/showthread.php?t=977493
Thanks! I think I found another route, but your solution looked good.
I used Odin and put the cwm-recovery-ALL.tar on after having put CWMrecovery.tar (the older version) and it started into red. I applied the update.zip and installed cwm-recovery-ALL.zip and then am now in the process of restoring my backup. Whew! That was close.
*EDIT*
So, that didn't actually work. When I tried to restore with RED Clockwork it froze during the restore. It specifically froze on restoring the "tegra_flash_image". I even tried using the DL09_stock.zip and that didn't work either. I used the method you recommended and it worked very well. In fact If I need to go back to stock this method seemed the fastest and most straightforward. Thanks again.
For those who read this later. I then installed my ROM choice, which is non voodoo Superclean v2.6 after doing everything listed here http://forum.xda-developers.com/showthread.php?t=977493 and it was much cleaner than what I had originally.

[Q] Bricked Phone from MIUI

Hey guys
I flashed my phone with the latest MIUI ROM with Rom Manager, and now I'm stuck in a soft brick. It gave me an error when I tried flashing the ROM, and when I try restarting the phone, it is just stuck in the Vibrant boot screen. I went into the recovery and tried flashing my backups and doing a full backup recovery, but nothing works. I can't mount either the sdcard or the external sdcard, it gives me the error (device busy). Also, I can't seem to mount into USB, and I can't mount anything on principle, even if it was mounted before and I unmounted it. Is my phone toast?
you HAVE to odin to stock JFD first. it's been explained and exclaimed MANY times in the CM7/MIUI threads. the recovery on 2.3 does not work with nandroids made using a 2.xxx CWM recovery (GB has to CWM v 3 or higher).
Also, there is a different partition type using CM7/MIUI that isn't cmpatible with the stuff samsung uses.
tl;dr: ODIN to JFD and the flash your roms/nandroids.
can't find any working JFD links online, or the files needed for ODIN.. anyone got a link?
OK, cool, finally got ODIN to work, phone unbricked, thanks!
OK, but if I follow the instruction for MIUI, it says that I need to start with a 2.2 ROM. I was using bionix. Is Bionix fine to start with as long as you follow the other instructions?
geoffcorey said:
you HAVE to odin to stock JFD first. it's been explained and exclaimed MANY times in the CM7/MIUI threads. the recovery on 2.3 does not work with nandroids made using a 2.xxx CWM recovery (GB has to CWM v 3 or higher).
Also, there is a different partition type using CM7/MIUI that isn't cmpatible with the stuff samsung uses.
tl;dr: ODIN to JFD and the flash your roms/nandroids.
Click to expand...
Click to collapse
Could you elaborate on this or point to a source? I'm not at all doubting your credibility, it's just that I've been having signal issues that I'm can only hope are software-related (it's all spelled out in this thread). I've used Odin to flash JFD (official), JK2 (official), and Eugene's 'Froyo that doesn't brick' dozens of times in the past 2 days and I'm still not able to get any AT&T signal. I know my SIM is fine, as well.
One of the JK2 installs I had kept constantly giving RIL reset messages.
Or were you talking about the different FS format used in CM7 vs rfs/ext4?

After rushing in, ODIN is not helping me to recover =(

Hi I'm a new member,
I rooted my fascinate easily enough. Then searching and learning about ROMs and Kernels I decided to do use ODIN CWM Recovery to 'backup' or whatever most forums tell you to before installing a new ROM. Point is my phone is stuck in manual boot mode and I cannot undo it.
I have tried multiple times using ODIN plus the four stock files
Stock-i500-VZW-Kernel.tar.md5
Stock-i500-VZW-pit.pit
Stock-i500-VZW-Recovery.tar.md5
Stock-i500-VZW-System.tar.md5
(I always would try to implement them in order pit/system, pit/kernel, pit/recovery)
Unfortunately after the first one (pit/system) ODIN says the process fails, I go ahead with the other two and they both amount to nothing happening. My phone does not reset or do anything for this matter and I am forced to shut down ODIN and unplug my phone (upon which it dies with no battery).
Then I put back in the battery and Im back to before in manual boot mode with
Reboot system Now
Apply sdcard:update.zip
wipe data/factory rset
wipe cache partition
Btw wiped data and wiped cache and it didn't help me =(.
Please someone help me, I really don't want this new phone to be dead... Thanks in advance
Oh and when I press "apply sdcard:update.zip" I receive
E:Can't mount \dev\block\vold\179:9
(No such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.
I really don't care at all about keeping the phone rooted or not or whatever. I just want to be able to make calls again!
So it looks like you're stuck in blue recovery ... sounds like something that Odining a stock package should fix.
Here is a nice thread for getting back to stock (it's a sticky in the general section). The packages include system, recovery, kernel, and radio in a single file (I've actually never odin'd four separate files to get back to stock, or even ever flashed a system-only file), though no pit file.
So open up odin with your phone in download mode (with the battery out, otherwise there's a small chance of odin stalling at the end), and use:
- either the DI01 all-in-one, EB01 all-in-one, or this DL09 package in PDA
- the pit file in PIT (the link says DI01/EB01 but it also works with DL09)
- check "re-partition" if it isn't already checked
- run odin and hopefully in five minutes your phone will work again If for some reason it doesn't, that thread has instructions for using heimdall, although I've never had to resort to it.
So try this and see if it works! (For which package to use, I'd suggest trying DL09 first (since you'll need it to get to the official froyo build) and DI01 if that fails. If you're wondering whether DL09+pit actually works, I've used it to get out of a "stuck in blue recovery after odining stuff" situation myself so yes, it works.)
Thank you for the response! It's encouraging to hear any support and I think yours is promising.
So unfortunately I tried D101 and no go. Turns out this was before I realized this was for 2.1 and I'd prefer 2.2 for the upgrades. Although would you suggest 2.1 for the purpose of rooting/ROMing/Kerneling in the future? I ask because I'm slowly gaining confidence that after fixing this I might be willing to try this again...
Odin (1.7 -> I decided at your poster friend's advice to upgrade from 1.3) worked well said 'pass' and everything. Unfortunately when booting my phone it went straight to the boot screen as always.
Meanwhile I'm downloading the EB01 and your suggested DL09 to test those two.
Hopefully one of those will work but if not, I guess I'll try that heimdall technique the poster suggested in the other forum. Hopefully not tho b/c it looks a bit more complicated.
I'll let ya know if one of these others works.
Yes it worked!! Thank you so much! I would buy you a round at the ale house if I could!
After running EB01 it worked (with the pit file going all the way back to factory settings). So I'm not sure what this means - maybe since it was after upgrading to 2.2 that my phone bugged out, it could only be restored to the 2.2 state which is EB01?? Idk, thanks anways.
Oh ya for the future if I try do this again - would you suggest I stay away from ROM Manager for backing up, which I believe is what started this problem in the first place? It seemed like ODIN did a fine job of managing my OS. Any thoughts? Thankss!!
mattjac1 said:
Yes it worked!! Thank you so much! I would buy you a round at the ale house if I could!
After running EB01 it worked (with the pit file going all the way back to factory settings). So I'm not sure what this means - maybe since it was after upgrading to 2.2 that my phone bugged out, it could only be restored to the 2.2 state which is EB01?? Idk, thanks anways.
Oh ya for the future if I try do this again - would you suggest I stay away from ROM Manager for backing up, which I believe is what started this problem in the first place? It seemed like ODIN did a fine job of managing my OS. Any thoughts? Thankss!!
Click to expand...
Click to collapse
Definately stay away from rom manager cwm if you have the voodoo lagfix enabled, but since all the new fascinate roms are edify scripted, flashing through cwm in rom manager would be ok.
Sent from my Froyo'd Evil Fascinate full of PB&J

Categories

Resources