[Q] Am I screwed - AT&T Samsung Galaxy S II Skyrocket SGH-I727

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.

Related

Well damn, seems I've bricked.

Tonight I flashed the leaked i9000 GB and when I was done I tried to flash to stock with Odin and thats the last my phone has done anything. My phone is completely unresponsive. Black screen with no response to USB or 3button or anything. So I'm going to go cause a rukus at ATT in the morning when they open and hopefully I'll have a nice new Captivate tomorrow lol.
Just thought I'd share.
USB Jig?
Well from my research it seems that since my phone won't do ANYTHING then its a bootloader issue so a JIG won't work.
ih4ckback said:
Well from my research it seems that since my phone won't do ANYTHING then its a bootloader issue so a JIG won't work.
Click to expand...
Click to collapse
Jig will fix it.
ryude said:
Jig will fix it.
Click to expand...
Click to collapse
Really? well I guess I'll head to radioshack and try that first. I'd love to not have to deal with ATT.
Hmm . Im on gb now. Havnt flash stock yet
Sent from my GT-I9000 using XDA Premium App
Yup. Same here. LOL. Damned leaked GB. I think it's because it's a development snapshot, so it might not be very stable yet.. Or they DID lock the bootloader with it. I'm not sure. I find it weird, since I've flashed tons of crap, and this is the one that bricks my captivate. I just ordered a jig. Thank god my brother had a Captivate, and he's friendless so I'm using his phone for now.
You need to watch what you flash. Most newer leaks contain bootloaders that will brick your device if you try to flash back to something substantially older.
Yep I know. lol.
If it helps, when I flashed to the leaked GB, I couldn't access download mode with the new 3 button comb after I (noobishly) tried to boot into clockworkmod recovery from rom manager. I had to hold down both vol up+down as well as power, and the instant it turned off, I switched to holding down only vol down and power, which got me into download mode.
Having similar issues.
No matter what I try, I cannot get past the Galaxy S logo. I can send ADB commands but the download command simply reboots the phone.
Device manager also sees it as a Nexus S now instead of a Captivate, not sure if this affects how ADB sends commands.
well at least you can do something with your phone lol.
If adb sees as a nexus, it probably wasnt a real galaxy s leak
That's why it is nice to have a jig even if you never had a need for it, just one time it pays for itself.
that's what I'm hoping lol I'm going to head over to radioshack as soon as they open at 10 lol.
Yea flash stock works for me..just like any i9k rom
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
ih4ckback said:
that's what I'm hoping lol I'm going to head over to radioshack as soon as they open at 10 lol.
Click to expand...
Click to collapse
If the jig doesn't work, then you are gonna have to see if ATT will do a swap or something.
is there any reason to think that the jig won't work?
There is always that chance.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
ih4ckback said:
is there any reason to think that the jig won't work?
Click to expand...
Click to collapse
People have reported that it didn't work in that situation. Im pretty sure you need a jtag but it can't hurt to try.
I was hard bricked once after a bad flash so I was in the same position as you. I didn't have a jig at the time to test so I just brought it in to AT&T and said the ota update bricked it. They replaced it with a refurbished one with no questions asked.
Sent from my GT-I9000 using XDA App

[q] bricked....help!!!

ok.. was running oo9.m kernal and cwmtouch.. flashed qickwiz..thought i did a full swipe but there was no option to wipe boot..?....all was going well untill i seen my previouse home page taking turns flashing in and out with quikwiz.. so i rebooted back into recovery ... did a wipe again.. but unfortunatly i wiped the rom as well.... my sd card will never back up in cwm?. is it cause its to small..4gb?.. all my nanbackups say no data....i then ported to windows.xp via usb and put my skyrocket in download odin mode... for sum reason my odin file says bad file...as i was holding my phone i pressed volume and power key on accident and it went dead.....now my computer still beeps when skyrocket plugged in ..but no power.. vibrate or life for that matter.. i have uckj2. 1727 stock file downloaded az well as super stockbzip...is there still hope?.. if anyone can give me instructions with links provided i would find it very easy to donate to anyone of your causes or developments.. thank you....
So your computer is still acting like it's connecting to the skyrocket when you plugin the USB cable? If this is the case, can you access anything on your phone? Can you access either of the drives internal/sd card?
$100 says his battery is dead .. LOL
JeffreyLee .. suggestion, since this could possible be your 5th bricked phone since starting this what, 1 week !!! Sorry to say it .. GIVE UP .. very soon, AT&T will catch on to what you are doing to these phones .. and hate to tell you, they will catch on .. and you will be stuck with a bricked phone.
LordGeek said:
$100 says his battery is dead .. LOL
JeffreyLee .. suggestion, since this could possible be your 5th bricked phone since starting this what, 1 week !!! Sorry to say it .. GIVE UP .. very soon, AT&T will catch on to what you are doing to these phones .. and hate to tell you, they will catch on .. and you will be stuck with a bricked phone.
Click to expand...
Click to collapse
agreed. I thought he was just trolling at first, but unfortunately it seems to be a lack of attention to detail.
yes i can access my sd card contents...is there away to unbrick.. cant get odin to verify.
I thought you finally had things worked out in another thread. Go to the dev section then to sticky. All in one. One of the members here put alot of time and effort into given info. So do some reading and googling.
Sent from my SAMSUNG-SGH-I727 using xda premium
Smh when isheeps go baaaaaaaaad. Lol
Sent from my SAMSUNG-SGH-I727 using Tapatalk
nrm5110 said:
Smh when isheeps go baaaaaaaaad. Lol
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Click to expand...
Click to collapse
Lol priceless

[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

[Q] Hard Bricked GS3

Hello, I just got my new GS3 yesterday. Eager to root and ROM and all the fun stuff. I rooted and unlocked, and used Odin to flash CWM Recovery. Flashed the latest version of Android Revolution HD 16. I wiped cache, dalvik, the whole 9 yards. I did not WIPE boot.img though. Flashed Android Revolution 16, it all went good. Clicked Reboot Phone in CWM Recovery and nothing. No LED light on when plugged into USB or via wall charger. No Download mode, or recovery. Nothing, like nothing at all. Anything you guys suggest?
EDIT: I am not sure if it is Hard Bricked. When I plug it into my PC, it makes a sound. Also tries to install a driver and fails every time.
EDIT2: Okay guys, my fault. Downloaded a ROM that was meant for a different model/type GS3 forum when I have a Verizon GS3 (SCH-1535). Anyone know how to fix this problem? Please disregard this incorrect forum post.
If you flashed anything related to the international S3, Google search J-tag! Or return the device and play dumb...
droidstyle said:
Google search J-tag! Or return the device and play dumb...
Click to expand...
Click to collapse
I am paying for full coverage every month too, and okay, couldn't I also get a Usb JIG to force download mode?
T Greezy said:
I am paying for full coverage every month too, and okay, couldn't I also get a Usb JIG to force download mode?
Click to expand...
Click to collapse
No read my edited post. You most likely hardbricked your device, meaning you no longer have download mode.
droidstyle said:
No read my edited post. You most likely hardbricked your device, meaning you no longer have download mode.
Click to expand...
Click to collapse
Well, I NOW have a red LED on my phone when it is plugged into the PC without battery, sd card, or sim card. Is that a good sign?
T Greezy said:
Well, I NOW have a red LED on my phone when it is plugged into the PC without battery, sd card, or sim card. Is that a good sign?
Click to expand...
Click to collapse
No that verifies what i previously posted.
droidstyle said:
No that verifies what i previously posted.
Click to expand...
Click to collapse
I have faith, thought. I can maybe push something using ADB you think?
You need J-tag.
If there was a way to fix it yourself, nobody on here would worry about bricked phones.
Gotta be super careful and read every single word of a ROM thread and if you aren't sure if it will work for your phone or not, just ask and someone will say either yes or no
Sent from my SCH-I535 using xda app-developers app
josh995 said:
You need J-tag.
If there was a way to fix it yourself, nobody on here would worry about bricked phones.
Gotta be super careful and read every single word of a ROM thread and if you aren't sure if it will work for your phone or not, just ask and someone will say either yes or no
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I guess so. I read something about plugging the phone into the pc without the battery so the red light would come on. Then, you would hold a combination of buttons, and while you're still holding them, put the battery back in while you're still holding them. I guess J-Tag is the only way? Where can I get this? Someone link me. Thanks!
T Greezy said:
I guess so. I read something about plugging the phone into the pc without the battery so the red light would come on. Then, you would hold a combination of buttons, and while you're still holding them, put the battery back in while you're still holding them. I guess J-Tag is the only way? Where can I get this? Someone link me. Thanks!
Click to expand...
Click to collapse
Look like I'm going to drop 60 bucks for a JTAG service? Anyone please stop me if this is not the only way to fix this
email me at [email protected]!
No one is going to stop you. You flashed an international ROM on an s3. This is a known method of hard bricking your s3.
Sent from my SCH-I535 using xda app-developers app
T Greezy said:
Look like I'm going to drop 60 bucks for a JTAG service? Anyone please stop me if this is not the only way to fix this
email me at [email protected]!
Click to expand...
Click to collapse
That sounds about right. Luckily it's $60 and not $600 for a new phone
Sent from my SCH-I535 using xda app-developers app
Same thing happened to me. Needed a j-tag but risked calling Verizon told them my phone wouldn't come on all they asked me was if I damaged it with water or heat. (Either Verizon doesn't care or actually they just scrap the phone) I was rooted and unlocked but flashed the wrong carrier rom. Now I have a replacement phone that cost me $0.
They sent me the 16g and not the 32g by mistake I figured I've pushed my luck enough
Sent from my SCH-I535 using Tapatalk 2
First go to Get.cm download a d2vzw rom. Put it on your sd card. Put the sd card into phone
If you have ADB on your computer do
Code:
adb reboot recovery
You should boot in Clockwork Recovery.
From there flash the D2VZW Rom, Wipe Data,
That should save you.
ericerk said:
First go to Get.cm download a d2vzw rom. Put it on your sd card. Put the sd card into phone
If you have ADB on your computer do
Code:
adb reboot recovery
You should boot in Clockwork Recovery.
From there flash the D2VZW Rom, Wipe Data,
That should save you.
Click to expand...
Click to collapse
How do you figure? How can you adb recovery when the device wont turn on? The device is hardbricked plain and simple...your advice is simply false hope.
I do have a question for the op and the other guy who flashed an international ROM. Were did you get them and how did you find then ( like was it a site you googled?) I've noticed a lot of these lately and am wondering if it's something that can be avoided (besides the obvious read what you're flashing)
To the adb guy there us no recovery on his phone it was overwritten by part of the international ROM. he needs to JTAG his phone, don't call Verizon. You did this to your own phone, pay the 60 and learn your lesson.
Sent from my SGS3 running Eclipse 2.1
droidstyle said:
How do you figure? How can you adb recovery when the device wont turn on? The device is hardbricked plain and simple...your advice is simply false hope.
Click to expand...
Click to collapse
One day someone is going to find a way to unbrick the hard brick, lol. Eventually. Anyways, if it was "dead" then why would it show my S3 as "QHSUSB_DLOAD"? and attempts to install a driver. I'm gonna try to find the right driver to manually install, and troubleshoot from there. I mean come on guys, be optimistic. How great if this problem was RESOLVED? Also, the download mode got wiped/overwritten from a different ROM for a different model of the GS3. What about the Recovery? CWM? If I can just magically, somehow, maybe even push some type of command. Even maybe ADB? Or something in the terminal. I'm really trying to find a solution. So in the future, we will have a SOLUTION.
Anyways, I'm going to be shipping my GS3 Monday or Tuesday for Samsung to repair (If they can) or replace for no charge!
Wish me luck guys, gonna be really thinking out of the box.
Hope you can figure it out. But someone had a way to fix a hard brick.... The JTAG
Sent from my SGS3 running Eclipse 2.1
Okay guys, I've actually have gotten some good progress, I hope! I came across a thread that a guy named (therockk) he also, hard bricked his S3. Sent him a PM, and he told me he got ODIN to recognize his hard bricked S3 "WITHOUT" download mode. He said he found a driver for QHSUSB_DLOAD and manually applied the driver update. His PC, then recognized his S3 as a ID CODE: COM10 - I do not know what that means, I asked around. Some people say that it is the code for when your phone is connected in Download Mode? Nevertheless, this is good in my eyes. The phone as now, recognized as COM10 in ODIN, in its hard-bricked stage. This could be that also, maybe, the phone will be recognized in ADB/Fastboot commands. Maybe we can get something going here guys! I'm trying to look on the bright side. I'll keep you posted.
EDIT: Okay guys, was looking at some screenshots of the CODE ID's. Like I said, my buddy "therockk" said he got ODIN to recognize his phone as a COM10, while being hard-bricked. I am guessing there are different CODE ID's for each model/version of the S3. I did make an observation that he, has a different model S3 ( i747 ) and he got his to see COM10. Which means it was Added!! - My Verizon S3 (SCH-1525) should come up as COM4 when the PC recognizes it. When I do get my PC to recognize my S3, I will confirm that my SCH-1535 phone comes up as COM4, if not, I will confirm the correct CODE ID. therockk's i747 came up as a COM10, that is confirmed.
EDIT 2: Okay guys! Updated the driver successfully! QSHUSB_DLOAD is now Qualcomm HS-USB QDLoader 9008 (COM8). I feel like we're getting closer. Now to see if Odin will pick it up!
I can probably help you through this problem after work tonight if you are still having trouble. Just pm me around 10pm est
Sent from my SCH-I535 using xda app-developers app

[Q] bricked and terrified 4.3

okay i upgraded to 4.3 OTA and tried to revert back and soft bricked my phone. I still have access to download mode and the stock recovery. I know now that i can not revert but is there any way of getting it back to 4.3 so i can have a phone again?
thanks for the future help.
This is similar what happened to me. I have never done anything with my phone as far as rooting and I tried reverting to stock 4.1.2. In Odin I kept getting the "Nand Start! Fail (Auth)" because of the locked bootloader I guess. I flashed some other firmware that was unofficial with the locked bootloader and now I get the "unauthorized software detected" and I cant do anything but enter Odin download mode. What should I do?
that is exactly what is happing to me. same error and all.
Once you took the OTA 4.3 you got locked in. No way of going back.
Sent from my SCH-I535 using Tapatalk
I dont want to go back just get rid of the soft brick so i can use it
im having the same problem and need to get it fixed please help anyone???!!!! im leaving for florida in two days and have nothing else. HELP!!!!
If you took the OTA and tried to flash 4.1.2 Odin or unlock bootloader you are Hard bricked , no method or recovering it yet.
If you have stock recovery and download mode , only hope is wait for 4.3 .tar file
Theres no custom recovery I can flash and flash some other software or something?
Elemt said:
Theres no custom recovery I can flash and flash some other software or something?
Click to expand...
Click to collapse
Nope , once you take 4.3 OTA you done , no flashing anything. And once you try to flash recovery or revert to older software you are bricked.
Sorry to be the bear of bad news.
There is a full thread of why and how so many devices have been bricked
http://forum.xda-developers.com/showthread.php?t=2575661
jlyle said:
Nope , once you take 4.3 OTA you done , no flashing anything. And once you try to flash recovery or revert to older software you are bricked.
Sorry to be the bear of bad news.
There is a full thread of why and how so many devices have been bricked
http://forum.xda-developers.com/showthread.php?t=2575661
Click to expand...
Click to collapse
Do you know if anyone is working on a fix? or a .tar file of 4.3?
dvdavid2 said:
Do you know if anyone is working on a fix? or a .tar file of 4.3?
Click to expand...
Click to collapse
Thanks for the info. hopefully a fix will be done soon. And do you know how i should keep to see when the work around is finished .
thanks in advanced guys.
This might give you a chance to unbrick.... possibly
http://forum.xda-developers.com/showthread.php?t=2581166
I got the "unauthorised software detected" on my phone like 3 days ago from messing up on a recovery and all I did was go into the Verizon store and said idk what happened and they called technical support and they asked me if I flashed software on my phone and I just said "no, I just plugged it into my laptop and it did this" so they said they will just send me a new sgs3 and I just got it today.
Pretty simple.
And I don't have insurance .
Hit thanks if I helped
Sent from my SCH-I535 using xda app-developers app
ScubaSteev said:
I got the "unauthorised software detected" on my phone like 3 days ago from messing up on a recovery and all I did was go into the Verizon store and said idk what happened and they called technical support and they asked me if I flashed software on my phone and I just said "no, I just plugged it into my laptop and it did this" so they said they will just send me a new sgs3 and I just got it today.
Pretty simple.
And I don't have insurance .
Hit thanks if I helped
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Funny thing is Verizon can tell if phone was hacked with, and can choose to add the cost of phone to your bill so this method is not highly recommended.
Sent from my SCH-I535 using xda app-developers app
jlyle said:
Funny thing is Verizon can tell if phone was hacked with, and can choose to add the cost of phone to your bill so this method is not highly recommended.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Any break throughs????
dvdavid2 said:
Any break throughs????
Click to expand...
Click to collapse
None that I have seen
Sent from my SCH-I535 using xda app-developers app
jlyle said:
Funny thing is Verizon can tell if phone was hacked with, and can choose to add the cost of phone to your bill so this method is not highly recommended.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Not to mention it is basically fraud, and is the main reason Verizon decided to start locking down phones in the first place.
I understand everyone is taking risks when flashing custom, and flashes can go wrong even when you do everything right, but there is VERY little chance of bricking your phone if you take your time and do a bit of research before you hit any buttons. And if you do manage to brick your phone, man up and pay for a new phone or pay for it to be fixed. Otherwise stop treating your $600 piece of technology like a toy.
BattsNotIncld said:
Not to mention it is basically fraud, and is the main reason Verizon decided to start locking down phones in the first place.
I understand everyone is taking risks when flashing custom, and flashes can go wrong even when you do everything right, but there is VERY little chance of bricking your phone if you take your time and do a bit of research before you hit any buttons. And if you do manage to brick your phone, man up and pay for a new phone or pay for it to be fixed. Otherwise stop treating your $600 piece of technology like a toy.
Click to expand...
Click to collapse
The first time I ever rooted, I was worried about bricking. So i read everything I could find relevant.
Why in the world anyone would flash without reading is beyond me. Every single thread in Verizon Galaxy S3 at least mentions, if not totally devoted, to how bad 4.3 is and if you flash something on it you will brick.
I just don't get it.
Sent from my Last Ever Samsung Device.
If you do a battery pull and start back up in download mode (might take a couple of times to get it to work) then use the Verizon software upgrade assistant it should fix it but you will be stuck with 4.3. Worked for me

Categories

Resources