Hello all,
I recently rooted my Galaxy S3 only to have my Mic fail on me 2 weeks later... Very dissatisfied with my Samsung about that - even though I am loving the phone. Anyways, back to the issue. Verizon has agreed to send me a replacement and I have to send them mine back. The problem is that I know that if I send them a rooted phone they will not honor the warranty, and I am having a very hard time flashing the Verizon Stock rom.
More specifically, and to see if I am doing anything wrong.. I used ODIN to flash a custom rooted rom onto my phone which worked perfectly, and now I am once again trying to use ODIN in order to flash the stock rom which I downloaded from goo.im - the file that I am using is HOME_I535VRALF2_I535VZWALF2_618049_REV09_user_low_ship.tar.md5
Simple steps - reboot into downloading mode -> check auto-reboot and reset time on ODIN and choose the file above under PDA. All works fine, the phone reboots and I get a PASS, and yet my phone is stuck on the Verizon 4G loading intro. I think that's what they call a soft brick.
The first time this happened, I flashed a different rom and the phone loaded properly but it had the open lock symbol under Samsung which I think means that it was unlocked.. Either way, it was not the unrooted and official stock rom which is what I need on my phone in order to keep my warranty. The file that DOES work is COMBINATION_I535VRBLJ1_I535VZWBLJ1_381038_REV09_user_low_ship(NO_WIPE).tar.md5
I have followed the above steps over and over again and I always get the same result - stock doesn't work, the other one does.
Any ideas? What could the issue be?
http://forum.xda-developers.com/showthread.php?t=1762709
Personally I would try the files found in section 5 of this thread.
According to Droidstyles guide before his recent edits, if it freezes on the boot logo after a successful Odin factory flash then you're supposed to pull the battery, boot into recovery, and do a factory reset. Try that.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
According to Droidstyles guide before his recent edits, if it freezes on the boot logo after a successful Odin factory flash then you're supposed to pull the battery, boot into recovery, and do a factory reset. Try that.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yes this works, also had this happen to me, and to boot to recovery just hold home+volume up+power button. It should work.
Sent from my SCH-I535 using xda premium
You should probably factory reset after flashing, for you don't want to be running a buggy phone.
Sent from my Nexus 7 using xda app-developers app
Use a full wipe version and this would not happen...part of the reason why i removed nowipe versions such as f2. But yes as slimsnoop said, data wipe /factory reset will fix that.
So I bought the s3 Verizon it was rooted and switched to cricket pre paid before my friend sold it to me he tried to root back to Verizon but of course he failed, is there anyway to get the phone completelyback to stock even though he switched providers cuz the phone is stuck on the activating part I'm no noobe at rooting just don't know much bout this phone
Sent from my LT28at using xda app-developers app
FhtmChandley85 said:
is there anyway to get the phone completelyback to stock even though he switched providers cuz the phone is stuck on the activating part I'm no noobe at rooting just don't know much bout this phone
Sent from my LT28at using xda app-developers app
Click to expand...
Click to collapse
Follow section 5 of Droidstyle's (the guy above you) guide. Click the link in his signature. I'm not sure about how this handles modified network configuration though, that's not something I remotely know anything about.
I thought there was a way to bypass the activation screen? On older phones, you could tap the four corners of the screen or something like that? Anyone ever heard that before?
Sent from my SCH-I535 using xda app-developers app
Related
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
So, yesterday, I had a perfectly functioning, stock 4.1.1/rooted unit.
Got a little frisky and decided to try out Liquid Smooth. Flashed that through recovery (it's a 4.2.1 Beta 2) but forgot to do the bootlocker.
The latest LS has a Bluetooth sound problem that's pretty bad. So, I thought I'd switch over to CM10.1, their 4.2.1 effort.
Well, without the bootlocker in place, you can pretty much guess how that worked out.
So now, I've odin'ed a variety of roms and so forth; no clue what happened to my backup.
My main focus has been what I call the dunce-cap routine, of going back to stock and starting over.
The problem? I did that and now I'm stuck in roaming mode and my calls don't work.
I'm dead without this phone (considering how long I've been working on this, since 8 pm or so yesterday except for a couple of hours of sleep, I might be dead, period.) and I've got to have one functioning. It's so bad that I'm considering just trashing it and buying another one, even thought THAT would hurt.
Almost everything I try winds up either getting the yellow triangle or the odin fail.
Now, thanks to some help I've gotten here that focused me into understanding this total screw up is MY fault completely, I believe I know what has to be done.
The plan was to go back to stock, root and DO THE DAMNED BOOTLOCKER, then go back into CM10.1 and make some changes in subscribing to CDMA or something (don't have that in front of me this second) to get the phone part of the phone operational but I can't get there.
In the guide here I have completed step 1, flashing the factory image.
The next step is blowing me up. I have used the file I have for the Recovery: CWM6023TouchVZW.tar.md5.tar, maybe 4 times.
NOW when I try it, odin fails and the phone tells me "secure check fail : recovery."
And help would be appreciated. Before I feed this thing to my Doberman Cavalier Spaniel. Or something.
Have you tried Odin with a completely stock rom?
Sent from my SCH-I535 using xda app-developers app
Jarredw said:
Have you tried Odin with a completely stock rom?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yup. Completely stock rom is installed. The next step was installing the recovery... and using a file that I had used before, that's where I'm running into the problem of the secure check fail.
That very file HAS worked before, 3 or 4 times with no problem.
Why does the file end in ".tar.md5.tar"? It's supposed to end in ".tar.md5" Since owning this phone, I've never seen a file with ".tar" twice in the file name.
Sent from my SCH-I535 using xda app-developers app
kage87z said:
Yup. Completely stock rom is installed. The next step was installing the recovery... and using a file that I had used before, that's where I'm running into the problem of the secure check fail.
That very file HAS worked before, 3 or 4 times with no problem.
Click to expand...
Click to collapse
Disregard that, I'll be back in a minute with some help. I'm pretty sure the new boot chain will not except custom recovery. Try this guide.
http://forum.xda-developers.com/showthread.php?p=35418324
Sent from my VS920 4G using xda app-developers app
If you were able to Odin a stock rom then Odin a stock rom that has been pre rooted and then just use ez recovery from the play store to flash cwm
Sent from my SCH-I535 using xda app-developers app
kintwofan said:
Disregard that, I'll be back in a minute with some help. I'm pretty sure the new boot chain will not except custom recovery. Try this guide.
http://forum.xda-developers.com/showthread.php?p=35418324
Sent from my VS920 4G using xda app-developers app
Click to expand...
Click to collapse
OK.... working this.
Looks good. Booted into the rom with no warnings... It says "pass."
Jarredw said:
If you were able to Odin a stock rom then Odin a stock rom that has been pre rooted and then just use ez recovery from the play store to flash cwm
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
this was going to be my suggestion also.
ddurandSGS3 said:
this was going to be my suggestion also.
Click to expand...
Click to collapse
Any suggestions as to where I might get one of those?
The 5 minute time limit can be a PITA.
SlimSnoopOS said:
Why does the file end in ".tar.md5.tar"? It's supposed to end in ".tar.md5" Since owning this phone, I've never seen a file with ".tar" twice in the file name.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
The problem is that when I unzip it, I don't get an md5 file, I get an "image" file of some sort.
kage87z said:
Any suggestions as to where I might get one of those?
The 5 minute time limit can be a PITA.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1974114
Sent from my SCH-I535 using xda app-developers app
Update: OK... have gone through the guide which went brilliantly.
Now, do I just boot this thing into recovery and flash the CM10.1?
Is there anything I've overlooked? Anything else I need to do?
And do I do the factory reset/wipe dalvik and the rest before, or after?
I presume I have to use ezlock to unlock the bootloader again after this, right?
No, you still need to unlock bootloader and backup your IMEI. You may want to do quite a bit of reading, CM 10 is not as easy to fix some of the potential problems that you could possibly encounter.
I am not hating on them, but don't think it is as simple as one of the TW ROMS.
HHF2 said:
No, you still need to unlock bootloader and backup your IMEI. You may want to do quite a bit of reading, CM 10 is not as easy to fix some of the potential problems that you could possibly encounter.
I am not hating on them, but don't think it is as simple as one of the TW ROMS.
Click to expand...
Click to collapse
When I try this method to back up the IMEI it doesn't do anything after entering the *#7284# and if I hit the phone, it just sends me to a Verizon intercept operator.
The only reason I'm trying to get into a 4.2.1 ROM again was this:
http://forum.xda-developers.com/showpost.php?p=36396278&postcount=5
Just flash cm10.1 and fix your mobile settings. CDMA subscription > ruim/sim and toggle airplane mode.
This isn't the first time someone has had this problem.
Sent from my SCH-I535 using xda app-developers app
4.1.1 doesn't have this capability, and up to now, I haven't seen any other way to address the original issue.
Of you followed the guide I linked you are unlocked with cwm so boot into recovery wipe caches and reset and flash cm10.1 and gapps. First verify you are unlocked
Sent from my VS920 4G using xda app-developers app
kintwofan said:
Of you followed the guide I linked you are unlocked with cwm so boot into recovery wipe caches and reset and flash cm10.1 and gapps. First verify you are unlocked
Sent from my VS920 4G using xda app-developers app
Click to expand...
Click to collapse
OK, using EZLock I unlocked it successfully, but the status in EZLock is still listed as "unknown."
kage87z said:
The only reason I'm trying to get into a 4.2.1 ROM again was this:
http://forum.xda-developers.com/showpost.php?p=36396278&postcount=5
Just flash cm10.1 and fix your mobile settings. CDMA subscription > ruim/sim and toggle airplane mode.
This isn't the first time someone has had this problem.
Sent from my SCH-I535 using xda app-developers app
4.1.1 doesn't have this capability, and up to now, I haven't seen any other way to address the original issue.
Click to expand...
Click to collapse
If you can't figure it out you can pm me
Sent from my SCH-I535 using xda app-developers app
kage87z said:
OK, using EZLock I unlocked it successfully, but the status in EZLock is still listed as "unknown."
Click to expand...
Click to collapse
Just power on your phone if Samsung flashes very fast you're unlocked
Sent from my VS920 4G using xda app-developers app
kintwofan said:
Just power on your phone if Samsung flashes very fast you're unlocked
Sent from my VS920 4G using xda app-developers app
Click to expand...
Click to collapse
OK... it did... I'm going for it.
Stuck on "waiting for network."
Used the four taps method to get past it
I have no APN listed..
kage87z said:
OK... it did... I'm going for it.
Stuck on "waiting for network."
Used the four taps method to get past it
I have no APN listed..
Click to expand...
Click to collapse
Have you changed the subscription type to sim and toggled airplane mode
Sent from my VS920 4G using xda app-developers app
I just hard bricked my sgs3. FIRST TIME EVER!! I've been flashing roms,kernels, etc since the MyTouch3.
Little back story.....
I flashed the LSmooth - Linaro 4.2.1 Jelly Bean Rom with CWM6. I noticed that I could not find my nandroid backups. Searched XDA and saw a thread that stated that TWRP is compatible with 4.2.1 and it will move the internal /sdcard from /0 back to its original file location, etc, etc. I went to GooManager, downloaded the twrp.tar (d2vzw), then went to MobileOdin, loaded the .tar file and flashed.
BOOM!!! No power, DOA. dead ass!! :crying::crying:
(( FACE SLAP )) then I remembered via build.prop it was configured as "maguro" and not "d2vzw". So, I'm assuming that since I failed to edit the build.prop before flashing the d2vzw TWRP recovery, it bricked my phone.
-- No power via wall, usb
-- No download / recovery mode
-- NOTHING!
My question is, if I were to call in and ask for a warranty exchange, what is the likely hood of Verizon troubleshooting, reviving my phone and figuring it out that its been rooted?
Or, should I just send my phone to someone that can JTAG it for me?
Idk if you're permanently hard bricked. Reason being is because this person flashed the latest twrp using GooManager but it installed the Maguro version. Different method but they were able to get out of it. Have you tried pulling the battery then booting holding all three buttons for like 15-20 seconds? Might take a few tries.
Verizon could care less I think.
I have had three droid razrs replaced just because of a boot loop and if they would look into the memory, they could clearly see I rooted if.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Idk if you're permanently hard bricked. Reason being is because this person flashed the latest twrp using GooManager but it installed the Maguro version. Different method but they were able to get out of it. Have you tried pulling the battery then booting holding all three buttons for like 15-20 seconds? Might take a few tries.
Click to expand...
Click to collapse
I saw that post, lol. I tried that, but I will try it again. thanks
barrackOBAMA said:
Verizon could care less I think.
I have had three droid razrs replaced just because of a boot loop and if they would look into the memory, they could clearly see I rooted if.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Cool! Thanks!
MOD Close Thread, pls
MOD,
Can you close this thread please. Got my replacement today, so I'm Good.!!
So after seeing KitKat in action, I hunted down an Android phone eligible for a KitKat ROM. I traded my iPhone for a Verizon Samsung Galaxy S3 (i535) I got it rooted and CWM on it just fine, and the boot loader unlocked. (or so I thought) Went into recovery and did all the steps to install the ROM, got it installed, along with G-Apps and rebooted. My phone came to a screen saying
"system software not authorized by Verizon wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
As far as I can tell, the boot loader was not successfully unlocked. So, it's back to stock ROM via Odin, right? :laugh:
NO! All the guides I find say to download an app to reset the binary counter. How do I do that if I have no OS to boot to?
Any Ideas? Did my enticement for KitKat get the best of me?
You shouldn't need triangle away to Odin back to stock. Triangle away would be for if you were trying to take your phone back to Verizon or Samsung for warranty work and didn't want them to know it was previously rooted.
Sent from my SCH-I535 using xda app-developers app
dustin_b said:
You shouldn't need triangle away to Odin back to stock. Triangle away would be for if you were trying to take your phone back to Verizon or Samsung for warranty work and didn't want them to know it was previously rooted.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
O, thanks for clearing that up. So what's my next step to getting it back to a working phone?
jcaauwe said:
O, thanks for clearing that up. So what's my next step to getting it back to a working phone?
Click to expand...
Click to collapse
Follow the instructions in section 5 of this guide: http://forum.xda-developers.com/showthread.php?t=1762709. This will get you back to stock and unrooted. Then you will have to do the root unlock processs again.
Sent from my SCH-I535 using xda app-developers app
dustin_b said:
Follow the instructions in section 5 of this guide: http://forum.xda-developers.com/showthread.php?t=1762709. This will get you back to stock and unrooted. Then you will have to do the root unlock processs again.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
and or use the casual all in one tool and follow root, and flash insecure aboot then download Rom manager from google play and install latest CWM
I just had my s3 replaced under warranty. The new one, I used casual to root/unlock, etc. Worked great! I think I let casual install everything then flashed CM from recovery.
Sent from my SCH-I535 using xda app-developers app
jcaauwe said:
O, thanks for clearing that up. So what's my next step to getting it back to a working phone?
Click to expand...
Click to collapse
Not sure what you are trying to achieve, but once you get it back to functional and rooted, I would recommend you try out some of the wonderful custom TouchWIz ROMs on the forum here. They have most of if not more features than are in Kit Kat and there are no fully functional Kit Kat ROMSs for the S3 yet. Plus thse ROMs are stable and all your Samsung features will work properly . MORA, Hyperdrive, Synergy, and Jelly "beans" are good examples of excellent ROMs.
So I figured out what went wrong, and I'm still kicking myself for how stupid of problem it was. The reason Odin didn't want to work was because I was using the front USB ports on my system, which are not USB 2.0... I spent 6 hours trying to figure it out. So I hooked it up to a rear USB port, flashed it back to stock ROM, redid the Root, unlocked bootloader (which I didn't do in the first place) and now I'm getting Cyanogenmod on it.
Thanks everyone for the help! I hope anyone else who comes across this who where in the same boat I was can figure it out.
Sometimes it's a user-error.
Fix
jcaauwe said:
So after seeing KitKat in action, I hunted down an Android phone eligible for a KitKat ROM. I traded my iPhone for a Verizon Samsung Galaxy S3 (i535) I got it rooted and CWM on it just fine, and the boot loader unlocked. (or so I thought) Went into recovery and did all the steps to install the ROM, got it installed, along with G-Apps and rebooted. My phone came to a screen saying
"system software not authorized by Verizon wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
As far as I can tell, the boot loader was not successfully unlocked. So, it's back to stock ROM via Odin, right? :laugh:
NO! All the guides I find say to download an app to reset the binary counter. How do I do that if I have no OS to boot to?
Any Ideas? Did my enticement for KitKat get the best of me?
Click to expand...
Click to collapse
i know you say you are ROOT but why dont you check using ROOT CHECKER download it from the play store its gonna tell you if you are root or not. im using sspencer10 KITKAT 4.4 CM11 and is running pretty smooth why don't you try it out just download the .zip reboot into RECOVERY i preffer you use TWRP (last version) go to whipe>advanced wipe and clear, Dalvik Cache>System>Data>Cache (optional i alwayz check mark Internal storage looking for space and alwayz make a clean flash same as Format Data) make sure you backup everything first using Titatinium Backup go back, then go to Install search for your .zip file on ur SDCard or Internal Storage first select the ROM ADD MORE FILE and add the GAPPS click REBOOT SYSTEM AND ENJOY YOUR NEW KITKAT 4.4 CM11 ON YOUR SGS3.
Don't be scared of Kit Kat! Once u get ur issues figured out and get 4.4 up and running you will see its all worth it!
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