Just pulled in a new update on my s3 so let's pray it's the fix for mobile data. Will post up build number when finished. Build is I535VRBMF1 android 4.1.2 and was a pretty small update.
Is there multiwindow?
Sent from my SCH-I535 using xda app-developers app
Oh good.. That sounds like a new update. Hopefully that means InvisibleK will package a new AIO with the new modem/rpm/sbls for us.
Sent from my SCH-I535 using xda app-developers app
Multi Window is still there.
Currently not being productive on my S3.
---------- Post added at 12:23 AM ---------- Previous post was at 12:18 AM ----------
Build number I535VRBMF1
Currently not being productive on my S3.
http://www.droid-life.com/2013/06/1...hopefully-this-addresses-connectivity-issues/
Sent from my SCH-I535 using Tapatalk 2
Can anyone post the update file?
Sent from my SCH-I535 using xda app-developers app
bricked my phone
So I am pretty new to the community and have only rooted my phone for use of ARliberator. I recently took the MD3 OTA and the signal was crap, now I get the new update this am MF3 and it bricked my phone with the message "system software not authorized by vzw take to store" blah blah. I tried this using voodoo root keeper with out un-rooting first.
Guessing my only option is to flash back in odin mode or is there some recovery that I can try? I have everything backed up with titanium pro. how would I reload all of that after I flash?
Chadashcroft22 said:
...and was a pretty small update.
Click to expand...
Click to collapse
How small ? The previous update that they pulled was just under 130mb as I recall. This one should be very close to the same size unless it's a firmware update only and the "premium suite" will come later.
jdrama12 said:
So I am pretty new to the community and have only rooted my phone for use of ARliberator. I recently took the MD3 OTA and the signal was crap, now I get the new update this am MF3 and it bricked my phone with the message "system software not authorized by vzw take to store" blah blah. I tried this using voodoo root keeper with out un-rooting first.
Guessing my only option is to flash back in odin mode or is there some recovery that I can try? I have everything backed up with titanium pro. how would I reload all of that after I flash?
Click to expand...
Click to collapse
ODIN back to stock OEM , then take all the updates before rooting again. Make a full backup in recovery before using Titanium Backup to restore. Restoring Apps + data with TB can cause issues.
DigitalMD said:
ODIN back to stock OEM , then take all the updates before rooting again. Make a full backup in recovery before using Titanium Backup to restore. Restoring Apps + data with TB can cause issues.
Click to expand...
Click to collapse
So after trying about 5 times my phone booted back up and is working. The update did not go through but my phone is working as it was before. I dont know why the recovery wouldnt boot at first unless it was the update blocking it for a few minutes.
Might have made the rookie mistake since I didnt do the temp un-root with voodoo, but I was trying to be innovative and see if it worked with out it like it did with the MD3 OTA.
Thanks for everyones help on here, teaching a noob like me new tricks.
just updated and kept root...data is appears fixed, thank god
Sent from my Barnes & Noble Nook HD using xda premium
rsswga said:
just updated and kept root...data is appears fixed, thank god
Sent from my Barnes & Noble Nook HD using xda premium
Click to expand...
Click to collapse
Can you give some more details on this? Did you use voodoo root keeper and how did you do it?
I am weary of trying again since it bricked my phone for about 10 minutes.
Updated: I535VRBMF1
I can actually send text messages again...! Cant wait to test 4G in areas it was disabled with the mb3 update.
i used rootkeeper and ezrecovery, flashed to stock recovery and then updated
lost root and had to reroot and unlock bootloader again...............just restarted phone
all good now with mf1
jdrama12 said:
Can you give some more details on this? Did you use voodoo root keeper and how did you do it?
I am weary of trying again since it bricked my phone for about 10 minutes.
Click to expand...
Click to collapse
rsswga said:
i used rootkeeper and ezrecovery, flashed to stock recovery and then updated
lost root and had to reroot and unlock bootloader again...............just restarted phone
all good now with mf1
Click to expand...
Click to collapse
Many thanks. I just was trying to do it with voodoo with out any flashing like I was able to for MD3 however I have tried it twice and it has not worked. I will do have to try the flashing method sometime after work.
Thanks for the help.
Any way I can remove twrp so I can take the update?
Sent from my SCH-I535 using xda app-developers app
jdrama12 said:
Many thanks. I just was trying to do it with voodoo with out any flashing like I was able to for MD3 however I have tried it twice and it has not worked. I will do have to try the flashing method sometime after work.
Thanks for the help.
Click to expand...
Click to collapse
I tried just temp unrooting with voodokeeper, downloading and installing the update, and it worked and the phone loaded up phone and I was able to turn root back on with Voodkeeper no problem. I have two S3s, one is a mistake I made in getting a phone for a now ex that was supposed to pay their share of the bill, etc and didn't and I took the phone back. That's the one I experiment stuff with and tried it there with no problems. I'm afraid to do it without ODINing etc though on the phone I always use. The ex's phone never seems to have any problems with updates and re-rooting though.
something stSettem
kidqwik said:
I tried just temp unrooting with voodokeeper, downloading and installing the update, and it worked and the phone loaded up phone and I was able to turn root back on with Voodkeeper no problem. I have two S3s, one is a mistake I made in getting a phone for a now ex that was supposed to pay their share of the bill, etc and didn't and I took the phone back. That's the one I experiment stuff with and tried it there with no problems. I'm afraid to do it without ODINing etc though on the phone I always use. The ex's phone never seems to have any problems with updates and re-rooting though.
Click to expand...
Click to collapse
Glad to hear that method worked for you. I just tried it again and I get to right after it shuts off and get past the Samsung screen with RECOVERY in the top left in blue, to the yellow triangle saying "you have unauthorized VZW software...turn off device and take to store..." with SECURE:KERNEL in red in the top left...i think thats what it says.
Guessing flash method is all that will work for me, owell.
Thanks again.
Go to odin flash valrec or whatever it is then flash clockwork mod...flash the superuserfix that's used to root and unlock the bootloader...
sent from a violated Vzw Galaxy s3
rsswga said:
Go to odin flash valrec or whatever it is then flash clockwork mod...flash the superuserfix that's used to root and unlock the bootloader...
sent from a violated Vzw Galaxy s3
Click to expand...
Click to collapse
Thanks, just not sure how it got locked on me unless MD3 did that. I will try that later when I am not at work though.
Related
Im on stock rooted 2.3.4
My phone is trying to go 2.3.6
I currently have no interest in this and as of 10pm tonight i am leaving on vaca for 4 days. directly after work (3pm) i am going to dmv where i will prob rot for about 3 hours.
My main question is at least this. If i just take the update to stop the constant nagging its doing to me (like i am doing to this forum right now) will i lose my root? I CANT lose root right now because without tethering I will be FORCED to actually talk with my girlfreind while away instead of tethering her phone and letting her play on the web. This to me is like having my nuts squeezed in a vice!
If I take the update and my phone screws up I will have NO time to redo it until I get back. If it wasnt of this kind of importance I would have already tried the update and just restored if it didnt work. I have an image of my phone in CMR BUUUUUUUUUUUUT I have had CMR break down on me before trying to restore and cant risk it. Dont want to have to press later for 4 days lol.
Thanks
If you want to be on 2.3.6 save yourself the trouble and flash a rooted version.
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
If you want to be on 2.3.6 save yourself the trouble and flash a rooted version.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
i just want to stop the nagger
tevil said:
i just want to stop the nagger
Click to expand...
Click to collapse
Its simple. Either take the update and then flash superuser from cwm to gain root again or just flash the update in cwm.
Ether way your bootloader will not be changed neither will your recovery.
Sent from my Nexus S 4G
if i flash it in CWR will it remove the root or does it stay there. also i have been looking for the update somewhere and havent had luck.
I see one 2.3.6 rom that was pulled for the 9020a and one update for i think the 9023
if you have a 9020a update link i can install from CWM i would appreciate it. Tried using search funtion.
thanks
i let the ota through and didn't loose root. did you check here for what you're looking for:
http://forum.xda-developers.com/showthread.php?t=1056062
I was laying in bed (with food poisoning) trying to get some sleep, when I noticed my phone vibrated and randomly rebooted.
After it booted up to the Andy firmware update image, and finally to the home screen with the update message I knew I was screwed.
THIS WAS A FORCED UPDATE BY VERIZON. I NEVER ACCEPTED OR DECLINED ANYTHING (re: food poisoning)!
You WILL lose root, on device app searching (Apple legal bs), and probably your unlock!
The perfect end to a perfect night! THANKS Verizon! /sarcasm
mcduck$ said:
I was laying in bed (with food poisoning) trying to get some sleep, when I noticed my phone vibrated and randomly rebooted.
After it booted up to the Andy firmware update image, and finally to the home screen with the update message I knew I was screwed.
THIS WAS A FORCED UPDATE BY VERIZON. I NEVER ACCEPTED OR DECLINED ANYTHING (re: food poisoning)!
You WILL lose root, on device app searching (Apple legal bs), and probably your unlock!
The perfect end to a perfect night! THANKS Verizon! /sarcasm
Click to expand...
Click to collapse
What ROM were you running? It should have disable OTA's thats why I ask.
Brian Gove said:
What ROM were you running? It should have disable OTA's thats why I ask.
Click to expand...
Click to collapse
The title says rooted stock.
I was runing the stock touchwiz rom (with the VRGL2 or 1 baseband) rooted, stock recovery, and the bootloader unlocked.
I just checked the EZ unlocker app and it claims that the bootloader is still unlocked. I have no way of verifying this, but if true, I'm only half screwed until somebody finds a root method for the new firmware.
If/when that happens I'll be more than happy to flash away from Verizon's bs nonsense.
Grrr...
mcduck$ said:
I was runing the stock touchwiz rom (with the VRGL2 or 1 baseband) rooted, stock recovery, and the bootloader unlocked.
I just checked the EZ unlocker app and it claims that the bootloader is still unlocked. I have no way of verifying this, but if true, I'm only half screwed until somebody finds a root method for the new firmware.
If/when that happens I'll be more than happy to flash away from Verizon's bs nonsense.
Grrr...
Click to expand...
Click to collapse
Did you try re-rooting using current methods?
mcduck$ said:
I was runing the stock touchwiz rom (with the VRGL2 or 1 baseband) rooted, stock recovery, and the bootloader unlocked.
I just checked the EZ unlocker app and it claims that the bootloader is still unlocked. I have no way of verifying this, but if true, I'm only half screwed until somebody finds a root method for the new firmware.
If/when that happens I'll be more than happy to flash away from Verizon's bs nonsense.
Grrr...
Click to expand...
Click to collapse
Wow rooted stock with stock recovery. Why not custom recovery? That probably the reason the update went through. Still ridiculous though, don't get me wrong. I'm guessing you weren't doing a lot of flashing.
Sent from my Nexus 7 using Tapatalk 2
Zalithian said:
Did you try re-rooting using current methods?
Click to expand...
Click to collapse
Negative. I currently feel like crap (see OP) and don't feel like messing with my Windows laptop to try it.
Do you think there's any chance I could brick my phone when I attempt it? Or is it simply a will work/won't work thing?
mcduck$ said:
Negative. I currently feel like crap (see OP) and don't feel like messing with my Windows laptop to try it.
Do you think there's any chance I could brick my phone when I attempt it? Or is it simply a will work/won't work thing?
Click to expand...
Click to collapse
Pretty sure it will just work or fail, but I'd wait for confirmation from someone else first - better safe than sorry.
Can you supply your new Baseband Version number?
I just froze sdm 1.0. I went to the software update and it crashed. I so let's hope that stops the update...
Sent from Land Line using pay phone
epikos said:
Can you supply your new Baseband Version number?
Click to expand...
Click to collapse
I535VRLG7
epikos said:
Can you supply your new Baseband Version number?
Click to expand...
Click to collapse
marcucci217 said:
Wow rooted stock with stock recovery. Why not custom recovery? That probably the reason the update went through. Still ridiculous though, don't get me wrong. I'm guessing you weren't doing a lot of flashing.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I was going to play around with flashing different roms eventually, but after upgrading from a decrepit half working ICS flashed Droid X I was just happy to have fully working phone again. Unfortunately I was under the false impression that the jerks at Verizon would have given me the option to accept their so-called upgrade.
Didn't they already remove local search on Verizon? My phone came that way. Of course I didn't stay on stock once we were freed...
rooting with the rootdebugfs tool should still work!
I woke up to a failed update message. Ran the update again to see why it failed and it fails because it reboots into custom recovery. Rooted, unlocked, stock. Just have some apps disabled or frozen.
Can anyone point out where the in the directory the downloaded update zip would go to?
I didn't get an update message but I did check for one it was available for me. So I ticked ok and it downloaded but failed to update as expected because of the custom recovery I have in place.
But I can't find where the zip file download to.
I wanted to try and see if Chainfire's Mobile ODIN Pro would root the updated zip as it claims.
Cache>fota>update zip...you'll see it
sent from my freed beast...&ikiller
Yes my laziness allowed verizon to update both of my SGS3 to I535VRLG7. I hope I can reroot when I get a chance later.
I was running stock root on both devices.
Sent from my SCH-I535 using xda premium
Successful OTA Flash using Mobile Odin Pro and Kept Root/Unlocked Status
Hulk0069 said:
Cache>fota>update zip...you'll see it
sent from my freed beast...&ikiller
Click to expand...
Click to collapse
Thanks, running a backup now before I try Mobile ODIN Pro. Will update this post:
Edit: Ok, it seems I have a successful flash using Mobile ODIN Pro.
Mobile Odin Pro gave me some Warnings in advance before continuing the Flash.
1) EverRoot may need to remove Google Maps during the flash to free up some space... yadda yadda..
2) The Modem Image on your device does not match the signature check....yadda yadda..
3) 5 out of 499 system files do not match the signature checks in the OTA zip... yadda yadda..
NOTE: I disabled signature checks on both warnings before proceeding.
But you do that AT YOUR OWN RISK!!
From what I gather, Mobile Odin made its own OTA zip from the target file before flashing it
I"ve uploaded some screen shots.
IMPORTANT!
PLEASE RUN A BACK UP before attempting anything risky like this.
ALSO! and VERY IMPORTANT!!
If you are using CWM as your recovery PLEASE PLEASE PLEASE check the size of your backup before proceeding with the update.
It seems CWM is not working properly on my SGSIII because the backup file sizes were only about 22 MB's large.. and thats is SO NOT GOOD!!
I went into GooManager and Flashed TWRP over CWM and ran a backup via TWRP and checked the file size to be in the range of 2.34GB's and thats what it should be (IMO). The only thing that bugs me about both recoveries is the date is 1979-12-31.. and thats definately wrong..
Anyways, my way of checking for root after an OTA is to run Titanium Backup because it always asks for SuperUser Rights before loading.
So all is well with that and checking to see if the Bootloader on my device was still Unlocked with EZ-Unlock said it still was..
Thats all I can think for now..
Hulk0069 said:
Cache>fota>update zip...you'll see it
sent from my freed beast...&ikiller
Click to expand...
Click to collapse
Stock rooted & it tried & failed 2x to do the update and there is nothing in /fota/
I still have root
Second attempt it booted into recovery & I just restarted as it had a fail error
I am scared that i know the answer to this but thought i would ask. I was rooted, unlocked the bootloader the whole bit and was running Jellywiz for a while. I decided to go back to stock via restore. My phone started downloading the latest verizon update and without thinking i agreed to it. I lost root and was wondering if there is a easy way to get it back without physically going through the whole rooting process again? i tried installing supersu and doing the update but that did not work. Thanks in advance
You could try Odin-ing a image thats already rooted but honestly to be safe I'd just go through the steps again. I have done that myself once (not on a samsung phone) . Even though it sucks to lose your setup I'd rather be careful then risk a brick. Just my .02 cents though.
I followed this after update no issues
http://forum.xda-developers.com/showthread.php?p=31485604
Sent from my SCH-I535 using Tapatalk 2
AJ26T said:
I followed this after update no issues
http://forum.xda-developers.com/showthread.php?p=31485604
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thank you, i will give it a shot when i get home tonight
all current root methods work with the latest ota...just reroot and enjoy.
My OTA Jelly Bean update does nothing but fail. It gets as far in the update as having the little 'Droid with the progress bar underneath, but gets 1/3 of the way and fails every time. I AM rooted.
Tried the following:
Wifi
4G
3G
Factory Reset
Removing SD
Putting SD back in
Updating while rooted (didn't mean to)
Updating without root
Updating while on Temp Unroot with Voodoo Rootkeeper
I'm starting to get aggravated, and I really don't want to have to go through Verizon customer service. Any ideas?
(PS: First post!)
Flameninja00 said:
My OTA Jelly Bean update does nothing but fail. It gets as far in the update as having the little 'Droid with the progress bar underneath, but gets 1/3 of the way and fails every time. I AM rooted.
Tried the following:
Wifi
4G
3G
Factory Reset
Removing SD
Putting SD back in
Updating while rooted (didn't mean to)
Updating without root
Updating while on Temp Unroot with Voodoo Rootkeeper
I'm starting to get aggravated, and I really don't want to have to go through Verizon customer service. Any ideas?
(PS: First post!)
Click to expand...
Click to collapse
Hi, did you remove bloatware? Possibly the OTA refuses because of this (was in my case....)
Furthermore, attention to how you proceed with the root - in the process of updating I've lost mine - so do check out the psosts regarding root/update, it might work for you
flying_dutchman said:
Hi, did you remove bloatware? Possibly the OTA refuses because of this (was in my case....)
Furthermore, attention to how you proceed with the root - in the process of updating I've lost mine - so do check out the psosts regarding root/update, it might work for you
Click to expand...
Click to collapse
Yes, I did remove bloatware, but when I factory reset, they came back, and worked fine.
Did what 90%+ of posts say. Use Voodoo to "hide" your root while you update, then restore.
Update still failed. Will be calling Verizon when I get home from class today because it's just making me mad at this point.
UPDATE:
Talked to Verizon, and the tech (who is a fellow phone nerd) says that the first step in the update is to check the bootloader. If it's been tampered, it will fail. He also said that if I can pull it back all the way to factory everything, no root, and they can't tell the bootloader has been modified, then they'll replace it. If they see the bootloader's been touched, they're gonna charge me $299.
I have rooted via MotoFail2Go, would a step in that process be to modify the bootloader? Pardon my ignorance, I haven't done any tinkering into real modifications. Although, now I'm gonna go back and play around with my Droid X
Flameninja00 said:
Yes, I did remove bloatware, but when I factory reset, they came back, and worked fine.
Did what 90%+ of posts say. Use Voodoo to "hide" your root while you update, then restore.
Update still failed. Will be calling Verizon when I get home from class today because it's just making me mad at this point.
UPDATE:
Talked to Verizon, and the tech (who is a fellow phone nerd) says that the first step in the update is to check the bootloader. If it's been tampered, it will fail. He also said that if I can pull it back all the way to factory everything, no root, and they can't tell the bootloader has been modified, then they'll replace it. If they see the bootloader's been touched, they're gonna charge me $299.
I have rooted via MotoFail2Go, would a step in that process be to modify the bootloader? Pardon my ignorance, I haven't done any tinkering into real modifications. Although, now I'm gonna go back and play around with my Droid X
Click to expand...
Click to collapse
I'm having the same exact software. I uninstalled and froze a few bloatwear. Used MotoFail2Go to get my root. So what do we do now??? are you tell me we're stranded unless we beef up another 300.00 for a new device?????? Nahhh all these nerds on XDA someone's gotta have an answer....................right?
I'm glad I'm not the only one having issues, but I agree. Someone's gotta have an idea on what to do, or try next.
Sent from my DROID RAZR HD using xda app-developers app
Well I gave up. Luckily I got Verizon to send me another device
Sent from my DROID RAZR HD using xda app-developers app
same thing happened to me..and yes they gave me another device too...
Ncruze said:
Well I gave up. Luckily I got Verizon to send me another device
Click to expand...
Click to collapse
johnxpotter said:
same thing happened to me..and yes they gave me another device too...
Click to expand...
Click to collapse
I'm assuming you both were rooted via MotoFail2Go? What did you do before you sent it in to hide your root? Just unrooted and restore to factory?
Thanks everybody for your help!!!
Sent from my DROID RAZR HD using xda app-developers app
Cool did your new device come pre installed with job? If not did you have any problems upgrading to job on ur replacement device?
Sent from my DROID RAZR HD using xda app-developers app
Not that it matters much anymore, but with root, if you actually deleted bloatware apps with titanium, or froze them, but didnt defrost them, the update will fail. Also, if you had safestrap installed, the OTA will fail.
Most you want to do with the bloatware is just freeze it. and then remember to defrost it before the OTA.
Gotta be careful.
djousma said:
Not that it matters much anymore, but with root, if you actually deleted bloatware apps with titanium, or froze them, but didnt defrost them, the update will fail. Also, if you had safestrap installed, the OTA will fail.
Most you want to do with the bloatware is just freeze it. and then remember to defrost it before the OTA.
Gotta be careful.
Click to expand...
Click to collapse
The bloatware came back and works fine after a factory reset though.
Are you telling me I'm screwed then?
Sent from my DROID RAZR HD using xda app-developers app
No, you are not screwed. You may have to reload original ICS from FBR process. It is documented on this site. I had to do that not because the OTA failed, but because I lost root.
"UPDATE:
Talked to Verizon, and the tech (who is a fellow phone nerd) says that the first step in the update is to check the bootloader. If it's been tampered, it will fail."
I have the Dev Edition with an unlocked Bootloader.. is this why my update is failing?
My Jelly Bean OTA gets all the way to the last tiny bit, then right before the end Andy Android ends up on his back with the red triangle over his open stomach, my phone reboots, goes through the update process and shows update failed but I'm running Jelly Bean.
When I try to load the update my self through recovery, same thing happens, but the error shows....
assert failed:motorola.update_bl_backup()
Any one...Any one...Bueller.
rebretz000 said:
My Jelly Bean OTA gets all the way to the last tiny bit, then right before the end Andy Android ends up on his back with the red triangle over his open stomach, my phone reboots, goes through the update process and shows update failed but I'm running Jelly Bean
Click to expand...
Click to collapse
Mine fails 1/3 of the way up the bar, but the animation is the same.
Sent from my DROID RAZR HD using xda app-developers app
Hi I am using galaxy S2 i1900g. yesterday i downloaded the jellybean update for my device OTA. when installing it said device will reboot .
After the droid loading symbol it rebooted and now its stuck where the device name "Samsung GALAXY SII" comes and its stuck here for the past 2 and a half hours .
what should i do..... should i reset the device in the middle of installation but that will curru[pt the device right?? Has the installation failed.???? please help
I am running stock 4.1.2 rooted and froze SDM 1.0 with titanium backup to avoid the constant update reminders.
I am now curious can I accept the updates and keep root somehow?
Is something like OTA root keeper worthwhile?
You can still root but cannot unlock the bootloader. I'd recommend reading the 4.3 sticky thread before taking the ota even if you want to stay stock.
Sent from my d2lte using XDA Premium 4 mobile app
dpeeps74 said:
You can still root but cannot unlock the bootloader. I'd recommend reading the 4.3 sticky thread before taking the ota even if you want to stay stock.
Sent from my d2lte using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Are you saying that because of the 4.3 issues?
I would rather not mess with the phone but I just got a gear 2 neo and it will not connect. I think this is because of the older android version. The specs on the gear software say it requires 4.2 or higher
scottfarcuz said:
Are you saying that because of the 4.3 issues?
I would rather not mess with the phone but I just got a gear 2 neo and it will not connect. I think this is because of the older android version. The specs on the gear software say it requires 4.2 or higher
Click to expand...
Click to collapse
Ya you need 4.3.
So you have options, since you're have a galaxy gear you're probably going to be running stock TouchWiz, so I would just take the upgrade.
You can root later, but the gear would never work with aosp anyway. Safestrap can make your phone run pretty well with a TouchWiz custom rom if you eventually decide you want one.
Or you can load a custom TouchWiz 4.3 rom right now and see if it connects, then you wouldn't lock your phone down permanently.
Sent from my HTC6525LVW using Tapatalk
Id like to go with a custom rom but don't have a clue what I'm doing.
Thanks for the help
scottfarcuz said:
Id like to go with a custom rom but don't have a clue what I'm doing.
Thanks for the help
Click to expand...
Click to collapse
OK then read the sticky threads in the development section, everything there has guides available for rooting and installing roms, then ask more questions if you have them.
Make sure you're reading the older sticky thread, not the 4.3 one.
Sent from my HTC6525LVW using Tapatalk
I've been unable to even get the OTA to work. It downloads then fails on install.
I have reset the flash counter but thought that was all that would be required to repair/delete before running the OTA update.
Does anyone have a suggestion?
Just to clarify the phone is currently rooted (casual method) on 4.1.2. I never touched the rom or bootloader after rooting i just installed titanium backup and froze all the bloat. Id like to get the OTA even if i lose root.
I reset the flash counter with triangle away and did a batch unfreeze with titanium backup.The OTA downloads then fails on install.
You would probably need to unfreeze everything for the update to work, at least thats what I have heard.
Sent from my SCH-I535 using Tapatalk
scottfarcuz said:
I've been unable to even get the OTA to work. It downloads then fails on install.
I have reset the flash counter but thought that was all that would be required to repair/delete before running the OTA update.
Does anyone have a suggestion?
Just to clarify the phone is currently rooted (casual method) on 4.1.2. I never touched the rom or bootloader after rooting i just installed titanium backup and froze all the bloat. Id like to get the OTA even if i lose root.
I reset the flash counter with triangle away and did a batch unfreeze with titanium backup.The OTA downloads then fails on install.
Click to expand...
Click to collapse
Use this thread to Odin flash 4.3. It's the exact same as taking the Ota.
http://forum.xda-developers.com/showthread.php?t=2586319
I'm sure you already know what taking the update entails, just be absolutely sure it's what you want to do before you flash it. There's no going back.
Sent from my HTC6525LVW using Tapatalk