Related
thanky you to anyone ahead of time for reading this post. I really could use some help.
I have a Verizon galaxy s3 which I rooted 3 weeks ago when i got it. I know it was rooted as i had super user permissions, and deleted many bloatware apps. I waited until cm10 came out to flash a new rom and after doing so last night my phone now boots up with this message "System software not authorized by verizon wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
So I tried to boot it in to recovery mode but when I did, the same message came up, only this time it said "recovery booting" in small blue writing in the top left corner.
I followed the directions to a T from a page entitled "Jelly Bean for Verizon Galaxy S3: Unofficial CyanogenMod 10 (CM10) Nightlies Available for Flashing!
From what I understand, the bootloader was somehow never unlocked by kexec. because I cant get in to recovery mode, I was wondering if there was a way to disable the bootlock by installing kexec via odin.
Also, whether it was a good idea or not, I re flashed the stock rom via oden last, which was successful but, nothing has changed still the same response all boot ups. Download boot obviously works though as I have been able to mess with it in odin.
any insight on this would be graciously appreciated.
Lembro said:
thanky you to anyone ahead of time for reading this post. I really could use some help.
I have a Verizon galaxy s3 which I rooted 3 weeks ago when i got it. I know it was rooted as i had super user permissions, and deleted many bloatware apps. I waited until cm10 came out to flash a new rom and after doing so last night my phone now boots up with this message "System software not authorized by verizon wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
So I tried to boot it in to recovery mode but when I did, the same message came up, only this time it said "recovery booting" in small blue writing in the top left corner.
I followed the directions to a T from a page entitled "Jelly Bean for Verizon Galaxy S3: Unofficial CyanogenMod 10 (CM10) Nightlies Available for Flashing!
From what I understand, the bootloader was somehow never unlocked by kexec. because I cant get in to recovery mode, I was wondering if there was a way to disable the bootlock by installing kexec via odin.
Also, whether it was a good idea or not, I re flashed the stock rom via oden last, which was successful but, nothing has changed still the same response all boot ups. Download boot obviously works though as I have been able to mess with it in odin.
any insight on this would be graciously appreciated.
Click to expand...
Click to collapse
Okay, first, If you did follow the directions for that thread, i'm sure it would of worked, I'm pretty sure you are missing something here and i'm pretty sure from reading your post that I think you didn't unlock your bootloader. kexec was a workaround for the locked bootloader, it doesn't unlock it. I would follow droidstyle's guide to unlocking the bootloader, http://forum.xda-developers.com/showpost.php?p=28530409&postcount=2 after you unlocked it, i'm pretty sure you forgot that step. But the issue when flashing back to stock via odin and still showing up its a custom rom, I don't know why that would happen but I suggest reading section 2 of droidstyle's guide on flashing back to stock. http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
So first, I suggest to return to stock, then root, then unlock bootloader, and then install the rom of your choice, preferably without kexec, if you don't want the triple reboot.
RyanW114 said:
Okay, first, If you did follow the directions for that thread, i'm sure it would of worked, I'm pretty sure you are missing something here and i'm pretty sure from reading your post that I think you didn't unlock your bootloader. kexec was a workaround for the locked bootloader, it doesn't unlock it. I would follow droidstyle's guide to unlocking the bootloader, http://forum.xda-developers.com/showpost.php?p=28530409&postcount=2 after you unlocked it, i'm pretty sure you forgot that step. But the issue when flashing back to stock via odin and still showing up its a custom rom, I don't know why that would happen but I suggest reading section 2 of droidstyle's guide on flashing back to stock. http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
So first, I suggest to return to stock, then root, then unlock bootloader, and then install the rom of your choice, preferably without kexec, if you don't want the triple reboot.
Click to expand...
Click to collapse
Agreed! Op, do more reading and less flashing before you end up with a 600.00 paperweight!
Like he says above you have not unlocked your bootloader . Restore nandroid or recover to stock. Then unlock your bootloader and try again
Sent from my SCH-I535 using xda premium
Get rid of the Verizon screen of death
I got the same error msg after flashing a nightly of d2hacker's unofficial cm10, after I had flashed a few nightly's before of the same ROM w/ no problems. I had to
1. Flash a stock bloated unrooted ROM via odin (lemme know if you need a link to one)
2.boot into droid recovery and do a factory reset, and wipe the cache partition also.
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
I haven't re-rooted yet but I'll be trying the official cm10 now that it's up.
MDMoore313 said:
I got the same error msg after flashing a nightly of d2hacker's unofficial cm10, after I had flashed a few nightly's before of the same ROM w/ no problems. I had to
1. Flash a stock bloated unrooted ROM via odin (lemme know if you need a link to one)
2.boot into droid recovery and do a factory reset, and wipe the cache partition also.
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
I haven't re-rooted yet but I'll be trying the official cm10 now that it's up.
Click to expand...
Click to collapse
Refer to my last post
droidstyle said:
Refer to my last post
Click to expand...
Click to collapse
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
Incorrect. It actually means the opposite. The only way to tell if your bootloader is unlocked is to flash a custom rom/kernel and boot up. Please people, do some reading before you turn your phone into a paperweight. That unlocked lock/custom means you're running or were running custom software and it's been detected as such. One possible culprit is your "custom" recovery. If your bootloader is unlocked, you will not have that problem.
MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
refer to post #3 and read this link
http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13
Zalithian said:
Incorrect. It actually means the opposite. The only way to tell if your bootloader is unlocked is to flash a custom rom/kernel and boot up. Please people, do some reading before you turn your phone into a paperweight. That unlocked lock/custom means you're running or were running custom software and it's been detected as such. One possible culprit is your "custom" recovery. If your bootloader is unlocked, you will not have that problem.
Click to expand...
Click to collapse
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
MDMoore313 said:
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Click to expand...
Click to collapse
I think it has to do with the "degree" of customization. IE a custom ROM or Kernel will get you the verizon screen of death for sure if you're not unlocked. The custom/unlock icon seems more for minor things like a custom recovery, possibly different firmware or tweaking specific settings.
Zalithian said:
I think it has to do with the "degree" of customization. IE a custom ROM or Kernel will get you the verizon screen of death for sure if you're not unlocked. The custom/unlock icon seems more for minor things like a custom recovery, possibly different firmware or tweaking specific settings.
Click to expand...
Click to collapse
That makes more sense, as the nightlys progress and more modifications are being made, overnight the "switch is flipped" so to speak, and if you're not running a custom rom,
MDMoore313 said:
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
Click to expand...
Click to collapse
Could he Odin back to stock through download mode though? Or will the locked bootloader block download mode and recovery mode too when it detects tampering?
MDMoore313 said:
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Click to expand...
Click to collapse
The secure aboot.img only checks 3 of the 5 system images on boot. Since we can flash a custom recovery to the recovery partition, the secure aboot img lets it ride, but knows it there....hence why you see the custom lock screen, but device still boots. Kexec allowed the bootloader aka secure aboot.img to see the stock kernel(boot.img) and pass signature checks, then side loads the custom kernel. Thats why there was 3 reboots...now that the bootloader is unlocked, we ditch kexec because unsecure aboot is unlocked and not checking signatures.
However, if you flash a kernel thats non kexec and the bootloader is locked, you will get the verizon screen of death since the secure aboot.img is checking signatures. So never lock the bootloader unless your on stock rom/kernel or using kexec.
Deleted
Jesus. All of these people who don't read up on things before they flash something astounds me.
Lol, the exact same thing happen to me as Op, I was unlock (ezrecovery app) and rooted(casual-revision131) but when I flash unofficial CM10 KANG I was lock out by Verizon message.Thanks to DroidStyle awesome GUIDE i just Odin back to stock along with kernel.Thank you to all the cool people here at xda who help and evolve Android:thumbup:
Ezrecovery app must not have work properly even tho it said unlock, so I use Adam casual R131 flash Unsecure Aboot too.
Sent from my SCH-I535 using xda premium
EvoSideHustlAZ said:
Lol, the exact same thing happen to me as Op, I was unlock (ezrecovery app) and rooted(casual-revision131) but when I flash unofficial CM10 KANG I was lock out by Verizon message.Thanks to DroidStyle awesome GUIDE i just Odin back to stock along with kernel.Thank you to all the cool people here at xda who help and evolve Android:thumbup:
Ezrecovery app must not have work properly even tho it said unlock, so I use Adam casual R131 flash Unsecure Aboot too.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
ezrecovery to unlock? What?
MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
No, that just means that it normally has detected some changed files. If you WERE unlocked you would never see that icon.
TAPPED in on my (now unlocked bootloader) Verizon S3
strung said:
Could he Odin back to stock through download mode though? Or will the locked bootloader block download mode and recovery mode too when it detects tampering?
Click to expand...
Click to collapse
Well, step 1 is going Odin back to stock, but if a cache wipe and factory reset aren't done (like in Droidstyle's guide), then it will never completely boot, at least that's what I experienced after my phone sat at that screen for 10+ minutes. It doesn't run the user setup again.
Got the yellow triangle with " unauthorized software found on your device. Return to authorized Verizon dealer." I was trying to return this to stock and the directions on Odin said the bootloader had to be locked. I took the EZunlock and locked it back then all hell broke loose. Any ideas?
ergon said:
Got the yellow triangle with " unauthorized software found on your device. Return to authorized Verizon dealer." I was trying to return this to stock and the directions on Odin said the bootloader had to be locked. I took the EZunlock and locked it back then all hell broke loose. Any ideas?
Click to expand...
Click to collapse
where did u read the bootloader had to be locked? all u need to do is odin back to stock, root, unlock bootloader.
All you need to do is download Odin, and and whatever tar file you want, boot phone into download (volume down, home, power), select yes when it asks are you sure, open Odin, select the tar file and start. Easy schmeasy
Sent from my SCH-I535 using xda app-developers app
ergon said:
Got the yellow triangle with " unauthorized software found on your device. Return to authorized Verizon dealer." I was trying to return this to stock and the directions on Odin said the bootloader had to be locked. I took the EZunlock and locked it back then all hell broke loose. Any ideas?
Click to expand...
Click to collapse
You rebooted your phone after locking the bootloader. You shouldn't have done that. Your issue isn't unfixable tho, not by any means. IIRC VRALF2 I'm pretty sure is the only stock image that doesn't re-lock the bootloader(I haven't tested all of them). If you choose VRALG1 that will re-lock the bootloader for you when you flash it, it did for me the other day when I started over.
Just boot into download mode and flash the G1 thru Odin then do a factory wipe and you should be fine. I'm 99% sure you didn't trip the flash counter doing this, someone else chime in on this please?
And make sure you use PDA mode when you use Odin and don't unplug your phone from it until it says finished(even if it says removed, let it continue rebooting and doing its thing before unplugging. The Start and Cancel buttons should 'come back to life' when it's ok)
This might be the source the OP was referring to:
http://forum.xda-developers.com/showthread.php?t=1867253&highlight=odin+to+stock
Although it clearly says to NOT reboot after re-locking your bootloader, it does say that the first step is to lock it before flashing to stock via Odin. Further down in the thread he says he'll remove it from the guide, but I don't think flashing stock via Odin locks the BL so if youre trying to return it to Verizon I would lock it first.
nghtrain88 said:
This might be the source the OP was referring to:
http://forum.xda-developers.com/showthread.php?t=1867253&highlight=odin+to+stock
Although it clearly says to NOT reboot after re-locking your bootloader, it does say that the first step is to lock it before flashing to stock via Odin. Further down in the thread he says he'll remove it from the guide, but I don't think flashing stock via Odin locks the BL so if youre trying to return it to Verizon I would lock it first.
Click to expand...
Click to collapse
Certain stock images do. I've had g1 lock and I've read that he will to.
Don't get me wrong, locking it yourself prior to flashing thru Odin is a good thing to do just to make sure. It's easier than having to re-root just to lock it then flash all over again.
Brian Gove said:
Certain stock images do. I've had g1 lock and I've read that he will to.
Don't get me wrong, locking it yourself prior to flashing thru Odin is a good thing to do just to make sure. It's easier than having to re-root just to lock it then flash all over again.
Click to expand...
Click to collapse
the only stock rom i have found that locks the bootloader is vralhd... are you sure g1 locked your bootloader because i thought we had this conversation already lol? unless your returning the device, why would you even want to lock it back up?
droidstyle said:
the only stock rom i have found that locks the bootloader is vralhd... are you sure g1 locked your bootloader because i thought we had this conversation already lol? unless your returning the device, why would you even want to lock it back up?
Click to expand...
Click to collapse
Yeah, I meant HD, not HE.
We did, but that was when I flashed F2. F2 doesn't lock it, but a week or so ago I had to flash back to stock to start over, used G1 and it re-locked my bootloader on me.
One of these days when I'm bored I'll sit down and try them all just to double check too.
cvbcbcmv said:
Don't over think it. This is simply happening because the bootloader is locked and your trying to run a custom rom. Just restore to stock and you're fine.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I am having the same issue but when I go to restore back to stock Odin says it has completed 100% but when the phone reboots I get the triangle again. Please help.
i get this very same problem with with yellow triangle when i try to flash a rom it happend to me 2 times so i had to odin back any ideas why it happens when i try to flash a rom
Bootloader is locked
Sent from my SCH-I535 using xda app-developers app
Verizon note 2 will not go into download just yellow triangle
Okay bye hope someone can help me I rooted my galaxy note 2 by Verizon with framaroot and didn't realize the boot loader was locked and try to download ROM manager and it locked my phone up all I got was a yellow triangle said that they did not recognize a program then I did Adam's way of returning to stock with casual will not read it so then I found the root66_vzw..... same as stock but rooted and unlock boot loader and I flashed it and the pit file that went with it using Odin. It said pass when everything was done it upload bar on the phone I seen it on the screen and when it went to reset then it come back to the same Verizon yellow triangle and now I can't get it to going to download mode or do anything at all except for when I plug in the cable to my computer the yellow triangle come on. Can someone help?? Please I really we'd love to have my phone back! I would appreciate it very much thank you sincerely
worknman69 said:
Okay bye hope someone can help me I rooted my galaxy note 2 by Verizon with framaroot and didn't realize the boot loader was locked and try to download ROM manager and it locked my phone up all I got was a yellow triangle said that they did not recognize a program then I did Adam's way of returning to stock with casual will not read it so then I found the root66_vzw..... same as stock but rooted and unlock boot loader and I flashed it and the pit file that went with it using Odin. It said pass when everything was done it upload bar on the phone I seen it on the screen and when it went to reset then it come back to the same Verizon yellow triangle and now I can't get it to going to download mode or do anything at all except for when I plug in the cable to my computer the yellow triangle come on. Can someone help?? Please I really we'd love to have my phone back! I would appreciate it very much thank you sincerely
Click to expand...
Click to collapse
We don't have a Note 2 go to the Note 2 forums to get help.
I went to make a backup and ROM Manager said there was a new version of Recovery (ended in .8). I accepted and selected the Touch version. When I then tried to make a backup, the phone rebooted and I got this massage:
System software not authorized by Verizon Wireless has been found on your phone.
Please turn off your phone and go to the nearest Verizon Wireless store for help
Volume up/home/power just boots to this message every time. So does Volume down/home/power. There is no way to restore a backup or use the phone in any way. I have been doing this since the days of the OG Droid, but I am lost now. Please help.
sounds like you didnt unlock your booloader
Yes it does, but it has been unlocked for a long time, and I don't think I lost the unlock with tthe 4.1.2 update. How can I unlock the bootloader without being able to start the phone?
melucci said:
Yes it does, but it has been unlocked for a long time, and I don't think I lost the unlock with tthe 4.1.2 update. How can I unlock the bootloader without being able to start the phone?
Click to expand...
Click to collapse
Prostrate yourself to Odin.
Sent from my SCH-I535 using Tapatalk 2
melucci said:
Yes it does, but it has been unlocked for a long time, and I don't think I lost the unlock with tthe 4.1.2 update.
Click to expand...
Click to collapse
OTA's ALWAYS re-lock the bootloader and remove root.
Sent from my SCH-I535 using xda app-developers app
melucci said:
Yes it does, but it has been unlocked for a long time, and I don't think I lost the unlock with tthe 4.1.2 update. How can I unlock the bootloader without being able to start the phone?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1974114
See download #4 and step 1 on how to use odin.
melucci said:
Volume up/home/power just boots to this message every time. So does Volume down/home/power. There is no way to restore a backup or use the phone in any way. I have been doing this since the days of the OG Droid, but I am lost now. Please help.
Click to expand...
Click to collapse
Are you sure? Make sure you hold down Volume Down + Home for a few seconds before also hitting the Power button. I saw that same message yesterday when going back to stock and I was still able to boot into recovery/download mode. Also make sure your device is completely powered down (and not plugged in/charging)
deleted
THAT DID IT! I held volume down/home for a few seconds and then held power. The phone booted to a mode I had not seen before (recovery/download as you said?) and I said cancel and the phone booted!
I ran EZ-Unlock to unlock the boot loader. I tried several apps that require superuser permissions and they were granted it and run fine. So I assume I am still rooted, right?
Thanks so much for your help.
sounds like you should be good to go. one thing you should should consider doing is backing your IMEI if you havent already.
http://forum.xda-developers.com/showthread.php?t=1852255
bricked
melucci said:
THAT DID IT! I held volume down/home for a few seconds and then held power. The phone booted to a mode I had not seen before (recovery/download as you said?) and I said cancel and the phone booted!
I ran EZ-Unlock to unlock the boot loader. I tried several apps that require superuser permissions and they were granted it and run fine. So I assume I am still rooted, right?
Thanks so much for your help.
Click to expand...
Click to collapse
I done the same thing and it continues to go back to that same screen and will not restart.
PLEASE HELP!
kustom1955 said:
I done the same thing and it continues to go back to that same screen and will not restart.
PLEASE HELP!
Click to expand...
Click to collapse
Odin flash a stock image then re-root and unlock your bootloader if you so desire.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Odin flash a stock image then re-root and unlock your bootloader if you so desire.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
My computer will not recognize my phone has been plugged in. I have deleted all the drivers and then reinstalled them anf can get my phone in odin mode but the computer still will not recognize my device.
Thanks for your help
kustom1955 said:
My computer will not recognize my phone has been plugged in. I have deleted all the drivers and then reinstalled them anf can get my phone in odin mode but the computer still will not recognize my device.
Thanks for your help
Click to expand...
Click to collapse
First, some background info is needed.
1) What did you do to your phone?
2) You have no success booting into Download mode?
3) Did you flash something in recovery? If so, what is the file name of the file you flashed?
Edit: Disregard #2, apparently I can't read. Are you using the Samsung OEM cable? Have you tried using a different USB port? Different computer?
SlimSnoopOS said:
First, some background info is needed.
1) What did you do to your phone?
2) You have no success booting into Download mode?
3) Did you flash something in recovery? If so, what is the file name of the file you flashed?
Edit: Disregard #2, apparently I can't read. Are you using the Samsung OEM cable? Have you tried using a different USB port? Different computer?
Click to expand...
Click to collapse
I just noticed the person you helped before me had a galaxy s3 and mine is a note 2 I605.
I opened the ROM manager app and it said something about allowing other devices to text from your same #.
I really hope this helps to figure this out. I'm going to try a different computer now.
kustom1955 said:
I just noticed the person you helped before me had a galaxy s3 and mine is a note 2 I605.
I opened the ROM manager app and it said something about allowing other devices to text from your same #.
I really hope this helps to figure this out. I'm going to try a different computer now.
Click to expand...
Click to collapse
You...have a Note 2? Why are you commenting in the Verizon GSIII forum bud? You have to try either your respective Note 2 carrier forum (i605 = Verizon Note 2 right?) or the international Note 2 forums. No one here can help you. Create a new thread in the Q/A section of the proper phone forum you need and you will receive relevant help.
SlimSnoopOS said:
You...have a Note 2? Why are you commenting in the Verizon GSIII forum bud? You have to try either your respective Note 2 carrier forum (i605 = Verizon Note 2 right?) or the international Note 2 forums. No one here can help you. Create a new thread in the Q/A section of the proper phone forum you need and you will receive relevant help.
Click to expand...
Click to collapse
Sorry, I didn't realize I was in the wrong area.
Thanks for your help
Verizon Warning NO MATTER WHAT
SlimSnoopOS said:
Odin flash a stock image then re-root and unlock your bootloader if you so desire.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
So far flashed HyperDrive, now AOKP, no matter what I do I get a yellow triangle and a warning.
I reflash stock
relfash VARLEC bootchain
reflash CWM
and try again.
No matter what options, settings, or ROM, I keep getting softbricked! ANY IDEAS?!>!
garvus said:
So far flashed HyperDrive, now AOKP, no matter what I do I get a yellow triangle and a warning.
I reflash stock
relfash VARLEC bootchain
reflash CWM
and try again.
No matter what options, settings, or ROM, I keep getting softbricked! ANY IDEAS?!>!
Click to expand...
Click to collapse
After flashing CWM, you need to unlock the bootloader. You should be flashing a vrale6 bootloader zip OR using EZ Unlock v1.2 to unlock.
Sent from my SCH-I535 using Tapatalk 4 Beta
boot loader
if during start up and i see the word SAMSUNG WITH A LOCK THAT APPEARS UNLOCKED does that mean i have an unlocked bootloader?
puchodog1977 said:
if during start up and i see the word SAMSUNG WITH A LOCK THAT APPEARS UNLOCKED does that mean i have an unlocked bootloader?
Click to expand...
Click to collapse
That means your Bootloader is not Unlocked. Make sure you use ez unlock 1.2 when unlocking. You can verify it's unlocked when you turn on the phone, and you see the word Samsung flash for a split second.
Sent from my SCH-I535 using Tapatalk 2
Ok, i rooted and unlocked the bootloader on my S3 per the directions here... i tried a few custom roms right a way and didnt like missing out on the touchwiz widgets on asop roms, so i went back to stock rooted and it stayed like that for months...
recently i decided to try some custom roms again which need the boot loader unlocked(clean rom) which will not boot. and MIUI which destroys my sd card's format.... this didn't happen before so i know something is messed up... these roms worked fine before and have a good reputation for stability... Im also seeing something new on boot.... as the samsung logo pops on the screen below it is seen a lock in the unlocked position... when i also go to oden mode i see that it lists my phones condition as custom!!!! The only instructions ive seen listed to get the phone back to stock is to oden the stock recovery.... which i have done... but the custom status remains... what am i missing? how can i get this thing to format competely back to factory so i can do a fresh unlock/root?
You need to use Triangle Away app to reset your flash counter
Thanks doesn't hurt....
ramdesai said:
You need to use Triangle Away app to reset your flash counter
Thanks doesn't hurt....
Click to expand...
Click to collapse
ok, how does the flash counter keep me from flashing custom roms properly? and is this unlocked lock saying my bootloader is still unlocked? i attached a pic of it at boot up...
i wasnt going to bother with the flash counter as i have no plans of sending this back to samsung, i just want to make sure the bootloader and OS are factory so i can re-root and unlock fresh....
If you have unlocked bootloader, then the samsung splash screen will quickly disappear else it takes some time. If u went to stock then re run procedure for the root. If you have root, you may use EZ-Unlock app to unlock bootloader.
Thanks doesn't hurt....
teddyv said:
Ok, i rooted and unlocked the bootloader on my S3 per the directions here... i tried a few custom roms right a way and didnt like missing out on the touchwiz widgets on asop roms, so i went back to stock rooted and it stayed like that for months...
recently i decided to try some custom roms again which need the boot loader unlocked(clean rom) which will not boot. and MIUI which destroys my sd card's format.... this didn't happen before so i know something is messed up... these roms worked fine before and have a good reputation for stability... Im also seeing something new on boot.... as the samsung logo pops on the screen below it is seen a lock in the unlocked position... when i also go to oden mode i see that it lists my phones condition as custom!!!! The only instructions ive seen listed to get the phone back to stock is to oden the stock recovery.... which i have done... but the custom status remains... what am i missing? how can i get this thing to format competely back to factory so i can do a fresh unlock/root?
Click to expand...
Click to collapse
Follow the instructions in this thread. It will get you back to factory stock.
http://forum.xda-developers.com/showthread.php?t=1867253
tscalia2 said:
Follow the instructions in this thread. It will get you back to factory stock.
http://forum.xda-developers.com/showthread.php?t=1867253
Click to expand...
Click to collapse
teddyv, I recently followed the instructions posted in tbe above thread that tscalia posted for you and they worked great!! After I got back to stock, I rerooted and put on twrp recovery... then I made sure to do a nandroid backup before I flashed any new roms.... that makes it easier to revert back next time
When Odin back to stock will it lock the bootloader? Specifically from a unlocked firmware and then Odin to 4.3 image.
Sent from my SCH-I535 using xda premium
jl2222 said:
When Odin back to stock will it lock the bootloader? Specifically from a unlocked firmware and then Odin to 4.3 image.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I should imagine that if you Odin using an OTA or stock tar from your provider then yes, you will lock your bootloader. AFAIK (which, mind you could be in error) the bootloader in the 4.3 OTA locks and deploys KNOX.
To save root I would ODIN stock root ROM or the like from XDA. Better yet install a custom recovery and then install rooted stock.
HTH
skeeterpro said:
I should imagine that if you Odin using an OTA or stock tar from your provider then yes, you will lock your bootloader. AFAIK (which, mind you could be in error) the bootloader in the 4.3 OTA locks and deploys KNOX.
To save root I would ODIN stock root ROM or the like from XDA. Better yet install a custom recovery and then install rooted stock.
HTH
Click to expand...
Click to collapse
Ok thanks. Yeah it may sound weird but my goal is to get one of my phones completely back to stock. Stock recovery, Knox, Bootloader locked etc. I believe I have achieved my overall goal but cannot tell if I have a lock or unlocked bootloader still. When I first started my phone after Odin it showed a splash screen that said custom with an unlock symbol which threw me off. After booting the phone the custom lock splash screen during boot up went away. Kinda weird.
jl2222 said:
Ok thanks. Yeah it may sound weird but my goal is to get one of my phones completely back to stock. Stock recovery, Knox, Bootloader locked etc. I believe I have achieved my overall goal but cannot tell if I have a lock or unlocked bootloader still. When I first started my phone after Odin it showed a splash screen that said custom with an unlock symbol which threw me off. After booting the phone the custom lock splash screen during boot up went away. Kinda weird.
Click to expand...
Click to collapse
Yeah. That is odd. Which is why we all take chances of borking our devices when we flash. Crazy stuff can happen. The Custom reference and unlock to me implies you still have a custom recovery and unlocked BL. Either way with the KNOX trip your phone is out of warranty. But then perhaps the person at VZW won't check.
Something I've started to do (suggestion from prdog1) is when I flash I wipe System along with Dalvik and Data. Clears out any "leftovers" from previous flashes it seems.
Just a thought.
skeeterpro said:
Yeah. That is odd. Which is why we all take chances of borking our devices when we flash. Crazy stuff can happen. The Custom reference and unlock to me implies you still have a custom recovery and unlocked BL. Either way with the KNOX trip your phone is out of warranty. But then perhaps the person at VZW won't check.
Something I've started to do (suggestion from prdog1) is when I flash I wipe System along with Dalvik and Data. Clears out any "leftovers" from previous flashes it seems.
Just a thought.
Click to expand...
Click to collapse
Yea I was unaware of KNOX until after I Odin to 4.3. So a little worried I tripped it in the process. Also I never Triangled Away before either. Im wondering if I should saferoot her then use triangle away and then Odin one more time.
Yea I also like to wipe system sometimes too. I've noticed most every Rom will wipe system during installation anyways tho.
jl2222 said:
Yea I was unaware of KNOX until after I Odin to 4.3. So a little worried I tripped it in the process. Also I never Triangled Away before either. Im wondering if I should saferoot her then use triangle away and then Odin one more time.
Yea I also like to wipe system sometimes too. I've noticed most every Rom will wipe system during installation anyways tho.
Click to expand...
Click to collapse
Well, IMHO it's immaterial resetting with Triangle Away. Since KNOX is tripped and cannot be reversed any VZW employee who happens to looks and discovers the KNOX trip can reject the phone (AFAIK).
skeeterpro said:
Well, IMHO it's immaterial resetting with Triangle Away. Since KNOX is tripped and cannot be reversed any VZW employee who happens to looks and discovers the KNOX trip can reject the phone (AFAIK).
Click to expand...
Click to collapse
Well cross my fingers it passes and they don't check it. Thank for the help.
jl2222 said:
Well cross my fingers it passes and they don't check it. Thank for the help.
Click to expand...
Click to collapse
You're welcome. Good luck