[Q] Is it possible to unroot Verizon gs3 with cracked digitizer? - Verizon Samsung Galaxy S III

I rooted my Verizon gs3 using Saferoot (I think). I dropped the phone and cracked the screen and digitizer (phone will power on but can't see anything on the screen). I've received my insurance replacement phone and have to send the cracked one back. Is there any way to unroot the phone before I return it? I did trade for the phone used so I could plead ignorance and say that the previous owner must have done it if Verizon catches it. TIA

cdput said:
I rooted my Verizon gs3 using Saferoot (I think). I dropped the phone and cracked the screen and digitizer (phone will power on but can't see anything on the screen). I've received my insurance replacement phone and have to send the cracked one back. Is there any way to unroot the phone before I return it? I did trade for the phone used so I could plead ignorance and say that the previous owner must have done it if Verizon catches it. TIA
Click to expand...
Click to collapse
Look for a program that will display your screen through the computer.
Or you could simply flash a stock 4.4.2 rom through download mode, then everything looks like it hasn't been touched. Download mode is easy to get into and you don't need a working screen.
Sent from my HTC6525LVW using Tapatalk

Thanks! I'll have to do some research on getting into download mode or if you can please point me to a guide. I've never flashed a rom to my phone (although I have thought about it). The main thing that I've ever needed has been root to be able to use the wifi tethering.

cdput said:
Thanks! I'll have to do some research on getting into download mode or if you happen to be able to point me to a guide. I've never flashed a rom to my phone (although I have thought about it). The main thing that I've ever needed has been root to be able to use the wifi tethering.
Click to expand...
Click to collapse
Power off phone, then it's power +volume down +home. Once it boots, give it a minute then hit volume up. You can verify you're in download mode if Odin recognizes your phone.
Sent from my HTC6525LVW using Tapatalk

BadUsername said:
Power off phone, then it's power +volume down +home. Once it boots, give it a minute then hit volume up. You can verify you're in download mode if Odin recognizes your phone.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Thanks again! I am a complete noob when it comes to Odin so I'll research. I mess with this type stuff strictly for myself and just to see if I can. So I don't do it often. I normally don't ask questions unless I just can't seem to find the answers on my own.

cdput said:
Thanks again! I am a complete noob when it comes to Odin so I'll research. I mess with this type stuff strictly for myself and just to see if I can. So I don't do it often. I normally don't ask questions unless I just can't seem to find the answers on my own.
Click to expand...
Click to collapse
Check the softbrick repair guide, instructions are completely laid out for you, just make sure you use a 4.4 rom not the included 4.3 rom.
Sent from my HTC6525LVW using Tapatalk

BadUsername said:
Check the softbrick repair guide, instructions are completely laid out for you, just make sure you use a 4.4 rom not the included 4.3 rom.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Thanks so much!

Related

Bricked

Just picked up my G3, rooted and unlocked bootloader as soon as i got home. Downloaded one of the jelly bean roms and cwm, did a backup then flashed the rom. Everything looked fine but the screen went dark after the boot animation then nothing. Wont power up or reset using the power home volume combo. What the heck do i do now, thanks for any help.
Might be a stupid question, but have you pulled the battery?
Be more specific.
VZW GALAXY S 3 4G LTE
Do YOUR homework first
How about reading all the threads about unbricking. It certainly seems you did not read all the threads about rooting the phone. Do that too.
Finally, and I know this is not that helpful. Don't screw with a new phone. Use it at least for a month to make sure there are no problems with it.
That being said, there is plenty of information about how to handle your problem here in xda. Read all that and try what has already been posted before asking people to solve your self inflicted problem.
BTW when you do ask for help specify exactly what you did, with what script. I.E. don't ask someone to solve your problem without you taking the time to be very specific about how you got there.
pull the battery and go into recovery or odin and fix it.
Dead battery?
Sent from my Transformer TF101 using xda premium
Skubacb - Don't be a douche buddy. If you do not have any thing to add then shut the **** up.
With that being said I have been rooting phones for years, never had an issue when I couldn't get the phone to at least go into recovery. The phone is dead. Battery was fully charged and I have done a battery pull. It is a Verizon G3. I have read the unbrick articles but none explain if the phone will not boot into recovery. If someone could could just point me in the correct direction I would greatly appreciate it.
How did you actually do the flash? Odin? Some other way? As noted, more details are needed.
I flashed the new rom using Rom manager, went in to revovery and flashed it
jmill75 said:
I flashed the new rom using Rom manager, went in to revovery and flashed it
Click to expand...
Click to collapse
I don't believe rom manager is supported for our phone yet. U need to flash straight from recovery. That said I'm sorry I'm not sure where u go from here.
Sent from my SCH-I535 using xda premium
If you can't get into either recovery , or download mode you maybe SOL. However I would take this to IRC and see if someone can help on there. #verizons3 channel.
If the phone is under warranty, one other alternate solution is to take it into a VZW store and say it won't start. Of course I'd only go that route if I couldn't get it going any other way. On the plus side, your could at least confirm that battery didn't die on you.
Looks like you forgot to flash the insecure bootloader, buddy.
Sent from my SCH-I535
Rom manager is supported I flashed clockwork there And the 3 cm nightlies
Sent from my SCH-I535 using Tapatalk 2
Keep this discussion to technical solutions only, please. Leave gray area ethics out of it.
JMink said:
I don't believe rom manager is supported for our phone yet. U need to flash straight from recovery. That said I'm sorry I'm not sure where u go from here.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Completely incorrect.
mikeew83 said:
Rom manager is supported I flashed clockwork there And the 3 cm nightlies
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Me too, been doing it since 6.0.1.2
abissel22 said:
Looks like you forgot to flash the insecure bootloader, buddy.
Sent from my SCH-I535
Click to expand...
Click to collapse
I'm gonna go with this one (possibly). Did you unlock the phone? Sorry, did you say it won't boot into anything? Download/Odin mode? Recovery? Anything at all when you do the vol up/down, home key, and power button?
Idk if this would help but I'd order a downloader jig off ebay for a couple dollars and use that to see if it'll boot to recovery
Sent from my GT-I9300 using xda app-developers app
Me too
I went to turn on my Verizon SGS3 on this morning and nothing happened. I have not even rooted it yet. It was charged when I turned it off 5 minutes before that and even did a battery swap. Phone is completely dead. Will not turn on. I have had it since it first came out, so I called Verizon and they are over-nighting me a "like-new" one. I hope I don't hear more of these stories.
jmill75 said:
Just picked up my G3, rooted and unlocked bootloader as soon as i got home. Downloaded one of the jelly bean roms and cwm, did a backup then flashed the rom. Everything looked fine but the screen went dark after the boot animation then nothing. Wont power up or reset using the power home volume combo. What the heck do i do now, thanks for any help.
Click to expand...
Click to collapse
I had a similar issue. If you do the volume/home/power combo (try both volume buttons separately, i forgot which one worked) and hold them through the initial Samsung logo it should put you into download mode, where you can Odin back to stock. I used PureMotive's Unbrick method in the Dev section (I think) and it took all of 20 min. Just make sure to follow the directions carefully.
Sent from my SCH-I535 using xda app-developers app
Is there a difference is button sequence between recovery and download mode? (I thought it was the same thing)
Sent from my SCH-I535 using XDA Premium App

[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

Flashed My Phone Incorrectly Now It Won't Boot

I was following a tutorial on rooting my Galaxy S3 and by mistake I loaded the "VRALEC.bootchain.tar.md5" file under the boot loader option rather than the PDA option.
This was the tutorial "How To Root Verizon Samsung Galaxy S3 4.1.2/4.1.1 & Install CWM Recovery! SCH-I535."
Now my phone won't boot at all and isn't being recognized by my computer when plugged in. Any help with this is greatly appreciated!
dsims9t said:
I was following a tutorial on rooting my Galaxy S3 and by mistake I loaded the "VRALEC.bootchain.tar.md5" file under the boot loader option rather than the PDA option.
This was the tutorial "How To Root Verizon Samsung Galaxy S3 4.1.2/4.1.1 & Install CWM Recovery! SCH-I535."
Now my phone won't boot at all and isn't being recognized by my computer when plugged in. Any help with this is greatly appreciated!
Click to expand...
Click to collapse
If your phone doesn't power on at all no led, no recovery or download access, no vibration even, then I'm afraid by putting the VRALEC.bootchain.tar.md5 in the wrong spot and flashing it through Odin you have hard bricked your phone. At this point warranty would be your best option.
Sent from my SCH-I535 using xda premium
shimp208 said:
If your phone doesn't power on at all no led, no recovery or download access, no vibration even, then I'm afraid by putting the VRALEC.bootchain.tar.md5 in the wrong spot and flashing it through Odin you have hard bricked your phone. At this point warranty would be your best option.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Dude he voided his warranty by rooting so JTAG is best option.
jmxc23 said:
Dude he voided his warranty by rooting so JTAG is best option.
Click to expand...
Click to collapse
Dude...
If anyone at Verizon has any clue why a phone won;t turn on , then you might be right, but they don;t and they don;t have the time to worry with it, so they will just replace it if its less than a year old.
DigitalMD said:
Dude...
If anyone at Verizon has any clue why a phone won;t turn on , then you might be right, but they don;t and they don;t have the time to worry with it, so they will just replace it if its less than a year old.
Click to expand...
Click to collapse
That part is true.
So there's absolutely no way to recover it at this point. I didn't get a warranty on it specifically because I was planning on running Cyanogenmod.
It has a 1 year warranty that Verizon will honor
Sent from my SCH-I535 using xda app-developers app
dsims9t said:
So there's absolutely no way to recover it at this point. I didn't get a warranty on it specifically because I was planning on running Cyanogenmod.
Click to expand...
Click to collapse
No, there is a way to recover it. There just is not a fixable way via xda. Third party services such as MobileTechVideos can fix your phone via jtag as a few others suggest.
dsims9t said:
So there's absolutely no way to recover it at this point. I didn't get a warranty on it specifically because I was planning on running Cyanogenmod.
Click to expand...
Click to collapse
If you don't have a warranty on your device the only other real option is to use JTAG to revive the phone. I would recommend checking out this place that will repair your bricked Galaxy S3 for you.
Seems to be an almost daily occurrence. Reading a new thread because someone can't follow directions and bricking their phone.
Sent from my SCH-I535 using xda premium
bbqsfire said:
Seems to be an almost daily occurrence. Reading a new thread because someone can't follow directions and bricking their phone.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
He was simply asking if it could be fixed, which is kind of what this section is for. I personally would've asked the same question if it happened to me because I haven't seen any questions based on this specific chain of events. He just put the file in the wrong slot, could happen to people, now this specific question will be able to be searched for by people who actually search.
So to answer the question, your bootloader is kind of your essential command for your phone that starts the booting process. You basically erased that with a file that doesn't execute that process. Luckily a jtag is able to rewrite that entire command. I think it's only $60, which is well worth the cost.
Sent from my SCH-I535 using Tapatalk 2

[Q] bricked,hard bricked?

i just used that stupid ez unlock app. my phone needed to be rebooted so I rebooted it. I tried turning it on but theres nothing. I take the battery out and the red light turns on for like a minute then turns back off. I put the battery in and connect it to my laptop and it recongnizes it but I don't know if I can put it in download mode. can someone please help????:crying:
foton92 said:
i just used that stupid ez unlock app. my phone needed to be rebooted so I rebooted it. I tried turning it on but theres nothing. I take the battery out and the red light turns on for like a minute then turns back off. I put the battery in and connect it to my laptop and it recongnizes it but I don't know if I can put it in download mode. can someone please help????:crying:
Click to expand...
Click to collapse
That sound like a hard brick but it cant hurt to try to put it in download mode and see if odin sees it. Just keep trying until it works or you get sick of doing it.
edit
Never mind I didn't read your post good enough. That's weird but i stand by my try statement. Never hurts to try try again especially when you cant see if you pushed the buttons at the right time or not.
If the led lights up red there is still hope. You need a class 10 SD card the exact same size as your internal memory and Google debrick.IMG for the S3. I cannot remember the link at the monument but it is possible to bring it back from the dead at this state.
Sent from my GT-N5110 using xda app-developers app
foton92 said:
i just used that stupid ez unlock app. my phone needed to be rebooted so I rebooted it. I tried turning it on but theres nothing. I take the battery out and the red light turns on for like a minute then turns back off. I put the battery in and connect it to my laptop and it recongnizes it but I don't know if I can put it in download mode. can someone please help????:crying:
Click to expand...
Click to collapse
I'm not even sure a debrick image will fix it. If you were on stock 4.3 and used ez-unlock you basically screwed up your bootchain by flashing an incompatible bootloader.
You flashed an insecure aboot image that won't work with the 4.3 bootchain. Using the debrick image probably won't work in this instance. You can try to send it in for a jtag, but that might not work either.
Apparently a jtag should theoretically work because there shouldn't be a qfuse on the s3. If this happened on an s4 for instance, there's probably no way to recover from this situation. If a jtag can rewrite your base commands, you should be able to get it working again. However, it's very possible that a jtag won't work either.
Anyone reading this who has 4.3, please read everything over and over again before you root the device or do anything with it.
1. Once on 4.3 you are unable to revert back to an earlier version.
2. You are unable to use custom roms because our previous bootloader unlock involved using an old aboot image to bypass the kernel check, 4.3 needs the entire boot chain to function and modifying it in any way will cause an instant hard brick.
3. Do not use ez-unlock!! The entire purpose of it is to flash the modified aboot file to allow custom roms and kernels to boot, this will cause an instant brick by breaking the 4.3 bootloader.
Sent from my SCH-I535 using Tapatalk 2
Eodmule said:
If the led lights up red there is still hope. You need a class 10 SD card the exact same size as your internal memory and Google debrick.IMG for the S3. I cannot remember the link at the monument but it is possible to bring it back from the dead at this state.
Sent from my GT-N5110 using xda app-developers app
Click to expand...
Click to collapse
I just ended up sending my phone to samsung and luckily I didn't get charged. Know what NOT to do. Anyway thanks guys
Sent from my SCH-I535 using xda app-developers app
foton92 said:
I just ended up sending my phone to samsung and luckily I didn't get charged. Know what NOT to do. Anyway thanks guys
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
So you couldn't man up and pay for your mistake? Insurance fraud is wrong. This is why VZW lock our bootloaders
Sent from my SCH-I535 using Tapatalk
Sandman-007 said:
So you couldn't man up and pay for your mistake? Insurance fraud is wrong. This is why VZW lock our bootloaders
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
It was not really insurance fraud. I told them my phone won't turn on and I sent it in. They said my phone was still under warranty so they fixed it for free and they ended up changing the logic board instead of replacing the whole phone. If they were going to charge me. I would pay for it just so I could get my phone back. But I just got lucky on this one and they said it was free
Sent from my SCH-I535 using xda app-developers app
Sandman-007 said:
So you couldn't man up and pay for your mistake? Insurance fraud is wrong. This is why VZW lock our bootloaders
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I just got the feeling that next time I do this. Samsung will catch my ass and charge me for what I've done to the phone. So for now this was a lesson learned. Don't use unheard of apps that need root access to your device
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