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.
I was laying in bed (with food poisoning) trying to get some sleep, when I noticed my phone vibrated and randomly rebooted.
After it booted up to the Andy firmware update image, and finally to the home screen with the update message I knew I was screwed.
THIS WAS A FORCED UPDATE BY VERIZON. I NEVER ACCEPTED OR DECLINED ANYTHING (re: food poisoning)!
You WILL lose root, on device app searching (Apple legal bs), and probably your unlock!
The perfect end to a perfect night! THANKS Verizon! /sarcasm
mcduck$ said:
I was laying in bed (with food poisoning) trying to get some sleep, when I noticed my phone vibrated and randomly rebooted.
After it booted up to the Andy firmware update image, and finally to the home screen with the update message I knew I was screwed.
THIS WAS A FORCED UPDATE BY VERIZON. I NEVER ACCEPTED OR DECLINED ANYTHING (re: food poisoning)!
You WILL lose root, on device app searching (Apple legal bs), and probably your unlock!
The perfect end to a perfect night! THANKS Verizon! /sarcasm
Click to expand...
Click to collapse
What ROM were you running? It should have disable OTA's thats why I ask.
Brian Gove said:
What ROM were you running? It should have disable OTA's thats why I ask.
Click to expand...
Click to collapse
The title says rooted stock.
I was runing the stock touchwiz rom (with the VRGL2 or 1 baseband) rooted, stock recovery, and the bootloader unlocked.
I just checked the EZ unlocker app and it claims that the bootloader is still unlocked. I have no way of verifying this, but if true, I'm only half screwed until somebody finds a root method for the new firmware.
If/when that happens I'll be more than happy to flash away from Verizon's bs nonsense.
Grrr...
mcduck$ said:
I was runing the stock touchwiz rom (with the VRGL2 or 1 baseband) rooted, stock recovery, and the bootloader unlocked.
I just checked the EZ unlocker app and it claims that the bootloader is still unlocked. I have no way of verifying this, but if true, I'm only half screwed until somebody finds a root method for the new firmware.
If/when that happens I'll be more than happy to flash away from Verizon's bs nonsense.
Grrr...
Click to expand...
Click to collapse
Did you try re-rooting using current methods?
mcduck$ said:
I was runing the stock touchwiz rom (with the VRGL2 or 1 baseband) rooted, stock recovery, and the bootloader unlocked.
I just checked the EZ unlocker app and it claims that the bootloader is still unlocked. I have no way of verifying this, but if true, I'm only half screwed until somebody finds a root method for the new firmware.
If/when that happens I'll be more than happy to flash away from Verizon's bs nonsense.
Grrr...
Click to expand...
Click to collapse
Wow rooted stock with stock recovery. Why not custom recovery? That probably the reason the update went through. Still ridiculous though, don't get me wrong. I'm guessing you weren't doing a lot of flashing.
Sent from my Nexus 7 using Tapatalk 2
Zalithian said:
Did you try re-rooting using current methods?
Click to expand...
Click to collapse
Negative. I currently feel like crap (see OP) and don't feel like messing with my Windows laptop to try it.
Do you think there's any chance I could brick my phone when I attempt it? Or is it simply a will work/won't work thing?
mcduck$ said:
Negative. I currently feel like crap (see OP) and don't feel like messing with my Windows laptop to try it.
Do you think there's any chance I could brick my phone when I attempt it? Or is it simply a will work/won't work thing?
Click to expand...
Click to collapse
Pretty sure it will just work or fail, but I'd wait for confirmation from someone else first - better safe than sorry.
Can you supply your new Baseband Version number?
I just froze sdm 1.0. I went to the software update and it crashed. I so let's hope that stops the update...
Sent from Land Line using pay phone
epikos said:
Can you supply your new Baseband Version number?
Click to expand...
Click to collapse
I535VRLG7
epikos said:
Can you supply your new Baseband Version number?
Click to expand...
Click to collapse
marcucci217 said:
Wow rooted stock with stock recovery. Why not custom recovery? That probably the reason the update went through. Still ridiculous though, don't get me wrong. I'm guessing you weren't doing a lot of flashing.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I was going to play around with flashing different roms eventually, but after upgrading from a decrepit half working ICS flashed Droid X I was just happy to have fully working phone again. Unfortunately I was under the false impression that the jerks at Verizon would have given me the option to accept their so-called upgrade.
Didn't they already remove local search on Verizon? My phone came that way. Of course I didn't stay on stock once we were freed...
rooting with the rootdebugfs tool should still work!
I woke up to a failed update message. Ran the update again to see why it failed and it fails because it reboots into custom recovery. Rooted, unlocked, stock. Just have some apps disabled or frozen.
Can anyone point out where the in the directory the downloaded update zip would go to?
I didn't get an update message but I did check for one it was available for me. So I ticked ok and it downloaded but failed to update as expected because of the custom recovery I have in place.
But I can't find where the zip file download to.
I wanted to try and see if Chainfire's Mobile ODIN Pro would root the updated zip as it claims.
Cache>fota>update zip...you'll see it
sent from my freed beast...&ikiller
Yes my laziness allowed verizon to update both of my SGS3 to I535VRLG7. I hope I can reroot when I get a chance later.
I was running stock root on both devices.
Sent from my SCH-I535 using xda premium
Successful OTA Flash using Mobile Odin Pro and Kept Root/Unlocked Status
Hulk0069 said:
Cache>fota>update zip...you'll see it
sent from my freed beast...&ikiller
Click to expand...
Click to collapse
Thanks, running a backup now before I try Mobile ODIN Pro. Will update this post:
Edit: Ok, it seems I have a successful flash using Mobile ODIN Pro.
Mobile Odin Pro gave me some Warnings in advance before continuing the Flash.
1) EverRoot may need to remove Google Maps during the flash to free up some space... yadda yadda..
2) The Modem Image on your device does not match the signature check....yadda yadda..
3) 5 out of 499 system files do not match the signature checks in the OTA zip... yadda yadda..
NOTE: I disabled signature checks on both warnings before proceeding.
But you do that AT YOUR OWN RISK!!
From what I gather, Mobile Odin made its own OTA zip from the target file before flashing it
I"ve uploaded some screen shots.
IMPORTANT!
PLEASE RUN A BACK UP before attempting anything risky like this.
ALSO! and VERY IMPORTANT!!
If you are using CWM as your recovery PLEASE PLEASE PLEASE check the size of your backup before proceeding with the update.
It seems CWM is not working properly on my SGSIII because the backup file sizes were only about 22 MB's large.. and thats is SO NOT GOOD!!
I went into GooManager and Flashed TWRP over CWM and ran a backup via TWRP and checked the file size to be in the range of 2.34GB's and thats what it should be (IMO). The only thing that bugs me about both recoveries is the date is 1979-12-31.. and thats definately wrong..
Anyways, my way of checking for root after an OTA is to run Titanium Backup because it always asks for SuperUser Rights before loading.
So all is well with that and checking to see if the Bootloader on my device was still Unlocked with EZ-Unlock said it still was..
Thats all I can think for now..
Hulk0069 said:
Cache>fota>update zip...you'll see it
sent from my freed beast...&ikiller
Click to expand...
Click to collapse
Stock rooted & it tried & failed 2x to do the update and there is nothing in /fota/
I still have root
Second attempt it booted into recovery & I just restarted as it had a fail error
So, my phone is running 4.1.2 rooted, and it got an OTA recently. The OTA failed because the bootloader was unlocked.
I thought easy-peasy, just odin flash the locked boot loader and download/apply OTA again, right?
Flashed fine, locked and clean for initial boot. But when it went to install the OTA, same problem happened, the bootloader was miraculously unlocked again, and the OTA failed.
Any ideas on how I can get past this? I really don't mind loosing root, just trying to avoid a complete odin reflash and loosing everything...
I am just curious ... why would you want to update to the OTA 4.3 and forever lock down the bootloader? Once the verizon 4.3 update takes hold, you might be able to root, but (so far) will not be able to load custom roms without bricking the device.
vax1170 said:
I am just curious ... why would you want to update to the OTA 4.3 and forever lock down the bootloader? Once the verizon 4.3 update takes hold, you might be able to root, but (so far) will not be able to load custom roms without bricking the device.
Click to expand...
Click to collapse
Well your almost right. First off you for sure can root. Second you can install custom roms with safestrap. Its limited to tw roms atm. There have been a hand full of people who upgraded just to use safestrap. I wouldnt recomend it right now because its alittle buggy.
RedBullet said:
So, my phone is running 4.1.2 rooted, and it got an OTA recently. The OTA failed because the bootloader was unlocked.
I thought easy-peasy, just odin flash the locked boot loader and download/apply OTA again, right?
Flashed fine, locked and clean for initial boot. But when it went to install the OTA, same problem happened, the bootloader was miraculously unlocked again, and the OTA failed.
Any ideas on how I can get past this? I really don't mind loosing root, just trying to avoid a complete odin reflash and loosing everything...
Click to expand...
Click to collapse
Wife's phone. She doesn't want to mess with it.
I think I figured it out, looks like I had a custom recovery installed. Flashed that to stock and locked bootloader and all is fine now. Running latest and greatest. Just what the missus is looking for...
RedBullet - Ah, I fully understand now I'm having a similar conversation with my misses.
ThePagel - Thanks. One one of my phones was cursed with an accidental OTA 4.3 upgrade. Nice to know something is in the works, I'll dig up that thread and watch it.
vax1170 said:
RedBullet - Ah, I fully understand now I'm having a similar conversation with my misses.
Click to expand...
Click to collapse
I assume if one wants to go the custom ROM route they would simply need to odin flash one of the older stock images and go from there. Doesn't seem like a big problem. Of course > 50% chance I have no idea what I'm talking about...
RedBullet said:
I assume if one wants to go the custom ROM route they would simply need to odin flash one of the older stock images and go from there. Doesn't seem like a big problem. Of course > 50% chance I have no idea what I'm talking about...
Click to expand...
Click to collapse
If you take the 4.3 OTA, you cannot odin flash an older stock image. Will brick your device.
landshark68 said:
If you take the 4.3 OTA, you cannot odin flash an older stock image. Will brick your device.
Click to expand...
Click to collapse
Really? That is pretty tragic. I may only buy unlocked devices from here on out; they seem to be getting better and better at making their devices less and less useful...
It sure is sad but true. Im thankful google blessed us with the nexus 5
RedBullet said:
Really? That is pretty tragic. I may only buy unlocked devices from here on out; they seem to be getting better and better at making their devices less and less useful...
Click to expand...
Click to collapse
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
I have gone thru the thread on how to go back to stock however i still have some questions, my s3 had a broken screen for quiet sometime so i am not sure where to start on getting it back to stock or whatever to get me back on the latest firmware. It is rooted on 4.1.2 but i dont know how to check if bootloader was unlocked or not.
If i can just flash a file to get me the latest i can do that as well. It does have TWRP for recovery
aford89 said:
I have gone thru the thread on how to go back to stock however i still have some questions, my s3 had a broken screen for quiet sometime so i am not sure where to start on getting it back to stock or whatever to get me back on the latest firmware. It is rooted on 4.1.2 but i dont know how to check if bootloader was unlocked or not.
If i can just flash a file to get me the latest i can do that as well. It does have TWRP for recovery
Click to expand...
Click to collapse
Its not unlocked by default but the last version of Android you were able to unlock it was on 4.1.2. You can unlock it with casual or ez unlock. If you however unroot it and take the OTA up to 4.4.2 your bootloader will be permanently locked and you will not be able to revert it back
Sent from my Nexus 5
ShapesBlue said:
Its not unlocked by default but the last version of Android you were able to unlock it was on 4.1.2. You can unlock it with casual or ez unlock. If you however unroot it and take the OTA up to 4.4.2 your bootloader will be permanently locked and you will not be able to revert it back
Sent from my Nexus 5
Click to expand...
Click to collapse
I am aware of that, i need to get it back to stock and to the latest version 4.4.x im just not sure how to go about it so i dont brick it. I have odin just looking for the correct stock files to get me the rest of the way and how to use them in what order
Can i just odin straight to 4.4.2? if i am rooted and unlocked on 4.1.2?
aford89 said:
Can i just odin straight to 4.4.2? if i am rooted and unlocked on 4.1.2?
Click to expand...
Click to collapse
You have to unroot first. Once your unrooted you can take the OTA. Just warning you about the bootloader being locked once you take the OTA. As far as straight to 4.4.2 I'm not sure. Never took an OTA on my S3. Start with unrooting first and see where it goes
Sent from my Nexus 5
ShapesBlue said:
You have to unroot first. Once your unrooted you can take the OTA. Just warning you about the bootloader being locked once you take the OTA. As far as straight to 4.4.2 I'm not sure. Never took an OTA on my S3. Start with unrooting first and see where it goes
Sent from my Nexus 5
Click to expand...
Click to collapse
how do i go about unrooting? like i said this phone sat for a LONG time im pretty sure i did it from outlawers method when i first got it
Thanks in advance
aford89 said:
how do i go about unrooting? like i said this phone sat for a LONG time im pretty sure i did it from outlawers method when i first got it
Thanks in advance
Click to expand...
Click to collapse
What SU app do you have on it?
Sent from my Nexus 5
ShapesBlue said:
What SU app do you have on it?
Sent from my Nexus 5
Click to expand...
Click to collapse
the one that looked like a superman shield, i went thru settings and found unroot however its not prompting me for an OTA and when i check it says its up to date. If i just odin the same version thats on there that should be fine right? then it'll start prompting for OTA's?
aford89 said:
the one that looked like a superman shield, i went thru settings and found unroot however its not prompting me for an OTA and when i check it says its up to date. If i just odin the same version thats on there that should be fine right? then it'll start prompting for OTA's?
Click to expand...
Click to collapse
Did you freeze any system apps? That is supersu your speaking of. I'm not completely sure if you can just odin to the newest firmware or not
Sent from my Nexus 5
ShapesBlue said:
Did you freeze any system apps? That is supersu your speaking of. I'm not completely sure if you can just odin to the newest firmware or not
Sent from my Nexus 5
Click to expand...
Click to collapse
No system apps are frozen, i did a factory wipe on it just thru TWRP and its still saying nothing is available
aford89 said:
No system apps are frozen, i did a factory wipe on it just thru TWRP and its still saying nothing is available
Click to expand...
Click to collapse
Then I would say try to Odin back to stock. It should work but don't quote me on that
Sent from my Nexus 5
ShapesBlue said:
Then I would say try to Odin back to stock. It should work but don't quote me on that
Sent from my Nexus 5
Click to expand...
Click to collapse
Yeah took the dive and used Odin from 4.1.2 all the way to 4.4.2 and everything worked out fine, was slow to boot and gave me an error but factory recovery wipe fixed that
Thanks for all the replies trying to help