Looks like I've soft-bricked my S3 and cannot get it back working at all.
When you power it on, it shows the yellow triangle and "Firmware Upgrade encountered an issue. Please use software repair assistant and try again."
I can get into download mode but nothing flashes through. I've tried ML1, MF1, the VRALEC bootchain method, including the PIT file, everything. Odin just won't complete any of the flashes. On some it hangs on Initializing (and I've tried all USB ports, different cables, and two laptops), on others it hangs on nand write partition. I even tried the trick where I add the PIT file but unselect Re-Partition. Nada. Oh, and I tried the actual verizon repair assistand and at 83% it says "phone was disconnected, please reconnect and try again."
Here's what the download mode screen looks like if that helps anyone http://i.imgur.com/zpNGAy4.jpg
Help please? I would really appreciate it.
What did you exactly do that brought you to this state?
thebballkid said:
Looks like I've soft-bricked my S3 and cannot get it back working at all.
When you power it on, it shows the yellow triangle and "Firmware Upgrade encountered an issue. Please use software repair assistant and try again."
I can get into download mode but nothing flashes through. I've tried ML1, MF1, the VRALEC bootchain method, including the PIT file, everything. Odin just won't complete any of the flashes. On some it hangs on Initializing (and I've tried all USB ports, different cables, and two laptops), on others it hangs on nand write partition. I even tried the trick where I add the PIT file but unselect Re-Partition. Nada. Oh, and I tried the actual verizon repair assistand and at 83% it says "phone was disconnected, please reconnect and try again."
Here's what the download mode screen looks like if that helps anyone http://i.imgur.com/zpNGAy4.jpg
Help please? I would really appreciate it.
Click to expand...
Click to collapse
Are you brick with 4.3?
I'm having the same problem (stock rooted 4.3). I flashed clockworkmod via ROM manager and when I went to boot into recovery... yellow triangle of death. I too have tried Odin back to stock, but everything fails. Trying Odin from the triangle screen right now. Seems to be hanging on "SetupConnection".
Update: Failed.
jpmi23 said:
I'm having the same problem (stock rooted 4.3). I flashed clockworkmod via ROM manager and when I went to boot into recovery... yellow triangle of death. I too have tried Odin back to stock, but everything fails. Trying Odin from the triangle screen right now. Seems to be hanging on "SetupConnection".
Update: Failed.
Click to expand...
Click to collapse
If you took the 4.3 OTA you will be unable to flash a custom recovery. This very helpful thread created by @BadUsername will get you back up and running:
http://forum.xda-developers.com/showthread.php?t=2639337
Looks like that's working! Thanks man!
buhohitr said:
Are you brick with 4.3?
Click to expand...
Click to collapse
I think so? I tried going back to stock from being rooted and on CM and I'm actually not positive if I'm on 4.3 now or not since the flash never succeeded. I may have had the wrong bootloader when trying to flash 4.3.
Any ideas?
BattsNotIncld said:
What did you exactly do that brought you to this state?
Click to expand...
Click to collapse
Great question. I was rooted and on CM 10.2 when the phone started shutting down randomly. Reinstalled everything CM-related and it was still happening. I then used TriangleAway to reset root counter which worked flawlessly. Tried putting on a stock rom (the latest off of sammobile I believe 4.3), when the flash failed and then I got where I am now. Maybe I had the wrong bootloader for 4.3? Throughout my research I kept leaning towards this being the case similar to many that flashed OTA 4.3 and got a brick, but all the solutions for that haven't worked for me
thebballkid said:
Great question. I was rooted and on CM 10.2 when the phone started shutting down randomly. Reinstalled everything CM-related and it was still happening. I then used TriangleAway to reset root counter which worked flawlessly. Tried putting on a stock rom (the latest off of sammobile I believe 4.3), when the flash failed and then I got where I am now. Maybe I had the wrong bootloader for 4.3? Throughout my research I kept leaning towards this being the case similar to many that flashed OTA 4.3 and got a brick, but all the solutions for that haven't worked for me
Click to expand...
Click to collapse
You can tell which bootloader you are on from download mode. Use this thread it has all the info you need including how to fix it:
http://forum.xda-developers.com/showthread.php?t=2639337
Unless you've tried all those methods already? I think specifically this is the method you should try:
http://forum.xda-developers.com/showthread.php?t=2586319
BattsNotIncld said:
You can tell which bootloader you are on from download mode. Use this thread it has all the info you need including how to fix it:
http://forum.xda-developers.com/showthread.php?t=2639337
Unless you've tried all those methods already? I think specifically this is the method you should try:
http://forum.xda-developers.com/showthread.php?t=2586319
Click to expand...
Click to collapse
Thanks, at least I've confirmed I'm on the 4.3 baseband. However, I tried the guide on there and the guide you provided and am still unable to get past the "Initialzation" step in Odin. Any ideas?
thebballkid said:
Thanks, at least I've confirmed I'm on the 4.3 baseband. However, I tried the guide on there and the guide you provided and am still unable to get past the "Initialzation" step in Odin. Any ideas?
Click to expand...
Click to collapse
You're using Odin right?
Try to flash it with the pit file. If that doesn't work then try to use the Verizon utility. That thread should work if you follow those directions perfectly, at least I haven't heard of it not working yet.
Sent from my SCH-I535 using Tapatalk 2
thebballkid said:
Thanks, at least I've confirmed I'm on the 4.3 baseband. However, I tried the guide on there and the guide you provided and am still unable to get past the "Initialzation" step in Odin. Any ideas?
Click to expand...
Click to collapse
Hmm. Well at this point I would suggest you make sure you're using a quality USB cable and make sure you use the USB port right on the motherboard. But it looks like you already tried all that. What version of ODIN are you using?
Sent from my SCH-I535 using Tapatalk
BadUsername said:
You're using Odin right?
Try to flash it with the pit file. If that doesn't work then try to use the Verizon utility. That thread should work if you follow those directions perfectly, at least I haven't heard of it not working yet.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Hey thanks for chiming in, really appreciated your guide. I followed everything to the T and had no luck. Tried both Odin 3.07 (PDA) and 3.09 (AP) and your method kept getting stuck at Initialzation in Odin. I tried the PIT file on both too, same thing. Tried the Verizon Utility and at 83% it says "phone is disconnected, lease reconnect and try again."
I will say this: when it gets stuck on Initialzation and I unplug the phone, Odin says "PIT file not found." Not sure if that means anything since the phone is unplugged but only other info I can think to share.
Got any other ideas? Would hate to be the first one that couldn't be helped by your directions. Thanks anyways!
BattsNotIncld said:
Hmm. Well at this point I would suggest you make sure you're using a quality USB cable and make sure you use the USB port right on the motherboard. But it looks like you already tried all that. What version of ODIN are you using?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I have tried, been using two official Samsung USB cables that came with the phone and my Nexus 10. I'm working on two laptops and tried all of the different ports getting the same result, Odin hangs on Initialzation.
I tried using both Odin 3.07 (PDA) and 3.09 (AP).
Any other ideas? Thanks!
thebballkid said:
Hey thanks for chiming in, really appreciated your guide. I followed everything to the T and had no luck. Tried both Odin 3.07 (PDA) and 3.09 (AP) and your method kept getting stuck at Initialzation in Odin. I tried the PIT file on both too, same thing. Tried the Verizon Utility and at 83% it says "phone is disconnected, lease reconnect and try again."
I will say this: when it gets stuck on Initialzation and I unplug the phone, Odin says "PIT file not found." Not sure if that means anything since the phone is unplugged but only other info I can think to share.
Got any other ideas? Would hate to be the first one that couldn't be helped by your directions. Thanks anyways!
Click to expand...
Click to collapse
I didn't write the softbrick guide, @ThePagel deserves that credit. I just made a sticky thread to have everything in one place.
I think you followed everything perfectly and did all that you could, you've read around a lot and tried everything you found. My guess is somehow your system partition is in a read only state and simply isn't letting anything write to it. That would explain what is happening.
What I would do is treat this as a hard brick. I would do one of 3 things:
1) try to hardbrick the phone yourself, maybe run the old version of casual and flash the insecure aboot file to unlock the phone, this obviously will corrupt the 4.3 bootloader and hardbrick the phone. Then you could use the hardbrick restore guide to fix it that way.
2) or you could send it in "as is" for jtag that will write the bootchain for you and most likely fix the problem.
3) try to use the methods in this thread but use all the 4.3 files. If you could somehow get this to work you should write a guide for it and I'll post it in the sticky. I think you have enough know how to attempt it.
http://forum.xda-developers.com/showthread.php?t=1840030
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
I didn't write the softbrick guide, @ThePagel deserves that credit. I just made a sticky thread to have everything in one place.
I think you followed everything perfectly and did all that you could, you've read around a lot and tried everything you found. My guess is somehow your system partition is in a read only state and simply isn't letting anything write to it. That would explain what is happening.
What I would do is treat this as a hard brick. I would do one of 3 things:
1) try to hardbrick the phone yourself, maybe run the old version of casual and flash the insecure aboot file to unlock the phone, this obviously will corrupt the 4.3 bootloader and hardbrick the phone. Then you could use the hardbrick restore guide to fix it that way.
2) or you could send it in "as is" for jtag that will write the bootchain for you and most likely fix the problem.
3) try to use the methods in this thread but use all the 4.3 files. If you could somehow get this to work you should write a guide for it and I'll post it in the sticky. I think you have enough know how to attempt it.
http://forum.xda-developers.com/showthread.php?t=1840030
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I tried the method you posted under 3) and Odin is still stuck on Initialzation
As for hard bricking it myself, it does look like that's my only choice now since booting into download mode does nothing for me since I can't flash anything. When you talk about the insecure aboot file from casual, can you please be more specific? I looked at the casual thread (http://forum.xda-developers.com/showthread.php?t=2332825) and in the jar file I downloaded, there's a Scripts folder, under which there's a d2vzw toolkit zip file, in which there's a aboot.mbn file. Is this what you were referring to?
If I can avoid JTAG I would prefer that. Guess my next goal is to hard brick then try the write to SD Card and boot method.
thebballkid said:
I tried the method you posted under 3) and Odin is still stuck on Initialzation
As for hard bricking it myself, it does look like that's my only choice now since booting into download mode does nothing for me since I can't flash anything. When you talk about the insecure aboot file from casual, can you please be more specific? I looked at the casual thread (http://forum.xda-developers.com/showthread.php?t=2332825) and in the jar file I downloaded, there's a Scripts folder, under which there's a d2vzw toolkit zip file, in which there's a aboot.mbn file. Is this what you were referring to?
If I can avoid JTAG I would prefer that. Guess my next goal is to hard brick then try the write to SD Card and boot method.
Click to expand...
Click to collapse
Just make sure you have all the equipment for a hard brick restore first.
There's an old version of casual, not the most recent one, it's on the thread. It has an option to unlock the device. I'm not sure it will work in this circumstance, but if you can get it to recognize your phone you should be able to select that option only.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Just make sure you have all the equipment for a hard brick restore first.
There's an old version of casual, not the most recent one, it's on the thread. It has an option to unlock the device. I'm not sure it will work in this circumstance, but if you can get it to recognize your phone you should be able to select that option only.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Casual won't recognize the phone
I tried flashing a GSM radio and it hung on initialzation again. Am I somehow stuck between a soft and hard brick now?
thebballkid said:
Casual won't recognize the phone
I tried flashing a GSM radio and it hung on initialzation again. Am I somehow stuck between a soft and hard brick now?
Click to expand...
Click to collapse
Man you have a tough situation.
I'd just get it a jtag repair. It'll start you clean and you can start over. I can't think of anyway to force download mode to write something to your phone.
That other guide is your exact symptom, but we don't have a way to fix a read only state on a 4.3 system.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 11:03 AM ---------- Previous post was at 10:59 AM ----------
thebballkid said:
Casual won't recognize the phone
I tried flashing a GSM radio and it hung on initialzation again. Am I somehow stuck between a soft and hard brick now?
Click to expand...
Click to collapse
Technically you're softbricked in a read only state.
Sent from my SCH-I535 using Tapatalk 2
NEED HELP
I have the same problem as the OP. Nothing will work. Any ideas? :/. I have tried absolutely everything
Related
I'm trying to flash my friend's Galaxy s 4g, but I'm having an issue with Odin failing to flash.
I originally used Vibrant 3g .pit and .tar files, not knowing it wouldn't work on the 4g model. Anyway, that semi bricked it, while still allowing it to get to the download mode.
So I figured I needed the "custom" .tar file to flash the 4g model. I booted up Odin and opened just the .tar that's in the noob guide. This time all I got from Odin is a red panel saying FAIL! It happened during the cache.rfs process. And now I get a new download mode screen. Before it used to be the android digging, now it's just an image of a phone and a computer with an exclamation mark in between the two.
When I get FAIL! on Odin, the progress bar on the phone freezes about 75% of the way.
So what am I doing wrong? Do I need a .pit file? Is it my computer? Should I try another computer? help me out please
I'm not sure about that second message you got, but did you make sure to open ODIN before flashing?
And do you also have the correct USB Drivers downloaded for your computer?
bustanut said:
I'm not sure about that second message you got, but did you make sure to open ODIN before flashing?
And do you also have the correct USB Drivers downloaded for your computer?
Click to expand...
Click to collapse
Yea, i had ODIN open before I connected the phone. And I made sure to install the correct drivers for it (It said "drivers installed successfully)
Another thing, is when I was trying to flash it thinking the regular vibrant 3g method would work, I had "Re-Partition" checked. Could that be part of the problem?
You're not supposed to have Re-Partition checked.
Refer to this guide to make sure you're doing everything right in the flashing process : http://forum.xda-developers.com/showthread.php?t=1001759
Well, I have been following that guide. Step by step.
But that was after I semibricked it.
Before, I thought using the method for rooting a vibrant 3g would work for the 4g model. I guess the "Re-partition" box was checked (before I started following that "Noobs guide") and that's why I'm having problems now.
The symbol you are now seeing on your phone means you have a currupt firmware. It was most likely caused by using the vibrants pit file. If you try everything else and it still doesn't work. You may have to wait until we either have a working pit. But follow the directions on the Odin flashing instruction and keep trying.
Good luck
Sent from my GT-I9000 using XDA Premium App
So, there's nothing I can do now besides keep trying? It's not my phone though... my friend was expecting it back today.
Is there a way I can get to the recovery menu and download somebody's nandroid backup to restore mine?
bryanoid said:
So, there's nothing I can do now besides keep trying? It's not my phone though... my friend was expecting it back today.
Is there a way I can get to the recovery menu and download somebody's nandroid backup to restore mine?
Click to expand...
Click to collapse
Sorry bud. Cwm doesn't work that way yet. And even so, I don't think you can even get into recovery mode with your problem. When you used the vibrant pit file you formatted the phone to be like the vibrant which its not. Its very similar, but different enough to cause issues.
Sent from my GT-I9000 using XDA Premium App
Ok so I've been rooted and unlocked for a while now, but stayed with the stock rom as when I tried out Synergy Nightlies it gave me some errors. So I went to try out CleanRom 2.1, people liked it and I didn't notice any flashing errors. So I flashed it through CWM 6.0.1 and it gave me the yellow exclamation mark saying I had unauthorized data on my phone. So I followed the sticky on how to unbrick my phone using the 2 boot loaders and the root66 stock image. My issue is that when running the root66 stock image through Odin it fails at _XmitData_Read, which seems to be somewhere in system.img.ext4. I've tried rebooting the computer, the phone, Odin, it just doesn't work. So when I reboot my phone after the failure I get Odin auto loading saying:
Odin Mode
Product Name: SCH-I535
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
Qualcomm Secureboot: Enable
Then an image of a phone, 2 dots, a yellow exclamation, 2 dots and a computer are shown with the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.
Anyone able to help me?
can you still get to odin mode? also if you have kies installed on the computer erase it.
kidhudi said:
can you still get to odin mode? also if you have kies installed on the computer erase it.
Click to expand...
Click to collapse
Kies isn't installed on the computer and yes I am still able to get into Odin Mode.
I'm under the impression that "unauthorized software" message comes from the locked bootloader (if I'm wrong about that someone plese correct me.)
Sounds like you're functional enough to be able to Odin back to stock and go from there - that's what I'd try. See the stickied thread in the Q&A forum.
I would run the FULL VRALF stock image through ODIN to return to stock. That is always the safest way out of a sticky situation.
Thanks guys, according to another post the version of EZ-Unlock I used most likely gave a false report and never actually unlocked my phone. The problem with going back to stock, which if what I'm trying to do, is that it fails.
Could be an USB issue - an intermittent connection would be most likely to cause problems while sending the system partition since that's the biggest. I've had problems using adb from time to time if I plug into one of the front-panel ports on my PC but no trouble with one on the back.
Maybe try switching ports or try a different cable ...
Actually what usb plug are you using on your computer? You should be using one in the back of your computer by the power supply. Seen the front jacks not work correctly for large transfers. Finally, try another usb cable.
Sent from my SCH-I535 using xda app-developers app
Strange.... i was able to flash syergy on thefirst try. Never used odin during the whole process....
If youre rooted you need to make sure you have a custom recovery in place like cwm or twrp. Make sure you make a nand-backup.
I used casual to flash unsecure bootloader, with that and recovery in place you should be able to flash roms without any hitches....
I could never find a comprehensive guide on using odin so i never got around to testing it
kintwofan said:
Actually what usb plug are you using on your computer? You should be using one in the back of your computer by the power supply. Seen the front jacks not work correctly for large transfers. Finally, try another usb cable.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
So far I've tried 3 different USB cables and both a desktop, both front and back ports and a laptop, each one fails on the write of XmitData under system.img.ext4
I had a custom recovery installed and Odin is only being used to get me back to a stock rom, otherwise I did all my flashing under CWM 6.0.1 or twrp. I think the whole fake unlocked bootloader just hard bricked the software.
EDIT: Come to think of it I remember waking up to my phone in download mode. I think Verizon tried to install the update to my phone while I was sleeping. Granted it failed at the end, but I'm wondering if that did something to brick me now.
If you can get in download mode it can be saved. I woud re download the stock firmware or the 66, but personally i would go bone stock. You may just have a bad download.
Sent from my SCH-I535 using xda app-developers app
kintwofan said:
If you can get in download mode it can be saved. I woud re download the stock firmware or the 66, but personally i would go bone stock. You may just have a bad download.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yea, I'm currently downloading at the speed of slug the newest update from the forums, will probably just redownload at home, since it's going to take over an hour >.<
EDIT:
Does anyone have a link for an older EZ-Unlocker, that is known to work, so that I don't get this problem yet again.
FIXED!
Ok, so using the newest stock rom from the dev forum worked. Can someone please give me a link to an old EZ-Unlocker so I can flash without worrying about another massive brick in my palm. I'm guessing that running the original root66 stock rom through dropbox somehow corrupted it.
LlirasChosen said:
Ok, so using the newest stock rom from the dev forum worked. Can someone please give me a link to an old EZ-Unlocker so I can flash without worrying about another massive brick in my palm. I'm guessing that running the original root66 stock rom through dropbox somehow corrupted it.
Click to expand...
Click to collapse
I personally suggest not using the app if you already had trouble. Just root your phone using the Debug Root method in Development, download the aboot.img from Adam Outlers thread HERE to your phone, and run the commands at the very bottom in Terminal Emulater app (from the market).
That way you know for sure your bootloader is unlocked. This is what I have done and never had an issue.
Edit: Glad you got your issue resolved!
I decided to switch from synergy 4.0.4 to cm10 , Backed up under TWRP, then wiped cache / system , installed cm10 / gapps and rebooted...
My phone is locked up on a black screen saying '' software unauthorized by verizon, contact customer line or go the closest store...''
I need Help, I looked around but could not find anything, I am under mac osx 10.7.5 and could not get anything to work with Odin app ( modified version for mac that I downloaded doesn't show any infos about the phone when connected...)
I NEED HELP PLEASE... Just want to get my phone back to a working state,please....
***UPDATE ::::
I Did it, Got finally Odin to work under VIRTUAL BOX, XP, Lot of patience...then Restore twrp back up ..i m back to life! thank you all for the help.
Tee****sky said:
I decided to switch from synergy 4.0.4 to cm10 , Backed up under TWRP, then wiped cache / system , installed cm10 / gapps and rebooted...
My phone is locked up on a black screen saying '' software unauthorized by verizon, contact customer line or go the closest store...''
I need Help, I looked around but could not find anything, I am under mac osx 10.7.5 and could not get anything to work with Odin app ( modified version for mac that I downloaded doesn't show any infos about the phone when connected...)
I NEED HELP PLEASE... Just want to get my phone back to a working state,please....
Click to expand...
Click to collapse
Can you get it into download mode? (ODIN)
ODIN screen ON
shojus said:
Can you get it into download mode? (ODIN)
Click to expand...
Click to collapse
Although the Phone is on downloading mode '' odin '' screen, the ODIN software on my mac does not show it, I also tried Kies, it knows there is a device and try to connect but no success neither.
Tee****sky said:
Although the Phone is on downloading mode '' odin '' screen, the ODIN software on my mac does not show it, I also tried Kies, it knows there is a device and try to connect but no success neither.
Click to expand...
Click to collapse
Well... I am not familiar with a mac but have you tried uninstalling your kies (and all samsung drivers) and re-installing the drivers again? You should be able to get out of that state but with a mac I cannot be very specific with you... Don't worry, you have not bricked your phone (well you soft bricked it) but are most-likely experiencing some software issues... I added a couple threads maybe they can help? I will keep lookin for ya....
http://forum.xda-developers.com/showthread.php?t=1762709
http://forum.xda-developers.com/showthread.php?t=1840030
I appreciate your support
shojus said:
Well... I am not familiar with a mac but have you tried uninstalling your kies (and all samsung drivers) and re-installing the drivers again? You should be able to get out of that state but with a mac I cannot be very specific with you... Don't worry, you have not bricked your phone but are most-likely experiencing some software issues...
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
I reinstalled twice drivers and upgraded kies too. restart my computer few times to make sure but nothing so far.
I spent my night trying, I am hoping some script genius instal kinda thing may be my only chance...
I know there are few people out there that had the same issue, I am a novice but I have been flashing and using custom roms on my androids for the past three years and I am good at looking out and doing / following step by step solution....
I am hoping some of the guys at cm or some of you to be able to direct me to the right process to recover..
thanks again
( PS: stuck on my Tbolt the time I figure it out...I HATE IT..
Tee****sky said:
I reinstalled twice drivers and upgraded kies too. restart my computer few tines to make sure but nothing so far.
I spent my night trying, I am hoping some script genius instal kinda thing may be my only chance...
I know there are few people out there that had the same issue, I am a novice but I have flashing and using custom roms on my androids for the past three years and I am good at looking out and doing / following step by step solution....
I am hoping some of the guys at cm or some of you to be.able to direct me to the right process to recover..
thanks again
Click to expand...
Click to collapse
Sorry I can't be of more help but I am blind with a mac... There has definitely been others that have had your same problem and have come out of it fine but that was with ODIN on a windows machine so I am not sure... Good luck! I have been there too!
From reading through some posts it sounds like you may have re-locked your bootloader by accident? Anyway that could have happened?
You probably used EZ Unlock from the Play Store which is broken - it doesn't unlock the boot loader. Your Odin problems sound Driver/Mac related - if you keep having problems with Odin try Heimdall.
Fix your Odin problems, go back to stock, re root using DebugFS, get EZ Unlock version 1.2 from RootzWiki and so on.
BlackBytes said:
You probably used EZ Unlock from the Play Store which is broken - it doesn't unlock the boot loader. Your Odin problems sound Driver/Mac related - if you keep having problems with Odin try Heimdall.
Fix your Odin problems, go back to stock, re root using DebugFS, get EZ Unlock version 1.2 from RootzWiki and so on.
Click to expand...
Click to collapse
What he said....
I did not use ez unlock
BlackBytes said:
You probably used EZ Unlock from the Play Store which is broken - it doesn't unlock the boot loader. Your Odin problems sound Driver/Mac related - if you keep having problems with Odin try Heimdall.
Fix your Odin problems, go back to stock, re root using DebugFS, get EZ Unlock version 1.2 from RootzWiki and so on.
Click to expand...
Click to collapse
I used " casual app method " by Adam on the stock Rom , it worked like a charm. I installed synergy rom and ran it no prob at all for two months + ...
then I tried to instal cm10 this morning to give a try to jelly modufugin bean..
no luck I guess....dawn it..
Tee****sky said:
I used " casual app method " by Adam on the stock Rom , it worked like a charm. I installed synergy rom and ran it no prob at all for two months + ...
then I tried to instal cm10 this morning to give a try to jelly modufugin bean..
no luck I guess....dawn it..
Click to expand...
Click to collapse
Well you only get the "blabla Verizon Store" screen if your boot loader is locked and you flash something.
Like I said try to get your Odin problem fixed. Maybe one of your friends can give you access to a Windows PC - you can check Droid Styles Guide (Sticky in Development Sub Forum) for instructions how to go back to stock.
Well the unauthorized software error is definitely from trying to load an unsigned kernel with a secure aboot (ie bootloader is locked). So if it was unlocked before, it is somehow relocked. I dont think you will be able to get anywhere w/o getting Odin running.
I sure will
BlackBytes said:
Well you only get the "blabla Verizon Store" screen if your boot loader is locked and you flash something.
Like I said try to get your Odin problem fixed. Maybe one of your friends can give you access to a Windows PC - you can check Droid Styles Guide (Sticky in Development Sub Forum) for instructions how to go back to stock.
Click to expand...
Click to collapse
I don't really know why odin doesnt work, I am trying to instal Heimdall too to take a look at it.
I guess I might be wrong and the method I used originally did not unlock my bootloader but this is what it said...
Adam Outler's Casual for Rooting/Unlocking Bootloader/CWM recovery(mac/linux) ( http://forum.xda-developers.com/showthread.php?t=1762709 )
Which means I was unlocked theoretically for about 2 months, I was running synergy rom perfectly ....
I don't think there was anything wrong from my side in the process of backing up,wiping flashing... when I installed cm10, then I had problems...
Did their nightly locked my bootloader again? maybe...
Please read forum rules before posting
Questions go in Q&A
Thread moved
Friendly Neighborhood Moderator
kennyglass123 said:
Please read forum rules before posting
Questions go in Q&A
Thread moved
Friendly Neighborhood Moderator
Click to expand...
Click to collapse
I like your sig but I don't think people care too much about the "Thanks" button anymore even though you try to help them at 2-3 AM....
I have a mac too and trying to do anything with a GS3 on a mac is a real pain. That's why I use boot camp. I definitely recommend using it. Getting windows is pretty easy if you know where to look
Sent from my SCH-I535 using xda app-developers app
Just rooted my new SGS3 using New Root Method Released for Verizon’s Galaxy S3, No Odin Required. i did the data & kelvic wipe then install Clean Rom 5.0. All progressed without a hitch. Even backed up with CWM prior to flash.
I rebooted into the new rom and got this: System software not authorized by Verizon Wireless... rebooted several time with same result.
What can I do now? Thanks for your help.
Just a wild guess, but me thinks your bootloader is still locked! But I'm not sure that will even apply because I rooted my device before unlocking the bootloader. But I rooted my device via ODIN first.
You can try EZ-Unlock via the Market. The GUI is still very buggy and will show the status as unknown but the internal workings of the app works good.
You got nothin to loose in trying. Go back to stock and give it another whirl after you've unlocked the bootloader.
Of that fails then I would suggest using the tried and true method..ODIN.
G'luck!
yup your bootloader is still locked
check the downloads thread and use version 1.2.
That means your boatloader is locked. You now must Odin back to stock and start over. Droid style has a guide stickied in the development thread. Follow section 6 of it.
Next time use ez unlock version 1.2 to unlock you boatloader.
Sent from my SGS3 running Eclipse 2.1
downloads list
http://forum.xda-developers.com/showthread.php?t=1850506
tekrhino said:
Just a wild guess, but me thinks your bootloader is still locked! But I'm not sure that will even apply because I rooted my device before unlocking the bootloader. But I rooted my device via ODIN first.
You can try EZ-Unlock via the Market. The GUI is still very buggy and will show the status as unknown but the internal workings of the app works good.
You got nothin to loose in trying. Go back to stock and give it another whirl after you've unlocked the bootloader.
Of that fails then I would suggest using the tried and true method..ODIN.
G'luck!
Click to expand...
Click to collapse
Thanks. I can't get past the warning dialogue screen. Pulled the battery, no good. PC can't see the phone with USB.
Prophotog said:
Thanks. I can't get past the warning dialogue screen. Pulled the battery, no good. PC can't see the phone with USB.
Click to expand...
Click to collapse
Yikes, ok
You have to get into DOWNLOAD MODE.. Power+ Volume Down+ Home key at the same time after a fresh battery pull.
Do a search on the Development forum to set up Odin on your PC.
YOU Must FOLLOW directions EXACTLY our you will have very expensive BRICK!
This forum could help:
http://forum.xda-developers.com/showthread.php?t=1762709
Or even better, this one:
http://forum.xda-developers.com/showthread.php?t=1840030
tekrhino said:
Yikes, ok
You have to get into DOWNLOAD MODE.. Power+ Volume Down+ Home key at the same time after a fresh battery pull.
Do a search on the Development forum to set up Odin on your PC.
YOU Must FOLLOW directions EXACTLY our you will have very expensive BRICK!
This forum could help:
http://forum.xda-developers.com/showthread.php?t=1762709
Or even better, this one:
http://forum.xda-developers.com/showthread.php?t=1840030
Click to expand...
Click to collapse
Thanks to everyone!! Looks to be a long night. :>)
tekrhino said:
Yikes, ok
You have to get into DOWNLOAD MODE.. Power+ Volume Down+ Home key at the same time after a fresh battery pull.
Do a search on the Development forum to set up Odin on your PC.
YOU Must FOLLOW directions EXACTLY our you will have very expensive BRICK!
This forum could help:
http://forum.xda-developers.com/showthread.php?t=1762709
Or even better, this one:
http://forum.xda-developers.com/showthread.php?t=1840030
Click to expand...
Click to collapse
I lol'ed at your post. A little dramatic, don't you think? He's not even close to bricked. Just Odin from download mode back to stock, and redo the steps with bootloader unlock.
Here is a gift (working ez-unlock v1.2)
http://dl.dropbox.com/u/42057363/com.mmmeff.ez.unlock_3.apk
@Techsavvy
Yeah, perhaps a tad overdone on the theatricals.
Cut me some slack, I'm taking acting classes..lol
And... I know... I know..don't quit my day job!
Still having issues. I "think" I am in the download mode. Screen says Downloading.... It has Odin in red in top left corner. Device connects with Odin. BUT I am not getting a PASS message when flashing VRALEC bootchain. Last text line in Odin is: <OSM> Leave CS...
I have tried several attempts.
Suggestions?
Prophotog said:
Still having issues. I "think" I am in the download mode. Screen says Downloading.... It has Odin in red in top left corner. Device connects with Odin. BUT I am not getting a PASS message when flashing VRALEC bootchain. Last text line in Odin is: <OSM> Leave CS...
I have tried several attempts.
Suggestions?
Click to expand...
Click to collapse
No need to do the boot chains. Just follow section 5 of this guide and I recommend root 66 for the ROM you flash
http://forum.xda-developers.com/showthread.php?p=28530394
Sent from my SGS3 running Eclipse 2.1
tekrhino said:
@Techsavvy
Yeah, perhaps a tad overdone on the theatricals.
Cut me some slack, I'm taking acting classes..lol
And... I know... I know..don't quit my day job!
Click to expand...
Click to collapse
I appreciate the theatricals...however, I am having issues with Odin. Can't get the Pass message. I assume the "Downloading..." text means I'm in the download mode. Tried several attempts. I AM glad I'm not close to bricked too! Can't afford $600 or a divorce. Might have to sell a camera instead.
Prophotog said:
Just rooted my new SGS3 using New Root Method Released for Verizon’s Galaxy S3, No Odin Required. i did the data & kelvic wipe then install Clean Rom 5.0. All progressed without a hitch. Even backed up with CWM prior to flash.
I rebooted into the new rom and got this: System software not authorized by Verizon Wireless... rebooted several time with same result.
What can I do now? Thanks for your help.
Click to expand...
Click to collapse
And just for future reference, it's Dalvik, not Kelvic
Sent from my SCH-I535 using xda app-developers app
Prophotog said:
I appreciate the theatricals...however, I am having issues with Odin. Can't get the Pass message. I assume the "Downloading..." text means I'm in the download mode. Tried several attempts. I AM glad I'm not close to bricked too! Can't afford $600 or a divorce. Might have to sell a camera instead.
Click to expand...
Click to collapse
Just a heads up. You can get a real brick with Odin and easy. Follow the guide I linked earlier to a t and you'll be fine
Sent from my SGS3 running Eclipse 2.1
kintwofan said:
Just a heads up. You can get a real brick with Odin and easy. Follow the guide I linked earlier to a t and you'll be fine
Sent from my SGS3 running Eclipse 2.1
Click to expand...
Click to collapse
You are a scholar and a gentleman!! THANK YOU very much. You can have a portrait session on me any time. Name the time and place.
Prophotog said:
You are a scholar and a gentleman!! THANK YOU very much. You can have a portrait session on me any time. Name the time and place.
Click to expand...
Click to collapse
Cool, I take it you're up and running again. Just make sure you use ez unlock 1.2 next time. And the positive is you're an Odin pro now!
Sent from my SGS3 running Eclipse 2.1
Hi, I have a Verizon S3 flashed to Boost Mobile. I tried to gain root by flashing a stock rooted Rom and messed up the flash. I had to take it back to be flashed again  Now I'm more cautious before hand. I should have backed it up before attempting it, I know I know lol can anyone shed some light on how to update a flashed phone as well as how to root it. I could really use the help 
Also after I messed up the boost flash I paniced and flashed a sprint kernel hoping this would fix the problem. Since then anything that I've tried to view including taking camera shots and web browsing if done in landscape mode will be upside down, any remedy for this problem? I know now... root first, flash later. 
Sent from my SPH-L710 using XDA HD
Alex0826 said:
Hi, I have a Verizon S3 flashed to Boost Mobile. I tried to gain root by flashing a stock rooted Rom and messed up the flash. I had to take it back to be flashed again  Now I'm more cautious before hand. I should have backed it up before attempting it, I know I know lol can anyone shed some light on how to update a flashed phone as well as how to root it. I could really use the help 
Also after I messed up the boost flash I paniced and flashed a sprint kernel hoping this would fix the problem. Since then anything that I've tried to view including taking camera shots and web browsing if done in landscape mode will be upside down, any remedy for this problem? I know now... root first, flash later. 
Sent from my SPH-L710 using XDA HD
Click to expand...
Click to collapse
Sprint kernel is causing the inversion. Flash a vzw kernel. Read first flash later.
Sent from my SCH-I535 using xda app-developers app
Who ever did your flash might not done it right cause ya not supposed to lose a flash like that unless he didn't do things right. I can factory reset mine and I wont loose flash
Sent from my SPH-L900 using Tapatalk 2
So I have an old Infuse that my kids use and it went crazy the other day. Not sure what happened. Long story short I keep getting a boot loop at the ATT screen. This phone is not rooted and I'm not sure if it was on Froyo or GB. I've flashed every return from brick I can find on XDA. I'm using Odin and I'm pretty familiar with flashing/rooting etc. Can't figure this one out. The only thing I can think is the boot loaders are not the correct ones? Not sure, I keep seeing GTG's ultimate unbrick but all the links I get to it don't work. this is the only thing I haven't tried. Any help would be appreciated.
Edit to add: After I flash in Odin it goes to reboot then does the open update, verifying update, installing update, successfully installed update package.
Copying media files it says failed to mount/sdcard, can't mount /sdcard your storage not prepared yet please use UI menu for format and reboot. ??? I think that's the problem. How do I fix??
Just search in the stickies for bootloaders. That will solve your problems
Sent from my SGH-I997 using xda app-developers app
COfatboy said:
So I have an old Infuse that my kids use and it went crazy the other day. Not sure what happened. Long story short I keep getting a boot loop at the ATT screen. This phone is not rooted and I'm not sure if it was on Froyo or GB. I've flashed every return from brick I can find on XDA. I'm using Odin and I'm pretty familiar with flashing/rooting etc. Can't figure this one out. The only thing I can think is the boot loaders are not the correct ones? Not sure, I keep seeing GTG's ultimate unbrick but all the links I get to it don't work. this is the only thing I haven't tried. Any help would be appreciated.
Edit to add: After I flash in Odin it goes to reboot then does the open update, verifying update, installing update, successfully installed update package.
Copying media files it says failed to mount/sdcard, can't mount /sdcard your storage not prepared yet please use UI menu for format and reboot. ??? I think that's the problem. How do I fix??
Click to expand...
Click to collapse
If you'd like to try GTG's Ultimate Unbrick, you can find a working download here:
http://forum.xda-developers.com/showpost.php?p=22404446&postcount=391
Tried everything and no go. Not sure where to go from here. Sure seems like a hardware issue.
COfatboy said:
Tried everything and no go. Not sure where to go from here. Sure seems like a hardware issue.
Click to expand...
Click to collapse
You mentioned it's boot-looping at the Samsung logo - perhaps there's an issue with the power button.
Here's a couple of threads that may be helpful:
http://forum.xda-developers.com/showthread.php?t=2107558
http://forum.xda-developers.com/showthread.php?t=1996709
prairied0gg said:
You mentioned it's boot-looping at the Samsung logo - perhaps there's an issue with the power button.
Here's a couple of threads that may be helpful:
http://forum.xda-developers.com/showthread.php?t=2107558
http://forum.xda-developers.com/showthread.php?t=1996709
Click to expand...
Click to collapse
It goes past the Samsung logo screen then to the ATT Rethink Possible screen then keeps looping on that screen over and over. It charges normally also.
COfatboy said:
It goes past the Samsung logo screen then to the ATT Rethink Possible screen then keeps looping on that screen over and over. It charges normally also.
Click to expand...
Click to collapse
I would try flashing just a kernel (not the whole unbrick package). I have been in a similar situation and after trying everything imaginable that's what ended up fixing it for me.
Sent from my SGH-I997 using Tapatalk 2
prairied0gg said:
I would try flashing just a kernel (not the whole unbrick package). I have been in a similar situation and after trying everything imaginable that's what ended up fixing it for me.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Tried that earlier I thought, tried again just to make sure. Still no go. I appreciate all your help! :good: I'm gonna give up for tonight anyways.
COfatboy said:
Tried that earlier I thought, tried again just to make sure. Still no go. I appreciate all your help! :good: I'm gonna give up for tonight anyways.
Click to expand...
Click to collapse
This happened to me earlier. What I did was-
1 Went to full stock using heimdal one click, After completetion, U may stuck in bootloop in at&t as you said
2 Flash efs.zip found in the link below using odin. put efs.zip in odin and untouch any other setting and flash, (Ur imei may be previously corrupted so u got bootloop). This doesnot do any harm. So flash with confidence. If ur device doesnot show up in odin after u flash with heimdal one click , reinstal drivers with kies mini
Link for download http://forum.xda-developers.com/showthread.php?t=1729838
3 Now u'll be out of AT&T bootloop if ur imei was previously corrupted.
I was in similar situation. And this solved my proble.
Hit me thanks if I helped you :good:
Thanks for all the advise. Still not working. Tried everything above and much more. Different things I do give different results but pretty much the same in end. Either sticks in recovery or boot loops one way or another. Really don't see how this could be related to software but you never know I guess.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app