Database Users

restore from ROM manager bricked my phone

I did a search and couldn't find much help.
I recently dropped my phone and the screen got a slight crack, so the insurance company sent me a new one.
I figured I'd use ROM manager to backup my old phone, and restore it on my new phone.
New phone restores, reboots, and gets stuck at the black Vibrant screen.
I can get back into recovery mode fine, but nothing seems to work.
I let it sit at the Vibrant screen for about an hour before I try again.
Its attempt 3 when I decided to come on this site for some help.
Specs:
Stock
Rooted
Launcher pro
Nothing too much to be confusing and brick, so wtf?
Oh and I understand I could use odin to reflash my phone, please please please don't suggest odin, because I don't own a PC, I own a mac. Please don't tell me to go out and buy a PC or to download a program that costs $50 to use PC programs on a mac. I could have told myself that kind of information.
HELP, my brand new phone is destroyed wahhhh

From the sound of it you still have your old phone. If so, rather than restore using nandroid, try downloading a copy of titanium backup to backup/restore your apps. I have found that sms restore does a good job restoring texts. For me those two apps get the job done restoring my info. Also, if you haven't, sync your contacts to google and they will auto sync upon load. Of course this all assumes you still have your old phone in working order. ..
Also, there are stock roms flashable via clockwork that basically do the same as odin. Check the ' bible' sticky for links.
Hope this helps
Sent from my SGH-T959 using XDA App

a400meter said:
From the sound of it you still have your old phone. If so, rather than restore using nandroid, try downloading a copy of titanium backup to backup/restore your apps. I have found that sms restore does a good job restoring texts. For me those two apps get the job done restoring my info. Also, if you haven't, sync your contacts to google and they will auto sync upon load. Of course this all assumes you still have your old phone in working order. ..
Also, there are stock roms flashable via clockwork that basically do the same as odin. Check the ' bible' sticky for links.
Hope this helps
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I still have my old phone in working order, but that doesn't help the fact that my new phone is stuck on bootup, and can only enter recovery mode...

yelowbottlecaps said:
I still have my old phone in working order, but that doesn't help the fact that my new phone is stuck on bootup, and can only enter recovery mode...
Click to expand...
Click to collapse
The only way I can think of that a nandroid restore would soft brick you, is because you have restored a version of android with a different kernel.
If the original phone had the original firmware (JFD), and the replacement had the most recent (JI6), this is what would be expected to happen.
Since you seem unable and unwilling to use Odin, your going to have to tell us more details (i.e. which versions of the firmware as related above were actually in play) before we can begin to help. If you don't know, well....
You can also simply take it back to a local T-Mobile store and do another swap, or you can find a friend with a Windows PC and Odin (or Samsung's Mini KIES with JI6). These are your only real options...

both phones had JI6
Thank you for the quick responses.
I'm not unwilling to use odin, but unless anyone knows of a free software to use PC programs on a mac, I'm SOL.

so, you got the new phone, rooted, got rom manager and then got clockwork recovery right?
You did a nandroid backup right (on the new phone), before flashing anything right?
Why not just download Fusion and flash that to get the phone up and running?

yelowbottlecaps said:
both phones had JI6
Thank you for the quick responses.
I'm not unwilling to use odin, but unless anyone knows of a free software to use PC programs on a mac, I'm SOL.
Click to expand...
Click to collapse
Well hmm....so much for guessing on my part. Crossing different build kernels is one sure fire way to brick...
Well, there is a solution for Mac and Linux for reloading firmware on a Samsung phone from Download Mode, an open project called Heimdall. It does everything Odin does, but without a GUI, so it depends on how comfortable you are with commandline/shell.
I'll pass you the relevant links so you can see for yourself what's going on.
[PROGRAM] Heimdall - Cross-Platform Open-Source Flashing Software (1.0.0 Available)
Heimdall's Website, with downloads...
XDA Dev Thread with JI6 Odin .tar file....
Best of luck!

s15274n said:
so, you got the new phone, rooted, got rom manager and then got clockwork recovery right?
You did a nandroid backup right (on the new phone), before flashing anything right?
Why not just download Fusion and flash that to get the phone up and running?
Click to expand...
Click to collapse
True that...Why didn't I think of that obvious ploy. If he can get into Recovery, and bounce over to clockwork...Well now's a good a time as any to try Bionix or Bionix Fusion...or a few other of the CW Recovery installable builds...Definitely easier than Heimdall or working out Odin on a mac....and definitely preferable to staring at a Vibrant logo...
{{facepalm}}

masterotaku said:
Well hmm....so much for guessing on my part. Crossing different build kernels is one sure fire way to brick...
Well, there is a solution for Mac and Linux for reloading firmware on a Samsung phone from Download Mode, an open project called Heimdall. It does everything Odin does, but without a GUI, so it depends on how comfortable you are with commandline/shell.
I'll pass you the relevant links so you can see for yourself what's going on.
Best of luck!
Click to expand...
Click to collapse
If there was a step by step walkthrough, I have no problem trying this out.
But I downloaded it and have no idea what I'm doing. Therefore, still SOL

^ are you? You didn't answer my questions.

I'm gonna guess and say you also dl'd the oclf from the market to root too... so now you can't get back into CwR... right?
If you can get adb to recognize your phone then your not SOL. Im not sure what the exact command lines would be but you could delete the update.zip and replace it with another ROM. GL

I just tried using Odin on my roommates PC. An error happened and now the phone is showing a picture of a phone, a couple dots, an exclamation mark, a couple dots, and a computer.
Nothing I can do is taking it out of this screen. Unplugged from computer, took out battery, took out sd card, put it back in... nothing
Am I bricked for good now?
This is a terrible day.

edit: i managed to be able to get the phone into download mode.

No you are not completely bricked! Honestly that is almost impossible on this phone. The only way you'll lose this phone is if YOU give up.
Just keep trying and take a few deep breathes. Take a break actually. Just redo the process from step one.
Edit: you're half way there. Just flash Eugene's froyo that doesn't brixk, reboot, flash JFD or JI6, reboot... then you'll be right back to out of the box status.

All~G1 said:
I'm gonna guess and say you also dl'd the oclf from the market to root too... so now you can't get back into CwR... right?
If you can get adb to recognize your phone then your not SOL. Im not sure what the exact command lines would be but you could delete the update.zip and replace it with another ROM. GL
Click to expand...
Click to collapse
If someone can back this up with some instructions that would be amazing.

All~G1 said:
No you are not completely bricked! Honestly that is almost impossible on this phone. The only way you'll lose this phone is if YOU give up.
Just keep trying and take a few deep breathes. Take a break actually. Just redo the process from step one.
Edit: you're half way there. Just flash Eugene's froyo that doesn't brixk, reboot, flash JFD or JI6, reboot... then you'll be right back to out of the box status.
Click to expand...
Click to collapse
Thank you for the motivation!

yelowbottlecaps said:
Thank you for the motivation!
Click to expand...
Click to collapse
No worries, we've all been there. It took me 6 hours lol. Best part is after you go through this once it will only take you 5-10 mins the next time. The hard part is just getting everything setup in the mist of anger, frustration, fear & panic.

All~G1 said:
No worries, we've all been there. It took me 6 hours lol. Best part is after you go through this once it will only take you 5-10 mins the next time. The hard part is just getting everything setup in the mist of anger, frustration, fear & panic.
Click to expand...
Click to collapse
and in the midst of a roommate that needs his pc back.
I still need a fix that would work for macs... if not, I'd have to wait for my roommate to let me bum his pc again

Do my posts not show up or something? wtf.

s15274n said:
Do my posts not show up or something? wtf.
Click to expand...
Click to collapse
/me pats s15274n on the back....don't get mad...get even! =P
Honestly, sounds like yelow's focusing on getting all the help s/he needs from All~G1. I wouldn't worry about it.
~SB

need serious help ASAP! Please!

Tonight I decided to mess with my phone. I flashed eugene's new r13 rom, got it working fantastic. Then. I decided to try a lagfix. I heard of one in the market so i searched and found an "unofficial" app that applied the voodoo lagfix. needless to say it messed up my phone big time. At first, it restarted and some voice said "converting partition........not enough space on partition." So reboot into recovery mode and to my surprise its a diff, voodoo, version of clockwork recovery. I look at the voodoo options, cant find anything. found the area to partition the sd card. I partition 512mb i believe with no sway (i think). phone restarts. freezes on galaxy S screen. try booting into recovery. will not work. tried 10 times. tried to reboot into recovery via adb, phone is recognized and reboots but doesnt get to recovery mode, just galaxy S screen then freezes. I have NO idea what to do! Please help!!! if i left out any info, please ask!!!

first restore back to stock via Odin.
second, root and install roms again.
third, use your newly working device to read the post about non-development stuff going in the Q&A section.

adb reboot download and use odin to flash back to stock (froyo or eclair) there are plenty of threads on how to do this method. Best of luck

Use ODIN to go back to stock. no?
Umm, calm down, i think you will be fine.
Although some people are going to scream at you for putting this in the developers section.
Can you get to download mode? Turn phone off, hold down volume up and volume down at the same time, but don't touch the power button. Then, with your usb cable connected to your computer, plug the usb into your phone, while still holding down the volume buttons.
If you can get to download, then can't you just put your phone back to stock using ODIN?
I'm not an expert, but I'm assuming that should work for you.
edit:
I just uploaded odin, and the tar and pit files you need to get back to stock JFD.
I found all these files in xda originally, but didn't feel like finding each thread individually, so uploaded them on sendspace for you, much faster than searching the forum for each of these.
ODIN latest version:
http://www.sendspace.com/file/o0ivp2
Pit file:
http://www.sendspace.com/file/j9ytb3
JFD tar file:
still uploading...will post soon. ...nevermind upload taking too long, found the download link providing by justanotherdev
http://www.justanotherdev.slackdev.com/T959UVJFD.tar
I'm not an expert, but maybe you should ask everyone else if it is safe to ODIN to stock once you have messed with a lagfix and partitions.
good luck

Sounds like a trip down the "odin" lane to JFD is in order for ya. Go to the vibrant bible sticky, grab odin 1.70 and the JFD stock ".tar" file. Follow the tutorial posted, should get you back up and running.
p.s. wrong section...
EDIT: This should help you out
http://forum.xda-developers.com/showthread.php?t=810130

SamsungVibrant said:
Umm, calm down, i think you will be fine.
Although some people are going to scream at you form putting this in the developers section.
Click to expand...
Click to collapse
Correct. I'm not going to scream, but it's generally bad for to post "help me help me" threads in the development section. Either post them in the appropriate ROM thread (in your case, the thread for R13) OR in the Q&A section. Otherwise, you'll get posts just like mine that probably wont be as nice.
As for your issue, you have a soft-brick. Download ODIN, download the correct PIT and TAR files, follow the instructions in the ODIN thread to flash to stock and start over. Thats the only way you're going to fix your phone at this point.

im sorry if i placed this thread in the wrong place, im kind of new here. Guys, i really appreciate the help! can someone point in the direction of how to use odin? I have literally no idea what it even looks like or how to install it.

Also check the bible
the Vibrant and gallagherm1993 guys are right, but when you have flashed 2.2 it is safer to use the disable voodoo lag first (may not work cause you are saying it some hack version) but I d go that way first then flash the eugenes froyo that does not brick.... no repartition (do not check that box) reboot back to recovery then flash back to stock when going back to stock, you do check the repartition...from there, you can do anything you want
There is in the 1st page a thread that has a complete zip but not the froyo that does not brick you will need to get that from the bible sticky
good luck

http://www.youtube.com/watch?v=uGMDycXJ2i0

wolf3142 said:
im sorry if i placed this thread in the wrong place, im kind of new here. Guys, i really appreciate the help! can someone point in the direction of how to use odin? I have literally no idea what it even looks like or how to install it.
Click to expand...
Click to collapse
hey wolf...look up a couple posts, i'm putting all the files you need there.

The only way to fix this is to use odin. Are you familiar with odin? You better be! Since you played with VooDoo without really knowing what you got yourself into, you need to do this.
You will lose all of your data!
First ODIN Eugenes froyo that doesnt brick. Search for it here on xda. Get used to using the search feature. Then after that you can odin back to jfd and work from there. If you read enough, there are ways to work through this. Good luck and if you still dont get it, PM me.

what is the point of eugenes froyo that doesn't brick?
jdkackley said:
The only way to fix this is to use odin. Are you familiar with odin? You better be! Since you played with VooDoo without really knowing what you got yourself into, you need to do this.
You will lose all of your data!
First ODIN Eugenes froyo that doesnt brick. Search for it here on xda. Get used to using the search feature. Then after that you can odin back to jfd and work from there. If you read enough, there are ways to work through this. Good luck and if you still dont get it, PM me.
Click to expand...
Click to collapse
Why does he need "eugenes froyo that doesn't brick" ???
I was Running Axura 2.0.5, and used ODIN today to go straight to stock JFD.
Then I flashed the leaked JK6 froyo.
what is the point of "eugenes froyo that doesn't brick" ?

if you flash a rom without disabling voodoo, the partition stays as ext4 eugene's froyo that does not brick reformats that partition. JFD doesnt work the same way.

Follow this guide, if it doesnt work look at the other tutorials in the BIBLE section in Development.
Follow exactly no skipping steps.
http://forum.xda-developers.com/showthread.php?t=799105

byt3b0mb said:
if you flash a rom without disabling voodoo, the partition stays as ext4 eugene's froyo that does not brick reformats that partition. JFD doesnt work the same way.
Click to expand...
Click to collapse
Ohhh I get it. So people who f*cked up their partition or messed around with a lagfix, should use eugenes froyo that doesn't brick first. BTW eugene seems to have pulled everything off xda, I can't find that in the search.

Your phone is totally dead... give you $20 for it.

I'm all for lending a helping hand, and it's clear that all the relevant information has already been posted, but it still amazes me how often people will attempt to modify their device without doing their homework first and then freak out when things go awry.
I know I've f-ed up my phones plenty of times either by bad builds or not paying attention to details, but I've never thought the best fix would be to start a new thread on a forum under the assumption that I'm the first to have this problem or to avoid having to search for a resolution.
We all start somewhere and are always learning as we experiment with new tricks, but jeebus cripes people, why would you install something risky without having a backup plan in case something goes wrong?
Ah well, whatever. Sorry for a useless response.

SamsungVibrant said:
Ohhh I get it. So people who f*cked up their partition or messed around with a lagfix, should use eugenes froyo that doesn't brick first. BTW eugene seems to have pulled everything off xda, I can't find that in the search.
Click to expand...
Click to collapse
if you need eugene's stuff go to his forum located here
Froyo that doesn't brick is under vibrant android development.

[Q] Installed rom now phone is broke

Today I installed my first rom, it was called dl09_supah_clean_04. That worked ok but I could not receive text messages. I thought maybe I'd try another rom. So I downloaded one called hamsters rom. Once I booted the phone up with that rom I got a bunch of errors. So I restarted and now get nothing but the samsung logo flashing. I go into recovery mode, click on update.zip to load clockwork recovery and get a message saying:
e:can't mount /dev/block/vold/179:9
(no such file or directory)
e:can't mount sdcard:update.zip
Installation aborted
I'm just wondering if I am screwed here. I'm about to plug the sdcard into my computer and copy update.zip again in hopes of getting clockwork recovery to work.... just wondering if anyone has any ideas in case this doesn't work.

You need to put it on the phones internal sd card plus sometimes you need to put text message setting yourself like message centres number .
Sent from my GT-I9000 using XDA App

Is this a troll?
mdisaac said:
Today I installed my first rom, it was called dl09_supah_clean_04. That worked ok but I could not receive text messages.
Click to expand...
Click to collapse
That's because you have to install a DL09 kernel and modem as well.
I thought maybe I'd try another rom. So I downloaded one called hamsters rom.
Click to expand...
Click to collapse
How clueless are you?
That's a i9000 ROM. Or Captivate port.
Every single flashing thread warns
DO NOT FLASH ANYTHING NOT SPECIFICALLY FOR THE VERIZON FASCINATE
You flashed a GSM ROM onto a CDMA phone. That's just asking for a brick.
Now download this (and since you can't figure obvious things out, flash it into *PDA* of Odin, NOT NOT NOT NOT NOT "phone"), and pray it works.

THANK YOU, THANK YOU, THANK YOU!!
My phone is back and working on the stock rom. I am definitely clueless when it comes to this but I am not giving up. I am going to get the dl09_supah_clean_04 rom working. I'll be more careful this time though.
Thanks again!
s44 said:
Is this a troll?
That's because you have to install a DL09 kernel and modem as well.
How clueless are you?
That's a i9000 ROM. Or Captivate port.
Every single flashing thread warns
DO NOT FLASH ANYTHING NOT SPECIFICALLY FOR THE VERIZON FASCINATE
You flashed a GSM ROM onto a CDMA phone. That's just asking for a brick.
Now download this (and since you can't figure obvious things out, flash it into *PDA* of Odin, NOT NOT NOT NOT NOT "phone"), and pray it works.
Click to expand...
Click to collapse

not trying to be a d!ck but, you really need to stop before you do brick your phone. read, read, and read some more. its clear you dont understand what your doing and are going to end up screwing up even worse. read EVERYTHING dealing with ONLY the VZN fascinate. if it says anything other that VZN fascinate DO NOT READ IT. your in to big of a hurry and will brick your phone. hell, i have been hacking phones for years and am still not comfortable with android yet. i have rooted but not installed a rom because i dont want to mess it up. hell, i havent even done the new update from VZN. im waiting for more reports to come in. just take your time and read, then worry about flashing to another rom.

If you mess your phone up just use odin and the official stock DL09.md5 to return the phone to normal. Easy.

mdisaac said:
Today I installed my first rom, it was called dl09_supah_clean_04. That worked ok but I could not receive text messages. I thought maybe I'd try another rom. So I downloaded one called hamsters rom. Once I booted the phone up with that rom I got a bunch of errors. So I restarted and now get nothing but the samsung logo flashing. I go into recovery mode, click on update.zip to load clockwork recovery and get a message saying:
e:can't mount /dev/block/vold/179:9
(no such file or directory)
e:can't mount sdcard:update.zip
Installation aborted
I'm just wondering if I am screwed here. I'm about to plug the sdcard into my computer and copy update.zip again in hopes of getting clockwork recovery to work.... just wondering if anyone has any ideas in case this doesn't work.
Click to expand...
Click to collapse
You also need to odin the DL09 modem. or SMS and other things WILL be broken.

1.4hitachi said:
If you mess your phone up just use odin and the official stock DL09.md5 to return the phone to normal. Easy.
Click to expand...
Click to collapse
When people take Odin for granted, they end up with bricks.

Odin can be your friend...as long as you use PDA and not Phone...which is counter intuitive

adrynalyne said:
When people take Odin for granted, they end up with bricks.
Click to expand...
Click to collapse
Shouldn't you say, 'when people use Odin incorrectly"? I mean, as long as he follows the instructions and un-does and kernel changes beforehand the device will be returned back to stock. Also with the official DL09.md5 package it has inside all necessary operating parts. It sounds to me like all he did was attempt a rom flash twice. Odin with the "offical" DL09.md5 will return his Fascinate to stock.

Thanks everybody! I got back to stock and let phone receive the ota update of DL09. Figured that would take care of the kernel and modem and I could install dl09_supah_clean_04. Worked like a champ. I think I learned a lot in this process as well... time will tell.

[Q] Samsung Epic Stuck at Boot Screen, no access whatsoever.

I've been scared to make a thread for my problem cause I know how much you all hate that when there's another thread with the answer. However, I've been getting lost in links and threads for hours with now results and no actual help. If there's a thread for my exact problem please post the link or redirect me.
What I did:
I had a STOCK EC05 on my Epic. I had rooted it about a week ago using the method presented here:http://forum.xda-developers.com/showthread.php?t=808103
I had to use MAC method, cause my laptop won't charge so I had no other choice. It worked, except I had no CWM. Then today, I wanted the CWM so I repeated what I did and I finally got CWM, it was CWM 2.X. After that I decided to take it a step further and tried flashing Syndicate 1.1 Frozen ROM. It looked like it worked, I wiped everything beforehand like I'm supposed to.
Ok, now my problem is, it's stuck on the Samsung boot screen after it rebooted itself. I can't do anything with it. It only responds to the power button and a charger.I can't get into CWM, it'll turn on with the power button but can only turn it off by pulling the battery. Also, When I plug in the cord it tries to bring up the battery picture but just freezes with the little circling circles in the middle of the battery, and it won't recognize on my computer.
I can't find any links or threads that have the answer I'm searching for, especially since I'm on a MAC OSX 10.6.7. If It's best I use a PC then I could gain access to one. Any help is appreciated. and like I said, if there's already an answer posted then I probably missed it, and I apologize.

What you did wrong was root with 2.x, which kept you with an rfs filesystem and then you flashed an ext4 filesystem rom. To flash an ext4 rom you need to root with 3.x. if you can't get back to stock, and you're on mac you'll probably need to use heimdall since I don't think odin works with mac. Hopefully somone can give u more info on heimdall cuz I'm not familiar with it.
Sent from my SPH-D700 using XDA App

Try turning on your phone by holding the 1 key on the keyboard and the power button. If that brings you to the download screen you can use hemidal on mac or odin on pc to restore your phone.
Sent from my SPH-D700 using XDA App

Use the TAR located here to fix your phone. Download the CMW 3.0.0.6 version.
---> http://forum.xda-developers.com/showthread.php?t=1061912
I'm assuming Hemidal is the same as ODIN but MAC version.
So just Flash that tar with hemidal. (make sure to boot phone while holding "1" on slideout keyboard.)
Then after you let it boot, you can go into CMW, (let it EXT4 itself) then you can install SRF 1.1 =D )

The "1" on the keyboard...OMFG, Thank you!!! I'm so happy to see something else other than that Samsung screen, YES! Ok, my hope has been renewed. Thanks to all of you. I never even heard of Heimdall till now...I'll get to work on it now
EDIT:Ok, I had spent 12 hours straight figuring everything out. Finally, as I was LITERALLY about to give up hope, I had used Odin on my on my Laptop. I found a PIT and used the TAR that Shoulon suggested. Finally worked. It's miraculous that I had just so happened to receive my new charger for my laptop, because nothing was working for me on my Mac. Thanks to you all for the assistance.

Vibrant stuck on boot loop

My vibrant is stuck on a boot loop, i was in the middle of installing ics and now it is in a boot loop. What can i do, if you want i can post of video of this boot loop for any advice.

lovenokia said:
My vibrant is stuck on a boot loop, i was in the middle of installing ics and now it is in a boot loop. What can i do, if you want i can post of video of this boot loop for any advice.
Click to expand...
Click to collapse
Just because you didn't care to read ANY of the stickies around... I'll make sure you do, i'll give you instructions but lets see if you can go back a page and click the stickies to learn how to do all of this:
you will need to get into download mode, and odin - this is the safest and recommended route
if you want to take a bit of a risk you can try to go into recovery and flash the ROM you were in before - this can lead to more bootloops/brick

here is the video
http://www.youtube.com/watch?v=cwNzHqezAuU&feature=youtu.be

If only there was a guide that explained what to do when you get a bootloop while installing ICS. Hmmm. (Hint: see my sig).
If that doesn't work, rider's is the way to go.
Edit:: saw that you posted your video. That is a fast ass bootloop. Hit your thanks button by accident. Anyways try pulling your battery and booting into recovery and reflashing ICS again over itself. Did you wipe and factory reset?

i am a dumbass that followed a youtube video tutorial congratulations to me(pissed >(, i went straight from eclair to ics. wopdee do. I got odin in a ".rar" file and cant open it, but i prob have the wrong odin then right?

Not sure about your Odin file but check my guide for clear instructions. Need to go from 2.1 to CM7 to ICS flavor.

Alright i am lost and pissed? what should i do now, (i did my touchpad just fine to ics) to let you know that i am not a complete n00b about this, but the vibrant is not liking me...

ok, now that i've seen the video this is not any normal BOOT LOOP.
What exactly did you do to get this? Which flashing procedures did you look at?
Can you at all get into recovery/download mode?* most important question*
Do you have Froyo Bootloaders or GB bootloaders? (if you don't know what these are and have not messed with bootloaders you are on Froyo.)
I have just read what the recovery says through the video
It pretty much says that it is trying to flash ICS PASSION, but it cannot because your sdcard is either a) wiped b) not mounted c) the ICS PASSION file is corrupted and/or ics passion has been deleted somehow.
-after reading some latest posts from you, i'm sorry for making you feel like a dumbass but you did not read the instructions, mainly the stickies, and did not follow the instructions on how to get to ICS from eclair. That is why. Many do not and I prefer not to give any help at all to people who can't help themselves, but I understand your situation and i'll try to help. Sorry for offending you if I did, its just that some people need to be treated that way so they open their eyes and start reading around.

i understand that, but i did a battery pull and the samsung vibrant is still doing the same thing, when i hold power and volume down it stays at the "vibrant" thing but that is it, i can do anything else but watch it boot loop.

okay, i did a wipe on my sd card before installing, let me try to find the youtube guide

here is the guide that i followed, i just went from step three onward because it was rooted but nothing else
http://www.youtube.com/watch?v=iryi3TzylN4

Rider, see if you can help him out. My boy just woke up. Let me get him back to sleep and ill be back after these messages.
PS I just PM'd him the CM7 Rom.

thanks, i hope someone can help me out.

lovenokia said:
thanks, i hope someone can help me out.
Click to expand...
Click to collapse
read this post, i think you missed it, answer the questions while i watch the video guide and see if theres anything wrong in there.
xriderx66 said:
ok, now that i've seen the video this is not any normal BOOT LOOP.
What exactly did you do to get this? Which flashing procedures did you look at?
Can you at all get into recovery/download mode?* most important question*
Do you have Froyo Bootloaders or GB bootloaders? (if you don't know what these are and have not messed with bootloaders you are on Froyo.)
I have just read what the recovery says through the video
It pretty much says that it is trying to flash ICS PASSION, but it cannot because your sdcard is either a) wiped b) not mounted c) the ICS PASSION file is corrupted and/or ics passion has been deleted somehow.
-after reading some latest posts from you, i'm sorry for making you feel like a dumbass but you did not read the instructions, mainly the stickies, and did not follow the instructions on how to get to ICS from eclair. That is why. Many do not and I prefer not to give any help at all to people who can't help themselves, but I understand your situation and i'll try to help. Sorry for offending you if I did, its just that some people need to be treated that way so they open their eyes and start reading around.
Click to expand...
Click to collapse
----
Okay..... so after watching that guide. I have never seen ANYONE using that method, mainly because he didn't flash ANY kind of CM7 kernel etc.
Most of his instructions were right, but he just did something on his phone that seemed unusual, but i guess worked for him...

xriderx66 said:
ok, now that i've seen the video this is not any normal BOOT LOOP.
What exactly did you do to get this? Which flashing procedures did you look at?
Can you at all get into recovery/download mode?* most important question*
Do you have Froyo Bootloaders or GB bootloaders? (if you don't know what these are and have not messed with bootloaders you are on Froyo.)
I have just read what the recovery says through the video
It pretty much says that it is trying to flash ICS PASSION, but it cannot because your sdcard is either a) wiped b) not mounted c) the ICS PASSION file is corrupted and/or ics passion has been deleted somehow.
-after reading some latest posts from you, i'm sorry for making you feel like a dumbass but you did not read the instructions, mainly the stickies, and did not follow the instructions on how to get to ICS from eclair. That is why. Many do not and I prefer not to give any help at all to people who can't help themselves, but I understand your situation and i'll try to help. Sorry for offending you if I did, its just that some people need to be treated that way so they open their eyes and start reading around.
Click to expand...
Click to collapse
no i cant get into recovery mode
i did not mess with any bootloaders
i wiped, unmounted as in not plugged in then yes, i installed zip from phone unmounted

Dude that video is wack. He pirates one version of CWR but once it boots up is a completely different version. Check out the numbers on top. The edits are terrible. Cuts out some pretty huge points. Plus he starts out with Passion beta 1 on his settings screen before he edits back to show you how to do it, but ends up with RC1.

so am i screwed? if i am than thanks for trying to help me though.

No you are not screwed. Odin back to stock 2.1 and then follow the instructions. Don't sweat getting Gingerbread bootloaders for now. Get your phone in download mode.
You probably won't know this but even if you phone doesn't show download mode on its screen, you want that yellow COM box to light up in Odin. Once you see that, profit.

Woodrube said:
Dude that video is wack. He pirates one version of CWR but once it boots up is a completely different version. Check out the numbers on top. The edits are terrible. Cuts out some pretty huge points. Plus he starts out with Passion beta 1 on his settings screen before he edits back to show you how to do it, but ends up with RC1.
Click to expand...
Click to collapse
Yeah i'm completely confused from the video as well...
lovenokia said:
so am i screwed? if i am than thanks for trying to help me though.
Click to expand...
Click to collapse
First read the post above this and try to get odin to light up yellow, if it does, no JIG needed, odin and you should be good. If that does not happen, then you will need a JIG.
Since you cannot get into recovery or download mode, I would try a JIG before claiming that your phone is a brick.

does the odin and stock rom from the video that i used work? or where should i get the odin and stock rom this time without effing up?