Database Info

[Q] flashing locked bootloader doesn't stick?

So, my phone is running 4.1.2 rooted, and it got an OTA recently. The OTA failed because the bootloader was unlocked.
I thought easy-peasy, just odin flash the locked boot loader and download/apply OTA again, right?
Flashed fine, locked and clean for initial boot. But when it went to install the OTA, same problem happened, the bootloader was miraculously unlocked again, and the OTA failed.
Any ideas on how I can get past this? I really don't mind loosing root, just trying to avoid a complete odin reflash and loosing everything...

I am just curious ... why would you want to update to the OTA 4.3 and forever lock down the bootloader? Once the verizon 4.3 update takes hold, you might be able to root, but (so far) will not be able to load custom roms without bricking the device.

vax1170 said:
I am just curious ... why would you want to update to the OTA 4.3 and forever lock down the bootloader? Once the verizon 4.3 update takes hold, you might be able to root, but (so far) will not be able to load custom roms without bricking the device.
Click to expand...
Click to collapse
Well your almost right. First off you for sure can root. Second you can install custom roms with safestrap. Its limited to tw roms atm. There have been a hand full of people who upgraded just to use safestrap. I wouldnt recomend it right now because its alittle buggy.

RedBullet said:
So, my phone is running 4.1.2 rooted, and it got an OTA recently. The OTA failed because the bootloader was unlocked.
I thought easy-peasy, just odin flash the locked boot loader and download/apply OTA again, right?
Flashed fine, locked and clean for initial boot. But when it went to install the OTA, same problem happened, the bootloader was miraculously unlocked again, and the OTA failed.
Any ideas on how I can get past this? I really don't mind loosing root, just trying to avoid a complete odin reflash and loosing everything...
Click to expand...
Click to collapse
Wife's phone. She doesn't want to mess with it.
I think I figured it out, looks like I had a custom recovery installed. Flashed that to stock and locked bootloader and all is fine now. Running latest and greatest. Just what the missus is looking for...

RedBullet - Ah, I fully understand now I'm having a similar conversation with my misses.
ThePagel - Thanks. One one of my phones was cursed with an accidental OTA 4.3 upgrade. Nice to know something is in the works, I'll dig up that thread and watch it.

vax1170 said:
RedBullet - Ah, I fully understand now I'm having a similar conversation with my misses.
Click to expand...
Click to collapse
I assume if one wants to go the custom ROM route they would simply need to odin flash one of the older stock images and go from there. Doesn't seem like a big problem. Of course > 50% chance I have no idea what I'm talking about...

RedBullet said:
I assume if one wants to go the custom ROM route they would simply need to odin flash one of the older stock images and go from there. Doesn't seem like a big problem. Of course > 50% chance I have no idea what I'm talking about...
Click to expand...
Click to collapse
If you take the 4.3 OTA, you cannot odin flash an older stock image. Will brick your device.

landshark68 said:
If you take the 4.3 OTA, you cannot odin flash an older stock image. Will brick your device.
Click to expand...
Click to collapse
Really? That is pretty tragic. I may only buy unlocked devices from here on out; they seem to be getting better and better at making their devices less and less useful...

It sure is sad but true. Im thankful google blessed us with the nexus 5
RedBullet said:
Really? That is pretty tragic. I may only buy unlocked devices from here on out; they seem to be getting better and better at making their devices less and less useful...
Click to expand...
Click to collapse

Questions about flashing 4.4 ROM. Coming from 4.1 Please help!

So like the title says I have been out of the ROM game for a little bit. Every couple of months I check in and see whats new and flash something else.
I was on the Jelly Beans ROM (Build 16 I think) and Android 4.1. I did some searching last night as was going to try flashing Gummy ROM…bad idea. I am guessing I needed something prior to jumping up to a 4.4 base. I booted to recovery and wiped everything and tried to flash with no luck. So the phone would not boot and I could only get into recovery and download mode. I did not have my micro SD adapter in order to get jelly beans back on it to flash so I ended up having to use odin to flash a stock rooted 4.1 image. Finally got everything back up and running but I still want to try some of the 4.4 ROMs. So what exactly do I need first in order to flash one? (Modem maybe)…if you know for sure why that happened and what I need to do please let me know. Thanks!
My Current "About Phone" Info...
Android Version - 4.1.2
Baseband version - I535VRBMB1
Jelly Beans - Build 20
P.S. I have tried doing the research and nothing I have found has been clear but one thing I came across is the official 4.3 update was bad news and broke the root methods? So should I stay away from 4.3 ROMs and is the old root method blocked in 4.4 as well or is that a different case since it wasn't actually released for our phone. If that makes sense lol

aholeinthewor1d said:
So like the title says I have been out of the ROM game for a little bit. Every couple of months I check in and see whats new and flash something else.
I was on the Jelly Beans ROM (Build 16 I think) and Android 4.1. I did some searching last night as was going to try flashing Gummy ROM…bad idea. I am guessing I needed something prior to jumping up to a 4.4 base. I booted to recovery and wiped everything and tried to flash with no luck. So the phone would not boot and I could only get into recovery and download mode. I did not have my micro SD adapter in order to get jelly beans back on it to flash so I ended up having to use odin to flash a stock rooted 4.1 image. Finally got everything back up and running but I still want to try some of the 4.4 ROMs. So what exactly do I need first in order to flash one? (Modem maybe)…if you know for sure why that happened and what I need to do please let me know. Thanks!
P.S. I have tried doing the research and nothing I have found has been clear but one thing I came across is the official 4.3 update was bad news and broke the root methods? So should I stay away from 4.3 ROMs and is the old root method blocked in 4.4 as well or is that a different case since it wasn't actually released for our phone. If that makes sense lol
Click to expand...
Click to collapse
Can't tell you exactly why that happened, but it shouldve worked.
You're right though, stay away from the stock Ota 4.3 update. I'm happy you read first because so many people don't. My guess is your firmware was a little too old. Try to flash the mf1 firmware aio and then try gummy.
To be clear, you can still use any custom rom, even the 4.3 ones, just stay away from the stock rom or anything having to do with 4.3 ML1 firmware
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
Can't tell you exactly why that happened, but it shouldve worked.
You're right though, stay away from the stock Ota 4.3 update. I'm happy you read first because so many people don't. My guess is your firmware was a little too old. Try to flash the mf1 firmware aio and then try gummy.
To be clear, you can still use any custom rom, even the 4.3 ones, just stay away from the stock rom or anything having to do with 4.3 ML1 firmware
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick reply. What do you mean try to flash the MF1 firmware...does that mean a 4.2 ROM?
I think I saw the new jellyBeans/alliance ROM was 4.3...or maybe it was something else..either way it would be ok to flash the 4.3 ROM? and if I wanted I could go back to a 4.1 Rom then..

aholeinthewor1d said:
Thanks for the quick reply. What do you mean try to flash the MF1 firmware...does that mean a 4.2 ROM?
I think I saw the new jellyBeans/alliance ROM was 4.3...or maybe it was something else..either way it would be ok to flash the 4.3 ROM? and if I wanted I could go back to a 4.1 Rom then..
Click to expand...
Click to collapse
Yes you can interchange between both of them if you want to.
So go here, read all of the details, and just follow his recommendation:
http://forum.xda-developers.com/showthread.php?t=1788313
Also don't double post, modify your post in the development section and put "wrong section, mod please delete".
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
Yes you can interchange between both of them if you want to.
So go here, read all of the details, and just follow his recommendation:
http://forum.xda-developers.com/showthread.php?t=1788313
Also don't double post, modify your post in the development section and put "wrong section, mod please delete".
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
The reason I have so confused is cause of the link you sent. I read that before and it says..
"You should NOT flash the I535VRUCML1 firmware (or any subsequent releases for that matter). You will brick. This is what vzw/samsung did on the first OTA for the Galaxy S4. They changed the keys they sign the firmware with. This prevents us from 'mis-matching' our firmware like we've been doing all along. We've been leaving aboot (VRUAME6, the african-canadian sock-monkey leaked bootloader) alone and updating everything else. Since they're signing with different keys now, doing this will brick your device. If you update the ENTIRE bootchain (including aboot) you shouldn't brick, but will be stuck with a locked bootloader and any attempt to downgrade (via dd, etc) will brick you as well."
Like i said I have been out for a while and lost track of what firmwares came out and the order of them and which I need to be on to flash a 4.4 ROM. Someone else told me the only reason my first flash failed was because my recovery was older
***EDIT****
Ignore that entire thing I just realized you said to stay away from ML1 and that MF1 is ok..opps

aholeinthewor1d said:
The reason I have so confused is cause of the link you sent. I read that before and it says..
"You should NOT flash the I535VRUCML1 firmware (or any subsequent releases for that matter). You will brick. This is what vzw/samsung did on the first OTA for the Galaxy S4. They changed the keys they sign the firmware with. This prevents us from 'mis-matching' our firmware like we've been doing all along. We've been leaving aboot (VRUAME6, the african-canadian sock-monkey leaked bootloader) alone and updating everything else. Since they're signing with different keys now, doing this will brick your device. If you update the ENTIRE bootchain (including aboot) you shouldn't brick, but will be stuck with a locked bootloader and any attempt to downgrade (via dd, etc) will brick you as well."
Like i said I have been out for a while and lost track of what firmwares came out and the order of them and which I need to be on to flash a 4.4 ROM. Someone else told me the only reason my first flash failed was because my recovery was older
Click to expand...
Click to collapse
I see, that actually makes perfect sense.
I think I read you were on the mb1 firmware, that's new enough to not cause problems.
Basically you can't get the ml1 firmware from that thread I linked you. The only ml1 file available is the modem, and that's perfectly safe to flash.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
I see, that actually makes perfect sense.
I think I read you were on the mb1 firmware, that's new enough to not cause problems.
Basically you can't get the ml1 firmware from that thread I linked you. The only ml1 file available is the modem, and that's perfectly safe to flash.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I think I am getting it... I am on MB1...next was MF1....and then ML1. As long as I have a new recovery I can flash any MF1 based ROM right over MB1...and then I can flash the ML1 modem ONLY. If that is correct let me know..also does it matter if I do MF1 ROM or ML1 modem first?
again just wanted to say thanks for the help I appreciate it

aholeinthewor1d said:
I think I am getting it... I am on MB1...next was MF1....and then ML1. As long as I have a new recovery I can flash any MF1 based ROM right over MB1...and then I can flash the ML1 modem ONLY. If that is correct let me know..also does it matter if I do MF1 ROM or ML1 modem first?
again just wanted to say thanks for the help I appreciate it
Click to expand...
Click to collapse
You're close, firmware is completely independent from rom. You can flash any 4.3, 4.4, or 4.1 rom without changing your firmware.
Right now you can flash mf1 aio package, then ml1 modem, or just flash the ml1 modem over your current mb1 firmware.
Basically you aren't required to be on a specific rom build in order to use a specific modem.
Edit: I think you have the right idea, flash any rom you want, then the mf1 aio package, then the ml1 modem. Your firmware sequence is correct.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
You're close, firmware is completely independent from rom. You can flash any 4.3, 4.4, or 4.1 rom without changing your firmware.
Right now you can flash mf1 aio package, then ml1 modem, or just flash the ml1 modem over your current mb1 firmware.
Basically you aren't required to be on a specific rom build in order to use a specific modem.
Edit: I think you have the right idea, flash any rom you want, then the mf1 aio package, then the ml1 modem. Your firmware sequence is correct.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
ah ok...idk why I was thinking the firmware was what the ROMs were based from....so either way ML1 firmware sucks and I stay away...I guess my last questions are...what would be an advantage of going to the MF1 firmware...
and I always used clockworkmod recovery...do you know the option available now? and maybe some features of each

[Q] VRUCNC1 Help?

I have read through multiple posts but I am still slightly confused. So I have a Samsung Galaxy S3 running VRUCNC1. I have read that it is unrootable and that using ODIN to downgrade is the only option, but I have also read that downgrading will brick your phone. Could someone assist me with this?

Trevon75 said:
I have read through multiple posts but I am still slightly confused. So I have a Samsung Galaxy S3 running VRUCNC1. I have read that it is unrootable and that using ODIN to downgrade is the only option, but I have also read that downgrading will brick your phone. Could someone assist me with this?
Click to expand...
Click to collapse
Once your phone has taken either 4.3 OTA (VRUCML1 or VRUCNC1), downgrading to 4.1.2 will result in a hard brick. You can only switch between VRUMCL1 and VRUCNC1, the phone will essentially not boot on any other firmware. Downgrade to VRUCML1 then root via Saferoot. It is safe to do this.
Users with unlocked bootloaders (aka people who did not take either 4.3 OTA) can switch to ICS or JB 4.1.2 via Odin without fail or issue. We can do so, unless somehow we end up taking either 4.3 ota.

SlimSnoopOS said:
Once your phone has taken either 4.3 OTA (VRUCML1 or VRUCNC1), downgrading to 4.1.2 will result in a hard brick. You can only switch between VRUMCL1 and VRUCNC1, the phone will essentially not boot on any other firmware. Downgrade to VRUCML1 then root via Saferoot. It is safe to do this.
Users with unlocked bootloaders (aka people who did not take either 4.3 OTA) can switch to ICS or JB 4.1.2 via Odin without fail or issue. We can do so, unless somehow we end up taking either 4.3 ota.
Click to expand...
Click to collapse
Thank you! I apologize for the late response, but you explained this perfectly for me. I was able to downgrade and root, install safestrap, and even flash a ROM. However, I have only gotten one ROM to flash correctly. Is there another step I have missed? I have only gotten CleanROM 8.1 to flash correctly while everything else flashes but does not boot. I really appreciate the help!

Trevon75 said:
Thank you! I apologize for the late response, but you explained this perfectly for me. I was able to downgrade and root, install safestrap, and even flash a ROM. However, I have only gotten one ROM to flash correctly. Is there another step I have missed? I have only gotten CleanROM 8.1 to flash correctly while everything else flashes but does not boot. I really appreciate the help!
Click to expand...
Click to collapse
Unsure why it won't flash any other roms try this thread it's a good starting point
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Xparent ICS Tapatalk 2

Install Lollipop OTA while Rooted

Hi, I am curious if I receive the Lollipop OTA update and choose to install it, what exactly will happen? I am rooted, running stock and franco kernel. I remember I installed the 4.4.4 OTA update while rooted, and it installed fine and I still had root.

If i were u i would unroot...reinstall stock kernel and recovery... Considering the fact that it is biggest ever update..so things may go wrong if not entirely stock...
However since i m nt u...i would rather flash system directly

You can't apply any ota if you have modified system or have a custom kernel, so why not just flash a rooted stock zip, which will come out before you get the OTA.anyway
Sent from my Nexus 5 using Tapatalk

Why do people care about an OTA when it will be at least a week after the initial release before a lot of people will even get it?
#stayparanoid

Pirateghost said:
Why do people care about an OTA when it will be at least a week after the initial release before a lot of people will even get it?
#stayparanoid
Click to expand...
Click to collapse
Because 99% of XDA have zero idea what they're actually doing and just want to be spoonfed with an OTA.

OP, there is a thread in the sticky roll-up that has all the info you need about OTA's and how to flash them.
Closed.

[Q] ReRoot: Non official update but custom 4.4.4

Just researching converting back to factory. Thought Odin would be straight forward, and maybe it still is. But read something that scared the bejeebees out of me. Something about not converting back from 4.3 to 4.1 or something like that = brick. Now, I am assuming they do mean the Official OTA 4.3 update and assuming that my updates have always been from custom roms since 4.1 and are not going to affect returning to stock = brick. IS THIS TRUE?
Second question, I am looking for the Verizon download for the latest firmware available now.
Third, is Odin still the best choice to return to root?

iclickjohn said:
Just researching converting back to factory. Thought Odin would be straight forward, and maybe it still is. But read something that scared the bejeebees out of me. Something about not converting back from 4.3 to 4.1 or something like that = brick. Now, I am assuming they do mean the Official OTA 4.3 update and assuming that my updates have always been from custom roms since 4.1 and are not going to affect returning to stock = brick. IS THIS TRUE?
Second question, I am looking for the Verizon download for the latest firmware available now.
Third, is Odin still the best choice to return to root?
Click to expand...
Click to collapse
1. Unless you want to be stuck on a locked bootloader do not take any official OTA.
2. If you want a locked bootloader it's available here in the forums, I highly suggested again this
3. Odin doesn't root the phone, if your still on a custom rom then your already rooted
Sent from my SCH-I535 using Xparent ICS Tapatalk 2