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
Related
Hi everyone,
I just flashed the JellyBean leaked TEST OTA India to my P3100 from SamMobile. Is my warranty void now? If yes, will I be able to get it back? Will I receive any further updates from Samsung? How will I get the official version of JB? I am really very confused. Also, my Tab isn't connecting through Kies. And what about the Flash Counter?
Please help.
Thanks a lot.
aqshyt said:
Hi everyone,
I just flashed the JellyBean leaked TEST OTA India to my P3100 from SamMobile. Is my warranty void now? If yes, will I be able to get it back? Will I receive any further updates from Samsung? How will I get the official version of JB? I am really very confused. Also, my Tab isn't connecting through Kies. And what about the Flash Counter?
Please help.
Thanks a lot.
Click to expand...
Click to collapse
Yes, technically your warranty is void, and no you can't get it back. I say technically because I've seen manufacturers turn a blind eye to some things (I once sent an obviously rooted phone in without question). You won't receive further updates, because they are unlikely to make patches for a leak that isn't supposed to be public. You'll either get official JB by flashing back the latest stock firmware, or by flashing the stock OTA when its available for download.
Next time I would suggest you research these questions before flashing leaked builds.
Warranty is not void.You can reset the flash counter using triangle away. You can Odin back to any version you want to in order to take OTAs. Though if your going to root and use a custom recovery its best to wait for someone to make it custom recovery rdy rather then reverting to stock for a ota your going to root anyways. Most times hours after a ota there is a rooted flashable version posted. Should be careful flashing any leaked software least they find a way to patch our current root methods.
RomsWell said:
Should be careful flashing any leaked software least they find a way to patch our current root methods.
Click to expand...
Click to collapse
The only way to do that would be to lock the bootloader, and Verizon Wireless is the only one having that done these days. Even HTC and Motorola's locked devices can be unlocked if you want now.
Thanks a lot
RomsWell said:
Warranty is not void.You can reset the flash counter using triangle away. You can Odin back to any version you want to in order to take OTAs. Though if your going to root and use a custom recovery its best to wait for someone to make it custom recovery rdy rather then reverting to stock for a ota your going to root anyways. Most times hours after a ota there is a rooted flashable version posted. Should be careful flashing any leaked software least they find a way to patch our current root methods.
Click to expand...
Click to collapse
Thanks a lot RomsWell for your reply. Am happy that I can get back my warranty and make my Tab 2 just as I got from the store I hope the Samsung people will never come to know what I did?
i updated my verizon Galaxy S3 (I535) today, and forgot to unroot it so expectedly i go the "unsuccessful" update, but it did update, i have the changes. but i cannot get into supersu so i cannot unroot my phone (never really used the rooting anyways)
is there anyway to unroot my phone atm? and/or to make sure i have the entire update?
(wasnt really expecting to get the update at all with a rooted phone)
also i cannot get into supersu cause my phone is still recongnized as 4.3 instead of 4.1.2
...not really sure what to do
Hmm, well you can root using SafeRoot according to multiple users in our general TW 4.3 thread.
Maybe you can unroot after you root using that but there's no way to downgrade or Odin flash a ML1 tar unless we see one published in the near future. If you unroot after rooting then you could probably try installing the TW 4.3 update.zip in recovery but there's no guarantees it'll work and if it messes up, you're SOL until further notice.
Edit: so its clear, you can ONLY root. Flashing roms is not possible or recommended as of this moment if on TW 4.3
SlimSnoopOS said:
Hmm, well you can root using SafeRoot according to multiple users in our general TW 4.3 thread.
Maybe you can unroot after you root using that but there's no way to downgrade or Odin flash a ML1 tar unless we see one published in the near future. If you unroot after rooting then you could probably try installing the TW 4.3 update.zip in recovery but there's no guarantees it'll work and if it messes up, you're SOL until further notice.
Edit: so its clear, you can ONLY root. Flashing roms is not possible or recommended as of this moment if on TW 4.3
Click to expand...
Click to collapse
ok thanks,
ill keep watch, i mean everything seems fine on my phone its just the "unsucessful update" is a bit foreboding given that i obviously have the update o.o
no way to downgrade either atm i take it?
if i could down grade i could unroot easily and then update
KabuTheFox said:
ok thanks,
ill keep watch, i mean everything seems fine on my phone its just the "unsucessful update" is a bit foreboding given that i obviously have the update o.o
no way to downgrade either atm i take it?
if i could down grade i could unroot easily and then update
Click to expand...
Click to collapse
Nah, you'll have a hardbricked phone with seemingly no way to fix it if you attempt to downgrade. If/when VRUCML1 stock tar file is posted then you could flash that in Odin. What you'll need is something specifically for TW 4.3 whether that's root, root/unlock, or Odin. Nothing older is compatible.
KabuTheFox said:
i updated my verizon Galaxy S3 (I535) today, and forgot to unroot it so expectedly i go the "unsuccessful" update, but it did update, i have the changes. but i cannot get into supersu so i cannot unroot my phone (never really used the rooting anyways)
is there anyway to unroot my phone atm? and/or to make sure i have the entire update?
Click to expand...
Click to collapse
I believe that by going to the OTA 4.3, you are no longer rooted. The update "unrooted" you.
Thanks Slim !!
:good::good:
SlimSnoopOS said:
Hmm, well you can root using SafeRoot according to multiple users in our general TW 4.3 thread.
Maybe you can unroot after you root using that but there's no way to downgrade or Odin flash a ML1 tar unless we see one published in the near future. If you unroot after rooting then you could probably try installing the TW 4.3 update.zip in recovery but there's no guarantees it'll work and if it messes up, you're SOL until further notice.
Edit: so its clear, you can ONLY root. Flashing roms is not possible or recommended as of this moment if on TW 4.3
Click to expand...
Click to collapse
SafeRoot was a success and I now have a rooted device. I just purchased this used and it did an automatic update when i turned it on. Pretty bummed about now being able to switch out the ROM, but at least I've got root now! saferoot is awesome!
aarontsuru said:
I believe that by going to the OTA 4.3, you are no longer rooted. The update "unrooted" you.
Click to expand...
Click to collapse
the update database doesnt recongize my phone tho, and thats why it couldnt complete the update.
but according to my phone im still on 4.3 technically
it has been some time, there might already be something out for all i know by now
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
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
Hi there
I'm currently on 4.3 / VRUCML1, but would like to upgrade to KitKat. I actually dont mind TouchWiz and really just looking for a deodexed, debloated 4.4.x ROM. I've searched and read a bunch of articles here, but I'm still having a difficult time determining if there's an official ROM I can upgrade to that wont lock my bootloader. Is there a good option for this?
If there isnt a good option Im wondering if I should I just upgrade to something like 4.4 SuperLiteRom / VRUDNE1 knowing I'll be locked in? Im planning to upgrade my phone in the next few months anyway, so that wouldnt be the worst thing if thats my only option. If I do go this route, whats the recommended upgrade path? Go right to loading SuperLite? Or revert to stock, update OTA, then goto SuperLite?
Thanks in advance!!
timofcourse said:
Hi there
I'm currently on 4.3 / VRUCML1, but would like to upgrade to KitKat. I actually like TouchWiz and really just looking for a deodexed, debloated 4.4.x ROM. I've searched and read a bunch of articles here, but I'm still having a difficult time determining if there's an official ROM I can upgrade to that wont lock my bootloader.
Could someone clarify this (or point me to someplace that does) for me?
Thanks!
Click to expand...
Click to collapse
There is no rom available that won't lock your bootloader. They can't get a 4.4 rom to boot without the 4.4 stock kernel, so you're limited up to 4.3.
Sent from my HTC6525LVW using Tapatalk
BadUsername said:
There is no rom available that won't lock your bootloader. They can't get a 4.4 rom to boot without the 4.4 stock kernel, so you're limited up to 4.3.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
So if I wanted upgrade to 4.4 to something like the superlite rom, whats the recommended upgrade path? Go right to loading SuperLite? Or revert to stock, update OTA, then goto SuperLite?
timofcourse said:
So if I wanted upgrade to 4.4 to something like the superlite rom, whats the recommended upgrade path? Go right to loading SuperLite? Or revert to stock, update OTA, then goto SuperLite?
Click to expand...
Click to collapse
You would need to Odin flash kitkat stock rom first, then install through safestrap.
Just realize that once you do that you're stuck, there's no going back.
Sent from my HTC6525LVW using Tapatalk
I am on 4.3 AllianceROM. I rooted and unlocked the phone before they came out with the official 4.3 update that, from my understanding, locks KNOX. Am I correct in assuming that I cannot load a newer version of Android on this phone unless I lock the bootloader? Are there no CM or ASOP options available?
I know this is lame but I want to put Pokemon Go on it and I need 4.4 for it to run.
Any suggestions?
JurKZ said:
I am on 4.3 AllianceROM. I rooted and unlocked the phone before they came out with the official 4.3 update that, from my understanding, locks KNOX. Am I correct in assuming that I cannot load a newer version of Android on this phone unless I lock the bootloader? Are there no CM or ASOP options available?
I know this is lame but I want to put Pokemon Go on it and I need 4.4 for it to run.
Any suggestions?
Click to expand...
Click to collapse
If you're bootloader unlocked you're fine, lots of AOSP 5.0 Roms available.
Just follow directions to update the modem without locking your bootloader.