Hey everyone,
Recently I rooted my GS3 using this thread:
http://forum.xda-developers.com/showthread.php?t=1984436
After a successful root, I tried to run CWM and all of the sudden it rebooted to a screen that said "software not authorized by Verizon Wireless". This is not so much a problem since I can just boot into downloading mode and then cancel and it will boot normally, but it seems I have tripped the flash counter.
My question is whether or not you think my bootloader is unlocked. I want to unroot my phone because I realize that I do not know enough information about rooting to continue with custom ROMs and I am having connectivity issues after I rooted so I want to go back to factory settings. I want to know the best way to unroot my phone, I have read that I need to use Triangle Away, but it says that it will brick my phone if I use it on a locked bootloader, so I am not sure what to do at this point.
Please let me know if anyone has some suggestions!
Thanks :good:
twofooted said:
Hey everyone,
Recently I rooted my GS3 using this thread:
http://forum.xda-developers.com/showthread.php?t=1984436
After a successful root, I tried to run CWM and all of the sudden it rebooted to a screen that said "software not authorized by Verizon Wireless". This is not so much a problem since I can just boot into downloading mode and then cancel and it will boot normally, but it seems I have tripped the flash counter.
My question is whether or not you think my bootloader is unlocked. I want to unroot my phone because I realize that I do not know enough information about rooting to continue with custom ROMs and I am having connectivity issues after I rooted so I want to go back to factory settings. I want to know the best way to unroot my phone, I have read that I need to use Triangle Away, but it says that it will brick my phone if I use it on a locked bootloader, so I am not sure what to do at this point.
Please let me know if anyone has some suggestions!
Thanks :good:
Click to expand...
Click to collapse
Sounds like you understand most of it, you just didn't unlock your bootloader properly.
Download ez unlock version 1.2 and install that, you can unlock your bootloader from there. At that point you can flash any custom rom or use your custom recovery without issues. But if you want to go back to stock...
Download triangle away then run it, that will reset your flash counter.
Then Odin flash a stock Rom, then accept any ota needed, then you're completely stock.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Download ez unlock version 1.2 and install that, you can unlock your bootloader from there. At that point you can flash any custom rom or use your custom recovery without issues. But if you want to go back to stock...
Download triangle away then run it, that will reset your flash counter.
Then Odin flash a stock Rom, then accept any ota needed, then you're completely stock
Click to expand...
Click to collapse
Thanks, will I need to still download ez unlock before running triangle away?
twofooted said:
Thanks, will I need to still download ez unlock before running triangle away?
Click to expand...
Click to collapse
I think so, you mentioned that the app needed you to have the bootloader unlocked. EZ unlock is how you do that, so I would do that first.
BadUsername said:
I think so, you mentioned that the app needed you to have the bootloader unlocked. EZ unlock is how you do that, so I would do that first.
Click to expand...
Click to collapse
Thanks! EZ-Unlock worked perfectly. I went ahead and unlocked the bootloader and flashed CM 10.2. Figured I might as well try something out while its rooted.
twofooted said:
Thanks! EZ-Unlock worked perfectly. I went ahead and unlocked the bootloader and flashed CM 10.2. Figured I might as well try something out while its rooted.
Click to expand...
Click to collapse
That's exactly what I wanted you to say, hope you have a good experience.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
That's exactly what I wanted you to say
Click to expand...
Click to collapse
Glad I could make your night. Working great so far, thanks again for the help.
Related
I was doing my normal thing flashing roms, and i have everything set up. I was on stock touchwiz firmware, and it was rooted and unlocked, and i try to download Slim Rom, and once it flashed i reboot and get a yellow triangle that says i cannot start the device.
Can anyone help me please?! I dont want to bring it to Verizon!
your bootloader is not unlocked...use the ez unlock 1.1 or 1.2 app. If you already use the app then make sure you grant super user permissions and the binaries in SU are up to date.
I am bricked
Chuckleb0ne said:
I am bricked
Click to expand...
Click to collapse
You're not bricked. You just have to flash back to stock by using odin and use ez-bootunlock.
emckai said:
You're not bricked. You just have to flash back to stock by using odin and use ez-bootunlock.
Click to expand...
Click to collapse
well he is but he isn't......he's soft-bricked meaning that it is still recoverable......if he was hardbricked he wouldn't be able to even see that yellow triangle.........but yeah, do like emckai said and odin back to root66 stock rooted image and then use ez-bootunlock version 1.2 (not 1.4 because its glitchy, theres a link to it on the market for the 1.4 version) to unlock your bootloader and you're good to go
If you haven't already, do the following here:
http://forum.xda-developers.com/showthread.php?t=1840030
I had that Triangle of Death before. The above method saved me.
Samsung.Galaxy.S3 said:
If you haven't already, do the following here:
http://forum.xda-developers.com/showthread.php?t=1840030
I had that Triangle of Death before. The above method saved me.
Click to expand...
Click to collapse
Don't need all that. Just odin back to stock rooted and start over with unlocked boot loader.
Basically I'm asking before I apply the ORA whether or not it will be a harder, easier, or exactly the same process to get root and unlock the bootloader.
Any extra steps to flash or incompatible roms afterwards?
Just curious. I am not rooted but have studied the process to where I know I could if I wanted to. Wondering if applying the OTA will change what I already know and/or make it harder to get root.
Sent from my SCH-I535 using xda app-developers app
GoodVibrant-ions said:
Basically I'm asking before I apply the ORA whether or not it will be a harder, easier, or exactly the same process to get root and unlock the bootloader.
Any extra steps to flash or incompatible roms afterwards?
Just curious. I am not rooted but have studied the process to where I know I could if I wanted to. Wondering if applying the OTA will change what I already know and/or make it harder to get root.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Check out this thread over in the dev section.
http://forum.xda-developers.com/showthread.php?t=2046439
GoodVibrant-ions said:
Basically I'm asking before I apply the ORA whether or not it will be a harder, easier, or exactly the same process to get root and unlock the bootloader.
Any extra steps to flash or incompatible roms afterwards?
Just curious. I am not rooted but have studied the process to where I know I could if I wanted to. Wondering if applying the OTA will change what I already know and/or make it harder to get root.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I re rooted after going back to stock ICS. Verified root, then upgraded to OTA Jellybean. Root stayed via OTA Rootkeeper.
GoodVibrant-ions said:
Basically I'm asking before I apply the ORA whether or not it will be a harder, easier, or exactly the same process to get root and unlock the bootloader.
Any extra steps to flash or incompatible roms afterwards?
Just curious. I am not rooted but have studied the process to where I know I could if I wanted to. Wondering if applying the OTA will change what I already know and/or make it harder to get root.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
If you use cwm6 you won't lose anything. Accept the update, after booting into recovery cwm will ask if you want to install un trusted . zip. Say yes. It installs, just before reboot it will ask if you want to keep root, then ask if you want to keep custom recovery. Answer yes and you're good. It will reboot and say update failed but that's just because you kept the recovery. If you go to check for update it will say you are up to date.
Frunple said:
If you use cwm6 you won't lose anything. Accept the update, after booting into recovery cwm will ask if you want to install un trusted . zip. Say yes. It installs, just before reboot it will ask if you want to keep root, then ask if you want to keep custom recovery. Answer yes and you're good. It will reboot and say update failed but that's just because you kept the recovery. If you go to check for update it will say you are up to date.
Click to expand...
Click to collapse
This is correct. Same thing happened on my rooted GS 3. The update menu said "failed" but the update did actually take.
But don't do what I just did: try to back up the ROM Manager. It will not make the phone happy. Now stuck at the soft brick screen. Argh
Knightvision said:
This is correct. Same thing happened on my rooted GS 3. The update menu said "failed" but the update did actually take.
But don't do what I just did: try to back up the ROM Manager. It will not make the phone happy. Now stuck at the soft brick screen. Argh
Click to expand...
Click to collapse
If you haven't already fixed it, this happened to me upgrading to the various JB leaks once when I forgot to re-unlock the bootloader and tried to boot into CWM recovery. It gave me the Verizon warning screen, but I was able to use the Vol. Down + Home method to get into download mode and then just had the phone reboot. It booted normally and then you can use EZ-unlock to unlock the bootloader again. It might tell you that it is already unlocked, which isn't right so lock it and then unlock it.
BigErnM said:
If you haven't already fixed it, this happened to me upgrading to the various JB leaks once when I forgot to re-unlock the bootloader and tried to boot into CWM recovery. It gave me the Verizon warning screen, but I was able to use the Vol. Down + Home method to get into download mode and then just had the phone reboot. It booted normally and then you can use EZ-unlock to unlock the bootloader again. It might tell you that it is already unlocked, which isn't right so lock it and then unlock it.
Click to expand...
Click to collapse
I can confirm that this method works. I used Voodoo to keep my root and then answered yes to allowing CWM to install the unsigned .zip and answered yes to keeping root. I then got the dreaded Verizon warning triangle and was prepared to Odin back to Stock and start over. Just by chance I went into download mode and it allowed me boot my Rom. Once in, I checked EZ-unlock and it said I was unlocked, so I went ahead and locked and then unlocked and all was good! Hope this helps saves someone else some hassle.
Real_JESRadio said:
I re rooted after going back to stock ICS. Verified root, then upgraded to OTA Jellybean. Root stayed via OTA Rootkeeper.
Click to expand...
Click to collapse
man I tried this but it didnt work rootkeeper says its rooted but no root access the super user app is there...could i have done something wrong?? do i have do something after i upgrade to get to work?? thanx
BigErnM said:
If you haven't already fixed it, this happened to me upgrading to the various JB leaks once when I forgot to re-unlock the bootloader and tried to boot into CWM recovery. It gave me the Verizon warning screen, but I was able to use the Vol. Down + Home method to get into download mode and then just had the phone reboot. It booted normally and then you can use EZ-unlock to unlock the bootloader again. It might tell you that it is already unlocked, which isn't right so lock it and then unlock it.
Click to expand...
Click to collapse
It's fixed now. The CMW recovery mode wasn't working for some reason. Whatever broke ROM Manager did so by breaking CMW Recovery. I blame myself for stupidly trying to run a backup like that. Anyway, all I could get was the triangle screen and it would only reboot to that or the CMW that wasn't working. Ended up putting it in Odin mode and reflashing with one of the no-wipe leaks. Works fine now. And VZW says I am up to date.
Will get around to rerooting/unlocking again later today. And smacking myself for getting into this mess.
Good to learn from mistakes that are not fatal. Good to have LOTS of resources to figure out how to bail it out too!
Phone - Galaxy S3 I535 (Verizon)
Currently on 4.1.1
I535VRBLK3
Kernel Version 3.0.31-381038
I used this guide to root (http://galaxys3root.com/galaxy-s3-root/how-to-root-verizon-galaxy-s3-sch-i535/) and want to install this custom rom (http://forum.xda-developers.com/showthread.php?t=2028443) as an end product.
Alright, so I had a rooted phone, wanted to get the 4.1.2 pushed update, wouldn't work, and stripped my phone to unrooted, stock ROM with a factory data wipe. So far I've gotten back to rooting my phone, downloading ROM manager, and flashing CWM recovery successfully. However, when I go to reboot into recovery mode, it won't load anything, saying "Unauthorized Software was detected blah blah blah" and then at the top it says "Secure Fail: Kernel".
I've been searching and I can't find anything that makes sense to try, and I don't want to brick my phone. I have no idea what to do from here, so does anyone have any advice or a fix? I can navigate a computer with the best of them, but these androids are throwing me for a loop.
Thanks in advance guys.
You need to make sure the bootloader is unlocked before you can boot into recovery. As long as you have functional root access you can download EZ-Unlock version 1.2 and install it. Then run it and click unlock. If it tells you that you are already unlocked, click lock and then unlock. You can find it various places here on the forums.
Haha, as soon as I ran through that, it worked like a charm thanks for the advice
Help Please!
Eroth said:
Phone - Galaxy S3 I535 (Verizon)
Currently on 4.1.1
I535VRBLK3
Kernel Version 3.0.31-381038
I used this guide to root (http://galaxys3root.com/galaxy-s3-root/how-to-root-verizon-galaxy-s3-sch-i535/) and want to install this custom rom (http://forum.xda-developers.com/showthread.php?t=2028443) as an end product.
Alright, so I had a rooted phone, wanted to get the 4.1.2 pushed update, wouldn't work, and stripped my phone to unrooted, stock ROM with a factory data wipe. So far I've gotten back to rooting my phone, downloading ROM manager, and flashing CWM recovery successfully. However, when I go to reboot into recovery mode, it won't load anything, saying "Unauthorized Software was detected blah blah blah" and then at the top it says "Secure Fail: Kernel".
I've been searching and I can't find anything that makes sense to try, and I don't want to brick my phone. I have no idea what to do from here, so does anyone have any advice or a fix? I can navigate a computer with the best of them, but these androids are throwing me for a loop.
Thanks in advance guys.
Click to expand...
Click to collapse
BigErnM said:
You need to make sure the bootloader is unlocked before you can boot into recovery. As long as you have functional root access you can download EZ-Unlock version 1.2 and install it. Then run it and click unlock. If it tells you that you are already unlocked, click lock and then unlock. You can find it various places here on the forums.
Click to expand...
Click to collapse
Sorry to resurrect an older post, but I have the same exact problem as the OP, but I have 4.3 on the S3. I've read in other forums that the bootloader cannot be unlocked on 4.3, and that trying to do so will brick the phone. So what do I do? Shouldn't I still be able to boot into recovery even with a locked bootloader?
psteichen said:
Sorry to resurrect an older post, but I have the same exact problem as the OP, but I have 4.3 on the S3. I've read in other forums that the bootloader cannot be unlocked on 4.3, and that trying to do so will brick the phone. So what do I do? Shouldn't I still be able to boot into recovery even with a locked bootloader?
Click to expand...
Click to collapse
In short you don't need to have an unlocked bootloader to enter recovery, but you do need one to install a custom recovery.
Got the Casual Root, Unlock Bootloader, Install Custom Recovery .jar file about a week ago. Rooted my phone, no problem. A few days later unlocked the bootloader, no problem. Just installed ClockWorkMod Touch Recovery and tried to boot into it and got the yellow triangle with "System software not authorized by Verizon found on your phone. Turn off and go to store for help. At the top in red "Secure Fail:Kernel. Did I just brick my phone? Searched for a way out and found a few but they are for 4.3 and I'm running 4.1.1 and not sure if it's even bricked. Help would be appreciated. Thanks in advance.
BoJatey said:
Got the Casual Root, Unlock Bootloader, Install Custom Recovery .jar file about a week ago. Rooted my phone, no problem. A few days later unlocked the bootloader, no problem. Just installed ClockWorkMod Touch Recovery and tried to boot into it and got the yellow triangle with "System software not authorized by Verizon found on your phone. Turn off and go to store for help. At the top in red "Secure Fail:Kernel. Did I just brick my phone? Searched for a way out and found a few but they are for 4.3 and I'm running 4.1.1 and not sure if it's even bricked. Help would be appreciated. Thanks in advance.
Click to expand...
Click to collapse
You unlocked through casual right? Sometimes it doesn't always take properly.
Boot into download mode, and hit volume down to force the phone to boot into the system. Download ez unlock version 1.2 and install it, open it and unlock, then you're good to go.
If you can't get that to work, you need to Odin this rom, reroot with casual, then get ez unlock and make sure you're unlocked before you flash a custom recovery:
http://www.androidfilehost.com/?fid=23134718111254196
Sent from my SCH-I535 using Tapatalk 2
Yeah, tried to unlock with Casual. Tried DL mode before I posted and didn't work. Worked now and up and running. So the phone locked because bootloader wasn't unlocked when I tried to flash recovery. Got it. Thanks, thought I bricked it.
BoJatey said:
Yeah, tried to unlock with Casual. Tried DL mode before I posted and didn't work. Worked now and up and running. So the phone locked because bootloader wasn't unlocked when I tried to flash recovery. Got it. Thanks, thought I bricked it.
Click to expand...
Click to collapse
You did brick it.
Easy fix though, glad you are up and running again quickly.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
You did brick it.
Easy fix though, glad you are up and running again quickly.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thank you again. Installed the latest CWM Touch I think and now just need to pick a ROM. With my DroidX all I had to do was root , install recovery and flash. Now I'm seeing custom kernels and modems and firmware. Think I'll read a little more and flash on the weekend. Thanks again. By the way, which Rom did you link me to that you wanted me to flash?
Added later: Going to go ahead and flash that zip you sent. It doesn't say what it is but I think it's the 4.1.2 stock or some version of it. Want to get on that before I try customs. Thanks again.
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
eatcyanide said:
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
Click to expand...
Click to collapse
Do you have a custom recovery or flashed a kernel? You must be 100% stock
Sent from my Nexus 5 using XDA Free mobile app
I'm on stock android. The only thing I have changed is rooting it and unlocking it
Sent from my Nexus 5
eatcyanide said:
I'm on stock android. The only thing I have changed is rooting it and unlocking it
Sent from my Nexus 5
Click to expand...
Click to collapse
I am stuck in the same situation. Tried it twice with no luck.
I too rooted my phone with towelroot and unrooted it with superSu.
Did you find any solution? Please do share. Thanks.
eatcyanide said:
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
Click to expand...
Click to collapse
rahul9five said:
I am stuck in the same situation. Tried it twice with no luck.
I too rooted my phone with towelroot and unrooted it with superSu.
Did you find any solution? Please do share. Thanks.
Click to expand...
Click to collapse
You either have a modified system file or a file left over from being rooted. The easiest and fastest solution would be to fastboot flash the system image. You could of course flash the factory image.
wantabe said:
You either have a modified system file or a file left over from being rooted. The easiest and fastest solution would be to fastboot flash the system image. You could of course flash the factory image.
Click to expand...
Click to collapse
Well now i remember changing the mixer_path.xml ... Will i have to unlock my bootloader to flash the factory image as i had rooted my phone with towelroot so i didnt have to do it earlier..
Also is it possible to replace the mixer path file with the original one from the internet
rahul9five said:
Well now i remember changing the mixer_path.xml ... Will i have to unlock my bootloader to flash the factory image as i had rooted my phone with towelroot so i didnt have to do it earlier..
Also is it possible to replace the mixer path file with the original one from the internet
Click to expand...
Click to collapse
That sucks! ; ) I've always used the sdk so I don't know a whole lot about towelroot. Your bootloader will have to be unlocked to flash the factory image. If you can reroot you could then use the app BootUnlocker.
I just looked and I don't have the stock mixer_paths.xml anymore or I would link to it.
wantabe said:
That sucks! ; ) I've always used the sdk so I don't know a whole lot about towelroot. Your bootloader will have to be unlocked to flash the factory image. If you can reroot you could then use the app BootUnlocker.
I just looked and I don't have the stock mixer_paths.xml anymore or I would link to it.
Click to expand...
Click to collapse
Thankyou for your efforts and advise. I guess i will just rerrot with towelroot, unclock the bootloader with the app you suggestee and flash factory image..
Btw. Will flashing the factory image unroot my phone and lock the bootloader or is there some procedure that needs to be done to do that?
rahul9five said:
Thankyou for your efforts and advise. I guess i will just rerrot with towelroot, unclock the bootloader with the app you suggestee and flash factory image..
Btw. Will flashing the factory image unroot my phone and lock the bootloader or is there some procedure that needs to be done to do that?
Click to expand...
Click to collapse
Flashing the factory image or a system image will always unroot your device. Lock the bootloader using the sdk. The command is fastboot oem lock.
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
beekay201 said:
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
Click to expand...
Click to collapse
Yea, you can't flash the ota through a custom recovery anymore
Sent from my Nexus 9 using XDA Free mobile app
beekay201 said:
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
Click to expand...
Click to collapse
Thankyou.. I am more of a soft modder. Like playing with rooted apps and xposed mainly. I dont see myself flashing a custom rom. Love the stock on my nexus 5. So i dont see the need to leave the bootloader unlocked.
rahul9five said:
Thankyou.. I am more of a soft modder. Like playing with rooted apps and xposed mainly. I dont see myself flashing a custom rom. Love the stock on my nexus 5. So i dont see the need to leave the bootloader unlocked.
Click to expand...
Click to collapse
Err... I didn't suggest that you flash a custom ROM. Read what I said.