Database Info

[Q] (Q) Downgrade frm CM 9 back to gingerbread and bricked [Resolved, please delete]

I tried going back to gingerbread using Heimdall 1 click and it gives me a kernel error and failed. Now phone won't boot past the rogers logo. Any suggestions? No samsung screen. No green battery indicator when plugged in. Heimdall does detect the phone, and I've tried all USB ports and cords at my disposal. I use a mac so no access to odin. This is the first brick I haven't been able to get myself out of. Any help you would be appreciated

I am a gt i9000 owner, but can you get into download mode?
Sent by Santa Clause

If you can get download mode, then flash a gingerbread stock rom, even if it means you will lose root still do it, then flash a new rom of your choice, if you can get into download mode then you haven't got a brick
Sent by Santa Clause

Been bricked more than once...you have?
Embarking on a fresh new ROM without educating oneself can be very frustrating....since your on a Mac..with in the one click you say it reading your phone...can you get to download mode?
Pull battery
Plug in USB to phone
Hold both volume button
Pop battery back in
Do you see...the yellow Android digging?

http://forum.xda-developers.com/showthread.php?t=1293751

bigjoe2675 said:
Been bricked more than once...you have?
Embarking on a fresh new ROM without educating oneself can be very frustrating....since your on a Mac..with in the one click you say it reading your phone...can you get to download mode?
Pull battery
Plug in USB to phone
Hold both volume button
Pop battery back in
Do you see...the yellow Android digging?
Click to expand...
Click to collapse
I can get into download mode.heimdall detects my phone. I tried both qksters and adam outlers 1 click. neither would take. If I upgrade heimdall version (as it tells me its out of date) it wont get through the initial connection to the phone. if I use with out upgrade it continues to fail on kernel download.
This is my second brick (first one was when trying to root it on my mac) First brick was fixed through odin at my work. Unfortunately I don't want to wait till monday to have a functioning phone

teknhard said:
I can get into download mode.heimdall detects my phone. I tried both qksters and adam outlers 1 click. neither would take. If I upgrade heimdall version (as it tells me its out of date) it wont get through the initial connection to the phone. if I use with out upgrade it continues to fail on kernel download.
This is my second brick (first one was when trying to root it on my mac) First brick was fixed through odin at my work. Unfortunately I don't want to wait till monday to have a functioning phone
Click to expand...
Click to collapse
Hummmm..ok
Let's step back here does out prompt you for drivers?
....you might have to make a stop at your office..

Try different USB ports, I used heimdall yesterday to go back to gingerbread (so I could get the boot loaders) and I had the same problem as you, I finally got it to work with a different USB port and even then it kept failing...but I just kept trying and eventually it went through
(Pull battery, place battery back in, hold volume up and down, plug USB in-should put you in download mode...even if you can't see anything on your screen you can still enter download mode)
Sent from my SGH-I997 using XDA

DOesnt prompt me for drivers. It detects my phone and says ready to flash. I see the download mode screen. so its not completey screwed. Just can't get past the rogers logo.. I only have two USB on my macbook.. tried both quite a few times guess i'll mess with it some more. see if I can get it going. Thanks for the tips. ANy others ideas would also be appreciated

Alright, here it is:
I encountered the same problems yesterday, heimdall doesn't work when flashing back to stock from ics, from what I've found, you must use gtg's ultimate unbrick, the pit repartitions everything and also resets your binary counter (cha-ching! ). Once completed, your phone will reboot and be stuck at "...installing default apk files..." for a few minutes, don't panic, let it run its course. From there on, you can do the usual root/flash cwm deal. .
Sent from my SGH-I997 using Tapatalk 2 Beta-5

theROMinator said:
Alright, here it is:
I encountered the same problems yesterday, heimdall doesn't work when flashing back to stock from ics, from what I've found, you must use gtg's ultimate unbrick, the pit repartitions everything and also resets your binary counter (cha-ching! ). Once completed, your phone will reboot and be stuck at "...installing default apk files..." for a few minutes, don't panic, let it run its course. From there on, you can do the usual root/flash cwm deal. .
Sent from my SGH-I997 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
Funny I just did that yesterday using qkster heimdall after running the ics for the day....no issues utilizing it...so i say it does work...

theROMinator said:
Alright, here it is:
I encountered the same problems yesterday, heimdall doesn't work when flashing back to stock from ics, from what I've found, you must use gtg's ultimate unbrick, the pit repartitions everything and also resets your binary counter (cha-ching! ). Once completed, your phone will reboot and be stuck at "...installing default apk files..." for a few minutes, don't panic, let it run its course. From there on, you can do the usual root/flash cwm deal. .
Sent from my SGH-I997 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
I went back to stock from ics yesterday using heimdall...just took a long time and a lot of tries
I really think it depends on the computer though, for some Odin works best...for others heimdall works best
Sent from my SGH-I997 using XDA

bigjoe2675 said:
Funny I just did that yesterday using qkster heimdall after running the ics for the day....no issues utilizing it...so i say it does work...
Click to expand...
Click to collapse
I did not mean to be misleading, as you both have said, either or may work, I simply wanted to share my experience
mg2195 said:
I went back to stock from ics yesterday using heimdall...just took a long time and a lot of tries
I really think it depends on the computer though, for some Odin works best...for others heimdall works best
Sent from my SGH-I997 using XDA
Click to expand...
Click to collapse
Sent from my SGH-I997 using Tapatalk 2 Beta-5

mg2195 said:
I went back to stock from ics yesterday using heimdall...just took a long time and a lot of tries
I really think it depends on the computer though, for some Odin works best...for others heimdall works best
Sent from my SGH-I997 using XDA
Click to expand...
Click to collapse
Agreed. On my desktop (quad core 6 gb ram, watercooled blablablabl) can't run heimdal nor Odin to save its life.
My netbook (single core atom) took me back from CM9 with Odin like it was nothing.
My 7 year old laptop (running Ubuntu) works great using Heimdal (just run the .jar file as an executable)

theROMinator said:
I did not mean to be misleading, as you both have said, either or may work, I simply wanted to share my experience
Sent from my SGH-I997 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
No ... understood..no worries...there are some many that have never flashed or much less read anything regarding flashing are having so many prob`s...when this ics it's still bring birthed...for the infuse.
Instead of going to the dev section and doing some home work...understanding the basic info....they see ICS and have pictures of Sunday treats....in their mind...having no clue about the current ROM they are on now...Then the questions pop up...from individuals...after wards yelling SOS...But hey it's their phone.

bigjoe2675 said:
No ... understood..no worries...there are some many that have never flashed or much less read anything regarding flashing are having so many prob`s...when this ics it's still bring birthed...for the infuse.
Instead of going to the dev section and doing some home work...understanding the basic info....they see ICS and have pictures of Sunday treats....in their mind...having no clue about the current ROM they are on now...Then the questions pop up...from individuals...after wards yelling SOS...But hey it's their phone.
Click to expand...
Click to collapse
I've flashed lots of roms and never had any issues. Also looked through the forum and know the basics about getting back to stock. I'm no expert, but I have a decent idea what I'm doing. I do appreciate a forum you can ask questions though and have people help out when your stumped. I did what i could from the tools I have at my disposal here, and ran into some problems. I'm not yelling SOS, just asking for some tips as what I have tried hasn't worked. All the same I do appreciate everyones opinions and help they provide. THat's what makes this forum great.

why would you need to heimdall if you are on a rogers infuse? Isn't that for AT&T phones only?

teknhard said:
I've flashed lots of roms and never had any issues. Also looked through the forum and know the basics about getting back to stock. I'm no expert, but I have a decent idea what I'm doing. I do appreciate a forum you can ask questions though and have people help out when your stumped. I did what i could from the tools I have at my disposal here, and ran into some problems. I'm not yelling SOS, just asking for some tips as what I have tried hasn't worked. All the same I do appreciate everyones opinions and help they provide. THat's what makes this forum great.
Click to expand...
Click to collapse
I apologize wasn't directed to you just in general and your correct this forum is great...

Then reflash ics lol
Sent from my SGH-I997 using xda premium

threi_ said:
why would you need to heimdall if you are on a rogers infuse? Isn't that for AT&T phones only?
Click to expand...
Click to collapse
Because I don't have access to a PC for Odin, and the at&t should work to get me out of brick state. I currently can't get past rogers boot screen
GoSooners345 said:
Then reflash ics lol
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
I don't have recovery.. otherwise I certainly would have

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

Can't access the settings section of my Atrix 2

So I've been reading the noob guide all day (To which, literally nothing in it has worked for me, I just want to get my phone onto ICS) and in the process of attempting to start over, I launch my phone into AP fastboot and it always says Flash Failure, RSD Lite doesn't recognize the phone other than being connected, and when I boot back into my phone normally, I can't even get to the settings section, it just gives me an error

First things first, i am assuming you on AT&T?
And are you currently on the ics leak?
Need to know these things to help ya.
But don't fret, this is fixable.
Sent from my MB865 using xda premium

Fall of Enosis said:
First things first, i am assuming you on AT&T?
And are you currently on the ics leak?
Need to know these things to help ya.
But don't fret, this is fixable.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I'm going to sound like a total tool, but I actually figured out what I was doing wrong, I forgot to patch my FXZ file so it just kept messing up everytime. Once I did that everything went flawlessly
my next issue to tackle is to understand how bootmenu works and how I "reboot" into it
otherwise I guess this topic is pointless/can be closed

[Q] Help, SHG-I727R might be bricked

Hello, I have had a Samsung Galaxy S II LTE from Rogers for three months now and it suddenly stopped working after trying to make a phone call.
The firmware was the Gingerbread 2.3.6 I believe (The most current firmware before ICS for the SGH-I727R)
There has been a history of attemping to install Cyanogenmod 10, but I had Clockwork Recovery installed and I was never able to install Cyanogenmod 10 because it gave me errors.
So I used Odin and an official release from Rogers to restore back to Gingerbread.
A month later, this is where I am at.
Status:
I can boot as far as the Carrier logo before going blank and vibrating every 2 - 3 seconds
I can go into download and recovery mode for 5 seconds before being met with a quick flash of a blue screen.
The phone randomly vibrates when a battery is inserted, when it is being charged, or a combination of the two
The battery needs to be taken out and placed back in before attempting a normal, download or recovery boot.
I also do not know if Samsung can tell, as there is no Clockwork Mod or any left over roms or Superuser permissions.
What should I do? Thanks!

If you do a battery pull and reinsert it, does the phone start to boot on it's own without any button pushs
Sent from my SGH-I727 using xda premium

xbladeinc said:
Hello, I have had a Samsung Galaxy S II LTE from Rogers for three months now and it suddenly stopped working after trying to make a phone call.
The firmware was the Gingerbread 2.3.6 I believe (The most current firmware before ICS for the SGH-I727R)
There has been a history of attemping to install Cyanogenmod 10, but I had Clockwork Recovery installed and I was never able to install Cyanogenmod 10 because it gave me errors.
So I used Odin and an official release from Rogers to restore back to Gingerbread.
A month later, this is where I am at.
Status:
I can boot as far as the Carrier logo before going blank and vibrating every 2 - 3 seconds
I can go into download and recovery mode for 5 seconds before being met with a quick flash of a blue screen.
The phone randomly vibrates when a battery is inserted, when it is being charged, or a combination of the two
The battery needs to be taken out and placed back in before attempting a normal, download or recovery boot.
I also do not know if Samsung can tell, as there is no Clockwork Mod or any left over roms or Superuser permissions.
What should I do? Thanks!
Click to expand...
Click to collapse
You should read the stickies that people invested much time into helping.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

stoopendis said:
If you do a battery pull and reinsert it, does the phone start to boot on it's own without any button pushs
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
Yes, it boots on its own. If I plug it in, it shows the battery icon for a moment and then goes to black.

xbladeinc said:
Yes, it boots on its own. If I plug it in, it shows the battery icon for a moment and then goes to black.
Click to expand...
Click to collapse
Sounds like a stuck power button. I'd try pushing it on and off a ton and see if that clears it. Reinserting the battery shouldn't do anything until you push the power button. If all else fails.... Bring it back.
Sent from my SGH-I727 using xda premium

stoopendis said:
Sounds like a stuck power button. I'd try pushing it on and off a ton and see if that clears it. Reinserting the battery shouldn't do anything until you push the power button. If all else fails.... Bring it back.
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
I will keep on trying that. Any more ideas? Should I send it in to Rogers or send it to mobiletechvideos.com for their J-TAG service?

xbladeinc said:
I will keep on trying that. Any more ideas? Should I send it in to Rogers or send it to mobiletechvideos.com for their J-TAG service?
Click to expand...
Click to collapse
It's not bricked. This phone we have is notorious for power button issues... Not your fault.. Let Rogers deal with it!
Is there a Rogers store near by where you can take your phone?
Sent from my SGH-I727 using xda premium

stoopendis said:
It's not bricked. This phone we have is notorious for power button issues... Not your fault.. Let Rogers deal with it!
Is there a Rogers store near by where you can take your phone?
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
Yeah, I am going to take it there tomorrow. Would they be able to tell if I have previously rooted my phone before in this case? I know that it is an official firmware on here now, but still. Thanks for the help!

xbladeinc said:
Yeah, I am going to take it there tomorrow. Would they be able to tell if I have previously rooted my phone before in this case? I know that it is an official firmware on here now, but still. Thanks for the help!
Click to expand...
Click to collapse
Just show them how it starts to boot on it's own. They should recognize the issue. If the phone never fully boots they can't see what's on there. And if you've never used Odin then the flash counter has never been incremented.
Sent from my SGH-I727 using xda premium
---------- Post added at 05:06 PM ---------- Previous post was at 05:05 PM ----------
Btw... Your welcome!
Sent from my SGH-I727 using xda premium

stoopendis said:
Just show them how it starts to boot on it's own. They should recognize the issue. If the phone never fully boots they can't see what's on there. And if you've never used Odin then the flash counter has never been incremented.
Sent from my SGH-I727 using xda premium
---------- Post added at 05:06 PM ---------- Previous post was at 05:05 PM ----------
Btw... Your welcome!
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
I have used Odin a few times, but I cleared all my caches, reformated and etc. using Clockwork Recovery with ICS, then I installed the Gingerbread Rom. This was a month ago, so idk.
If I can't even get into it, then it should be fine. Right?

xbladeinc said:
I have used Odin a few times, but I cleared all my caches, reformated and etc. using Clockwork Recovery with ICS, then I installed the Gingerbread Rom. This was a month ago, so idk.
If I can't even get into it, then it should be fine. Right?
Click to expand...
Click to collapse
Right. You gotta start somewhere. Just claim ignorance...... You got the official update and bam!
Sent from my SGH-I727 using xda premium

xbladeinc said:
I have used Odin a few times, but I cleared all my caches, reformated and etc. using Clockwork Recovery with ICS, then I installed the Gingerbread Rom. This was a month ago, so idk.
If I can't even get into it, then it should be fine. Right?
Click to expand...
Click to collapse
Once they unstick that button they'll see everything. They might not care, if they do you'll be paying for a new phone.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

xcrazydx said:
Once they unstick that button they'll see everything. They might not care, if they do you'll be paying for a new phone.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
The thing is about this is that I don't have it Clockwork Recovery installed nor is it rooted, so I don't know if they would be able to tell.

xbladeinc said:
The thing is about this is that I don't have it Clockwork Recovery installed nor is it rooted, so I don't know if they would be able to tell.
Click to expand...
Click to collapse
if you restored to stock w/odin then you are fine, it wipes over previous roms/recoveries/rooting and "no one" would be able to see that you had previously installed custom roms or that the phone was rooted.
using odin does "not" increase the flash counter, using certain modified stock firmware like k0anes stock rom which you would use odin to install would increase your flash counter, but thats from an old thread and no one else has made a odin flashable stock rom since then, all the latest recovery flashable roms(zip files) would not increase the flash counter.
you are good to go for warranty repair, maybe wipe your internal sdcard if you can and take out your sdcard

My phone is currently experiencing same problem as the OP. :crying: Please don't tell me bringing it back to Rogers is the only option. My 1 year warranty might be expired already.

A quick update. I went to the store and they said that they would take it. They tried to fix the button with an exacto knife. I wasn't ready to send it in yet so I waited a few hours. I tried again and I was able to boot it properly. So, there is nothing wrong with the software. To those who might be having the same issues, check your power button first before sending it in.
Thanks for the help!

xbladeinc said:
A quick update. I went to the store and they said that they would take it. They tried to fix the button with an exacto knife. I wasn't ready to send it in yet so I waited a few hours. I tried again and I was able to boot it properly. So, there is nothing wrong with the software. To those who might be having the same issues, check your power button first before sending it in.
Thanks for the help!
Click to expand...
Click to collapse
They fixed it.?.... With a exacto knife?
Sent from my SGH-I727 using xda premium

To Juude90
Hi I had a similar issue. I'ts most likely the power button. If you're willing to open up the device and clean the power button area try that.
If you're still under warranty, try to send it in for a repair.
Here is some info on my situation:
http://forum.xda-developers.com/showthread.php?t=1993616
Here is info that was helpful to me.
vincom said:
its 99% the power button, hearing it click is no indication thats its working as its an internal problem, theres 3 links to the problem in the "info" section in the "1 stop" sticky in my sig . taking it apart to get to the internal contact is one way to fix it, maybe the only way to fix it. if phone starts as soon as you put the battery in w/out touching any buttons then its a sticky/failed power button. warranty repair is also another solution
its 1% for a battery and/or battery contact problem
here are the links:
[INFO] Skyrocket randomly restarts and vibrates at 2 second intervals ...... possible sticky power button and solution
[INFO] Another thread with a bootloop problem
[INFO] Video of Skyrocket randomly restarts and vibrates at 2 second intervals />
Click to expand...
Click to collapse
I hope it helps.

stoopendis said:
They fixed it.?.... With a exacto knife?
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
Yeah, that's what I was thinking. I was wondering what the hell they were doing. It worked I guess, but sometimes it still randomly reboots. I will send it in when I have the time, I'm not in a rush.
Yeah, Rogers acted in an unprofessional manner.

Take it in to Rogers,
I just had mine serviced and returned from Rogers, No problems and free of charge.
I dropped it off to Rogers with TWRP recovery/CM10 still installed, and the reason it was broken was I used a screwdriver to remove my sim card and tore out the sim card slot from the motherboard. Totally my fault. Also, my skyrocket is a used one from ebay, no less. Did not get it new from rogers myself.
Rogers fixed, no problems or cost to me. Rogers kindly restored it to a rogers Firmware, which I promptly removed immediately.
Heeter

Phone wont boot after rom install

I install slimroms 4.2.1 stable rom and went to reboot phone and now i cant boot it up. I tried getting into recovery or download mod by holding Home power and volume up or down but nothing happens. The screen just remains off. Is there a way around this or is it done?

Remove then reinstall the battery. Then try again. Cal you get into download mode?
Sent from my Nexus 7 using Tapatalk 2

search for how to fix a hard brick you mightve flashed a rom for a different carrier dude, something like that. if you cant boot into odin than its probably hard bricked. try leaving it for awhile and go back to it later, sometimes technology is weird like that. i doubt it though..

sob372 said:
search for how to fix a hard brick you mightve flashed a rom for a different carrier dude, something like that. if you cant boot into odin than its probably hard bricked. try leaving it for awhile and go back to it later, sometimes technology is weird like that. i doubt it though..
Click to expand...
Click to collapse
Well I'll be honest I looked at SD card and I flashed and i9300 rom on it. I've tried leaving battery and stuff but the phone just won't power on. Screen just remains off. When I plug into computer with battery out a red light comes on and phone tried to install a driver but doesn't install and Odin doesn't see. I have Samsung drivers installed so i don't know what it's trying to install. Am I screwed? Throw phone away? Lol

Google jtag. I don't think there's another way to get your phone fixed. Flashing an international rom is the surest way to hard brick.
Sent from my SCH-I535 using xda app-developers app

bobAbooE said:
Google jtag. I don't think there's another way to get your phone fixed. Flashing an international rom is the surest way to hard brick.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I head jtag doesn't work anymore after 2.3 android or maybe it was the jig I was reading about.

http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
Hopefully someone will have another way to fix it but I'm pretty sure jtag is the only way.
Sent from my SCH-I535 using xda app-developers app