Related
So I was running 2.1 Fusion and I installed Voodoo via OCLF and I then tried flashing over it without disabling voodooo. However, I am able to get into cwm and i flashed a voodoo-disable.zip i keep handy in there, no help.
My phone won't reboot, I've ODIN'd and I get an error saying "WIPE DATA FAILED" in big red letters, it shows the S bootup animation however it doesn't fully bootup. I can access Download mode and CWM recovery menus but I can't restore anything it just doesn't boot up... What should I do??? I NEED to use my phone!!!
Helpppppp!!!!11
Do you have adb installed?
Sent from my T-Mobile G2 using XDA App
shaynesaw said:
Do you have adb installed?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
nooo i don't....
ANYBODY??? What would re-partition do if i set it on ODIN?
bobbbb said:
ANYBODY??? What would re-partition do if i set it on ODIN?
Click to expand...
Click to collapse
Yea repartition, use this odin image also. Worked good for me.
GTO777 said:
Yea repartition, use this odin image also. Worked good for me.
Click to expand...
Click to collapse
I checked Repartition with another odin image I found, it's the one i've always used and it always works, and it still doesn't boot... i have the bottom four buttons lighting up but that's it, nothing booots
I odind that image from your link but it takes me into recovery and there it says cannot verify whole-signature and i still can't reboot...
bobbbb said:
I odind that image from your link but it takes me into recovery and there it says cannot verify whole-signature and i still can't reboot...
Click to expand...
Click to collapse
well if you cant get it to work in ODIN, neither will Samsung most likely. Hope you have insurance IM KIDDING!
What ports is it?
itskohler said:
well if you cant get it to work in ODIN, neither will Samsung most likely. Hope you have insurance IM KIDDING!
What ports is it?
Click to expand...
Click to collapse
I'm not sure what you mean http://media.xda-developers.com/images/smilies/frown.gif but I'm coming from Fusion 2.1 on Galaxy S vibrant...
Whenever I try to odin with that 2.2 image it says cannot in stall update.zip (because i have taken out my sd card) HELP!!!! fmlllll
So i tried the odin 2.2 image with my sd card in and i checked re-partition and it goes to the recovery where it gives me this:
E: Can't mount /dev/block/mmcblk0p2
(Invalid argument)
E: copy_data_default_apk: Can't mount DBDATA:\\E: failed to open/mnt/internal_sd?update.zip
(No such file or directory)
E: signature verification failed
installation aborted
how i do fix my baby????
My p hone boots to the point where the colorful S appears but then it blinks a few seconds and goes black, and i can't turn the phone back on...
No one can save my ass
you can't turn it anymore? even when charging?
iynfynity said:
you can't turn it anymore? even when charging?
Click to expand...
Click to collapse
No... My phone can turn on, get into recovery and get into download mode, but whenever I odin it boots up the S animation then just goes to a black screen. I can't access cwm recovery because i don't have the update.zip, how can I push a ROM to my sd card using ADB, because that's what I think I'll have to do....
have you tried flashing froyo that doesnt brick?
as long there's ODIN and the never failing download mode, vibrant will always comeback from a brick.
bobbbb said:
No... My phone can turn on, get into recovery and get into download mode, but whenever I odin it boots up the S animation then just goes to a black screen. I can't access cwm recovery because i don't have the update.zip, how can I push a ROM to my sd card using ADB, because that's what I think I'll have to do....
Click to expand...
Click to collapse
as long as it's turning on you will be able to fix it. Try to download another stock .tar file then use a pit file. if not try Eugene's Froyo that doesn't brick that wipes everything.
xtone said:
have you tried flashing froyo that doesnt brick?
as long there's ODIN and the never failing download mode, vibrant will always comeback from a brick.
Click to expand...
Click to collapse
Im coming from a 2.1 build can i still dl the froyo that doesn't brick? Even if I don't have ADB, or the cwm or update.zip on my internal sd card?
Sell it to me...just kidding...try to download a 2.1 image file.,maybe that'll work.
Edit: search for the mirror file thread on the development section. Scroll down to the odin section and d/l the newest 2.1 leak img file. Try to flash that with odin. They have the latest update.zip over there that you can d/l.
bobbbb said:
Im coming from a 2.1 build can i still dl the froyo that doesn't brick? Even if I don't have ADB, or the cwm or update.zip on my internal sd card?
Click to expand...
Click to collapse
Sent from my GT-I9000 using XDA App
so i tried to install the simply galaxy 3.0 n it went into a bootloop and made crazy noises and colors every time it tried to boot. so i flashed ji6 through odin and no it will only boot to recovery. any help please?
tjhill01 said:
so i tried to install the simply galaxy 3.0 n it went into a bootloop and made crazy noises and colors every time it tried to boot. so i flashed ji6 through odin and no it will only boot to recovery. any help please?
Click to expand...
Click to collapse
Did you do a nandroid back up?
Try this
1 Flash just the .tar and check only auto reboot and F. Reset time
2 when it boots up and gives you an error in recover thats fine!
3 pull battery and put it into download mode again
4 flash a JFD tar with the 512 pit and check re partition, auto reboot, f reset time, phone efs clear, and phone bootloader update.
5 when it finishes let it sit for about 15 minutes and boot, and you should be back to stock, then you can root and away you go with your favorite rom!
Let me know if this works
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
My phone crashed this morning after running the daily OMFGB from the 31st for a few days. I tried to restart, it won't go past the Glitch Kernel screen. When I go into recovery, I am greeted with this message:
ClockwordMod Recovery v4.0.1.0
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
wiping data, did not help. reflashing the rom and kernel did not help. I still can't start the phone. What are the steps I need to take to fix this as I am currently not able to use my phone at all.
alemondemon said:
My phone crashed this morning after running the daily OMFGB from the 31st for a few days. I tried to restart, it won't go past the Glitch Kernel screen. When I go into recovery, I am greeted with this message:
ClockwordMod Recovery v4.0.1.0
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
wiping data, did not help. reflashing the rom and kernel did not help. I still can't start the phone. What are the steps I need to take to fix this as I am currently not able to use my phone at all.
Click to expand...
Click to collapse
Same thing happened to me yesterday..the only way I got my phone working again was to odin eb01 with the atlas 2.2..reboot fully...I then tried to go back to cm7 and got the same message and the only way I was about to fix it was to flash the com rom 2.0 obviously wipe everything before..let that boot and tried to flash cm7 with the recovery from com rom....still same message...i had to odin otb3.x.x.recovery... Download times infinity's recovery zip and flash that in otb recovery, then reboot recovery so I had ti's purple recovery...wipe everything and flash cm7...and success! I used the 7/17 build cause I didn't want nightly then rebooted from power button menu and flashed glitch and gapps.
Sent from my SCH-I500 using XDA App
Oh my goodness, sounds like something is really busted. Do you think it is OMFGB related? Yikes.
I have same thing, but I cant get the phone to show in download mode to odin anything
Same here. I'm now stuck in a boot loop. I can't even restore a backup.
Edit: Just tried to do a restore and the MD5 Sums don't match. I've had to do Odin reset three times today.
I think I might do Vodoo and try to restore that way. I will report back.
alemondemon said:
Oh my goodness, sounds like something is really busted. Do you think it is OMFGB related? Yikes.
Click to expand...
Click to collapse
No I don't think its omfgb related cause I've never ran that rom but I do think it has something to do with all the different recoveries we have floating around and so many different builds with different formats things are bound to get screwed up...my problem came from forgetting to wipe before flashing a different kernel and got me stuck in a boot loop.
Sent from my SCH-I500 using XDA App
I've had this problem ever since I got my Fascinate and tried to get CM7 on it. (2 days ago) I was always able to flash new builds just fine if I managed to get into the orange recovery and not the CM7 one. I believe the one I used was the one on ROM Manager.
This is kinda upsetting...
Hyphnx said:
Same here. I'm now stuck in a boot loop. I can't even restore a backup.
Click to expand...
Click to collapse
Its not the quickest but it should get you back...odin eb01 with the atlas 2.2pit...and reboot. Then odin recovery boot immediately to recovery via 3 finger salute...wipe everything and flash the rom you want...I've had good luck with cwm 3-30 fix all or otb 3x.x.x....if you want to go to cm7 odin the fixed recovery in jt's post and flash cm7 from that recovery....the sticky in the dev section...going from cm7/miui/gb to any other rom should give you some good info and instructions
Sent from my SCH-I500 using XDA App
efan450 said:
Its not the quickest but it should get you back...odin eb01 with the atlas 2.2pit...and reboot. Then odin recovery boot immediately to recovery via 3 finger salute...wipe everything and flash the rom you want...I've had good luck with cwm 3-30 fix all or otb 3x.x.x....if you want to go to cm7 odin the fixed recovery in jt's post and flash cm7 from that recovery....the sticky in the dev section...going from cm7/miui/gb to any other rom should give you some good info and instructions
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
We are having problems with the recovery he posted in his post.
Tried CWM-Recovery-All, turned my phone into muffed up phone. UGH!
Sorry for the double post. I've had to Odin 2 more times which makes it a total of 5 today. I used all the recoveries that are available. One at a time and they all end in the same way.
Hyphnx said:
Sorry for the double post. I've had to Odin 2 more times which makes it a total of 5 today. I used all the recoveries that are available. One at a time and they all end in the same way.
Click to expand...
Click to collapse
So what rom are you running now?
Sent from my SCH-I500 using XDA App
efan450 said:
Same thing happened to me yesterday..the only way I got my phone working again was to odin eb01 with the atlas 2.2..reboot fully...I then tried to go back to cm7 and got the same message and the only way I was about to fix it was to flash the com rom 2.0 obviously wipe everything before..let that boot and tried to flash cm7 with the recovery from com rom....still same message...i had to odin otb3.x.x.recovery... Download times infinity's recovery zip and flash that in otb recovery, then reboot recovery so I had ti's purple recovery...wipe everything and flash cm7...and success! I used the 7/17 build cause I didn't want nightly then rebooted from power button menu and flashed glitch and gapps.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
".i had to odin otb3.x.x.recovery... Download times infinity's recovery zip and flash that in otb recovery"
can you link to that? Is it the voodoo one form here:
http://forum.xda-developers.com/showthread.php?t=1046905
and which is the recovery zip that u flashed from otb recovery? can you link to them, i don't wanna screw this up any more than i already have.
alemondemon said:
".i had to odin otb3.x.x.recovery... Download times infinity's recovery zip and flash that in otb recovery"
can you link to that? Is it the voodoo one form here:
http://forum.xda-developers.com/showthread.php?t=1046905
and which is the recovery zip that u flashed from otb recovery? can you link to them, i don't wanna screw this up any more than i already have.
Click to expand...
Click to collapse
Yup...boot into the otb 3x.x.x recovery and flash the times infinity.zip and then select reboot recovery while in cwm and it should go from the otb one to the times infinity one...at that point wipe everything and flash cm7 build 7/17..not the nightly....once your on the mtd build you can flash the nightly if you wanted
From the power button menu
Sent from my SCH-I500 using XDA App
Edit: I suppose you could just odin times infinity's recovery...I just happened to have the zip on my sd handy so thats why I did it that way...it was that recovery that worked so you could odin it if you wanted it's in the link you posted try flashing it from ti's recovery..I just got there a little differently
Any suggestions if you cant get odin to recognize the phone? Ive tried three Win7 machines both x86 and x64 and three different cables...ALL of them say unknown device. Ive tried pointing to both the Sammy drivers and the nexus ones with no luck.
My phone was revived by simply doing the atlas odin method. I then flashed a fully rooted image...and from there on it's child's play. With that said, I can't get into download mode now, to odin things. What could be causing that? Not, very urgent, because at the moment the phone is running like it should
Thanks so much!
OK so I copied infinity times cwm red to phone and applied that. I still got message about cache. I ran the cwm4 from recovery and now Im back to square one again. I can try to install a ROM, but it boot loops everytime. Can my phone be revived w/o odin? Do I need an updated update.zip file?
humblewarfare said:
OK so I copied infinity times cwm red to phone and applied that. I still got message about cache. I ran the cwm4 from recovery and now Im back to square one again. I can try to install a ROM, but it boot loops everytime. Can my phone be revived w/o odin? Do I need an updated update.zip file?
Click to expand...
Click to collapse
unfortunately a boot loop normally requires odin...use the eb01 tar and the atlas 2.2pit and your phone will be back up and running
From there I would flash com rom and reboot then if you wanna take a stab at cm7...try and flash it with the com rom recovery...if it doesn't work you can just try odin'ing different recoveries as long as you don't let the phone boot fully you can simply pull the battery and try to odin a different recovery.try the one from com rom, the 3-30 fix all, ti's recovery, or jt's fixed recovery...I don't know where I got the file but I also have a recovery named fixed 3 x.x for cm7 but I came remember where I got it.it is important that you let eb01 sit for a few minutes after booting and also let com rom sit for a few minutes after flashing also...I just skipped all the setup stuff to get the main screen and then pulled the battery and started flashing
Sent from my SCH-I500 using XDA App
humblewarfare said:
Any suggestions if you cant get odin to recognize the phone? Ive tried three Win7 machines both x86 and x64 and three different cables...ALL of them say unknown device. Ive tried pointing to both the Sammy drivers and the nexus ones with no luck.
Click to expand...
Click to collapse
I'm running vista home edition...if it matters and I'm using odin v.1.7 try the samsung generic drivers also.but once I'm on cm7 my pc says it doesn't recognize my phone but if I put it in download mode and hook up odin recognizes it...so I'm not sure on that one
Sent from my SCH-I500 using XDA App
alemondemon said:
My phone was revived by simply doing the atlas odin method. I then flashed a fully rooted image...and from there on it's child's play. With that said, I can't get into download mode now, to odin things. What could be causing that? Not, very urgent, because at the moment the phone is running like it should
Thanks so much!
Click to expand...
Click to collapse
Try holding the down button while you plug into your wall charger then just move it to your pc...if that doesn't work...clean the contacts with rubbing alcohol...with the phone off.at worse case there is a jig you can manually force download mode...you can buy or make them
Sent from my SCH-I500 using XDA App
Okay, as the thread title states and as I had searched for a Samsung Vibrant related thread about this issue I haven't found any. My issue as stands is when I try to perform a Factory Data Reset on my Samsung Vibrant t959VUVKD1, 2.2.1 Froyo, it only comes up with this set of words on the recovery screen.
-- Wiping data...
Formatting DATA:...
Data wipe failed.
Formatting CACHE:...
Formatting DBDATA:...
Db data wipe Failed.
-- Appling Multi-CSC...
Installing Multi-CSC
Install default apk;files, please wait
E: Can't mount /dev/block/mmcblk0p2
(No such file or directory)
E:copy_data_default_apk:Can't mount DATA:
your storage not prepared yet, please use UI menu for format and reboot actions.
Click to expand...
Click to collapse
So, as one can see this is evidence of my attempt at rooting and using Clockworkmod Recovery.
What I used was SuperOneClick 2.2 and successfully rooted my phone but then I decided to unroot after finding out ClockworkMod Recovery wasn't able to create a backup on my phone, also, I used a 3e_recovery_installer batch file I found somewhere which managed to unlock my Android system recovery so I could get into Clockworkmod Recovery but ever since I unrooted and uninstalled Clockworkmod Recovery it won't allow me to perform a factory data reset. I was able to do it TWICE after unrooting my phone but now I can't perform the factory data reset and I do not understand why.
Have you tried to odin back to stock or use the toolbox?
http://forum.xda-developers.com/showthread.php?t=954509
Never used Odin or Toolbox before because I've never found a concrete tutorial on how to correctly flash/root my vibrant. I would like to flash but I just don't feel safe about it even though I had downloaded a supposedly stock rom of the UKVD1 rom for Vibrant.
nomadrider123 said:
Have you tried to odin back to stock or use the toolbox?
http://forum.xda-developers.com/showthread.php?t=954509
Click to expand...
Click to collapse
Erm, I used the Toolbox to use "Flash to Stock" and when Odin opened up I selected Pit.pit and it showed a yellow to green color on the first box and my phone turns off then nothing happens. What does this mean?
1. When odin opens select pit
2.click the Pit.pit file after screen change and click open
3.You should be returned to odin main.
4. click pda
5.click pda file and click open.
6.you are returned to main odin.
7.set phone down, click start and do not unplugg
8 let it run till pass, and auto reboot
Sugartibbs said:
1. When odin opens select pit
2.click the Pit.pit file after screen change and click open
3.You should be returned to odin main.
4. click pda
5.click pda file and click open.
6.you are returned to main odin.
7.set phone down, click start and do not unplugg
8 let it run till pass, and auto reboot
Click to expand...
Click to collapse
I did all that just now but now I'm stuck on a looping charging screen or a looping Samsung Vibrant screen. However, this isn't the same as the original T-Mobile screen and even so how do I get past the looping screen?
1. pull the battery
2. insert the battery
3.hold down volumeup/ volumedown buttons
4. insert the usb cable, you should enter download.
5 reset toolbox and select flash to stock, odin should appear,
My experience.
When you are facing boot loop, it's very hard to get in to download mode.
I tried button trick for download mode, but I failed.
So I used adb and tried to reboot into download mode by command.
I repeated it until I could get into the mode.
Anyway, download Toolbox and once u get into the mode,
try to go back to stock. That 'll fix everything.
I also know that the logo changed after I flashed back to stock.
I faced I9000 logo which wasn't before.
FYI: + the version will be eclair, and I couldn't get the official update.
Anyway good luck.
---------- Post added at 03:09 AM ---------- Previous post was at 03:02 AM ----------
If you never get into download mode.. Try to use JIG.
Another way is to disassembly your phone and do something.
I suggest you buy a JIG.
Problem is, I can easily get into Download mode by:
1. Remove USB Cable
2. Pull battery and re-insert
3. Plug in USB cable
4. Hold Volume - and +
And it's in Download mode
But I want to get the original Smasung Vibrant 2.2.1 UVKD1 Rom back on but it appears the provided files aren't it?
Btw, what is a Pit and and PDA file supposed to be, I'm a complete noob at this point.
The pit and pda files in aio toolbox are the stock rom the vibrant is shipped with, if you want anythig else on it you have to download it and flash it through odin, rom manager, or cwm.
Sugartibbs said:
The pit and pda files in aio toolbox are the stock rom the vibrant is shipped with, if you want anythig else on it you have to download it and flash it through odin, rom manager, or cwm.
Click to expand...
Click to collapse
I see. But now when the phone starts up it shows a buncha dots in consecutive order to the Samsung Vibrant screen after I flashed to stock using the pit and pda files and it just loops continuously until I pull the battery. Is there anything that can be done to get past the looping?
Does the pitcure look like a phone....!....computer? If so then you are softbricked and just get back in download mode and re-Odin, but make sure that when you Odin, you DO NOT have the repartition checked. Probably what happened.
If it is not the above, can you get into recovery? Can you now do a factory reset? Wipe cache, dalvik and reset usually clears the bootloop problem.
Woodrube said:
Does the pitcure look like a phone....!....computer? If so then you are softbricked and just get back in download mode and re-Odin, but make sure that when you Odin, you DO NOT have the repartition checked. Probably what happened.
If it is not the above, can you get into recovery? Can you now do a factory reset? Wipe cache, dalvik and reset usually clears the bootloop problem.
Click to expand...
Click to collapse
Unfortunately I can't get into recovery. I also Odin'd with the given Pit.pit and PDA.tar files with Repartition unchecked but that didn't change anything.
I cant figure how you could be in a bootloop coming out of odin. Is the AIO you downloaded for vibrant. I think theres one for fascinate and captivate.
Sugartibbs said:
I cant figure how you could be in a bootloop coming out of odin. Is the AIO you downloaded for vibrant. I think theres one for fascinate and captivate.
Click to expand...
Click to collapse
I used the AIO Toolbar for Vibrant as provided by the link by the person earlier. The loop just continues forever and ever until I remove the battery.
The three button method of entering recovery hasnt worked?
You mean hold Power and Vol + and -?
No, it doesn't work.
i am hesitant to advise anything, the fact that factory reset didnt work, and recovery has been removed is troubling. when i get a fail message when flashing to stock ive used eugenes froyo that does not brick. If all else fails you might google it and read the op. Its a pda file used by odin.
What I find strange is that download mode works perfectly fine but nothing else.
what I find strange is coming out of odin and looping, you should come out in recovery with an error message. a cannot mount data or bdata. storage not ready. Removing recovery may have removed more than was expected. check the op on eugenes froyo you have to get back to stock.