I hope I dont get chewed out for asking this, but I'm on 4.3 I535VRUCML1. I've done so much stuff to it that I need to go back to stock in order to get the 4.4 update. I can odin back to the stock version of this correct? I'm just confused.....
xcodybx said:
I hope I dont get chewed out for asking this, but I'm on 4.3 I535VRUCML1. I've done so much stuff to it that I need to go back to stock in order to get the 4.4 update. I can odin back to the stock version of this correct? I'm just confused.....
Click to expand...
Click to collapse
Yes, just Odin the stock ML1 and after that you should able to OTA upgrade to 4.4kitkat.
Yeah I just did this earlier today. Used Odin to get back to stock 4.3, and then installed the OTA, and it worked fine.
Related
I used this http://forum.xda-developers.com/showthread.php?t=1755386 and now it wont update to the newest OTA. I locked the bootloader, reset the flash counter, reloaded the stock image and nothing seems to work. I need to send this phone back to Verizon.
Edit: **** it, I just flashed the newest Odin OTA, http://goo.im/devs/invisiblek/i535/...535VZWALG1_743127_REV09_user_low_ship.tar.zip
I doubt Verizon techs will know any better.
When did this ota role out wonder what it is???
Sent from Vzw Galaxy SIII running CleanROM 2.0 w/CleanKERNEL
ForeverSupra said:
I used this http://forum.xda-developers.com/showthread.php?t=1755386 and now it wont update to the newest OTA. I locked the bootloader, reset the flash counter, reloaded the stock image and nothing seems to work. I need to send this phone back to Verizon.
Edit: **** it, I just flashed the newest Odin OTA, http://goo.im/devs/invisiblek/i535/...535VZWALG1_743127_REV09_user_low_ship.tar.zip
I doubt Verizon techs will know any better.
Click to expand...
Click to collapse
What were you running for a ROM on your phone? Did you flash the stick kernel back to?
-Need to figure out how to do something with your phone? Check out this Guide
-Did my rantings somehow help you? Hit the thanks button [email protected] :silly:
-Sent from my Synergized SIII
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 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
l flashed kitkat with Odin and rooted with cf autoroot. Is it safe enough to use Mobile Odin to revert back to 4.1.2?
Yes, you can flash stock 4.1.2 with mobile odin, but you will still have de kitkat bootloader.
In what way does that matter, I mean is there anything I should be aware of?
eta: How do I get the old bootloader back, just in case I need/want it?
schnurrbidurr said:
In what way does that matter, I mean is there anything I should be aware of?
eta: How do I get the old bootloader back, just in case I need/want it?
Click to expand...
Click to collapse
good question! KK bootloader just fuked up odin and everything usefulll...so even you flashed back 4.1.2 u wont be able to flash anything else . even the KK (idiotic) version of Samsung Roms....so nothing usefull
i still cant resolve the nonworking wifi issue, nothing works as it should be...
appreciate any advises
I did get the wifi to work by flashing KK with Odin, but wifi as a whole seems a little temperamental. I have not yet returned to JB as I'm a big ol' chicken and don't want to mess a working, albeit rubbish, rom up.
I can not figure out how to get 67.220.3.ME865.Retail.en.05 flashed back to my ME865. RSD will not work, it shows failure. It downloads as tar.gz file.
I can get the MB865 ATT version on, but really want to put this back to stock, as i am selling it. Thanks.
jeffelzy said:
I can not figure out how to get 67.220.3.ME865.Retail.en.05 flashed back to my ME865. RSD will not work, it shows failure. It downloads as tar.gz file.
I can get the MB865 ATT version on, but really want to put this back to stock, as i am selling it. Thanks.
Click to expand...
Click to collapse
The reason you can't go back to the proper firmware is because you made the mistake of flashing the AT&T firmware. Once you've flashed that one it's there to stay and you can't flash any others.
P.S. My mind and thumb wandered at the same time so enjoy the free thanks and don't spend it all in one place.
It failed prior to me flashing the AT&T version. Flashing the AT&T was just to make sure I could go back to ICS.
So is it possible to go back to Gingerbread then update to ICS?
jeffelzy said:
So is it possible to go back to Gingerbread then update to ICS?
Click to expand...
Click to collapse
No once your on ics you cant go back, unless you want to brick..