Hey guys, I somehow managed to soft brick my verizon GS3 this afternoon. I just need a little help in getting the thing back up and running and possibly an explanation on were I went wrong. I thought I had unlocked the bootloader and then rooted the phone. I managed to install TWRP 2.5.0.0 and do a backup. Then I installed a custom ROM and got the infamous "Software not authorized" message with the yellow triangle.
1st, is it possible to get this far with the bootloader still being locked??
2nd, If I understand correctly, I need to use ODIN to go back to stock and start over. Correct? Or is there another way to salvage this situation. If I have to go back to stock, can someone point me to the latest files? I've found links to a lot of different ones and I don't want to make a bad situation worse. BTW, I can't get into recovery but I can get into ODIN mode.
Any help is greatly appreciated!!
Ok, using ODIN, I was able to get a stock ROM onto the phone and get the thing booted. So essentially I'm back to square 1 and I still didn't figure out what I did wrong the first time around. Bummer Eh?
scheirere said:
Ok, using ODIN, I was able to get a stock ROM onto the phone and get the thing booted. So essentially I'm back to square 1 and I still didn't figure out what I did wrong the first time around. Bummer Eh?
Click to expand...
Click to collapse
Yea, I soft bricked once and was able to boot into recovery by holding volume up, power, and home at the same time while the phone was off. I thanked my lucky stars I had a nandroid backup. I would make sure you unlocked the boot loader properly. When I first started rooting YouTube was great for instructions. I would post a link to a YouTube video but it won't allow me until I have ten posts, I swear some of these rules are retarded. Anyway search in YouTube having visual and audio guide helps a lot. good luck!
Related
I attempted to use Odin to return to stock, I followed directions, because I was having problems with the home button not working unless I'd reboot. I figured I'd take it into AT&T after testing stock to see if it was an issue with the rom. Anyway, for some reason Odin failed. I have used Odin before on my skyrocket and each time was a success so the .tar is legit. I have no clue what went wrong. How do I get past the yellow triangle to attempt again? All the posts I read they never say how they get a second chance just that they tried again and it worked. I took my battery out for 20 minutes and it went back to the triangle. I had no idea about kies firmware recovery since I'm an android noob so I don't have a recovery code or whatever and can't attempt samsung's way. Any ideas will be much appreciated.
Can you get into dload mode? OR CWM?
led65 said:
I attempted to use Odin to return to stock, I followed directions, because I was having problems with the home button not working unless I'd reboot. I figured I'd take it into AT&T after testing stock to see if it was an issue with the rom. Anyway, for some reason Odin failed. I have used Odin before on my skyrocket and each time was a success so the .tar is legit. I have no clue what went wrong. How do I get past the yellow triangle to attempt again? All the posts I read they never say how they get a second chance just that they tried again and it worked. I took my battery out for 20 minutes and it went back to the triangle. I had no idea about kies firmware recovery since I'm an android noob so I don't have a recovery code or whatever and can't attempt samsung's way. Any ideas will be much appreciated.
Click to expand...
Click to collapse
Ok figured it out and this is for anyone else who ends up in a similar situation. Download this file megaupload.com/?d=AQX73AN0 I'm assuming that its the emergency firmware recovery as it is only 10mb (I'm too new to post the full link so add the rest). I ran it through Odin and I accidently left F. Reset Time Checked along with Auto Reboot, glad it didn't make things worse not sure it was necessary, but hey it kicked my phone into recovery mode. Where I was able to run the stock .tar k0nane.info/rom/SGH-I727-UCKJ2-k0nane.7z (retrieved from another thread thank K0nane not me) and my phone is up and running again. I hope that I was able to help someone out at some point.
Finally was able to thank you for the quick response!
Well I like how you know the value of knowledge. And i always like getting thanked whenever i help to ppl.
led65 said:
Finally was able to thank you for the quick response!
Click to expand...
Click to collapse
I think I may have bricked my SGS3. Well, not permanently, I hope, but I'm stuck at a point and have reached the limit of my knowledge.
I had flashed AOKP. Part of this meant installing VZW GS3 EZ-Recovery App and flashing some sort of file with it, which I believe may have been a kernel. In retrospect, my lack of knowledge here probably should have made me pause... I'm not exactly clear on what a kernel is in the first place.
Due to some issues, I decided to go back to my rooted stock. I planned on booting into recovery and restoring to the point I backed up with Clockwork Mod. Suspecting that this kernel(?) business would need to be the same as when I was on stock before, I opened VZW GS3 EZ-Recovery App and tried to flash to the “stock” option in it. I think this was my mistake.
From here, I rebooted into recovery. And that’s where the problem started. I’m stuck in what I think is the generic Android recovery menu. I can clear data and cache, but there is no option to restore. When I select the reboot option, an error picture shows up in the background. The phone will begin to reboot, but always ends up back in recovery.
I’m guessing that ODIN thing is going to be used to solve this, and I have downloaded it.
Thank you for taking the time to read this. I thought I knew the basics of rooting, having installed several custom ROMs on my old Droid X, but my current situation makes me think that I don't know as much as I thought I did. I'm sorry if I'm missing something blindingly obvious. If you want to lecture me on why I should have researched more or tried to do less, go ahead—as long as you can help. This is my personal phone, and I have my fingers crossed that I didn’t do irreversible damage.
Feel free to ask for any more information. I can probably take a picture of the recovery menu if that will help.
Again, I’m sorry for my stupidity.
Thanks,
Romuluscrohns
Get your phone in download mode and flash a stock rooted or stock rom with odin. To get in download mode turn off your phone and turn it on by pressing volume down, home, and power together. We all make mistakes while learning to root a phone and then we learn from it. Just remember to always be careful with what you do.
Thank you for the advice! I am trying this right now.
EDIT: SOLVED! Thank you again! I'll definitely be more careful.
Hello, I have a Motorola Defy which i have rooted and installed clockworkmod on it. I tried to install Cyanogen mod 7.1 from the website. The phone got to the boot screen where it continued to cycle through it thing and nothing more. I restarted the phone and now it gets stuck at the first screen where its says "google". I tried to enter recovery again (power + volume down) and clockworkmod is completely gone. I want to go back to the stock OS so it atleast works again. Ive tried using the update.zip option in the stock recovery mode but I keep getting an error "failed to verify whole-file signature" when using a signed copy of cyanogen mod. I also tried putting my backup in a zip with the same error. Ive even tried formatting my sd card. What do i do?
I was more or less where you are around June or so. I'm no expert by any means, but perhaps I can help. If memory serves I used a program called RSD Lite to flash it back to the stock unlocked rom I got from the "bl7 finally rooted" thread - if you unlocked a different way, I'd try to find your original rom.
Once you get to where you understand how to get back to stock it makes the whole thing a lot less scary, or it did for me. Once you get back up and running, try flashing Whiterabbit. I didn't have luck getting anything else to run, but that one worked the first time I tried it, and I'm very happy I persevered. Miles better than the stock OS.
Marvelicious75 said:
I was more or less where you are around June or so. I'm no expert by any means, but perhaps I can help. If memory serves I used a program called RSD Lite to flash it back to the stock unlocked rom I got from the "bl7 finally rooted" thread - if you unlocked a dirrerent way, I'd try to find your original rom.
Once you get to where you understand how to get back to stock it makes the whole thing a lot less scary, or it did for me. Once you get back up and running, try flashing Whiterabbit. I didn't have luck getting anything else to run, but that one worked the first time I tried it, and I'm very happy I persevered. Miles better than the stock OS.
Click to expand...
Click to collapse
I cant use the program as my phone doesnt get detected when connected to my pc.
OK, lets start with the basics, if I can remember it right... Have you used RSD Lite successfully before this? Drivers installed? Using bootloader mode? If any of this is unfamiliar go hit the beginner's thread - if you have done all this you may be beyond my help and in need of someone a bit more experienced.
Marvelicious75 said:
OK, lets start with the basics, if I can remember it right... Have you used RSD Lite successfully before this? Drivers installed? Using bootloader mode? If any of this is unfamiliar go hit the beginner's thread - if you have done all this you may be beyond my help and in need of someone a bit more experienced.
Click to expand...
Click to collapse
I fixed it, there were a different set of buttons to hold to get into boot loader. The default recovery was not over written as i thought (happened to all my other phones). Thank you very much for you help. It has been very much appreciated.
Glad to hear it.
Anyone know of, or or have a link to a factory rom (hell any rom would do at this point) that I would be able to flash with the stock S3 recovery? Just trying to unbrick my phone. Story of what happened below:
I'm running stock 4.1.1 rooted touchwiz. I wake up this morning to a notification saying I had an update on my phone. Should have definitely waited but without thinking I went ahead and updated, which of course soft bricks? The phone. (boots up, and but hangs at the 4Glte, flash screen)normally this would be an easy fix, I could Odin back to stock or something but I'm down in Mississippi till Monday for training and do not have access to my pc.
I can access the factory recovery on the phone but that's it, have no clue where CWM is. I've tried flashing some backups but the factory recovery says that it's not a signed package or whatever. Anyone have any idea how I can get this sucker booted up and running using just an android tablet?
What about reflashing CWM so I can access my backups? Could I somehow flash CWM with factory recovery?:
Dr. Light said:
Anyone know of, or or have a link to a factory rom (hell any rom would do at this point) that I would be able to flash with the stock S3 recovery? Just trying to unbrick my phone. Story of what happened below:
I'm running stock 4.1.1 rooted touchwiz. I wake up this morning to a notification saying I had an update on my phone. Should have definitely waited but without thinking I went ahead and updated, which of course soft bricks? The phone. (boots up, and but hangs at the 4Glte, flash screen)normally this would be an easy fix, I could Odin back to stock or something but I'm down in Mississippi till Monday for training and do not have access to my pc.
I can access the factory recovery on the phone but that's it, have no clue where CWM is. I've tried flashing some backups but the factory recovery says that it's not a signed package or whatever. Anyone have any idea how I can get this sucker booted up and running using just an android tablet?
What about reflashing CWM so I can access my backups? Could I somehow flash CWM with factory recovery?:
Click to expand...
Click to collapse
first of all you can't flash anything on a stock recovery hence the need of a custom recovery. Second you don't accept the OTA when rooted as it can cause the exact issue that you have. Last there isn't a way to fix your problem via another android device that I know of.
U are going to need a pc and then u will need to download Odin http://forum.xda-developers.com/attachment.php?attachmentid=1165122&d=1340993443 and u can get the official software from here on XDA http://hotfile.com/dl/182822657/9f6...WBLK3_381038_REV09_user_low_ship.tar.md5.html this is the 4.1.1 software. Here is a link to some official pre rooted software http://forum.xda-developers.com/showthread.php?t=1984436 all of these software's you can install though Odin just look up here on XDA on how to use Odin and you will be fine once your phone is up and running again then you will need to get you a custom recovery. Then you can access your backups.
Always_Jonezen said:
U will need to download Odin http://forum.xda-developers.com/attachment.php?attachmentid=1165122&d=1340993443 and u can get the official software from here on XDA http://hotfile.com/dl/182822657/9f6...WBLK3_381038_REV09_user_low_ship.tar.md5.html this is the 4.1.1 software. Here is a link to some official pre rooted software http://forum.xda-developers.com/showthread.php?t=1984436 all of these software's you can install though Odin just look up here on XDA on how to use Odin and you will be fine once your phone is up and running again then you will need to get you a custom recovery.
Click to expand...
Click to collapse
He doesn't have access to his PC PLUS he already knows what to do on that end.
jmxc23 said:
He doesn't have access to his PC PLUS he already knows what to do on that end.
Click to expand...
Click to collapse
Just trying to help out but of course someone always has to criticize. I don't see you giving him any advice.
Thanks for all of advice guys. I'll prob just wait it out till Monday. Thanks again.
Always_Jonezen said:
Just trying to help out but of course someone always has to criticize. I don't see you giving him any advice.
Click to expand...
Click to collapse
He was asking if he can use an android tablet to fix his phone. He doesn't have access to PC at least until Monday it says so in his post. I wasn't even criticizing you at all. Unless he knows someone with a PC in Mississippi or someone here knows how to use one android device to flash something on another android device he sadly will have to wait until he gets home to fix his phone. You didn't do anything to be criticized for trying to help all I did was point out the info that you missed without personally attacking you making it a critique.
jmxc23 said:
He was asking if he can use an android tablet to fix his phone. He doesn't have access to PC at least until Monday it says so in his post. I wasn't even criticizing you at all. Unless he knows someone with a PC in Mississippi or someone here knows how to use one android device to flash something on another android device he sadly will have to wait until he gets home to fix his phone. You didn't do anything to be criticized for trying to help all I did was point out the info that you missed without personally attacking you making it a critique.
Click to expand...
Click to collapse
hey all, I've been reading , downloading etc for hours trying to get back into my GS3.. i was as usual roaming around and saw a post that said something to this effect "do ya need to get back to stock?" and figured yes i need to so i jumped in with both feet ..i had my boot loader unlocked and for some reason locked the darned thing remembering it was locked before i rooted and then i get the screen that says ie: "System software not authorized ~~~~~~~~~~~~" with a yellow triangle over it with an "!" mark in it..
all would have been ok except the line up of the way to do things was kinda outta line.. after i had locked bootloader "which is the way the GS3 came" i thought. at any rate i am now where i said i was and if i can be helped it would be appreciated.. and no repeated.. next time i'll read their whole line up first.. so help me if ya can and i am game right now for about anything ..
Not sure if my phone is a lost cause and only good as a door stop. My phone at one stage would only display a screen asking me to plug into smart switch to recover the phone so I tried that but smart switch wasn't happening. I downloaded the latest stock rom and installed it successfully via ODIN but now my phone will not get past the boot logo. I can only get into download mode, Any advise on if I can get my phone working again?
Thanks
Andrew
andrew88 said:
Not sure if my phone is a lost cause and only good as a door stop. My phone at one stage would only display a screen asking me to plug into smart switch to recover the phone so I tried that but smart switch wasn't happening. I downloaded the latest stock rom and installed it successfully via ODIN but now my phone will not get past the boot logo. I can only get into download mode, Any advise on if I can get my phone working again?
Thanks
Andrew
Click to expand...
Click to collapse
Bro, I've been there and this is why I made an account on xda to see if my s6 (G-920F) can be fixed in any way. Yesterday I had the same thing as you when I tried to re-flash the phone with its proper, latest stock-ROM (UK/EE Nougat 7.0). Given how it hadn't worked, the update attempt through Odin screaming a big "FAIL!" at me, I was afraid I had bricked it completely, so I proceeded to re-install TWRP with Odin by putting the phone in download mode. I wiped the phone again with TWRP and now I'm not sure what I have to do as I am stuck with the UK Nougat bootloader and nothing else on it.
Before this whole ordeal I had rooted the phone and unlocked the bootloader following some instructions from a Youtube video and successfully installed a nighty build of LineageOS, which was buggy as **** (couldn't answer calls, use data, use the camera and a ****ton of apps were just not working). Dumbly enough, I thought I could just remove it through a wipe and put something else back on it but oh was I wrong.
Right now I'd just want to get my phone back to working (like you), as I am out of a job and need to be able to take phone calls with a normal, working phone.
Sorry I couldn't be of much help, but yeah maybe a first step towards fixing it would be to flash TWRP recovery on it and through the terminal, see what bootloader version you have with the command "getprop ro.bootloader". At least you will know the version of the broken bootloader you're experiencing difficulties with and *hopefully* an actual dev from the forums will entertain themselves in trying to solve this noobish puzzle we've created for ourselves.
Seriously, if there is a dev ready to board this crazy adventure with us, please help.
My namesake or username is pretty much a clue to what got me into this position.
I wish it was that simple for me mate, I cant access the recovery menu, I've tried flashing various recovery options but cant boot into any of them. I'm certain I could fix the phone if I could get to recovery. I'm now leaning towards it being a hardware fault with my phone. As you have access to recovery I think you may have more luck with your phone.
TerribleChoices said:
Bro, I've been there and this is why I made an account on xda to see if my s6 (G-920F) can be fixed in any way. Yesterday I had the same thing as you when I tried to re-flash the phone with its proper, latest stock-ROM (UK/EE Nougat 7.0). Given how it hadn't worked, the update attempt through Odin screaming a big "FAIL!" at me, I was afraid I had bricked it completely, so I proceeded to re-install TWRP with Odin by putting the phone in download mode. I wiped the phone again with TWRP and now I'm not sure what I have to do as I am stuck with the UK Nougat bootloader and nothing else on it.
Before this whole ordeal I had rooted the phone and unlocked the bootloader following some instructions from a Youtube video and successfully installed a nighty build of LineageOS, which was buggy as **** (couldn't answer calls, use data, use the camera and a ****ton of apps were just not working). Dumbly enough, I thought I could just remove it through a wipe and put something else back on it but oh was I wrong.
Right now I'd just want to get my phone back to working (like you), as I am out of a job and need to be able to take phone calls with a normal, working phone.
Sorry I couldn't be of much help, but yeah maybe a first step towards fixing it would be to flash TWRP recovery on it and through the terminal, see what bootloader version you have with the command "getprop ro.bootloader". At least you will know the version of the broken bootloader you're experiencing difficulties with and *hopefully* an actual dev from the forums will entertain themselves in trying to solve this noobish puzzle we've created for ourselves.
Seriously, if there is a dev ready to board this crazy adventure with us, please help.
My namesake or username is pretty much a clue to what got me into this position.
Click to expand...
Click to collapse
andrew88 said:
I wish it was that simple for me mate, I cant access the recovery menu, I've tried flashing various recovery options but cant boot into any of them. I'm certain I could fix the phone if I could get to recovery. I'm now leaning towards it being a hardware fault with my phone. As you have access to recovery I think you may have more luck with your phone.
Click to expand...
Click to collapse
Oh dear.
Yeah it does sound like something got deeply ****ed up in this case. I had the luck to somehow get past the smart switch error when the phone died of low battery. As I attached it to the charger I quickly boot it into download mode before the screen would become a bootloop again and that's where I was able to reinstall the latest version of TWRP recovery. After that, I was able to flash a stock ROM of Nougat that didn't have a ****ed up bootloader like I had. Specifically the one from this thread: https://forum.xda-developers.com/galaxy-s6/help/device-5-binary-3-s6-sm-g920f-t3706025
by forumber2.
It's the Netherlands stock-ROM. Not sure if you're from the US and the carrier would be wrong with that CSC, but it was a good bet for me. I got my phone back to working normally now.
Worst case scenario I'd say see if you have a phone repair shop nearby and ask them an opinion on what could be wrong. I'm just an amateur like you.
Still, I wish you the best of luck with it. Maybe there's still some hope. :/