I think I bricked my Epic... - Epic 4G General

I was on AA ROM V5 and wanted to switch back to ACS frozen. So I was following the instructions and flashing. I successfully flashed EC05 stock, and I was flashing the CWM 3.1.0.1 tar here. After it said it had finished flashing, it had the symbol which was a phone with an arrow pointing to a computer. I tried to flash EC05, but it kept failing immediately. I tried one last time, and then it got stuck. I waited twentyish minutes then pulled the battery to try again. Now the phone won't respond to anything.

Keep battery out, then plug in usb. see if that gets you into download mode.

You shouldnt check repartition!!! Try the 'button' and uf ut doesnt work, unplug everything from your phone, pull the battery.and leave it like.that obernight. Then try odin

I'm assuming my method worked since u thanked me?

Shoulon said:
Keep battery out, then plug in usb. see if that gets you into download mode.
Click to expand...
Click to collapse
Thank you!!!
And yeah, Marc that was bad idea but I was following this guide. I'd read it the past you shouldn't but I wanted to make sure I didn't screw it up when I flashed the rom so I did it anyways. How ironic.

Dariste said:
Thank you!!!
And yeah, Marc that was bad idea but I was following this guide. I'd read it the past you shouldn't but I wanted to make sure I didn't screw it up when I flashed the rom so I did it anyways. How ironic.
Click to expand...
Click to collapse
Glad to be of help. Next time please do post in Q&A. I do a sweep of the threads there as often I can to make sure newcomer's and regulars alike get help.

Sorry, I usually don't screw up like this. I've been flashing roms since Dec on this phone, and Kernels on my Pre before, but I never manged to mess up like this. Next it will go in Q&A, thank you again.

Shoulon said:
Glad to be of help. Next time please do post in Q&A. I do a sweep of the threads there as often I can to make sure newcomer's and regulars alike get help.
Click to expand...
Click to collapse
i post questions in general and just press on this is a question button. mwhaha... i need sammiches and treats soon

Related

Losing ADB Device when going into recovery

So ADB was working (I thought?) and ADB recognizes my phone when I just plug it in, but when I go to do the steps for rooting, it no longer recognizes it.
I got it to say offline ONCE after the loop, but the on the unplug re-plug, it went away. I'm bummed...
cmon now http://forum.xda-developers.com/showthread.php?t=703429
You must have misread my post. I've looked thoroughly through that post, actually.
What I am needing help with is after that loop, going from offline in ADB to recovery...
thanks!
Can A Mod PLease Lock this thread, thee is Multi Post in Multi threads Reading this!
The Answer you are Looking for.... UN-PLug the the USB wait 5 second if that and plug it back into the Phone..
I did that, on several different occasions, but alright, will try again. Thanks.
missxoash said:
You must have misread my post. I've looked thoroughly through that post, actually.
What I am needing help with is after that loop, going from offline in ADB to recovery...
thanks!
Click to expand...
Click to collapse
ITs not recognizing your phone when in recovery thought correct? if so thats the same thing discussed there. If it did recognize it as offline in recovery then do as eugene said.
missxoash said:
I did that, on several different occasions, but alright, will try again. Thanks.
Click to expand...
Click to collapse
it needs to stick to offline, not just say it onec or twice. itll say offline many times not just once then disappear. Once it does it and sticks, it doesnt turn off, you dont need to rush and hit ctrl c
I'm having a issue that's somewhat related. I have a tmo mts3g and I had it rooted with no issues following the instructions provided in eugene's previous posts on the matter. Tmobile recently dropped a OTA update for 2.1 and it relocked my phone. Now that I'm trying to reroot it I'm having issues getting the phone to be adb online in recovery mode. I do adb reboot recovery and when it starts I have the loop going and I have no problem getting it to say "device offline" but when I unplug the device (no matter how long I wait) and plug it back in it still remains in "offline" status under adb devices. I've heard about driver issues and all kinds of other madness but I'm using the same computer that I used when I rooted it previously. My question is; is this something tmobile might have fixed in their ota update and am I just wasting my time continuing to try this method? If not i'm more than happy to continue to try but not if it's with no point.
Thing is you did the OTA update, so instead of following the old guide, you follow the one in the rom bible in the development section. Hope that helps.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Yeah, I found my way there eventually. I got it all straightened out and currently on Eugene's MyFroyo6 with no complaints. Thanks

<HOW TO> Easy Guide to Using Odin/Unbricking Your Phone

I have noticed that while there are many guides to do this, people still ask the question in threads, so I'll simplify it here. It is meant as an Odin helper.
Make sure you have downloaded the files you need (firmware and odin) from the bottom of this post. I have only included Odin v3.1 and the needed file for UCJF6 restore, cause the jh3 and other stuff is too big to upload directly. This Odin works with all firmwares. Just d/l the desired firmware and use this odin to flash. Just unzip both my files and there you go.
1 - PHONE MUST BE POWERED OFF (not plugged in and pull the battery for 5 seconds if you have to).
2 - Open Odin and choose the files you need. Do everything EXCEPT press start.
3 - HOLD BOTH volume buttons and, while holding them, count to 2 then plug in usb and wait 2-4 more seconds. Phone will enter download mode and Odin will recognize it on a COM.
4 - Press start in Odin. When it completes and your phone reboots, close Odin.
5 - BE PATIENT!!! Your phone may now appear to stick on one of the boot screens or a blackscreen, but it is really doing stuff. Wait 5-10 minutes before you impatient people decide it didnt work.
I can only say this: THIS METHOD HAS NEVER FAILED FOR ME
I hope this helps someone, as someone was kind enough to do for me.....
Enjoy, and happy modding! =)
You should also add how to do it if someone flashes a I9000 rom
Sent from my phone so excuse the spelling errors
You guys should really read the stickies...
http://forum.xda-developers.com/showthread.php?t=731989
tytdfn said:
You should also add how to do it if someone flashes a I9000 rom
Sent from my phone so excuse the spelling errors
Click to expand...
Click to collapse
Same procedure.
designgears said:
You guys should really read the stickies...
http://forum.xda-developers.com/showthread.php?t=731989
Click to expand...
Click to collapse
I have read almost every sticky here, and I swear of the 15-20 threads I am subscribed to I see AT LEAST 3 a day saying ".... I think my phone is bricked.....", so I figured I'd just put it right there on the 1st easy post in kind of a monkeys-could-do-it-like-this mode. I'm just trying to help those that DON'T read the really long threads. We know they should, but they don't.
techmik67 said:
I have read almost every sticky here, and I swear of the 15-20 threads I am subscribed to I see AT LEAST 3 a day saying ".... I think my phone is bricked.....", so I figured I'd just put it right there on the 1st easy post in kind of a monkeys-could-do-it-like-this mode. I'm just trying to help those that DON'T read the really long threads. We know they should, but they don't.
Click to expand...
Click to collapse
It's in the OP... if they cant find it in the thread with the tools how are they going to find it in some random thread?
designgears said:
It's in the OP... if they cant find it in the thread with the tools how are they going to find it in some random thread?
Click to expand...
Click to collapse
It seems like most people are messing up AFTER they have the necessary firmware files, which is why I didn't add any links. At least that's what I'm getting from the posts they make.
Honestly, and really I mean no offense here because I love your work AND advice, I see 1 flaw in your post, at least on my captivate which is all i can practice on. Copied from your post:
1. Download and install the correct drivers below (mac and linux don't need drivers)
2. Plug in your usb cable to your phone and computer
3. Open Odin
4. Enter Download Mode (see below)
5. Click Start
If I plug in BEFORE opening Odin, Odin does not pick up my phone. Doing it my way, holding both volume and then inserting usb while holding them with the phone powered off, has NEVER not worked for me. That's all I was trying to clarify for people. Sorry if I stepped on your toes.
Uploaded Odin and stock jf6 to the OP
Then what you can do is ask DG to include this as a method. There is no reason for you posting the same info which is already a sticky thread. This will eventually get lost while the sticky will stay at the top.
Alright i just wanted to say thank you to everyone. With your help i was finally able recover my phone using odin 1click. I have to say thay i was convinced that it was an unrecoverable brick and i had that sick feeling in my stomach but i read, read again, and re read the entrire odin 1click thread, and i discovered that i was booting into stock recov and not download. I think out of the 10 plus times i tried it i actually got it to go into download, by luck im afraid. Anyway the point of my long post is to thank you guys for being so smart lol u saved my phone. And me from getting an ulcer. Note Do Not download circle batt mod with black evo notification bar with the vibrant hybrid rom. from eugene. It Will brick your phone. At least it did mine. Now to figure out if i want to root again after dodging that bullet lol
Sent from my SAMSUNG-SGH-I897 using XDA App
Also i dont care where it gets posted to be honest. I am one of those monkies that probably should not root, but cant help myself trying ti learn all i can from you all lol
Sent from my SAMSUNG-SGH-I897 using XDA App
flashman2002 said:
Then what you can do is ask DG to include this as a method. There is no reason for you posting the same info which is already a sticky thread. This will eventually get lost while the sticky will stay at the top.
Click to expand...
Click to collapse
I didn't even think of that. You are right. Although I personally prefer my 3.1 odin to the 1 click, it should've been added to his, since my main point was/is the ease of getting into d/l mode if needed. I'll think before I start a new thread next time =)
flashman2002 said:
Then what you can do is ask DG to include this as a method. There is no reason for you posting the same info which is already a sticky thread. This will eventually get lost while the sticky will stay at the top.
Click to expand...
Click to collapse
It has been in there for about a month now... people don't read which is why that thread is 2093482094823 pages long
did you see how many time I had to post not to flash to an I9000, bolded at the top of the OP like 10 times
techmik67 said:
I didn't even think of that. You are right. Although I personally prefer my 3.1 odin to the 1 click, it should've been added to his, since my main point was/is the ease of getting into d/l mode if needed. I'll think before I start a new thread next time =)
Click to expand...
Click to collapse
No worries, it was just a suggestion and I feel that if this method works it would be best up there. Im glad this method worked for you as compared to the other methods.

Successfully bricked my Vibrant

So I just wanted to share with you guys that I successfully bricked my Vibrant. Getting a new one on Thursday or Friday. You know what they say. That you learn the best way when you failed in something. So I have learned today what not to do to keep the phone up and running.
UPDATE:
Followed instructions kizer at http://forum.xda-developers.com/showthread.php?t=741027&highlight=bricked+download+mode&page=5 and it took me to download mode.
How did you brick it?
Segnaro said:
How did you brick it?
Click to expand...
Click to collapse
I was putting Eugene's leaked froyo on my vibrant. Been having problems with the SD card so I decided I was going to reflash it again. So I clicked on the re-partition in Odin as I tried doing it without repartitioning. For some reason it stopped in the middle of the process, I got impatient (waited only like 5 minutes) and decided to restart it. Was having problems with the computer at the time as well. To many things running.
I think that the controller for the keys got wiped as nothing responded afterward this happened. It would not even recognized being connected to the computer.
how did you explain it to t-mobile?
iynfynity said:
how did you explain it to t-mobile?
Click to expand...
Click to collapse
Just told them that their JI6 update crashed it with an incomplete installation. I know they guy that put in the warranty exchange for me. And as he hadn't got the update to his phone yet he figured that it makes sense. Heard about the update doing weird stuff.
I just figured they would take the phone and reflash it when they get it.
swehes said:
I was putting Eugene's leaked froyo on my vibrant. Been having problems with the SD card so I decided I was going to reflash it again. So I clicked on the re-partition in Odin as I tried doing it without repartitioning. For some reason it stopped in the middle of the process, I got impatient (waited only like 5 minutes) and decided to restart it. Was having problems with the computer at the time as well. To many things running.
I think that the controller for the keys got wiped as nothing responded afterward this happened. It would not even recognized being connected to the computer.
Click to expand...
Click to collapse
so another person messes up their phone and fraud's the warranty, great post.
Next are you SURE it's bricked? I've had many failed ODIN's and I've never ever bricked one.
rsfaze said:
so another person messes up their phone and fraud's the warranty, great post.
Next are you SURE it's bricked? I've had many failed ODIN's and I've never ever bricked one.
Click to expand...
Click to collapse
Hmmmm. Found one last post of how to get into download mode, and it took it in. Greatly surprised and happy as I am quite fond of this phone. Odin new Froyo to it. Quite remarkable.
MOD. Can you please remove this thread as I managed to undo my mistake?
swehes said:
Hmmmm. Found one last post of how to get into download mode, and it took it in. Greatly surprised and happy as I am quite fond of this phone. Odin new Froyo to it. Quite remarkable.
MOD. Can you please remove this thread as I managed to undo my mistake?
Click to expand...
Click to collapse
You didn't manage to undo your mistake.. You managed to fraud t-mobile on YOUR mistake.
Glad you "Fixed" your phone.
Lol so who doesn't have insurance?
Sent from my SGH-T959 using XDA App
The insurance doesn't cover bricking your phone by way of flashing unofficial firmwares anyways does it? So what's the point?
Sent from my SGH-T959
catchy subject header, and what a turn around like mine. I now know for sure the Vibrant is 100% bullet proof figuratively lol.

[HOW-TO] Fix 5 vibrate and black screen

Here was my situation: when trying to boot the phone, it would go to the splash screen for a few seconds, then go to a black screen and vibrate 5 times. Had to pull the battery to escape. However, when booting after a battery pull with the charger in it booted just fine, but with no sd card recognition or usb/adb functionality. A factory reset and both htc's and verizon's tech support didn't fix it at all. I had this problem and there seemed to be no good guide on how to fix it so I decided to gather all the right sources in one place.
The reason it's messed up comes from the usb problem, which is why plugging it in lets it boot sometimes. So, contrary to all of tech support, fixing the usb is all you need to do to get it working same as usual again. I've outlined the steps below in the way I think makes the most sense, but read all of what I wrote to understand what you're doing before you start. The links are the specific instructions for each piece written by people smarter than me. I only take credit for figuring out what I needed to do and bringing all of their minds together in one place.
The Process
First thing is to see if you can get it booted. Best bet is to take out the battery and charger, hold down the power button for 10 seconds, then connect the charger and battery and boot. If you can't do that then your only option would be to try some fastboot adb trickery (which is over my head) or flash the stock rom in hboot from http://www.droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html. Note which radio you have (listed in settings -> about phone somewhere or on top of hboot) to get the right file. If you can get it booted then move to the next step.
To fix the sd card and usb go to http://forum.xda-developers.com/showthread.php?t=695243.
Fastboot is in the tools folder of the android sdk, not platform-tools like adb. To get the drivers working go to http://www.flexjunk.com/2010/05/01/installing-htc-incredible-android-sd-drivers/
UPDATE: To clarify: fastboot is a completely separate (although closely related) piece of software from adb. If you do not have "fastboot.exe", download it from http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/ and follow the instructions there. Or, you can just download the full sdk from google which should include adb and fastboot. I recommend the second option, but my hard drive can take the hit. (thanks BonzTM)
UPDATE: If you get an error saying "The Program can't start because AdbWinApi.dll is missing from your computer" you need to copy that file from platform-tools to tools, then it should work (thanks Jester1614).
If you had to reflash and lost root download z4root from http://forum.xda-developers.com/showthread.php?t=833953 and do a temporary root to be able to run the commands to fix the usb.
Once the sd card and usb are fixed then it should reboot with or without the charger plugged in. Now your phone is stable and will work with unrevoked again and you should be good to go!
Disclaimer
Note: This is what I experienced with my amoled incredible; in no way do I take responsibility for anything you do. If you try to blame me for bricking your phone I will enjoy a hearty laugh while salting my soup with your tears.
Worked great for me and saved me from the hassle of needing a new phone.
THANK YOU!
goblue13579 said:
here was my situation: When trying to boot the phone, it would go to the splash screen for a few seconds, then go to a black screen and vibrate 5 times. Had to pull the battery to escape. However, when booting after a battery pull with the charger in it booted just fine, but with no sd card recognition or usb/adb functionality. A factory reset and both htc's and verizon's tech support didn't fix it at all. I had this problem and there seemed to be no good guide on how to fix it so i decided to gather all the right sources in one place.
The reason it's messed up comes from the usb problem, which is why plugging it in lets it boot sometimes. So, contrary to all of tech support, fixing the usb is all you need to do to get it working same as usual again. I've outlined the steps below in the way i think makes the most sense, but read all of what i wrote to understand what you're doing before you start. The links are the specific instructions for each piece written by people smarter than me. I only take credit for figuring out what i needed to do and bringing all of their minds together in one place.
the process
first thing is to see if you can get it booted. Best bet is to take out the battery and charger, hold down the power button for 10 seconds, then connect the charger and battery and boot. If you can't do that then your only option would be to try some fastboot adb trickery (which is over my head) or flash the stock rom in hboot from http://www.droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html. Note which radio you have (listed in settings -> about phone somewhere or on top of hboot) to get the right file. If you can get it booted then move to the next step.
To fix the sd card and usb go to http://forum.xda-developers.com/showthread.php?t=695243.
Fastboot is in the tools folder of the android sdk, not platform-tools like adb. To get the drivers working go to http://www.flexjunk.com/2010/05/01/installing-htc-incredible-android-sd-drivers/
if you had to reflash and lost root download z4root from http://forum.xda-developers.com/showthread.php?t=833953 and do a temporary root to be able to run the commands to fix the usb.
Once the sd card and usb are fixed then it should reboot with or without the charger plugged in. Now your phone is stable and will work with unrevoked again and you should be good to go!
disclaimer
note: This is what i experienced with my amoled incredible; in no way do i take responsibility for anything you do. If you try to blame me for bricking your phone i will enjoy a hearty laugh while salting my soup with your tears.
Click to expand...
Click to collapse
u saved my life/phone i love u son
Perfect Solution!
Thanks Thanks Thanks +1
So...question: Does this mean if you had to reflash and are currently unrooted, that you have to wait for z4root to show up in the market. Because it seems there is no way to root aside from that, and without root no usb, and no usb no adb
sofocused715 said:
So...question: Does this mean if you had to reflash and are currently unrooted, that you have to wait for z4root to show up in the market. Because it seems there is no way to root aside from that, and without root no usb, and no usb no adb
Click to expand...
Click to collapse
Actually you can download it from the link I provided in my post to the xda page for it (http://forum.xda-developers.com/showthread.php?t=833953). Scroll to the bottom of the first post and in the attached files there is a version that works. That's what I did, and then you can run the usb fixing commands. Then it's just reboot, re-root, and restore.
Hope this helps.
This thread needs more attention.
This needs to be stickied(sp?) and maybe added to the Development section where it would most likely be looked for first.
If I've helped you, hit the thanks button!
As you can see by my post count I can't put anything anywhere, so if someone wants to move it feel free.
goblue13579 said:
As you can see by my post count I can't put anything anywhere, so if someone wants to move it feel free.
Click to expand...
Click to collapse
I re-worded your OP and posted it on another forum. I did credit you though. You are now famous.
Cool, thanks!
I wish I would have known this back in March when this happened to me! But then again my phone was S-ON and to get the USB fix to work you said you need root so I might have still been SOL.
brando56894 said:
I wish I would have known this back in March when this happened to me! But then again my phone was S-ON and to get the USB fix to work you said you need root so I might have still been SOL.
Click to expand...
Click to collapse
That is what the z4 root is for. You dont need s-off, just root. The things are going to s-on by themselves when something is trying to write to the misc, thus the misc brick. PITA brick if ya ask me.
doug piston said:
That is what the z4 root is for. You dont need s-off, just root. The things are going to s-on by themselves when something is trying to write to the misc, thus the misc brick. PITA brick if ya ask me.
Click to expand...
Click to collapse
Glad yall were able to make something of this. This is gonna save some people since warranties are finally running out. Hey Doug, I seen your thread over on AF. You did a very good job of writing that up.
Oh and thanks for the tiny little peace of credit, heh. Glad I could help 'point' the late and great dougpiston in the right direction on something, lol
wildstang83 said:
Glad yall were able to make something of this. This is gonna save some people since warranties are finally running out. Hey Doug, I seen your thread over on AF. You did a very good job of writing that up.
Oh and thanks for the tiny little peace of credit, heh. Glad I could help 'point' the late and great dougpiston in the right direction on something, lol
Click to expand...
Click to collapse
Late and great is an over statement. I am just a user like most here. I appreciate you taking the time to reply to my PM. I have been out of the Inc game for some time now so a little direction was very helpful.
Like I said I knew what had to be done but ADB kept ****ting itself, as soon as I read the OP and to use a terminal emulator I slammed my head on my desk.
So simple, I was spending all my time trying to get ADB to run that the idea of the usb being borked hadn't even crossed my mine.
This thread really does deserve more credit and to OP good on ya son. Well done.
Thank you goblue13579, wildstang83 and Doug Piston! My phone is totally functional once again.
Odd timing how the problem happened only 2 days ago on my phone, and coincidentally, a fix was hashed out in the same time period after all this time of it being unfixable.
I owe you all a beer! Thanks again!
doug piston said:
Late and great is an over statement. I am just a user like most here. I appreciate you taking the time to reply to my PM. I have been out of the Inc game for some time now so a little direction was very helpful.
Like I said I knew what had to be done but ADB kept ****ting itself, as soon as I read the OP and to use a terminal emulator I slammed my head on my desk.
So simple, I was spending all my time trying to get ADB to run that the idea of the usb being borked hadn't even crossed my mine.
This thread really does deserve more credit and to OP good on ya son. Well done.
Click to expand...
Click to collapse
Yea bud, even I use adb so much that I keep forgetting that there's emulators to use. Its just one of those things we never think about.
Even though it was really more dumb luck and excessive googling that got me to this solution, thanks! I'm glad my compilation has helped so many people. And honestly, it's the least I can do for all the help and goodies I've gotten from these forums and developers.
Happy modding!
What if the devise isn't rooted?
Let the phone sit for an hour with the battery out. Put the battery in after that, should be good
Sent from my 2.3.5 Incredible Obsession

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?

Categories

Resources