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
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
Here's the story:
I got excited about the bootloader vulnerability (Loki) being released, and I saw that a few devs had updated their ROMs to work with Loki so I decided to give it a shot.
The easiest, fail-free way of installing a recovery was to install TWRP through goomanager. I had only ever used CWM, but I figured it couldn't be that difficult to learn/use. And it wasn't, I'm just dumb. I went to wipe my S4 and I misunderstood what I was supposed to do and ended up formatting the phone instead. On CWM, this is normal and basically just means factory restore, but on TWRP this wipes everything, including the OS. This might not have been as big of a problem if that wipe hadn't just erased the ROM I was intending to install.
Long story short, with no OS on the phone, I was stuck on the Samsung boot screen and I could not even get into recovery. I tried ODIN restoring the stock firmware twice, but despite the fact that ODIN said "SUCCESS", my phone was in the same state. After panicking for a couple of hours :crying: and trying different things (including just leaving the phone alone for a while in hopes that I would come back and it would be magically fixed) I downloaded Kies. I figured, Kies comes directly from Samsung. If there's a way to fix my phone, this has to be it.
I did the emergency firmware recovery, and it took forever and when it was done it looked like I was going to end up right where I started, when after about a minute of the Samsung boot screen, I saw the heavenly blue-purple swish of the boot animation. :victory:
tl;dr: I thought I bricked my phone. I brought it back to life with Kies.
That's my story. Hopefully it'll help someone who is panicking that they just borked their new phone and helps them restore it.
I'm sad to say that I also wiped a phone with TWRP. It wasn't an S4 and I didn't need Kies.
I had no idea that it would delete the OS - I don't think there was even a warning.
What ROM were you going to use that supported Loki?? I can't seem to find one anywhere...
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
drucquerkellan said:
What ROM were you going to use that supported Loki?? I can't seem to find one anywhere...
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Okay, I hope it goes without saying that what you do with this is your responsibility. That being said, I was going to try:
[ROM][BETA][4.2.2][May 23] Slim Bean jflteatt [build 5.6] - LOKI patched
and here are a few more:
[ROM] Task650 AOKP(Jellybean 4.2.2)(5.23.2013)(LOKI-d) (AT&T)
[KERNEL][ATT][AOSP/TW][5/23/2013] KT-SGS4 - MDL - LOKI'd - KTweaker
CyanogenMod 10.1 Loki'd for the Galaxy S4 ATT
okzygen said:
Okay, I hope it goes without saying that what you do with this is your responsibility. That being said, I was going to try:
[ROM][BETA][4.2.2][May 23] Slim Bean jflteatt [build 5.6] - LOKI patched
and here are a few more:
[ROM] Task650 AOKP(Jellybean 4.2.2)(5.23.2013)(LOKI-d) (AT&T)
[KERNEL][ATT][AOSP/TW][5/23/2013] KT-SGS4 - MDL - LOKI'd - KTweaker
CyanogenMod 10.1 Loki'd for the Galaxy S4 ATT
Click to expand...
Click to collapse
OK thanks I'll try them in a little bit and report back here how it goes!
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
You can still mount to USB through recovery and transfer a ROM zip over and then flash it.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
okzygen said:
Here's the story:
I got excited about the bootloader vulnerability (Loki) being released, and I saw that a few devs had updated their ROMs to work with Loki so I decided to give it a shot.
The easiest, fail-free way of installing a recovery was to install TWRP through goomanager. I had only ever used CWM, but I figured it couldn't be that difficult to learn/use. And it wasn't, I'm just dumb. I went to wipe my S4 and I misunderstood what I was supposed to do and ended up formatting the phone instead. On CWM, this is normal and basically just means factory restore, but on TWRP this wipes everything, including the OS. This might not have been as big of a problem if that wipe hadn't just erased the ROM I was intending to install.
Long story short, with no OS on the phone, I was stuck on the Samsung boot screen and I could not even get into recovery. I tried ODIN restoring the stock firmware twice, but despite the fact that ODIN said "SUCCESS", my phone was in the same state. After panicking for a couple of hours :crying: and trying different things (including just leaving the phone alone for a while in hopes that I would come back and it would be magically fixed) I downloaded Kies. I figured, Kies comes directly from Samsung. If there's a way to fix my phone, this has to be it.
I did the emergency firmware recovery, and it took forever and when it was done it looked like I was going to end up right where I started, when after about a minute of the Samsung boot screen, I saw the heavenly blue-purple swish of the boot animation. :victory:
tl;dr: I thought I bricked my phone. I brought it back to life with Kies.
That's my story. Hopefully it'll help someone who is panicking that they just borked their new phone and helps them restore it.
Click to expand...
Click to collapse
all you have to do is boot to recovery, and push a rom through adb to your phone. I've done this dozens of times accidentally and the easiest way to avoid it is to keep a backup rom on your sd at all times
mcmb03 said:
all you have to do is boot to recovery, and push a rom through adb to your phone. I've done this dozens of times accidentally and the easiest way to avoid it is to keep a backup rom on your sd at all times
Click to expand...
Click to collapse
or....takeout the sdcard...put the rom on it and flash....
Sent from my SGH-I337M using xda premium
niceppl said:
or....takeout the sdcard...put the rom on it and flash....
Sent from my SGH-I337M using xda premium
Click to expand...
Click to collapse
yeah, either way kies was probably at the bottom of the list for solutions since you were trying to put a different rom on your phone anyways
niceppl said:
or....takeout the sdcard...put the rom on it and flash....
Sent from my SGH-I337M using xda premium
Click to expand...
Click to collapse
Or the easiest of the options that I already mentioned 4 posts up... Don't even need to bother with adb or taking off your back cover. Plug in, mount, click-and-drag file transfer, unmount, flash, done.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
I'm just glad you got it taken care of OP. Hopefully this thread will help others who may have a mishap while flashing ROMs.
To all of those talking about recovery... maybe I wasn't clear. It's not that I couldn't get into TWRP. I couldn't get into recovery mode at all. I could get into download mode, which is why I went the ODIN route. Whenever I would try to boot into recovery, it would show the little blue text on the top right of the screen, and the proceed to throw me right back to the booth screen.
This is incredible. Incredible how badly you almost screwed yourself over with, and incredible that Kies was actually helpful.
I installed Kies to backup contacts, once. After that? Thing crashes on updates, takes 30 minutes to load, hated any music I threw at it, didnt like my wireless transfer setting....
idk I had a pretty bad experience with Kies, i'm glad to hear that program isnt all useless.
okzygen said:
To all of those talking about recovery... maybe I wasn't clear. It's not that I couldn't get into TWRP. I couldn't get into recovery mode at all. I could get into download mode, which is why I went the ODIN route. Whenever I would try to boot into recovery, it would show the little blue text on the top right of the screen, and the proceed to throw me right back to the booth screen.
Click to expand...
Click to collapse
Yea that part doesn't make sense though. Many times I've seen people try to boot out of recovery with no system and always be able to get right back into recovery. Not that I don't believe you, just saying it's weird. Which leads me to the guy above... he didn't really screw himself that bad, no danger of bricking at all, just needed a reflash.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Just FYI on Kies
Am not sure on windows pc, but on my imac adb does not work with Kies. Had to use the Kies uninstaller to get if off imac then use adb. Maybe this isn't an issue on all phones?
Just got s4, and coming from HTC One S. So, if this is old news, sorry--
okzygen said:
To all of those talking about recovery... maybe I wasn't clear. It's not that I couldn't get into TWRP. I couldn't get into recovery mode at all. I could get into download mode, which is why I went the ODIN route. Whenever I would try to boot into recovery, it would show the little blue text on the top right of the screen, and the proceed to throw me right back to the booth screen.
Click to expand...
Click to collapse
I'm pretty sure you have to wipe cache once you do odin in order to boot back in OS or else you'll just get stuck at logo
polish_pat said:
I'm pretty sure you have to wipe cache once you do odin in order to boot back in OS or else you'll just get stuck at logo
Click to expand...
Click to collapse
I'm curious, is there a way to do this in download mode (via Odin or otherwise)? As far as I know, I can only do that through recovery. Do I have to adb and wipe /cache?
Sent from my SGH-I337 using xda app-developers app
okzygen said:
I'm curious, is there a way to do this in download mode (via Odin or otherwise)? As far as I know, I can only do that through recovery. Do I have to adb and wipe /cache?
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
i do it thru recovery, thats always how it worked for me. You cant do it thru adb since you need root to do that and odin wipes root
okzygen said:
Okay, I hope it goes without saying that what you do with this is your responsibility. That being said, I was going to try:
[ROM][BETA][4.2.2][May 23] Slim Bean jflteatt [build 5.6] - LOKI patched
and here are a few more:
[ROM] Task650 AOKP(Jellybean 4.2.2)(5.23.2013)(LOKI-d) (AT&T)
[KERNEL][ATT][AOSP/TW][5/23/2013] KT-SGS4 - MDL - LOKI'd - KTweaker
CyanogenMod 10.1 Loki'd for the Galaxy S4 ATT
Click to expand...
Click to collapse
OK I installed the AOKP one and it works like a charm. Only thing is NFC doesn't work so once that works it will be pretty Much perfect
Sent from my SGH-I337 using Tapatalk 2
jasbur17 said:
I'm sad to say that I also wiped a phone with TWRP. It wasn't an S4 and I didn't need Kies.
I had no idea that it would delete the OS - I don't think there was even a warning.
Click to expand...
Click to collapse
Yeah me too, was and still am not happy about it. Should gave stuck to CWM. TWRP is a cool recovery, as long as you realize what you hit.
Glad Kies worked! Now that I have an Att phone I can utilize it again. Wouldn't recognize my International SGS3, so Kies was useless.
Sent from GT-I9505 transformed SGH-I337
I've done some searching, finding similar things that have happened to others here, but nothing that specifically fits what I'm experiencing...
I'm hoping someone has a step-by-step that I can do to get this phone rooted properly... First, I've been on XDA for a while, Droid Eris and HTC Incredible 2, but this is the first Samsung phone I've owned... A few days ago, I tried the Casual Root method and went ahead and rooted, unlocked the bootloader (unsecure ABOOT) and loaded CWM touch as my recovery. All looked fine, but when I went in to recovery to try and backup the stock rom, it threw a ton of Not able to write/Cannot Mount errors... My phone came with the MF1 4.1.2 already running.
Since, I've tried EZ-Unlock 1.2 to check and unlock the bootloader (which it showed as "Unknown" until I clicked unlock) and I've tried installing different recoveries through EZ Recovery (TWRP 2.2.2, CWM variants, etc...). Still, no joy in getting this to work properly.
The last attempt kept the phone in Download mode until I rebooted using the Power, Vol. Down, Menu to bypass it (Not detecting ANY recovery now!?). I'm still able to get back to the original Rom (which is rooted now), but I'm concerned with bricking if I keep trying this.
So, I'm thinking now of just doing an Odin back to stock and reflashing all the original firmware so I can start over with Casual. Was wondering if anyone had any other input which might get the R/W issue fixed so I don't have to go through all the Odin stuff? Compared to HTC phones, this is quite different with Root/Flashing, so I'm a little confused with the whole process of things right now... Any help would really be appreciated! I'm looking forward to deving at some point, once I'm comfortable with the process...
Thanks,
Rich
Anyone?
Sent from my SCH-I535 using xda premium
Never mind...
Macrodroid said:
I've done some searching, finding similar things that have happened to others here, but nothing that specifically fits what I'm experiencing...
I'm hoping someone has a step-by-step that I can do to get this phone rooted properly... First, I've been on XDA for a while, Droid Eris and HTC Incredible 2, but this is the first Samsung phone I've owned... A few days ago, I tried the Casual Root method and went ahead and rooted, unlocked the bootloader (unsecure ABOOT) and loaded CWM touch as my recovery. All looked fine, but when I went in to recovery to try and backup the stock rom, it threw a ton of Not able to write/Cannot Mount errors... My phone came with the MF1 4.1.2 already running.
Since, I've tried EZ-Unlock 1.2 to check and unlock the bootloader (which it showed as "Unknown" until I clicked unlock) and I've tried installing different recoveries through EZ Recovery (TWRP 2.2.2, CWM variants, etc...). Still, no joy in getting this to work properly.
The last attempt kept the phone in Download mode until I rebooted using the Power, Vol. Down, Menu to bypass it (Not detecting ANY recovery now!?). I'm still able to get back to the original Rom (which is rooted now), but I'm concerned with bricking if I keep trying this.
So, I'm thinking now of just doing an Odin back to stock and reflashing all the original firmware so I can start over with Casual. Was wondering if anyone had any other input which might get the R/W issue fixed so I don't have to go through all the Odin stuff? Compared to HTC phones, this is quite different with Root/Flashing, so I'm a little confused with the whole process of things right now... Any help would really be appreciated! I'm looking forward to deving at some point, once I'm comfortable with the process...
Thanks,
Rich
Click to expand...
Click to collapse
If you were able to root your phone successfully, then what I would recommend what to do is download whatever image you want (for me, I downloaded twrp 2.6.3.0) and then flash it through flashify (free in play store).
If you want to get it an easier way, then use goomanager and then install open recovery script (you'll see it when you press menu). It should install the recovery automatically.
If you want clockworkmod touch, then if you want an image, use flashify to flash it. Doing either of the options will give you a working recovery.
david_hume said:
If you were able to root your phone successfully, then what I would recommend what to do is download whatever image you want (for me, I downloaded twrp 2.6.3.0) and then flash it through flashify (free in play store).
If you want to get it an easier way, then use goomanager and then install open recovery script (you'll see it when you press menu). It should install the recovery automatically.
If you want clockworkmod touch, then if you want an image, use flashify to flash it. Doing either of the options will give you a working recovery.
Click to expand...
Click to collapse
Ok, I've gotvtwrp 2.6.3.0 loaded, works... But, I cannot mount anything, backup totally fails. Any ideas? Twrp also asks for a password for some reason...
Btw, nice to see a familiar face on here! How's life treating you these days?
Sent from my SCH-I535 using xda premium
Try this. But download and use the correct and updated cwm recovery from somewhere else.
http://bestandroidtricks.com/how-to...covery-on-the-samsung-galaxy-s3-all-versions/
Sent from my SCH-I535 using xda app-developers app
stolo said:
Try this. But download and use the correct and updated cwm recovery from somewhere else.
http://bestandroidtricks.com/how-to...covery-on-the-samsung-galaxy-s3-all-versions/
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks! After going through Rom Manager and letting it update CWR on it's own, I finally got everything working now! Backup of the Stock Rom is done finally and I can start flashing some Rom's to get comfortable with things... Hopefully, I can start putting out some Rom's for this device soon!! Thanks for all the help, I really appreciate it!
I have been using kitkang cm11, so far really excited and loving 4.4. I have been updating daily.
Sent from my SCH-I535 using xda app-developers app
stolo said:
I have been using kitkang cm11, so far really excited and loving 4.4. I have been updating daily.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Got wicked loaded up! So far, so good. I might try pulling a repo on cm11 sometime soon...
Sent from my SCH-I535 using xda premium
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!