I am playing around with my old S3 and decided to root and load custom firmware. I was dumb and rooted via towelroot then installed Clockwork Recovery... before reading up on the fact that my S3 running 4.4.2 (Build I535VRUDNE1) has a locked bootloader. Whoops. Now my recovery seems to be bricked (Yellow Verizon triangle warning of unauthorized software).
I have followed the steps in this thread to flash the stock recovery using ODIN 3.09. I don't get any error messages and it appears successful within ODIN, but when I try to boot into recovery afterwards, I get the same yellow Verizon triangle.
For what it's worth, Odin mode is showing my binary count as 2 ("BOOTLADER RP SWREV: 2")
What am I doing wrong?
Posting in the wrong forum, this is for the i9300 only.
Report your own past and ask a moderator to move it for you.
Related
I have a Galaxy S3 from Verizon on 4.3. Right now im trying to install clockwork recovery with Odin. Buy Odin fails every time. I mean EVERY time! It stops right at the end for anything i try to do. Then says fail. Can someone Please help?
VZW S3s have a locked bootloader. You should not be attempting to install CWM via Odin on 4.3, especially. You must root and use SafeStrap Recovery.
http://forum.xda-developers.com/showthread.php?t=2605648
Greetings,
I recently rooted my Verizon 4.4.2 S3 using TowelRoot. (SCH-I535) Afterward I attempted to flash TWRP using ODIN. I kept getting an error message when flashing. I think tried TWRP Manager. I selected the proper IMG and flashed. It said flash successful. When I enter recovery I receive a LARGE yellow caution triangle with the message, "System Software not Authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest VW store for help."
I attempted to flash the factory recovery (Verizon-SCH-I535-StockRecovery.tar) using ODIN. It says the flash is successful but I still receive the same error message. My flash counter is at zero. Any idea how I can either get my factory Recovery back or get a functional recovery?
Thanks so much!
You're in the wrong forum.
This is only for the s3 i9300 INTERNATIONAL.
Everything you try to flash will brick you're phone.
Send From A Devil3 - f2fs - Dualboot Jb4.3/cm11 Powered Machine
I have a Verizon Note 2 running 4.4.2.
I successfully rooted it without unlocking the bootloader or flashing a custom recovery, everything was stock. Everything worked fine after and I was able to use root-requiring apps.
Then, after attempting to flash custom recovery, since the bootloader was locked, I am now stuck at the screen that says: "System software not authorized by Verizon Wireless has been found on your phone..."
I am able to enter recovery (the stock recovery) as well as go into download mode. Normally this wouldn't be a problem as I could just flash stock through Odin in download mode.
However, ever since the soft-brick Odin won't recognize my phone (the yellow COM square does not come up), which is strange because Odin recognized my Note 2 in download mode before this happened.
And even stranger is the fact that it is not a driver issue, as when I plug in my Note 2 in download mode I get a message from Windows 7 saying that the serial gadget device driver was found and installed successfully (and the phone also shows up in Device Manager in control panel as fully installed while in download mode.
Yet Odin won't recognize it.
I have spent days searching for an answer and have yet to come across an issue identical to mine (everyone seems to be able to just flash stock through Odin to fix this particular soft-brick, but Odin is not recognizing my device), so I finally decided to post here.
Any suggestions at all are welcome as I am somewhat desperate at this point. I'd just like to get it back to stock (or flash a custom rom, it does not matter as long as I can get the phone to work).
I would like to point out that I have already tried the following:
- Different USB ports
- Using different USB cables
- Uninstalling and reinstalling the drivers
- Wipe/Factory Reset in stock recovery
From what I can see, my only options are to either somehow get Odin to recognize the phone (suggestions welcome here), or somehow flash stock through the default recovery (if possible, again, any input is appreciated).
William31 said:
I have a Verizon Note 2 running 4.4.2.
I successfully rooted it without unlocking the bootloader or flashing a custom recovery, everything was stock. Everything worked fine after and I was able to use root-requiring apps.
Then, after attempting to flash custom recovery, since the bootloader was locked, I am now stuck at the screen that says: "System software not authorized by Verizon Wireless has been found on your phone..."
I am able to enter recovery (the stock recovery) as well as go into download mode. Normally this wouldn't be a problem as I could just flash stock through Odin in download mode.
However, ever since the soft-brick Odin won't recognize my phone (the yellow COM square does not come up), which is strange because Odin recognized my Note 2 in download mode before this happened.
And even stranger is the fact that it is not a driver issue, as when I plug in my Note 2 in download mode I get a message from Windows 7 saying that the serial gadget device driver was found and installed successfully (and the phone also shows up in Device Manager in control panel as fully installed while in download mode.
Yet Odin won't recognize it.
I have spent days searching for an answer and have yet to come across an issue identical to mine (everyone seems to be able to just flash stock through Odin to fix this particular soft-brick, but Odin is not recognizing my device), so I finally decided to post here.
Any suggestions at all are welcome as I am somewhat desperate at this point. I'd just like to get it back to stock (or flash a custom rom, it does not matter as long as I can get the phone to work).
I would like to point out that I have already tried the following:
- Different USB ports
- Using different USB cables
- Uninstalling and reinstalling the drivers
- Wipe/Factory Reset in stock recovery
From what I can see, my only options are to either somehow get Odin to recognize the phone (suggestions welcome here), or somehow flash stock through the default recovery (if possible, again, any input is appreciated).
Click to expand...
Click to collapse
Wow... I'm stumped too as to why Odin won't recognize the phone. What method did you use to try to flash the custom recovery and what recovery did you flash? (You probably know now, but just in case.... if you can get the phone restored to stock 4.4.2 again... then you can't flash a standard custom recovery onto the phone because of the bootloader being locked down. You can use the modified TWRP called Safestrap recovery if you root again... and can only flash 4.4.2 touchwiz roms with stock 4.4.2 kernel after you get rooted again).
When you rooted, all I can think of is that something may have corrupted the drivers somehow and that's now conflicting with ODIN. With the phone in download mode... have have you went into the PC's Device Manager and tried to delete/reinstall any Samsung related drivers, (make sure to look for hidden drivers.... click scan for hardware changes after deleting them and the computer should reinstall the correct drivers). Also... have you made sure no other conflicting programs (like Kies) are running in the background?
You might try to do a system restore to an earlier point on your PC where ODIN recognized the phone to see if that would work.
If ODIN version 3.07 isn't recognizing the phone, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed.
Good luck!
mattnmag said:
Wow... I'm stumped too as to why Odin won't recognize the phone. What method did you use to try to flash the custom recovery and what recovery did you flash? (You probably know now, but just in case.... if you can get the phone restored to stock 4.4.2 again... then you can't flash a standard custom recovery onto the phone because of the bootloader being locked down. You can use the modified TWRP called Safestrap recovery if you root again... and can only flash 4.4.2 touchwiz roms with stock 4.4.2 kernel after you get rooted again).
When you rooted, all I can think of is that something may have corrupted the drivers somehow and that's now conflicting with ODIN. With the phone in download mode... have have you went into the PC's Device Manager and tried to delete/reinstall any Samsung related drivers, (make sure to look for hidden drivers.... click scan for hardware changes after deleting them and the computer should reinstall the correct drivers). Also... have you made sure no other conflicting programs (like Kies) are running in the background?
You might try to do a system restore to an earlier point on your PC where ODIN recognized the phone to see if that would work.
If ODIN version 3.07 isn't recognizing the phone, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed.
Good luck!
Click to expand...
Click to collapse
So I tried recovering with Kies and it just kept throwing errors at me, then finally I just closed it and, am not quite sure why, but went into Odin and it worked! Apparently trying to recover with Kies somehow fixed the Odin issue and I was able to flash stock through Odin. Thanks so much!
You mentioned there was a way to flash a safestrap recovery and then flash touchwiz roms? Do you by chance have instructions on how I could do this, or links to this information...?
William31 said:
So I tried recovering with Kies and it just kept throwing errors at me, then finally I just closed it and, am not quite sure why, but went into Odin and it worked! Apparently trying to recover with Kies somehow fixed the Odin issue and I was able to flash stock through Odin. Thanks so much!
You mentioned there was a way to flash a safestrap recovery and then flash touchwiz roms? Do you by chance have instructions on how I could do this, or links to this information...?
Click to expand...
Click to collapse
Cool. Glad you got it fixed.
As you know, you can root with GhettoRoot from this thread: http://forum.xda-developers.com/showthread.php?p=57238246
Then can install Safestrap from this thread: http://forum.xda-developers.com/showthread.php?p=51616723
I've never used Safestrap because I can use regular custom recoveries like CWM and TWRP. I'm still on a 4.1.2 unlocked bootloader and currently running TrentsKKRom, Build #2...which is 4.4.2 based with stock kernel, so I think it would work with Safestrap.
I'd recommend reading through the Safestrap thread thoroughly and asking questions there to make sure you get everything installed correctly. I've read that with Safestrap, you need to make a backup of your Stock ROM first and save it somewhere safe, like to your computer and on your external sd card...so you can easily restore it if needed. (I'd also make a backup of the ESF in Safestrap if it lets you, then save it somewhere safe).
After you are rooted with Safestrap, you'll have to flash custom ROM's over the stock slot in Safestrap, as the other slots apparently don't work. Again, you're limited to only using Touchwiz ROM's with the stock kernel because of the bootloader still being locked.
Check out TrentsKKRom and Alliance build 30 . (I personally like Trent's build 2 best with the S5 clean theme). I've also found Trent's ROM to be really smooth without UI lagging, the Bluetooth works good with no stuttering, and it pairs well with my Sony Smartwatch 3. (Edit: If you do try Trent's ROM, you may need to install a couple apps.... Chainfire's Supersu app to control your root permissions (at least I needed to), and the FolderMount app to fix a KitKat internal storage mounting issue).
Have fun!!
Had my phone rooted with 4.4.4
Wanted to upgrade to 5.0. Went with Stock firmware
I try to "reroot" install CWM with ODIN -Pass
Used CF Auto Root - Failed
I try to get into the recovery screen and I get an error that say s Firmware Upgrade encountered an issue.. Use Kies to restore.
Problem here is Kies will not recognize my S/N and in talking to their support they claim kies can't be used after a phone has been rooted.
Just a side note I was having problems before I upgraded the ROM woudl get that error saying SEANDROID not enforcing. I was hoping the new firmware would resolve this. I don't get this error anymore but can't get into recovery either.
Thoughts?
chewyma said:
Had my phone rooted with 4.4.4
Wanted to upgrade to 5.0. Went with Stock firmware
I try to "reroot" install CWM with ODIN -Pass
Used CF Auto Root - Failed
I try to get into the recovery screen and I get an error that say s Firmware Upgrade encountered an issue.. Use Kies to restore.
Problem here is Kies will not recognize my S/N and in talking to their support they claim kies can't be used after a phone has been rooted.
Just a side note I was having problems before I upgraded the ROM woudl get that error saying SEANDROID not enforcing. I was hoping the new firmware would resolve this. I don't get this error anymore but can't get into recovery either.
Thoughts?
Click to expand...
Click to collapse
If you can get into Download Mode you can Odin 5.0
May is Motorcycle Awareness Month Sent from my Galaxy Note 3
I did that, I was able to get 5.0 running..
So I installed CWM with Odin and that installed.
Used Odin for CF Root. it failed..
Can't get into recovery either as if I do it goes that error then I"m stuck there. Seems like the only way I can get out of it is to reinstall 5.0 fully via Odin then I'm back in business.
chewyma said:
I did that, I was able to get 5.0 running..
So I installed CWM with Odin and that installed.
Used Odin for CF Root. it failed..
Can't get into recovery either as if I do it goes that error then I"m stuck there. Seems like the only way I can get out of it is to reinstall 5.0 fully via Odin then I'm back in business.
Click to expand...
Click to collapse
I was under the impression that you needed to root first, Then install a recovery? maybe it doesn't make a difference...
but I would try Odin the stock tar,
then Odin cf auto root
then Odin twrp
worked perfectly for me.
(also, I don't ever use kies for anything. ever.)
Hi, I have a GS4 (SCH-I545) and I tried to get TWRP and then CyangenMod, so I rooted my phone, used ROM Manager to get TWRP, rebooted into recovery, only to get the stock recovery. So I tried Flashify, rebooted, but got the Verizon warning screen, so then I used the workaround to get back in to my phone. I then tried again but then I couldn't get bacl into a recovery mode, just odin mode with "Could not do normal boot" in the top left. So I did the workaround again, I then figured something was wrong with the bootloader, so I used Flashify to flash "a-boot.img" hoping it would work, now I can't get into recovery mode, can't get into Android, can't even charge my phone, the odin mode will always come on, I can go intpo normal odin mode though, but that's it, I can't do anything on my phone, only go into odin mode, so I guess I've bricked my phone. What should I do?
SolidSG said:
Hi, I have a GS4 (SCH-I545) and I tried to get TWRP and then CyangenMod, so I rooted my phone, used ROM Manager to get TWRP, rebooted into recovery, only to get the stock recovery. So I tried Flashify, rebooted, but got the Verizon warning screen, so then I used the workaround to get back in to my phone. I then tried again but then I couldn't get bacl into a recovery mode, just odin mode with "Could not do normal boot" in the top left. So I did the workaround again, I then figured something was wrong with the bootloader, so I used Flashify to flash "a-boot.img" hoping it would work, now I can't get into recovery mode, can't get into Android, can't even charge my phone, the odin mode will always come on, I can go intpo normal odin mode though, but that's it, I can't do anything on my phone, only go into odin mode, so I guess I've bricked my phone. What should I do?
Click to expand...
Click to collapse
Well, first of all, if your galaxy didn't have the MDK bootloader (first version of firmware, android 4.2.2) you are not able to get CM nor Recovery (CWM, TWRP...), because Verizon locked the bootloader in all the other versions. If you touched our "lovely" bootloader you could have messed up your device, but you can get into download mode so you should try downloading a stock rom equal or newer to the android version you used to have before you bricked your device (you cannot downgrade your phone), if that doesn't work you can try Samsung Smart Switch to repair it.
Okay ill try downloadig a stock rom, but I don't really know how to do it, got any links telling how?
Well, we can't point you to a stock ROM to odin with. You can't just simply Odin back to MDK. That has been blocked off by a physical qfuse, which will further mess up your device. Can you get into download mode and tell us what version do you have?
All download mode says is this: odin mode
Product name: SCH-I545
Current binary: Samsung Official
System status: custom
CSB-CONFIG-LSB: 0x30
Write protection: Enable
eMMC BURST MODE enabled
Nothing about the version
Id say the version I have was later than 4.2.2 considering I couldn't get a recovery working, the previous owner updated it some time in early 2014 maybe june so any version of KitKat later than that might work