Database Info

I think I am in trouble

Hello Everyone,
I have a rogers captivate. I was trying to update to 2.3 android using Odin . I followed the whole process as stated. After rebooting, I got AT&T logo??? and the phone will not boot, go into recovery mode, or connect to my computer. Have I messed up my phone. Please advice.

how did you get an AT&T logo if it doesnt boot?
also what part of the process were you at? gingerbread shouldnt give the white ATT screen
it should give the "i9000" screen with gingerbread.
or were you flashing stock ATT first?
there is nothing wrong with having the wrong boot screen AND A FIX WAS RELEASED LAST NIGHT FOR GB
the fix for stock ATT has been out for a while. AND MY STOCK ROM FIXES IT TOO!
did you read the part about the button combos changing with gingerbread? or if you are on the ATT stock, use old button combos. Also you should have found my stock rom link before flashing, info there too!, its in my sig,
you have to give us more information to help you.

I beleive I was installing it to stock ATT first. That is when this happened. I was on Odin one click install. I remember the phone saying "do not disconnect the target". then all the installation was done from odin. This phone had 2.2 from samsung.Right now all that happens is that the phone starts and a flashing att logo on white background stays..
please let me know what other info is needed. i will post it all to the best possible

boot into download mode and flash ATT stock again. something messed up
are you using the "one click odin" or the other odin?
and what gingerbread are you trying after?

how do i do that. i have tried vol up+down+power combo. still the same flashing logo with no menus. i was using one click odin. and i was still on installing stock android. never got the chance to go to 2.3

If you can't get into download mode through the 3 button way you might need the jig. You got lucky since you're still able to boot up some have perma brick so try the jig and flash back to stock
Sent from my SAMSUNG-SGH-I897 using XDA App

HOLD VOL UP + DOWN
the plug in USB to PC.
keep buttons held until screen comes on!
i asked which gingerbread you were going to do AFTER

What is the build number on your phone, 4 numbers printed under the battery, mine is a 1010 for example, which mean oct. Of 2010 is when it was built. Some phones 1010 and after will not accept the one click odin rom and cause a bootloop like you are having, Try an odin package from TRusselo's sig instead.

my packages dont have the bootloaders. that might be whats screwed up with blinking att boot.
need download first before anything. i do have a GB bootloader package separately

something else:
try removing battery,
plug in USB to PC and Phone
Hold both Volume buttons
put battery back in.
should get you download mode

I really have noidea about what gingerbread i was after, i guess i wanted just the stock android without any custom software from samsung. I am total noob here as far as androids go.
the number on the battery say 2010.12.20 and the last forr nos under the battery at s/n are 11.02.
what is a jig. how do i use it. My phone cannot connect to the computer.
When I try to reset my device by any method, whether usb or power combos, it goes into either a. ATT logo flashing every few secs. or b. battery charging logo with nothing happeining.
Also my phone cannot be seen on my computer

gingerbread isnt for noobs
NOT THE DATE ON the battery
UNDER the battery ON THE PHONE
4 digit number
if you dont know what a jig or gingerbread or any of this stuff is,
you shouldnt have touched your friggin phone!

My apologies. the number is 1102. I understand I have screwed up. Any chance of having a working phone again.

GO GOOGLE A CAPTIVATE JIG AND BUY ONE
you wont be able to make one if you cant follow instructions.
that is your only hope. if not your phone is F'ed up perminantly.
your ONLY HOPE AFTER, is if your phone *somehow stops* turning on *forever*
and you send it back for warranty, and play dumb! ..... ..... ... .. .
PROGRAMMING a phone cant be learned it 5 minutes.
HELL you cant even read the friggin instructions (written for experienced users) in 5 minutes
this was an expensive lesson on researching and learning before doing

hitechchef said:
My apologies. the number is 1102. I understand I have screwed up. Any chance of having a working phone again.
Click to expand...
Click to collapse
Sorry for stepping in..
Yes there is. Might be a little complicated tho. You have some reading to do my friend.
Tru, I'll let you handle it but HiTechChef, you might've to go in for waranty and exchange it saying it did that after you tried to update through Kies. They'll check it and give you another one.

Thanks I will try this method

BWolf56 said:
Sorry for stepping in..
Yes there is. Might be a little complicated tho. You have some reading to do my friend.
Tru, I'll let you handle it but HiTechChef, you might've to go in for waranty and exchange it saying it did that after you tried to update through Kies. They'll check it and give you another one.
Click to expand...
Click to collapse
he's a rogers phone and it boots to ATT screen
it has to *stop* booting to get *warranty*

TRusselo said:
he's a rogers phone and it boots to ATT screen
it has to *stop* booting to get *warranty*
Click to expand...
Click to collapse
Oh right.. Wow..
Yep, go read about a JIG (it's pretty simple to use). You can either build it or buy one from mobiletechvideo or ebay.

TRusselo said:
he's a rogers phone and it boots to ATT screen
it has to *stop* booting to get *warranty*
Click to expand...
Click to collapse
Lol That kind of subtly is lost here... noone is picking up on your suggestion...

and thats how its going to stay,
ive said it before with almost the same words.
ive laid out all the tools....
correction of the original problem is necessary,
research is salvation,
resistance is futile.
there it is... i laughed... all is good again...

[Q] So confused...

I have completely screwed my phone. I have rooted and ROM'ed at least 5 Android phones in the past.
This one is simply ridiculous.
I have used ODIN and had no problems. Now when I flashed my rom through CWM it just flashes a Samsung screen.
I have redone everything 10 times I am doing everything correctly.
I have tried different ROMs different kernels, same thing every time.
I am lost, and need help PLEASE!

Did you flash a pit file? Repartitioning usually does the trick.
Sent from my SCH-I510 using Tapatalk

Now that I've wiped my phone, how do I disable the voodoo lagfix without being able to do anything on the phone so I can install a ROM? This doesn't make sense to me.

ilovesoad said:
Did you flash a pit file? Repartitioning usually does the trick.
Sent from my SCH-I510 using Tapatalk
Click to expand...
Click to collapse
I'm sorry I don't know what that is.

mjdato said:
I'm sorry I don't know what that is.
Click to expand...
Click to collapse
Check out this thread for info on (and to get) the pit file.

I did this and now my phone will not boot up at all...

This phone is a total piece...

mjdato said:
This phone is a total piece...
Click to expand...
Click to collapse
No, you just do not know what your doing, simple as that. Tons of people here and elsewhere have no problems. You haven't listed what roms and kernels you are trying. My guess is either using froyo rom with GB kernel or not using odin right, it's pretty easy to use but also easy to get wrong, I suggest actually taking some time to learn what to do and what everything is. It's evident you are very impatient by your constant posts in this thread and their content which implies you didn't take the proper time to research what you are doing and how it all works. With some actual useful information like rom and kernel we could probably help

I've been researching this phone and the tools for a week now, and started this process at 1PM, so no im not impatient.
This phone is a piece. It was bad when it came out and it still is crap. I've rooted, Rom'ed and modded every Android phone I've ever had with no issue. Different carriers, different manufacturer's. Never had an issue.
Now, thanks for the lecture Dad, if you have any insight as to why my phone will not boot up after flashing the pit file it would be much appreciated, if not, troll somewheres else.
Thanks!

mjdato said:
if you have any insight as to why my phone will not boot up after flashing the pit file it would be much appreciated, if not, troll somewheres else.
Thanks!
Click to expand...
Click to collapse
Are you drunk? Maybe try again when you sober up?
Sent from my mobile office.

What roms and kernals have you tried?
Are you making sure that you are using the PDA option in Odin instead of phone?
Are you using the PIT option with the right boxes checked/unchecked?
Give us a little more insight on what you have done and what you are trying to do and we will do our best to help you out.
Sent from my SCH-I510 using XDA App

mjdato said:
I've been researching this phone and the tools for a week now, and started this process at 1PM, so no im not impatient.
This phone is a piece. It was bad when it came out and it still is crap. I've rooted, Rom'ed and modded every Android phone I've ever had with no issue. Different carriers, different manufacturer's. Never had an issue.
Now, thanks for the lecture Dad, if you have any insight as to why my phone will not boot up after flashing the pit file it would be much appreciated, if not, troll somewheres else.
Thanks!
Click to expand...
Click to collapse
If you have been researching this phone for weeks wouldn't you have known if it were a piece of #### before you bought it? So far I like the phone very light and reliable. Definitely needs root though the original software is terrible.

jfl14609 said:
If you have been researching this phone for weeks wouldn't you have known if it were a piece of #### before you bought it? So far I like the phone very light and reliable. Definitely needs root though the original software is terrible.
Click to expand...
Click to collapse
If I'm not mistaken when you use a pit file you have to Odin a new rom right after. It wipes everything off the partitions.but I've only used a pit one time so may be wrong . The first few times I flashed this phone I had problems but eventually I caught everything that usually causes a problem. And I was just like you, had been flashing evo, incredible and hero for a long time with no problem. But Samsung gave me a headache. But i was stuck in a bootloop and nothing would flash. I ran the pit then flashed a new tar file and she booted up fine
Didn't mean to quote that post. Oops

Please use the Q&A Forum for questions Thanks
Moving to Q&A

It was given to me by my job. I didn't have a choice if I wanted my bill paid for every month.

Ok, so I have tried:
0808_charge_overclock
NAMELESS_Kernel_Cleanup_Script
ROMS i have tried:
Altered BeastAlpha 5
Eclipse_TW4_v1.1
humble50_rc2

At this point it will not charge or boot up into anything so I'm not sure if it's even recoverable right now....where should I even start?

mkarps said:
Are you drunk? Maybe try again when you sober up?
Sent from my mobile office.
Click to expand...
Click to collapse
I truly wish I was. LOL

mjdato said:
Ok, so I have tried:
0808_charge_overclock
NAMELESS_Kernel_Cleanup_Script
ROMS i have tried:
Altered BeastAlpha 5
Eclipse_TW4_v1.1
humble50_rc2
Click to expand...
Click to collapse
Well since u partitioned with the pit. Ur phone is sitting there with nothing on it. No rom, no kernel,recovery etc. So i know humble 5 wont work cuz it doesn't include a kernel. Humble 4 will however work. It includes a kernel and a recovery .have u did everything in the "Hoe to fix your phone "thread on top of development section?

mjdato said:
At this point it will not charge or boot up into anything so I'm not sure if it's even recoverable right now....where should I even start?
Click to expand...
Click to collapse
I've had problems at times getting my phone into download mode. Just gonna toss some stuff out there as I'm sure there are people that know more than me. Is there anyway you can have a charged or extra battery charged? I would hmm uninstall the samsung drivers etc..or atleast re install so your phone is recognized when you plug it in the usb. So you can get your phone into download mode and Odin doesnt see it? Have you followed the directions in the stickys on the Dev page to a T? Im sure you have tried all usb ports,different cable, hell different computer. If you still can't get it back up as many have posted they haven't seen to many totally bricked phones I would love to have something to just play around with. If you dont have insurance and cant get it exchanged let me know. Pretty sure though more people will chime in and get things working though.

[Q] Does anyone know what's wrong with this screen?

I was trying to update my mom's Infuse to ICS, then all of a sudden this (attached) happened. Heimdall had just given me the libusb.dll error (I needed to update the bootloader cause I kept getting rainbows in CWM), so I was unplugging the phone so I could get the right drivers.
I have a horrible feeling I did something very wrong. I can't imagine why what I was doing would have caused this though, since the cmd had gone back to a default state after giving the error.
Is there any way to fix this?? Thanks a ton in advance!

mvgc3 said:
I was trying to update my mom's Infuse to ICS, then all of a sudden this (attached) happened. Heimdall had just given me the libusb.dll error (I needed to update the bootloader cause I kept getting rainbows in CWM), so I was unplugging the phone so I could get the right drivers.
I have a horrible feeling I did something very wrong. I can't imagine why what I was doing would have caused this though, since the cmd had gone back to a default state after giving the error.
Is there any way to fix this?? Thanks a ton in advance!
Click to expand...
Click to collapse
can you get it into download mode...?
if so run the one click again and you might have to check the box for bootloaders, on the second run...meaning I would run it twice...

It does that immediately on power up. Doesn't even get to the Samsung screen. Odin will recognize the phone, but when I try to flash a return to stock package (which I used earlier perfectly fine), it says the md5 is invalid.
Like I said, I never even got to the point of installing the bootloader since I forgot about the drivers. Are you saying I should install the drivers and try to flash the bootloader again?
Thanks so much for the help! I've never had this much trouble with a phone before
EDIT: I'm a dumbass. since I couldn't see the screen, I forgot to press up again after entering download mode. Odin is now in the process of installing the aforementioned return to stock package. And I think it worked!
You have no idea how grateful I am of you for pointing that out! I feel kind of dumb for not trying it, but when the screen looked like that I could only assume there was no functionality!
THANKS AGAIN! Times a million!

Lol ok let us know when you get it up and running....kk
Sent from my SAMSUNG-SGH-I717 using xda premium

What EXACTLY gave you the idea to put your mother's phone on a ROM that half works and has many bugs? Just trying to understand... I could have done this to my friend's mom's atrix, but I didn't because the stock ROM will always have the least bugs for unpopular devices like ours. (ones that don't get official support for CM or AKOP or anything)

wayzata said:
What EXACTLY gave you the idea to put your mother's phone on a ROM that half works and has many bugs? Just trying to understand... I could have done this to my friend's mom's atrix, but I didn't because the stock ROM will always have the least bugs for unpopular devices like ours. (ones that don't get official support for CM or AKOP or anything)
Click to expand...
Click to collapse
whooo there...slow your roll...
the op has the options to put what he wants, and actually if you have been tracking the ICS/CM9/AOKP threads they have made leaps in the smashing of bugs....actually very stable and good to go now, seeing how just months ago we didn't even have any ver of ICS, and yes it takes homework to install..
and you kept stock on your friends Mommy phone well that was between you and him and Mommy...
so long story short....as far as unpopular, I see this device being sold and for a high demand on CL and Ebay...with all the support given here...that is my IMHO...as is yours

+10 Char

bigjoe2675 said:
whooo there...slow your roll...
the op has the options to put what he wants, and actually if you have not been tracking the ICS/CM9/AOKP threads they have made leaps in the smashing of bugs....actually very stable and good to go now, seeing how just months ago we didn't even have any ver of ICS, and yes it takes homework to install..
and you kept stock on your friends Mommy phone well that was between you and him and Mommy...
so long story short....as far as unpopular, I see this device being sold and for a high demand on CL and Ebay...with all the support given here...that is plenty IMHO...as is yours
Click to expand...
Click to collapse
This makes about as much sense in English as it does in Japanese.

wayzata said:
This makes about as much sense in English as it does in Japanese.
Click to expand...
Click to collapse
You are a smart guy... i am sure you understood me....
Arigatou gozaimasu btw...just leave it as that....

Hajimemashita Joe sama
Sent from my SGH-I997 using xda premium

mvgc3 said:
I was trying to update my mom's Infuse to ICS, then all of a sudden this (attached) happened. Heimdall had just given me the libusb.dll error (I needed to update the bootloader cause I kept getting rainbows in CWM), so I was unplugging the phone so I could get the right drivers.
I have a horrible feeling I did something very wrong. I can't imagine why what I was doing would have caused this though, since the cmd had gone back to a default state after giving the error.
Is there any way to fix this?? Thanks a ton in advance!
Click to expand...
Click to collapse
Same thing happened to mine when i flashed back to stock. Kept trying download mode and finally worked. Keep trying and also try recovery. Worked for me
Sent from my SAMSUNG-SGH-I717 using xda premium

wayzata said:
What EXACTLY gave you the idea to put your mother's phone on a ROM that half works and has many bugs? Just trying to understand... I could have done this to my friend's mom's atrix, but I didn't because the stock ROM will always have the least bugs for unpopular devices like ours. (ones that don't get official support for CM or AKOP or anything)
Click to expand...
Click to collapse
First of all, every once in a while, she asks me if there are any updates yet.
Second, there's only a short list of insignificant bugs mentioned in the ICS topics.
I flashed GB on it a while back, and I figured since CWM and everything was set up already I wouldn't have a problem; flash, reboot, flash again, done. Unfortunately, it wasn't flashing the second time for whatever reason, and I figured it had something to do with the now half-functional CWM.
Anyway, to those of you who weren't unreasonably judging me, and rather decided to help: Thank you, the phone is now back up and running!

Prometh1216 said:
Hajimemashita Joe sama
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
LOL, woooooooootttttttt

Same thing happened to me. What I did was send my phone back to Samsung tell them everything ( except about rooting) they will email you a label then ship it off and get back in about 1 week. They will put stock gingerbread on it. Hopes this helps.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2

Hard brick?

I successfully flashed to att ICS using Jim's method. Then I decided to roll back to 2.3.6 and used Jim's ICS back to 2.3.5 fxz fix zip file. The RSD stopped at 5/19 reboot bootloader for a long time and the screen was off. I hit the power button trying to turn on the screen without thinking. Then I realized that I was flashing! It was too late and I saw FAILED on RSD. My A2 cant turn on anymore. I did not unplug or pull the battery. Any help would be appreciate!

qtqt710 said:
I successfully flashed to att ICS using Jim's method. Then I decided to roll back to 2.3.6 and used Jim's ICS back to 2.3.5 fxz fix zip file. The RSD stopped at 5/19 reboot bootloader for a long time and the screen was off. I hit the power button trying to turn on the screen without thinking. Then I realized that I was flashing! It was too late and I saw FAILED on RSD. My A2 cant turn on anymore. I did not unplug or pull the battery. Any help would be appreciate!
Click to expand...
Click to collapse
DId you replace ALL of the files and then point the RSD to the xml?

Can you boot into fastboot by holding power button and vol down.If can you just reflash it using rsd lite.Tell me more detail about your atrix 2 current rom and which version of rom you are flash with rsdlite.
Sent from my MB865 using xda premium

Exact same problem has occurred to me as well.
I did replaced the files Jim created to FXZ back to 2.3.6 from ICS
My Battery was fully charged at the time of flashing. Flashing stopped at 5/19 reboot bootloader for 15 mins then tried rebooting it manually but it didn't started.
Now I've tried everything but it is not even starting in Fastboot
Please help me with this, I don't want to start any new thread so posted my problem here.
EDIT: I think this is a common problem as the OP here also have the same problem
http://forum.xda-developers.com/showthread.php?t=1781045
http://forum.xda-developers.com/showthread.php?t=1700775
I only flashed ICS when Jim confirmed that it was possible to revert back to 2..3.5
I think there is a problem in reverting back to 2.3.5 once applied ICS update and people should be aware of that.
Everyone should stop flashing ICS leaks otherwise they might end up bricking their phone forever.

100% same to me.
Up to ICS ok, back to Fxz with RSD and stuck at 5/19 reboot-bootloader step, I disconnected cable and phone black forever.
A lot of people they failed when flash with RSD but no problem, just take battery out and return, boot again to fastboot to re-flash. I think wrong file in Fxz not makes this problem, main cause I still don't know ! Maybe we are unlucky man ?

FXZ is not wrong one as I did used it when I had to flash back to stock from lithium Rom last week. I think phone is dead because it is not even booting into fastboot.. I've tried even booting to our stock recovery by pressing 3 buttons but no luck so far.
Its just very bad few hours back I was running ICS and now my phone is not even booting up.

OMG man!! I should have make a thread about this yesterday, but maybe nobody would of paid attention. I didn't really want this to happen to anyone, when flashing from 4.0.4 back to 2.3.5 it will get stuck at 5/20, something like that saying "rebooting loader". Now my phone with a blackscreen is getting hot when I insert the battery and when I plug it without a battery into my laptop or wallcharger and I dont have warranty. I call it white LED of death, when I plug it in to my laptop without a battery hehe , so I guess i'll be paying maybe 200$ dollar for it to be repaired, well if they repair it though, they charge so much here.. But i'm still trying to look what I can do, before I take it to a repair shop.

I heard about this problem when leak ICS for China/HK market 1 month ago, from xda man, and Jim he warned everybody here take care when coming back GB from ICS leak should make your phone bricked.
Now ATT ICS leak was released and all trusted Devs here confirmed that we can turn back to GB without problem, so I thought that it was safe to do with. Next day Jim posted new thread with new patch file. So sad ... I'm too late, we're too late ...

vinamilk said:
I heard about this problem when leak ICS for China/HK market 1 month ago, from xda man, and Jim he warned everybody here take care when coming back GB from ICS leak should make your phone bricked.
Now ATT ICS leak was released and all trusted Devs here confirmed that we can turn back to GB without problem, so I thought that it was safe to do with. Next day Jim posted new thread with new patch file. So sad ... I'm too late, we're too late ...
Click to expand...
Click to collapse
I didn't even flashed ICS leak first day, I did it second day when Jim confirmed and uploaded a link for new replace files.

prasannapmv said:
I didn't even flashed ICS leak first day, I did it second day when Jim confirmed and uploaded a link for new replace files.
Click to expand...
Click to collapse
So this is the point that I'm very confused, I think that even failed flashing phone still powered on normally : wrong boot.img --> just jamed at boot logo, wrong bootloader --> screen turn on and shows errors; need to be flashed again by RSD or script. Some man here even not flashed anything, just root then reboot and phone dead without any reason.

vinamilk said:
So this is the point that I'm very confused, I think that even failed flashing phone still powered on normally : wrong boot.img --> just jamed at boot logo, wrong bootloader --> screen turn on and shows errors; need to be flashed again by RSD or script. Some man here even not flashed anything, just root then reboot and phone dead without any reason.
Click to expand...
Click to collapse
I guess it has something to do with our bootloader, maybe it's stuck or not even working.

darkmixta said:
I guess it has something to do with our bootloader, maybe it's stuck or not even working.
Click to expand...
Click to collapse
I just talked to a Motorola service person he was saying in some rare cases a inbuilt ROM(read only memory) chip which stores bootloader files gets corrupted and in that case it might not even be possible to boot into fastboot.
I don't know how far he is right but one ting we are sure that our hardware was perfectly ok before flashing FXZ.
For me I even made sure that my battery was fully charged before starting FXZ.

prasannapmv said:
I just talked to a Motorola service person he was saying in some rare cases a inbuilt ROM(read only memory) chip which stores bootloader files gets corrupted and in that case it might not even be possible to boot into fastboot.
I don't know how far he is right but one ting we are sure that our hardware was perfectly ok before flashing FXZ.
For me I even made sure that my battery was fully charged before starting FXZ.
Click to expand...
Click to collapse
Same here I had like 90% battery or more, is you're phone becoming hot? When you plug it in or insert the battery?

darkmixta said:
Same here I had like 90% battery or more, is you're phone becoming hot? When you plug it in or insert the battery?
Click to expand...
Click to collapse
yes its getting heated when connected to a wall socket or on a battery.

Did anyone upgrade RSDlite to 5.7 before trying this by any chace?
That might be an issue.
Also, this could be something that was introduced to later model phones. My a2 was able to fxz back, but it ws made in SEPT 2011. Just another thought.
Sent from my SAMSUNG-SGH-I747 using xda premium

prasannapmv said:
yes its getting heated when connected to a wall socket or on a battery.
Click to expand...
Click to collapse
Hahaha, what should we do? Yesterday I felt like throwing my phone into the wall man and just %$#@ Motorola, this is like the biggest failure ever!! Hard bricked without doing something wrong.. Wish I could go back in time sometimes and I don't even have warranty which sucks, what are you gonna do?
Really hard to hard brick? http://forum.xda-developers.com/showpost.php?p=28324515&postcount=10
We hard bricked so easy..

jimbridgman said:
Did anyone upgrade RSDlite to 5.7 before trying this by any chace?
That might be an issue.
Also, this could be something that was introduced to later model phones. My a2 was able to fxz back, but it ws made in SEPT 2011. Just another thought.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I was already using RSD 5.7

jimbridgman said:
Did anyone upgrade RSDlite to 5.7 before trying this by any chace?
That might be an issue.
Also, this could be something that was introduced to later model phones. My a2 was able to fxz back, but it ws made in SEPT 2011. Just another thought.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I did not. It is 5.6. That may be the reason. I got my A2 from att in Nov 2011, so I guess it is the same earlier version, right?

To those with the issue, can you not get back into ap fast boot? Either hold both volume buttons down with power, then select it from the menu, or i have found that holding up with power will boot you right into fastboot.
Sent from my MB865 using xda premium

Fall of Enosis said:
To those with the issue, can you not get back into ap fast boot? Either hold both volume buttons down with power, then select it from the menu, or i have found that holding up with power will boot you right into fastboot.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Nope they can not even power on anymore. This is what we all feared. The hk leak had this same thing in it...
Looks like moto will be warrantying a bunch of phones.
I am just not sure why I can still do it...
We have had way too many of these now for it to be user error or an accident.
Sent from my SAMSUNG-SGH-I747 using xda premium

[Q] Am I screwed

Well I was doing a back up and flashed a new ROM, Blinky's revenge, and when I went to reboot nothing. My battery was at 94%.
When I got to plug in the charger I do not even get the battery icon. I cannot reboot into CWM I get nothing.
Do I now own a nice paper weight?
It is still under the one year warrenty. Will they know what happened if I send it in and tell them it is not working period?
Thank you

What phone do you have?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Galaxy 2 skyrocket SGH i727

catchjeff said:
Galaxy 2 skyrocket SGH i727
Click to expand...
Click to collapse
Can you get into download mode?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

catchjeff said:
Galaxy 2 skyrocket SGH i727
Click to expand...
Click to collapse
Are you sure you got the right rom for the i727, where did you get it from. If it doesn't turn on or boot up no one can tell that you tried to flash a rom. It sure sounds like you've bricked it. Any luck getting odin to recognize it. If it does, flash the stock rom.
Sent from the short bus

catchjeff said:
Well I was doing a back up and flashed a new ROM, Blinky's revenge, and when I went to reboot nothing. My battery was at 94%.
When I got to plug in the charger I do not even get the battery icon. I cannot reboot into CWM I get nothing.
Do I now own a nice paper weight?
It is still under the one year warrenty. Will they know what happened if I send it in and tell them it is not working period?
Thank you
Click to expand...
Click to collapse
here's how you check for a heart beat on the phone plug it into the PC and see if you get a Qhusb DL if you do enjoy the paper weight... and maybe an exchange might but the carrier can only give you an answer

Gosh dang it mother F$*%er thats where I messed up.
I can not get into download mode nor get odin to reconize it. It is officially a paper weight. I put in for an exchange with AT&T should be here tomorrow.
I flashed the wrong ROM. I flashed for the I777 not the i727. I hit the wrong button when I was installing I meant to go back but hit the power button by error and that is what did it.
Thank you everyone for your help. It is the first time I ever bricked a phone and I have rooted about 9 different phones and this was completely my error.
Now here is a question. Will they be able to tell it was rooted and I bricked it?

Probably not. From experience, I don't think you need to worry.
Sent from the short bus

catchjeff said:
Gosh dang it mother F$*%er thats where I messed up.
I can not get into download mode nor get odin to reconize it. It is officially a paper weight. I put in for an exchange with AT&T should be here tomorrow.
I flashed the wrong ROM. I flashed for the I777 not the i727. I hit the wrong button when I was installing I meant to go back but hit the power button by error and that is what did it.
Thank you everyone for your help. It is the first time I ever bricked a phone and I have rooted about 9 different phones and this was completely my error.
Now here is a question. Will they be able to tell it was rooted and I bricked it?
Click to expand...
Click to collapse
No they won't be able to tell anything.
Question...why did you have a Rom for a different phone on your sd card?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

xcrazydx said:
No they won't be able to tell anything.
Question...why did you have a Rom for a different phone on your sd card?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Stupid error. I was using my QR code reader to download and must have hit the wrong QR code and just from habit I hit download. Never made this mistake before ever.
I just want to kick myself in the arse.

catchjeff said:
Stupid error. I was using my QR code reader to download and must have hit the wrong QR code and just from habit I hit download. Never made this mistake before ever.
I just want to kick myself in the arse.
Click to expand...
Click to collapse
Poo happens. Luckily, you're within a year, so it's just a couple weeks without a Skyrocket (if it won't turn on, Sammy can't tell that it was rooted and bricked on a flash). If you were outside of 12 months, well, that would've been a pretty costly lesson. I still double-check the file name before flashing anything on any of my phones, including my Cappy, just to make absolutely certain I'm not about to flash something for a different phone by mistake.

T.J. Bender said:
Poo happens. Luckily, you're within a year, so it's just a couple weeks without a Skyrocket (if it won't turn on, Sammy can't tell that it was rooted and bricked on a flash). If you were outside of 12 months, well, that would've been a pretty costly lesson. I still double-check the file name before flashing anything on any of my phones, including my Cappy, just to make absolutely certain I'm not about to flash something for a different phone by mistake.
Click to expand...
Click to collapse
Yeah I was within a year and just got my new phone yesterday and wiped all the rom and kernals off my sd card and will just take the time to redo everyting which is kind of fun for me. I get to do most of this stuff at work on my work pc.
Thank you everyone
Your the bomb

I just hit you all with a thanks!!!!
That is what I love about this community, you guys and gals are there for us when we need it and even when we do not.
I got it rooted and CWM on there now time to wipe and re do my roms. Just glad I got a backup of my previous setup before the bricking.