Related
Hey folks, I've been doing some reading on the topic this morning and found some good options but need a few more specifics and maybe some extra expert opinion. Something is awry with my USB port - It will charge but cannot get it to recognize the presence of the computer. It also goes through seasons where it rapidly toggles back and forth to/from dock mode.
Basic facts/stats:
SGS3 verizon, SCH-I535, running 4.0.4 I535VRLF2.
Rooted, Stock ROM, never unlocked bootloader.
Running CWM Recovery v5.5.0.4
I'm trying to restore to a point where I can do a warranty return for the hardware issue without being dinged for software mods.
So I think my options are these.. Feedback?
Mobile Odin... but don't want to unlock the bootloader, seems to be a step in the wrong direction.
ABD Wifi
Terminal emulator on the phone
Here's a thread that I found helpful...
http://forum.xda-developers.com/showthread.php?p=27206637&postcount=5
So, finally, my questions that I haven't been able to find an answer to...
Anyone know where can I find the stock recovery image? Not hard to find an image for the whole system, but why flash the whole kit'n'kabodle when you only need the one part?
If I was going to go the ABD/terminal route, is this the correct command? dd if=location of image of=/dev/block/mmblk0p22. This is the location for the Galaxy S2, but not sure if it is correct for S3.
Thanks guys, definitely don't want to make a mistake here in this crippled situation.
xaris1 said:
Hey folks, I've been doing some reading on the topic this morning and found some good options but need a few more specifics and maybe some extra expert opinion. Something is awry with my USB port - It will charge but cannot get it to recognize the presence of the computer. It also goes through seasons where it rapidly toggles back and forth to/from dock mode.
Basic facts/stats:
SGS3 verizon, SCH-I535, running 4.0.4 I535VRLF2.
Rooted, Stock ROM, never unlocked bootloader.
Running CWM Recovery v5.5.0.4
I'm trying to restore to a point where I can do a warranty return for the hardware issue without being dinged for software mods.
So I think my options are these.. Feedback?
Mobile Odin... but don't want to unlock the bootloader, seems to be a step in the wrong direction.
ABD Wifi
Terminal emulator on the phone
Here's a thread that I found helpful...
http://forum.xda-developers.com/showthread.php?p=27206637&postcount=5
So, finally, my questions that I haven't been able to find an answer to...
Anyone know where can I find the stock recovery image? Not hard to find an image for the whole system, but why flash the whole kit'n'kabodle when you only need the one part?
If I was going to go the ABD/terminal route, is this the correct command? dd if=location of image of=/dev/block/mmblk0p22. This is the location for the Galaxy S2, but not sure if it is correct for S3.
Thanks guys, definitely don't want to make a mistake here in this crippled situation.
Click to expand...
Click to collapse
Your on ICS. I would just use EZ-unlock 1.2 and unlock. Takes about about 30 seconds. If flash counter is tripped use free Triangle Away here on XDA to reset it. Another minute. Then use Mobile Odin to flash back full stock image. About 10 minutes. Done.
xaris1 said:
Hey folks, I've been doing some reading on the topic this morning and found some good options but need a few more specifics and maybe some extra expert opinion. Something is awry with my USB port - It will charge but cannot get it to recognize the presence of the computer. It also goes through seasons where it rapidly toggles back and forth to/from dock mode.
Basic facts/stats:
SGS3 verizon, SCH-I535, running 4.0.4 I535VRLF2.
Rooted, Stock ROM, never unlocked bootloader.
Running CWM Recovery v5.5.0.4
I'm trying to restore to a point where I can do a warranty return for the hardware issue without being dinged for software mods.
So I think my options are these.. Feedback?
Mobile Odin... but don't want to unlock the bootloader, seems to be a step in the wrong direction.
ABD Wifi
Terminal emulator on the phone
Here's a thread that I found helpful...
http://forum.xda-developers.com/showthread.php?p=27206637&postcount=5
So, finally, my questions that I haven't been able to find an answer to...
Anyone know where can I find the stock recovery image? Not hard to find an image for the whole system, but why flash the whole kit'n'kabodle when you only need the one part?
If I was going to go the ABD/terminal route, is this the correct command? dd if=location of image of=/dev/block/mmblk0p22. This is the location for the Galaxy S2, but not sure if it is correct for S3.
Thanks guys, definitely don't want to make a mistake here in this crippled situation.
Click to expand...
Click to collapse
The same thing happened with my first S3, I used mobile odin and flashed back to stock and sent it into verizon for my replacement and this was a couple months ago. I would suggest that route.
Can't post outside links yet, but search for this on youtube..
How To Unroot Galaxy S3 Verizon/AT&T/Sprint/T-mobile - Flash Stock Rom & Fix Warranty
http://www.youtube.com/watch?v=vVVHRyDb4IQ
Nice little video guide for mobile odin.
Have you tried a different USB cable? I've had the same problem and a new cable worked wonders.
Sent from my SCH-I535 using xda app-developers app
cmb3497 said:
Have you tried a different USB cable? I've had the same problem and a new cable worked wonders.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Several, and the cables work with my old phone w/ no problems. Reinstalled the samsung drivers. I'm pretty sure that it's the USB due to the issue with rapid toggling in/out of dock mode. A quick squirt of compressed air fixes the dock mode issue but there are still periodic re-occurrences.
Downloading the stock firmware now. I'll keep you all posted. Thanks a ton for the advice.
Try the xperia x8 drivers. I can't get the Samsung ones to connect for anything. I haven't had an issue since ditching the Samsung ones.
I had the same problems, constant toggling. Just my opinion, it's a driver issue.
Sent from my SCH-I535 using xda app-developers app
prdog1 said:
Your on ICS. I would just use EZ-unlock 1.2 and unlock. Takes about about 30 seconds. If flash counter is tripped use free Triangle Away here on XDA to reset it. Another minute. Then use Mobile Odin to flash back full stock image. About 10 minutes. Done.
Click to expand...
Click to collapse
THANKS man, your guidance got me there without a hitch. Really appreciate it. Samsung is shipping me a new S3, now this one will be ready to return.
bobAbooE said:
Try the xperia x8 drivers. I can't get the Samsung ones to connect for anything. I haven't had an issue since ditching the Samsung ones.
I had the same problems, constant toggling. Just my opinion, it's a driver issue.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Gave it a try but it didn't work. Thanks anyway man.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
So I had a Galaxy S1 Captivate for about 2 year and my wife has a Fascinate and I rooted/flashed them both like it was my job for the last couple years. I never once hard bricked either and for the most part knew what I was doing. I have a couple home made jigs so DL mode or (soft bricks) were never an issue. My question to you guys is I'm trying to gauge how difficult/risky is it to root and rom the GS3 (Verizon model specifically). The reason I'm wondering this info is because I personally don't own my GS3, it is property of my company and I don't want to chance bricking or not being able to easily flash back to stock unless it has gotten easier or less risky since the original Galaxy lineup. I mean if you had 2.3 bootloaders on your GS1 and you had access to a jig, there was pretty much a 0% chance of hard bricking unless you do something really stupid. Sorry for rambling on!
jayjr1105 said:
So I had a Galaxy S1 Captivate for about 2 year and my wife has a Fascinate and I rooted/flashed them both like it was my job for the last couple years. I never once hard bricked either and for the most part knew what I was doing. I have a couple home made jigs so DL mode or (soft bricks) were never an issue. My question to you guys is I'm trying to gauge how difficult/risky is it to root and rom the GS3 (Verizon model specifically). The reason I'm wondering this info is because I personally don't own my GS3, it is property of my company and I don't want to chance bricking or not being able to easily flash back to stock unless it has gotten easier or less risky since the original Galaxy lineup. I mean if you had 2.3 bootloaders on your GS1 and you had access to a jig, there was pretty much a 0% chance of hard bricking unless you do something really stupid. Sorry for rambling on!
Click to expand...
Click to collapse
I came from the Fascinate and this phone is just as easy to flash. Just make sure you read the OP and only flash things made for the US versions and you'll be fine. If something gets hosed, you can always odin back. Here is a great guide to get you started.
http://forum.xda-developers.com/showthread.php?t=1762709
Sent from my SCH-I535 using xda app-developers app
Deliquified said:
I came from the Fascinate and this phone is just as easy to flash. Just make sure you read the OP and only flash things made for the US versions and you'll be fine. If something gets hosed, you can always odin back. Here is a great guide to get you started.
http://forum.xda-developers.com/showthread.php?t=1762709
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I haven't checked that link out yet but how easy is it to go back to the Verizon stock ROM if need be?
Does the ROM procedure go something like this?...
Power Off, DL mode with jig, ODIN a CWM or Kernel package with CWM, mount SD, drag and drop ROM, Flash, win?
well...
well the good news is that you don't have to flash a custom rom for root. I just rooted and unlocked my phone while still running the stock rom. =) i'd post my tutorial but I'm a new member and I have 8 more posts to do before I can post in development.
eorly420 said:
well the good news is that you don't have to flash a custom rom for root. I just rooted and unlocked my phone while still running the stock rom. =) i'd post my tutorial but I'm a new member and I have 8 more posts to do before I can post in development.
Click to expand...
Click to collapse
There is already an in depth tutorial for that as well as one for those who have the recent OTA.
http://forum.xda-developers.com/showthread.php?t=2046439
The above link is those with the jelly bean OTA.
http://forum.xda-developers.com/showthread.php?t=1762709
This above is the in depth guide I was talking about. It was posted on 7/10/12. So there is no need for another tutorial unless you found a new way to do it. If you are talking about RootDebugFS then there is a tutorial for that here as well as the SuperSU version here as well.
I also came from a fascinate which was super easy to flash. As long as you read up on your homework this phone is cake to flash.
You shouldn't have many problems. If you need help, PM me. I'm glad to help.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
So I'm wondering one last thing. I hear about a "flash counter" on the GS3... anything I need to be really careful about to not trip this "counter"? Will Verizon void the warranty if tripped?
Thanks again guys!
Also, I'm going to be using this phone a lot for work and I ported my old personal number to Google Voice so this will be my personal phone as well, so I need the phone to be pretty solid and stable, should I be looking to flash Original ROMs or from the regular development section?
jayjr1105 said:
So I'm wondering one last thing. I hear about a "flash counter" on the GS3... anything I need to be really careful about to not trip this "counter"? Will Verizon void the warranty if tripped?
Thanks again guys!
Also, I'm going to be using this phone a lot for work and I ported my old personal number to Google Voice so this will be my personal phone as well, so I need the phone to be pretty solid and stable, should I be looking to flash Original ROMs or from the regular development section?
Click to expand...
Click to collapse
Once your rooted, you can download Triangle Away from the App Store and that will restore the counter to 0.
lvgdgts said:
Once your rooted, you can download Triangle Away from the App Store and that will restore the counter to 0.
Click to expand...
Click to collapse
Thanks! Do you need to run the app every time you flash or just right before you would need to take it in to Verizon for warranty/service?
jayjr1105 said:
Thanks! Do you need to run the app every time you flash or just right before you would need to take it in to Verizon for warranty/service?
Click to expand...
Click to collapse
If you unlock bootloader before you flash recovery you will not trip flash counter. If counter is tripped must use Triangle Away while still on stock rom. That being said flash counter does not affect anything except warranty and requires you to Odin stock root, run triangle Away then Odin full stock so best to fix as soon as you root and unlock to avoid extra work at time of return to Verizon.
prdog1 said:
If you unlock bootloader before you flash recovery you will not trip flash counter. If counter is tripped must use Triangle Away while still on stock rom. That being said flash counter does not affect anything except warranty and requires you to Odin stock root, run triangle Away then Odin full stock so best to fix as soon as you root and unlock to avoid extra work at time of return to Verizon.
Click to expand...
Click to collapse
Is there a way to just see if you tripped the flash counter without Triangle Away?
Just got an upgrade from my carrier (a small local carrier) and I chose the s3. Came from some Motorola peice of fail. I'm looking to root and flash an insecure bootloader but I have encountered a confusing conflict. Having a Verizon model phone with a us cellular build of android loaded. And yes I'm certain it is a Verizon model phone (google schi535mbb if you don't believe me) with us cellular stock rom loaded (with some tweeks like 4g disabled). Rom and software model say the following R530 & d2usc. Bootloader is I535VRALE6 baseband I535VRLF2. This as far as I can tell was acomplished by a company called ultimobile. Which customizes devices to function on small mobile carriers. If anybody has any ideas or suggestions on what I might try, please let me know. I just don't want to screw something up and have a brick, just coming from a device that was all but brickable.
Sent from my SCH-I535 using xda premium
Lrs121 said:
Just got an upgrade from my carrier (a small local carrier) and I chose the s3. Came from some Motorola peice of fail. I'm looking to root and flash an insecure bootloader but I have encountered a confusing conflict. Having a Verizon model phone with a us cellular build of android loaded. And yes I'm certain it is a Verizon model phone (google schi535mbb if you don't believe me) with us cellular stock rom loaded (with some tweeks like 4g disabled). Rom and software model say the following R530 & d2usc. Bootloader is I535VRALE6 baseband I535VRLF2. This as far as I can tell was acomplished by a company called ultimobile. Which customizes devices to function on small mobile carriers. If anybody has any ideas or suggestions on what I might try, please let me know. I just don't want to screw something up and have a brick, just coming from a device that was all but brickable.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Interesting. From the sound of it it may just be software blocked. Verizon root and unlock should work. The trick is gonna be finding software that will work with that carrier. If it is using straight UC Cellular may be able to run what those guys are running. If it is that small carrier that controls access then that would be the problem. Without a backup of the stock rom don't know how you would get it running again. According to the numbers it is a Verizon S3 running Us Cellular. Good luck.
prdog1 said:
Interesting. From the sound of it it may just be software blocked. Verizon root and unlock should work. The trick is gonna be finding software that will work with that carrier. If it is using straight UC Cellular may be able to run what those guys are running. If it is that small carrier that controls access then that would be the problem. Without a backup of the stock rom don't know how you would get it running again. According to the numbers it is a Verizon S3 running Us Cellular. Good luck.
Click to expand...
Click to collapse
The recovery that's on it right now has built in options for nvbackup. From what I've read that is the radio, imei, and other files used to connect to the network. I was gonna make several backups of everything as soon as I gained root control. The real problem comes down to when I go to throw cm on here. Figuring out which vzw or usc will cooperate with the carrier files.
Sent from my SCH-I535 using xda premium
Lrs121 said:
The recovery that's on it right now has built in options for nvbackup. From what I've read that is the radio, imei, and other files used to connect to the network. I was gonna make several backups of everything as soon as I gained root control. The real problem comes down to when I go to throw cm on here. Figuring out which vzw or usc will cooperate with the carrier files.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Make a nandroid backup and maybe post to see what your running as?
Sent from my SCH-I535 using Tapatalk 2
Addiso said:
Make a nandroid backup and maybe post to see what your running as?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Was definitely gonna make a nandroid, but as for 'post to see what I'm running as' what do you mean?
Sent from my SCH-I535 using xda premium
Lrs121 said:
Was definitely gonna make a nandroid, but as for 'post to see what I'm running as' what do you mean?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Maybe the build.prop?
Edit: Attach it via Pastebin!
SlimSnoopOS said:
Maybe the build.prop?
Edit: Attach it via Pastebin!
Click to expand...
Click to collapse
Here ya go. Have fun http://pastebin.com/eUj5z2VT
Sent from my SCH-I535 using xda premium
Lrs121 said:
Here ya go. Have fun http://pastebin.com/eUj5z2VT
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Looks like us cellular under the ultimobile ID?
Sent from my SCH-I535 using Tapatalk 2
Addiso said:
Looks like us cellular under the ultimobile ID?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
It's weird though right? I'm not sure how to go about suggesting how to flash roms. I have to side with prdog1 and say it's a VZW GSIII running USC. I really can't suggest a good way to proceed since it's hard to tell what you would use to revert back to stock in case of emergences.
Anyone familiar with Team US Cellular? Any input from there?
Addiso said:
Looks like us cellular under the ultimobile ID?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
thats what i saw too. the difficult thing to figure out is if to use the verizon unlock and root or the us cellular model. it is most definately a verizon model of phone just loaded up with us cell software. ive flashed verizon a based rom over a locked down motorola peice of fail, but that couldnt touch the kernel, base band, or anything but the system with out it requiring a complete reflash to stock. i dont exactly have that option if every thing screws up in the process of gaining root. id have to take it into the store and wait till they can reflash it there.
Lrs121 said:
thats what i saw too. the difficult thing to figure out is if to use the verizon unlock and root or the us cellular model. it is most definately a verizon model of phone just loaded up with us cell software. ive flashed verizon a based rom over a locked down motorola peice of fail, but that couldnt touch the kernel, base band, or anything but the system with out it requiring a complete reflash to stock. i dont exactly have that option if every thing screws up in the process of gaining root. id have to take it into the store and wait till they can reflash it there.
Click to expand...
Click to collapse
I'm fairly certain you should use the unified toolkit to root and maybe unroot. In your build.prop, I noticed it reads on the fifth line:
ro.build.version.incremental=R530UVXALK5
Click to expand...
Click to collapse
and the toolkit supports LK5 build for the d2usc. I think they're both locked down the same but on Team US Cellular's website that's what I'm seeing some people have used too. Idk about your specific case using another carrier but a d2usc GSIII but I'm thinking that's a start. Idk about returning to stock though.
Edit: Gonna add this, this means there is an Odin flashable of LK5 available somewhere.
Edit x2: POW!
SlimSnoopOS said:
I'm fairly certain you should use the unified toolkit to root and maybe unroot. In your build.prop, I noticed it reads on the fifth line:
and the toolkit supports LK5 build for the d2usc. I think they're both locked down the same but on Team US Cellular's website that's what I'm seeing some people have used too. Idk about your specific case using another carrier but a d2usc GSIII but I'm thinking that's a start. Idk about returning to stock though.
Edit: Gonna add this, this means there is an Odin flashable of LK5 available somewhere.
Edit x2: POW!
Click to expand...
Click to collapse
really i need to gain fastboot access to the phone. there are some files i need to check and i need to pull the special recovery that came with the phone. if i can do that i should be able to pull what i need from the phone to be able to return to stock. im also gonna perform an nvback up, a qpst backup and the synergy back up. but first things first i need fastboot access to the phone. i know how to get into recovery and download mode but for the life of me i cant figure out how to get to a fastboot compliant mode. from there i can figure how im gonna proceed to root.
edit: what i see in download mode
odin mode
Product name: sch--i535
custom binary download: yes (1 counts)
current binary: custom
system status: custom
Qualcom secureboot: enable
Lrs121 said:
really i need to gain fastboot access to the phone. there are some files i need to check and i need to pull the special recovery that came with the phone. if i can do that i should be able to pull what i need from the phone to be able to return to stock. im also gonna perform an nvback up, a qpst backup and the synergy back up. but first things first i need fastboot access to the phone. i know how to get into recovery and download mode but for the life of me i cant figure out how to get to a fastboot compliant mode. from there i can figure how im gonna proceed to root.
edit: what i see in download mode
odin mode
Product name: sch--i535
custom binary download: yes (1 counts)
current binary: custom
system status: custom
Qualcom secureboot: enable
Click to expand...
Click to collapse
Here's a left field suggestion, could you call this UltiMobile company and ask about what they used?
SlimSnoopOS said:
Here's a left field suggestion, could you call this UltiMobile company and ask about what they used?
Click to expand...
Click to collapse
havent done that yet. its on a list of things to do the problem is that everywhere they put information out they say to contact the carrier not them for everything. i may just have to wait till the phone isnt so new at my carrier and let the IT department play around with it for a while. i can then get information from them.
Lrs121 said:
havent done that yet. its on a list of things to do the problem is that everywhere they put information out they say to contact the carrier not them for everything. i may just have to wait till the phone isnt so new at my carrier and let the IT department play around with it for a while. i can then get information from them.
Click to expand...
Click to collapse
That's real tricky but sounds like your best option. At least you're rooted and unlocked with the VRALE6 bootloader and can debloat. Out of curiosity, what recovery are you using that has all these options?
As an aside, this table tells you where the recovery partition is. I've heard of people using dd commands to pull whatever partition they want to their sdcard but idk how viable an option this is in terms of pushing a recovery to that partition. I'm not recommending you try it either.
SlimSnoopOS said:
That's real tricky but sounds like your best option. At least you're rooted and unlocked with the VRALE6 bootloader and can debloat. Out of curiosity, what recovery are you using that has all these options?
As an aside, this table tells you where the recovery partition is. I've heard of people using dd commands to pull whatever partition they want to their sdcard but idk how viable an option this is in terms of pushing a recovery to that partition. I'm not recommending you try it either.
Click to expand...
Click to collapse
The vrale6 is unlocked? If so then why does it say that the qualcom secure boot is enabled. And I haven't rooted just yet but am working on it. Its a recovery built by ultimobile.
Sent from my Nexus 7 using XDA Premium HD app
Lrs121 said:
The vrale6 is unlocked? If so then why does it say that the qualcom secure boot is enabled. And I haven't rooted just yet but am working on it. Its a recovery built by ultimobile.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Yes indeed. VRALE6 is the prerelease bootloader that was leaked which EVERY d2vzw (d2usc I suppose too) uses in order to allow flashing of roms/kernels. It's a little weird to explain but basically everyone's Download Mode reads almost the same. Mine reads "custom binary: Samsung Official" though and I'm rooted/unlocked. Idk the technical or even the proper way to explain it but the unlocked VRALE6 bootloader has no bearing on what Download mode says. Although your custom binary should be at 0 if/when you do warranty exchanges.
SlimSnoopOS said:
Yes indeed. VRALE6 is the prerelease bootloader that was leaked which EVERY d2vzw (d2usc I suppose too) uses in order to allow flashing of roms/kernels. It's a little weird to explain but basically everyone's Download Mode reads almost the same. Mine reads "custom binary: Samsung Official" though and I'm rooted/unlocked. Idk the technical or even the proper way to explain it but the unlocked VRALE6 bootloader has no bearing on what Download mode says. Although your custom binary should be at 0 if/when you do warranty exchanges.
Click to expand...
Click to collapse
Ah makes sense now it just doesn't do a hash/encryption check. I've dealt with a lot of bootloader stuff with my old phone. the phone came like that with the count at 1. Was like that before I tried anything. Probably was triggered when the d2usc stock was flashed onto it. Which probably means I should stick with d2usc builds to ensure compatibility with connecting with my carrier.
Sent from my Nexus 7 using XDA Premium HD app
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
I'm having a bit of an issue here with my Verizon Samsung Galaxy S III where I tried to downgrade from Android 4.3 to 4.1.2. I used Odin and the 4.1.2 firmware that matches my device and when the process was finished Odin indicated that it was a failure and now my phone is not able to turn on, and gives an error message stating that "Firmware upgrade has encountered an issue. Please use Software Repair Assistant & try again." I'm not sure what Software Repair Assistant is exactly so I haven't tried anything regarding that. Also I tried entering download mode but then clicking the volume down button so that it restarts the phone.
Thanks.
protocol.code0 said:
I'm having a bit of an issue here with my Verizon Samsung Galaxy S III where I tried to downgrade from Android 4.3 to 4.1.2. I used Odin and the 4.1.2 firmware that matches my device and when the process was finished Odin indicated that it was a failure and now my phone is not able to turn on, and gives an error message stating that "Firmware upgrade has encountered an issue. Please use Software Repair Assistant & try again." I'm not sure what Software Repair Assistant is exactly so I haven't tried anything regarding that. Also I tried entering download mode but then clicking the volume down button so that it restarts the phone.
Thanks.
Click to expand...
Click to collapse
Once you are on 4.3, the bootloader is locked, you can't downgrade or install custom rom/kernel recovery. The only thing you can do is root. If you want to flash a few available rom you will need to install safestrap. Back to your issue:
SOFT BRICK - able to get to download mode
http://forum.xda-developers.com/showthread.php?t=2586319
------------------------------
HARD BRICK - phone not turn on
http://forum.xda-developers.com/showthread.php?t=2581166
buhohitr said:
Once you are on 4.3, the bootloader is locked, you can't downgrade or install custom rom/kernel recovery. The only thing you can do is root. If you want to flash a few available rom you will need to install safestrap. Back to your issue:
SOFT BRICK - able to get to download mode
http://forum.xda-developers.com/showthread.php?t=2586319
------------------------------
HARD BRICK - phone not turn on
http://forum.xda-developers.com/showthread.php?t=2581166
Click to expand...
Click to collapse
So I tried the soft brick tutorial and that seemed to have fixed the problem. I'm also interested in this safestrap you mentioned. How does it work? If I want to get something like PACMan ROM on my GS3 that runs 4.3, how do I use it in order to do that?
Currently its very limited, only works with TW ROM, so you need to wait a little bit longer since they are working on a patch for custom ROM for safestrap.
Sent from my Galaxy Nexus using xda premium
buhohitr said:
Currently its very limited, only works with TW ROM, so you need to wait a little bit longer since they are working on a patch for custom ROM for safestrap.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Any good sources where I can keep informed of the new updates?
protocol.code0 said:
Any good sources where I can keep informed of the new updates?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2618887
buhohitr said:
Once you are on 4.3, the bootloader is locked, you can't downgrade or install custom rom/kernel recovery. The only thing you can do is root. If you want to flash a few available rom you will need to install safestrap. Back to your issue:
SOFT BRICK - able to get to download mode
http://forum.xda-developers.com/showthread.php?t=2586319
------------------------------
HARD BRICK - phone not turn on
http://forum.xda-developers.com/showthread.php?t=2581166
Click to expand...
Click to collapse
I tried this method, and it did work. However, I messed something up again, and this time it won't go into download mode for some reason. Also the phone didn't come with a micro SD card so I don't have one on me.
protocol.code0 said:
I tried this method, and it did work. However, I messed something up again, and this time it won't go into download mode for some reason. Also the phone didn't come with a micro SD card so I don't have one on me.
Click to expand...
Click to collapse
What did you do to mess it up?
buhohitr said:
What did you do to mess it up?
Click to expand...
Click to collapse
I misread your indication that there is absolutely no way to downgrade from 4.3 to 4.1.2, so I tried re-downgrading back to 4.1.2 using a different tutorial (which I no longer have the link for), and this is what ended up happening to my phone.
protocol.code0 said:
I misread your indication that there is absolutely no way to downgrade from 4.3 to 4.1.2, so I tried re-downgrading back to 4.1.2 using a different tutorial (which I no longer have the link for), and this is what ended up happening to my phone.
Click to expand...
Click to collapse
OK, you just have borrow or buy a sdcard and following the hardbrick instruction a few thread up.
buhohitr said:
OK, you just have borrow or buy a sdcard and following the hardbrick instruction a few thread up.
Click to expand...
Click to collapse
How many GB should the SD card be?
The Sd card needs to be the same size as your phones internal memory. It would do you good to really read and research before messing with your phone. This particular section (Verizon s3 troubleshooting and questions) is FULL of threads about people bricking because they failed to read that you can't downgrade or you'll brick. I know that doesn't sound very nice, and please don't take it personally...It's not meant to be.
Sent from my SCH-I535 using xda app-developers app
DiSiD said:
The Sd card needs to be the same size as your phones internal memory. It would do you good to really read and research before messing with your phone. This particular section (Verizon s3 troubleshooting and questions) is FULL of threads about people bricking because they failed to read that you can't downgrade or you'll brick. I know that doesn't sound very nice, and please don't take it personally...It's not meant to be.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
How do I find out the size of my phone's internal memory? I don't know it and I don't really know how to check.
protocol.code0 said:
How do I find out the size of my phone's internal memory? I don't know it and I don't really know how to check.
Click to expand...
Click to collapse
Check the back of your phone behind the battery, the sticker will tell you
Sent from my SCH-I535 using Tapatalk 2