Database Info

Unable to flash cwm recovery

Getting error in red text " this build is for development purposes only do not distribute outside htc with out htc write permission failure to comply my lead to legal action "
What's this? How to proceed. Any help will be appreciated.

man_is_h said:
Getting error in red text " this build is for development purposes only do not distribute outside htc with out htc write permission failure to comply my lead to legal action "
What's this? How to proceed. Any help will be appreciated.
Click to expand...
Click to collapse
If the phone otherwise works normally, that's nothing to worry about. I believe it's something that happens either when there's an internal HTC ENG HBOOT with S-OFF, or it might happen with unlocked bootloaders.

Hunt3r.j2 said:
If the phone otherwise works normally, that's nothing to worry about. I believe it's something that happens either when there's an internal HTC ENG HBOOT with S-OFF, or it might happen with unlocked bootloaders.
Click to expand...
Click to collapse
Phone works normally. No issues. Was able to unlock the bootloader, just can't get rooted or CWM flashed.

no one can help you unless you give the exact steps that you tried to flash recovery and root
there is a thread on this in dev section
are you s4 or s3

rugmankc said:
no one can help you unless you give the exact steps that you tried to flash recovery and root
there is a thread on this in dev section
are you s4 or s3
Click to expand...
Click to collapse
I followed two different processes to flash recovery and then root. First one step-by-step manual process, as instructed at http://forum.xda-developers.com/showthread.php?t=1583427
First time I tried this, I got the error after the bootloader was unlocked. Thinking I might have done something wrong I carefully followed the step by step procedure there. Again same issue. I see quite a few people there with the same issue, but actually no resolution seems to be getting... I tried to Google, as well.
Then I thought of using the all-in-one tool for HTC One S from http://forum.xda-developers.com/showthread.php?t=1705913
No luck again
I'm on S3..
I tried using Paul's CWM to get to the recovery, but got stuck everytime at at the Red Text Error. Unlocking bootloader was easily done.

Ok , thanks for info
S3 may be the issue. I am not familiar with the procedures for S3, you might google S3 rooting
Someone should come along that knows more about it to help--sorry
I don't want to give wrong info
But, either way you will need htc drivers installed and working, if you don't already adb/fastboot setup

You need a recovery made for S3, right now only TWRP
http://forum.xda-developers.com/showthread.php?p=29075644

baseballfanz said:
You need a recovery made for S3, right now only TWRP
http://forum.xda-developers.com/showthread.php?p=29075644
Click to expand...
Click to collapse
Thanks! I will try this out. Will post if I still face any issues.

man_is_h said:
Thanks! I will try this out. Will post if I still face any issues.
Click to expand...
Click to collapse
Hey... This actually worked. Many thanks!

Phone shows unlocked but s=off

I had ended up using the all in one HTC One S root utility that was linked in the fourms. After following all the steps that where listed (While following the youtube guide) My phone when on bootloader will show ****Unlocked**** across the top but s=off any ideas on why that is? I havent quite been able to figure it out im just looking for more information so when I get home I can have at it again :/ just find it odd that given the steps and the fact I had done them all to the T im still having this issue. Any help would be great thanks for taking the time.
I assume this might be better fit for Q&A if your a mod i apologize if you could move it that would be great couldnt figure out how to delete the poist :/ "edit/delete" wont remove the post :/ sorry again

Well if you can post a photo of the boot loader screen that would help me in sorting out your issue.
Sent from my MIUI powered one s
If I helped you in any way please hit thanks!

Taco991 said:
Well if you can post a photo of the boot loader screen that would help me in sorting out your issue.
Sent from my MIUI powered one s
If I helped you in any way please hit thanks!
Click to expand...
Click to collapse
No worries I would be more than happy to provide one after I get home from work

smO[pdx] said:
I had ended up using the all in one HTC One S root utility that was linked in the fourms. After following all the steps that where listed (While following the youtube guide) My phone when on bootloader will show ****Unlocked**** across the top but s=off any ideas on why that is? I havent quite been able to figure it out im just looking for more information so when I get home I can have at it again :/ just find it odd that given the steps and the fact I had done them all to the T im still having this issue. Any help would be great thanks for taking the time.
I assume this might be better fit for Q&A if your a mod i apologize if you could move it that would be great couldnt figure out how to delete the poist :/ "edit/delete" wont remove the post :/ sorry again
Click to expand...
Click to collapse
Don't know what you are disappointed about. S-OFF stands for security being off. This may sound bad, but from a developer perspective, it's pretty good. If you have true S-OFF like you claim you do, you can flash ROMs, kernels, radios, etc... in a recovery with no issues at all; regardless of what hboot or custom recovery you have. Unlocked means that you can flash custom recoveries and such using fastboot, which is what you want. To sum it up, S-OFF is good; many devs are trying to get S-OFF, but NONE can figure it out. Just be happy about it.
Having this 'Unlocked' text is what you're going to get if you root/unlock the phone. No way to get around it. If you want to return to complete stock settings and re-lock, your best bet is to be on stock recovery and flash an RUU that corresponds to your network. You may also want to try 'fastboot oem lock'.

Closed Source Project said:
Having this 'Unlocked' text is what you're going to get if you root/unlock the phone. No way to get around it. If you want to return to complete stock settings and re-lock, your best bet is to be on stock recovery and flash an RUU that corresponds to your network. You may also want to try 'fastboot oem lock'.
Click to expand...
Click to collapse
Actually I think since he has s-off I think he can make it say whatever he wants.

Once you get the photo up PM me so I can help you out :laugh:

Taco991 said:
Once you get the photo up PM me so I can help you out :laugh:
Click to expand...
Click to collapse
So I can recall when I had the mytouch 4g the screen posted was exactly where you would go to flash the zip have they changed it since then? because I cant find the option to load a .zip rom file from :/

smO[pdx] said:
So I can recall when I had the mytouch 4g the screen posted was exactly where you would go to flash the zip have they changed it since then? because I cant find the option to load a .zip rom file from :/
Click to expand...
Click to collapse
Where's the S-OFF lol? And yes I think you can do that. It's PD some numbers IMG.zip..

smO[pdx] said:
So I can recall when I had the mytouch 4g the screen posted was exactly where you would go to flash the zip have they changed it since then? because I cant find the option to load a .zip rom file from :/
Click to expand...
Click to collapse
Facepalm. You do NOT have S-OFF, What the hell made you think you did. This is normal... Wow. You need to install a custom recovery to flash zips, by the way.

Hey easy on him, he was just mistaken. OP, do you need me to show you how to go back to stock?

smO[pdx] said:
I had ended up using the all in one HTC One S root utility that was linked in the fourms. After following all the steps that where listed (While following the youtube guide) My phone when on bootloader will show ****Unlocked**** across the top but s=off any ideas on why that is? I havent quite been able to figure it out im just looking for more information so when I get home I can have at it again :/ just find it odd that given the steps and the fact I had done them all to the T im still having this issue. Any help would be great thanks for taking the time.
I assume this might be better fit for Q&A if your a mod i apologize if you could move it that would be great couldnt figure out how to delete the poist :/ "edit/delete" wont remove the post :/ sorry again
Click to expand...
Click to collapse
Oh sweet jesus you're lucky as hell.
Never ever ever sell your phone, because you got your hands on a developer one or just a phone that slipped through the cracks, because you have full S-OFF.
You should be able to flash ROMs in recovery without going to fastboot to ever flash a kernel, if the ROM is set up for it.

You would do better to change thread title...

Hunt3r.j2 said:
Oh sweet jesus you're lucky as hell.
Never ever ever sell your phone, because you got your hands on a developer one or just a phone that slipped through the cracks, because you have full S-OFF.
You should be able to flash ROMs in recovery without going to fastboot to ever flash a kernel, if the ROM is set up for it.
Click to expand...
Click to collapse
Look at a couple post above urs he doesn't have soff
Sent from my HTC VLE_U using xda premium

Please help installing CleanROM 4.5....Stuck in Recovery....

I had my phone rooted and unlocked and was also using CleanROM 4.1 before I decided today to change to CleanROM 4.5.
So, I downloaded the file and went to Recovery and flashed it (it did take very little time with flashing which I found rather strange.) When I rebooted, the phone was stuck at the HTC screen. I figured that I MIGHT have had CWM installed and I didn't know it (I can't be quite 100% sure of this as I thought I DID have TWRP since it was a touch recovery that I had.) Since I was able to boot back up to Fastboot, I said "Let me flash the TWRP recovery file and try again".....Well, I did that and according to the Command Prompt it was successful (showed sending, writing, finished etc....) Once finished, I rebooted back and all I see now is the TeamWin logo in Recovery and THAT'S IT. It won't give me any menu options. If I let it sit, it will reboot back to the HTC screen.
What are my options right now? Is there a specific file I can flash through Fastboot that will allow me to proceed?
I would appreciate the help and I'll be sure to come back and let you know how successful I was. :fingers-crossed:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!

reflash
Try flashing the boot.IMG from the the zipped ROM you were trying to flash to boot partition through the bootloader (cmd in windows: fastboot flash boot boot.img[enter] after you put The boot.img in the same folder as the adb & cd to that folder) and flash cwm for recovery, then you can reflash twrp

thesm4rt1 said:
Try flashing the boot.IMG from the the zipped ROM you were trying to flash to boot partition through the bootloader (cmd in windows: fastboot flash boot boot.img[enter] after you put The boot.img in the same folder as the adb & cd to that folder) and flash cwm for recovery, then you can reflash twrp
Click to expand...
Click to collapse
I will definitely be trying that. Will be back in a couple of hours and let you know how it went. Thank you!

bbonline said:
I had my phone rooted and unlocked and was also using CleanROM 4.1 before I decided today to change to CleanROM 4.5.
So, I downloaded the file and went to Recovery and flashed it (it did take very little time with flashing which I found rather strange.) When I rebooted, the phone was stuck at the HTC screen. I figured that I MIGHT have had CWM installed and I didn't know it (I can't be quite 100% sure of this as I thought I DID have TWRP since it was a touch recovery that I had.) Since I was able to boot back up to Fastboot, I said "Let me flash the TWRP recovery file and try again".....Well, I did that and according to the Command Prompt it was successful (showed sending, writing, finished etc....) Once finished, I rebooted back and all I see now is the TeamWin logo in Recovery and THAT'S IT. It won't give me any menu options. If I let it sit, it will reboot back to the HTC screen.
What are my options right now? Is there a specific file I can flash through Fastboot that will allow me to proceed?
I would appreciate the help and I'll be sure to come back and let you know how successful I was. :fingers-crossed:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!
Click to expand...
Click to collapse
In the future I suggest factory wipe even if going from CR to CR. Also, make sure to check the MD5 once you move the file on to your storage.

Butters619 said:
In the future I suggest factory wipe even if going from CR to CR. Also, make sure to check the MD5 once you move the file on to your storage.
Click to expand...
Click to collapse
I did do the factory wipe.
By the way, I tried what I was told to do and nothing happened. It successfully flashes the boot image and recovery, but when it tries to boot into the recovery, it just freezes in the recovery with the word TEAMWIN and a blue background....No menu or options.... I did try several different ways by downloading and installing several versions of the CWM and TWRP, but no success. Any other suggestions? Will I be stuck with this piece of brick now? Please help.

bbonline said:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!
Click to expand...
Click to collapse
^That right there is normal by the way and will always be there.
Looks like it's time for you to relock your bootloader (don't worry you can unlock it again), download an RUU, and try again.

Butters619 said:
^That right there is normal by the way and will always be there.
Looks like it's time for you to relock your bootloader (don't worry you can unlock it again), download an RUU, and try again.
Click to expand...
Click to collapse
Ughh! Do you know if I will lose any documents/pictures that are in my USB storage? Which RUU do you think is the best in my case? Thanks!

bbonline said:
Ughh! Do you know if I will lose any documents/pictures that are in my USB storage? Which RUU do you think is the best in my case? Thanks!
Click to expand...
Click to collapse
You will lose the contents of your SD card, which is why you should back that up before flashing. Since you were on CR 4.1, I would go with the 1.85 RUU. If you use 2.20, you will add an extra step or two in when it comes to flashing ROMs. But hey, your phone should work again!

Butters619 said:
You will lose the contents of your SD card, which is why you should back that up before flashing. Since you were on CR 4.1, I would go with the 1.85 RUU. If you use 2.20, you will add an extra step or two in when it comes to flashing ROMs. But hey, your phone should work again!
Click to expand...
Click to collapse
I know, silly me. Usually I backup the data and everything goes well and when I don't, there goes my luck! I really appreciate the suggestion.
One quick question, if in the future I need to have the phone sent in for warranty, is this the same procedure I need to follow? Relock and flash an RUU? Will they not know it had been unlocked before?

bbonline said:
I know, silly me. Usually I backup the data and everything goes well and when I don't, there goes my luck! I really appreciate the suggestion.
One quick question, if in the future I need to have the phone sent in for warranty, is this the same procedure I need to follow? Relock and flash an RUU? Will they not know it had been unlocked before?
Click to expand...
Click to collapse
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.

Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
Darn.... I just hope I don't have to deal with sending it for any repair. Gave you thanks!

Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
But only if they reboot and look, which from what I've seen here, they never seem to do.

iElvis said:
But only if they reboot and look, which from what I've seen here, they never seem to do.
Click to expand...
Click to collapse
I took my One X back to Best Buy to swap it out just before the return policy expired because my gf dropped it and put a small dent in the casing and I didn't even bother to relock or even RUU my device. I said I had a software issue and couldn't get the OTA. They turned it on and played with it and it had a custom boot animation and a ROM on it lol. They also couldn't get the OTA so they approved the return.

Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
it doesn't say RELOCKED when you run an RUU. It gets rid of everything like Tampered and Unlocked and returns the phone to LOCKED. like it came
---------- Post added at 08:34 PM ---------- Previous post was at 08:31 PM ----------
Butters619 said:
I took my One X back to Best Buy to swap it out just before the return policy expired because my gf dropped it and put a small dent in the casing and I didn't even bother to relock or even RUU my device. I said I had a software issue and couldn't get the OTA. They turned it on and played with it and it had a custom boot animation and a ROM on it lol. They also couldn't get the OTA so they approved the return.
Click to expand...
Click to collapse
hahaha, thank god for company cutbacks sometimes... it makes the employees not give a ****. and rightfully so too!!
the fact that companies cut back to make a few more billion dollars makes me sick anyways. but this is not the place for this conversation. carry-on

trichrome1 said:
it doesn't say RELOCKED when you run an RUU. It gets rid of everything like Tampered and Unlocked and returns the phone to LOCKED. like it came
---------- Post added at 08:34 PM ---------- Previous post was at 08:31 PM ----------
hahaha, thank god for company cutbacks sometimes... it makes the employees not give a ****. and rightfully so too!!
the fact that companies cut back to make a few more billion dollars makes me sick anyways. but this is not the place for this conversation. carry-on
Click to expand...
Click to collapse
Nope once you unlocked it won't ever say locked again. Just re-locked

gunnyman said:
Nope once you unlocked it won't ever say locked again. Just re-locked
Click to expand...
Click to collapse
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.

trichrome1 said:
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.
Click to expand...
Click to collapse
You should probably double check that. Anybody with an AT&T One X had to have SuperCID to unlock their bootloader so that wouldn't matter. I have unlocked two AT&T One Xs and run the 1.85 RUU on both (one of them a couple times) and I have run the 2.20 RUU on one. every time it says RELOCKED.

Mine did this to when going to 4.5.
I did the following to get back into Recovery.
Use fastboot to flash the boot.img from the cleanrom 4.5 zip.
"fastboot flash boot boot.img"
I then flashed the recovery (TWRP 2.2.1.4 at the moment) again to the phone.
next I erased Cache.
"fastboot erase cache"
I then used the phone itself to reboot the bootloader and went into recovery. It took about 10 minutes but recovery finally booted.
At this point I had no access to anything on the SD card. so I selected mount and mounted the sd card as disk drive to access it through my PC. I was forced to format the drive at this point and loaded a fresh copy of the ROM onto the drive for flashing.

You probably just got a wrong recovery. The recovery on twrp website didn't work for me. The one I downloaded from the development section works fine.
Sent from my One X using xda app-developers app

trichrome1 said:
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.
Click to expand...
Click to collapse
Screenshots PLS

So did I just brick my phone?

Phone was rooted using TWRP. I locked the bootloader and now I can't boot up into anything but the page with the TAMPERED RELOCKED screen, also has bootloader, reboot, reboot bootloader, power down. Am I screwed? I just wanted to revert my rooted phone back to the original OS and it's been a freaking NIGHTMARE ):

XHaGGeNx said:
Phone was rooted using TWRP. I locked the bootloader and now I can't boot up into anything but the page with the TAMPERED RELOCKED screen, also has bootloader, reboot, reboot bootloader, power down. Am I screwed? I just wanted to revert my rooted phone back to the original OS and it's been a freaking NIGHTMARE ):
Click to expand...
Click to collapse
So you've relocked the bootloader, and then nothing else?
Run the RUU from the bootloader screen. Make sure the RUU is for YOUR phone

That's the thing, I can't get into it! I can't get into that screen where I could access stuff to INSTALL, MOUNT, etc.. it keeps taking me to the white screen with bootloader,reboot, etc.

XHaGGeNx said:
That's the thing, I can't get into it! I can't get into that screen where I could access stuff to INSTALL, MOUNT, etc.. it keeps taking me to the white screen with bootloader,reboot, etc.
Click to expand...
Click to collapse
Seeing as though you have relocked the bootloader you can either a. unlock the phone again so you can install a custom rom or b. run a ruu to get it back to stock.

Yeah because the problem is i have no OS to boot into. It just goes into recovery mode. Can you point me in the direction on how I can unlock the bootloader again?

XHaGGeNx said:
Yeah because the problem is i have no OS to boot into. It just goes into recovery mode. Can you point me in the direction on how I can unlock the bootloader again?
Click to expand...
Click to collapse
No no no. You said you wanted to go back to stock correct?
Download your stock RUU, and run from that white menu that says RE-LOCKED at the top. That's your bootloader

Ok, when you mean run from that white menu that says RELOCKED, how can I run it from that menu if I cant get into anything from this menu? Do you mean just run the RUU program from my computer and have my phone connected to the PC? I used to be able to go into that TWRP screen when i was in bootloader but now I can't.

XHaGGeNx said:
Ok, that's what I am doing already. I am downloading the RUU for my phone. Hope to gawd this will save my phone. I am just worried because it's literally stuck at this bootloader menu screen. I can't do anything else.
Click to expand...
Click to collapse
Believe me, the fact your screen is on is a sign you are not bricked. Run the RUU (Make sure it's one that is easily rootable, like the 1.85 for ATT), and go through the process of bootloader and unlock and rooting. Hope this helped

I am glad to hear that. It's almost done downloading, about 4 minutes left. I really want to thank you for helping me out here. I am such a screw up with this stuff. Sigh. anyways, I'll let you know what happens here shortly. Thank you so much once again. Really..

Honestly man once you get back to stock, don't worry about unlocking and rooting it. You have no business rooting your phone and flashing roms if you can accidentally delete your os, backup file, and the recovery partition. Not trying to be rude, but think about it, you could of destroyed your phone with one more bad flash

It's working! It's updating and everything. Phew! No offense taken, I hear ya and agree. Just being a noob at all this can put me into a lot of trouble. I have learned a lot of stuff though lol. Anyways, thank you everyone for helping me! I should be good from here

Glad to hear its working

Cheers man, good to hear everything is fixed.
If you need anything else, contact me. There are a bunch of ways to.
As for rooting again? Just read up and you'll be set.

mgutierrez87 said:
Honestly man once you get back to stock, don't worry about unlocking and rooting it. You have no business rooting your phone and flashing roms if you can accidentally delete your os, backup file, and the recovery partition. Not trying to be rude, but think about it, you could of destroyed your phone with one more bad flash
Click to expand...
Click to collapse
Hate to bump heads with ya dude but this isn't the way to be, I frown upon threads like this as well but I encourage others to root no matter who they are. Granted they do need to take the time to research what they are doing and how to get themselves out of a hole like this but someone has to help them learn
This is a community working towards a common goal, you never know maybe this dude will make his way towards development somewhere in the future. Or more likely since others helped him in his time in need he will turn around and try to do the same for someone else
Just my two cents
Sent from my HTC One XL using Tapatalk 2

mgutierrez87 said:
Honestly man once you get back to stock, don't worry about unlocking and rooting it. You have no business rooting your phone and flashing roms if you can accidentally delete your os, backup file, and the recovery partition. Not trying to be rude, but think about it, you could of destroyed your phone with one more bad flash
Click to expand...
Click to collapse
A simple "Be more careful next time because of ..." would have been just fine.

superchilpil said:
Hate to bump heads with ya dude but this isn't the way to be, I frown upon threads like this as well but I encourage others to root no matter who they are. Granted they do need to take the time to research what they are doing and how to get themselves out of a hole like this but someone has to help them learn
This is a community working towards a common goal, you never know maybe this dude will make his way towards development somewhere in the future. Or more likely since others helped him in his time in need he will turn around and try to do the same for someone else
Just my two cents
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
My apologies. We had been PMing for over an hour before this thread trying to get his phone back. I came off a little rude on that last post but he knows how hard I was trying to help him and that he can always come here for answers. Most forum guys would tell him to "search it"

please
how did you fix your phone i almost have same problem

He didn't delete ROM, recovery or anything. He relocked his bootloader. It just won't let you reboot unless you relock with a stock recovery flashed.
Sent from my One X using Tapatalk 2

http://forum.xda-developers.com/showthread.php?t=1982968
Could u guys stop by my thread and help me out?
I kinda have the same problem, and RUU tells me phone is off, error 170.
Thanks

[Q] Unauthorized software message ONLY when booting into recovery

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.