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.
Related
Still pretty new to this stuff so I have a couple questions,
I am conflicted on whether I still have to "unlock bootloader" or not. Some threads I read seem like it has been unlocked now and isn't a manual thing. Is this true?
What is the purpose of backing up IMEI?
Are the results any different if I load CWM via ODIN, EZ Recovery, etc? Is one better then the other as far a funtion not ease of method?
Once I'm rooted and have a custom recovery (CWM) can I still connect for software updates (stock rom of course) or can Verzion tell I've made changes?
gfausey211 said:
Still pretty new to this stuff so I have a couple questions,
I am conflicted on whether I still have to "unlock bootloader" or not. Some threads I read seem like it has been unlocked now and isn't a manual thing. Is this true?
What is the purpose of backing up IMEI?
Are the results any different if I load CWM via ODIN, EZ Recovery, etc? Is one better then the other as far a funtion not ease of method?
Once I'm rooted and have a custom recovery (CWM) can I still connect for software updates (stock rom of course) or can Verzion tell I've made changes?
Click to expand...
Click to collapse
Short answers:
Yes, you have to do it manually
You back up IMEI/NV because some people have lost it by flashing custom roms or kernels and it is much easier and more effective to have a backup than to repair the damage without one.
There shouldn't be a difference in terms of recovery function depending on install method
You should NEVER accept updates from Verizon once rooted and there really is no need to because we devs will have the updates shortly after...or sometimes before...they are official
For a longer discussion, see this thread:
http://forum.xda-developers.com/showthread.php?p=30591784
Bleelas said:
Short answers:
Yes, you have to do it manually
You back up IMEI/NV because some people have lost it by flashing custom roms or kernels and it is much easier and more effective to have a backup than to repair the damage without one.
There shouldn't be a difference in terms of recovery function depending on install method
You should NEVER accept updates from Verizon once rooted and there really is no need to because we devs will have the updates shortly after...or sometimes before...they are official
For a longer discussion, see this thread:
http://forum.xda-developers.com/showthread.php?p=30591784
Click to expand...
Click to collapse
Thanks that is great info
for the boot loader, as far as i know, After you root, there is an app called Ez root which unlocks your verizon S3 in a second.
the_incredble said:
for the boot loader, as far as i know, After you root, there is an app called Ez root which unlocks your verizon S3 in a second.
Click to expand...
Click to collapse
Careful there turbo. The app that unlocks the bootloader is called EZ-unlock. Unlocking is different than rooting.
Sent from my SGS3 on Synergy Nightlies
the_incredble said:
for the boot loader, as far as i know, After you root, there is an app called Ez root which unlocks your verizon S3 in a second.
Click to expand...
Click to collapse
For some reason Google Play is throwing an error when I try to download EZ Unlock.
I tried to flash Synergy (lastest nightlies) but I couldn't get my wifi to connect. IT wouldn't let me toggle it on at all. Anyone have this problem?
Should I keep trying to down the nightlies as they come out or is their certain what I should go with?
gfausey211 said:
For some reason Google Play is throwing an error when I try to download EZ Unlock.
I tried to flash Synergy (lastest nightlies) but I couldn't get my wifi to connect. IT wouldn't let me toggle it on at all. Anyone have this problem?
Should I keep trying to down the nightlies as they come out or is their certain what I should go with?
Click to expand...
Click to collapse
I am running Beans build 9 and really like it everything seems to be stable for me. I also would suggest using EZ unlock to unlock your bootloader and EZ recovery to flash CWM and use that to flash roms.
KIS
gfausey211 said:
For some reason Google Play is throwing an error when I try to download EZ Unlock.
I tried to flash Synergy (lastest nightlies) but I couldn't get my wifi to connect. IT wouldn't let me toggle it on at all. Anyone have this problem?
Should I keep trying to down the nightlies as they come out or is their certain what I should go with?
Click to expand...
Click to collapse
Don't know about all these ez apps. Its probably best to do it manually so you know what you are doing. That being said you can use Adam Outlers "Casual" app that does it all. Its easy and does it all.
http://forum.xda-developers.com/showthread.php?t=1762709
---------- Post added at 05:26 PM ---------- Previous post was at 04:54 PM ----------
Well I spoke to soon I guess. EZRecovery is for flashing Recoveries. I'm coming from an OG Droid and someone eleses Droid Bionic. I don't get why we need anything other than Clock Work Mod for recovery. I never bothered with flashing kernels. Just ROMs
gfausey211 said:
For some reason Google Play is throwing an error when I try to download EZ Unlock.
I tried to flash Synergy (lastest nightlies) but I couldn't get my wifi to connect. IT wouldn't let me toggle it on at all. Anyone have this problem?
Should I keep trying to down the nightlies as they come out or is their certain what I should go with?
Click to expand...
Click to collapse
You can get around the play error by just downloading the apk over here:
http://rootzwiki.com/topic/32456-app-ez-unlock-easiest-way-to-unlock-your-bootloader/
As far as when to update to the nightlies, it's all preference. If something gets changed that you like, go ahead and flash. Otherwise if it aint broke don't fix it
Generally what I do when I'm on a nightly rom is download the rom daily or every other day, go into recovery, wipe cache & Dalvik cache and flash the rom. Once a week or every other week I'll wipe the whole phone out instead of just wiping the caches.
I need to return my phone and ive used the guide to reset my flash counter with triangle away (which was never tripped, just did it for piece of mind), then i used odin and used the stock kernel and stock image to reinstall back to stock. Everything passed but when i boot my phone up right under the samsung logo it still says custom with the unlock logo. How do i get rid of this so i can return my phone back to verizon?
EDIT***** So i re-rooted then installed ez-unlocker and locked the bootloader again. Then reinstalled stock image through odin and all is well now
shortguy088 said:
I need to return my phone and ive used the guide to reset my flash counter with triangle away (which was never tripped, just did it for piece of mind), then i used odin and used the stock kernel and stock image to reinstall back to stock. Everything passed but when i boot my phone up right under the samsung logo it still says custom with the unlock logo. How do i get rid of this so i can return my phone back to verizon?
Click to expand...
Click to collapse
Try locking your bootloader with Ez-Unlock in the play store.
fr8cture said:
Try locking your bootloader with Ez-Unlock in the play store.
Click to expand...
Click to collapse
My phones not rooted so i cant use the app.
I thought using Odin with the stock rom/kernel automatically locks the bootloader?
Sent from my SCH-I535 using xda app-developers app
Jarredw said:
I thought using Odin with the stock rom/kernel automatically locks the bootloader?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I thought so as well but when I restarted my phone it still said custom. I tried to factory wipe data after I reflashed stock and still didn't work. So I dont know what happened
Tap'n
Wish i could help but i have no idea. I guess your gonna have to try your luck.
techgov8 said:
I thought so as well but when I restarted my phone it still said custom. I tried to factory wipe data after I reflashed stock and still didn't work. So I dont know what happened
Tap'n
Click to expand...
Click to collapse
that means your bootloader is indeed locked...look around on the forums a bit! When the custom unlock screen is gone then your unlocked. I believe there is a guide in the dev section that explains this. :angel:
droidstyle said:
that means your bootloader is indeed locked...look around on the forums a bit! When the custom unlock screen is gone then your unlocked. I believe there is a guide in the dev section that explains this. :angel:
Click to expand...
Click to collapse
Well when you first boot up a brand new phone it doesn't have the custom on the samsung screen and that's locked
Tap'n
Need to get rid of custom Samsung bootloader screen
techgov8 said:
Well when you first boot up a brand new phone it doesn't have the custom on the samsung screen and that's locked
Tap'n
Click to expand...
Click to collapse
. I've tried all the guides and their bot working for me on my galaxy s4 d or s anyone know where I can find a step by step guide I'm a noon on rooting
garygnobriga said:
. I've tried all the guides and their bot working for me on my galaxy s4 d or s anyone know where I can find a step by step guide I'm a noon on rooting
Click to expand...
Click to collapse
Wait hold up if you have an s4 why are you on the S3 forums? I am assuming you have at&t , T-Mobile or Sprint go to those threads as it makes much more sense to do that.
Okay - I pulled a real stupid move today and need some help.. I'm somewhat of a flashing noob.
I installed AOKP 4.2 the other day and was having issues, so I decided to try a Synergy Rom. I use Clockword Mod Recovery to do this. When going in to flash Synergy I noticed the recovery wasn't accessing the SD like it usually does. It was giving me some error code about not being able to read external SD (I dont even have one in the phone I only use internal storage). So eventually I found the synergy file on the internal storage and flashed it. So I flashed it and was having all sorts of issues like no data, FC's etc and went back into recovery to flash my backup of the AOKP 4.2 ROM.
Here's my stupid part - I was in a rush at work this morning and wiped data / cache and got side tracked. Came back and thought I had flashed the new rom and hit restart phone in the recovery. So now I have nothing installed on the phone and the only thing I can get it to do is boot into the Download screen in Odin.
If this helps, the screen in Odin says:
Odin Mode
Product Name: SCH-I535
Custom Binary Download: Yes (2 counts)
Current Binary: Custom
System Status: Official
Qualcomm Secureboot: Enable
I have downloaded Odin to my computer and plugged it and tried to flash this .tar file and get a new recovery this way: http://forum.xda-developers.com/showthread.php?t=1695238 and had no luck as it errors out in Odin. When I connect the phone to Odin I get 0:[COM5] with a yellow colored background towards the top. I still tried to follow the above link's steps and it just errors out.
I'm at wits end and have no idea what to do now. If anyone has any idea, I would REALLY appreciate help. I have been searching for hours and haven't come up with anything that can really replicate my complete issue. I can chat via Gchat if thats easier or whatever, I just really need to get this fixed!
Thanks
Why are you trying to flash something intended for the international GSIII on your Verizon GSIII?
Had to state that cuz it is a terrible way to go about fixing your phone. Flash the rooted VRBKL3 tar in mrRobinson's thread in the Verizon GSIII dev section and then unlock your bootloader using EZ Unlock v1.2. If you didn't successfully flash anything for the i93000 then you should be fine in a few mins.
Edit: that thread you linked to even says what models it works for in the third line of the OP! lol
SlimSnoopOS said:
Why are you trying to flash something intended for the international GSIII on your Verizon GSIII?
Had to state that cuz it is a terrible way to go about fixing your phone. Flash the rooted VRBKL3 tar in mrRobinson's thread in the Verizon GSIII dev section and then unlock your bootloader using EZ Unlock v1.2. If you didn't successfully flash anything for the i93000 then you should be fine in a few mins.
Edit: that thread you linked to even says what models it works for in the third line of the OP! lol
Click to expand...
Click to collapse
Good call - god I'm an idiot....
So when you say flash the file you listed above, I assume your talking about through Odin since I cannot access recovery.
And no, nothing successfully flashed from the i9300 link.
Steve182 said:
Good call - god I'm an idiot....
So when you say flash the file you listed above, I assume your talking about through Odin since I cannot access recovery.
And no, nothing successfully flashed from the i9300 link.
Click to expand...
Click to collapse
Yes sir, flash it via Odin. There are two rooted tars per image: wipe and no wipe. It's all detailed in mrRobinson's thread. You're in an easily recoverable situation. Just make sure to unlock your bootloader using EZ Unlock v1.2 and install a custom recovery if need be.
You are a SAVIOR. Just got it to work, thank you so much.
Steve182 said:
You are a SAVIOR. Just got it to work, thank you so much.
Click to expand...
Click to collapse
My pleasure, I troll the q/a section just to help people!
Sent from my SCH-I535 using xda app-developers app
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
This is my first post ever here so I'm sorry if I'm breaking some rule (read the forum rules so I don't think I am) or if it's in the wrong subforum (although this does seem like a help & troubleshooting topic to me).
A little backstory is probably necessary.
I rooted my s3 (latest OTA update) via CASUAL (thread: http://forum.xda-developers.com/showthread.php?t=2332825) and it seemed like it worked for the most part, although it didn't boot into twrp like it should have and instead booted into normal recovery. I just assumed that it was because something went wrong with the recovery installation so I just thought "ok whatever."
Root access was there, and I assumed the bootloader was unlocked since I read several places that when it's unlocked, the initial samsung boot logo appears for about a second as opposed to several seconds when it's locked. So I just assumed all i needed was to reinstall a custom recovery and I was golden.
Installed ROM Manager, flashed CWM through the app, and rebooted the phone, and as it was booting into recovery I was greeted with the infamous "NO CUSTOM SOFTWARE ALLOWED PLEASE ALERT PAPA VERIZON IMMEDIATELY" warning.
I was about to flash back to stock through odin (which i regretted since I've had bad experiences in the past using it) when I figured out I could get the device to boot normally by clicking cancel in the download mode confirmation window. I guess it kept trying to reboot to recovery after every unsuccessful boot, which made it seem like it was softbricked to me.
Phone is operating normally now, and it should after another reboot as long as it doesn't try to go into recovery again (though I'm kind of afraid to even do that).
Is there any way without Odin I can fix my recovery and/or bootloader? I'm not sure what the problem is here and I don't think this sort of thing is a common searchable issue. Google/XDA search didn't bring up anything that sounded like someone had 100% the same problem I do.
Also on a semi-related note, does EZ-Unlock still work with this latest OTA? And if my bootloader is potentially unlocked already, would unlocking it again through EZ-Unlock break something?
Sleix said:
This is my first post ever here so I'm sorry if I'm breaking some rule (read the forum rules so I don't think I am) or if it's in the wrong subforum (although this does seem like a help & troubleshooting topic to me).
A little backstory is probably necessary.
I rooted my s3 (latest OTA update) via CASUAL (thread: http://forum.xda-developers.com/showthread.php?t=2332825) and it seemed like it worked for the most part, although it didn't boot into twrp like it should have and instead booted into normal recovery. I just assumed that it was because something went wrong with the recovery installation so I just thought "ok whatever."
Root access was there, and I assumed the bootloader was unlocked since I read several places that when it's unlocked, the initial samsung boot logo appears for about a second as opposed to several seconds when it's locked. So I just assumed all i needed was to reinstall a custom recovery and I was golden.
Installed ROM Manager, flashed CWM through the app, and rebooted the phone, and as it was booting into recovery I was greeted with the infamous "NO CUSTOM SOFTWARE ALLOWED PLEASE ALERT PAPA VERIZON IMMEDIATELY" warning.
I was about to flash back to stock through odin (which i regretted since I've had bad experiences in the past using it) when I figured out I could get the device to boot normally by clicking cancel in the download mode confirmation window, rebooting the phone normally. I guess it kept trying to reboot to recovery after every unsuccessful boot, which made it seem like it was softbricked to me.
Phone is operating normally now, and it should after another reboot as long as it doesn't try to go into recovery again (though I'm kind of afraid to even do that).
Is there any way without Odin I can fix my recovery and/or bootloader? I'm not sure what the problem is here and I don't think this sort of thing is a common searchable issue. Google/XDA search didn't bring up anything that sounded like someone had 100% the same problem I do.
Also on a semi-related note, does EZ-Unlock still work with this latest OTA? And if my bootloader is potentially unlocked already, would unlocking it again through EZ-Unlock break something?
Click to expand...
Click to collapse
That is really weird...
I was reading it and was going to suggest easy unlock v1.2,you will not break anything using that app.
If that still doesn't work, try to flash TWRP through goo manager and see if it somehow fixes your recovery issue.
It sounds to me that your Bootloader is unlocked though... But give it a shot.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
That is really weird...
I was reading it and was going to suggest easy unlock v1.2,you will not break anything using that app.
If that still doesn't work, try to flash TWRP through goo manager and see if it somehow fixes your recovery issue.
It sounds to me that your Bootloader is unlocked though... But give it a shot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick response.
That was going to be what I tried first, that's why I asked about it.
I'll wait for a little more input before trying it though if it's really that weird of an issue.
Sleix said:
Thanks for the quick response.
That was going to be what I tried first, that's why I asked about it.
I'll wait for a little more input before trying it though if it's really that weird of an issue.
Click to expand...
Click to collapse
It's just strange that you only get that message with recovery mode, it normally will not do that.
At the very worst, an odin back to stock is pretty easy. Just follow the same process, but use ez recovery instead of rom manager. It was made specifically for our phone, and never gives me any issues when installing recoveries.
I still think if you use ez unlock it'll probably fix the issue completely. Let me know if you figure it out. Good luck.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
It's just strange that you only get that message with recovery mode, it normally will not do that.
At the very worst, an odin back to stock is pretty easy. Just follow the same process, but use ez recovery instead of rom manager. It was made specifically for our phone, and never gives me any issues when installing recoveries.
I still think if you use ez unlock it'll probably fix the issue completely. Let me know if you figure it out. Good luck.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. Used ez unlock to unlock the bootloader. It was previously labeled as "Unknown".
Downloading ez recovery right now. Do you think I need to reinstall my recovery just to make sure?
Sleix said:
Thanks. Used ez unlock to unlock the bootloader. It was previously labeled as "Unknown".
Downloading ez recovery right now. Do you think I need to reinstall my recovery just to make sure?
Click to expand...
Click to collapse
No, but it wouldn't hurt.
Use 1.2 of ez unlock, versions 1.3 and 1.4 will give an unknown message. There have also been lots of reports saying that version 1.4 did not unlock their bootloader.
These are the most recent recoveries, download and flash in the ez recovery app if you need to.
http://forum.xda-developers.com/showthread.php?t=2096735
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
No, but it wouldn't hurt.
Use 1.2, versions 1.3 and 1.4 will give an unknown message. There have also been lots of reports saying that version 1.4 did not unlock their bootloader.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Reflashed CMW (I used the version provided by ez recovery, please let me know if that's a problem) just in case and it worked like a charm. Thanks!
Also I did use version 1.2. I actually had it sitting on my phone's home screen before I made this thread.
It still showed up as "Unknown". Maybe that indicated the problem?
Regardless, this problem seems to have been fixed. Now it's time to do some research on verizon s3 roms.
Also another semi-unrelated note, it seems I tripped a flash counter somewhere along the line.
Is Triangle Away one of those apps that is just "open and press a button"? I've been kind of wary of using it since it has that huge warning in app's description.
Sleix said:
Reflashed CMW (I used the version provided by ez recovery, please let me know if that's a problem) just in case and it worked like a charm. Thanks!
Also I did use version 1.2. I actually had it sitting on my phone's home screen before I made this thread.
It still showed up as "Unknown". Maybe that indicated the problem?
Regardless, this problem seems to have been fixed. Now it's time to do some research on verizon s3 roms.
Also another semi-unrelated note, it seems I tripped a flash counter somewhere along the line.
Is Triangle Away one of those apps that is just "open and press a button"? I've been kind of wary of using it since it has that huge warning in app's description.
Click to expand...
Click to collapse
Glad to hear it's working! Strange issue but looks like you ironed it out.
Triangle away is the app you would use. You tripped it using the rooting method injecting your recovery through odin, it's a big warning because it messes with your boot partition. If it fails and borks your boot partition, then you'd have to jtag your phone to fix it.
I personally wouldn't use it unless I was turning in my phone for service or replacement. But the app has great reviews and not many reports of bricks.
Before flashing anything, use a newer recovery image. The one provided by ez recovery is from last year, the newer versions are better written to prevent possible errors that come up with jellybean.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Glad to hear it's working! Strange issue but looks like you ironed it out.
Triangle away is the app you would use. You tripped it using the rooting method injecting your recovery through odin, it's a big warning because it messes with your boot partition. If it fails and borks your boot partition, then you'd have to jtag your phone to fix it.
I personally wouldn't use it unless I was turning in my phone for service or replacement. But the app has great reviews and not many reports of bricks.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'll keep that in mind, thanks again!
Any roms you'd recommend?
Sleix said:
I'll keep that in mind, thanks again!
Any roms you'd recommend?
Click to expand...
Click to collapse
Read through the op's and decide based on what you're looking for.
Mostly stock, very stable:
Clean rom, bonestock, darthstalker x1.
More modified stocks, more buggy but can run very well:
Hyperdrive, axis, goodness, moar
AOSP isn't my cup of tea, but they are fast and lag free.
Make sure you update your recovery image first, I edited my last post but think you missed it.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Read through the op's and decide based on what you're looking for.
Mostly stock, very stable:
Clean rom, bonestock, darthstalker x1.
More modified stocks, more buggy but can run very well:
Hyperdrive, axis, goodness, moar
AOSP isn't my cup of tea, but they are fast and lag free.
Make sure you update your recovery image first, I edited my last post but think you missed it.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Will do. Thanks for pointing that edit out.