Database Info

[Q] should I update to 2.3.2 and reroot?

I recently just rooted my sns and got a notification for 2.3.2 and was wondering if I should install the update and see if the root sticks or
Unroot then install the update then root my sns
Sent from my Nexus S using XDA App

I'm assuming you're on stock rom.
Go ahead and update; some people are reporting they don't even lose root. I lost root privileges when I updated on stock rom but the files were still there, they had just had their executable permissions changed by the update. They're easy enough to get back.
I made some steps to follow using Clockwork Recovery that ensure you update and keep your root without needing a computer or any reboots. They're here" http://forum.xda-developers.com/showpost.php?p=10811723&postcount=29
If you have stock recovery and don't want to use Clockwork, go to the first post in that thread, and there's a link for stock recovery updates.
Edit, if you've got the OTA notification, you can just let it do its thing, and if you do lose root, just use fastboot to flash clockwork and then re-run the su zip file from it. You're back to full root.

Need Major Help Please

Today I went to reclock my bootloade on my evo design 4g. After it was locked I get a Security warning. The only way to get to the phone is to unlock it again.. Now I have a custom recovery installed CWM 5.0.2.7 installed. Now I was trying to but back stock recovery so I can get the new ics update when it come out.. But everything I have tried as failed in trying to reinstall stock recover or get future ota updates.. I hear I need to push it to the phone using adb, but not sure how it is done.. Can someone please post instructions on how this is done.. This is the second phone with the security warning issue I have had since unlocking the bootloader, and no one knows why it happens even HTC.

This thread can be closed. I solved my problem sort of. I managed to flash my stock recovery with bootloader still unlocked. Next was able to download and install OTA updates with bootloader still unlocked.. Now have all files necessary incase I run into same issue again.. So no need for this thread to stay open..

[Q] Verizon Galaxy S3 OTA after root?

I'm really confused about something and before I get flamed for not searching before posting, let me preface by saying that I have and still can't find a definitive answer given that nobody seems to reference the problem I'm having - at least it doesn't show up in my attempts to search.
My Question: Once I'm rooted, what is the process for accepting an OTAs (over the air updates) from Verizon? Whenever I download and install them, I get the "Custom" Lock Icon during bootup.
Here are the steps I've followed:
1. Flashed back to stock 4.1.1
2. Flashed the VRALEC bootchain
3. Flashed CWMR
4. Booted into CWMR recovery and ran the SuperSU_Bootloader_FIXED.zip (Note: no message appeared asking me about locking
5. Flashed the 4.1.1 bootchain
6. Downloaded and it auto rebooted to install the OTA (I wanted to see what it's like the NEXT time verizon pushes out an OTA so I know what the process is once all my apps are installed)
7. When finished applying the update it asks me: A. Do I want to Disable recovery flash? and B. Do I want to preserve root?
At first I tried answering both questions with yes and yes since I saw the message about that here: http://forum.xda-developers.com/showthread.php?t=2046439
My Problem: As soon as I rebooted, I get the custom lock icon message during bootup. So then I repeated the entire process and answered No and No to those questions. And again, I get the custom lock icon message during bootup.
Yes, I realize, I can and probably should install the OTA and then root the device. But that's not my point. I want to understand what to do the NEXT time Verizon pushes out an OTA. Do I have to flash back to stock every time I install the OTA and root the device only after installing the OTA just to avoid getting the custom lock icon? If not, how do I accept the OTA without getting the custom lock icon? (Obviously I can't seem to figure out how to do it now, so I won't be able to do it the next time an OTA rolls around - thus the reason for my question).
Thanks,
Jonathan

you might have to flash a custom ROM to block Verizon from pushing OTA.

http://forum.xda-developers.com/showthread.php?t=1762709
Reference section 5 for me. It looks like you already know how to get to that point. It has great instructions for recovering to stock from the triangle.
As far as disabling updates go I would recommend titanium backup, and freezing the update service. "FWUpgrade" as well as "SDM" are the names. You can also uninstall it, but freezing it in Titanium is my recommendation.... This will prevent your phone from pinging OTA updates in the future even when big red pushes them.
Honestly, if you want the new feature just wait a day or two after the release. There is always a lovely developer waiting to debloat, deodex, and optimize the official OTA update for your use without breaking root access.
Have I helped with your question? Or have I misinterpreted your needs?

First, thanks for the replies!
ManiakalSealion said:
http://forum.xda-developers.com/showthread.php?t=1762709
Reference section 5 for me. It looks like you already know how to get to that point. It has great instructions for recovering to stock from the triangle.
Click to expand...
Click to collapse
I think you misunderstood me on this point. When installing an OTA after root, I never get the yellow triangle, so there is no need to recover. The problem I'm having is that on the very first screen that appears when you first power on the phone (after installing the OTA on top of a rooted version of Android) it adds a large lock icon with the word "CUSTOM" to black screen (think it says Samsung but I don't recall) to indicate that Verizon has detected something custom about the phone.
I was trying to determine if after having rooted my phone if there was a way to accept the OTA and still maintain root - rather than having to flash back to stock or flash an update using ODIN. It's a pain to have to always flash something at home - I'd like to be able to accept the OTA if possible while I'm away from home. I tried OTA Rootkeeper but that didn't seem to do anything for me - perhaps I'm not using it correctly???
ManiakalSealion said:
http://forum.xda-developers.com/showthread.php?t=1762709
As far as disabling updates go I would recommend titanium backup, and freezing the update service. "FWUpgrade" as well as "SDM" are the names. You can also uninstall it, but freezing it in Titanium is my recommendation.... This will prevent your phone from pinging OTA updates in the future even when big red pushes them.
Click to expand...
Click to collapse
So if I understand correctly, an app such as OTA Rootkeeper is useless for Verizon Galaxy S3 - the only way to get root and the Verizon OTA is to either 1. flash back to stock, install all OTAs and then re-root OR else 2. flash the custom OTA from a forum member, is that correct? In other words, once I've rooted, I always have to use ODIN to get an update - there is no other option?

jkrueger2020 said:
First, thanks for the replies!
I think you misunderstood me on this point. When installing an OTA after root, I never get the yellow triangle, so there is no need to recover. The problem I'm having is that on the very first screen that appears when you first power on the phone (after installing the OTA on top of a rooted version of Android) it adds a large lock icon with the word "CUSTOM" to black screen (think it says Samsung but I don't recall) to indicate that Verizon has detected something custom about the phone.
Click to expand...
Click to collapse
I'll suggest using EZ Unlock v1.2, just tap to lock then immediately tap to unlock your bootloader and you'll hear an audio confirmation upon pressing unlock. I think that should take care of the custom lock when booting up.
I was trying to determine if after having rooted my phone if there was a way to accept the OTA and still maintain root - rather than having to flash back to stock or flash an update using ODIN. It's a pain to have to always flash something at home - I'd like to be able to accept the OTA if possible while I'm away from home. I tried OTA Rootkeeper but that didn't seem to do anything for me - perhaps I'm not using it correctly???
Click to expand...
Click to collapse
I'll say this, most custom roms block Verizon OTA's from installing so you'll just have to accept that you need to flash back to stock to accept an OTA OR just stick to a rooted OTA based rom. There's at least seven of these, one per OTA or leak that we've seen to date.
So if I understand correctly, an app such as OTA Rootkeeper is useless for Verizon Galaxy S3 - the only way to get root and the Verizon OTA is to either 1. flash back to stock, install all OTAs and then re-root OR else 2. flash the custom OTA from a forum member, is that correct? In other words, once I've rooted, I always have to use ODIN to get an update - there is no other option?
Click to expand...
Click to collapse
Absolutely correct. Can I ask you something? Do you intend on using custom roms or do you just want to use rooted stock OTA's? Cuz you're inquiring an awful lot about OTA's for someone who would be using custom roms. That said, XDA devs have posted a rooted version of each OTA available. Each is in the dev section, they'll be titled something like "Stock Root JB 4.1.2 - I535VRBMB1 Official Update". You could easily just flash any one of these then pull down an OTA since these are left untouched with the only addition being SuperUser. Even still, you would need to re-root after accepting an OTA since OTA's wipe out root so you'll be doing this for as long as we see updates on this phone.

If you're rooted you can use OTA Rootkeeper to back up root, install OTA and then use it again to restore root. I just did this for the current OTA without any issues. Just make sure you also have stock recovery reinstalled if you installed TWRP or CWM, and relock the boot loader first.
Sent from my SCH-I535 using xda app-developers app

SlimSnoopOS said:
I'll suggest using EZ Unlock v1.2, just tap to lock then immediately tap to unlock your bootloader and you'll hear an audio confirmation upon pressing unlock. I think that should take care of the custom lock when booting up.
Click to expand...
Click to collapse
Yes! That removed the lock icon. So my next question is, when my phone booted back up and said the OTA failed (yet still shows the incremented version number making it appear like the update actually was successful) was there anything that got messed up as part of the upgrade? Or would I be better off going the route of another person's reply which said I should lock the bootloader and flash back to stock recovery first before accepting the OTA?
SlimSnoopOS said:
I'll suggest using EZ Unlock v1.2
Can I ask you something? Do you intend on using custom roms or do you just want to use rooted stock OTA's?
Click to expand...
Click to collapse
Currently I'm not really looking for custom ROMS - my experience with ROMS with my original Galaxy S was just a buggy experience (i.e. call volumes that kept reverting to max for every call, etc) and was not very enjoyable. As long as I stay rooted and current with Android I'm happy at this point (of course that could change down the road).

mav3rick478 said:
If you're rooted you can use OTA Rootkeeper to back up root, install OTA and then use it again to restore root. I just did this for the current OTA without any issues. Just make sure you also have stock recovery reinstalled if you installed TWRP or CWM, and relock the boot loader first.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thank you!!!! That was exactly what I was hoping to find! I tried this out just for kicks to see if it would work for me and it did!
For anyone interested, here are the steps I took with my rooted device :
1. Lock the boot loader using EZ-Unlock 1.2
2. Using EZ-Recovery 2.2, I flashed the stock recovery
3. Backed up root access using OTA Root Keeper
4. Downloaded and installed the OTA
Note: The lock icon appeared still
5. Used EZ-Recovery 2.2. to flash CWM recovery in place of the stock recovery (I couldn't get it to flash the same tar.md5 file I used with ODIN though - don't know what kind of file EZ-Recovery needs - so I used the version of CMWR that it provided)
6. Restored root access using OTA Root Keeper (needs reboot I think for this step)
7. Unlocked boot loader using EZ-Unlock 1.2
I may have gotten these steps slightly out of order but this successfully allowed me to install the OTA (with a successful install message too) and got rid of my lock icon!!!

jkrueger2020 said:
Thank you!!!! That was exactly what I was hoping to find! I tried this out just for kicks to see if it would work for me and it did!
For anyone interested, here are the steps I took with my rooted device :
1. Lock the boot loader using EZ-Unlock 1.2
2. Using EZ-Recovery 2.2, I flashed the stock recovery
3. Backed up root access using OTA Root Keeper
4. Downloaded and installed the OTA
Note: The lock icon appeared still
5. Used EZ-Recovery 2.2. to flash CWM recovery in place of the stock recovery (I couldn't get it to flash the same tar.md5 file I used with ODIN though - don't know what kind of file EZ-Recovery needs - so I used the version of CMWR that it provided)
6. Restored root access using OTA Root Keeper (needs reboot I think for this step)
7. Unlocked boot loader using EZ-Unlock 1.2
I may have gotten these steps slightly out of order but this successfully allowed me to install the OTA (with a successful install message too) and got rid of my lock icon!!!
Click to expand...
Click to collapse
Almost worked flawlessly... I had to reboot from SuperSU to get root again.

I found the sdm thing to freez
smalrus said:
Almost worked flawlessly... I had to reboot from SuperSU to get root again.
Click to expand...
Click to collapse
I found the sdm thing to freez but could not find the fwupgrade one. I was also not able to fine the ez unlocker is that in the play store?
I am not sure if the sdm will block the update but now when I go to about phone and select software update it errors out. Also I am only rooted do I realy need to worry about the update? Also looking for a good stable rom. If anyone wants recomend one. Just got my phone like a week ago. Thank you guys. Xda has been great help.

joker66599 said:
I found the sdm thing to freez but could not find the fwupgrade one. I was also not able to fine the ez unlocker is that in the play store?
I am not sure if the sdm will block the update but now when I go to about phone and select software update it errors out. Also I am only rooted do I realy need to worry about the update? Also looking for a good stable rom. If anyone wants recomend one. Just got my phone like a week ago. Thank you guys. Xda has been great help.
Click to expand...
Click to collapse
Re-read the thread to find EZ Unlock, I'm fairly certain someone posted a link. I will say it's been removed from the Play Store for awhile now.
Freezing sdm 1.0 is all you really need to do. That's normal that it errors out now. You froze that setting so it won't be polling for an OTA nor allow you to manually search for an OTA. Whether you want the OTA or not is on you, there isn't much present that we do not already have in custom roms plus the OTA has already been rooted.
Sent from my SCH-I535 using xda app-developers app

This is what worked for me except I reversed step 5 and 6 (I edited the quote below to match what I did). Thanks!
jkrueger2020 said:
Thank you!!!! That was exactly what I was hoping to find! I tried this out just for kicks to see if it would work for me and it did!
For anyone interested, here are the steps I took with my rooted device :
1. Lock the boot loader using EZ-Unlock 1.2
2. Using EZ-Recovery 2.2, I flashed the stock recovery
3. Backed up root access using OTA Root Keeper
4. Downloaded and installed the OTA
5. Restored root access using OTA Root Keeper
6. Used EZ-Recovery 2.2. to flash TWRP recovery in place of the stock recovery
7. Unlocked boot loader using EZ-Unlock 1.2
I may have gotten these steps slightly out of order but this successfully allowed me to install the OTA (with a successful install message too) and got rid of my lock icon!!!
Click to expand...
Click to collapse

Stock rooted MB1 here w/ TWRP. Tried to update earlier and completely soft bricked my phone. Had to do some fancy work to get it back and restore.
Now I tried this process:
1. Lock the boot loader using EZ-Unlock 1.2
2. Using EZ-Recovery 2.2, I flashed the stock recovery
3. Backed up root access using OTA Root Keeper
4. Downloaded and installed the OTA
5. Restored root access using OTA Root Keeper
6. Used EZ-Recovery 2.2. to flash TWRP recovery in place of the stock recovery
7. Unlocked boot loader using EZ-Unlock 1.2
and when I get to the step of actually installing the OTA - it reboots into stock recovery - and about 15 seconds in it fails and shows the android guy on his back. lol
It actually boots back into the phone properly & says that the update failed. Status page shows the baseband got updated, but not the ROM. Any ideas?
thanks
Edit: Bah. It's the stupid 'E: Error in /tmp/sideload/package.zip error.' According to my searches there's no easy fix.
Edit #2: I just wound up dirty flashing the full stock root package from Scott & Beans. That worked.

I'm running the MD3 on the stock ROM and rooted. Now when I originally rooted my phone (using this guide: http://forum.xda-developers.com/showthread.php?t=2046439), I'm fairly confident that I did NOT unlock the bootloader and also installed the CWM Touch recovery. After the process was over I had an unlocked padlock image show up on my phone every time it booted.
Now, I tried to install the new update via OTA (I defrosted all apps I had frozen) and when the phone re-booted to start the update, I received the warning message "System software not authorized by Verizon...." and in the upper left hand corner it says in red, "Secure: Kernel". The phone will continue to boot to this message. When I try to boot into recovery, it goes to this message, not the CWM recovery. The only way to get out of that message is to boot into Odin mode and hit Vol DOWN to cancel.
SO.....what do I need to do in order to install this new update?
UPDATE: I unlocked via EZ Unlock and rebooted into recovery and this time I was able to get into my CWM recovery and updated the zip file posted on another thread in the general forum. All is well now.

Can I upgrade OTA after root but on STOCK ROM?
So if I'm rooted, but still running one of the VERIZON's STOCK ROM,
1. Can I upgrade OTA?
2. Will suck OTA upgrade unroot my phone?
Thanks

mandar_h said:
So if I'm rooted, but still running one of the VERIZON's STOCK ROM,
1. Can I upgrade OTA?
2. Will suck OTA upgrade unroot my phone?
Thanks
Click to expand...
Click to collapse
As of this moment, yes to both. The newest ota is VRBMF1 and you can still root/unlock that version just as easy as any other.

[Q] Samsung Galaxy Tab 2 10.1 won't update

I have a samsung galaxy tab 2 10.1 gt-p5113
I tried to root it before, but got as far as flashing the recovery software ( can't find the thread I used to do this but I think it involved odin)
anyways when I flashed the recovery software the tab got stuck at the boot screen and I though it was bricked but after reflashing and restarting it a few times it worked again....needless to say I didn't have the balls to try rooting it after that.....
now when I search for software updates it says my device has been modified and cannot update ( it still is NOT rooted )
Is this because of the recovery software?...which as far as I can tell hasn't been properly installed cause I can't find any evidence of it on my tab, even when i hold down the power and volume button and the recovery software is supposed to show up.
and how do i undo it so that I can get updates? I just want the stock software back. will a factory reset do the trick?

No, the instant you attempted to install CWM, a bootloader data value changed that made your device always read as modified. There are three ways to get to Jelly Bean from where you are.
1. Root and run TriangleAway. This app will reset the bootloader counter, so you should be able to upgrade normally.
2. Install CWM via ODIN and install a custom JB-based ROM. You will need to root first if you want to keep your data via Titanium Backup.
3. ODIN a JB-based ROM for your carrier/region. Same deal as above with rooting and keeping your data.
Posted from my Fascinate using XDA Premium

MultipleMonomials said:
No, the instant you attempted to install CWM, a bootloader data value changed that made your device always read as modified. There are three ways to get to Jelly Bean from where you are.
1. Root and run TriangleAway. This app will reset the bootloader counter, so you should be able to upgrade normally.
2. Install CWM via ODIN and install a custom JB-based ROM. You will need to root first if you want to keep your data via Titanium Backup.
3. ODIN a JB-based ROM for your carrier/region. Same deal as above with rooting and keeping your data.
Posted from my Fascinate using XDA Premium
Click to expand...
Click to collapse
I have this same exact problem. I have tried to un-root but nothing happned. I have tried to update via Kies and nothing happened. Should I try to root again? I just want to get the 4.2.2 update.

If you want your device's status to read "official",
1. Root your device (I prefer Chainfire autoroot)
2.a) Run triangle away, reset your bin (flash) counter. Now your bootloader will say 0 counts.
2.b) As for the device status (in about device), there's a button just under "reset" in triangle away application, tap it and reboot. Your device status will now be "official"
3. (Optional) Go to your Superuser application, tap cleanup and unroot (if available)
Now you're unrooted, and running official firmware. You can use OTA anytime.

[Q] Probable softbrick (at least half)

What are my alternatives now?
Previously I was running CleanRom7 – but somehow must taken enough of update to somehow have locked the bootloader:
I’m currently running a “official Samsung” version that is 4.1.2.
I can do the following:
• Flash Root
• Flash a new recovery – used the latest CWM version 2.6.3.1
• Any attempt to either flash the latest ML1 or old CleanRom7 don’t successfully boot.
• At that point I can ODIN back to the 4.1.2 official Samsung version
The download screen looks like this:
Product Name: ICH-I535
Custom Binary Download: Yes (2 count)
Current Binary: Samsung Official
System Status: Official
Qualcom Secureboot: Enable
I’m constantly getting asked by some app if I want to do the OTA upgrade, I have been postponing for 1 hour
Question is given these 2 alternatives, what are the opinions to these two questions:
At this point should I just either ODIN or flash the latest ML1 upgrade and then root?
Or
Stay on 4.1.2?

bgbird said:
What are my alternatives now?
Previously I was running CleanRom7 – but somehow must taken enough of update to somehow have locked the bootloader:
I’m currently running a “official Samsung” version that is 4.1.2.
I can do the following:
• Flash Root
• Flash a new recovery – used the latest CWM version 2.6.3.1
• Any attempt to either flash the latest ML1 or old CleanRom7 don’t successfully boot.
• At that point I can ODIN back to the 4.1.2 official Samsung version
The download screen looks like this:
Product Name: ICH-I535
Custom Binary Download: Yes (2 count)
Current Binary: Samsung Official
System Status: Official
Qualcom Secureboot: Enable
I’m constantly getting asked by some app if I want to do the OTA upgrade, I have been postponing for 1 hour
Question is given these 2 alternatives, what are the opinions to these two questions:
At this point should I just either ODIN or flash the latest ML1 upgrade and then root?
Or
Stay on 4.1.2?
Click to expand...
Click to collapse
Ok, The question is, do you still want to flash custom rom/kernel?? If you do and since you're still on 4.1.2 you still can unlock the bootloader and flash custom 4.3 rom (with unlocked bootloader) for the 4.3 experience/look & feel.

More info
buhohitr said:
Ok, The question is, do you still want to flash custom rom/kernel?? If you do and since you're still on 4.1.2 you still can unlock the bootloader and flash custom 4.3 rom (with unlocked bootloader) for the 4.3 experience/look & feel.
Click to expand...
Click to collapse
I'd like a custom rom - but when I tried to flash the ML4.3 offered on this site - or even tried to reflash my old Cleanrom7 that i still had on my external flash memory that previously worked I couldn't boot.
I flashed VRUCML1_Stock_Root_Deodex (12.31.13 downloaded from the link. MD5 checked OK) this would try to boot - then just go back into recovery (I used the latest version of TWRP and used EZ-Unlock). Of course I wiped the device before I started. I flashed the rom and observed all of the successful messages during the flash. I never caught the really little blue message that flashed at the beginning of the boot cycle before it went black and rebooted to recovery. At that point I wiped again and flashed Cleanrom 7. It flashed, then started the installer that let me pick all sorts of apps. When I tried to boot - it just hung on the Samsung SIII banner that appears shortly after boot. I let it sit there for about an hour before pulling the battery. Then I ODINed back the the 4.1.2 version that I'm running now.
I tried this several times - even going as far as installing CRP recovery - same result.
So I'm about our of ideas...

bgbird said:
I'd like a custom rom - but when I tried to flash the ML4.3 offered on this site - or even tried to reflash my old Cleanrom7 that i still had on my external flash memory that previously worked I couldn't boot.
I flashed VRUCML1_Stock_Root_Deodex (12.31.13 downloaded from the link. MD5 checked OK) this would try to boot - then just go back into recovery (I used the latest version of TWRP and used EZ-Unlock). Of course I wiped the device before I started. I flashed the rom and observed all of the successful messages during the flash. I never caught the really little blue message that flashed at the beginning of the boot cycle before it went black and rebooted to recovery. At that point I wiped again and flashed Cleanrom 7. It flashed, then started the installer that let me pick all sorts of apps. When I tried to boot - it just hung on the Samsung SIII banner that appears shortly after boot. I let it sit there for about an hour before pulling the battery. Then I ODINed back the the 4.1.2 version that I'm running now.
I tried this several times - even going as far as installing CRP recovery - same result.
So I'm about our of ideas...
Click to expand...
Click to collapse
When you flashed back to 4.1.2 and it's working fine, at this point check to see if your bootloader is unlocked (even unlock tool said unlocked, you need to verify that it's unlocked). If it's not what ever you flash will not work.

buhohitr said:
When you flashed back to 4.1.2 and it's working fine, at this point check to see if your bootloader is unlocked (even unlock tool said unlocked, you need to verify that it's unlocked). If it's not what ever you flash will not work.
Click to expand...
Click to collapse
I never "flash" back. I have an ODIN image (KIES_HOME_I535VRBMF1_1152558_REV09_user_low_ship.tar.md5 ) that I use. At that point everything is replaced and I'm back to a stock bootloader (at least that's how it looks to me). When I root - then use EZ-Unlock at this point, the bootloader is locked. I suppose that it would be interesting to try to "flash" a 4.1.2 original and see what would happen.

bgbird said:
I never "flash" back. I have an ODIN image (KIES_HOME_I535VRBMF1_1152558_REV09_user_low_ship.tar.md5 ) that I use. At that point everything is replaced and I'm back to a stock bootloader (at least that's how it looks to me). When I root - then use EZ-Unlock at this point, the bootloader is locked. I suppose that it would be interesting to try to "flash" a 4.1.2 original and see what would happen.
Click to expand...
Click to collapse
I believe your image is fine. The key I want to point out is make sure your bootloader is unlocked. After you unlock with EZ-Unlock, boot into download mode and verify that the bootloader is actually unlock, before you proceed to flash anything else.

buhohitr said:
I believe your image is fine. The key I want to point out is make sure your bootloader is unlocked. After you unlock with EZ-Unlock, boot into download mode and verify that the bootloader is actually unlock, before you proceed to flash anything else.
Click to expand...
Click to collapse
OK - I'll try that. What do I look for in download mode that would indicate (or what should I try to do) that would prove that I'm "unlocked"?

boot into Odin mode (download mode) and you shoud see.

buhohitr said:
boot into Odin mode (download mode) and you shoud see.
Click to expand...
Click to collapse
I don't see anything about "unlocked"
when i press the down volume, home and power button I start into ODIN mode.
if i press the down arrow the phone will just re-boot
then i press the up arrow to continue into ODIN (download mode) I get:
:
Product Name: ICH-I535
Custom Binary Download: Yes (3 count)
Current Binary: Customl
System Status: Customl
Qualcom Secureboot: Enable
I still don't see anything about the unlocked bootloader

bgbird said:
I don't see anything about "unlocked"
when i press the down volume, home and power button I start into ODIN mode.
if i press the down arrow the phone will just re-boot
then i press the up arrow to continue into ODIN (download mode) I get:
:
Product Name: ICH-I535
Custom Binary Download: Yes (3 count)
Current Binary: Customl
System Status: Customl
Qualcom Secureboot: Enable
I still don't see anything about the unlocked bootloader
Click to expand...
Click to collapse
This Qualcom Secureboot: Enable - meaning bootloader is locked

buhohitr said:
This Qualcom Secureboot: Enable - meaning bootloader is locked
Click to expand...
Click to collapse
Just as a matter of curiosity, EZ-Unlock reports the bootloader to be “unlocked”. Wonder what’s wrong with that?
So pretty much at this point it appears that the only thing that I can do is to ODIN the official 4.3 tar file or stay on the 4.1.2 file that I ODINed previously.

bgbird said:
Just as a matter of curiosity, EZ-Unlock reports the bootloader to be “unlocked”. Wonder what’s wrong with that?
So pretty much at this point it appears that the only thing that I can do is to ODIN the official 4.3 tar file or stay on the 4.1.2 file that I ODINed previously.
Click to expand...
Click to collapse
Are you rooted? if not it's not going to work.

buhohitr said:
This Qualcom Secureboot: Enable - meaning bootloader is locked
Click to expand...
Click to collapse
I am rooted - I'm sure of that...
I'm also running the latest TWRP recovery.
EZ-Unlock still lets me lock and unlock the bootloader.
I'm also thinking of flashing VRLE6.bootloader.zip, rebooting, doing an EZ-Unlock and seeing what happens.
If that doesn't work - I'll have to decide
1. do I f staying where I'm at - running 4.1.2 ?
or
2. Do I give up and take the softbrick tar file and lock everything up ?
I'm not sure of what are the pros and cons of either alternative

bgbird said:
EZ-Unlock still lets me lock and unlock the bootloader. I'm also thinking of flashing VRLE6.bootloader.zip, rebooting, doing an EZ-Unlock and seeing what happens.
If that doesn't work - I'll have to decide
1. do I f staying where I'm at - running 4.1.2 ?
or
2. Do I give up and take the softbrick tar file and lock everything up ?
I'm not sure of what are the pros and cons of either alternative
Click to expand...
Click to collapse
If you're not rooted, EZ unlock just report false results.
If you like to play with custom rom/kernel, meaning not bug free and become a flashcoholic then stay with 4.1.2
If you want a stable, no headache trouble free then upgrade to 4.3
I upgraded my wife to 4.3 and very happy with the results. Everything just work, performance is very good and smooth, gps locked in seconds...enough said.

buhohitr said:
If you're not rooted, EZ unlock just report false results.
If you like to play with custom rom/kernel, meaning not bug free and become a flashcoholic then stay with 4.1.2
If you want a stable, no headache trouble free then upgrade to 4.3
I upgraded my wife to 4.3 and very happy with the results. Everything just work, performance is very good and smooth, gps locked in seconds...enough said.
Click to expand...
Click to collapse
Even if I had to stay on 4.1.2 I'd want CleanRom7 at least. I used that since July when it came out. I liked the features and customizations. I'd like to continue to flash - however every time that I try ( and you can see the results earlier in the thread) the phone wouldn't boot. I think that some part of the OTA got on the phone. For a period of time, I was constantly nagged to take the upgrade. I think that my son answered "yes" and some part updated - until stopped Cleanrom.
Anyway I tried to reflash CleanRom as well as the non-locked ML1 item. Each time, Samsung flashes, then the ornamental Samsung SIII graphic just sits there. In a normal boot, that only lasts a second. Maybe I'll try it again and let sit there for an hour or two and see if something changes.

bgbird said:
Even if I had to stay on 4.1.2 I'd want CleanRom7 at least. I used that since July when it came out. I liked the features and customizations. I'd like to continue to flash - however every time that I try ( and you can see the results earlier in the thread) the phone wouldn't boot. I think that some part of the OTA got on the phone. For a period of time, I was constantly nagged to take the upgrade. I think that my son answered "yes" and some part updated - until stopped Cleanrom.
Anyway I tried to reflash CleanRom as well as the non-locked ML1 item. Each time, Samsung flashes, then the ornamental Samsung SIII graphic just sits there. In a normal boot, that only lasts a second. Maybe I'll try it again and let sit there for an hour or two and see if something changes.
Click to expand...
Click to collapse
If you are switch from rom to rom, you may have trash residuals. I would wipe cache/dalvik cache/data/system before I flash another rom (clean install), saved me a lot of little issues here and there...

buhohitr said:
If you are switch from rom to rom, you may have trash residuals. I would wipe cache/dalvik cache/data/system before I flash another rom (clean install), saved me a lot of little issues here and there...
Click to expand...
Click to collapse
Formatting your internal SD may also be needed, because 4.3 creates a 0/ folder that 4.1 doesn't have.
Alternatively, philz touch recovery has a 0/folder migration that will clear out that folder when switching.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
Formatting your internal SD may also be needed, because 4.3 creates a 0/ folder that 4.1 doesn't have.
Alternatively, philz touch recovery has a 0/folder migration that will clear out that folder when switching.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
two questions?
1. Do you have a link for philz touch recovery?
2. If I format the internal SD - will an nandroid backup still work? I thought that that had to back into an identical file structure...
Also I do a factory reset each time that I flash.
I know that I'm root because EZ-Unlock requires it. If root isn't enabled - it terminates. When Root is enabled, SuperSU asks permission to do the unlock

bgbird said:
two questions?
1. Do you have a link for philz touch recovery?
2. If I format the internal SD - will an nandroid backup still work? I thought that that had to back into an identical file structure...
Click to expand...
Click to collapse
1.
http://forum.xda-developers.com/showthread.php?t=2588639
2. No, The file structure gets completely replaced because a nandroid copies your internal sd card. It'll remake the folder structure.
Sent from my SCH-I535 using Tapatalk 2

Just a quick question to cover all the bases. Which version of EZ Unlock are you using? Version 1.2 is the only one that actually works to unlock your bootloader.